https://community.extremenetworks.com/t5/faqs/translating-matrix-n-series-trap-vs-cli-port-numbering/m-p/42363#M106 Article ID: 5567 <BR /> <BR /> <B>Products</B><BR /> DFE <BR /> <BR /> <B>Protocols/Features</B><BR /> SNMP<BR /> Traps<BR /> Mibs<BR /> Netflow <BR /> <BR /> <B>Goals</B><BR /> Translate trap vs cli port numbering <BR /> <BR /> <B>Cause</B><BR /> 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'. <BR /> <BR /> <B>Solution</B><BR /> To translate between the two numbering methods, query mib 'dot1dBasePortIfIndex=1.3.6.1.2.1.17.1.4.1.2'. <BR /> <BR /> 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 <A href="http://bit.ly/1cyABR3" target="_blank" rel="nofollow noreferrer noopener">5456</A>: <BR /> <BR /> Object Instance Type Value<BR /> <BR /> dot1dBasePortIfIndex 1 INTEGER 1<BR /> dot1dBasePortIfIndex 34 INTEGER 15501<BR /> dot1dBasePortIfIndex 64 INTEGER 11001<BR /> dot1dBasePortIfIndex 65 INTEGER 11002<BR /> dot1dBasePortIfIndex 66 INTEGER 11003<BR /> . . .<BR /> dot1dBasePortIfIndex 111 INTEGER 11048<BR /> dot1dBasePortIfIndex 112 INTEGER 12001<BR /> . . .<BR /> dot1dBasePortIfIndex 117 INTEGER 12006<BR /> dot1dBasePortIfIndex 194 INTEGER 25501<BR /> dot1dBasePortIfIndex 320 INTEGER 22001<BR /> dot1dBasePortIfIndex 321 INTEGER 22002<BR /> dot1dBasePortIfIndex 322 INTEGER 22003<BR /> . . .<BR /> dot1dBasePortIfIndex 331 INTEGER 22012<BR /> dot1dBasePortIfIndex 1792 INTEGER 1005001<BR /> dot1dBasePortIfIndex 1793 INTEGER 1005002<BR /> dot1dBasePortIfIndex 1794 INTEGER 1005003<BR /> . . .<BR /> dot1dBasePortIfIndex 1839 INTEGER 1005048 Tue, 17 Dec 2013 21:12:00 GMT FAQ_User 2013-12-17T21:12:00Z https://community.extremenetworks.com/t5/faqs/translating-matrix-n-series-trap-vs-cli-port-numbering/m-p/42363#M106 Article ID: 5567 <BR /> <BR /> <B>Products</B><BR /> DFE <BR /> <BR /> <B>Protocols/Features</B><BR /> SNMP<BR /> Traps<BR /> Mibs<BR /> Netflow <BR /> <BR /> <B>Goals</B><BR /> Translate trap vs cli port numbering <BR /> <BR /> <B>Cause</B><BR /> 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'. <BR /> <BR /> <B>Solution</B><BR /> To translate between the two numbering methods, query mib 'dot1dBasePortIfIndex=1.3.6.1.2.1.17.1.4.1.2'. <BR /> <BR /> 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 <A href="http://bit.ly/1cyABR3" target="_blank" rel="nofollow noreferrer noopener">5456</A>: <BR /> <BR /> Object Instance Type Value<BR /> <BR /> dot1dBasePortIfIndex 1 INTEGER 1<BR /> dot1dBasePortIfIndex 34 INTEGER 15501<BR /> dot1dBasePortIfIndex 64 INTEGER 11001<BR /> dot1dBasePortIfIndex 65 INTEGER 11002<BR /> dot1dBasePortIfIndex 66 INTEGER 11003<BR /> . . .<BR /> dot1dBasePortIfIndex 111 INTEGER 11048<BR /> dot1dBasePortIfIndex 112 INTEGER 12001<BR /> . . .<BR /> dot1dBasePortIfIndex 117 INTEGER 12006<BR /> dot1dBasePortIfIndex 194 INTEGER 25501<BR /> dot1dBasePortIfIndex 320 INTEGER 22001<BR /> dot1dBasePortIfIndex 321 INTEGER 22002<BR /> dot1dBasePortIfIndex 322 INTEGER 22003<BR /> . . .<BR /> dot1dBasePortIfIndex 331 INTEGER 22012<BR /> dot1dBasePortIfIndex 1792 INTEGER 1005001<BR /> dot1dBasePortIfIndex 1793 INTEGER 1005002<BR /> dot1dBasePortIfIndex 1794 INTEGER 1005003<BR /> . . .<BR /> dot1dBasePortIfIndex 1839 INTEGER 1005048 Tue, 17 Dec 2013 21:12:00 GMT https://community.extremenetworks.com/t5/faqs/translating-matrix-n-series-trap-vs-cli-port-numbering/m-p/42363#M106 FAQ_User 2013-12-17T21:12:00Z