Interesting. Will try that out. On Sat, 14 Mar 2020 at 06:07, Erik Sundberg <[email protected]> wrote:
> Hope this helps > > I opened bug with Cisco where I had to shut and no shut the bridge domain, > this is on a ASR920. ASR1000's are also noted on the bug list. > > Bug: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvj18480/?rfs=iqvred > > Here is what I submitted. > > When creating a new VPLS Network on a ASR920. I need to shut and no shut > the bridge-domain. The VFI's to the remote 3 device remain in down state. > > See the below config > Router#conf t > Router(config)#bridge-domain 650 > Router(config-bdomain)# > Router(config-bdomain)#l2 vfi 11111 manual > Router(config-vfi)# vpn id 11111 > Router(config-vfi)# bridge-domain 650 > Router(config-vfi)# mtu 9180 > Router(config-vfi)# neighbor 192.168.0.96 pw-class VPLS > Router(config-vfi-neighbor)# neighbor 192.168.0.82 pw-class VPLS > Router(config-vfi-neighbor)# neighbor 192.168.0.92 pw-class VPLS > Router(config-vfi-neighbor)# > Router(config-vfi-neighbor)#int Gi0/0/1 > Router(config-if)# service instance 1 ethernet > Router(config-if-srv)# encapsulation default > Router(config-if-srv)# bridge-domain 650 > Router(config-if-srv)# > Router(config-if-srv)#exit > Router(config-if)#exit > Router(config)#exit > Router#sh mpls l2transport vc vcid 11111 > > Local intf Local circuit Dest address VC ID Status > ------------- -------------------------- --------------- ---------- > ---------- > VFI 11111 vfi 192.168.0.82 11111 DOWN > > VFI 11111 vfi 192.168.0.92 11111 DOWN > > VFI 11111 vfi 192.168.0.96 11111 DOWN > > > Router#conf t > Enter configuration commands, one per line. End with CNTL/Z. > Router(config)#bridge-domain 650 > Router(config-bdomain)#shut > Router(config-bdomain)#no shut > Router(config-bdomain)#end > Router#sh mpls l2transport vc vcid 11111 > > Local intf Local circuit Dest address VC ID Status > ------------- -------------------------- --------------- ---------- > ---------- > VFI 11111 vfi 192.168.0.82 11111 UP > > VFI 11111 vfi 192.168.0.92 11111 UP > > VFI 11111 vfi 192.168.0.96 11111 UP > > > Router# > > ------------------------------ > *From:* cisco-nsp <[email protected]> on behalf of Mark > Tees <[email protected]> > *Sent:* Thursday, March 12, 2020 11:45 PM > *To:* Cisco-nsp List <[email protected]> > *Subject:* [c-nsp] ASR1000 local L2 bridge or local PW > > Hey guys, > > Has anyone got any form of local L2 working on ASR1000? > > Still seems broken in latest code I have and needed it for a customer. > By broken I mean MAC's are learnt inside bridge domain but on either > ingress or egress tagging is something unexpected. I still need to > confirm PCAP. > > I was using service instance on physical interface with a > bridge-domain to tie two ports together and some tag mangling/rewrite. > I have the same config working on ASR920 but one is ASIC and other > ASR1000 ESP so I expect some differences there. > > Tried the local xconnect variants also. > > Was planning on lodging TAC case soon. > > Cheers, > > Mark > > > > interface GigabitEthernet0/0/0 > service instance 666 ethernet > encapsulation dot1q 666 > rewrite ingress tag pop 1 symmetric > bridge-domain 667 > ! > interface GigabitEthernet0/0/1 > service instance 667 ethernet > encapsulation dot1q 667 > rewrite ingress tag pop 1 symmetric > bridge-domain 667 > ! > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > ------------------------------ > > CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files > or previous e-mail messages attached to it may contain confidential > information that is legally privileged. If you are not the intended > recipient, or a person responsible for delivering it to the intended > recipient, you are hereby notified that any disclosure, copying, > distribution or use of any of the information contained in or attached to > this transmission is STRICTLY PROHIBITED. If you have received this > transmission in error please notify the sender immediately by replying to > this e-mail. You must destroy the original transmission and its attachments > without reading or saving in any manner. Thank you. > -- Regards, Mark Tees _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
