Object value of OID .1.3.6.1.4.1.8072.4.2

[Pushpa Thimmaiah]

Hi All,

I can see a snmp-agent sending out snmpv1 trap OID while restarting.
Please let me know
corresponding mib-object name


:~$* snmptranslate -m all -M ./mibs/ -IR 1.3.6.1.4.1.8072.4.2*
Unknown object identifier: 1.3.6.1.4.1.8072.4.2

:~$ *snmptranslate -m all -M ./mibs/ -Td 1.3.6.1.4.1.8072.4.2*
NET-SNMP-MIB::netSnmpNotificationPrefix.2
netSnmpNotificationPrefix OBJECT-TYPE
-- FROM NET-SNMP-MIB
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
netSnmp(8072) netSnmpNotificationPrefix(4) 2 }


:~$ *snmptranslate -m all -M ./mibs/ -Tp 1.3.6.1.4.1.8072.4.2*
+--netSnmpNotificationPrefix(4)
|
+--netSnmpNotifications(0)
| |
| +--nsNotifyStart(1)
| +--nsNotifyShutdown(2)
| +--nsNotifyRestart(3)
|
+--netSnmpNotificationObjects(1)


Thanks,
Pushpa.T

[Wes Hardaker]

I can see a snmp-agent sending out snmpv1 trap OID  while restarting.

I think that's a mistake and it should be sending ...8072.4.0.2 instead,
which is the shutdown trap. IE, when you're restarting it should be
doing both a shutdown and a restart.

[Pushpa Thimmaiah]

Hi Wes Hardaker,

Adding to previous email. I have verified shutdown traps using net-snmp
5.7.2 and used following procedure


Kept snmptrapd running and authenticate community 'public'
1. stop snmpDaemon
sudo /etc/init.d/snmpd stop

2. add line 'trapsink 192.168.a.b public' in /etc/snmp/snmpd.conf
3. start snmpDaemon
sudo /etc/init.d/snmpd start

Result: snmptrapd shows coldstart traps
2017-05-25 15:18:46 192.168.x.y(via UDP:
[192.168.x.y]:53779->[192.168.a.b]:162) TRAP, SNMP v1, community public
iso.3.6.1.4.1.8072.3.2.10 Cold Start Trap (0) Uptime: 0:00:00.01

4. stop snmpDaemon
sudo /etc/init.d/snmpd stop
Result: snmptrapd shows below traps

2017-05-25 15:19:03 192.168.x.y(via UDP:
[192.168.x.y]:39845->[192.168.a.b]:162) TRAP, SNMP v1, community public
iso.3.6.1.4.1.8072.4 Enterprise Specific Trap (2) Uptime: 0:00:33.38
<---- <comment>Here trap-oid is .1.3.6.1.4.18072.4.2 , Am I correct?
</comment>

I am using ubuntu. Kindly let me know if any configuration info required.

Thank you,
Pushpa.T


---------- Forwarded message ----------
From: Pushpa Thimmaiah <***@gmail.com>
Date: Thu, May 25, 2017 at 1:24 PM
Subject: Re: Object value of OID .1.3.6.1.4.1.8072.4.2
To: Wes Hardaker <***@users.sourceforge.net>
Cc: "net-snmp-***@lists.sourceforge.net" <
net-snmp-***@lists.sourceforge.net>


Hi Wes Hardaker,

snmp-agent sending both 4.0.2 (snmpv2c trap) and 4.2 (snmpv1 trap).


SilverCreek trap-receiver log:-

Thu May 18 2017 16:28:33.27
SNMPv2-SMI:enterprises.8072.4.0.2 SNMPv2c trap from 192.168.x.y
Received Trap OID : 1.3.6.1.4.1.8072.4.0.2
SNMPv2-MIB:sysUpTime.0 22508 type TimeTicks
SNMPv2-MIB:snmpTrapOID.0 SNMPv2-SMI:enterprises.8072.4.0.2 type ObjectID
SNMPv2-MIB:snmpTrapEnterprise.0 SNMPv2-SMI:enterprises.8072.4 type ObjectID

Thu May 18 2017 16:28:33.28
SNMPv2-SMI:enterprises.8072.4.2 SNMPv1 trap from 192.168.x.y
Received Trap OID : 1.3.6.1.4.1.8072.4.2
SNMPv1 Trap PDU fields: V1
Trap agent-addr 10.208.207.62 generic-trap enterpriseSpecific
6 specific-trap 2 time-stamp 22508
Name of the notification received: enterprises.8072.4.2
Notification enterprises: 1.3.6.1.4.1.8072.4 (
SNMPv2-SMI:enterprises.8072.4 )



Is the MIB 1.3.6.1.4.1.8072.4.2 is old/obsolete? I couldnot find
respective MIB object name
in net.

Thank you,

Pushpa.T

Post by Wes Hardaker

Post by Pushpa Thimmaiah
I can see a snmp-agent sending out snmpv1 trap OID while restarting.

I think that's a mistake and it should be sending ...8072.4.0.2 instead,
which is the shutdown trap. IE, when you're restarting it should be
doing both a shutdown and a restart.
--
Wes Hardaker
USC/ISI