Proliant NIC sensor unable to recognize Gen10 disconnect
Modified on 2025-06-10 12:45:33 +0200
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Important: We no longer maintain this article. The information might be out of date.
I am monitoring ML350 Gen10 through it's iLO and the Proliant Network Interface Sensor is unable to recognize whether the NICs are down or not. iLO does notice the disconnection. All of the NICs, besides one are configured as HyperV virtual switches.
Does the sensor need to be configured differently or is there another way to monitor whether the NICs are up/down?
Article Comments
Thanks for the update, glad it's working now :)
Kind regards,
Stephan Linke, Tech Support Team
Jun, 2018 - Permalink
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
I ditched the Proliant sensors and swapped to SNMP Traffic sensors. They recognize disconnected NICs correctly
https://helpdesk.paessler.com/en/support/solutions/articles/66962-port-down-not-alerting-in-prtg
Jun, 2018 - Permalink