i browsed theses mib files, but could'nt find the correct O.I.D that i receive from the 5324 switch on my supervision server using snmptrapd daemon :
O.I.D received : .1.3.6.1.4.1.89.0.151
string received : \'enterprises ():%STP-W-PORTSTATUS: g2: STP status Forwarding enterprises ():1 enterprises ():2 enterprises ():0\'
Content of the log file of snmptrapd (using "snmptt" to translate the mibs in a human readable format -
www.snmptt.org )
Thu Oct 18 13:14:49 2007: Unknown trap (.1.3.6.1.4.1.89.0.151) received from sw-5324-04 at:
Value 0: sw-5324-04
Value 1: 192.168.XXX.248
Value 2: 41:6:04:52.30
Value 3: .1.3.6.1.4.1.89.0.151
Value 4: 192.168.XXX.248
Value 5: public
Value 6: .1.3.6.1.4.1.89
Ent Value 0: .1.3.6.1.4.1.89.2.3.1.0=%STP-W-PORTSTATUS: g2: STP status Forwardin
Ent Value 1: .1.3.6.1.4.1.89.2.3.2.0=1
Ent Value 2: .1.3.6.1.4.1.89.57.2.8.1.0=2
Ent Value 3: .1.3.6.1.4.1.89.57.2.8.2.0=0
You may be using the wrong MIB for the 5324. The private enterprise OID prefix shown is 1.3.6.1.4.1.89 which is for RND Networks (Radware). Dell's enterprise prefix is 1.3.6.1.4.1.674 and all of Dell's network products have an organization oid of 10895. You may want to clear out all of the MIBs from your browser and try it again with only the 5324 MIBs loaded.
i know this, but, the trap i receive from this Powerconnect 5324 is really with theses informations (snmptrapd log file) :
Fri Oct 19 10:28:53 2007: Unknown trap (.1.3.6.1.4.1.89.0.151) received from sw-5324-04 at:
Value 0: sw-5324-04
Value 1: 192.168.XXX.248
Value 2: 42:3:19:25.86
Value 3: .1.3.6.1.4.1.89.0.151
Value 4: 192.168.XXX.248
Value 5: public
Value 6: .1.3.6.1.4.1.89
Ent Value 0: .1.3.6.1.4.1.89.2.3.1.0=%STP-W-PORTSTATUS: g1: STP status Forwardin
Ent Value 1: .1.3.6.1.4.1.89.2.3.2.0=1
Ent Value 2: .1.3.6.1.4.1.89.57.2.8.1.0=1
Ent Value 3: .1.3.6.1.4.1.89.57.2.8.2.0=0
Nb : i have more than 10 PowerConnect models 5324 here, and i receive such an O.I.D from nearly all of them...
I believe the MIB you're looking for is the RADLAN-MIB. Within this MIB are the traps supported on the 5324 including rldot1dStpPortStateForwarding. This MIB can be found in the zip file from the link given above. [RADLAN-MIB.rldot1dStpPortStateForwarding=1.3.6.1.4.1.89.0.151] Is this what you are looking for?
Using Dell OMNM 4.3 the trap is translated as a rldot1dStpPortStateForwarding trap, but I'm not sure that the radlan mib pertains also to the 6248. Each switch model has it's own MIB to manage it's set of features and where it says above "RadLan Mib even on the 6248' may not be accurate. The radlan mib is probably not part of the 62xx mib set, but you can download that MIB separately from support.dell.com and it should be in the zip file that also contains the latest firmware. You should also make sure you are using the latest firmware for your switches (3xxx, 5xxx, and 6xxx).
Looking into the same trap from the 3448 using the 34xx mibs found a bug in the apollo.txt which was causing it not to load. I assume this is probably also true for other switches but need to test.
VlanIndex, dot1qFdbId
FROM Q-BRIDGE-MIB;
dellExtension FROM Dell-Vendor-MIB;
should be
VlanIndex, dot1qFdbId
FROM Q-BRIDGE-MIB <------- no ;
dellExtension FROM Dell-Vendor-MIB;
It is my humble opinion since this file has not changed since 2005 and people have reported this bug it should have been fixed by now.
I have tried OMNM twice actually and both times decided not to use it. I am glad that OMNM works for you but I found the functionality lacking, the overhead and lack of functionality unacceptable.
bh1633
909 Posts
0
October 17th, 2007 19:00
fgilain
1 Rookie
•
32 Posts
0
October 18th, 2007 12:00
Value 0: sw-5324-04
Value 1: 192.168.XXX.248
Value 2: 41:6:04:52.30
Value 3: .1.3.6.1.4.1.89.0.151
Value 4: 192.168.XXX.248
Value 5: public
Value 6: .1.3.6.1.4.1.89
Ent Value 0: .1.3.6.1.4.1.89.2.3.1.0=%STP-W-PORTSTATUS: g2: STP status Forwardin
Ent Value 1: .1.3.6.1.4.1.89.2.3.2.0=1
Ent Value 2: .1.3.6.1.4.1.89.57.2.8.1.0=2
Ent Value 3: .1.3.6.1.4.1.89.57.2.8.2.0=0
DELL-Victor
98 Posts
0
October 18th, 2007 13:00
fgilain
1 Rookie
•
32 Posts
0
October 19th, 2007 08:00
Value 0: sw-5324-04
Value 1: 192.168.XXX.248
Value 2: 42:3:19:25.86
Value 3: .1.3.6.1.4.1.89.0.151
Value 4: 192.168.XXX.248
Value 5: public
Value 6: .1.3.6.1.4.1.89
Ent Value 0: .1.3.6.1.4.1.89.2.3.1.0=%STP-W-PORTSTATUS: g1: STP status Forwardin
Ent Value 1: .1.3.6.1.4.1.89.2.3.2.0=1
Ent Value 2: .1.3.6.1.4.1.89.57.2.8.1.0=1
Ent Value 3: .1.3.6.1.4.1.89.57.2.8.2.0=0
fgilain
1 Rookie
•
32 Posts
0
October 22nd, 2007 14:00
fgilain
1 Rookie
•
32 Posts
0
April 16th, 2008 14:00
DELL-Victor
98 Posts
0
April 16th, 2008 17:00
Rseiwert
11 Posts
0
October 10th, 2011 17:00
This trap is still not resolved even with the RadLan Mib even on the 6248.
snmptranslate .1.3.6.1.4.1.674.10895.5000.2.89.0.151 -Tdo
Dell-Vendor-MIB::rndMib.0.151
rndMib OBJECT-TYPE
-- FROM Dell-Vendor-MIB
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dell(674) dellLan(10895) dellStandard(5000) dellExtension(2) rndMib(89) 0 151 }
DELL-Victor
98 Posts
0
October 11th, 2011 08:00
Using Dell OMNM 4.3 the trap is translated as a rldot1dStpPortStateForwarding trap, but I'm not sure that the radlan mib pertains also to the 6248. Each switch model has it's own MIB to manage it's set of features and where it says above "RadLan Mib even on the 6248' may not be accurate. The radlan mib is probably not part of the 62xx mib set, but you can download that MIB separately from support.dell.com and it should be in the zip file that also contains the latest firmware. You should also make sure you are using the latest firmware for your switches (3xxx, 5xxx, and 6xxx).
Rseiwert
11 Posts
0
October 11th, 2011 11:00
Looking into the same trap from the 3448 using the 34xx mibs found a bug in the apollo.txt which was causing it not to load. I assume this is probably also true for other switches but need to test.
VlanIndex, dot1qFdbId
FROM Q-BRIDGE-MIB;
dellExtension FROM Dell-Vendor-MIB;
should be
VlanIndex, dot1qFdbId
FROM Q-BRIDGE-MIB <------- no ;
dellExtension FROM Dell-Vendor-MIB;
It is my humble opinion since this file has not changed since 2005 and people have reported this bug it should have been fixed by now.
I have tried OMNM twice actually and both times decided not to use it. I am glad that OMNM works for you but I found the functionality lacking, the overhead and lack of functionality unacceptable.
Rseiwert
11 Posts
0
October 11th, 2011 11:00
have 34xx, 53xx, 54xx, and 62xx. I have pages of unknown traps. I have used and built a trap translation for all known traps in the various mibs.