That looks like it would work! I'm going to give it a spin and will let you know the outcome.
Original Message:
Sent: May 01, 2024 11:24 AM
From: Mflowers@beta.team
Subject: E911 SNMP Walk for 6300M
I think this is what you are asking for:
MIB = BRIDGE-MIB
.1.3.6.1.2.1.17.4.3.1.1 - MAC - dot1dTpFdbAddress
.1.3.6.1.2.1.17.4.3.1.2 - PORT - dot1dTpFdbPort
If you walk 1.3.6.1.2.1.17.4.3.1.1 it will give you the mac address table. If you walk .1.3.6.1.2.1.17.4.3.1.2 it will give you the port ID. This will allow you to match port to mac address.
Example:
.1.3.6.1.2.1.17.4.3.1.1.40.41.134.122.63.197 = XX-XX-XX-7A-3F-C5
.1.3.6.1.2.1.17.4.3.1.2.40.41.134.122.63.197 = 24
Original Message:
Sent: Apr 30, 2024 12:24 PM
From: alight4
Subject: E911 SNMP Walk for 6300M
Hello,
We are rolling out an E911 Manager within our environment and have run into a snag. The vendor helping with the roll-out process is unable to gather the information they need via SNMP walk on our 6300M (JL659A) switches.
Our current firmware version our switches are on is 10.10.1040.
They specifically stated the RFC(s) normally used for this process are 1493 and 4188. However those RFC(s) are no longer supported at the current firmware version our switches are on.
V. 10.04 did support RFC 1493 and 4188 and provided this information in the release notes:
SNMP Added support for BRIDGE-MIB. The Bridge MIB consists of L2 forwarding information organized into a set of tables representing base bridge information,dynamicandstaticMACforwardingentries,STPconfiguration information,andstatistics.TheBridgeMIBisdescribedinRFC1493and RFC4188.Thefollowingtablesareincluded:dot1dBase,dot1dStatic,dot1dTp, dot1dStp.MIBdataelementsareaccessedusingSNMP.
As per the vendor, in a nut shell, this is what we are looking to do,
"E911 manager manager will walk the switches when a phone registers and look for that devices mac address, here are OIDs for Aruba Switches:
Aruba:
------------
1.3.6.1.2.1.3.1.1.2
1.3.6.1.4.1.9.9.46.1.3.1.1.2.1
1.3.6.1.2.1.17.1.4.1.1 - specify vlan for snmp v3 - used during switch initialization
1.3.6.1.2.1.17.1.4.1.2 - specify vlan for snmp v3 - used during switch initialization
1.3.6.1.2.1.2.2.1.1 - used during switch initialization
1.3.6.1.2.1.2.2.1.2 - used during switch initialization
1.3.6.1.2.1.2.2.1.3 - used during switch initialization
1.3.6.1.2.1.17.4.3.1.1 - specify vlan for snmp v3
1.3.6.1.2.1.17.4.3.1.2 - specify vlan for snmp v3
1.3.6.1.2.1.17.4.3.1.3 - specify vlan for snmp v3"
I'm not overly well versed in the area of MIBs and OIDs so I apologize for any information I failed to provide.
Does anyone have a solution to this issue?
Thank you.
Alex