[c-nsp] ASR903 AToM

[Mohammad Khalil]

Hi
You mean VFI without BGP peering?

From: ggiannou at gmail.com
Date: Sun, 19 Apr 2015 19:11:12 +0300
Subject: Re: [c-nsp] ASR903 AToM
To: eng_mssk at hotmail.com
CC: adam.vitkovsky at gamma.co.uk; cisco-nsp at puck.nether.net

oops.. my mistake..
You need to configure l2vpn vfi instead of l2vpn xconnectTake a look at http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l2_vpns/configuration/xe-3s/asr903/mp-l2-vpns-xe-3s-asr903-book/mp-vpls.html
On Sun, Apr 19, 2015 at 6:41 PM, Mohammad Khalil <eng_mssk at hotmail.com> wrote:



Hi when i configure the l2vpn xconnect context i cannot bind the service instance 1 

From: ggiannou at gmail.com
Date: Sun, 19 Apr 2015 18:04:09 +0300
Subject: Re: [c-nsp] ASR903 AToM
To: eng_mssk at hotmail.com
CC: adam.vitkovsky at gamma.co.uk; cisco-nsp at puck.nether.net

Hi,
I'd use the following config for the service instances and the L2VPNI guess you can't use the service instance in the L2VPN, because of the bridge-domain command inside the service instance.
service instance 1 ethernet  encapsulation dot1q 100,200,300  rewrite ingress tag pop 1 symmetric
l2vpn xconnect context L2VPNmember GigabitEthernet0/0/0 service instance 1member GigabitEthernet0/1/0 service instance 1member pseudowire 20
Maybe the trunk keyword in the service instance plays some role..

--George

On Sun, Apr 19, 2015 at 3:34 PM, Mohammad Khalil <eng_mssk at hotmail.com> wrote:
I have applied the configuration and The same

The circuit is up but no ping between the CEs

I issued the command show monitor event-trace atom and mismatched c-bit message appeared



From: Adam.Vitkovsky at gamma.co.uk

To: eng_mssk at hotmail.com; cisco-nsp at puck.nether.net

Subject: RE: [c-nsp] ASR903 AToM

Date: Sun, 19 Apr 2015 09:10:40 +0000



Hi Mohamad,







I'm not sure if this "new-style" config works yet.







This is how it would look like using the "old-style"







ASR903



interface GigabitEthernet0/0/0



  service instance trunk 1 ethernet



    encapsulation dot1q 100,200,300



    rewrite ingress tag pop 1 symmetric



    xconnect 2.2.2.2 20 encapsulation mpls







! interface GigabitEthernet0/1/0



!  service instance trunk 1 ethernet



!    encapsulation dot1q 100,200,300



!    rewrite ingress tag pop 1 symmetric



!    xconnect 2.2.2.2 40 encapsulation mpls



! -- config related to backup PW--







Also on ME I'd recommend using xconnect under the service instance rather than attaching the service instance to a BD and configuring xconnect under the VLAN interface. Because if you attach a service instance to a BD by default MAC learning is in place and you don't want that for a simple p2p PW (MAC learning can be disabled using cmd: " no mac learning" under the BD config).







ME3600



interface GigabitEthernet0/x



  service instance trunk 1 ethernet



    encapsulation dot1q 100,200,300



    rewrite ingress tag pop 1 symmetric



    xconnect 1.1.1.1 20 encapsulation mpls



!     backup peer 1.1.1.1 40 encapsulation mpls



! -- config related to backup PW--







adam



> -----Original Message-----



> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of



> Mohammad Khalil



> Sent: 18 April 2015 01:08



> To: cisco-nsp at puck.nether.net



> Subject: [c-nsp] ASR903 AToM



>



> Hi all



> I have the below setup



> I have ASR903 connected to ME3600 (both are acting as PEs)



> The ASR903 is part of REP ring consisting of other 3400 switches with ASR903



> being the primary



> I have two CEs , one is directly connected to the ME3600 box , and the other



> CE is connected to one of the 3400 switches which are part of the REP ring



> What am trying to do is to establish AToM (Xconnect) between the two CEs



> The Vlan used for testing is 100 (there are other Vlans passing through the



> trunks that are not for MPLS service)



>



> ASR903



> interface GigabitEthernet0/0/0



>  description Connected-To-AS1-G0/2



>  no ip address



>  negotiation auto



>  rep segment 20 edge primary



>  rep preempt delay 30



>  rep block port 3 vlan 1-4094



>  service instance trunk 1 ethernet



>   encapsulation dot1q 100,200,300



>   rewrite ingress tag pop 1 symmetric



>   bridge-domain from-encapsulation



>



>



> interface GigabitEthernet0/1/0



>  description Connected-To-AS2-G0/2



>  no ip address



>  negotiation auto



>  rep segment 20 edge preferred



>  rep preempt delay 30



>  service instance trunk 1 ethernet



>   encapsulation dot1q 100,200,300



>   rewrite ingress tag pop 1 symmetric



>   bridge-domain from-encapsulation



>



> interface pseudowire 20



> encapsulation mpls



> neighbor 2.2.2.2 20



>



> l2vpn xconnect context L2VPN



> member GigabitEthernet0/0/0 --> When I tried to put service-instance , it did



> not accept the command



> member pseudowire 20



>



> ME3600



> interface vlan 100



> no ip address



> xconnect 1.1.1.1 20 encapsulation mpls



>



> Now , the xconnect came up as shown in the output below



>



> ME3600X#show mpls l2transport vc 20



>



> Local intf     Local circuit              Dest address    VC ID      Status



> -------------  -------------------------- --------------- ---------- ----------



> Vl100          Eth VLAN 100               1.1.1.1         20         UP



>



> ASR903#sh xconnect all



> Legend:    XC ST=Xconnect State  S1=Segment1 State  S2=Segment2 State



>   UP=Up       DN=Down            AD=Admin Down      IA=Inactive



>   SB=Standby  HS=Hot Standby     RV=Recovering      NH=No Hardware



>



> XC ST  Segment 1                         S1 Segment 2                         S2



> ------+---------------------------------+--+---------------------------------+--



> UP pri mpls 2.2.2.2:20                   UP   ac Gi0/0/0:6(Ethernet)          UP



>



> No ping between the two sites , I tried to modify the MTU vlaue on the



> interfaces going to the CE side , and the xconnect is down directly



> I have tested L3VPN using the exact same setup (without modifying the MTU



> values on any interface) and it worked fine



>



> Any ideas?



>



> Thanks in advance



>



> BR,



> Mohammad



>



> _______________________________________________



> 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/







  This email has been scanned for email related threats and delivered safely by Mimecast.

 For more information please visit http://www.mimecast.com



_______________________________________________

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/