ESX hosts do not show any network connections mapped within Spectrum VHM Manager
Release : 10.3.2 10.4 10.4.1
Component : Spectrum Core / SpectroSERVER
Container models do not participate in polling or connections.
Within the VHM Manager ESX hosts are modeled as container device models.
There won't be a connection between ESX container models and network device connections.
Any connections that you see to an ESX container is not actually its connection but the connection to the VMS within it.
There are only connections between VMs and network devices and this is by design.
| VM————Rpt_Segment ——-|——————Switch
| VM________/ | /
| VM_______/ |/
| / |
| VM————Rpt_Segment— |
The Rpt represents the internal virtual switch in the ESX.
You would need to use the non-VHM SNMP discovered instance of the ESX Model for the network device associations you are seeking (This will be dependant on what data the SNMP agent running on the ESX host is providing to Spectrum - If Mib2 has full support for the interfaces, and if the upstream switch has the info).
Having the device discovered twice in Spectrum is not ideal, but if the container does not have a network address the trap events\alarms will only be asserted on the model SNMP model, and polling would also only happen for the SNMP based ESX model.
You can use Global Collections to logically group ESX Hosts outside of the VHM Manager.