VMM 2.1 problems

[Dmitry Sobolevskiy]

After upgrading to VMM 2.1 from VMM 2.0.2, ESX 3.0 hosts are registered now. However, no individual VMs are being discovered. It doesn't work for the 2.5.4 ESX hosts (which worked before) either. Does HP have a fix?

[Rob Buxton]

It worked here for ESX 3.0.1.
Two servers previously registered and licensed worked as soon as the updated agents were installed. On a couple of unlicensed ESX 3.0.1 Servers I went through the full process of Agent install, registration & licensing and then all worked as well.
It did take a few minutes before the VMM information seemed to populate HPSIM.

Not sure about 2.5.4, our other Servers are 2.5.3 and they're fine as well, again after the update of the VMM agent.

[Dmitry Sobolevskiy]

I can see Virtual Machine hosts (after agent upgrade), but Virtual machines themselves are not being populated/servers are not auto discovered. I can create them manually, that seems to work OK.

[Navigator_1]

referring to the following doc would help you configure the VM's
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00815693

[pal_pal]

There has been a change in the VM discovery mechanism with VMM 2.1. To stop unused VMs from being displayed in the All Systems page, all VMs need to be discovered using SIM.

Once you have configured the VM with proper IP address, you can use the manual discovery and then only the VM shows up on the All systems page.

[dave rowland_2]

I have registered my VM's manually, some work ok and others have unknown status rather than server and not linked to the VM Host. Not sure if its a W2000 vs W2003 issue or if something else is wrong.

Also we have two VM Hosts that have no VM's displayed, even if looking via the host properties it says no VM's registered. THe only difference i can find is we have some VM's registered on those hosts that dont actually exist, they are there for failover from another san and the vmfs volume isnt presented. Looks like a vmm 2.1 bug?