Hardware Monitoring: SNMP-based connectors test fails with errno: 100 on Linux

Description

When configuring the Hardware Sentry KM to monitor a system running on Linux using SNMP-based connectors such as "Dell OpenManage Server Administrator" or "HP Insight Management Agent - Server", you may get the following error message:

        
SNMP TEST on  ankara: FAILED

          ---------------------

          The SNMP  'get_next' request failed:

          - Host:  ankara

          - Community:  public

          -  OID:1.3.6.1.4.1.674.10892.1.300.10.1

        - errno: 100

If after double-checking that the SNMP test actually fails with the third-party utility snmpwalk and making sure that the system management solution is properly installed and that the snmp daemon is also running, you will have to verify that there is not a configuration problem in your /etc/snmp/snmpd.conf file which prevents the KM/snmpwalk from querying some specific OID’s.

Procedure

1. Open /etc/snmp/snmpd.conf in a text editor
2. Search for the  view all included .1
3. Uncomment the line view all included .1
4. Only allow the specific OIDs that are used by the KM:
   view    systemview    included   .1.3.6.1.2.1.1
   view    systemview    included   .1.3.6.1.2.1.25.1.1
   view    systemview    included   .1.3.6.1.4.1.674.10892
   view    systemview    included   .1.3.6.1.4.1.674.10893
5. Save your changes.
6. Restart the snmp daemon:
   [root@ankara ~]# /etc/init.d/snmpd restart
   Stopping snmpd:                                            [  OK  ]
   Starting snmpd:                                            [  OK  ]
7. Perform the SNMP test again. The report should now show:
   SNMP TEST on ankara: SUCCEEDED
   ------------------------------
   The SNMP 'get_next' request completed successfully:
   - Host: ankara
   - Community: public
   - OID:1.3.6.1.4.1.674.10892.1.300.10.1
   - Value:1.3.6.1.4.1.674.10892.1.300.10.1.1.1      integer      1

   For local monitoring (i.e., PATROL Agent installed on the monitored server), please check that the KM is allowed to communicate with the SNMP agent using at least a read-only community string. You may have to add the following permission in your snmpd.conf, if you have ACL’s implemented rocommunity M0n1t0ring 127.0.0.1

Related Topics

• All SNMP-based Connectors Fail for one Hour before Reactivating
• Collecting an SNMP Walk/Dump
• Hardware Monitoring: Monitoring Servers Using SNMP
• 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