HP OneView for VMware vCenter User Manual

Page 124

Advertising
background image

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

Step 1

.

4.

Select Tools

→Shutdown or Restart Controller.

5.

Select the following:

Operation: Restart

Controller type: Management

Controller: A or B, as determined in

Step 3

6.

Click Restart now.

7.

Log in to the SMU.

8.

Refresh the Storage Module for vCenter cache.

For instructions, see

“Refreshing Storage 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 Storage Module for vCenter.

Duplicate LUNs displayed in Storage 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.

Action: There are two options for addressing this issue:

Reconfigure the LUNs so they have a single LUN number across all paths. For more information,
see article 1003973 in the

VMware Knowledge Base

.

Disable the VMware advanced setting Scsi.CompareLUNNumber.
1.

Select a host in the vSphere Client.

2.

Click the Configuration tab.

3.

Click Advanced Settings in the Software pane.

4.

Click Scsi in the list of advanced settings.

5.

Edit the Scsi.CompareLUNNumber value, and then click OK.

LUN displayed multiple times for VM or datastore that is part of a cluster

Possible cause: The Storage Module for vCenter uses an ESXi Host+LUN number as the unique
identifier. When a single LUN is presented to multiple hosts that are part of a cluster, the LUN is
listed on the Related VMs and Related Datastores pages for each host.

124

Troubleshooting

Advertising