My issue slightly differs from missing adapters in that thread: https://helpdesk.paessler.com/en/support/solutions/articles/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?
Article Comments
Sorry, but Microsoft Switch Embedded Teaming is new industry standard redundancy solution for Hyper-V servers since Windows Server 2016.
For now I will go with “HPE ProLiant via SNMP” sensor, as it reports network adapter connectivity loss. Nevertheless, please review my scenario and find out why WMI sensor doesn’t list physical adapters without IPv4/IPv6 protocols enabled.
Jun, 2020 - Permalink
Hi there,
Thank you for your answer. I will contact you via mail with another idea.
Kind regards,
Andreas Günther
Tech Support, Paessler AG
support@paessler.com
Jun, 2020 - Permalink
Thanks for the registry tweak - I've successfully added these physical adapters participating in Teaming, which actually don't have either IP or MACs assigned.
The great disapointment is WMI Network Adapter sensor simply can't display media failure or administrative down states for like at all :(
Jun, 2020 - Permalink
Hi there,
You're very welcome. I'm sorry to hear that though!
Kind regards,
Andreas Günther
Tech Support, Paessler AG
support@paessler.com
Jun, 2020 - Permalink
Hi there,
Thank you for your message.
Have you tried the native teaming in windows already and does this make a difference?
In case you're using the native windows teaming, have you tried the vendor's teaming software?
Kind regards,
Andreas Günther
Tech Support, Paessler AG
support@paessler.com
Jun, 2020 - Permalink