Ethernet Switching
Highlighted
Ethernet Switching

MAC address associates with ae0.0 instead of physical interface

[ Edited ]
‎11-06-2017 11:46 AM

I have multiple MC-LAG deployments at an extreamly large site. Occasionally I need to track a MAC address to an access port, so I get the MAC assosicated with the devices IP address off of my firewall then login to the access switch and do show ethernet-switching table | match <MAC>. The problem is some MAC addresses associate with the aggergation interface (ae0.0) instead of the physical interface then I have no idea what acesse port I need to look at.

 

So my question is why do some MACs in the ARP table associate with the logical interface while others associate with the physical interface? WIll MAC address associating with ae0.0 cause problems? And is there another way to see which MAC addresses are connected to what interface?

 

(Example)

pack-plc 00:07:af:e6:be:a0 D - ge-0/0/7.0
pack-plc 00:07:af:e6:c7:b0 D - ge-0/0/18.0
pack-plc 00:07:af:e7:49:00 D - ge-0/0/10.0
pack-plc 00:0c:29:0f:0b:b9 D - ae0.0
pack-plc 00:0c:29:1c:86:a0 D - ae0.0
pack-plc 00:0c:29:52:25:66 D - ae0.0

 

 

2 REPLIES 2
Highlighted
Ethernet Switching
Solution
Accepted by topic author wbcrisman
‎11-06-2017 05:20 PM

Re: MAC address associates with ae0.0 instead of physical interface

‎11-06-2017 12:38 PM
Because they are on a different access switch and are being learned from your core.
Highlighted
Ethernet Switching

Re: MAC address associates with ae0.0 instead of physical interface

‎11-06-2017 07:15 PM
I just saw your username lol.

If you look up the MAC on core1/mdf1a first it will show you the ae interface of the correct access switch. If it shows up on ae0.0 there it means it’s being learned from core2/mdf1b–so check there next.
Feedback