CMS server not identified

[ms.tim]

In attachment you will find All Systems screenshot.
the third server is CMS.
it is also our lab machine and we are runing some virtual machines for testing purposes via VMware and MS Virtual Server 2005.
VMware installed few virtual LAN connections and one of those IP addresses is represented as System Address.
any idea how to make Incight Manager discover CMS's "true" IP address?
I think that it is the reason why the discover doesn't discover CMS properly.
Under Status Information in Identity tab (All Systems - click on system name) I have Hardware Status only from ping and not also from SNMP and IM agents.
SNMP service is configured to allow SNMP traps from localhost and trap destination is set to systems "true" IP address.

[David Claypool]

Are you saying that the 3rd item is a VMware ESX server' Service Console? Have you installed the tarball with the agents for ESX? http://www.hp.com/servers/swdrivers

Additionally, there are sections on HP SIM managing both ESX and MSVS in the Best Practices white papers for each environment at http://www.hp.com/servers/activeanswers --> Infrastructure Solutions --> Virtualization