First off, kudos to the OpManager development team for the vSphere support and the vastly improved VMware monitoring performance. It finally does pretty much everything we've been asking for in an intuitive manner.

That said, I am experiencing some weird reporting with some of the virtual machines in my vSphere environment.

A number of our virtual machines have secondary storage drives that are SAN LUNS attached via the MS iSCSI initiator on a back channel network that is not visible to the public network..

VM IP: 10.10.1.1 <--- Public Network

iSCSI Initiator IP: 192.168.69.1 <-- Back Channel Network

On some of these virtual machines, OpManager is showing the iSCSI address instead of the public address and FQDN. Because of this, OM thinks that the VM is down as it can't communicate with the back channel network. Only some of the virtual machines are experiencing this behavior.

Now, within the vCenter Client Summary tab under IP addresses, it is showing the back channel addresses first, and lists the public IP address under "View All". I suspect that OM is reacting this way because that is what the vSphere API is feeding it.

Is there any way to specify within OpManager the particular IP address to monitor or use for discovery? I am unaware of a method to change what order that vSphere reports the existing addresses but that may also be a potential fix.

Thanks in advance for any advice or direction.