[c-nsp] ASR 901 EoMPLS

[sthaug at nethelp.no]

> Do you still need to do that when it's a port-based pw?

If you do, I'd say this is a bug. A port-based pseudowire shouldn't
care about L2 protocols or similar. It should just forward anything
it receives on the port into the pseudowire, and vice versa. With a
possible exception for Ethernet flow-control frames.

Steinar Haug, Nethelp consulting, sthaug at nethelp.no
> 
> Sent from my iPhone
> 
> > On Nov 18, 2013, at 8:19 AM, Dimitris Befas <dimitris.befas at gmail.com> wrote:
> > 
> > Hi Fredrik,
> > 
> > Please check the command "l2protocol ?" under interface config.
> > 
> > 
> > 2013/11/18 Fredrik Vöcks <fredrik.vocks at bredband2.se>
> > 
> >> 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  cisco-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/cisco-nsp
> >> archive at http://puck.nether.net/pipermail/cisco-nsp/
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/