Discussion:
mib file to map an trap oid
(too old to reply)
Pushpa Thimmaiah
2015-10-29 06:06:04 UTC
Permalink
Hi Folks,

I have installed snmpagent (net-snmp-5.7.1) and it sends out trap
.1.3.6.1.4.1.8072.4.2 during its restart. I am not able to map the trap
oid .1.3.6.1.4.1.8072.4.2
I have searched online but didnot get any information . Kindly let me know
what is the mib for .1.3.6.1.4.1.8072.4.2



Thank you,
Pushpa.T
Fulko Hew
2015-10-29 12:34:20 UTC
Permalink
On Thu, Oct 29, 2015 at 2:06 AM, Pushpa Thimmaiah <
Post by Pushpa Thimmaiah
Hi Folks,
I have installed snmpagent (net-snmp-5.7.1) and it sends out trap
.1.3.6.1.4.1.8072.4.2 during its restart. I am not able to map the trap
oid .1.3.6.1.4.1.8072.4.2
I have searched online but didnot get any information . Kindly let me
know what is the mib for .1.3.6.1.4.1.8072.4.2
You will find it in NET-SNMP-AGENT-MIB.
Pushpa Thimmaiah
2015-10-30 05:16:01 UTC
Permalink
Hi Fulko Hew,

Thank you. trap oid 1.3.6.1.4.1.8072.4.2 getting resolved after loading
NET-SNMP-AGENT-MIB as follows.
2015-10-29 16:01:34 172.16.1.xxx(via UDP:
[172.16.1.xxx]:40431->[172.16.1.yyy]) TRAP, SNMP v1, community public
NET-SNMP-MIB::netSnmpNotificationPrefix Enterprise Specific Trap
(NET-SNMP-AGENT-MIB::nsNotifyShutdown) Uptime: 0:00:23.44

I have doubt here,
When I used snmptranslate on 1.3.6.1.4.1.8072.4.2 ,

$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4.2
NET-SNMP-MIB::netSnmpNotificationPrefix.2

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

MIB tree netSnmpNotificationPrefix has only 2 child-nodes
netSnmpNotifications(0) and netSnmpNotificationObjects(1) but I dont know
how oid .1.3.6.1.4.1.8072.4.2 resolved in the traps

$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4
NET-SNMP-MIB::netSnmpNotificationPrefix

$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4.1
NET-SNMP-MIB::netSnmpNotificationObjects

$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4.2
NET-SNMP-MIB::netSnmpNotificationPrefix.2


Thank you,
Pushpa
Post by Fulko Hew
On Thu, Oct 29, 2015 at 2:06 AM, Pushpa Thimmaiah <
Post by Pushpa Thimmaiah
Hi Folks,
I have installed snmpagent (net-snmp-5.7.1) and it sends out trap
.1.3.6.1.4.1.8072.4.2 during its restart. I am not able to map the trap
oid .1.3.6.1.4.1.8072.4.2
I have searched online but didnot get any information . Kindly let me
know what is the mib for .1.3.6.1.4.1.8072.4.2
You will find it in NET-SNMP-AGENT-MIB.
Pranesh Kulkarni
2015-10-30 06:18:30 UTC
Permalink
*Traps*

*SNMPD STOP*
*# /etc/init.d/snmpd stop*
Shutting down snmpd: [ OK ]

#snmptrapd -f -Le
NET-SNMP version 5.7.2.1 AgentX subagent connected
NET-SNMP version 5.7.2.1
2015-10-30 11:46:35 localhost [UDP: [127.0.0.1]:33534->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (7889669) 21:54:56.69
SNMPv2-MIB::snmpTrapOID.0 = OID: NET-SNMP-AGENT-MIB::nsNotifyShutdown
SNMPv2-MIB::snmpTrapEnterprise.0 = OID:
NET-SNMP-MIB::netSnmpNotificationPrefix
AgentX master disconnected us, reconnecting in 15


*SNMPD START*
*#/etc/init.d/snmpd start*
Starting snmpd: [ OK ]

2015-10-30 11:47:33 localhost [UDP: [127.0.0.1]:48886->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3) 0:00:00.03
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::coldStart
SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10



*SNMPD RESTART*
*# /etc/init.d/snmpd restart*
Shutting down snmpd: [ OK ]
Starting snmpd: [ OK ]

2015-10-30 11:48:25 localhost [UDP: [127.0.0.1]:48886->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (5255) 0:00:52.55
SNMPv2-MIB::snmpTrapOID.0 = OID: NET-SNMP-AGENT-MIB::nsNotifyShutdown
SNMPv2-MIB::snmpTrapEnterprise.0 = OID:
NET-SNMP-MIB::netSnmpNotificationPrefix
AgentX master disconnected us, reconnecting in 15
2015-10-30 11:48:25 localhost [UDP: [127.0.0.1]:52598->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2) 0:00:00.02
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::coldStart
SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10


On Fri, Oct 30, 2015 at 10:46 AM, Pushpa Thimmaiah <
Post by Pushpa Thimmaiah
Hi Fulko Hew,
Thank you. trap oid 1.3.6.1.4.1.8072.4.2 getting resolved after loading
NET-SNMP-AGENT-MIB as follows.
[172.16.1.xxx]:40431->[172.16.1.yyy]) TRAP, SNMP v1, community public
NET-SNMP-MIB::netSnmpNotificationPrefix Enterprise Specific Trap
(NET-SNMP-AGENT-MIB::nsNotifyShutdown) Uptime: 0:00:23.44
I have doubt here,
When I used snmptranslate on 1.3.6.1.4.1.8072.4.2 ,
$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4.2
NET-SNMP-MIB::netSnmpNotificationPrefix.2
$ snmptranslate -m all -M ./mibs -Tp .1.3.6.1.4.1.8072.4
+--netSnmpNotificationPrefix(4)
|
+--netSnmpNotifications(0)
| |
| +--nsNotifyStart(1)
| +--nsNotifyShutdown(2)
| +--nsNotifyRestart(3)
|
+--netSnmpNotificationObjects(1)
MIB tree netSnmpNotificationPrefix has only 2 child-nodes
netSnmpNotifications(0) and netSnmpNotificationObjects(1) but I dont know
how oid .1.3.6.1.4.1.8072.4.2 resolved in the traps
$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4
NET-SNMP-MIB::netSnmpNotificationPrefix
$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4.1
NET-SNMP-MIB::netSnmpNotificationObjects
$ snmptranslate -m all -M ./mibs -Tl .1.3.6.1.4.1.8072.4.2
NET-SNMP-MIB::netSnmpNotificationPrefix.2
Thank you,
Pushpa
Post by Fulko Hew
On Thu, Oct 29, 2015 at 2:06 AM, Pushpa Thimmaiah <
Post by Pushpa Thimmaiah
Hi Folks,
I have installed snmpagent (net-snmp-5.7.1) and it sends out trap
.1.3.6.1.4.1.8072.4.2 during its restart. I am not able to map the trap
oid .1.3.6.1.4.1.8072.4.2
I have searched online but didnot get any information . Kindly let me
know what is the mib for .1.3.6.1.4.1.8072.4.2
You will find it in NET-SNMP-AGENT-MIB.
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
--
Thanks,
Pranesh
Loading...