JUNOSe 9.0.x BGP and MPLS Configuration Guide > Configuring VPLS > Configuration Tasks for VPLS with LDP Signaling

Configuration Tasks for VPLS with LDP Signaling

To configure VPLS with LDP signaling on the VE router:

1. Configure a single instance of VPLS, known as a VPLS instance, on the VE router for each VPLS domain in which the router participates.
2. (Optional) Configure optional attributes for the VPLS instance.
3. Configure network interfaces to connect the VE router to each CE device.
4. (Optional) Configure nondefault subscriber policies for the VPLS network interface.
5. Set up LDP signaling for this VPLS instance to establish targeted sessions to the remote VE neighbors configured at the edge of the MPLS core network.
6. Configure a loopback interface to be associated with the targeted LDP neighbor, and assign a router ID that uses the IP address of the loopback interface.
7. Configure MPLS LSPs to connect local and remote VE routers.
8. Configure an interior gateway protocol (IGP), such as Open Shortest Path First (OSPF) or Intermediate System–to–Intermediate System (IS-IS), to enable routing within the core network.

The following sections describe how to perform each of these tasks. See VPLS Configuration Example with LDP Signaling for a detailed sample configuration.

NOTE: For information about the maximum values that the router supports for VPLS configuration, see JUNOSe Release Notes, Appendix A, System Maximums.

Configuring VPLS Instances for LDP Signaling

As is the case with BGP signaling, when you use LDP signaling you must configure a VPLS instance for each VPLS domain in which the router participates. Unlike BGP signaling, however, configuring a VPLS instance for LDP signaling requires only that you specify the transport virtual router for this instance by issuing the bridge vpls transport-virtual-router command.

To configure a basic VPLS instance with LDP signaling on the VE router:

• From Global Configuration mode, create the VPLS instance by specifying the transport virtual router for this instance.

! Configure a VPLS instance named customer3.

host1(config)#bridge customer3 vpls transport-virtual-router vr1

If the bridge group you specify (customer3 in this example) already exists on the router, issuing this command causes the bridge group to become a VPLS instance.

bridge vpls transport-virtual-router

• Use to configure the transport virtual router for a VPLS instance. The transport virtual router specifies the name of the virtual router on which the LDP instance that signals reachability for this VPLS instance is configured.
• Issuing this command creates a new VPLS instance or causes an existing bridge group configured on the router to become a VPLS instance.
• Example

host1(config)#bridge vplsC vpls transport-virtual-router vr1

• Use the no version to remove the VPLS instance from the router and to clear any attributes configured for the deleted VPLS instance.

Configuring Optional Attributes for VPLS Instances

After you create a basic VPLS instance for LDP signaling, you can configure one or more optional attributes for this instance that provide transparent bridging functions such as managing MAC address entries and enabling SNMP link status processing. To configure these attributes, you use the same transparent bridging commands that you use to configure VPLS instances with BGP signaling.

For instructions, see Configuring Optional Attributes for VPLS Instances.

Configuring VPLS Network Interfaces

VPLS instances with LDP signaling, like VPLS instances with BGP signaling, use Ethernet or bridged Ethernet network interfaces to transmit packets between the VE router and each CE device to which the VE is connected. To configure network interfaces for LDP signaling, you use the same commands and procedure that you use to configure network interfaces for BGP signaling.

For instructions, see Configuring VPLS Network Interfaces.

Configuring Subscriber Policies for VPLS Network Interfaces

Network interfaces for VPLS instances with LDP signaling, like network interfaces for VPLS instances with BGP signaling, are associated with two default subscriber policies, subscriber and trunk, to enable intelligent flooding of packets within a VPLS domain. To configure and use nondefault subscriber policies for LDP signaling, you use the same commands and procedures that you use to configure nondefault subscriber policies for BGP signaling.

For instructions, see Configuring Subscriber Policies for VPLS Network Interfaces.

Configuring LDP Signaling

LDP signaling establishes targeted sessions to the remote VEs configured at the edge of the service provider's MPLS core network. To enable LDP to establish these targeted sessions, you issue the mpls ldp vpls-id command to configure a VPLS identifier for the VPLS instance, and the mpls ldp vpls neighbor command to configure a list of neighbor (peer) addresses to which LDP can send or from which LDP can receive targeted hello messages.

This section describes how to configure LDP signaling for a VPLS network, but does not provide complete details about configuring LDP on E-series routers. For more information about LDP, see Chapter 2, Configuring MPLS.

Table 53 lists the commands discussed in this section to configure LDP signaling for VPLS. For more information about the syntax of each command, see the JUNOSe Command Reference Guide A to M.

Table 53: Commands to Configure LDP Signaling for VPLS 

mpls ldp vpls neighbor

mpls ldp vpls vpls-id

To configure LDP signaling for VPLS on the VE router:

1. Configure the VPLS identifier, which is a globally unique identifier for each VPLS domain.
2. Configure a list of neighbor (peer) addresses to which LDP can send or from which LDP can receive targeted hello messages.

The following example configures LDP signaling for two VPLS instances named customer3 and customer4 on the VE router.

! Enable LDP signaling for customer3.

host1(config)#mpls ldp vpls customer3 vpls-id 3

host1(config)#mpls ldp vpls customer3 neighbor 10.3.3.3

! Enable LDP signaling for customer4.

host1(config)#mpls ldp vpls customer4 vpls-id 4

host1(config)#mpls ldp vpls customer3 neighbor 10.4.4.4

mpls ldp vpls neighbor

• Use to enable LDP signaling for a VPLS instance by configuring the remote VE device address of a neighbor in the VPLS domain in which this instance participates.
• If either or both LDP or MPLS are not configured on the current virtual router, issuing the mpls ldp vpls neighbor command creates the LDP and MPLS configurations.
• Example

host1(config)#mpls ldp vpls vplsC neighbor 10.1.1.1

• Use the no version to delete the neighbor from the VPLS domain.

mpls ldp vpls vpls-id

• Use to configure the VPLS identifier of a VPLS instance that uses LDP as the signaling protocol.
• The VPLS identifier is a globally unique identifier for the VPLS domain, in the range 1–4294967295, that must meet the following requirements:

• All VEs that participate in the same VPLS domain must use the same VPLS identifier.
• The VPLS identifier configured for a VPLS instance must not be the same as the PWid for Martini configurations for Ethernet layer 2 services over MPLS.

• Example

host1(config)#mpls ldp vpls vplsC vpls-id 1

• Use the no version to delete the VPLS identifier from the VPLS instance.

Configuring the Loopback Interface and Router ID for LDP Signaling

VPLS with LDP signaling, like VPLS with BGP signaling, requires configuration of a loopback interface. You can use a loopback interface to provide a stable IP address that can minimize the impact if a physical interface goes down. LDP uses the loopback interface as the associated interface for the targeted neighbors configured with the mpls ldp vpls neighbor command, as described in Configuring LDP Signaling.

After you configure the loopback interface, you use the ip router-id command to assign a router ID to uniquely identify the router within the VPLS domain. The router ID is the IP address of the loopback interface.

To configure the loopback interface and router ID on the VE router:

1. Configure a loopback interface on the VE router and assign it an IP address.
2. Assign the router ID using the IP address you configured for the loopback interface.

! Configure a loopback interface on the VE and assign it an IP address.

host1(config)#interface loopback 0

host1(config-if)#ip address 10.1.1.1 255.255.255.255

host1(config-if)#exit

! Assign the router ID for the VE using the IP address of the loopback interface.

host1(config)#ip router-id 10.1.1.1

interface loopback

• Use to access and configure a loopback interface.
• LDP uses the loopback interface as the associated interface for the targeted remote neighbors.
• Example

host1(config)#interface loopback 0

host1(config-if)#ip address 10.3.3.3 255.255.255.0

• Use the no version to delete the loopback interface.

ip router-id

• Use to assign a router ID, which is a unique identifier that IP routing protocols use to identify the router within the VPLS domain.
• Example

host1(config)#ip router-id 10.3.3.3

• Use the no version to remove the router ID assignment.

Configuring MPLS LSPs

VPLS with LDP signaling, like VPLS with BGP signaling, requires configuration of MPLS LSPs to connect the local VE router and the remote VE router through the provider (P) router in the MPLS core. To configure MPLS LSPs for LDP signaling, you can use the same commands and procedure that you use to configure MPLS LSPs for BGP signaling.

For instructions, see Configuring MPLS LSPs.

Configuring Routing in the Core Network

After you configure the transparent bridging, LDP, and MPLS components of the VPLS network, you must configure an IGP, such as OSPF or IS-IS, on the VE to set up routing within the core MPLS network.

This section explains one way to configure OSPF to enable routing in the core network. For complete information about configuring and using OSPF, see JUNOSe IP, IPv6, and IGP Configuration Guide, Chapter 5, Configuring OSPF. For complete information about configuring and using IS-IS, see JUNOSe IP, IPv6, and IGP Configuration Guide, Chapter 6, Configuring IS-IS.

Table 54 lists the commands discussed in this section to configure OSPF. For more information about the syntax of each command, see the JUNOSe Command Reference Guide N to Z.

Table 54: Commands to Configure OSPF for a VPLS Network 

network area

router ospf

To configure the VE to set up OSPF routing for the core MPLS network:

1. Create the OSPF routing process.
2. Create the range of IP addresses associated with the routing process and the corresponding OSPF interfaces.
3. Assign an area ID associated with each range of IP addresses.

This example configures an OSPF routing process with process ID 1, and creates two OSPF interfaces in the backbone area (area 0.0.0.0): one using IP address 1.1.1.1, and one using IP address 10.10.10.0. The network area commands also create the two OSPF areas if they do not already exist.

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

network area

• Use to configure a range of OSPFv2 interfaces and their related area.
• If the specified range matches one or more of the IP addresses configured for IP interfaces, one or more corresponding OSPF interfaces are created and placed in the specified area.
• Create address ranges that do not overlap; you can attach only the same range of interfaces to a single area.
• Example—shows the creation of one OSPF interface in the backbone area

host1(config-if)#ip address 2.2.2.1 255.255.0.0

host1(config)#router ospf 2

host1(config-router)#network 2.2.2.0 0.0.0.255 area 0

• Use the no version to delete OSPF interfaces, ranges, and areas.

router ospf

• Use to set a process ID for an OSPF routing process.
• The process ID can be any positive integer in the range 1–65535.
• You must assign a unique ID for each OSPF routing process.
• Example

host1(config)#router ospf 5

• Use the no version to end the designated OSPF routing process.