- This article explains how to solve the hardware monitoring problem encountered when using SNMP-based connectors with PATROL Agent v.9.5.00.02
- Connectors, SNMP
Unable to Monitor Hardware Using SNMP-based Connectors with PATROL Agent v.9.5.00.02
KB1162 - Nov 26, 2014
SNMP-based connectors are not working as expected when using PATROL Agent v.9.5.00.02 with Hardware Sentry KM for PATROL, although the configuration is correct (SNMP community string, port, etc.). The error message “Unable to snmp_walk on…” appears in the KM debug logs or in the System Output Window even though the SNMP walk/get command works properly.
Note: To ensure that the SNMP Walk command returns results, you can perform the snmpwalk -v1 -c HOSTNAME OID command in a third-party utility (e.g. snmpwalk) against the same OIDs.
This is a known issue identified for the PATROL Agent v.9.5.00.02 and registered as QM001859325 (PATROL Agent terminated abnormally when snmp_walk PSL function referred the uninitialized memory block.)
To solve this issue, you just have to update to PATROL Agent v.9.5.00.03 or higher.
- All SNMP-based Connectors Fail for one Hour before Reactivating
- Collecting an SNMP Walk/Dump
- Hardware Monitoring: Monitoring Servers Using SNMP
- Hardware Monitoring: SNMP-based connectors test fails with errno: 100 on Linux
- Hardware Monitoring: Understanding Missing Devices and Connector Failures
- Hardware Sentry: Some Connectors Shows a Zero Byte Size
- Instances are Missing Even Though Connectors Are Properly Loaded
- Monitoring HP Blade Chassis Virtual Connect with Hardware Sentry
- Monitoring HP Blade Systems with Hardware Sentry
- No Storage Connector Activating when Monitoring Dell Servers
- SNMP 'get_next' fails on Network adapter on HP ProLiant Servers
- SNMP-Based Connectors Stopped Working