What is the difference between Hardware Sensor (node) and Hardware Sensor (Chassis). I can't seem to find any specific documentation. Is one better that the other with regard to HPE ProLiant DL360 servers (Gen 7, 8 and 10)?
Ashley
What is the difference between Hardware Sensor (node) and Hardware Sensor (Chassis). I can't seem to find any specific documentation. Is one better that the other with regard to HPE ProLiant DL360 servers (Gen 7, 8 and 10)?
Ashley
I see in this document Monitor hardware health (solarwinds.com) that Hardware Monitoring supports certain vendors' chassis. In my environment, when trying to configure an alert and setting the alerting based on the chassis instead of node, the sample net objects show as "sys/chassis-1/fan-module-1-1/fan-1 - RPM on chassis-1" and so on. I think this is based on the actual chassis or physical appliance you bought, which could house several nodes. I'm thinking this is the difference between monitoring several VMs as nodes but monitoring the VM server as a chassis.
Just like you, I see no documentation on this.
I see in this document Monitor hardware health (solarwinds.com) that Hardware Monitoring supports certain vendors' chassis. In my environment, when trying to configure an alert and setting the alerting based on the chassis instead of node, the sample net objects show as "sys/chassis-1/fan-module-1-1/fan-1 - RPM on chassis-1" and so on. I think this is based on the actual chassis or physical appliance you bought, which could house several nodes. I'm thinking this is the difference between monitoring several VMs as nodes but monitoring the VM server as a chassis.
Just like you, I see no documentation on this.
I reached out to SolarWinds and they pointed me to this https://documentation.solarwinds.com/en/success_center/sam/content/sam-asset-inventory-and-hardware-health-monitoring-requirements.htm but it didn't really answer my question.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.