Hi, I just realised that this feature is not in the official software. We're running a pre-release 15.3.4 here (3.11 in XE speak), for our metroE deployment.
kind regards Pshem On 19 November 2013 09:04, Fredrik Vöcks <[email protected]> wrote: > Hi, > > Im trying to do this on Version 15.3(3)S but the xconnect is rejected if I > enable l2protocol forward. > > Which version are you succesfully doing this on? > > > (config-if-srv)# l2protocol forward > (config-if-srv)#xconnect x.x.x.x 1730 encapsulation mpls > Layer2 protocol tunnel/forward/peer configured. Command rejected > > /F > > > > > On 18 November 2013 19:43, Pshem Kowalczyk <[email protected]> wrote: >> >> Hi, >> >> The only way we could get the L2 forwarding going on ASR901 was using >> a single service instance with encapsulation default (this only works >> in newest software): >> >> interface GigabitEthernet0/8 >> no ip address >> negotiation auto >> no keepalive >> service instance 1 ethernet >> encapsulation default >> l2protocol forward >> xconnect 10.123.129.3 34322 encapsulation mpls >> mtu 9000 >> >> >> kind regards >> Pshem >> >> >> On 19 November 2013 02:11, 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/
