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

Configuration Tasks for VPLS with BGP Signaling

To configure VPLS with BGP 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. Configure a loopback interface and assign a router ID that uses the IP address of the loopback interface.
6. Configure MPLS label-switched paths (LSPs) to connect local and remote VE routers.
7. Set up BGP signaling on the autonomous system configured to signal reachability for this VPLS instance.

The following sections describe how to perform each of these tasks. See VPLS Configuration Example with BGP 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 with BGP Signaling

You must configure a VPLS instance for each VPLS domain in which the router participates. From a configuration standpoint, a VPLS instance is simply a new or existing bridge group that you configure with additional VPLS attributes.

Table 48 lists the commands that you use to configure a basic VPLS instance, as described in this section. For more information about the syntax of each command, see the JUNOSe Command Reference Guide A to M.

Table 48: Commands to Configure Basic VPLS Instances 

bridge vpls rd	bridge vpls site-range
bridge vpls route-target	bridge vpls transport-virtual-routers
bridge vpls site-name site-id	–

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

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

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

NOTE: To configure a VPLS instance, you must issue the bridge vpls transport-virtual-router command before you issue any of the other bridge vpls commands in this procedure. If the bridge vpls transport-virtual-router command is not issued first, the other bridge vpls commands fail.

2. Specify the maximum number of customer sites that can participate in the VPLS domain represented by the VPLS instance. (By default, a VPLS domain must consist of at least one site.)
3. Specify a name and unique identifier for the customer site that belongs to the VPLS instance.

The site ID value must be greater than zero and be unique across the VPLS domain.

4. Specify the unique, two-part route distinguisher (RD) for the VPLS instance.

Certain rules apply when you configure the route distinguisher for a VPLS instance. For more information, see bridge vpls rd.

In the example that follows, the first number in the route distinguisher (100) is the number of the AS. The second number in the route distinguisher (11) uniquely identifies the VPLS instance within the AS.

5. Create or add a route target to the import and export lists of VPN extended communities for this VPLS instance.

The VE router uses the lists of VPN extended communities to determine which routes are imported by this VPLS instance.

In the following example, the first number in the route target (100) is the number of the AS in which the extended community resides. The second number in the route target (1) uniquely identifies the extended community. This example uses the both keyword to add the route target to both the import list and the export list for this VPLS instance.

! Configure a VPLS instance named customer1.

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

host1(config)#bridge customer1 vpls site-range 15

host1(config)#bridge customer1 vpls site-name westford site-id 1

host1(config)#bridge customer1 vpls rd 100:11

host1(config)#bridge customer1 vpls route-target both 100:1

bridge vpls rd

• Use to specify a unique two-part route distinguisher to identify a VPLS instance that uses BGP signaling.
• Specify the route distinguisher in the format number1:number2, where:

• number1—An AS number or an IP address
• number2—A unique integer that is 32 bits if number1 is an AS number, or 16 bits if number1 is an IP address

• After you set the route distinguisher for a VPLS instance, you cannot change it for that VPLS instance. To change the route distinguisher, you must either remove the transport virtual router configuration from the VPLS instance or delete the VPLS instance from the router. You can then reconfigure the VPLS instance with a new route distinguisher.
• Multiple VPLS instances that use the same transport virtual router cannot have the same route distinguisher. Conversely, multiple VPLS instances that use different transport virtual routers can have the same route distinguisher.

For example, the following commands configure the transport virtual router for each of three VPLS instances: vplsA, vplsB, and vplsC. The transport virtual router for both vplsA and vplsC is vr1, and the transport virtual router for vplsB is vr2.

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

host1(config)#bridge vplsB vpls transport-virtual-router vr2

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

Because vplsA and vplsC use the same transport virtual router, vr1, you cannot assign them the same route distinguisher. Consequently, the following operation fails, and the router displays an error message.

host1(config)#bridge vplsA vpls rd 1.1.1.1:10

host1(config)#bridge vplsC vpls rd 1.1.1.1:10

% Unable to set VPLS route distinguisher (can't re-use the route-distinguisher)

However, both vplsA and vplsB can use the same route distinguisher because their transport virtual routers are different. Consequently, the following commands are valid.

host1(config)#bridge vplsA vpls rd 1.1.1.1:10

host1(config)#bridge vplsB vpls rd 1.1.1.1:10

• Example

host1(config)#bridge vplsA vpls rd 100:20

• Because you cannot change or remove the route distinguisher for a VPLS instance after you set it, issuing the no version fails and causes the router to display the following error message:

host1(config)#no bridge vplsB vpls rd

% Unable to set VPLS route distinguisher (can't re-use the route-distinguisher)

• Because you cannot change or remove the route distinguisher for a VPLS instance after you set it, issuing the no version fails, and causes the router to display an error message.

bridge vpls route-target

• Use to create or add a route target to the import list, to the export list, or to both the import and export lists of VPN extended communities for a VPLS instance that uses BGP signaling.
• The VE router uses the lists of VPN extended communities to determine which routes are imported into the BGP address family for the specified VPLS instance. A route is imported when both of the following conditions are met:

• An update message with a route-target export list advertises a route.
• That list contains at least one route target that matches a route target in the VPLS instance's route-target import list.

• To add the route target to both the VPLS instance's import list and export list of VPN extended communities, use the both keyword. This is the recommended setting for a VPLS instance.
• To add the route target only to the VPLS instance's import list of VPN extended communities, use the import keyword.
• To add the route target only to the VPLS instance's export list of VPN extended communities, use the export keyword.
• To identify the extended community, specify the route target in the format number1:number2, where:

• number1—An AS number or an IP address
• number2—A unique integer that is 32 bits if number1 is an AS number, or 16 bits if number1 is an IP address

• Example

host1(config)#bridge vplsA vpls route-target import 100:1

• Use the no version to remove a route target from the specified VPN extended communities list.

bridge vpls site-name site-id

• Use to configure a site name and a unique site identifier for a VPLS instance that uses BGP signaling.
• You must specify both of the following:

• A site name of up to 128 alphanumeric characters
• A site identifier that is an unsigned 16-bit integer greater than zero; the site identifier must be unique across the VPLS domain associated with this VPLS instance

• Example

host1(config)#bridge vplsA vpls site-name newyork site-id 5

• Use the no version to remove the site name and the site identifier from the VPLS instance.

bridge vpls site-range

• Use to configure the maximum number of customer sites that can participate in the specified VPLS domain that uses BGP signaling, in the range 1–65534.
• A VPLS domain must consist of at least one site.
• Example

host1(config)#bridge vplsA vpls site-range 10

• Use the no version to restore the default site range value, 1.

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 BGP 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.
• You must issue the bridge vpls transport-virtual-router command before you issue any other bridge vpls commands to configure VPLS attributes. If the bridge vpls transport-virtual-router command is not issued first, the other bridge vpls commands fail.
• Example

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

• Use the no version to remove the VPLS instance from the router and to clear any attributes for the deleted VPLS instance configured with the bridge vpls rd, bridge vpls route-target, bridge vpls site-name site-id, and bridge vpls site-range commands.

Configuring Optional Attributes for VPLS Instances

After you create a basic VPLS instance, you can configure one or more optional attributes to manage the MAC address entries in the VPLS instance's forwarding table, or to enable SNMP link status processing. To configure these attributes, you use the same transparent bridging commands that you use to configure bridge groups that do not function as VPLS instances.

Table 49 lists the optional attributes and associated commands that you can configure for VPLS instances. For more information about using these commands, see Configuring Optional Bridge Group Attributes in JUNOSe Link Layer Configuration Guide, Chapter 10, Configuring Transparent Bridging.

Table 49: Commands to Configure Optional Attributes for VPLS Instances 

Attribute	Command
Enable or disable the VPLS instance's ability to acquire dynamically learned MAC addresses	bridge acquire
Enable or disable the VPLS instance's ability to filter (forward or discard) frames with a particular MAC source or destination address	bridge address
Set the aging time of a dynamic (learned) entry in the VPLS instance's forwarding table	bridge aging-time
Set the maximum number of dynamic MAC addresses that a VPLS instance can learn	bridge learn
Enable SNMP link status processing for the VPLS instance	bridge snmp-trap link-status

bridge acquire

• Use to configure a VPLS instance to acquire dynamically learned MAC addresses.
• Example

host1(config)#bridge vplsB acquire

• Use the no version to prevent the VPLS instance from acquiring dynamically learned MAC addresses and to limit forwarding only to those nodes that have a statically configured address entry in the forwarding table.

bridge address

• Use to enable a VPLS instance to filter (forward or discard) frames based on a specific MAC address, and to add static (nonlearned) address entries to the forwarding table.
• You cannot create a static MAC address entry to forward to the VPLS virtual core interface.
• Example 1—Forwards frames destined for the node with MAC address 0090.1a40.4c7c out the specified Gigabit Ethernet interface

host1(config)#bridge vplsA address 0090.1a40.4c7c forward 

gigabitEthernet 3/0.1

• Example 2—Drops frames sent from or destined for the node with MAC address 1011.22b2.333c

host1(config)#bridge vplsB address 1011.22b2.333c discard

• Use the no version to remove the static MAC address entry from the forwarding table.

bridge aging-time

• Use to set the length of time, in the range 1–1000000 seconds, that a dynamic (learned) MAC address entry can remain in the forwarding table of the specified VPLS instance before expiring.
• Example

host1(config)#bridge vplsB aging-time 1000

• Use the no version to restore the default aging time, 300 seconds.

bridge learn

• Use to set the maximum number of dynamic MAC address entries that the specified VPLS instance can learn, in the range 0–64000.
• Example

host1(config)#bridge vplsB learn 2500

• Use the no version to restore the default value, 0 learned addresses. This default implies that there is no maximum number of learned entries for an individual VPLS instance; that is, an individual VPLS instance can learn an unlimited number of MAC addresses, up to the maximum number that the router supports.

bridge snmp-trap link-status

• Use to enable SNMP link status processing for all network interfaces associated with the specified VPLS instance.
• Example

host1(config)#bridge vplsB snmp-trap link-status

• Use the no version to disable SNMP link status processing for all network interfaces associated with the VPLS instance.

Configuring VPLS Network Interfaces

You must configure one of the following types of Ethernet or bridged Ethernet network interfaces to transmit packets between the VE router and each CE device to which the VE is connected:

• Bridged Ethernet over ATM 1483 subinterfaces
• Fast Ethernet
• Gigabit Ethernet
• 10-Gigabit Ethernet
• VLAN and S-VLAN subinterfaces over bridged Ethernet, Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interfaces

To configure a network interface for a VPLS instance:

1. From Global Configuration mode, select the interface that you want to assign to the VPLS instance.
2. From Interface Configuration mode or Subinterface Configuration mode, issue the bridge-group command to assign the interface to the specified VPLS instance.

Issuing this command with no optional keywords configures the network interface as a subscriber (client) interface by default.

3. (Optional) Configure one or more the following optional attributes for the network interface. You must issue a separate bridge-group command for each attribute.

• Configure the interface as a trunk (server) interface. For more information about the differences between a subscriber (client) interface and a trunk (server) interface, see Configuring Subscriber Policies for VPLS Network Interfaces.
• Set the maximum number of MAC addresses that the network interface can learn.
• Enable SNMP link status processing only for the specified network interface in the VPLS instance.

! Configure Gigabit Ethernet 3/0 and assign it to VPLS instance customer1 

! as a trunk interface

host1(config)#interface gigabitEthernet 3/0

host1(config-if)#bridge-group customer1

host1(config-if)#bridge-group customer1 subscriber-trunk

host1(config-if)#bridge-group customer1 learn 100

host1(config-if)#bridge-group customer1 snmp-trap link-status

bridge-group

• Use to assign a network interface to a specified VPLS instance.
• To assign the network interface to the VPLS instance as a subscriber (client) interface, which is the default, use the bridge-group command without any optional keywords.
• To configure the network interface as a trunk (server) interface, use the subscriber-trunk keyword.
• To set the maximum number of MAC addresses that the network interface can learn, use the learn keyword and specify a value in the range 0–64000. A value of 0 indicates that an individual network interface can learn an unlimited number of MAC addresses, up to the maximum number that the router supports.
• To enable SNMP link status processing for the specified network interface, use the snmp-trap link-status keyword.
• Examples

host1(config-subif)#bridge-group vpls1 subscriber-trunk

host1(config-subif)#bridge-group vpls1 learn 500

host1(config-subif)#bridge-group vpls1 snmp-trap link-status

• Use the no version to remove the network interface from the VPLS instance and restore the default value for the interface type (subscriber client), maximum number of learned MAC addresses (0), or SNMP link status processing (disabled).

Configuring Subscriber Policies for VPLS Network Interfaces

The router associates a VPLS network interface, as it does a bridge group interface, with a default subscriber policy that enables intelligent flooding of packets within a VPLS domain. This section describes how subscriber policies work and explains some important considerations when you use subscriber policies for VPLS instances.

Network Interface Types

VPLS instances, like bridge groups, support two types of network interfaces:

• Subscriber (client)—A subscriber (client) interface is downstream from the traffic flow; that is, the traffic flow direction is from the server (trunk) to the client (subscriber). This is the default network interface type for both VPLS instances and bridge groups.
• Trunk (server)—A trunk (server) interface is upstream from the traffic flow; that is, the traffic flow direction is from the client (subscriber) to the server (trunk). To configure a trunk interface, you must specify the subscriber-trunk keyword as part of the bridge-group command. The VPLS virtual core interface always acts as a trunk interface, and cannot be configured as a subscriber interface.

Default Subscriber Policies

Each network interface is associated with a default subscriber policy for that interface type. The subscriber policy is a set of forwarding and filtering rules that defines how the specified interface handles various packet or attribute types, as follows:

• For each packet type listed in Table 50, the subscriber policy specifies whether the network interface permits (forwards) or denies (filters or drops) packets of that type.
• For the relearn attribute, the subscriber policy specifies whether the network interface can relearn a MAC address entry on a different interface from the one initially associated with this entry in the forwarding table. Permit indicates that relearning is allowed; deny indicates that relearning is prohibited.

Table 50 lists the default values for each packet or attribute type defined in the policies for subscriber interfaces and trunk interfaces. The default subscriber policy differs in one way from the default trunk policy: broadcast packets and packets with unknown unicast destination addresses (DAs) are denied in the subscriber policy and permitted in the trunk policy.

Table 50: Default Subscriber Policies for VPLS Network Interfaces 

Packet/Attribute Type	Default Subscriber Policy	Default Trunk Policy
ARP	Permit	Permit
Broadcast	Deny	Permit
IP	Permit	Permit
MPLS	Permit	Permit
Multicast	Permit	Permit
PPPoE	Permit	Permit
Relearn	Permit	Permit
Unicast (user-to-user)	Permit	Permit
Unknown unicast DA	Deny	Permit
Unknown protocol	Permit	Permit

Modifying Subscriber Policies

For a network interface configured as a subscriber (client) interface, you can modify the default subscriber policy to change the default permit or deny value for one or more of the packet or attribute types listed in Table 50.

You cannot, however, change the default trunk policy for a network interface configured as a trunk interface or for the VPLS virtual core interface. Trunk interfaces and the VPLS virtual core interface always use the default trunk policy, which forwards packets of all types and permits relearning.

Table 51 lists the commands that you can use to modify subscriber policies for subscriber (client) interfaces associated with either a VPLS instance or a standard bridge group. For information about using these commands, see Configuring Subscriber Policies in JUNOSe Link Layer Configuration Guide, Chapter 10, Configuring Transparent Bridging.

Table 51: Commands to Configure Subscriber Policies 

arp	pppoe
bridge subscriber-policy	relearn
broadcast	subscriber-policy
ip	unicast
mpls	unknown-destination
multicast	unknown-protocol

Considerations for VPLS Network Interfaces

When you configure network interfaces for a VPLS instance, you must ensure that the subscriber policy in effect for the interface is appropriate for your network configuration.

To ensure that the network interface permits relearning and forwards (permits) packets for all of the protocol types listed in Table 50, be sure to configure the network interface as a trunk (server) interface so that it always uses the default trunk policy. For example, the following commands associate a 10-Gigabit Ethernet interface with a VPLS instance named vplsBoston, and configure the interface as a trunk.

host1(config)#interface tenGigabitEthernet 4/0/1

host1(config-if)#bridge-group vplsBoston subscriber-trunk

If you configure a VPLS network interface as a subscriber (client) interface, use care if you modify the default subscriber policy in effect for that interface. For example, if you use the arp command to change the default value for ARP packets from permit (forward) to deny (filter or drop), make sure you also use the bridge address command to add the appropriate static (nonlearned) ARP entry to the forwarding table. If an ARP entry expires from the forwarding table and the subscriber policy is configured to deny ARP packets, the router cannot properly forward subsequent ARP packets.

Configuring the Loopback Interface and Router ID for BGP Signaling

To establish a BGP session, BGP uses the IP address of the outgoing interface towards the BGP peer as the update source IP address for the TCP connection over which the BGP session runs. Typically, you configure a loopback interface as the update source interface because a loopback interface is inherently stable.

After you configure the loopback interface, you use the ip router-id command to assign a router ID to uniquely identify the router within a BGP AS. 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.3.3.3 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.3.3.3

interface loopback

• Use to access and configure 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.
• 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 an AS.
• Example

host1(config)#ip router-id 10.3.3.3

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

Configuring MPLS LSPs

As part of a VPLS configuration, you must create MPLS label-switched paths (LSPs) to connect the local VE router and the remote VE router.

This section explains one way to create a basic MPLS configuration using the mpls and mpls ldp commands. For complete information about configuring MPLS LSPs, see Chapter 2, Configuring MPLS.

To configure MPLS LSPs on the VE router:

1. Enable MPLS on the virtual router.
2. Configure the core-facing interface on which you want to enable MPLS, Label Distribution Protocol (LDP), and topology-driven LSPs.
3. Enable MPLS on the core-facing interface.
4. Enable LDP and topology-driven LSPs on the core-facing interface.

! Enable MPLS on the default virtual router.

host1(config)#mpls

! Configure a core-facing interface between the VE and P routers, 

! and assign it an IP address.

host1(config)#interface atm 5/0.100

host1(config-subif)#atm pvc 100 1 100 aal5snap 0 0 0

host1(config-subif)#ip address 192.168.5.5 255.255.255.0

! Enable MPLS on the core-facing interface.

host1(config-subif)#mpls

! Enable LDP and topology-driven LSPs on the core-facing interface.

host1(config-subif)#mpls ldp

host1(config-subif)#exit

mpls

• Use from Global Configuration mode to enable MPLS on a virtual router.
• Use from Interface Configuration mode or Subinterface Configuration mode to create an MPLS major interface stacked on the specified layer 2 interface, and to automatically enable MPLS on the current virtual router if it has not already been enabled.
• You cannot enable MPLS on a loopback interface.
• Example

host1(config-if)#mpls

• Use the no mpls version from Global Configuration mode to remove MPLS from the virtual router and delete the MPLS configuration.
• Use the no mpls version from Interface Configuration mode to remove the MPLS major interface.

mpls ldp

• Use to enable LDP and topology-driven LSPs on an interface, using the default values (that is, using an implicit default profile).
• You cannot enable LDP and topology-driven LSPs on a loopback interface.
• Example

host1(config-if)#mpls ldp

• Use the no version to disable LDP on an interface.

Configuring BGP Signaling

This section describes one way to configure BGP signaling for VPLS, but does not provide complete details about configuring BGP and BGP/MPLS VPNs. See Chapter 1, Configuring BGP Routing for information about configuring BGP, and Chapter 3, Configuring BGP-MPLS Applications for information about configuring BGP/MPLS VPNs.

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

Table 52: Commands to Configure BGP Signaling for VPLS 

address-family l2vpn	neighbor next-hop-self
address-family vpls	neighbor remote-as
exit-address-family	neighbor send-community
ip router-id	neighbor update-source
neighbor activate	router bgp

To configure BGP signaling for VPLS on the VE router:

1. Enable the BGP routing process in the specified AS.

The AS number identifies the VE router to other BGP routers.

2. Configure the VE-to-VE BGP session. Use neighbor commands to specify the peers to which BGP advertises routes.

In the example that follows this procedure, the BGP peer is a VE router with IP address 10.4.4.4.

For more information about using neighbor commands to configure BGP, see Chapter 1, Configuring BGP Routing and Chapter 3, Configuring BGP-MPLS Applications.

3. Create the L2VPN address family to configure the router to exchange layer 2 NLRI for all VPLS instances.

Optionally, you can use the signaling keyword for the L2VPN address family to specify BGP signaling of L2VPN reachability information. Currently, you can omit the signaling keyword with no adverse effects.

4. Activate the VE-to-VE session in the L2VPN address family. Use neighbor commands to configure additional address family parameters for the session.

For more information about using neighbor commands to configure BGP, see Chapter 1, Configuring BGP Routing and Chapter 3, Configuring BGP-MPLS Applications.

5. Create the VPLS address family to configure the router to exchange layer 2 NLRI for each VPLS instance configured on the router.

You must issue the address-family vpls command separately for each VPLS instance configured on the router.

In the following example, two VPLS instances named customer1 and customer2 are configured on the VE router.

After you configure MPLS LSPs and BGP signaling, the router automatically generates a VPLS virtual core interface for each VPLS instance. The VPLS virtual core interface represents all of the MPLS tunnels from the router to the remote VE device.

! Enable BGP in AS 100.

host1(config)#router bgp 100

! Configure the VE-to-VE BGP session.

host1(config-router)#neighbor 10.4.4.4 remote-as 100

host1(config-router)#neighbor 10.4.4.4 update-source loopback 0

host1(config-router)#neighbor 10.4.4.4 next-hop-self

! Create the L2VPN address family with BGP signaling for all VPLS instances.

host1(config-router)#address-family l2vpn signaling

! Activate the VE-to-VE session in the L2VPN address family.

host1(config-router-af)#neighbor 10.4.4.4 activate

host1(config-router-af)#neighbor 10.4.4.4 next-hop-self

host1(config-router-af)#exit-address-family

! Create the VPLS address family for VPLS instance customer1.

host1(config-router)#address-family vpls customer1

host1(config-router-af)#exit-address-family

! Create the VPLS address family for VPLS instance customer2.

host1(config-router)#address-family vpls customer2

host1(config-router-af)#exit-address-family

! Return to Global Configuration mode.

host1(config-router)#exit

address-family l2vpn

• Use to create the L2VPN address family, which enables you to configure the router to exchange layer 2 NLRI for all VPLS instances.
• Issuing this command accesses Address Family Configuration mode.
• To specify BGP signaling of L2VPN reachability information, use the optional signaling keyword. Currently, you can omit the signaling keyword with no adverse effects.
• This command takes effect immediately.
• Example

host1(config-router)#address-family l2vpn signaling

• Use the no version to remove the L2VPN address family for all VPLS instances.

address-family vpls

• Use to create the VPLS address family, which enables you to configure the router to exchange layer 2 NLRI only for the specified VPLS instance.
• Issuing this command accesses Address Family Configuration mode.
• This command takes effect immediately.
• Example

host1(config-router)#address-family vpls customer1

• Use the no version to remove the VPLS address family for the specified VPLS instance.

exit-address-family

• Use to exit Address Family Configuration mode and access Router Configuration mode.
• Example

host1(config-router-af)#exit-address-family

• There is no no version.

neighbor activate

• Use to specify neighbors that exchange routes from within the current address family.
• This command takes effect immediately.
• Example

host1(config-router)#neighbor 10.4.4.4 activate

• Use the default version to remove the explicit configuration from the peer or peer group and to reestablish inheritance of the feature configuration.
• Use the no version to specify that the router not exchange routes of the current address family with the peer.

neighbor next-hop-self

• Use to force the BGP speaker to report itself as the next hop for an advertised route that it learned from a neighbor.
• Example

host1(config-router)#neighbor 10.4.4.4 next-hop-self

• Use the default version to remove the explicit configuration from the peer or peer group and to reestablish inheritance of the feature configuration.
• Use the no version to disable this feature, thereby enabling next-hop processing of BGP updates.

neighbor remote-as

• Use to add an entry to the BGP neighbor table.
• Specifying a neighbor with an AS number that matches the AS number specified in the router bgp command identifies the neighbor as internal to the local AS. Otherwise, the neighbor is considered external.
• This command takes effect immediately.
• Example

host1(config-router)#neighbor 10.4.4.4 remote-as 100

• Use the no version to remove an entry from the BGP neighbor table.

neighbor update-source

• Use to allow the BGP session to use the IP address of a specific operational interface as the update source address for TCP connections.
• This command takes effect immediately and automatically bounces the BGP session.
• If you specify an interface in this command and later remove the interface, this command is also removed from the router configuration.
• Example

host1(config-router)#neighbor 10.4.4.4 update-source loopback 0

• Use the no version to restore the interface assignment to the closest interface.

router bgp

• Use to enable the BGP routing protocol on the VE router and to specify the local AS; that is, the AS to which this BGP speaker belongs.
• Issuing this command accesses Router Configuration mode.
• All subsequent BGP configuration commands are placed within the context of this router and AS; you can have only a single BGP instance per virtual router.
• Specify only one BGP AS per virtual router.
• Example

host1(config)#router bgp 100

• Use the no version to remove the BGP process.

The following sections describe how to perform each of these tasks. See VPLS Configuration Example with BGP 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.