The number provided is the bridge port number, not an ifIndex. We will bind
ifIndex and ifName into these traps in a future release of firmware.
The Try this command in the CLI:
"show port count *.*.* |find 321"
And3N 105(rw)->show port count *.*.* |find 321
Port: tg.2.2 MIB2 Interface: 23002 Bridge Port: 321
Using SNMP the MIB object dot1dBasePortIfIndex can be used to translate a
bridge port to an ifIndex. And ifName can then be used to get a port name from
ifIndex.
-----Original Message-----
From: Thorsten Steffen [mailto:[email protected]]
Sent: Friday, March 06, 2009 8:49 AM
To: Enterasys Customer Mailing List
Subject: Spam: [enterasys] Question concerning stp loop protect and stp
spanguard snmp traps
Hello,
I have a question concerning stp loop protect and spanguard snmp
traps.
In the traps there are port numbers listed but I don't know how to map
them to the real physical ports of the devices (e.g. dfe).
For example a loop protect trap contained the information
"dot1dStpPort = 367" when this event happened on port fe.2.48.
A spanguard trap contained "bridge port 321" when this event happened
on one of the ports fe.1.2 and fe.2.2; because there is no log entry on
the dfe I can't exactly find out which of this both ports triggered the
event.
Best Regards and many thanks in advance,
Thorsten Steffen
Westdeutscher Rundfunk Köln
IT- und Netz-Services / Netze und Telekommunikation
Appellhofplatz 1
50667 Köln
Germany
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
