Nagios Support Forum

Posted: **Tue Jun 03, 2014 7:01 am**

Hi All,

We are trying to do snmpwalk v3 to the firewall as below, we are receving the time out response from the firewall for the root user and when I ran with the nagios user I have got the below error

nagios@nagios-p ~]$ snmpwalk -v3 -a MD5 -x DES -l authpriv -u 'string' -A 'string' -X 'string' IP address

Code: Select all

No log handling enabled - turning on stderr logging
Did not find 'zeroDotZero' in module SNMPv2-SMI (/usr/share/snmp/mibs/IP-MIB.txt)
Did not find 'zeroDotZero' in module SNMPv2-SMI (/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt)
Did not find 'zeroDotZero' in module SNMPv2-SMI (/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt)

and we could find zerodotzero module in SNMPv2-SMi, Please find the below for response.

grep -i zerodotzero SNMPv2-SMI.txt
zeroDotZero OBJECT-IDENTITY

Please also find the output of grep -5 zeroDotZero /usr/share/snmp/mibs/*

Code: Select all

/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-IMPORTS
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MODULE-IDENTITY, OBJECT-TYPE,
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- Integer32, Unsigned32,
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- NOTIFICATION-TYPE, Counter32,
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt: Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- TEXTUAL-CONVENTION, RowStatus,
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- TruthValue FROM SNMPv2-TC
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MODULE-COMPLIANCE, OBJECT-GROUP,
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- NOTIFICATION-GROUP FROM SNMPv2-CONF
--
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- Each instance that fills the wildcard is independent of any
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- additional instances, that is, wildcarded objects operate
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- as if there were a separate table entry for each instance
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- that fills the wildcard without having to actually predict
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- all possible instances ahead of time."
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt: DEFVAL { zeroDotZero }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- ::= { mteTriggerEntry 6 }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-mteTriggerValueIDWildcard OBJECT-TYPE
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- SYNTAX TruthValue
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MAX-ACCESS read-create
--
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- Each instance that fills the wildcard is independent of any
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- additional instances, that is, wildcarded objects operate
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- as if there were a separate table entry for each instance
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- that fills the wildcard without having to actually predict
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- all possible instances ahead of time."
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt: DEFVAL { zeroDotZero }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- ::= { mteObjectsEntry 3 }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-mteObjectsIDWildcard OBJECT-TYPE
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- SYNTAX TruthValue
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MAX-ACCESS read-create
--
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MAX-ACCESS read-write
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- STATUS current
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- DESCRIPTION
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- "The object identifier from the NOTIFICATION-TYPE for the
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- notification to use if metEventActions has 'notification' set."
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt: DEFVAL { zeroDotZero }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- ::= { mteEventNotificationEntry 1 }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-mteEventNotificationObjectsOwner OBJECT-TYPE
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- SYNTAX SnmpAdminString (SIZE (0..32))
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MAX-ACCESS read-write
--
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- result in operation as one would expect when providing the
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- wrong identifier to a Set operation. The Set will fail or set
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- the wrong object. If the value syntax of the destination
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- object is not correct, the Set fails with the normal SNMP
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- error code."
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt: DEFVAL { zeroDotZero }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- ::= { mteEventSetEntry 1 }
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt-mteEventSetObjectWildcard OBJECT-TYPE
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- SYNTAX TruthValue
/usr/share/snmp/mibs/DISMAN-EVENT-MIB.txt- MAX-ACCESS read-write
--
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt-DISMAN-SCHEDULE-MIB DEFINITIONS ::= BEGIN
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt-
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt-IMPORTS
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt: Integer32, Unsigned32, Counter32, mib-2, zeroDotZero
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- FROM SNMPv2-SMI
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt-
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- TEXTUAL-CONVENTION,
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- DateAndTime, RowStatus, StorageType, VariablePointer
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- FROM SNMPv2-TC
--
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- MAX-ACCESS read-create
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- STATUS current
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- DESCRIPTION
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- "An object identifier pointing to a local MIB variable
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- which resolves to an ASN.1 primitive type of INTEGER."
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt: DEFVAL { zeroDotZero }
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- ::= { schedEntry 11 }
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt-
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt-schedValue OBJECT-TYPE
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- SYNTAX Integer32
/usr/share/snmp/mibs/DISMAN-SCHEDULE-MIB.txt- MAX-ACCESS read-create
--
/usr/share/snmp/mibs/IP-MIB.txt-
/usr/share/snmp/mibs/IP-MIB.txt-IMPORTS
/usr/share/snmp/mibs/IP-MIB.txt- MODULE-IDENTITY, OBJECT-TYPE,
/usr/share/snmp/mibs/IP-MIB.txt- Integer32, Counter32, IpAddress,
/usr/share/snmp/mibs/IP-MIB.txt- mib-2, Unsigned32, Counter64,
/usr/share/snmp/mibs/IP-MIB.txt: zeroDotZero FROM SNMPv2-SMI
/usr/share/snmp/mibs/IP-MIB.txt- PhysAddress, TruthValue,
/usr/share/snmp/mibs/IP-MIB.txt- TimeStamp, RowPointer,
/usr/share/snmp/mibs/IP-MIB.txt- TEXTUAL-CONVENTION, TestAndIncr,
/usr/share/snmp/mibs/IP-MIB.txt- RowStatus, StorageType FROM SNMPv2-TC
/usr/share/snmp/mibs/IP-MIB.txt- MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
--
/usr/share/snmp/mibs/IP-MIB.txt- MAX-ACCESS read-only
/usr/share/snmp/mibs/IP-MIB.txt- STATUS current
/usr/share/snmp/mibs/IP-MIB.txt- DESCRIPTION
/usr/share/snmp/mibs/IP-MIB.txt- "A pointer to the row in the prefix table to which this
/usr/share/snmp/mibs/IP-MIB.txt- address belongs. May be { 0 0 } if there is no such row."
/usr/share/snmp/mibs/IP-MIB.txt: DEFVAL { zeroDotZero }
/usr/share/snmp/mibs/IP-MIB.txt- ::= { ipAddressEntry 5 }
/usr/share/snmp/mibs/IP-MIB.txt-
/usr/share/snmp/mibs/IP-MIB.txt-ipAddressOrigin OBJECT-TYPE
/usr/share/snmp/mibs/IP-MIB.txt- SYNTAX IpAddressOriginTC
/usr/share/snmp/mibs/IP-MIB.txt- MAX-ACCESS read-only
--
/usr/share/snmp/mibs/SNMPv2-SMI.txt- Text ::= value(IA5String)
/usr/share/snmp/mibs/SNMPv2-SMI.txt-END
/usr/share/snmp/mibs/SNMPv2-SMI.txt-
/usr/share/snmp/mibs/SNMPv2-SMI.txt--- definitions of administrative identifiers
/usr/share/snmp/mibs/SNMPv2-SMI.txt-
/usr/share/snmp/mibs/SNMPv2-SMI.txt:zeroDotZero OBJECT-IDENTITY
/usr/share/snmp/mibs/SNMPv2-SMI.txt- STATUS current
/usr/share/snmp/mibs/SNMPv2-SMI.txt- DESCRIPTION
/usr/share/snmp/mibs/SNMPv2-SMI.txt- "A value used for null identifiers."
/usr/share/snmp/mibs/SNMPv2-SMI.txt- ::= { 0 0

Is there anything missing on nagios server, which is failing snmpwalk to the firewalls.

Posted: **Tue Jun 03, 2014 1:12 pm**

Are your files actually named [mib name].txt-? The hyphen will almost definitely cause snmp to miss those entirely or at least load them out of proper order and cause issues like this.

Posted: **Wed Jun 04, 2014 3:43 am**

Hi sreinhardt,

Thanks for your reply, Please find the below for the names of mibs,

-rw-rw-r--. 1 root root 182K Nov 22 2013 IP-MIB.txt
-rw-rw-r--. 1 root root 67K Nov 22 2013 DISMAN-EVENT-MIB.txt
-rw-rw-r--. 1 root root 25K Nov 22 2013 DISMAN-SCHEDULE-MIB.txt

The mibs have .txt only, still why I am receiving zerodorzero module is not found error. and I want to know will it affect the snmpwalk v3 to the firewall even the snmp is configured properly at both the ends

Posted: **Wed Jun 04, 2014 3:14 pm**

I would suggest by starting with a reinstall of net-snmp. This seems to be a common issue if the mib was overwritten or otherwise has issues.

Code: Select all

yum reinstall net-snmp

Nagios Support Forum

SNMPWalk v3 error

SNMPWalk v3 error

Re: SNMPWalk v3 error

Re: SNMPWalk v3 error

Re: SNMPWalk v3 error