HP OneView for VMware vCenter - Manual (Page 95)

for vCenter provisioning operations on HP arrays. To use the Storage Module for vCenter
provisioning features, you must configure the VMware Administrator role in a vSphere session. For
instructions, see the HP Insight Control for VMware vCenter Server Installation Guide.
Storage Module for vCenter GUI not responsive to mouse clicks
Possible cause: The Temporary Internet Files directory is full.
Action: Delete the temporary files created by Internet Explorer.
Refresh takes a long time to complete
In environments with P6000 EVAs, a data refresh takes a long time.
Possible cause: A hardware failure on a P6000 EVA. Some hardware failures can negatively
impact P6000 Command View performance and lead to significantly longer refresh times by the
Storage Module for vCenter.
Action: Remove or replace any failed drive on the P6000 EVA.
Error Unexpected state: The setup helper has not been created
occurs during array or management server configuration
Possible cause: The Insight Control for vCenter host name contains one or more unsupported
characters.
When you enter a host name, the only supported characters are a–z (case insensitive), 0–9, and
hyphens.
Action: Complete the following procedure:
1.
Open the configuration.json file, which is located in the install folder\uim
(assuming that the default installation directory was used).
2. Change the Insight Control for vCenter host name to the IP address.
3. Save and close the file.
4. Edit the install
folder\storage\jboss\standalone\configuration\standalone.xml
file.
5. Change the <wsdl-host> host name to the IP address.
6. Save and close the file.
7. Restart the HP Insight Control Storage Module for vCenter Service.
8. Restart the vSphere Client.
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 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.
Troubleshooting the Storage Module for vCenter 95