Header Only - DO NOT REMOVE - Extreme Networks

Translating Matrix N-series Trap vs CLI Port Numbering


Userlevel 3
Article ID: 5567

Products
DFE

Protocols/Features
SNMP
Traps
Mibs
Netflow

Goals
Translate trap vs cli port numbering

Cause
When an SNMP trap is received from a N-Series DFE system, port references do not directly reconcile to the ifIndex numbering scheme as seen in the cli or in Interface Description mib 'ifDescr=1.3.6.1.2.1.2.2.1.2'.

Solution
To translate between the two numbering methods, query mib 'dot1dBasePortIfIndex=1.3.6.1.2.1.17.1.4.1.2'.

In the sample result shown below, the 'Instance' column contains the 'dot1dBasePort=1.3.6.1.2.1.17.1.4.1.1' (trap) numbering, while the 'Value' column contains the corresponding 'ifIndex=1.3.6.1.2.1.2.2.1.1' numbering which may be further translated to logical port instances as explained in 5456:

Object Instance Type Value

dot1dBasePortIfIndex 1 INTEGER 1
dot1dBasePortIfIndex 34 INTEGER 15501
dot1dBasePortIfIndex 64 INTEGER 11001
dot1dBasePortIfIndex 65 INTEGER 11002
dot1dBasePortIfIndex 66 INTEGER 11003
. . .
dot1dBasePortIfIndex 111 INTEGER 11048
dot1dBasePortIfIndex 112 INTEGER 12001
. . .
dot1dBasePortIfIndex 117 INTEGER 12006
dot1dBasePortIfIndex 194 INTEGER 25501
dot1dBasePortIfIndex 320 INTEGER 22001
dot1dBasePortIfIndex 321 INTEGER 22002
dot1dBasePortIfIndex 322 INTEGER 22003
. . .
dot1dBasePortIfIndex 331 INTEGER 22012
dot1dBasePortIfIndex 1792 INTEGER 1005001
dot1dBasePortIfIndex 1793 INTEGER 1005002
dot1dBasePortIfIndex 1794 INTEGER 1005003
. . .
dot1dBasePortIfIndex 1839 INTEGER 1005048[/code]

0 replies

Be the first to reply!

Reply