[Contents] [Prev] [Next] [Index] [Report an Error]

Example: VPLS Configuration (BGP Signaling)

Figure 94: VPLS Topology Diagram

Image g017142.gif

In Figure 94, a simple VPLS topology is enabled between routers PE1 and PE2. CE routers CE1 and CE2 use Ethernet-based interfaces to connect VLAN 600 to their local PE router. The PE routers PE1 and PE2 are connected to one another by LSPs enabled across a service provider backbone running MPLS, BGP, RSVP, and OSPF.

In a VPLS routing instance named green, PE1 has a local interface fe-0/1/0 and a virtual port of vt-0/3/0.32770 (the virtual port is created dynamically on the Tunnel Services PIC when VPLS is configured). PE2 has a local interface fe-0/1/0 and a virtual port of vt-0/3/0.32771 in the same green instance. As a result, routers CE1 and CE2 can send Ethernet traffic to one another as if they are physically connected to each other on a LAN.

On Router CE1, the only item you need to configure is the Fast Ethernet interface that connects to PE1. Be sure to write down the VLAN identifier and IP address, so you can match them later on CE2.

Router CE1

[edit]
interfaces {
fe-0/1/0 {
vlan-tagging;# Configure VLAN tagging for VLAN VPLS or extended VLAN VPLS.
unit 0 {
vlan-id 600;# The Ethernet interface on CE2 must use the same VLAN ID.
family inet {
address 10.11.3.1/24; # The interface on CE2 must use the same prefix.
}
}
}
}

On Router PE1, prepare the router for VPLS by configuring BGP, MPLS, OSPF, and RSVP. (These protocols are the basis for most Layer 2 VPN-related applications, including VPLS.) Include the signaling statement at the [edit protocols bgp group group-name family l2vpn] hierarchy level, because VPLS uses the same infrastructure for internal BGP as Layer 2 VPNs.

Note: In JUNOS Release 7.3 and later, the signaling statement replaces the unicast statement at the [edit protocols bgp group group-name family l2vpn] hierarchy level. You must use the signaling statement if you wish to configure VPLS domains and Layer 2 VPNs simultaneously.

Next, configure VLAN tagging on the Fast Ethernet interface connected to Router CE1. Include VLAN VPLS encapsulation at both the physical and logical interface levels. Be sure to use the same VLAN ID for all Ethernet interfaces that are part of a single VPLS instance. Finally, add the Fast Ethernet interface into a VPLS routing instance and specify the site range, site ID number, and site name.

Router PE1

[edit]
interfaces {
fe-0/1/0 {
vlan-tagging;# Configure VLAN tagging for VLAN VPLS or extended VLAN VPLS.
encapsulation vlan-vpls; # Configure VPLS encapsulation on both the
unit 0 { # physical interface and the logical interface.
encapsulation vlan-vpls;
vlan-id 600;# The VLAN ID is the same one used by the CE routers.
}
}
so-1/1/0 {
unit 0 {
family inet {
address 10.11.1.5/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.245.14.218/32;
}
}
}
}
routing-options {
autonomous-system 69;
forwarding-table {
export exp-to-fwd;# Applies a policy that selects an LSP for the VPLS instance.
}
}
protocols {
rsvp {
interface all {
aggregate;
}
}
mpls {
label-switched-path pe1-to-pe2 { # Configure an LSP to reach other VPLS PEs.
to 10.245.14.219;
}
interface all;
}
bgp {
group vpls-pe {
type internal;
local-address 10.245.14.218;
family l2vpn { # VPLS uses the same infrastructure as Layer 2 VPNs
signaling; # for internal BGP.
}
neighbor 10.245.14.217;
neighbor 10.245.14.219;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface so-1/1/0.0 {
metric 11;
}
interface lo0.0 {
passive;
}
}
}
}
policy-options {
policy-statement exp-to-fwd {
term a {
from community grn-com; # Matches the community in the VPLS instance.
then {
install-nexthop lsp pe1-to-pe2; # If there are multiple LSPs that exist
accept; # between VPLS PE routers, this statement sends VPLS traffic
}
}
}
community grn-com members target:11111:1; # Adds the instance to a BGP community.
}
routing-instances {
green {
instance-type vpls; # Configure a VPLS routing instance.
interface fe-0/1/0.0;
route-distinguisher 10.245.14.218:1;
vrf-target target:11111:1; # This value is important to the BGP community.
protocols {
vpls {# Configure a VPLS site range, site name, and site identifier.
site-range 10;
site greenPE1 {
site-identifier 1;
}
}
}
}
}

On Router P0, configure BGP, MPLS, OSPF, and RSVP to interconnect PE1 and PE2.

Router P0

[edit]
interfaces {
so-0/0/0 {
unit 0 {
family inet {
address 10.11.2.6/30;
}
family mpls;
}
}
so-1/1/0 {
unit 0 {
family inet {
address 10.11.1.6/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.245.14.217/32;
}
}
}
}
protocols {
rsvp {
interface all {
aggregate;
}
}
mpls {
interface all;
}
bgp {
group vpls-pe {
type internal;
local-address 10.245.14.217;
family l2vpn { # VPLS uses the same infrastructure as Layer 2 VPNs
signaling; #for internal BGP.
}
neighbor 10.245.14.218;
neighbor 10.245.14.219;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface so-1/1/0.0 {
metric 11;
}
interface so-0/0/0.0 {
metric 15;
}
interface lo0.0 {
passive;
}
}
}
}

On Router PE2, configure BGP, MPLS, OSPF, and RSVP to complement the configuration on PE1. Next, configure VLAN tagging on the Fast Ethernet interface connected to Router CE2. Include VLAN VPLS encapsulation at both the physical and logical interface levels. Be sure to use the same VLAN ID for all Ethernet interfaces that are part of a single VPLS instance. Finally, add the Fast Ethernet interface into a VPLS routing instance and specify the site range, site ID number, and site name.

Router PE2

[edit]
interfaces {
fe-0/1/0 {
vlan-tagging; # Configure VLAN tagging for VLAN VPLS or extended VLAN VPLS.
encapsulation vlan-vpls; # Configure VPLS encapsulation on both the
unit 0 { # physical interface and logical interface.
encapsulation vlan-vpls;
vlan-id 600;# The VLAN ID is the same one used by the CE routers.
}
}
so-0/0/0 {
unit 0 {
family inet {
address 10.11.2.5/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.245.14.219/32;
}
}
}
}
routing-options {
autonomous-system 69;
forwarding-table {
export exp-to-fwd; # Applies a policy that selects an LSP for the VPLS instance.
}
}
protocols {
rsvp {
interface all {
aggregate;
}
}
mpls {
label-switched-path pe2-to-pe1 { # Configure an LSP to other VPLS PE routers.
to 10.245.14.218;
}
interface all;
}
bgp {
group vpls-pe {
type internal;
local-address 10.245.14.219;
family l2vpn { # VPLS uses the same infrastructure as Layer 2 VPNs
signaling; # for internal BGP.
}
neighbor 10.245.14.217;
neighbor 10.245.14.218;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface so-0/0/0.0 {
metric 15;
}
interface lo0.0 {
passive;
}
}
}
}
policy-options {
policy-statement exp-to-fwd {
term a {
from community grn-com; # Matches the community with the VPLS instance.
then {
install-nexthop lsp pe2-to-pe1; # If there are multiple LSPs that exist
accept; # between VPLS PE routers, this statement sends VPLS traffic
}
}
}
community grn-com members target:11111:1; # This adds the instance into a BGP community.
}
routing-instances {
green {
instance-type vpls; # Configure a VPLS routing instance.
interface fe-0/1/0.0;
route-distinguisher 10.245.14.219:1;
vrf-target target:11111:1; # This value is important for the BGP community.
protocols {
vpls { # Configure a VPLS site range, site name, and site identifier.
site-range 10;
site greenPE2 {
site-identifier 2;
}
}
}
}
}

On Router CE2, complete your VPLS network by configuring the Fast Ethernet interface that connects to PE2. Use the same VLAN identifier and IP address prefix used on Router CE1.

Router CE2

[edit]
interfaces {
fe-0/1/0 {
vlan-tagging; # Configure VLAN tagging for VLAN VPLS or extended VLAN VPLS.
unit 0 {
vlan-id 600; # The Ethernet interface on CE1 must use the same VLAN ID.
family inet {
address 10.11.3.2/24; # The interface on CE1 must use the same prefix.
}
}
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.