LDP Based VPLS – Configuration Between Cisco IOS XE and Juniper MX

ciscojunipermplsvpls

im struggeling in setting up LDP based VPLS in a Cisco/Juniper mixed vendor environment.

The configuration is currently running between two Cisco Boxes, but i have to migrate on side to Juniper.

this is the current configuration:

Cisco ASR1k:

l2 vfi VPLS-1839 manual 
vpn id 1839
bridge-domain 1839
neighbor x.x.x.x encapsulation mpls

interface GigabitEthernet0/0/3
 no ip address
 negotiation auto
 service instance 1839 ethernet
  encapsulation untagged
  rewrite ingress tag push dot1q 1839 symmetric
  bridge-domain 1839

Juniper MX:

routing-instances {
    VPLS-1839 {
        instance-type vpls;
        vlan-id none;
        interface xe-1/1/0.0;
        protocols {
            vpls {
                no-tunnel-services;
                vpls-id 1839;
                neighbor x.x.x.x;
            }
        }
    }
}

a "show vpls connections" on the Juniper shows following output.

Instance: VPLS-1839
  VPLS-id: 1839
    Neighbor                  Type  St     Time last up          # Up trans
    x.x.x.x(vpls-id 1839) rmt OL

OL is described as "no outgoing label", but i don't have an idea what this message is trying to tell me.

LDP is running on alle core-facing interfaces and the lo0.0. MPLS address-family is also present on all interfaces.

Any idea how to isolate the cause of this issue?
Thanks in advance for any hints.

Best Answer

No outgoing label indicates that Junos doesn't have a label for the loopback you are targeting on the Cisco (your x.x.x.x address)

Confirm the following:

  1. Your NNI interface from the Juniper has family mpls configured
  2. Under protocols mpls you have the NNI interface defined
  3. Under protocols ldp you have the NNI interface defined
  4. Under protocols ldp you also have the loopback interface defined
  5. Finally, use show ldp session or show route table inet.3 and confirm that the far-end loopback is visible in the list
Related Topic