HP Storage Essentials Enterprise Edition Software - Manual (Page 60)

Operational Details 48
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 the Hostagent service is not running.
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 are correct in HP Storage
Essentials SRM and ensure that the CIM extensions service is running on the Managed Node.
8. Un-mount/Export File system.
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 are stopped.
9. 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.
For more details on the failure, check the HP Storage Essentials SRM log files and the storage
array audit trails.
10. Return success/failure.
If all operations are successful, the Integration core will return success status to the integration
library and to the sapacosprep module. If any operation fails during the un-mount or un-present
operations, the Integration core will attempt to roll back any changes, leaving the Managed
Node in the same state that the operation started with, and return “failure” to the integration
library and to the sapacosprep module.
11. Call platform specific library with “deactivate IP”.
SAP ACC resumes control of operations and calls the platform specific library, using the
sapacosprep module, to deactivate the instance virtual IP address. Monitor the SAP ACC
application log for any errors.
12. Unlock Managed Node.
The last step in the operation is for SAP ACC to unlock the Managed Node and allow for any
other operations to be executed on this Managed Node.
In the same way as with the stop and unprepare (detach) process, the operations for prepare
(attach) and start can be initiated from the SAP AC server, but the order in executing some of the
processes is different.