HPE Community
Server Management - Systems Insight Manager
1830801 Members
2791 Online
110016 Solutions
New Discussion

Who Me Too'd this topic

Adam X. White
Advisor

‎09-08-2011 08:54 PM

‎09-08-2011 08:54 PM

Wrong primary IP on vSphere guests

Hi all

 

I have a couple of vSphere VMs running Windows server which have multiple NICs attached to different networks, e.g. MSCS heartbeat NIC. These VMs are not directly managed by SIM but have been detected via the vSphere hosts.

 

Unfortunately SIM is attempting to monitor these servers via the "wrong" IP address, which is not accessible from the CMS. For example if my CMS is 192.168.1.1 and my cluster node VM is 192.168.1.2 with a heartbeat address of 10.0.0.1 (not routable from 192.168.1.0), SIM shows the primary IP address 10.0.0.1 for the VM. The VMs appear as down in SIM with a message "The system is down, or the system has a firewall that prevents any access." in Health Status (ping failed).

 

If I try to Edit System Properties on the VM, the only option in the Primary IP drop-down list is the "wrong" address. In vSphere the virtual machine summary page shows the "correct" IP address by default and also the other address under "View All". The "Correct" address is assigned to Network adapter 1 in the VM settings.

 

Is there a way to force HP SIM to monitor the VM guest via an IP address I specify?

1 person had this problem.
0 Kudos
Reply
Who Me Too'd this topic
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.