User manual HP STORAGE ESSENTIALS STANDARD EDITION SRM SOFTWARE

[. . . ] HP Storage Essentials SRM Enterprise Edition 5. 1 Microsoft Windows Application Integration Software for SAP ACC version A. 01. 00 User Guide T4283-96091 Part number: T4283-96091 First edition: September 2007 Legal and notice information © Copyright 2002-2007 Hewlett-Packard Development Company, L. P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This document contains proprietary information, which is protected by copyright. [. . . ] The Storage specific library calls the Application Integration Software for SAP ACC using the information stored in the registry keys on the local system, and requests a "detach" operation for the SRID. The SAP ACC application log file does not display specific information for actions performed during the detach operation. For more specific information, it is necessary to connect to the Application Integration Software for SAP ACC and look at the log files for the specific instance or monitor the text version of the log file. The Application Integration Software for SAP ACC now has control of the storage operations and will perform the necessary tasks to "detach" or "attach" the storage. In the Application Integration Software log file, a message should be logged indicating that the integration core has received the request. If this message is missing, it would indicate that the 30 Interprocess Communications integration core is not running on that the listener port and the integration library port is not correct. Check to ensure the HP Storage Essentials SRM SAP ACC integration service is running on the HP Storage Essentials SRM server. This is an internal check from the Integration core service to ensure that the Managed node is accessible and configured in the Application Integration Software. If the Managed Node is not accessible, a potential problem can be that communication between OpenSSH from HP-SIM server to Managed Node is broken. Check the OpenSSH installation and run the specified communication checks (see "Installing OpenSSH" on page 25) to ensure communication from HP Storage Essentials SRM and HP SIM to Managed Node. Another potential issue can be that the Managed node is indicated as missing in HP Storage Essentials SRM. This would happen if a Managed node was discovered, but for some reason HP Storage Essentials SRM could not make contact to this node during the last hardware check process. In this case, check that the credentials for the Managed node is correct in HP Storage Essentials SRM and ensure that the CIM extensions service is running on the Managed Node. The Application Integration Software will now call the active host management module added to HP SIM to perform the necessary operations on the Managed node to un-mount and export the file systems associated with this SRID. For this operation to succeed, the OpenSSH communication with the host must be functional. For more details on execution errors, check the tasks log in HP SIM. If some user or process is still accessing a file system, it is possible that the operation will fail. In this case, ensure that application shutdown was performed correctly, and that all processes using this file system is stopped. Un-present physical storage from the Host. The Integration core uses the HP Storage Essentials SRM API to request a provisioning-action for the specific storage array in order to remove the presentations for the specific physical storage from the Managed Node. Provisioning-errors can occur if the service processor (SVP) of the storage array is in a locked status. It is important to minimize the use of the SVP for any storage changes, instead, it is recommended to perform all storage changes using HP Storage Essentials SRM. [. . . ] Please consult the corresponding vendor documentation. Troubleshooting This section describes the following: · Central Instance Scripts, page 65 · Database Instance Scripts, page 66 Central Instance Scripts If the scripts developed for a particular system fail to start or stop the SAP Central instance, the following troubleshooting procedure can be followed: User Guide 65 1. Verify that all the correct input parameter are provided, for example SAP system ID, Central Instance hostname, etc. Verify the path directories used in the script match the existent directory paths in the actual host where the scripts are executed. Make necessary corrections to match the path directories. [. . . ]