Dear Extreme people who know better:
We are attempting to use SNMP to determine the MAC address, port number, and port
status of the connected devices to a network switch. Since we are "newbies" to this
area we have attempted to research the best way to do this.
The approach we have taken is to attempt to use the definitions in RFC 1493 to query
the attached devices to network switches. We want to obtain the MAC address, switch
port, and port status for each attached device on a network switch via SNMP.
According to our (imperfect) understanding of RFC 1493, there should be a
dot1dTpFdbTable (OID = 1.3.6.1.2.1.17.4.3) that contains a list of attached devices.
There are three properties for each attached device: dot1dTpFdbAddress
(OID-1.3.6.1.2.1.17.4.3.1.1) which has the MAC address, dot1DTpBdbPort
(OID=1.3.6.1.2.1.17.4.3.1.2) which has the port number, and dot1DTpFdbStatus
(OID=1.3.6.1.2.1.17.4.3.1.3) which has the port status (typically "learned" or "3").
It is our understanding that if we want to query the attached devices for a switch
and extract their MAC address, port number, and port status, in accordance with RFC 1493
we should use these properties that are under OID=1.3.6.1.2.1.17.4.3.1.1
In the ExtremeWare v7.6 documentation, it states that it supports the RFC 1493 Bridge MIB.
However, when we view the MIB, we see that table of attached devices and the three properties
that we are interested (MAC address, port number, and port status) have very different
OIDs than specific in RFC 1493. In particular, the corresponding extremeFdbMacFdbTable
(OID=1.3.6.1.4.1.1916.1.16.1) contains three properties, extremeFdbMacFdbMacAddress
(OID=1.3.6.1.4.1.1916.1.16.1.1.3), extremeFdbMacFdbPortIfIndex (OID=1.3.6.1.4.1.1916.1.16.1.1.4),
and extremeFdbMacFdbStatus (OID=1.3.6.1.4.1.1916.1.16.1.1.5).
We were wondering why ExtremeWare v7.6 , which supports RFC 1493, has OIDs for these
properties that are different from RFC 1493. Are we misunderstanding RFC 1493? Are we using the
wrong OIDs from the Summit MIB and should we be looking somewhere else besides 1.3.6.1.4.1.1916.1.16.1?
Does Extreme place the table of attached devices at a variety of OIDs?
We would appreciate any help or insight you might be able to give us on this.
Thank you very much!
We are attempting to use SNMP to determine the MAC address, port number, and port
status of the connected devices to a network switch. Since we are "newbies" to this
area we have attempted to research the best way to do this.
The approach we have taken is to attempt to use the definitions in RFC 1493 to query
the attached devices to network switches. We want to obtain the MAC address, switch
port, and port status for each attached device on a network switch via SNMP.
According to our (imperfect) understanding of RFC 1493, there should be a
dot1dTpFdbTable (OID = 1.3.6.1.2.1.17.4.3) that contains a list of attached devices.
There are three properties for each attached device: dot1dTpFdbAddress
(OID-1.3.6.1.2.1.17.4.3.1.1) which has the MAC address, dot1DTpBdbPort
(OID=1.3.6.1.2.1.17.4.3.1.2) which has the port number, and dot1DTpFdbStatus
(OID=1.3.6.1.2.1.17.4.3.1.3) which has the port status (typically "learned" or "3").
It is our understanding that if we want to query the attached devices for a switch
and extract their MAC address, port number, and port status, in accordance with RFC 1493
we should use these properties that are under OID=1.3.6.1.2.1.17.4.3.1.1
In the ExtremeWare v7.6 documentation, it states that it supports the RFC 1493 Bridge MIB.
However, when we view the MIB, we see that table of attached devices and the three properties
that we are interested (MAC address, port number, and port status) have very different
OIDs than specific in RFC 1493. In particular, the corresponding extremeFdbMacFdbTable
(OID=1.3.6.1.4.1.1916.1.16.1) contains three properties, extremeFdbMacFdbMacAddress
(OID=1.3.6.1.4.1.1916.1.16.1.1.3), extremeFdbMacFdbPortIfIndex (OID=1.3.6.1.4.1.1916.1.16.1.1.4),
and extremeFdbMacFdbStatus (OID=1.3.6.1.4.1.1916.1.16.1.1.5).
We were wondering why ExtremeWare v7.6 , which supports RFC 1493, has OIDs for these
properties that are different from RFC 1493. Are we misunderstanding RFC 1493? Are we using the
wrong OIDs from the Summit MIB and should we be looking somewhere else besides 1.3.6.1.4.1.1916.1.16.1?
Does Extreme place the table of attached devices at a variety of OIDs?
We would appreciate any help or insight you might be able to give us on this.
Thank you very much!