Hello all,
I did see the dynamic mac-address via "show system internal l2fwder mac".
I need to link a MAC address to the port on which the address was learned using SNMP query.
For instance,
From Step 1, the MAC address is:
1.3.6.1.2.1.17.4.3.1.1.0.0.12.7.172.8 = Hex: 00 00 0C 07 AC 08
From Step 2, the bridge port tells that the MAC address belongs to bridge port number 13:
1.3.6.1.2.1.17.4.3.1.2.0.0.12.7.172.8 = 13
From Step 3, the bridge port number 13 has ifIndex number 2:
1.3.6.1.2.1.17.1.4.1.2.13 = 2
From Step 4, the ifIndex 2 corresponds to port Fast Ethernet 0/1:
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifName.2 = Fa0/1
Conclusion: The MAC address 00 00 0C 07 AC 08 is learned on port Fa0/1
My current issue is that, even if I see the dynamic mac-address via CLI cmd, I do not see it via SNMP 1.3.6.1.2.1.17.4.3.1.1. The snmp to Dot1dTpFdbEntry only show the static mac-addresses.
snmpwalk -v 2c -c public@401 192.168.168.141 1.3.6.1.2.1.17.4.3.1.1
iso.3.6.1.2.1.17.4.3.1.1.0.0.12.159.241.145 = Hex-STRING: 00 00 0C 9F F1 91
iso.3.6.1.2.1.17.4.3.1.1.82.84.0.14.81.241 = Hex-STRING: 52 54 00 0E 51 F1
switch# show system internal l2fwder mac
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False, C - ControlPlane MAC
VLAN MAC Address Type age Secure NTFY Ports
---------+-----------------+--------+---------+------+----+------------------
* 400 5254.001e.3740 dynamic 2d16h F F Eth1/13
* 401 5254.0016.8312 dynamic 00:04:29 F F Eth1/7
G 402 0000.0c9f.f192 static - F F sup-eth1(R)
G 401 0000.0c9f.f191 static - F F sup-eth1(R)
G 402 5254.000e.51f1 static - F F sup-eth1(R)
G 401 5254.000e.51f1 static - F F sup-eth1(R)
G 400 5254.000e.51f1 static - F F sup-eth1(R)
* 402 5254.0015.d4a7 dynamic 00:00:23 F F Eth1/6
G 400 0000.0c9f.f1f3 static - F F sup-eth1(R)
* 400 5254.0002.30dc dynamic 2d15h F F Eth1/9
* 401 5254.0017.3662 dynamic 00:00:24 F F Eth1/3
* 400 5254.0013.2091 dynamic 2d15h F F Eth1/11
Do anyone know if this is a known issue in Nexus 9000v? Does it happen in Nexus 9000 physical hardware?
Thanks and regards,
