HP OneView for VMware vCenter - Manual (Page 79)

c-Class server blade and that the corresponding Onboard Administrator is accessible from
the default system browser on the system where Insight Control for vCenter is installed.
For all other events delivered by Insight Control for vCenter to vCenter Server, the HP SNMP
agents or HP CIM providers must be installed and configured.
•
Verify that the Onboard Administrator is configured to forward events to Insight Control for
vCenter.
1.
Access the Insight Control for vCenter Home Settings page. For more information, see
“Configuring the Server Module for vCenter” (page 7) .
2. Click the Configuration tab.
3. Verify that OA Settings Forward Events is set to Yes. If No is currently selected, select
Yes, and then click Save.
Firmware inventory information is not shown
Possible causes: Insight Control for VMware vCenter supports firmware discovery only on ESXi
hosts that have the HP ESXi offline bundle for VMware installed. The ESXi user name and password
are required for communication with HP CIM providers.
•
If your login credentials are not valid, the following message is displayed:
There are no firmware components to display. The Insight Control for vCenter
plugin was unable to login to the ESXi host.
Please check the Host Settings in the properties page for this host.
•
If you have not configured login credentials, the following message is displayed:
•
If the host is not running ESXi, the following message is displayed:
There are no firmware components to display.
Firmware inventory is only supported on hosts running ESXi.
•
If the HP ESXi offline bundle for VMware is not installed on the host, the following message
is displayed:
There are no firmware components to display.
The HP ESXi Offline Bundle for VMware is not installed on this host.
•
If some other error occurs, the following message is displayed:
There are no firmware components to display.
An error occurred while discovering firmware.
For more information, see the Insight Control for vCenter logs. For information about accessing
the logs, see
“Viewing the log files” (page 73) .
Error No Virtual Connect information is available for this host
occurs
The following scenarios can cause this error:
•
Servers are not blade servers.
•
The Virtual Connect credentials are not valid.
•
Other errors occurred while retrieving Virtual Connect data.
For more information, see the Insight Control for vCenter logs. For information about accessing
the logs, see
“Viewing the log files” (page 73) .
Troubleshooting the Storage Module for vCenter
This section includes troubleshooting information specific to the Storage Module for vCenter. For
general Insight Control for vCenter troubleshooting, see
“Troubleshooting Insight Control for vCenter”
Troubleshooting the Storage Module for vCenter 79