Menu

#507 SNMP problems

open
5
2015-02-24
2009-10-14
Anonymous
No

I'm currently monitoring a number of servers using BigSis 1.02. However there is a linux machine (an uname -a command gives: Linux OBCARCL10 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux) in which all tests based on snmp simply do not work.

An execution of /usr/share/bigsis/uxmon/uxmon -D 5 gives :

Wed Oct 14 12:35:21 2009: uxmon: starting up
SNMP Error:
no response received
SNMPv1_Session (remote host: "170.70.91.189" [170.70.91.189].161)
community: "public"
request ID: -407202069
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/share/bigsister/bin/SNMP_util.pm line 599
SNMPWALK Problem for 1.3.6.1.2.1.25.2.3.1.1 on public@170.70.91.189
at /usr/share/bigsister/bin/snmp.pm line 163
SNMP Error:
no response received
SNMPv1_Session (remote host: "170.70.91.189" [170.70.91.189].161)
community: "public"
request ID: -407202068
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/share/bigsister/bin/SNMP_util.pm line 599
SNMPWALK Problem for 1.3.6.1.2.1.25.2.3.1.3 on public@170.70.91.189
at /usr/share/bigsister/bin/snmp.pm line 163

However the execution of the snmpwalk command in the server where the agent is installed throws the desired informartion:

SNMPv2-MIB::sysDescr.0 = STRING: Linux OBCARCL10 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1737095) 4:49:30.95
SNMPv2-MIB::sysContact.0 = STRING: Root <root@localhost> (configure /etc/snmp/snmp.local.conf)
SNMPv2-MIB::sysName.0 = STRING: OBCARCL10
SNMPv2-MIB::sysLocation.0 = STRING: Unknown (edit /etc/snmp/snmpd.conf)
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORID.1 = OID: IF-MIB::ifMIB
SNMPv2-MIB::sysORID.2 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.3 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.4 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.5 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORID.6 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.7 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.8 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.9 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance

Any hint?

Thanks.

Carlos

Discussion

  • Thomas Aeby

    Thomas Aeby - 2009-10-19

    It seems that you use SNMP v2 when manually doing an snmpwalk, while BigSister will use SNMP v1. Could you please try accessing via SNMP v1 manually, too (class snmpwalk: option "-v 1")? If this does not work, then maybe your SNMP agent has v1 disabled.

    Kind regards,
    Tom

     
  • Thomas Aeby

    Thomas Aeby - 2009-10-19
    • assigned_to: nobody --> aeby
     
  • Nobody/Anonymous

    Hello,

    Thanks a lot Thomas. After searching I have found somewhere that :

    >>64-bit host running a Net-SNMP snmpd older than
    >> version 5.4.1.
    (has a bug which)
    >> causes IPv4 addresses to be
    >> encoded as 64-bit values but marked in the PDU as being four bytes
    >> long.

    So the problem was that we were using Net-SNMP 5.4.1 in the server that we want to monitor. We have moved to Net-SNMP 5.5 and the problem has disappeared.

    Kind regards.

    Carlos

     

Log in to post a comment.