HP OneView for VMware vCenter User Manual
Page 128
HP MSA array information not displayed in StoreFront Module GUI
Possible cause: The SMI-S service on the array might be unresponsive.
Use the following actions to solve this issue. If one action does not work, proceed to the next action.
Action: Restart the HP MSA SMI-S service. This will not affect disk access.
1.
Log in to the SMU interface of the HP MSA array as a user with Manage access. Use the
available management IP address (for example: http://Management_IP_address).
2.
Select Configuration
→Services→Management.
3.
Clear the Storage Management Initiative Specification (SMI-S) check box, and then click Apply.
4.
Select the Storage Management Initiative Specification (SMI-S) check box, and then click Apply.
The SMI-S service is now running.
5.
Refresh the StoreFront Module for vCenter cache.
For instructions, see
“Refreshing StoreFront Module for vCenter data” (page 57)
.
Action 2: Restart the HP MSA array management controller.
IMPORTANT:
This procedure restarts the HP MSA array controller. If you restart a management
controller, communication with it is lost until it restarts successfully . This will not affect disk access.
If the restart fails, the partner management controller remains active with full ownership of operations
and configuration information. Other applications (such as Microsoft VSS and VDS) that rely on
the management controller services might be affected.
1.
Log in to the SMU interface of the HP MSA array as a user with Manage access. Use the
available management IP address (for example: http://Management_IP_address).
2.
Select Configuration
→System Settings→Network Interfaces.
3.
Determine which controller has the IP address used in
.
4.
Select Tools
→Shutdown or Restart Controller.
5.
Select the following:
•
Operation: Restart
•
Controller type: Management
•
Controller: A or B, as determined in
6.
Click Restart now.
7.
Log in to the SMU.
8.
Refresh the StoreFront Module for vCenter cache.
For instructions, see
“Refreshing StoreFront Module for vCenter data” (page 57)
.
HP XP P9000 virtual disk information missing from Storage Overview page
Possible cause: The hostgroup name for the ports on the array exceeds 16 characters.
Action: Rename the hostgroup on the array to a name that is up to 16 characters, and then initiate
a manual cache refresh. When the refresh process is complete, information will be displayed for
the HP XP P9000 virtual disks.
Concatenated replicated LUNs not recognized as replicated LUNs
Replication information is not available for a datastore that consists of two replicated LUNs.
Cause: This configuration is not supported by the StoreFront Module for vCenter.
Duplicate LUNs displayed in StoreFront Module for vCenter interface
Possible cause: When using multipathing, duplicate LUNs might be displayed if a LUN is presented
to a host using different LUN numbers across multiple paths.
128
Troubleshooting