Hi Ivan, You can use the following EVPL configuration which would allow you to see the mac addresses e.g. in the following example you can see the mac addresses under bridge-domain 10.
interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 100 rewrite ingress tag pop 1 symmetric bridge-domain 10 interface Vlan10 no ip address xconnect 2.2.2.2 10 encapsulation mpls Regards, Waris -----Original Message----- From: Ivan [mailto:[email protected]] Sent: Sunday, August 12, 2012 7:17 PM To: Pshem Kowalczyk Cc: Ivan; Waris Sagheer (waris); [email protected] Subject: Re: [c-nsp] ME3600X Embedded Packet Capture Hi, Yes, as far as I understand there is no mac learning which is great for resource utilisation and scalability. No requirement other than "it is helpful for troubleshooting" to see any macs. Cheers Ivan > Hi, > > > On 11 August 2012 10:32, Ivan <[email protected]> wrote: > > {cut} > >> xconnect 1.2.3.4 666 encapsulation mpls > > Speaking from general experience - this is the culprit. In > point-to-point L2VPNs there is (usually, I admit I'm not sure if > that's the case on 3600x) no MAC address learning (which nicely > conserves the resources on the switch). If you really need to see that > address - you should turn that into a point-to-point VPLS. > > kind regards > Pshem > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
