HP OneView for VMware vCenter/Operations Manager/Log Insight manual Gui

Port conflict occurs when trying to configure P6000 Command View and MSA proxy provider for use with Storage Module for vCenter

Possible cause: P6000 Command View and the MSA2000 G2 SMI-S proxy provider cannot coexist on the same server because they use the same ports to communicate.

Action: If you want to manage a P6000 EVA array and an MSA array with the same vCenter management server and the Storage Module for vCenter, do not install the Storage Module for vCenter on the P6000 Command View management server.

MSA2000 G2 or P2000 G3 MSA array information not displayed in Storage 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 MSA2000 G2 or P2000 G3 MSA SMI-S service. This will not affect disk access.

1.Log in to the SMU interface of the MSA2000 G2 or P2000 G3 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 Storage Module for vCenter data.

For instructions, see “Refreshing Storage Module for vCenter data” (page 33).

Action 2: Restart the MSA2000 G2 or P2000 G3 MSA array management controller.

IMPORTANT: This procedure restarts the MSA2000 G2 or P2000 G3 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 MSA2000 G2 or P2000 G3 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 data.

For instructions, see “Refreshing Storage Module for vCenter data” (page 33).

Troubleshooting the Storage Module for vCenter 81