HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

1. Locate the ESX host System Page by searching for it or by selecting it in All
Systems→Virtual Machine Hosts→ESX Hosts nodename.
2. Expand both the Virtual Machines section and the Associations section. If the VM guest
appears in the Virtual Machines section but not in the Associations section, the VMware
WBEM provider might have returned incorrect or incomplete data.
3. Restart the VMware CIM service, and identify the ESX host again:
a. Log on to ESX as root.
b. Enter the following command:
/etc/init.d/sfcbd-watchdog restart
c. Manually re-identify the ESX host using Options→Identify Systems.
HP and VMware are aware of this issue and working on a resolution.
• Check the environment changes:
Verify name resolution of the VM host.◦
◦ Verify the credentials in HP SIM are correct.
◦ Verify network connectivity between the ESX host and the CMS.
VM guests appear without system addresses in HP SIM
Issue
HP SIM shows VM guests with no system addresses (IP addresses) and/or Insight Control virtual
machine management displays two or more VM guests with the same IP address or some guests
with incorrect IP addresses.
Possible causes
This issue may occur if the VM guest was first detected by HP SIM prior to customization or while
powered off. In this situation, HP SIM is unable to perform a complete discovery of the VM guest.
Suggested actions
• Verify that the guests are powered on and fully operational.
• Verify that the guests have valid IP addresses.
• Perform a discovery of the guest(s) in HP SIM:
Select Options→Discovery…1.
2. Do one of the following:
a. If you already have a discovery task for the VM guests, verify their credentials and
execute that discovery task.
b. If you do not have a discovery task for the VM guests, create a new discovery task
for the VM guests with valid credentials for the guest, and execute that task.
Using HP Virtual Connect Flex-10 with VMware ESX
Issue
One physical link from the Flex-10 fabric appears as four Flex-10 NICs (physical NICs) to the
VMkernel. Because there is only one physical link, states of all the Flex-10 NICs change together
so that the link state of individual Flex-10 NICs is reported correctly. As a result, ESX might not be
able to detect failures when a corresponding external uplink is down, even if the SmartLink is turned
on and the Ethernet Connection Mode is connected to disable failover.
Suggested actions
• Before attempting the following workarounds, use the VCEM user interface to place the VC
Domain that contains the blade which will be running ESX into VC Domain Maintenance. To
162 Troubleshooting