Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > Example: Configuring VPLS LDP Signaling
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...

Example: Configuring VPLS LDP Signaling

The example in this section shows how to configure the VPLS topology illustrated in Figure 1. The example includes the commands for configuring VPLS on both the local E Series router (PE 1) and the remote E Series router (PE 2).

Figure 1: Topology for VPLS Configuration Example with LDP Signaling

Topology for VPLS Configuration Example
with LDP Signaling
  • Topology Overview of VPLS with LDP Signaling
  • Configuration on PE 1 (Local PE Router)
  • Configuration on PE 2 (Remote PE Router)

Topology Overview of VPLS with LDP Signaling

Because the basic components of a VPLS network are the same regardless of whether BGP signaling or LDP signaling is used, the sample topology shown for LDP signaling in Figure 1 is almost identical to the sample topology shown for BGP signaling in Topology for VPLS Configuration Example with BGP Signaling. Figure 1 includes two VPLS domains: VPLS A, which connects CE 1 and CE 3, and VPLS B, which connects CE 2 and CE 4. The local PE router, PE 1, and the remote PE router, PE 2, each participate in both the VPLS A domain and the VPLS B domain, and have one VPLS instance associated with each domain configured on each router.

Unlike a VPLS configuration with BGP signaling, a VPLS configuration with LDP signaling requires that you configure a VPLS ID for each VPLS instance to uniquely identify each VPLS domain. In the sample topology in Figure 1, instance vplsA is assigned VPLS ID 1, and instance vplsB is assigned VPLS ID 2 on both the local PE router and the remote PE router. You must also configure a list of remote neighbor (peer) addresses to which LDP can send or from which LDP can receive targeted hello messages. In the sample topology, the remote neighbor configured for PE 1 is PE 2 with IP address 2.2.2.2, and the remote neighbor configured for PE 2 is PE 1 with IP address 1.1.1.1.

The Ethernet and bridged Ethernet network interfaces, ATM core-facing interfaces, VPLS virtual core interfaces, and MPLS LSPs play the same role in a VPLS topology with LDP signaling as they do in a VPLS topology with BGP signaling. For more information about these components, see Topology Overview of VPLS with BGP Signaling.

Configuration on PE 1 (Local PE Router)

Use the following commands on the local PE router (PE 1) to configure the VPLS topology shown in Figure 1.

! Configure VPLS instance vplsA.host1(config)#bridge vplsA vpls transport-virtual-router default !! Configure VPLS instance vplsB.host1(config)#bridge vplsB vpls transport-virtual-router default !! Configure Fast Ethernet interface 2/1 between PE 1 and CE 1, ! and assign it to vplsA as a trunk interface.host1(config)#interface fastEthernet 2/1 host1(config-if)#bridge-group vplsA subscriber-trunk host1(config-if)#exit !! Configure bridged Ethernet interface 6/0.12 between PE 1 and CE 2, ! and assign it to vplsB as a trunk interface.host1(config)#interface atm 6/0.12 point-to-point host1(config-subif)#atm pvc 12 0 12 aal5snap 0 0 0 host1(config-subif)#encapsulation bridge1483 mac-address 0090.1a40.9991 host1(config-subif)#bridge-group vplsB subscriber-trunk host1(config-if)#exit !! Configure LDP signaling for vplsA.host1(config)#mpls ldp vpls vplsA vpls-id 1 host1(config)#mpls ldp vpls vplsA neighbor 2.2.2.2 ! Configure LDP signaling for vplsB.host1(config)#mpls ldp vpls vplsB vpls-id 2 host1(config)#mpls ldp vpls vplsB neighbor 2.2.2.2 !! Configure a loopback interface on PE 1 and assign it an IP address.host1(config)#interface loopback 0 host1(config-if)#ip address 1.1.1.1 255.255.255.255 host1(config-if)#exit !! Assign the router ID for PE 1 using the IP address of the loopback interface.host1(config)#ip router-id 1.1.1.1 !! Configure ATM core-facing interface 6/0.10 between PE 1 and the P router,! and assign it an IP address.host1(config)#interface atm 6/0.10 point-to-point host1(config-subif)#atm pvc 10 0 10 aal5snap 0 0 0 host1(config-subif)#ip address 10.10.10.1 255.255.255.0 !! Enable MPLS, LDP, and topology-driven LSPs on the core-facing interface.host1(config-subif)#mpls host1(config-subif)#mpls ldp host1(config-subif)#exit !! Configure OSPF routing in the core MPLS network.host1(config)#router ospf 1 host1(config-router)#network 1.1.1.1 0.0.0.0 area 0.0.0.0 host1(config-router)#network 10.10.10.0 0.0.0.255 area 0.0.0.0 host1(config-router)#exit

Configuration on PE 2 (Remote PE Router)

Use the following commands on the remote PE router (PE 2) to configure the VPLS topology shown in Figure 1.

! Configure VPLS instance vplsA.host2(config)#bridge vplsA vpls transport-virtual-router default !! Configure VPLS instance vplsB.host2(config)#bridge vplsB vpls transport-virtual-router default !! Configure Fast Ethernet interface 2/5 between PE 2 and CE 3, ! and assign it to vplsA as a trunk interface.host2(config)#interface fastEthernet 2/5 host2(config-if)#bridge-group vplsA subscriber-trunk host2(config-if)#exit !! Configure bridged Ethernet interface 6/0.21 between PE 2 and CE 4, ! and assign it to vplsB as a trunk interface.host2(config)#interface atm 6/0.21 point-to-point host2(config-subif)#atm pvc 21 0 21 aal5snap 0 0 0 host2(config-subif)#encapsulation bridge1483 mac-address 0090.1a40.9992 host2(config-subif)#bridge-group vplsB subscriber-trunk host2(config-if)#exit !! Configure LDP signaling for vplsA.host2(config)#mpls ldp vpls vplsA vpls-id 1 host2(config)#mpls ldp vpls vplsA neighbor 1.1.1.1 !! Configure LDP signaling for vplsB.host2(config)#mpls ldp vpls vplsB vpls-id 2 host2(config)#mpls ldp vpls vplsB neighbor 1.1.1.1 !! Configure a loopback interface on PE 2 and assign it an IP address.host2(config)#interface loopback 0 host2(config-if)#ip address 2.2.2.2 255.255.255.255 host2(config-if)#exit !! Assign the router ID for PE 2 using the IP address of the loopback interface.host2(config)#ip router-id 2.2.2.2 !! Configure ATM core-facing interface 6/1.20 between PE 2 and the P router,! and assign it an IP address.host2(config)#interface atm 6/1.20 point-to-point host2(config-subif)#atm pvc 20 0 20 aal5snap 0 0 0 host2(config-subif)#ip address 20.20.20.2 255.255.255.0 !! Enable MPLS, LDP, and topology-driven LSPs on the core-facing interface.host2(config-subif)#mpls host2(config-subif)#mpls ldp host2(config-subif)#exit !! Configure OSPF routing in the core MPLS network.host2(config)#router ospf 1 host2(config-router)#network 2.2.2.2 0.0.0.0 area 0.0.0.0 host2(config-router)#network 20.20.20.0 0.0.0.255 area 0.0.0.0 host2(config-router)#exit

Published: 2012-07-02

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out