cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
169
Views
5
Helpful
3
Replies
Highlighted
Beginner

EVPN VPWS port-active

I am trying to built an EVPN VPWS service with port-active load-balancing. One end of the VPWS is with two PE's (NCS55A2, PE-1 and PE-2) connected to a customer LAN the other end is a single PE (ASR9K - PE-3) connected to another customer LAN. in between the PE's SRP is running. All routers are running 6.6.3. I can get the VPWS up and running and both ends say that the remote end is "unknown":

 

sh l2vpn xconnect group EVPN-PA-01 detail 
Group EVPN-PA-01, XC EVPN-PA-01, state is down; Interworking none
  AC: Bundle-Ether870.870, state is up
    Type VLAN; Num Ranges: 1
    Rewrite Tags: []
    VLAN ranges: [870, 870]
    MTU 1500; XC ID 0xa0000010; interworking none
    Statistics:
      packets: received 0, sent 0
      bytes: received 0, sent 0
      drops: illegal VLAN 0, illegal length 0
  EVPN: neighbor 0.0.0.0, PW ID: evi 870, ac-id 870, state is down ( local ready )
    XC ID 0xc000000d
    Encapsulation MPLS
    Source address 5.186.161.101
    Encap type Ethernet, control word disabled
    Sequencing not set
    LSP : Up

      EVPN         Local                          Remote                        
      ------------ ------------------------------ -----------------------------
      Label        25311                          unknown                       
      MTU          1500                           unknown                       
      Control word disabled                       unknown                       
      AC ID        1870                           870                           
      EVPN type    Ethernet                       unknown                       

      ------------ ------------------------------ -----------------------------
    Create time: 21/01/2021 09:21:20 (00:00:19 ago)
    Last time status changed: 21/01/2021 09:21:20 (00:00:19 ago)
    Statistics:
      packets: received 0, sent 0
      bytes: received 0, sent 0

 

If I change the load-balancing to "single-active" the VPWS comes up. As far as I can see in the configuration guide port-active should be supported in EVPN VPWS. But what is missing? Anyone seems this before?

 

On the PE-1 and PE-2 the configuration looks like this:

 

 

interface Bundle-Ether870
 lacp system mac 1212.1212.1212
!
interface Bundle-Ether870.870 l2transport
 encapsulation dot1q 870
 rewrite ingress tag pop 1 symmetric
!
evpn
 evi 870
  control-word-disable
!
 interface Bundle-Ether870
  ethernet-segment
   identifier type 0 05.ba.a1.64.05.ba.a1.64.01
   load-balancing-mode port-active
!
!
!
l2vpn
 pw-class PW-MPLS
  encapsulation mpls
  !
 !
 xconnect group EVPN-PA-01
  p2p EVPN-PA-01
   interface Bundle-Ether870.870
   neighbor evpn evi 870 target 870 source 1870
    pw-class PW-MPLS
!
!
!

 

On PE-3 the configurations looks like this:

 

 

interface Bundle-Ether870
!
interface Bundle-Ether870.870 l2transport
 encapsulation dot1q 870
 rewrite ingress tag pop 1 symmetric
!
!
!
evpn
 evi 870
  control-word-disable
!
 interface Bundle-Ether870
  ethernet-segment
   identifier type 0 b9.a9.0c.18.00.00.00.00.00
   load-balancing-mode port-active
!
!
!
l2vpn
 pw-class PW-MPLS
  encapsulation mpls
  !
 !
 xconnect group EVPN-PA-01
  p2p EVPN-PA-01
   interface Bundle-Ether870.870
   neighbor evpn evi 870 target 1870 source 870
   pw-class PW-MPLS
!
!
!

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

IT look like that even though that port-active mode is configurable in 6.6.3, it is not supported before 7.1.2. I upgraded the routers to 7.2.2 and then the EVPN come up.

View solution in original post

3 REPLIES 3
Highlighted
Enthusiast

Hi, 

 

refer to this document. Maybe it will help you out. You could also provide some debugs. I haven't tried this scenario yet, so this is the only help I can provide.

https://xrdocs.io/ncs5500/tutorials/bgp-evpn-based-port-active-multihoming/

 

Highlighted

Hi

 

I have been following that tutorial without luck. It is also for a E-LAN and not E-LINE however it should work. 

 

Debug did not show much but here are what I see when debugging:

 

debug l2vpn errors 
RP/0/RSP1/CPU0:bord02.arc01#RP/0/RSP1/CPU0:Jan 20 13:19:54.817 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - del:0
RP/0/RSP1/CPU0:Jan 20 13:19:54.817 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:19:54.817 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:870, ACID:1870
RP/0/RSP1/CPU0:Jan 20 13:19:54.817 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - del:0
RP/0/RSP1/CPU0:Jan 20 13:19:54.817 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:19:54.817 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:871, ACID:871
RP/0/RSP1/CPU0:Jan 20 13:19:54.846 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - del:1
RP/0/RSP1/CPU0:Jan 20 13:19:54.846 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:870, ACID:1870
RP/0/RSP1/CPU0:Jan 20 13:19:54.846 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_free:124, Deleting EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870)
RP/0/RSP1/CPU0:Jan 20 13:19:54.846 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - del:1
RP/0/RSP1/CPU0:Jan 20 13:19:54.846 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:871, ACID:871
RP/0/RSP1/CPU0:Jan 20 13:19:54.846 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_free:124, Deleting EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871)
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 2048
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 1656
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 1656
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 1264
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 1264
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 1024
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 1024
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 784
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - del:0
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_create:725, Creating EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870)
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:870, ACID:1870
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - del:0
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_create:725, Creating EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871)
RP/0/RSP1/CPU0:Jan 20 13:19:55.019 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:871, ACID:871
RP/0/RSP1/CPU0:Jan 20 13:19:55.221 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 784
RP/0/RSP1/CPU0:Jan 20 13:19:55.221 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 392
RP/0/RSP1/CPU0:Jan 20 13:19:55.221 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 392
RP/0/RSP1/CPU0:Jan 20 13:19:55.221 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 0

RP/0/RSP1/CPU0:bord02.arc01#RP/0/RSP1/CPU0:Jan 20 13:20:25.677 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - del:0
RP/0/RSP1/CPU0:Jan 20 13:20:25.677 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:20:25.677 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:870, ACID:1870
RP/0/RSP1/CPU0:Jan 20 13:20:25.677 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - del:0
RP/0/RSP1/CPU0:Jan 20 13:20:25.677 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:20:25.677 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:871, ACID:871
RP/0/RSP1/CPU0:Jan 20 13:20:25.879 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 1088
RP/0/RSP1/CPU0:Jan 20 13:20:25.879 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 544
RP/0/RSP1/CPU0:Jan 20 13:20:25.879 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 544
RP/0/RSP1/CPU0:Jan 20 13:20:25.879 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 0
RP/0/RSP1/CPU0:Jan 20 13:20:25.916 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - del:0
RP/0/RSP1/CPU0:Jan 20 13:20:25.916 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:20:25.916 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:870, ACID:1870
RP/0/RSP1/CPU0:Jan 20 13:20:25.917 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - del:0
RP/0/RSP1/CPU0:Jan 20 13:20:25.917 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:20:25.917 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:871, ACID:871
RP/0/RSP1/CPU0:Jan 20 13:20:25.934 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - del:0
RP/0/RSP1/CPU0:Jan 20 13:20:25.934 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:870, esi:0005.baa1.6405.baa1.6401, etag:1870) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:20:25.934 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:870, ACID:1870
RP/0/RSP1/CPU0:Jan 20 13:20:25.934 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_mgr_remote_update:479, Unpacking EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - del:0
RP/0/RSP1/CPU0:Jan 20 13:20:25.934 UTC: l2vpn_mgr[1256]: DBG-EVPN: evpn_ead_modify:904, Modify EAD(evi:871, esi:0005.baa1.6405.baa1.6401, etag:871) - Modified:0 Reason: 0x0
RP/0/RSP1/CPU0:Jan 20 13:20:25.934 UTC: l2vpn_mgr[1256]: DBG-ERR|EVPN: evpn_vpws_mgr_remote_ead_del:659, EVPN VPWS: Null FWD Lookup. EVI:871, ACID:871
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 1872
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 1328
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 1328
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 784
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 784
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 392
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2654, EVPN LIB: Releasing....memory usage: 392
RP/0/RSP1/CPU0:Jan 20 13:20:26.119 UTC: bgp[1043]: DBG-EVPN: l2vpn_evpn_bgp_memory_release:2665, EVPN LIB: Releasing....memory usage: 0
Highlighted
Beginner

IT look like that even though that port-active mode is configurable in 6.6.3, it is not supported before 7.1.2. I upgraded the routers to 7.2.2 and then the EVPN come up.

View solution in original post

Content for Community-Ad

This widget could not be displayed.