L2VPN LDP signaled VPLS between Ios & Junos with Control Word enabled

[Jerems]

Hi dear community,

I have a good one for you regarding the setup of a vpls (ldp signaled) between a Cisco ISR1100X and a Juniper SRX300.

As an example i am sending a simple ping between each node at each side of the VPLS.

Both nodes are in Vlan 18 and has an IP **bleep** of 192.168.18.1/24 & 192.168.18.2/24

It was working well initially but for some learning purpose and because wireshark needed some specific parametres (" Decode As") related to PW Control Word, i decided to enable control word at each PE.

Could it be the reason of the failure when trying to ping each node ?

Here is the config :

Cisco PE :

l2vpn vfi context VPLS-12118 
 vpn id 12118
 member pseudowire12118
!
bridge-domain 18 
 member vfi VPLS-12118
!
interface pseudowire12118
 encapsulation mpls
 signaling protocol ldp
 neighbor 10.0.0.1 12118
 control-word include
!
interface GigabitEthernet0/0/1
 no ip **bleep**
 negotiation auto
 service instance 18 ethernet
  encapsulation dot1q 18
  bridge-domain 18

Juniper PE:

set interfaces ge-0/0/5 unit 18 description "vlan l2vpn-test-vpls"
set interfaces ge-0/0/5 unit 18 encapsulation vlan-vpls
set interfaces ge-0/0/5 unit 18 vlan-id 18
set interfaces ge-0/0/5 unit 18 family vpls
!
set routing-instances vpls-12118 protocols vpls neighbor 10.0.0.21
set routing-instances vpls-12118 protocols vpls encapsulation-type ethernet
set routing-instances vpls-12118 protocols vpls control-word
set routing-instances vpls-12118 protocols vpls no-tunnel-services
set routing-instances vpls-12118 protocols vpls vpls-id 12118
set routing-instances vpls-12118 protocols vpls pseudowire-status-tlv
set routing-instances vpls-12118 interface ge-0/0/5.18
set routing-instances vpls-12118 instance-type vpls
set routing-instances vpls-12118 vlan-id 18

and the results from the cisco perspective:

jey-isr1K-pe-01#sh l2vpn vfi name VPLS-12118 detail
Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: VPLS-12118, state: up, type: multipoint, signaling: LDP
  VPN ID: 12118
  Bridge-Domain 18 attachment circuits:
  Pseudo-port interface: pseudowire100003
  Interface          Peer **bleep**     VC ID        S
  pseudowire12118    10.0.0.1         12118        Y

jey-isr1K-pe-01#sh l2vpn service vfi peer 10.0.0.1 vcid 12118 detail 
Legend: St=State    XC St=State in the L2VPN Service      Prio=Priority
        UP=Up       DN=Down            AD=Admin Down      IA=Inactive
        SB=Standby  HS=Hot Standby     RV=Recovering      NH=No Hardware
        m=manually selected

  Interface          Group       Encapsulation                   Prio  St  XC St
  ---------          -----       -------------                   ----  --  -----
VPLS name: VPLS-12118, State: UP
  pw100003                       VPLS-12118(VFI)                 0     UP  UP   
  pw12118            core_pw     10.0.0.1:12118(MPLS)            0     UP  UP   
                                 Local VC label 47              
                                 Remote VC label 262145         

It seems like the mac addresses are correctly flowing between each peers :

jey-isr1K-pe-01#sh bridge-domain 18
Bridge-domain 18 (2 ports in all)
State: UP                    Mac learning: Enabled
Aging-Timer: 300 second(s)
Unknown Unicast Flooding Suppression: Disabled
Maximum **bleep** limit: 65536
    GigabitEthernet0/0/1 service instance 18
    vfi VPLS-12118 neighbor 10.0.0.1 12118
   AED MAC **bleep**    Policy  Tag       Age  Pseudoport
   0   207B.D2D9.24AD forward dynamic   299  GigabitEthernet0/0/1.EFP18
   0   A8B4.56B6.5480 forward dynamic   300  VPLS-12118.40401c

and the screenshot of a capture framed related to ARP request :

In the screenshot above, the PW ethernet Control Word Sequence number with the value 0 is not what is expected, i believe.

Do you have any thoughts on this subject please?

Thanks in advance,

Jerems

[Jerems]

So....

I launched another serie of test with two Cisco Router at each side of the VPLS service with Control Word Enabled and it works fine:

For some reasons the sequence number is still at 0.

I will disable the Control Word option on the pseudowire interface on each PE and will see what happens in an other serie of packet capture.

Regards,

Jerems

[Jerems]

So i changed the config from each Cisco PE :

From :

interface pseudowire2122
 encapsulation mpls
 signaling protocol ldp
 neighbor 10.0.0.22 212221
 mtu 1500
 control-word include

To:

interface pseudowire2122
 encapsulation mpls
 signaling protocol ldp
 neighbor 10.0.0.22 212221
 mtu 1500

 For sure it still works as shows the screenshot below :

PW option still there with no sequence number.

Disabling the Control Word has no effect as it turns into autosense mode:

So finally, i can suggest that there could be some interop issue or that  i am missing something in the configuration on the vpls between a Cisco and Juniper device.

@Harold Ritter @MHM Cisco World , any suggestions ?

Thanks in advance,

Jerems

[Jerems · Accepted solution]

As a reminder here is the config that does not work between Juniper and Cisco:

You will need to delete this statement to let the VPLS working well.

Regards,

Jerems

[Harold Ritter · Accepted solution]

Hi @Jerems ,

I have this configured between a CSR1k and a VMX device and it works well with or without the control word. I see that traffic if flowing between the 2 devices in your previous post. Can you be more specific on what is not working? What is the interop issue?

Regards,

[Jerems]

Hi @Harold Ritter ,

A continuous ping between both hosts at each side of the vpls stopped to work once i enabled the Control Word option on Juniper side. I should probably post something on juniper community website

[Harold Ritter · Accepted solution]

Hi @Jerems ,

Thanks for the additional information. This might be a platform specific issue. No issues for me between CSR1k and VMX with the exact same configuration.

Regards,