Before XE 3.11 (15.3.4S) the behavior is: 1) On EVC-BD, if no L2CP configuration is done, then tagged BPDUs are dropped and untagged BPDUs are peered
2) On EVC-Xconnect, by default, the tagged BPDUs are dropped and untagged BPDUs are forwarded 3) On Port-Xconnect, the tagged BPDUs are dropped and untagged BPDUs are forwarded This is not documented clearly and I'll work to get the external documentation updated to reflect this and create a longer term goal to more clearly state the behavior of control traffic on xconnect ports in different configurations on different platforms. On Mon, Nov 18, 2013 at 8:11 AM, Fredrik Vöcks <[email protected]>wrote: > Hi all, > > We are having a customer who says he can't forward BPDU packets over an > portbased EoMPLS using an ASR 901. > > Is this something known or am I missing something? Relevant configuration; > > interface TenGigabitEthernet0/1 > description c_customer433231 > no keepalive > xconnect x.x.x.x 1730 encapsulation mpls > > /F > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
