Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Example: Configuring H-VPLS BGP-Based and LDP-Based VPLS Interoperation

This example shows how to configure the hierarchical virtual private LAN service (H-VPLS) in a scenario that uses both LDP-based VPLS and BGP-based VPLS interoperating in a multihoming deployment. This scenario is useful when a customer deployment has the two different types of VPLS in use, and you need to integrate them. Another example is when ISP-A is running BGP-based VPLS and ISP-B is running the LDP-based VPLS, and the two ISPs are merging their networks.

Requirements

No special configuration beyond device initialization is required before configuring this example.

Overview

In this example, Device PE2 and Device PE3 are acting as internetworking provider edge (PE) routers with BGP-based as well as LDP-based VPLS termination.

The devices in this example have the following roles:

  • BGP VPLS only PE—Device PE1
  • LDP VPLS only PE—Device PE4
  • BGP-LDP VPLS PE—Device PE2 and Device PE3

Figure 1 shows the topology used in this example.

Figure 1: H-VPLS with LDP-Based and BGP-Based VPLS Interoperation

H-VPLS with LDP-Based and BGP-Based
VPLS Interoperation

From Device PE4, the pseudowire to Device PE3 is the primary or working path. The pseudowire Device PE2 is the backup path.

CLI Quick Configuration shows the configuration for all of the devices in Figure 1. The section Step-by-Step Procedure describes the steps on Device PE1, Device PE2, and Device PE4.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Device PE1

set interfaces ge-2/0/5 encapsulation ethernet-vplsset interfaces ge-2/0/5 unit 0 description to_CE1set interfaces ge-2/0/5 unit 0 family vplsset interfaces fe-2/0/9 unit 0 description to_PE2set interfaces fe-2/0/9 unit 0 family inet address 10.10.3.1/30set interfaces fe-2/0/9 unit 0 family mplsset interfaces fe-2/0/10 unit 0 description to_PE3set interfaces fe-2/0/10 unit 0 family inet address 10.10.1.1/30set interfaces fe-2/0/10 unit 0 family mplsset interfaces lo0 unit 0 family inet address 1.1.1.1/32set protocols mpls interface fe-2/0/10.0set protocols mpls interface fe-2/0/9.0set protocols ldp interface fe-2/0/10.0set protocols ldp interface fe-2/0/9.0set protocols ldp interface lo0.0set protocols bgp group internal-peers type internalset protocols bgp group internal-peers local-address 1.1.1.1set protocols bgp group internal-peers family l2vpn signalingset protocols bgp group internal-peers neighbor 2.2.2.2set protocols bgp group internal-peers neighbor 3.3.3.3set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface fe-2/0/10.0set protocols ospf area 0.0.0.0 interface fe-2/0/9.0set routing-instances h-vpls-PE1 instance-type vplsset routing-instances h-vpls-PE1 interface ge-2/0/5.0set routing-instances h-vpls-PE1 route-distinguisher 1:1set routing-instances h-vpls-PE1 vrf-target target:1:1set routing-instances h-vpls-PE1 protocols vpls interface ge-2/0/5.0set routing-instances h-vpls-PE1 protocols vpls site PE1-vpls site-identifier 2set routing-options autonomous-system 64510

Device PE2

set interfaces ge-2/0/6 encapsulation ethernet-vplsset interfaces ge-2/0/6 unit 0 description to_CE2set interfaces ge-2/0/6 unit 0 family vplsset interfaces fe-2/0/8 unit 0 description to_PE3set interfaces fe-2/0/8 unit 0 family inet address 10.10.4.2/30set interfaces fe-2/0/8 unit 0 family mplsset interfaces fe-2/0/9 unit 0 description to_PE4set interfaces fe-2/0/9 unit 0 family inet address 10.10.5.1/30set interfaces fe-2/0/9 unit 0 family mplsset interfaces fe-2/0/10 unit 0 description to_PE1set interfaces fe-2/0/10 unit 0 family inet address 10.10.3.2/30set interfaces fe-2/0/10 unit 0 family mplsset interfaces lo0 unit 0 family inet address 2.2.2.2/32set protocols mpls interface fe-2/0/10.0set protocols mpls interface fe-2/0/9.0set protocols mpls interface fe-2/0/8.0set protocols ldp interface fe-2/0/10.0set protocols ldp interface fe-2/0/9.0set protocols ldp interface fe-2/0/8.0set protocols ldp interface lo0.0set protocols bgp group ibgp type internalset protocols bgp group ibgp local-address 2.2.2.2set protocols bgp group ibgp family l2vpn signalingset protocols bgp group ibgp neighbor 3.3.3.3set protocols bgp group ibgp neighbor 1.1.1.1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface fe-2/0/10.0set protocols ospf area 0.0.0.0 interface fe-2/0/9.0set protocols ospf area 0.0.0.0 interface fe-2/0/8.0set routing-instances h-vpls-PE2 instance-type vplsset routing-instances h-vpls-PE2 interface ge-2/0/6.0set routing-instances h-vpls-PE2 route-distinguisher 1:2set routing-instances h-vpls-PE2 vrf-target target:1:1set routing-instances h-vpls-PE2 protocols vpls interface ge-2/0/6.0set routing-instances h-vpls-PE2 protocols vpls site PE2-vpls site-identifier 1set routing-instances h-vpls-PE2 protocols vpls site PE2-vpls multi-homingset routing-instances h-vpls-PE2 protocols vpls site PE2-vpls mesh-group h-vpls-PE2set routing-instances h-vpls-PE2 protocols vpls vpls-id 100set routing-instances h-vpls-PE2 protocols vpls mesh-group h-vpls-PE2 vpls-id 100set routing-instances h-vpls-PE2 protocols vpls mesh-group h-vpls-PE2 local-switchingset routing-instances h-vpls-PE2 protocols vpls mesh-group h-vpls-PE2 neighbor 4.4.4.4set routing-options autonomous-system 64510

Device PE3

set interfaces fe-2/0/8 unit 0 description to_PE2set interfaces fe-2/0/8 unit 0 family inet address 10.10.4.1/30set interfaces fe-2/0/8 unit 0 family mplsset interfaces fe-2/0/9 unit 0 description to_PE4set interfaces fe-2/0/9 unit 0 family inet address 10.10.6.1/30set interfaces fe-2/0/9 unit 0 family mplsset interfaces fe-2/0/10 unit 0 description to_PE1set interfaces fe-2/0/10 unit 0 family inet address 10.10.1.2/30set interfaces fe-2/0/10 unit 0 family mplsset interfaces ge-2/1/3 encapsulation ethernet-vplsset interfaces ge-2/1/3 unit 0 description to_CE3set interfaces ge-2/1/3 unit 0 family vplsset interfaces lo0 unit 0 family inet address 3.3.3.3/32set protocols mpls interface fe-2/0/10.0set protocols mpls interface fe-2/0/8.0set protocols mpls interface fe-2/0/9.0set protocols ldp interface fe-2/0/10.0set protocols ldp interface fe-2/0/9.0set protocols ldp interface fe-2/0/8.0set protocols ldp interface lo0.0set protocols bgp group internal-peers type internalset protocols bgp group internal-peers local-address 3.3.3.3set protocols bgp group internal-peers family l2vpn signalingset protocols bgp group internal-peers neighbor 2.2.2.2set protocols bgp group internal-peers neighbor 1.1.1.1set protocols ospf traffic-engineeringset protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface fe-2/0/10.0set protocols ospf area 0.0.0.0 interface fe-2/0/8.0set protocols ospf area 0.0.0.0 interface fe-2/0/9.0set routing-instances h-vpls-PE3 instance-type vplsset routing-instances h-vpls-PE3 interface ge-2/1/3.0set routing-instances h-vpls-PE3 route-distinguisher 1:3set routing-instances h-vpls-PE3 vrf-target target:1:1set routing-instances h-vpls-PE3 protocols vpls interface ge-2/1/3.0set routing-instances h-vpls-PE3 protocols vpls site PE3-vpls site-identifier 1set routing-instances h-vpls-PE3 protocols vpls site PE3-vpls multi-homingset routing-instances h-vpls-PE3 protocols vpls site PE3-vpls mesh-group h-vpls-PE3set routing-instances h-vpls-PE3 protocols vpls vpls-id 100set routing-instances h-vpls-PE3 protocols vpls mesh-group h-vpls-PE3 vpls-id 100set routing-instances h-vpls-PE3 protocols vpls mesh-group h-vpls-PE3 local-switchingset routing-instances h-vpls-PE3 protocols vpls mesh-group h-vpls-PE3 neighbor 4.4.4.4set routing-options autonomous-system 64510

Device PE4

set interfaces fe-2/0/9 unit 0 description to_PE3set interfaces fe-2/0/9 unit 0 family inet address 10.10.6.2/30set interfaces fe-2/0/9 unit 0 family mplsset interfaces fe-2/0/10 unit 0 description to_PE2set interfaces fe-2/0/10 unit 0 family inet address 10.10.5.2/30set interfaces fe-2/0/10 unit 0 family mplsset interfaces ge-2/1/7 encapsulation ethernet-vplsset interfaces ge-2/1/7 unit 0 description to_CE4set interfaces ge-2/1/7 unit 0 family vplsset interfaces lo0 unit 0 family inet address 4.4.4.4/32set protocols mpls interface fe-2/0/10.0set protocols mpls interface fe-2/0/9.0set protocols ldp interface fe-2/0/10.0set protocols ldp interface fe-2/0/9.0set protocols ldp interface lo0.0set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface fe-2/0/10.0set protocols ospf area 0.0.0.0 interface fe-2/0/9.0set routing-instances ldp-vpls instance-type vplsset routing-instances ldp-vpls interface ge-2/1/7.0set routing-instances ldp-vpls protocols vpls vpls-id 100set routing-instances ldp-vpls protocols vpls neighbor 3.3.3.3set routing-instances ldp-vpls protocols vpls neighbor 2.2.2.2

Device CE1

set interfaces ge-2/0/8 unit 0 description to_PE1set interfaces ge-2/0/8 unit 0 family inet address 172.16.0.1/24set interfaces lo0 unit 0 family inet address 10.255.14.214/32set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface ge-2/0/8.0

Device CE2

set interfaces ge-2/1/5 unit 0 description to_PE2set interfaces ge-2/1/5 unit 0 family inet address 172.16.0.2/24set interfaces lo0 unit 0 family inet address 10.255.14.215/32set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface ge-2/1/5.0

Device CE3

set interfaces ge-2/0/9 unit 0 description to_PE3set interfaces ge-2/0/9 unit 0 family inet address 172.16.0.3/24set interfaces lo0 unit 0 family inet address 10.255.14.218/32set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface ge-2/0/9.0

Device CE4

set interfaces ge-2/1/6 unit 0 description to_PE4set interfaces ge-2/1/6 unit 0 family inet address 172.16.0.4/24set interfaces lo0 unit 0 family inet address 10.255.14.219/32set protocols ospf area 0.0.0.0 interface lo0.0 passiveset protocols ospf area 0.0.0.0 interface ge-2/1/6.0

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure the BGP-based VPLS PE device:

  1. Configure the interfaces.

    On the device interface that connects to the customer edge, enable VPLS encapsulation and the VPLS address family.

    On the core-facing interfaces, enable MPLS labels.

    [edit interfaces]user@PE1# set ge-2/0/5 encapsulation ethernet-vplsuser@PE1# set ge-2/0/5 unit 0 description to_CE1user@PE1# set ge-2/0/5 unit 0 family vpls
    user@PE1# set fe-2/0/10 unit 0 description to_PE3user@PE1# set fe-2/0/10 unit 0 family inet address 10.10.1.1/30user@PE1# set fe-2/0/10 unit 0 family mpls
    user@PE1# set fe-2/0/9 unit 0 description to_PE2user@PE1# set fe-2/0/9 unit 0 family inet address 10.10.3.1/30user@PE1# set fe-2/0/9 unit 0 family mpls
    user@PE1# set lo0 unit 0 family inet address 1.1.1.1/32
  2. Enable MPLS and LDP on the interfaces.

    On the MTU device interfaces that connect to other PE devices, configure MPLS and LDP.

    [edit protocols mpls]user@PE1# set interface fe-2/0/10.0user@PE1# set interface fe-2/0/9.0
    [edit protocols ldp ]user@PE1# set interface fe-2/0/10.0user@PE1# set interface fe-2/0/9.0user@PE1# set interface lo0.0
  3. Enable routing on the interfaces.

    On the MTU device interfaces that connect to other PE devices, configure an interior gateway protocol (IGP), such as OSPF or IS-IS.

    [edit protocols ospf area 0.0.0.0]user@PE1# set interface lo0.0 passiveuser@PE1# set interface fe-2/0/10.0user@PE1# set interface fe-2/0/9.0
  4. Configure BGP with Layer 2 VPN signaling.

    The l2vpn signaling statement enables support for both VPLS and Layer 2 VPN advertisement under the same network layer reachability information (NLRI).

    The internal IBGP (IBGP) full mesh includes Device PE1, Device PE2, and Device PE3. Device PE4 is not included.

    [edit protocols bgp group internal-peers]user@PE1# set type internaluser@PE1# set local-address 1.1.1.1user@PE1# set family l2vpn signalinguser@PE1# set neighbor 2.2.2.2user@PE1# set neighbor 3.3.3.3
  5. Configure the VPLS routing instance.

    Because this is BGP-based VPLS, include a route distinguisher, a VRF target, and a site name and ID.

    [edit routing-instances h-vpls-PE1]user@PE1# set instance-type vplsuser@PE1# set interface ge-2/0/5.0user@PE1# set route-distinguisher 1:1user@PE1# set vrf-target target:1:1
    [edit routing-instances h-vpls-PE1 protocols vpls]user@PE1# set interface ge-2/0/5.0user@PE1# set site PE1-vpls site-identifier 2
  6. Configure the autonomous system (AS) number.
    [edit routing-options]user@PE1# set autonomous-system 64510

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure the BGP-LDP-based VPLS PE device:

  1. Configure the interfaces.

    On the PE-r device interface that connects to the customer edge, configure one of the VPLS encapsulation types and the VPLS address family. This enables VPLS.

    On the core-facing interfaces, enable MPLS labels.

    [edit interfaces]user@PE2# set ge-2/0/6 encapsulation ethernet-vplsuser@PE2# set ge-2/0/6 unit 0 description to_CE2user@PE2# set ge-2/0/6 unit 0 family vpls
    user@PE2# set fe-2/0/10 unit 0 description to_PE1user@PE2# set fe-2/0/10 unit 0 family inet address 10.10.3.2/30user@PE2# set fe-2/0/10 unit 0 family mpls
    user@PE2# set fe-2/0/9 unit 0 description to_PE4user@PE2# set fe-2/0/9 unit 0 family inet address 10.10.5.1/30user@PE2# set fe-2/0/9 unit 0 family mpls
    user@PE2# set fe-2/0/8 unit 0 description to_PE3user@PE2# set fe-2/0/8 unit 0 family inet address 10.10.4.2/30user@PE2# set fe-2/0/8 unit 0 family mpls
    user@PE2# set lo0 unit 0 family inet address 2.2.2.2/32
  2. Enable MPLS and LDP on the interfaces.

    On the MTU device interfaces that connect to other PE devices, configure MPLS and LDP.

    [edit protocols mpls]user@PE2# set interface fe-2/0/10.0user@PE2# set interface fe-2/0/9.0user@PE2# set interface fe-2/0/8.0
    [edit protocols ldp]user@PE2# set interface fe-2/0/10.0user@PE2# set interface fe-2/0/9.0user@PE2# set interface fe-2/0/8.0user@PE2# set interface lo0.0
  3. Enable routing on the interfaces.

    On the MTU device interfaces that connect to other PE devices, configure an interior gateway protocol (IGP), such as OSPF or IS-IS.

    [edit protocols ospf area 0.0.0.0]user@PE2# set interface lo0.0 passiveuser@PE2# set interface fe-2/0/10.0user@PE2# set interface fe-2/0/9.0user@PE2# set interface fe-2/0/8.0
  4. [edit protocols bgp group ibgp]user@PE2# set type internaluser@PE2# set local-address 2.2.2.2user@PE2# set family l2vpn signalinguser@PE2# set neighbor 3.3.3.3user@PE2# set neighbor 1.1.1.1
  5. Configure VPLS.

    The vpls-id statement enables LDP signaling for the VPLS instance.

    [edit routing-instances h-vpls-PE2]user@PE2# set instance-type vplsuser@PE2# set interface ge-2/0/6.0user@PE2# set route-distinguisher 1:2user@PE2# set vrf-target target:1:1
    [edit routing-instances h-vpls-PE2 protocols vpls]user@PE2# set interface ge-2/0/6.0user@PE2# set site PE2-vpls site-identifier 1user@PE2# set site PE2-vpls multi-hominguser@PE2# set site PE2-vpls mesh-group h-vpls-PE2user@PE2# set vpls-id 100user@PE2# set mesh-group h-vpls-PE2 vpls-id 100user@PE2# set mesh-group h-vpls-PE2 local-switchinguser@PE2# set mesh-group h-vpls-PE2 neighbor 4.4.4.4
  6. [edit routing-options]user@PE2# set autonomous-system 64510

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure LDP-based VPLS PE device:

  1. Configure the interfaces.

    On the PE-r device interface that connects to the customer edge, configure one of the VPLS encapsulation types and the VPLS address family. This enables VPLS.

    On the core-facing interfaces, enable MPLS labels.

    [edit interfaces]user@PE4# set fe-2/0/10 unit 0 description to_PE2user@PE4# set fe-2/0/10 unit 0 family inet address 10.10.5.2/30user@PE4# set fe-2/0/10 unit 0 family mpls
    user@PE4# set fe-2/0/9 unit 0 description to_PE3user@PE4# set fe-2/0/9 unit 0 family inet address 10.10.6.2/30user@PE4# set fe-2/0/9 unit 0 family mpls
    user@PE4# set ge-2/1/7 encapsulation ethernet-vplsuser@PE4# set ge-2/1/7 unit 0 description to_CE4user@PE4# set ge-2/1/7 unit 0 family vpls
    user@PE4# set lo0 unit 0 family inet address 4.4.4.4/32
  2. Enable MPLS and LDP on the interfaces.

    On the MTU device interfaces that connect to other PE devices, configure MPLS and LDP.

    [edit protocols mpls]user@PE4# set interface fe-2/0/10.0user@PE4# set interface fe-2/0/9.0
    [edit protocols ldp]user@PE4# set interface fe-2/0/10.0user@PE4# set interface fe-2/0/9.0user@PE4# set interface lo0.0
  3. Enable routing on the interfaces.

    On the MTU device interfaces that connect to other PE devices, configure an interior gateway protocol (IGP), such as OSPF or IS-IS.

    [edit protocols ospf area 0.0.0.0]user@PE4# set interface lo0.0 passiveuser@PE4# set interface fe-2/0/10.0user@PE4# set interface fe-2/0/9.0
  4. Configure VPLS.

    The vpls-id statement enables LDP signaling for the VPLS instance.

    [edit routing-instances ldp-vpls]user@PE4# set instance-type vplsuser@PE4# set interface ge-2/1/7.0user@PE4# set protocols vpls vpls-id 100
    [edit routing-instances ldp-vpls protocols vpls]user@PE4# set neighbor 3.3.3.3user@PE4# set neighbor 2.2.2.2

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show routing-instances, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Device PE1

user@PE1# show interfaces
ge-2/0/5 {encapsulation ethernet-vpls;unit 0 {description to_CE1;family vpls;}}
fe-2/0/9 {}
unit 0 {description to_PE2;family inet {address 10.10.3.1/30;}family mpls;}}
fe-2/0/10 {unit 0 {description to_PE3;family inet {address 10.10.1.1/30;}family mpls;}}
lo0 {unit 0 {family inet {address 1.1.1.1/32;}}}
user@PE1# show protocols
mpls {interface fe-2/0/10.0;interface fe-2/0/9.0;}
bgp {group internal-peers {type internal;local-address 1.1.1.1;family l2vpn {signaling;}neighbor 2.2.2.2;neighbor 3.3.3.3;}}
ospf {area 0.0.0.0 {interface lo0.0 {passive;}interface fe-2/0/10.0;interface fe-2/0/9.0;}}
ldp {interface fe-2/0/10.0;interface fe-2/0/9.0;interface lo0.0;}
user@PE1# show routing-instances
h-vpls-PE1 {instance-type vpls;interface ge-2/0/5.0;route-distinguisher 1:1;vrf-target target:1:1;protocols {vpls {interface ge-2/0/5.0;site PE1-vpls {site-identifier 2;}}}}
user@PE1# show routing-optionsautonomous-system 64510;

Device PE2

user@PE2# show interfaces
ge-2/0/6 {encapsulation ethernet-vpls;unit 0 {description to_CE2;family vpls;}}
fe-2/0/8 {unit 0 {description to_PE3;family inet {address 10.10.4.2/30;}family mpls;}}
fe-2/0/9 {unit 0{description to_PE4;family inet {address 10.10.5.1/30;}family mpls;}}
fe-2/0/10 {unit 0 {description to_PE1;family inet {address 10.10.3.2/30;}family mpls;}}
lo0 {unit 0 {family inet {address 2.2.2.2/32;}}}
user@PE2# show protocols
mpls {interface fe-2/0/10.0;interface fe-2/0/9.0;interface fe-2/0/8.0;}
bgp {group ibgp {type internal;local-address 2.2.2.2;family l2vpn {signaling;}neighbor 3.3.3.3;neighbor 1.1.1.1;}}
ospf {area 0.0.0.0 {interface lo0.0 {passive;}interface fe-2/0/10.0;interface fe-2/0/9.0;interface fe-2/0/8.0;}}
ldp {interface fe-2/0/10.0;interface fe-2/0/9.0;interface fe-2/0/8.0;interface lo0.0;}
user@PE2# show routing-instances
h-vpls-PE2 {instance-type vpls;interface ge-2/0/6.0;route-distinguisher 1:2;vrf-target target:1:1;protocols {vpls {interface ge-2/0/6.0;site PE2-vpls {site-identifier 1;multi-homing;mesh-group h-vpls-PE2;}vpls-id 100;mesh-group h-vpls-PE2 {vpls-id 100;local-switching;neighbor 4.4.4.4;}}}}
user@PE2# show routing-optionsautonomous-system 64510;

Device PE4

user@PE4# show interfaces
ge-2/1/7 {encapsulation ethernet-vpls;unit 0 {description to_CE4;family vpls;}}
fe-2/0/9 {unit 0 {description to_PE3;family inet {address 10.10.6.2/30;}family mpls;}}
fe-2/0/10 {unit 0 {description to_PE2;family inet {address 10.10.5.2/30;}family mpls;}}
lo0 {unit 0 {family inet {address 4.4.4.4/32;}}}
user@PE4# show protocols
mpls {interface fe-2/0/9.0;interface fe-2/0/10.0;}
ospf {area 0.0.0.0 {interface lo0.0 {passive;}interface fe-2/0/9.0;interface fe-2/0/10.0;}}
ldp {interface fe-2/0/10.0;interface fe-2/0/9.0;interface lo0.0;}
user@PE4# show routing-instances
ldp-vpls {instance-type vpls;interface ge-2/1/7.0;protocols {vpls {vpls-id 100;neighbor 3.3.3.3;neighbor 2.2.2.2;}}}

If you are done configuring the devices, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly. In a multihoming scenario with BGP-LDP VPLS, the LDP pseudowires are in the down state for the backup PE (Device PE2). Whereas on the LDP-only VPLS PE (Device PE4), the pseudowires to the primary and backup BGP-LDP PE devices are in the up state.

Verifying the VPLS Connections

Purpose

Verify that the VPLS connections are working as expected.

Action

From operational mode, enter the show vpls connections command.

Layer-2 VPN connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status 
Up -- operational           
Dn -- down

Instance: h-vpls-PE1
  Local site: PE1-vpls (2)
    connection-site           Type  St     Time last up          # Up trans
    1                         rmt   Up     Oct 16 16:52:27 2012           1
      Remote PE: 2.2.2.2, Negotiated control-word: No
      Incoming label: 800016, Outgoing label: 800009
      Local interface: vt-2/0/10.51380738, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls h-vpls-PE1 local site 2 remote site 1
user@PE2> show vpls connections
Layer-2 VPN connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status 
Up -- operational           
Dn -- down

Instance: h-vpls-PE2
  BGP-VPLS State
  Local site: PE2-vpls (1)
    connection-site           Type  St     Time last up          # Up trans
    1                         rmt   RN   
    2                         rmt   Up     Oct 16 17:12:31 2012           1
      Remote PE: 1.1.1.1, Negotiated control-word: No
      Incoming label: 800257, Outgoing label: 800000
      Local interface: vt-2/0/10.118489089, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls h-vpls-PE2 local site 1 remote site 2
  LDP-VPLS State
  VPLS-id: 100
  Mesh-group connections: h-vpls-PE2
    Neighbor                  Type  St     Time last up          # Up trans
    4.4.4.4(vpls-id 100)      rmt   Up     Oct 16 17:12:30 2012           1
      Remote PE: 4.4.4.4, Negotiated control-word: No
      Incoming label: 800000, Outgoing label: 800001
      Negotiated PW status TLV: No
      Local interface: vt-2/0/10.118489088, Status: Up, Encapsulation: ETHERNET
        Description: Intf - vpls h-vpls-PE2 neighbor 4.4.4.4 vpls-id 100
user@PE3> show vpls connections
Layer-2 VPN connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status 
Up -- operational           
Dn -- down

Instance: h-vpls-PE3
  BGP-VPLS State
  Local site: PE3-vpls (1)
    connection-site           Type  St     Time last up          # Up trans
    1                         rmt   LN   
    2                         rmt   LN   
  LDP-VPLS State
  VPLS-id: 100
  Mesh-group connections: h-vpls-PE3
    Neighbor                  Type  St     Time last up          # Up trans
    4.4.4.4(vpls-id 100)      rmt   LN   
user@PE4> show vpls connections
Layer-2 VPN connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status 
Up -- operational           
Dn -- down

Instance: ldp-vpls
  VPLS-id: 100
    Neighbor                  Type  St     Time last up          # Up trans
    2.2.2.2(vpls-id 100)      rmt   Up     Oct 16 17:12:23 2012           1
      Remote PE: 2.2.2.2, Negotiated control-word: No
      Incoming label: 800001, Outgoing label: 800000
      Negotiated PW status TLV: No
      Local interface: vt-2/0/10.17825793, Status: Up, Encapsulation: ETHERNET
        Description: Intf - vpls ldp-vpls neighbor 2.2.2.2 vpls-id 100
    3.3.3.3(vpls-id 100)      rmt   Up     Oct 16 17:12:20 2012           1
      Remote PE: 3.3.3.3, Negotiated control-word: No
      Incoming label: 800000, Outgoing label: 800000
      Negotiated PW status TLV: No
      Local interface: vt-2/0/10.17825792, Status: Up, Encapsulation: ETHERNET
        Description: Intf - vpls ldp-vpls neighbor 3.3.3.3 vpls-id 100

Meaning

On Device PE1, the BGP-VPLS connection to Device PE2 is up. In a steady-state condition, Device PE2 is the primary router and has all pseudowires terminating on it. Traffic flows from CE1 to PE1 to PE2 to PE4 to CE4.

On Device PE2, the BGP-VPLS connection to Device PE1 is up. The connection to Device PE3 is in the RN state. The LDP-VPLS connection to Device PE4 is up.

On Device PE3, all VPLS connections are in the LN state. This is expected because Device PE3 is the backup.

On Device PE4, the LDP-only VPLS router, the primary pseudowire to Device PE2 and the backup pseudowire to Device PE3 are in the up state.

Manually Triggering a Switch from the Active Pseudowire to the Backup Pseudowire

Purpose

Verify that when Device PE2 becomes unavailable, the traffic flow shifts to Device PE3.

Action

  1. On Device PE2, deactivate the interfaces.
    user@PE2# deactivate interfacesuser@PE2# commit
  2. Rerun the show vpls connections command on all of the PE devices.
    Layer-2 VPN connections:
    
    Legend for connection status (St)   
    EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
    EM -- encapsulation mismatch     WE -- interface and instance encaps not same
    VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
    CM -- control-word mismatch      -> -- only outbound connection is up
    CN -- circuit not provisioned    <- -- only inbound connection is up
    OR -- out of range               Up -- operational
    OL -- no outgoing label          Dn -- down                      
    LD -- local site signaled down   CF -- call admission control failure      
    RD -- remote site signaled down  SC -- local and remote site ID collision
    LN -- local site not designated  LM -- local site ID not minimum designated
    RN -- remote site not designated RM -- remote site ID not minimum designated
    XX -- unknown connection status  IL -- no incoming label
    MM -- MTU mismatch               MI -- Mesh-Group ID not available
    BK -- Backup connection          ST -- Standby connection
    PF -- Profile parse failure      PB -- Profile busy
    RS -- remote site standby        SN -- Static Neighbor
    LB -- Local site not best-site   RB -- Remote site not best-site
    VM -- VLAN ID mismatch
    
    Legend for interface status 
    Up -- operational           
    Dn -- down
    
    Instance: h-vpls-PE1
      Local site: PE1-vpls (2)
        connection-site           Type  St     Time last up          # Up trans
        1                         rmt   Up     Oct 17 12:24:01 2012           2
          Remote PE: 3.3.3.3, Negotiated control-word: No
          Incoming label: 800000, Outgoing label: 800257
          Local interface: vt-2/0/10.84934656, Status: Up, Encapsulation: VPLS
            Description: Intf - vpls h-vpls-PE1 local site 2 remote site 1
    user@PE2> show vpls connections
    Layer-2 VPN connections:
    
    Legend for connection status (St)   
    EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
    EM -- encapsulation mismatch     WE -- interface and instance encaps not same
    VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
    CM -- control-word mismatch      -> -- only outbound connection is up
    CN -- circuit not provisioned    <- -- only inbound connection is up
    OR -- out of range               Up -- operational
    OL -- no outgoing label          Dn -- down                      
    LD -- local site signaled down   CF -- call admission control failure      
    RD -- remote site signaled down  SC -- local and remote site ID collision
    LN -- local site not designated  LM -- local site ID not minimum designated
    RN -- remote site not designated RM -- remote site ID not minimum designated
    XX -- unknown connection status  IL -- no incoming label
    MM -- MTU mismatch               MI -- Mesh-Group ID not available
    BK -- Backup connection          ST -- Standby connection
    PF -- Profile parse failure      PB -- Profile busy
    RS -- remote site standby        SN -- Static Neighbor
    LB -- Local site not best-site   RB -- Remote site not best-site
    VM -- VLAN ID mismatch
    
    Legend for interface status 
    Up -- operational           
    Dn -- down
    
    Instance: h-vpls-PE2
      BGP-VPLS State
      Local site: PE2-vpls (1)
      LDP-VPLS State
      VPLS-id: 100
      Mesh-group connections: h-vpls-PE2
        Neighbor                  Type  St     Time last up          # Up trans
        4.4.4.4(vpls-id 100)      rmt   OL 
    user@PE3> show vpls connections
    Layer-2 VPN connections:
    
    Legend for connection status (St)   
    EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
    EM -- encapsulation mismatch     WE -- interface and instance encaps not same
    VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
    CM -- control-word mismatch      -> -- only outbound connection is up
    CN -- circuit not provisioned    <- -- only inbound connection is up
    OR -- out of range               Up -- operational
    OL -- no outgoing label          Dn -- down                      
    LD -- local site signaled down   CF -- call admission control failure      
    RD -- remote site signaled down  SC -- local and remote site ID collision
    LN -- local site not designated  LM -- local site ID not minimum designated
    RN -- remote site not designated RM -- remote site ID not minimum designated
    XX -- unknown connection status  IL -- no incoming label
    MM -- MTU mismatch               MI -- Mesh-Group ID not available
    BK -- Backup connection          ST -- Standby connection
    PF -- Profile parse failure      PB -- Profile busy
    RS -- remote site standby        SN -- Static Neighbor
    LB -- Local site not best-site   RB -- Remote site not best-site
    VM -- VLAN ID mismatch
    
    Legend for interface status 
    Up -- operational           
    Dn -- down
    
    Instance: h-vpls-PE3
      BGP-VPLS State
      Local site: PE3-vpls (1)
        connection-site           Type  St     Time last up          # Up trans
        2                         rmt   Up     Oct 17 12:24:01 2012           1
          Remote PE: 1.1.1.1, Negotiated control-word: No
          Incoming label: 800257, Outgoing label: 800000
          Local interface: vt-2/0/10.135266304, Status: Up, Encapsulation: VPLS
            Description: Intf - vpls h-vpls-PE3 local site 1 remote site 2
      LDP-VPLS State
      VPLS-id: 100
      Mesh-group connections: h-vpls-PE3
        Neighbor                  Type  St     Time last up          # Up trans
        4.4.4.4(vpls-id 100)      rmt   Up     Oct 17 12:24:02 2012           1
          Remote PE: 4.4.4.4, Negotiated control-word: No
          Incoming label: 800000, Outgoing label: 800000
          Negotiated PW status TLV: No
          Local interface: vt-2/0/10.135266305, Status: Up, Encapsulation: ETHERNET
            Description: Intf - vpls h-vpls-PE3 neighbor 4.4.4.4 vpls-id 100
    user@PE4> show vpls connections
    Layer-2 VPN connections:
    
    Legend for connection status (St)   
    EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
    EM -- encapsulation mismatch     WE -- interface and instance encaps not same
    VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
    CM -- control-word mismatch      -> -- only outbound connection is up
    CN -- circuit not provisioned    <- -- only inbound connection is up
    OR -- out of range               Up -- operational
    OL -- no outgoing label          Dn -- down                      
    LD -- local site signaled down   CF -- call admission control failure      
    RD -- remote site signaled down  SC -- local and remote site ID collision
    LN -- local site not designated  LM -- local site ID not minimum designated
    RN -- remote site not designated RM -- remote site ID not minimum designated
    XX -- unknown connection status  IL -- no incoming label
    MM -- MTU mismatch               MI -- Mesh-Group ID not available
    BK -- Backup connection          ST -- Standby connection
    PF -- Profile parse failure      PB -- Profile busy
    RS -- remote site standby        SN -- Static Neighbor
    LB -- Local site not best-site   RB -- Remote site not best-site
    VM -- VLAN ID mismatch
    
    Legend for interface status 
    Up -- operational           
    Dn -- down
    
    Instance: ldp-vpls
      VPLS-id: 100
        Neighbor                  Type  St     Time last up          # Up trans
        2.2.2.2(vpls-id 100)      rmt   OL   
        3.3.3.3(vpls-id 100)      rmt   Up     Oct 16 17:12:20 2012           1
          Remote PE: 3.3.3.3, Negotiated control-word: No
          Incoming label: 800000, Outgoing label: 800000
          Negotiated PW status TLV: No
          Local interface: vt-2/0/10.17825792, Status: Up, Encapsulation: ETHERNET
            Description: Intf - vpls ldp-vpls neighbor 3.3.3.3 vpls-id 100

Meaning

On Device PE1, the BGP-VPLS connection to Device PE3 is up. Traffic flows from CE1 to PE1 to PE3 to PE4 to CE4.

On Device PE2, the BGP-VPLS connection to Device PE1 is in the OL state.

On Device PE3, all VPLS connections are up.

On Device PE4, the VPLS connection to Device PE2 is in the OL state. The VPLS connection to Device PE3 is up.

If you reactivate the interfaces on Device PE2, the connections revert to their previous state and traffic flow.

Checking Connectivity

Purpose

Verify that Device CE1 can ping Device CE4.

Action

user@CE1> ping 10.255.14.219
PING 10.255.14.219 (10.255.14.219): 56 data bytes
64 bytes from 10.255.14.219: icmp_seq=0 ttl=64 time=1.149 ms
64 bytes from 10.255.14.219: icmp_seq=1 ttl=64 time=0.779 ms
^C
--- 10.255.14.219 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.779/0.964/1.149/0.185 ms

Meaning

The output shows that VPLS is operational.

Checking the BGP Layer 2 VPN Routing Tables

Purpose

Verify that the VPLS routes are learned from BGP.

Action

user@PE1> show route table bgp.l2vpn.0
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1:3:1:1/96                
                   *[BGP/170] 20:00:11, localpref 100, from 3.3.3.3
                      AS path: I, validation-state: unverified
                    > to 10.10.1.2 via fe-2/0/10.0
user@PE3> show route table bgp.l2vpn.0
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1:1:2:1/96                
                   *[BGP/170] 20:00:11, localpref 100, from 1.1.1.1
                      AS path: I, validation-state: unverified
                    > to 10.10.1.1 via fe-2/0/10.0

Checking the Layer 2 Circuit Routing Tables

Purpose

Verify that the VPLS routes are learned from LDP.

Action

user@PE3> show route table l2circuit.0
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

4.4.4.4:NoCtrlWord:5:100:Local/96                
                   *[VPLS/7] 01:30:11, metric2 1
                    > to 10.10.6.2 via fe-2/0/9.0
4.4.4.4:NoCtrlWord:5:100:Remote/96                
                   *[LDP/9] 20:41:57
                      Discard
user@PE4> show route table bgp.l2vpn.0
l2circuit.0: 3 destinations, 3 routes (2 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

3.3.3.3:NoCtrlWord:5:100:Local/96                
                   *[VPLS/7] 20:42:51, metric2 1
                    > to 10.10.6.1 via fe-2/0/9.0
3.3.3.3:NoCtrlWord:5:100:Remote/96                
                   *[LDP/9] 20:41:57
                      Discard

Published: 2013-02-28