I have implemented ESX 3.0.1, HP Agents 7.7 (hpmgmt-7.7.0-vmware3x), VirtualCenter 2.0.1, SIM 5.1 SP1, VMM 2.1 and SMP 2.1. Discovery of VMs and tying them up to the ESX host works far better than ever before. However a couple of small problems remain.
The name of the discovered VM starts of as the IP address and is eventually replaced by the computer name, that is the NetBIOS name of a Windows VM - but only as long as the VM is on the same subnet as the SIM CMS. I realise that this may be a limitation caused by the broadcast nature of the NetBIOS protocol, but is there a way to get round this?
The VMM does not seem to have an accurate record of the VM state, so when you try things like template creation or live migration they fail due to SIM having the incorrect power state, and you can’t change the power state in SIM due to it believing it has it correct. I can change it within VirtualCenter but that defeats the purpose. Any thoughts?
Any help or guidance would be appreciated.
Thanks, Andy.
