- This article describes the procedure to follow if all the SNMP based connectors fail for one hour before reactivating.
- Connectors, SNMP
All SNMP-based Connectors Fail for one Hour before Reactivating
KB1031 - Apr 30, 2010
Every hour, the KM will attempt to detect the SNMP community string if no string is specified. It will check if the SNMP service is running, then look in the snmpd.conf to find the community string.
If this detection fails (it will only try once), the community string will be set to "" i.e. blank for the next hour, until the next discovery. All SNMP connectors will fail during this period.
The issue generally arises on servers that have very heavy CPU usage at certain times of the day and are not able to perform the SNMP service detection within the KM’s timeout period.
Bypass the entire SNMP detection process by setting the variable “/SENTRY/HARDWARE/localhost/snmpCommunity” to the correct string.
- 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
- Unable to Monitor Hardware Using SNMP-based Connectors with PATROL Agent v.9.5.00.02