My issue slightly differs from missing adapters in that thread: https://kb.paessler.com/en/topic/64343-not-all-network-adapters-available
Got few Server 2019 Hyper-V hosts running Switch Embedded Teaming over two HPE Ethernet 1Gb 2-port 361i Adapters. This Server 2016+ teaming mode creates virtual adapters for host management, which use the same network stack as VM network adapters, which simplifies design. The foundation of that teaming - HPE 361i Adapters have IP-addresses and other protocols removed for that cause.
What I'm trying to monitor is these adapter physical state... as today one of them had RJ-45 jack disconnected:
Get-NetAdapter Output:
| Name | InterfaceDescription | ifIndex | Status | MacAddress | LinkSpeed |
|---|---|---|---|---|---|
| Ethernet 2 | HPE Ethernet 1Gb 2-port 361i Adapter #2 | 12 | Disconnected | 9C-8E-99-31-81-16 | 0 bps |
| vEthernet (Management) | Hyper-V Virtual Ethernet Adapter | 11 | Up | 9C-8E-99-31-81-17 | 1 Gpbs |
| vEthernet (SMB-2) | Hyper-V Virtual Ethernet Adapter #3 | 10 | Up | 00-15-5D-2C-C9-89 | 1 Gbps |
| Ethernet | HPE Ethernet 1Gb 2-port 361i Adapter | 5 | Up | 9C-8E-99-31-81-17 | 1 Gbps |
| vEthernet (SMB-1) | Hyper-V Virtual Ethernet Adapter #2 | 3 | Up | 00-15-5D-2C-C9-88 | 1 Gbps |
WMI "Windows Network Card" sensor displays me all three virtual management adapters with IP addresses (vEthernet), but not the physical 361i adapters. I already tried switching parent device to "Windows Compatibility - Use counters then WMI" with no luck.
Alternatively, "Hyper-V Network Adapter" sensor somehow also show both 361i physical adapters, however their readings are wrong and physical state is online (which is not true for Ethernet 2 above).
These are HPE Proliant Gen6 and Gen9 servers, which don't support HPE Agentless sensors. I believe alternative SNMP sensors won't tell me if adapter physics is down.
What are my options?
Last change on Jun 22, 2020 1:43:10 PM by
Add comment