MPLS L2VPN provides point-to-point and point-to-multipoint connections. This chapter describes only the MPLS L2VPN technologies that provide point-to-point connections. For information about the MPLS L2VPN technologies that provide point-to-multipoint connections, see "Configuring VPLS."

About MPLS L2VPN

MPLS L2VPN is an implementation of Pseudo Wire Emulation Edge-to-Edge (PWE3). It offers Layer 2 VPN services over an MPLS or IP backbone. MPLS L2VPN can transparently transmit Layer 2 data for different data link layer protocols such as Ethernet.

Basic concepts of MPLS L2VPN

CE

A customer edge (CE) is a customer device directly connected to the service provider network.

PE

A provider edge (PE) is a service provider device connected to one or more CEs. It provides VPN access by mapping and forwarding packets between user networks and public tunnels.

AC

An attachment circuit (AC) is a link between a CE and a PE, such as an Ethernet interface or VLAN.

PW

A Pseudowire (PW) is a virtual bidirectional connection between two PEs. An MPLS PW comprises a pair of LSPs in opposite directions.

Public tunnel

A public tunnel is a connection that carries one or more PWs across the MPLS or IP backbone. It can be an LSP tunnel, an MPLS TE tunnel, or a GRE tunnel.

Cross-connect

A cross-connect connects two physical or virtual circuits such as ACs and PWs. It switches packets between the two physical or virtual circuits. Cross-connects include AC to AC cross-connect, AC to PW cross-connect, and PW to PW cross-connect.

Site ID

A site ID uniquely identifies a site in a VPN. Sites in different VPNs can have the same site ID.

RD

A route distinguisher (RD) is added before a site ID to distinguish the sites that have the same site ID but reside in different VPNs. An RD and a site ID uniquely identify a VPN site.

Label block

A label block is a set of labels. It includes the following parameters:

· Label base—The LB specifies the initial label value of the label block. A PE automatically selects an LB value that cannot be manually modified.

· Label range—The LR specifies the number of labels that the label block contains. The LB and LR determine the labels contained in the label block. For example, if the LB is 1000 and the LR is 5, the label block contains labels 1000 through 1004.

· Label-block offset—The LO specifies the offset of a label block. If the existing label block becomes insufficient as the VPN sites increase, you can add a new label block to enlarge the label range. A PE uses an LO to identify the position of the new label block. The LO value of a label block is the sum of the LRs of all previously assigned label blocks. For example, if the LR and LO of the first label block are 10 and 0, the LO of the second label block is 10. If the LR of the second label block is 20, the LO of the third label block is 30.

A label block with LB, LO, and LR as 1000, 10, and 5, respectively, is represented as 1000/10/5.

For example, a VPN has 10 sites, and a PE assigns the first label block LB1/0/10 to the VPN. When another 15 sites are added, the PE keeps the first label block and assigns the second label block LB2/10/15 to extend the network. LB1 and LB2 are the initial label values that are randomly selected by the PE.

Route target

PEs use the BGP route target attribute (also called VPN target attribute) to manage BGP L2VPN information advertisement. PEs support the following types of route target attributes:

· Export target attribute—When a PE sends L2VPN information to the peer PE in a BGP update message, it sets the route target attribute in the update message to an export target. L2VPN information includes the site ID, RD, and label block.

· Import target attribute—When a PE receives an update message from the peer PE, it checks the route target attribute in the update message. If the route target value matches an import target, the PE accepts the L2VPN information in the update message.

Route target attributes determine from which PEs a PE can receive L2VPN information.

MPLS L2VPN network models

MPLS L2VPN network models include the remote connection and local connection models.

As shown in Figure 1, the remote connection model connects two CEs through a PW on an MPLS or IP backbone.

Figure 1 Remote connection model

As shown in Figure 2, the local connection model connects two CEs to the same PE so the CEs can communicate through the PE.

Figure 2 Local connection model

Remote connection establishment

To set up a remote MPLS L2VPN connection:

1. Set up a public tunnel to carry one or more PWs between PEs.

2. Set up a PW to connect customer networks.

3. Set up an AC between a PE and a CE.

4. Bind the AC to the PW.

After the PE receives packets from the AC, it adds the PW label into the packets and sends the packets to the peer PE through the public tunnel.

After the peer PE receives the packets from the public tunnel, it removes the PW label of the packets and forwards the packets to the AC bound to the PW.

Setting up a public tunnel

The public tunnel can be an LSP, MPLS TE, or GRE tunnel.

If multiple public tunnels exist between two PEs, you can configure a tunnel policy to control tunnel selection. For more information about tunnel policies, see "Configuring tunnel policies."

If a PW is established over an LSP or MPLS TE tunnel, packets on the PW have two labels. The outer label is the public LSP or MPLS TE tunnel label that MPLS uses to forward the packet to the peer PE. The inner label is the PW label that the peer PE uses to forward the packet to the destination CE.

Setting up a PW

PWs include static PWs, LDP PWs, BGP PWs, and Circuit Cross Connect (CCC) PWs.

· Static PW establishment

To establish a static PW, configure the peer PE address, and the incoming and outgoing PW labels for the PW on the two PEs. Static PWs consume a small amount of resources but have complex configurations.

· LDP PW establishment

To establish an LDP PW, configure LDP and specify the peer PE address on the two PEs. LDP defines a new FEC type named PW ID FEC for PEs to exchange PW-label bindings. The new FEC type uses a PW ID and a PW data encapsulation type to identify a PW. The PW ID is the ID of the PW between PEs. The PW data encapsulation type specifies the encapsulation type for data transmitted over the PW, such as Ethernet or VLAN. PEs advertise the PW label and PW ID FEC in label mapping messages to create a PW. Dynamic PWs have simple configurations but consume more resources than static PWs.

· BGP PW establishment

To establish BGP PWs, BGP advertises label block information in an extended BGP update to PEs in the same VPN. Each PE uses the received label block information to calculate outgoing labels and uses its own label block to calculate incoming labels. After two PEs complete label calculation, a BGP PW is established between them.

BGP PWs have the following features:

¡ Simplified configuration—There is no need to manually specify peer PEs. A PE automatically find peer PEs after receiving label block information from the peer PEs.

¡ Reduced workload—Label block advertisement enables assigning labels for multiple PWs at one time.

Setting up an AC

Set up an AC by configuring a link layer connection (such as a PPP connection) between a PE and a CE.

An AC can be one of the following types on a PE:

· Layer 3 physical interface—Transparently forwards received packets over the bound PW. The interface can be an Ethernet interface.

· Layer 3 subinterface—Forwards packets received from the corresponding link to the bound PW.

· Ethernet service instance on a Layer 2 Ethernet interface or Layer 2 aggregate interface—Forwards packets that are received on the interface and meet the match criteria of the Ethernet service instance to the bound PW. If the match criterion is VLAN ID, the VLAN is unique on a per interface basis rather than on a global basis.

NOTE:

When VLANs are globally unique, packets with the same VLAN ID are forwarded over the PW bound with that VLAN ID regardless of the receiving interfaces. If VLANs are unique on a per interface basis, packets with the same VLAN ID from different interfaces can be forwarded over different PWs.

Binding the AC to the PW

Bind the Layer 3 physical interface, Layer 3 subinterface, or Ethernet service instance to the PW, so the PE forwards packets between the AC and the PW.

Local connection establishment

To set up a local MPLS L2VPN connection between two CEs:

1. Set up ACs:

Configure the link layer protocol to set up an AC between the PE and each CE. For more information, see "Setting up an AC."

2. Bind the two ACs:

Bind the PE's interfaces connected to the two CEs so the PE can forward packets between CEs.

PW data encapsulation types

MPLS L2VPN transports Layer 2 data of different data link layer protocols through PWs. A PE encapsulates a Layer 2 packet received from an AC according to the PW data encapsulation type.

Relationship between AC types and PW data encapsulation types

The PW data encapsulation type is determined by the link type of the AC, as shown in Table 1.

Table 1 Relationship between AC types and PW data encapsulation types

AC type	PW data encapsulation type
Ethernet	Ethernet
Ethernet	VLAN

Ethernet over MPLS

Ethernet over MPLS uses MPLS L2VPN to connect Ethernets, and delivers Ethernet packets through a PW over the MPLS backbone.

The following PW data encapsulation types are available for Ethernet over MPLS:

· Ethernet—P-tag is not transferred on a PW.

¡ For a packet from a CE:

- If the packet contains a P-tag, the PE removes the P-tag, and adds a PW label and an outer tag into the packet before forwarding it.

- If the packet contains no P-tag, the PE directly adds a PW label and an outer tag into the packet before forwarding it.

¡ For a packet to a CE:

- If the access mode is configured as VLAN by using the ac interface command, the PE adds a P-tag into the packet before sending it to the CE.

- If the access mode is configured as Ethernet by using the ac interface command, the PE directly sends the packet to the CE.

You cannot rewrite or remove existing tags.

· VLAN—Packets transmitted over a PW must carry a P-tag.

¡ For a packet from a CE:

- If the peer PE does not require the ingress to rewrite the P-tag, the PE keeps the P-tag unchanged for the packet, and then encapsulates the packet. If the packet contains no P-tag, the PE adds a null label (the label value is 0) into the packet, and then encapsulates the packet.

- If the peer PE requires the ingress to rewrite the P-tag, the PE changes the P-tag to the expected VLAN tag (the tag value might be 0), and then adds a PW label and an outer tag into the packet. If the packet contains no P-tag, the PE adds a VLAN tag expected by the peer PE (the tag value might be 0), and then adds a PW label and an outer tag into the packet.

¡ For a packet to a CE:

- If the access mode is configured as VLAN by using the ac interface command, the PE rewrites or retains the P-tag before forwarding the packet.

- If the access mode is configured as Ethernet by using the ac interface command, the PE removes the P-tag before forwarding the packet.

Ethernet over MPLS supports the following modes:

· Port mode—A Layer 3 Ethernet interface is bound to a PW. Packets received from the Layer 3 Ethernet interface are forwarded through the bound PW. The default PW data encapsulation type for port mode is Ethernet.

Figure 3 Packet encapsulation in port mode

· VLAN mode—A Layer 3 Ethernet subinterface is bound to a PW. Packets received from the VLAN are forwarded through the bound PW. The peer PE can modify the VLAN tag as needed. The default PW data encapsulation type for VLAN mode is VLAN.

Control word

The control word field is between the MPLS label stack and the Layer 2 data. It carries control information for the Layer 2 frame, for example, the sequence number.

The control word feature has the following functions:

· Avoids fragment disorder. In multipath forwarding, fragments received might be disordered. The control word feature reorders the fragments according to the sequence number carried in the control word field.

· Transfers specific Layer 2 frame flags, such as the BECN bit.

· Identifies the original payload length for packets that include padding.

For some PW data encapsulation types, packets on the PW always carry the control word field, and the control word feature cannot be disabled.

When the PW data encapsulation type is Ethernet or VLAN, the control word field is optional. You can configure whether to carry the control word field in packets sent on the PW. If you enable the control word feature on both PEs, packets transmitted on the PW carry the control word field. Otherwise, the packets do not carry the control word field.

Flow label

Packets carrying different types of traffic might be transmitted through the same PW and encapsulated with the same PW label. The P devices forward the traffic flows of a PW over the same path even if Equal Cost Multiple Paths (ECMPs) exist.

The L2VPN flow label feature can enable a P device to perform load sharing on packets based on the flow types.

After you configure this feature, the P and PE devices process packets as follows:

· When the ingress PE encapsulates a packet, it adds a flow label before it adds a PW label, as shown in Figure 4.

The ingress PE adds different flow labels for packets of different traffic types.

· The P devices perform load sharing on packets based on the flow labels.

· The egress PE removes both the PW and flow labels from a packet before forwarding the packet.

Figure 4 L2VPN flow label feature

You can enable the flow label sending, receiving, or both sending and receiving capabilities on a PE.

· The sending capability enables a PE to send packets with flow labels. The PE adds a flow label before it adds a PW label to a packet during PW encapsulation.

· The receiving capability enables a PE to identify the flow label in a received packet and removes the flow label before forwarding the packet.

For two PE to successfully negotiate the flow label capabilities, make sure one end has the sending capability and the other end has the receiving capability.

For static PWs, you must manually configure flow label capabilities for the local and remote PEs. For dynamic PWs, you can configure the local and remote PEs to negotiate the flow label capabilities or manually configure flow label capabilities for the PEs.

PW redundancy

PW redundancy provides redundant links between PEs so that the customer networks can communicate when the path over one PW fails. As shown in Figure 5, PE 1 establishes two PWs (one primary and one backup). The CEs communicate through the primary PW. When the primary PW fails, PE 1 brings up the backup PW and forwards packets from CE 1 to CE 2 through the backup PW. When CE 2 receives the packets, it updates its MAC address table, so that packets from CE 2 to CE 1 also travel through the backup PW. Only static PWs and LDP PWs support PW redundancy.

Figure 5 PW redundancy

The MPLS L2VPN determines whether the primary PW fails according to the LDP session status or the BFD result. The backup PW is used when one of the following conditions exists:

· The public tunnel of the primary PW is deleted, or BFD detects that the public tunnel has failed.

· The primary PW is deleted because the LDP session between PEs goes down, or BFD detects that the primary PW has failed.

· A manual PW switchover is performed.

A PW can be in either of the following states:

· Active—The PW is in active state and can forward packets.

· Standby—The PW is in standby state and cannot forward packets.

Bypass PW

As shown in Figure 6, when the primary PW fails, CE 2 cannot immediately detect the failure and still sends the traffic to PE 2. As a result, traffic forwarding failure occurs.

To resolve the problem, you can create a bypass PW between PE 2 and PE 3.

As shown in Figure 6, after you create a bypass PW between PE 2 and PE 3, the bypass PW provides both PW bypass and AC bypass. Traffic is forwarded as follows:

· When the AC between PE 2 and CE 2 fails, traffic from CE 1 to CE 2 goes through the path CE 1—PE 1—PE 2—PE 3—CE 2.

· When the primary PW fails, traffic from CE 2 to CE 1 goes through the path CE 2—PE 2—PE 3—PE 1—CE 1.

Figure 6 Bypass PW

Multi-segment PW

Working mechanism

A multi-segment PW includes multiple concatenated static or LDP PWs. Creating two PWs for a cross-connect on a PE can concatenate the two PWs. Upon receiving a packet from one PW, the PE removes the tunnel ID and PW label of the packet, adds the PW label of the other PW, and forwards the packet over the public tunnel. Only static and LDP PWs can form a multi-segment PW.

As shown in Figure 7, to create a multi-segment PW between PE 1 and PE 4, you can concatenate PW 1 and PW 2 on PE 2, and PW 2 and PW 3 on PE 3.

Figure 7 Multi-segment PW

Multi-segment PWs include intra-domain multi-segment PWs and inter-domain multi-segment PWs.

Intra-domain multi-segment PW

An intra-domain multi-segment PW has concatenated PWs within an AS. You can create an intra-domain multi-segment PW between two PEs that have no public tunnel to each other.

As shown in Figure 8, there is no public tunnel between PE 1 and PE 4. There is a public tunnel between PE 1 and PE 2 and a public tunnel between PE 2 and PE 4. To create an intra-domain multi-segment PW between PE 1 and PE 4, you can perform the following operations:

1. Create a PW between PE 1 and PE 2 (PW 1) and a PW between PE 2 and PE 4 (PW 2).

2. Concatenate the two PWs on PE 2.

Intra-domain multi-segment PWs can fully use existing public tunnels to reduce end-to-end public tunnels.

Figure 8 Intra-domain multi-segment PW

Inter-domain multi-segment PW

An inter-domain multi-segment PW has concatenated PWs in different ASs, and is a method for inter-AS option B networking.

As shown in Figure 9, to create an inter-domain multi-segment PW between PE 1 and PE 2 in different ASs, you can perform the following operations:

· Concatenate PW 1 and PW 2 on ASBR 1.

· Concatenate PW 2 and PW 3 on ASBR 2.

Figure 9 Inter-domain multi-segment PW

VCCV

Virtual Circuit Connectivity Verification (VCCV) is an OAM feature for L2VPN. It verifies the connectivity of PWs on the data plane. VCCV includes the following modes:

· Manual mode—Use the ping mpls pw command to manually test the connectivity of a PW.

· Auto mode—Configure BFD to automatically test the connectivity of a PW.

For more information about VCCV, see "Configuring MPLS OAM."

MPLS L2VPN tasks at a glance

Configuring a remote connection

1. Enabling L2VPN

2. Configuring an AC

¡ Configuring a Layer 3 interface

¡ Configuring an Ethernet service instance on an interface

3. Configuring a cross-connect

4. Configuring a PW

Configure a static PW, LDP PW, BGP PW as needed.

¡ (Optional.) Configuring a PW class

¡ Configuring a static PW

¡ Configuring an LDP PW

¡ Configuring a BGP PW

5. Binding an AC to a cross-connect

6. (Optional.) Improving the MPLS L2VPN network reliability

¡ Configuring PW redundancy

¡ Configuring a bypass PW

7. (Optional.) Maintaining an MPLS L2VPN network

¡ Configuring L2VPN packet reflection

¡ Enabling bandwidth-based load sharing

¡ Enabling SNMP notifications for L2VPN PW

Configuring a local connection

1. Enabling L2VPN

2. Configuring an AC

To create a local connection, you must configure two ACs.

Choose one of the following tasks according to the AC type:

¡ Configuring a Layer 3 interface

¡ Configuring an Ethernet service instance on an interface

3. Configuring a cross-connect

4. Binding an AC to a cross-connect

Perform this task to bind the two ACs to the same cross-connect.

Configuring a multi-segment PW

1. Enabling L2VPN

2. Configuring a cross-connect

3. Configuring a PW

Configure two static or LDP PWs for a cross-connect to concatenate the two PWs.

¡ (Optional.) Configuring a PW class

¡ Configuring a static PW

¡ Configuring an LDP PW

4. (Optional.) Maintaining an MPLS L2VPN network

¡ Enabling bandwidth-based load sharing

¡ Enabling SNMP notifications for L2VPN PW

Prerequisites for MPLS L2VPN

To establish an MPLS L2VPN, you must perform the following tasks:

1. Configure an IGP to achieve IP connectivity within the backbone.

2. Configure basic MPLS, LDP, GRE, or MPLS TE to set up public tunnels across the backbone.

Enabling L2VPN

Prerequisites

Before you enable L2VPN, perform the following tasks:

· Configure an LSR ID for the PE with the mpls lsr-id command.

· Enable MPLS with the mpls enable command on the core-facing interface of the PE.

For more information about the mpls lsr-id and mpls enable commands, see MPLS Command Reference.

Procedure

1. Enter system view.

system-view

2. Enable L2VPN.

l2vpn enable

By default, L2VPN is disabled.

Configuring a Layer 3 interface

About configuring a Layer 3 interface

Configure a Layer 3 interface on a PE to establish an AC to the CE.

The PE forwards packets received from a Layer 3 interface through the bound PW without network layer processing. Therefore, the Layer 3 interface does not need an IP address.

On a Layer 3 Ethernet interface (including Layer 3 Ethernet interface and VE-L2VPN interface), both the PW data encapsulation type and access mode are Ethernet. On a Layer 3 Ethernet subinterface, both the PW data encapsulation type and access mode are VLAN

Configuring an Ethernet service instance on an interface

About configuring an Ethernet service instance on an interface

When the PE is connected to a CE through a Layer 2 Ethernet interface or Layer 2 aggregate interface, you can configure an Ethernet service instance on the interface to match packets for the AC.

Restrictions and guidelines

You cannot repeat the encapsulation command to modify the packet match criterion of an Ethernet service instance. To change the packet match criterion, first execute the undo encapsulation command to remove the original match criterion.

If the packet match criterion of an Ethernet service instance is removed, the binding between the Ethernet service instance and the cross-connect is removed automatically.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

¡ Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 2 aggregate interface view.

interface bridge-aggregation interface-number

3. Create an Ethernet service instance and enter Ethernet service instance view.

service-instance instance-id

4. Configure a packet match criterion for the Ethernet service instance.

encapsulation s-vid vlan-id

By default, no packet match criterion is configured.

Configuring a cross-connect

1. Enter system view.

system-view

2. Create a cross-connect group and enter cross-connect group view.

xconnect-group group-name

3. (Optional.) Configure a description for the cross-connect group.

description text

By default, no description is configured for a cross-connect group.

4. (Optional.) Enable the cross-connect group.

undo shutdown

By default, the cross-connect group is enabled.

5. Create a cross-connect and enter cross-connect view.

connection connection-name

6. (Optional.) Set an MTU for the PW.

mtu size

The default MTU is 1500 bytes.

The two PEs on an LDP PW must have the same MTU configured for the PW. Otherwise, the PW cannot come up.

Configuring a PW

Configuring a PW class

About configuring a PW class

You can configure PW attributes such as the PW data encapsulation type and enable control word in a PW class. PWs with the same attributes can use the same PW class.

Procedure

1. Enter system view.

system-view

2. Create a PW class and enter PW class view.

pw-class class-name

By default, no PW classes exist.

3. (Optional.) Enable control word.

control-word enable

By default, control word is disabled.

4. (Optional.) Specify the PW data encapsulation type.

pw-type { ethernet | vlan }

By default, the PW data encapsulation type is VLAN.

5. (Optional.) Enable the flow label feature and configure flow label capabilities.

flow-label { both | receive | send } [ static ]

By default, the flow label feature is disabled.

For the flow label feature to take effect, you need to configure the mpls load-sharing mode command on the P devices. For more information about the mpls load-sharing mode command, see basic MPLS commands in MPLS Command Reference.

Configuring a static PW

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. Configure a static PW, and enter cross-connect PW view.

peer ip-address pw-id pw-id in-label label-value out-label label-value [ admin | pw-class class-name | tunnel-policy tunnel-policy-name ] *

Configuring an LDP PW

About configuring an LDP PW

After an LDP PW is created, the PE automatically sends a targeted hello to create an LDP session to the peer PE. Then, the PE exchanges the PW ID FEC and PW label mapping with the peer.

Prerequisites

Before you configure an LDP PW, enable global and interface MPLS LDP on the PE. For information about MPLS LDP configuration, see "Configuring LDP."

Procedure

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. Configure an LDP PW, and enter cross-connect PW view.

peer ip-address pw-id pw-id [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

Configuring a BGP PW

Configuring BGP to advertise MPLS L2VPN label block information

1. Enter system view.

system-view

2. Enable BGP instance and enter BGP instance view.

bgp as-number [ instance instance-name ]

By default, BGP is disabled.

3. Configure the remote PE as a BGP peer.

peer { group-name | ip-address [ mask-length ] } as-number as-number

For more information about this command, see Layer 3—IP Routing Command Reference.

4. Create the BGP L2VPN address family and enter BGP L2VPN address family view.

address-family l2vpn

5. Enable BGP to exchange BGP L2VPN information with the specified peer or peer group.

peer { group-name | ip-address [ mask-length ] } enable

By default, BGP cannot exchange BGP L2VPN information with any peer or peer group.

For more information about this command, see Layer 3—IP Routing Command Reference.

6. Enable BGP to exchange label block information with the specified peer or peer group.

peer { group-name | ip-address [ mask-length ] } signaling [ non-standard ]

By default, BGP can exchange label block information with a BGP L2VPN peer or peer group by using RFC 4761 MP_REACH_NLRI.

7. Configure the BGP L2VPN address family.

For more information, see "Configuring BGP L2VPN address family."

8. Reset BGP L2VPN sessions.

For more information, see "Resetting BGP sessions."

Creating a BGP PW

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Configure the cross-connect group to automatically discover neighbors and create PWs through BGP and enter auto-discovery cross-connect group view.

auto-discovery bgp

By default, a cross-connect group does not automatically discover neighbors or create PWs through BGP.

4. Configure an RD for the cross-connect group.

route-distinguisher route-distinguisher

By default, no RD is configured for the cross-connect group.

5. Configure route targets for the cross-connect group.

vpn-target vpn-target&<1-8> [ both | export-extcommunity | import-extcommunity ]

By default, no route targets are configured for the cross-connect group.

6. (Optional.) Specify a PW class for the auto-discovery cross-connect group.

pw-class class-name

By default, no PW class is specified.

7. (Optional.) Set an MTU for the PW.

mtu size

The default MTU is 1500 bytes.

8. Create a local site and enter site view.

site site-id [ range range-value ] [ default-offset default-offset ]

9. Create a cross-connect and enter auto-discovery cross-connect view.

connection remote-site-id remote-site-id

After you execute this command, a PW to the specified remote site is created and is bound to the cross-connect.

10. (Optional.) Specify a tunnel policy for the auto-discovery cross-connect.

tunnel-policy tunnel-policy-name

By default, no tunnel policy is specified.

Configuring BGP L2VPN address family

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP L2VPN address family view.

address-family l2vpn

4. Permit the local AS number to appear in routes from the specified peer or peer group and specify the appearance times.

peer { group-name | ip-address [ mask-length ] } allow-as-loop [ number ]

By default, the local AS number is not allowed in routes from a peer or peer group.

For more information about this command, see Layer 3—IP Routing Command Reference.

5. Enable route target-based filtering of incoming BGP L2VPN information.

policy vpn-target

By default, route target-based filtering of incoming BGP L2VPN information is enabled.

6. Configure BGP route reflection:

a. Configure the router as a route reflector and specify a peer or peer group as its client.

peer { group-name | ip-address [ mask-length ] } reflect-client

By default, no route reflector or client is configured.

b. Enable L2VPN information reflection between clients.

reflect between-clients

By default, L2VPN information reflection between clients is enabled.

c. Configure the cluster ID of the route reflector.

reflector cluster-id { cluster-id | ip-address }

By default, a route reflector uses its own router ID as the cluster ID.

d. Configure a filtering policy for reflected L2VPN information.

rr-filter ext-comm-list-number

By default, the route reflector does not filter reflected L2VPN information.

For more information about the commands, see Layer 3—IP Routing Command Reference.

7. (Optional.) Set the BGP optimal route selection delay timer.

route-select delay delay-value

By default, the BGP optimal route selection delay timer is 0 seconds, which means optimal route selection is not delayed.

For more information about this command, see BGP commands in Layer 3—IP Routing Command Reference.

Resetting BGP sessions of L2VPN address family

To reset BGP sessions of the L2VPN address family, execute one of the following command in user view:

· Perform manual soft-reset for BGP sessions of the L2VPN address family.

refresh bgp [ instance instance-name ] { ip-address [ mask-length ] | all | external | group group-name | internal } { export | import } l2vpn

· Reset BGP sessions of the L2VPN address family.

reset bgp [ instance instance-name ] { as-number | ip-address [ mask-length ] | all | external | group group-name | internal } l2vpn

For more information about the commands, see Layer 3—IP Routing Command Reference.

Binding an AC to a cross-connect

About binding an AC to a cross-connect

When you bind an AC to a cross-connect, you can associate Track with the AC. Then, the AC is up only when one or more of the associated track entries are positive.

Associating Track with an AC helps detecting AC failure. For example, when an AC is a VE-L2VPN interface, the interface will not go down upon a link failure because the interface is a virtual interface. To resolve the problem, you can associate Track with the AC to detect failures on the link that connects the PE-agg to the L3VPN or IP backbone. When a failure occurs on the link, the VE-L2VPN interface is set to down. Consequently, the PW bound to the AC goes down. If the PW has a backup PW, traffic can be switched to the backup PW. For more information about VE-L2VPN interfaces and L2VPN access to L3VPN or IP backbone, see "Configuring L2VPN access to L3VPN or IP backbone."

Restrictions and guidelines for binding an AC to a cross-connect

This task is mutually exclusive with Ethernet link aggregation. If a Layer 3 or Layer 2 Ethernet interface has been added to a link aggregation group, you cannot bind the Layer 3 interface or an Ethernet service instance on the Layer 2 interface to a cross-connect, and vice versa.

If you bind a Layer 3 interface to a cross-connect, you cannot apply a user profile to the interface, and vice versa. For more information about applying user profiles to interfaces, see user profile configuration in BRAS Services Configuration Guide.

Binding a Layer 3 interface to a cross-connect

About binding a Layer 3 interface to a cross-connect

After you bind a Layer 3 interface to a cross-connect, packets received from the Layer 3 interface are forwarded through the PW or another AC bound to the cross-connect.

Restrictions and guidelines

After you bind a Layer 3 interface to a cross-connect, packets received from the Layer 3 interface are forwarded through the PW or another AC bound to the cross-connect.

When you bind a Layer 3 interface to a cross-connect, follow these restrictions and guidelines:

· The device does not support binding a VLAN interface to a cross-connect.

· The device does not support binding a Layer 3 Ethernet interface on SPC, CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E), and CMPE-1104 cards to a cross-connect. You can create a subinterface for the Layer 3 Ethernet interface and bind the subinterface to a cross-connect.

· After a subinterface of a Layer 3 Ethernet interface is bound to a cross-connect, the Layer 3 Ethernet interface cannot perform Layer 3 forwarding.

Binding a Layer 3 interface to a non-BGP cross-connect

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. Bind the Layer 3 interface to the cross-connect.

ac interface interface-type interface-number [ access-mode { ethernet | vlan } ] [ track track-entry-number&<1-3> ]

By default, no Layer 3 interface is bound to the cross-connect.

Binding a Layer 3 interface to a BGP cross-connect

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter auto-discovery cross-connect group view.

auto-discovery bgp

4. Enter site view.

site site-id [ range range-value ] [ default-offset default-offset-value ]

5. Enter auto-discovery cross-connect view.

connection remote-site-id remote-site-id

6. Bind the Layer 3 interface to the BGP cross-connect.

ac interface interface-type interface-number [ access-mode { ethernet | vlan } ] [ track track-entry-number&<1-3> ]

By default, no Layer 3 interface is bound to the BGP cross-connect.

Binding an Ethernet service instance to a cross-connect

About binding an Ethernet service instance to a cross-connect

On a Layer 2 Ethernet or Layer 2 aggregate interface, you can create an Ethernet service instance and bind it to a cross-connect. The Ethernet service instance matches packets received on that interface. The matching packets are then forwarded to the bound PW or another AC. An Ethernet service instance can match all packets, tagged packets, or untagged packets.

Restrictions and guidelines

When you bind an Ethernet service instance on an interface to a cross-connect, follow these restrictions and guidelines:

· The device does not support binding a cross-connect to multiple Ethernet service instances on a Layer 2 Ethernet interface on SPC, CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E), and CMPE-1104 cards.

· If you specify the access mode as Ethernet when you bind an Ethernet service instance on an interface on an SPC, CSPC, CMPE-1104, CSPEX-1104-E, or CSPEX-1204 card to a cross-connect, you must also enable QinQ on the interface.

Binding an Ethernet service instance to a non-BGP cross-connect

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. Bind an Ethernet service instance on an interface to the cross-connect.

ac interface interface-type interface-number service-instance instance-id [ access-mode { ethernet | vlan } ] [ track track-entry-number&<1-3> ]

By default, no Ethernet service instance is bound to the cross-connect.

Binding an Ethernet service instance to a BGP cross-connect

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter auto-discovery cross-connect group view.

auto-discovery bgp

4. Enter site view.

site site-id [ range range-value ] [ default-offset default-offset-value ]

5. Enter auto-discovery cross-connect view.

connection remote-site-id remote-site-id

6. Bind an Ethernet service instance on an interface to the BGP cross-connect.

ac interface interface-type interface-number service-instance instance-id [ access-mode { ethernet | vlan } ] [ track track-entry-number&<1-3> ]

By default, no Ethernet service instance is bound to the BGP cross-connect.

Configuring PW redundancy

Restrictions and guidelines for configuring PW redundancy

PW redundancy is mutually exclusive from the bypass PW feature. If you have configured a backup PW for a cross-connect PW by using the backup-peer command, you cannot configure a bypass PW for the cross-connect PW by using the bypass-peer command, and vice versa.

PW redundancy is mutually exclusive from the multi-segment PW feature. If you have configured two PWs by using the peer command, you cannot configure a backup PW by using the backup-peer command for the PWs, and vice versa.

Configuring static PW redundancy

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. (Optional.) Specify the switchover mode and set the wait time for the switchover.

revertive { wtr wtr-time | never }

By default, the switchover mode is revertive and the switchover wait time is 0 seconds.

5. (Optional.) Configure the dual receive feature for PW redundancy.

protection dual-receive

By default, the dual receive feature is disabled. When the primary PW is normal, the backup PW does not send or receive packets.

6. Enter cross-connect PW view.

peer ip-address pw-id pw-id [ admin | in-label label-value out-label label-value ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

7. Configure a backup cross-connect PW and enter backup cross-connect PW view.

backup-peer ip-address pw-id pw-id in-label label-value out-label label-value [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

Configuring LDP PW redundancy

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. (Optional.) Specify the switchover mode and set the wait time for the switchover.

revertive { wtr wtr-time | never }

By default, the switchover mode is revertive and the switchover wait time is 0 seconds.

5. (Optional.) Configure the dual receive feature for PW redundancy.

protection dual-receive

By default, the dual receive feature is disabled. When the primary PW is normal, the backup PW does not send or receive packets.

6. Enter cross-connect PW view.

peer ip-address pw-id pw-id [ admin | pw-class class-name | tunnel-policy tunnel-policy-name ] *

7. Configure a backup LDP PW and enter backup cross-connect PW view.

backup-peer ip-address pw-id pw-id [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

Performing a manual PW switchover

About performing a manual PW switchover

After you perform this task, if a PW has a backup PW or primary PW, this command switches traffic from the PW to the backup or primary PW. If the PW does not have a backup or primary PW, traffic switchover will not be performed.

Procedure

To manually switch the traffic of a PW to its backup PW, execute the following command in user view:

l2vpn switchover peer ip-address pw-id pw-id

Configuring a bypass PW

Restrictions and guidelines for configuring a bypass PW

Bypass PW and PW redundancy are mutually exclusive with each other. If you have configured a backup PW for a cross-connect PW by using the backup-peer command, you cannot configure a bypass PW for the cross-connect PW by using the bypass-peer command, and vice versa.

Bypass PW and multi-segment PW are mutually exclusive with each other. If you have configured two PWs by using the peer command, you cannot configure a bypass PW by using the bypass-peer command for the PWs, and vice versa.

Bypass PW is supported only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) cards.

Configuring a bypass LDP PW

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. Enter cross-connect PW view.

peer ip-address pw-id pw-id [ admin | pw-class class-name | tunnel-policy tunnel-policy-name ] *

5. Configure a bypass LDP PW and enter cross-connect bypass PW view.

bypass-peer ip-address pw-id pw-id pw-bypass [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

Configuring L2VPN packet reflection

About L2VPN packet reflection

After receiving a packet from the remote end, the local PE determines whether this packet is an ordinary data packet or a test packet. A packet whose destination IP address and UDP number match those specified by this feature is a test packet. Other packets are ordinary data packets.

· For an ordinary data packet, the local PE forwards the packet to the destination CE.

· For a test packet, the local PE encapsulates the packet with the specified IP and MAC addresses as the source IP and MAC addresses. Then, the local PE forwards the encapsulated packet to the remote PE.

This feature applies only to ICMP and UDP packets, and does not support VPLS PW test packet reflection. For more information about VPLS, see "Configuring VPLS."

Procedure

1. Enter system view.

system-view

2. Configure L2VPN packet reflection.

l2vpn reflector interface interface-type interface-number [ service-instance instance-id ] ip ip-address [ mac mac-address ] [ source-port source-port ] [ destination-port destination-port ]

By default, L2VPN packet reflection is disabled.

Enabling bandwidth-based load sharing

About bandwidth-based load sharing

If an L2VPN PW is carried by multiple equal-cost LDP LSPs, the PW evenly transmits packets through the LSPs. After you enable this feature, packets are transmitted through the LSPs in the proportion calculated based on the bandwidth of the egress interfaces.

This feature is available only when the public tunnels that carry a PW are LDP LSPs.

Procedure

1. Enter system view.

system-view

2. Enable bandwidth-based load sharing.

l2vpn bandwidth-based-sharing

By default, bandwidth-based load sharing is disabled.

Enabling SNMP notifications for L2VPN PW

About SNMP notifications for L2VPN PW

This feature enables L2VPN to generate SNMP notifications when PW deletions, PW switchovers, or PW status changes occur. For L2VPN event notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

Procedure

1. Enter system view.

system-view

2. Enable SNMP notifications for L2VPN PW.

snmp-agent trap enable l2vpn [ pw-delete | pw-switch | pw-up-down ] *

By default, SNMP notifications for L2VPN PW are disabled.

Display and maintenance commands for MPLS L2VPN

Execute display commands in any view and reset commands in user view.

Task	Command
Display LDP PW label information.	display l2vpn ldp [ peer ip-address [ pw-id pw-id ] \| xconnect-group group-name ] [ verbose ]
(In standalone mode.) Display cross-connect forwarding information.	display l2vpn forwarding { ac \| pw } [ xconnect-group group-name ] [ slot slot-number ] [ verbose ]
(In IRF mode.) Display cross-connect forwarding information.	display l2vpn forwarding { ac \| pw } [ xconnect-group group-name ] [ chassis chassis-number slot slot-number ] [ verbose ]
Display L2VPN information for Layer 3 interfaces bound to cross-connects.	display l2vpn interface [ xconnect-group group-name \| interface-type interface-number ] [ verbose ]
Display L2VPN PW information.	display l2vpn pw [ xconnect-group group-name ] [ protocol { bgp \| ldp \| static } ] [ verbose ]
Display L2VPN PW state machine information.	display l2vpn pw state-machine [ vsi vsi-name \| xconnect-group group-name ]
Display PW class information.	display l2vpn pw-class [ class-name ]
Display Ethernet service instance information.	display l2vpn service-instance [ interface interface-type interface-number [ service-instance instance-id ] ] [ verbose ]
Display cross-connect group information.	display l2vpn xconnect-group [ name group-name [ connection connection-name ] ] [ verbose ]
Display L2VPN label block information.	display l2vpn bgp [ peer ip-address \| local ] [ xconnect-group group-name ] [ verbose ]
Display BGP L2VPN peer group information.	display bgp [ instance instance-name ] group l2vpn [ group-name group-name ]
Display L2VPN label block information discovered by BGP.	display bgp [ instance instance-name ] l2vpn signaling [ peer ip-address { advertised \| received } [ statistics ] \| route-distinguisher route-distinguisher [ site-id site-id [ label-offset label-offset [ advertise-info ] ] ] \| statistics ]
Display BGP L2VPN peer information.	display bgp [ instance instance-name ] peer l2vpn [ ip-address mask-length \| group-name group-name log-info \| ip-address { log-info \| verbose } \| verbose ]
Display BGP L2VPN update group information.	display bgp [ instance instance-name ] update-group l2vpn [ ip-address ]
Reset BGP sessions for L2VPN.	reset bgp [ instance instance-name ] { as-number \| ip-address [ mask-length ] \| all \| external \| group group-name \| internal } l2vpn

For more information about the display bgp group l2vpn, display bgp peer l2vpn, display bgp update-group l2vpn, and reset bgp l2vpn commands, see Layer 3—IP Routing Command Reference.

MPLS L2VPN configuration examples

Example: Configuring local MPLS L2VPN connections

Network configuration

Configure local MPLS L2VPN connections between the PE and CEs to allow Layer 2 communication between CE 1 and CE 2.

Figure 10 Network diagram

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet3/1/1] quit

2. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 3/1/1

[CE2-GigabitEthernet3/1/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet3/1/1] quit

3. Configure PE:

# Enable L2VPN.

<PE> system-view

[PE] l2vpn enable

# Create a cross-connect group named vpn1, create a cross-connect named vpn1 in the group, and bind GigabitEthernet 3/1/1 and GigabitEthernet 3/1/2 to the cross-connect.

[PE] xconnect-group vpn1

[PE-xcg-vpn1] connection vpn1

[PE-xcg-vpn1-vpn1] ac interface gigabitethernet 3/1/1

[PE-xcg-vpn1-vpn1] ac interface gigabitethernet 3/1/2

[PE-xcg-vpn1-vpn1] quit

Verifying the configuration

# Verify that two AC forwarding entries exist on the PE.

[PE] display l2vpn forwarding ac

Total number of cross-connections: 1

Total number of ACs: 2

AC Xconnect-group Name Link ID

GE3/1/1 vpn1 0

GE3/1/2 vpn1 1

# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)

Example: Configuring a static PW

Network configuration

Create a static PW between PE 1 and PE 2 over the backbone to allow communication between CE 1 and CE 2.

Figure 11 Network diagram

Table 2 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE3/1/1	100.1.1.1/24	P	Loop0	192.4.4.4/32
PE 1	Loop0	192.2.2.2/32		GE3/1/1	10.1.1.2/24
	GE3/1/1	-		GE3/1/2	10.2.2.2/24
	GE3/1/2	10.1.1.1/24	PE 2	Loop0	192.3.3.3/32
CE 2	GE3/1/1	100.1.1.2/24		GE3/1/1	-
				GE3/1/2	10.2.2.1/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet3/1/1] quit

2. Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 192.2.2.2 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[PE1] l2vpn enable

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to the P device), and enable LDP on the interface.

[PE1] interface gigabitethernet 3/1/2

[PE1-GigabitEthernet3/1/2] ip address 10.1.1.1 24

[PE1-GigabitEthernet3/1/2] mpls enable

[PE1-GigabitEthernet3/1/2] mpls ldp enable

[PE1-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE1] ospf

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 10.1.1.1 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 192.2.2.2 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named svc in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] connection svc

[PE1-xcg-vpna-svc] ac interface gigabitethernet 3/1/1

# Create a static PW for the cross-connect to bind the AC to the PW.

[PE1-xcg-vpna-svc] peer 192.3.3.3 pw-id 3 in-label 100 out-label 200

[PE1-xcg-vpna-svc-192.3.3.3-3] quit

[PE1-xcg-vpna-svc] quit

[PE1-xcg-vpna] quit

3. Configure the P device:

# Configure an LSR ID.

<P> system-view

[P] interface loopback 0

[P-LoopBack0] ip address 192.4.4.4 32

[P-LoopBack0] quit

[P] mpls lsr-id 192.4.4.4

# Enable global LDP.

[P] mpls ldp

[P-ldp] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to PE 1), and enable LDP on the interface.

[P] interface gigabitethernet 3/1/1

[P-GigabitEthernet3/1/1] ip address 10.1.1.2 24

[P-GigabitEthernet3/1/1] mpls enable

[P-GigabitEthernet3/1/1] mpls ldp enable

[P-GigabitEthernet3/1/1] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 2), and enable LDP on the interface.

[P] interface gigabitethernet 3/1/2

[P-GigabitEthernet3/1/2] ip address 10.2.2.2 24

[P-GigabitEthernet3/1/2] mpls enable

[P-GigabitEthernet3/1/2] mpls ldp enable

[P-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[P] ospf

[P-ospf-1] area 0

[P-ospf-1-area-0.0.0.0] network 10.1.1.2 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 10.2.2.2 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 192.4.4.4 0.0.0.0

[P-ospf-1-area-0.0.0.0] quit

[P-ospf-1] quit

4. Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.3.3.3 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[PE2] l2vpn enable

# Enable globally LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to the P device), and enable LDP on the interface.

[PE2] interface gigabitethernet 3/1/2

[PE2-GigabitEthernet3/1/2] ip address 10.2.2.1 24

[PE2-GigabitEthernet3/1/2] mpls enable

[PE2-GigabitEthernet3/1/2] mpls ldp enable

[PE2-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE2] ospf

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 10.2.2.1 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] network 192.3.3.3 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named svc in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] connection svc

[PE2-xcg-vpna-svc] ac interface gigabitethernet 3/1/1

# Create a static PW for the cross-connect to bind the AC to the PW.

[PE2-xcg-vpna-svc] peer 192.2.2.2 pw-id 3 in-label 200 out-label 100

[PE2-xcg-vpna-svc-192.2.2.2-3] quit

[PE2-xcg-vpna-svc] quit

[PE2-xcg-vpna] quit

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 3/1/1

[CE2-GigabitEthernet3/1/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet3/1/1] quit

Verifying the configuration

# Verify that a static PW has been established on PE 1.

[PE1] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpna

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.3.3.3 3 100/200 Static M 0 Up

# Verify that a static PW has been established on PE 2.

[PE2] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpna

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.2.2.2 3 200/100 Static M Up

# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)

Example: Configuring an LDP PW

Network configuration

Create an LDP PW between PE 1 and PE 2 over the backbone to allow communication between CE 1 and CE 2.

Figure 12 Network diagram

Table 3 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE3/1/1	100.1.1.1/24	P	Loop0	192.4.4.4/32
PE 1	Loop0	192.2.2.2/32		GE3/1/1	10.1.1.2/24
	GE3/1/1	-		GE3/1/2	10.2.2.2/24
	GE3/1/2	10.1.1.1/24	PE 2	Loop0	192.3.3.3/32
CE 2	GE3/1/1	100.1.1.2/24		GE3/1/1	-
				GE3/1/2	10.2.2.1/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet3/1/1] quit

2. Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 192.2.2.2 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[PE1] l2vpn enable

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to the P device), and enable LDP on the interface.

[PE1] interface gigabitethernet 3/1/2

[PE1-GigabitEthernet3/1/2] ip address 10.1.1.1 24

[PE1-GigabitEthernet3/1/2] mpls enable

[PE1-GigabitEthernet3/1/2] mpls ldp enable

[PE1-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE1] ospf

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 10.1.1.1 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 192.2.2.2 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] connection ldp

[PE1-xcg-vpna-ldp] ac interface gigabitethernet 3/1/1

# Create an LDP PW for the cross-connect to bind the AC to the PW.

[PE1-xcg-vpna-ldp] peer 192.3.3.3 pw-id 3

[PE1-xcg-vpna-ldp-192.3.3.3-3] quit

[PE1-xcg-vpna-ldp] quit

[PE1-xcg-vpna] quit

3. Configure the P device:

# Configure an LSR ID.

<P> system-view

[P] interface loopback 0

[P-LoopBack0] ip address 192.4.4.4 32

[P-LoopBack0] quit

[P] mpls lsr-id 192.4.4.4

# Enable global LDP.

[P] mpls ldp

[P-ldp] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to PE 1), and enable LDP on the interface.

[P] interface gigabitethernet 3/1/1

[P-GigabitEthernet3/1/1] ip address 10.1.1.2 24

[P-GigabitEthernet3/1/1] mpls enable

[P-GigabitEthernet3/1/1] mpls ldp enable

[P-GigabitEthernet3/1/1] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 2), and enable LDP on the interface.

[P] interface gigabitethernet 3/1/2

[P-GigabitEthernet3/1/2] ip address 10.2.2.2 24

[P-GigabitEthernet3/1/2] mpls enable

[P-GigabitEthernet3/1/2] mpls ldp enable

[P-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[P] ospf

[P-ospf-1] area 0

[P-ospf-1-area-0.0.0.0] network 10.1.1.2 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 10.2.2.2 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 192.4.4.4 0.0.0.0

[P-ospf-1-area-0.0.0.0] quit

[P-ospf-1] quit

4. Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.3.3.3 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to the P device), and enable LDP on the interface.

[PE2] interface gigabitethernet 3/1/2

[PE2-GigabitEthernet3/1/2] ip address 10.2.2.1 24

[PE2-GigabitEthernet3/1/2] mpls enable

[PE2-GigabitEthernet3/1/2] mpls ldp enable

[PE2-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE2] ospf

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 192.3.3.3 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 10.2.2.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] connection ldp

[PE2-xcg-vpna-ldp] ac interface gigabitethernet 3/1/1

# Create an LDP PW for the cross-connect to bind the AC to the PW.

[PE2-xcg-vpna-ldp] peer 192.2.2.2 pw-id 3

[PE2-xcg-vpna-ldp-192.2.2.2-3] quit

[PE2-xcg-vpna-ldp] quit

[PE2-xcg-vpna] quit

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 3/1/1

[CE2-GigabitEthernet3/1/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet3/1/1] quit

Verifying the configuration

# Verify that an LDP PW has been established on PE 1.

[PE1] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpna

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.3.3.3 3 1279/1279 LDP M 1 Up

# Verify that an LDP PW has been established on PE 2.

[PE2] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpna

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.2.2.2 3 1279/1279 LDP M 1 Up

# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)

Example: Configuring a BGP PW

Network configuration

Create a BGP PW between PE 1 and PE 2 to allow communication between CE 1 and CE 2.

Figure 13 Network diagram

Table 4 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE3/1/1	100.1.1.1/24	P	Loop0	192.4.4.4/32
PE 1	Loop0	192.2.2.2/32		GE3/1/1	10.1.1.2/24
	GE3/1/1	-		GE3/1/2	10.2.2.2/24
	GE3/1/2	10.1.1.1/24	PE 2	Loop0	192.3.3.3/32
CE 2	GE3/1/1	100.1.1.2/24		GE3/1/1	-
				GE3/1/2	10.2.2.1/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet3/1/1] quit

2. Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 192.2.2.2 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[PE1] l2vpn enable

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to the P device), and enable LDP on the interface.

[PE1] interface gigabitethernet 3/1/2

[PE1-GigabitEthernet3/1/2] ip address 10.1.1.1 24

[PE1-GigabitEthernet3/1/2] mpls enable

[PE1-GigabitEthernet3/1/2] mpls ldp enable

[PE1-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE1] ospf

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 10.1.1.1 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 192.2.2.2 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

# Create an IBGP connection to PE 2, and enable BGP to advertise L2VPN information to PE 2.

[PE1] bgp 100

[PE1-bgp-default] peer 192.3.3.3 as-number 100

[PE1-bgp-default] peer 192.3.3.3 connect-interface loopback 0

[PE1-bgp-default] address-family l2vpn

[PE1-bgp-default-l2vpn] peer 192.3.3.3 enable

[PE1-bgp-default-l2vpn] quit

[PE1-bgp-default] quit

# Create a cross-connect group named vpnb, create a local site named site 1, and create a BGP PW from site 1 to remote site site 2.

[PE1] xconnect-group vpnb

[PE1-xcg-vpnb] auto-discovery bgp

[PE1-xcg-vpnb-auto] route-distinguisher 2:2

[PE1-xcg-vpnb-auto] vpn-target 2:2 export-extcommunity

[PE1-xcg-vpnb-auto] vpn-target 2:2 import-extcommunity

[PE1-xcg-vpnb-auto] site 1 range 10 default-offset 0

[PE1-xcg-vpnb-auto-1] connection remote-site-id 2

# Bind GigabitEthernet 3/1/1 to the PW.

[PE1-xcg-vpnb-auto-1-2] ac interface gigabitethernet 3/1/1

[PE1-xcg-vpnb-auto-1-2] return

3. Configure the P device:

# Configure an LSR ID.

<P> system-view

[P] interface loopback 0

[P-LoopBack0] ip address 192.4.4.4 32

[P-LoopBack0] quit

[P] mpls lsr-id 192.4.4.4

# Enable global LDP.

[P] mpls ldp

[P-ldp] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to PE 1), and enable LDP on the interface.

[P] interface gigabitethernet 3/1/1

[P-GigabitEthernet3/1/1] ip address 10.1.1.2 24

[P-GigabitEthernet3/1/1] mpls enable

[P-GigabitEthernet3/1/1] mpls ldp enable

[P-GigabitEthernet3/1/1] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 2), and enable LDP on the interface.

[P] interface gigabitethernet 3/1/2

[P-GigabitEthernet3/1/2] ip address 10.2.2.2 24

[P-GigabitEthernet3/1/2] mpls enable

[P-GigabitEthernet3/1/2] mpls ldp enable

[P-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[P] ospf

[P-ospf-1] area 0

[P-ospf-1-area-0.0.0.0] network 10.1.1.2 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 10.2.2.2 0.0.0.255

[P-ospf-1-area-0.0.0.0] network 192.4.4.4 0.0.0.0

[P-ospf-1-area-0.0.0.0] quit

[P-ospf-1] quit

4. Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.3.3.3 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to the P device), and enable LDP on the interface.

[PE2] interface gigabitethernet 3/1/2

[PE2-GigabitEthernet3/1/2] ip address 10.2.2.1 24

[PE2-GigabitEthernet3/1/2] mpls enable

[PE2-GigabitEthernet3/1/2] mpls ldp enable

[PE2-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE2] ospf

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 192.3.3.3 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 10.2.2.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Create an IBGP connection to PE 1, and enable BGP to advertise L2VPN information to PE 1.

[PE2] bgp 100

[PE2-bgp-default] peer 192.2.2.2 as-number 100

[PE2-bgp-default] peer 192.2.2.2 connect-interface loopback 0

[PE2-bgp-default] address-family l2vpn

[PE2-bgp-default-l2vpn] peer 192.2.2.2 enable

[PE2-bgp-default-l2vpn] quit

[PE2-bgp-default] quit

# Create a cross-connect group named vpnb, create a local site named site 2, and create a BGP PW from site 2 to remote site site 1.

[PE2] xconnect-group vpnb

[PE2-xcg-vpnb] auto-discovery bgp

[PE2-xcg-vpnb-auto] route-distinguisher 2:2

[PE2-xcg-vpnb-auto] vpn-target 2:2 export-extcommunity

[PE2-xcg-vpnb-auto] vpn-target 2:2 import-extcommunity

[PE2-xcg-vpnb-auto] site 2 range 10 default-offset 0

[PE2-xcg-vpnb-auto-2] connection remote-site-id 1

# Bind GigabitEthernet 3/1/1 to the PW.

[PE2-xcg-vpnb-auto-2-1] ac interface gigabitethernet 3/1/1

[PE2-xcg-vpnb-auto-2-1] return

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 3/1/1

[CE2-GigabitEthernet3/1/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet3/1/1] quit

Verifying the configuration

# Verify that a BGP PW has been established on PE 1.

<PE1> display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpnb

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.3.3.3 2 1036/1025 BGP M 1 Up

# Verify that a BGP PW has been established on PE 2.

<PE2> display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpnb

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.2.2.2 1 1025/1036 BGP M 1 Up

# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)

Example: Configuring a bypass PW

Network configuration

Create two LDP PWs to implement PW redundancy between CE 1 and CE 2. The primary PW goes through PE 1—PE 2. The backup PW goes through PE 1—PE 3. When the primary PW fails, CE 1 and CE 2 communicate through the backup PW.

Create a bypass PW between PE 2 and PE 3 to forward traffic when a primary/backup PW switchover occurs.

Figure 14 Network diagram

Table 5 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE3/1/1	192.1.1.1/24	PE 2	Loop0	2.2.2.2/32
PE 1	Loop0	1.1.1.1/32		GE3/1/1	10.1.1.2/24
	GE3/1/2	10.1.1.1/24		GE3/1/3	10.1.3.1/24
	GE3/1/3	10.1.2.1/24	PE 3	Loop0	3.3.3.3/32
CE 2	RAGG1	192.1.1.2/24		GE3/1/1	10.1.2.2/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 192.1.1.1 24

2. Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 1.1.1.1 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 1.1.1.1

# Enable L2VPN.

[PE1] l2vpn enable

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 2), and enable MPLS and LDP on the interface.

[PE1] interface gigabitethernet 3/1/2

[PE1-GigabitEthernet3/1/2] ip address 10.1.1.1 24

[PE1-GigabitEthernet3/1/2] mpls enable

[PE1-GigabitEthernet3/1/2] mpls ldp enable

[PE1-GigabitEthernet3/1/2] quit

# Configure GigabitEthernet 3/1/3 (the interface connected to PE 3), and enable MPLS and LDP on the interface.

[PE1] interface gigabitethernet 3/1/3

[PE1-GigabitEthernet3/1/3] ip address 10.1.2.1 24

[PE1-GigabitEthernet3/1/3] mpls enable

[PE1-GigabitEthernet3/1/3] mpls ldp enable

[PE1-GigabitEthernet3/1/3] quit

# Configure OSPF for LDP to create LSPs.

[PE1] ospf

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 10.1.1.1 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 10.1.2.1 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] connection ldp

[PE1-xcg-vpna-ldp] ac interface GigabitEthernet 3/1/1

# Create an LDP PW for the cross-connect to bind the AC to the PW, create a backup PW for the LDP PW, and configure the dual receive feature for PW redundancy.

[PE1-xcg-vpna-ldp] protection dual-receive

[PE1-xcg-vpna-ldp] peer 2.2.2.2 pw-id 11

[PE1-xcg-vpna-ldp-2.2.2.2-11] backup-peer 3.3.3.3 pw-id 22

[PE1-xcg-vpna-ldp-2.2.2.2-11-backup] quit

[PE1-xcg-vpna-ldp-2.2.2.2-11] quit

[PE1-xcg-vpna-ldp] quit

[PE1-xcg-vpna] quit

3. Configure CE 2:

# Create Layer 3 aggregate interface Route-Aggregation 1, use the static aggregation mode (the default), and configure the IP address and subnet mask for the aggregate interface.

<CE2> system-view

[CE2] interface route-aggregation 1

[CE2-Route-Aggregation1] ip address 192.1.1.2 24

[CE2-Route-Aggregation1] quit

# Add interfaces GigabitEthernet 3/1/2 and GigabitEthernet 3/1/3 to Layer 3 aggregation group 1.

[CE2] interface gigabitethernet 3/1/2

[CE2-GigabitEthernet3/1/2] port link-aggregation group 1

[CE2-GigabitEthernet3/1/2] quit

[CE2] interface gigabitethernet 3/1/3

[CE2-GigabitEthernet3/1/3] port link-aggregation group 1

[CE2-GigabitEthernet3/1/3] quit

4. Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 2.2.2.2 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 2.2.2.2

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to PE 1), and enable MPLS and LDP on the interface.

[PE2] interface gigabitethernet 3/1/1

[PE2-GigabitEthernet3/1/1] ip address 10.1.1.2 24

[PE2-GigabitEthernet3/1/1] mpls enable

[PE2-GigabitEthernet3/1/1] mpls ldp enable

[PE2-GigabitEthernet3/1/1] quit

# Configure GigabitEthernet 3/1/3 (the interface connected to PE 3), and enable MPLS and LDP on the interface.

[PE2] interface gigabitethernet 3/1/3

[PE2-GigabitEthernet3/1/3] ip address 10.1.3.1 24

[PE2-GigabitEthernet3/1/3] mpls enable

[PE2-GigabitEthernet3/1/3] mpls ldp enable

[PE2-GigabitEthernet3/1/3] quit

# Configure OSPF for LDP to create LSPs.

[PE2] ospf

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 10.1.1.2 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] network 10.1.3.1 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/2 to the cross-connect.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] connection ldp

[PE2-xcg-vpna-ldp] ac interface gigabitethernet 3/1/2

# Create an LDP PW for the cross-connect to bind the AC to the PW, and create a bypass PW for the LDP PW.

[PE2-xcg-vpna-ldp] peer 1.1.1.1 pw-id 11

[PE2-xcg-vpna-ldp-1.1.1.1-11] bypass-peer 3.3.3.3 pw-id 33

[PE2-xcg-vpna-ldp-1.1.1.1-11-bypass] quit

[PE2-xcg-vpna-ldp-1.1.1.1-11] quit

[PE2-xcg-vpna-ldp] quit

[PE2-xcg-vpna] quit

5. Configure PE 3:

# Configure an LSR ID.

<PE3> system-view

[PE3] interface loopback 0

[PE3-LoopBack0] ip address 3.3.3.3 32

[PE3-LoopBack0] quit

[PE3] mpls lsr-id 3.3.3.3

# Enable L2VPN.

[PE3] l2vpn enable

# Enable global LDP.

[PE3] mpls ldp

[PE3-ldp] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to PE 1), and enable MPLS and LDP on the interface.

[PE3] interface gigabitethernet 3/1/1

[PE3-GigabitEthernet3/1/1] ip address 10.1.2.2 24

[PE3-GigabitEthernet3/1/1] mpls enable

[PE3-GigabitEthernet3/1/1] mpls ldp enable

[PE3-GigabitEthernet3/1/1] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 2), and enable MPLS and LDP on the interface.

[PE3] interface gigabitethernet 3/1/2

[PE3-GigabitEthernet3/1/2] ip address 10.1.3.2 24

[PE3-GigabitEthernet3/1/2] mpls enable

[PE3-GigabitEthernet3/1/2] mpls ldp enable

[PE3-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE3] ospf

[PE3-ospf-1] area 0

[PE3-ospf-1-area-0.0.0.0] network 10.1.2.2 0.0.0.255

[PE3-ospf-1-area-0.0.0.0] network 10.1.3.2 0.0.0.255

[PE3-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0

[PE3-ospf-1-area-0.0.0.0] quit

[PE3-ospf-1] quit

# Create a cross-connect group named vpna, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/3 to the cross-connect.

[PE3] xconnect-group vpna

[PE3-xcg-vpna] connection ldp

[PE3-xcg-vpna-ldp] ac interface gigabitethernet 3/1/3

# Create an LDP PW for the cross-connect to bind the AC to the PW, and create a bypass PW for the LDP PW.

[PE3-xcg-vpna-ldp] peer 1.1.1.1 pw-id 22

[PE3-xcg-vpna-ldp-1.1.1.1-22] bypass-peer 2.2.2.2 pw-id 33

[PE3-xcg-vpna-ldp-1.1.1.1-22-bypass] quit

[PE3-xcg-vpna-ldp-1.1.1.1-22] quit

[PE3-xcg-vpna-ldp] quit

[PE3-xcg-vpna] quit

Example: Configuring an intra-domain multi-segment PW

Network configuration

As shown in Figure 15, there is no public tunnel between PE 1 and PE 2. There is an MPLS TE tunnel between PE 1 and P, and an MPLS TE tunnel between P and PE 2.

Configure a multi-segment PW within the backbone to allow communication between CE 1 and CE 2. The multi-segment PW includes an LDP PW between PE 1 and P, and a static PW between P and PE 2. The two PWs are concatenated on P.

Figure 15 Network diagram

Table 6 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE3/1/1	100.1.1.1/24	P	Loop0	192.4.4.4/32
PE 1	Loop0	192.2.2.2/32		GE3/1/1	23.1.1.2/24
	GE3/1/2	23.1.1.1/24		GE3/1/2	26.2.2.2/24
CE 2	GE3/1/1	100.1.1.2/24	PE 2	Loop0	192.3.3.3/32
				GE3/1/2	26.2.2.1/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet3/1/1] quit

2. Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 192.2.2.2 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[PE1] l2vpn enable

# Enable LDP globally.

[PE1] mpls ldp

[PE1-ldp] quit

# Configure MPLS TE to establish an MPLS TE tunnel between PE 1 and P. For more information, see "Configuring MPLS TE."

# Create a cross-connect group named vpn1, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE1] xconnect-group vpn1

[PE1-xcg-vpn1] connection ldp

[PE1-xcg-vpn1-ldp] ac interface gigabitethernet 3/1/1

# Create an LDP PW for the cross-connect to bind the AC to the PW.

[PE1-xcg-vpn1-ldp] peer 192.4.4.4 pw-id 1000

[PE1-xcg-vpn1-ldp-192.4.4.4-1000] quit

[PE1-xcg-vpn1-ldp] quit

[PE1-xcg-vpn1] quit

3. Configure the P device:

# Configure an LSR ID.

<P> system-view

[P] interface loopback 0

[P-LoopBack0] ip address 192.4.4.4 32

[P-LoopBack0] quit

[P] mpls lsr-id 192.4.4.4

# Enable L2VPN.

[P] l2vpn enable

# Enable LDP globally.

[P] mpls ldp

[P-ldp] quit

# Create a PW class named pwa, and configure the PW data encapsulation type as ethernet.

[P] pw-class pwa

[P-pw-pwa] pw-type ethernet

[P-pw-pwa] quit

# Configure MPLS TE to establish an MPLS TE tunnel between PE 1 and P, and between P and PE 2. For more information, see "Configuring MPLS TE."

# Create a cross-connect group named vpn1, create a cross-connect named ldpsvc in the group, and create an LDP PW and a static PW for the cross-connect to form a multi-segment PW.

[P] xconnect-group vpn1

[P-xcg-vpn1] connection ldpsvc

[P-xcg-vpn1-ldpsvc] peer 192.2.2.2 pw-id 1000 pw-class pwa

[P-xcg-vpn1-ldpsvc-192.2.2.2-1000] quit

[P-xcg-vpn1-ldpsvc] peer 192.3.3.3 pw-id 1000 in-label 100 out-label 200 pw-class pwa

[P-xcg-vpn1-ldpsvc-192.3.3.3-1000] quit

[P-xcg-vpn1-ldpsvc] quit

[P-xcg-vpn1] quit

4. Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.3.3.3 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[PE2] l2vpn enable

# Configure MPLS TE to establish an MPLS TE tunnel between P and PE 2. For more information, see "Configuring MPLS TE."

# Create a cross-connect group named vpn1, create a cross-connect named svc in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE2] xconnect-group vpn1

[PE2-xcg-vpn1] connection svc

[PE2-xcg-vpn1-svc] ac interface gigabitethernet 3/1/1

# Create a static PW for the cross-connect to bind the AC to the PW.

[PE2-xcg-vpn1-svc] peer 192.4.4.4 pw-id 1000 in-label 200 out-label 100

[PE2-xcg-vpn1-svc-192.4.4.4-1000] quit

[PE2-xcg-vpn1-svc] quit

[PE2-xcg-vpn1] quit

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 3/1/1

[CE2-GigabitEthernet3/1/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet3/1/1] quit

Verifying the configuration

# Verify that two PWs have been created to form a multi-segment PW on the P device.

[P] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 2

2 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.2.2.2 1000 1279/1150 LDP M 0 Up

192.3.3.3 1000 100/200 Static M 1 Up

# Verify that a PW has been created on PE 1.

[PE1] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.4.4.4 1000 1150/1279 LDP M 1 Up

# Verify that a PW has been created on PE 2.

[PE2] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.4.4.4 1000 200/100 Static M 1 Up

# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)

Example: Configuring an inter-domain multi-segment PW

Network configuration

PE 1 and ASBR 1 belong to AS 100. PE 2 and ASBR 2 belong to AS 200.

Set up an inter-domain multi-segment PW (a method for inter-AS Option B networking) within the backbone to allow communication between CE 1 and CE 2.

Configure the inter-domain multi-segment PW as follows:

· Configure LDP PWs between PE 1 and ASBR 1, and between PE 2 and ASBR 2, and configure public tunnels through LDP to carry the PWs.

· Configure an LDP PW between ASBR 1 and ASBR 2. Advertise labeled IPv4 routes between ASBR 1 and ASBR 2 through BGP to set up the public tunnel to carry the LDP PW.

· Concatenate the two PWs on ASBR 1.

· Concatenate the two PWs on ASBR 2.

Figure 16 Network diagram

Table 7 Interface and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE3/1/1	100.1.1.1/24	ASBR 1	Loop0	192.2.2.2/32
PE 1	Loop0	192.1.1.1/32		GE3/1/2	23.1.1.2/24
	GE3/1/2	23.1.1.1/24		GE3/1/1	26.2.2.2/24
PE 2	Loop0	192.4.4.4/32	ASBR 2	Loop0	192.3.3.3/32
	GE3/1/2	22.2.2.1/24		GE3/1/1	26.2.2.3/24
CE 2	GE3/1/1	100.1.1.2/24		GE3/1/2	22.2.2.3/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 3/1/1

[CE1-GigabitEthernet3/1/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet3/1/1] quit

2. Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 192.1.1.1 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 192.1.1.1

# Enable L2VPN.

[PE1] l2vpn enable

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to ASBR 1), and enable LDP on the interface.

[PE1] interface gigabitethernet 3/1/2

[PE1-GigabitEthernet3/1/2] ip address 23.1.1.1 24

[PE1-GigabitEthernet3/1/2] mpls enable

[PE1-GigabitEthernet3/1/2] mpls ldp enable

[PE1-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE1] ospf

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 23.1.1.1 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 192.1.1.1 0.0.0.0

[PE1-ospf-1-area-0.0.0.0] quit

[PE1-ospf-1] quit

# Create a cross-connect group named vpn1, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE1] xconnect-group vpn1

[PE1-xcg-vpn1] connection ldp

[PE1-xcg-vpn1-ldp] ac interface gigabitethernet 3/1/1

# Create an LDP PW for the cross-connect to bind the AC to the PW.

[PE1-xcg-vpn1-ldp] peer 192.2.2.2 pw-id 1000

[PE1-xcg-vpn1-ldp-192.2.2.2-1000] quit

[PE1-xcg-vpn1-ldp] quit

[PE1-xcg-vpn1] quit

3. Configure ASBR 1:

# Configure an LSR ID.

<ASBR1> system-view

[ASBR1] interface loopback 0

[ASBR1-LoopBack0] ip address 192.2.2.2 32

[ASBR1-LoopBack0] quit

[ASBR1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[ASBR1] l2vpn enable

# Enable global LDP.

[ASBR1] mpls ldp

[ASBR1-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 1), and enable LDP on the interface.

[ASBR1] interface gigabitethernet 3/1/2

[ASBR1-GigabitEthernet3/1/2] ip address 23.1.1.2 24

[ASBR1-GigabitEthernet3/1/2] mpls enable

[ASBR1-GigabitEthernet3/1/2] mpls ldp enable

[ASBR1-GigabitEthernet3/1/2] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to ASBR 2), and enable MPLS on the interface.

[ASBR1] interface gigabitethernet 3/1/1

[ASBR1-GigabitEthernet3/1/1] ip address 26.2.2.2 24

[ASBR1-GigabitEthernet3/1/1] mpls enable

[ASBR1-GigabitEthernet3/1/1] quit

# Configure OSPF for LDP to create LSPs.

[ASBR1] ospf

[ASBR1-ospf-1] area 0

[ASBR1-ospf-1-area-0.0.0.0] network 23.1.1.2 0.0.0.255

[ASBR1-ospf-1-area-0.0.0.0] network 192.2.2.2 0.0.0.0

[ASBR1-ospf-1-area-0.0.0.0] quit

[ASBR1-ospf-1] quit

# Configure BGP to advertise labeled routes on ASBR 1.

[ASBR1] bgp 100

[ASBR1-bgp-default] peer 26.2.2.3 as-number 200

[ASBR1-bgp-default] address-family ipv4 unicast

[ASBR1-bgp-default-ipv4] import-route direct

[ASBR1-bgp-default-ipv4] peer 26.2.2.3 enable

[ASBR1-bgp-default-ipv4] peer 26.2.2.3 route-policy policy1 export

[ASBR1-bgp-default-ipv4] peer 26.2.2.3 label-route-capability

[ASBR1-bgp-default-ipv4] quit

[ASBR1-bgp-default] quit

[ASBR1] route-policy policy1 permit node 1

[ASBR1-route-policy-policy1-1] apply mpls-label

[ASBR1-route-policy-policy1-1] quit

# Create a cross-connect group named vpn1, create a cross-connect named ldp in the group, and create two LDP PWs for the cross-connect to form a multi-segment PW.

[ASBR1] xconnect-group vpn1

[ASBR1-xcg-vpn1] connection ldp

[ASBR1-xcg-vpn1-ldp] peer 192.1.1.1 pw-id 1000

[ASBR1-xcg-vpn1-ldp-192.1.1.1-1000] quit

[ASBR1-xcg-vpn1-ldp] peer 192.3.3.3 pw-id 1000

[ASBR1-xcg-vpn1-ldp-192.3.3.3-1000] quit

[ASBR1-xcg-vpn1-ldp] quit

[ASBR1-xcg-vpn1] quit

4. Configure ASBR 2:

# Configure an LSR ID.

<ASBR2> system-view

[ASBR2] interface loopback 0

[ASBR2-LoopBack0] ip address 192.3.3.3 32

[ASBR2-LoopBack0] quit

[ASBR2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[ASBR2] l2vpn enable

# Enable global LDP.

[ASBR2] mpls ldp

[ASBR2-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to PE 2), and enable LDP on the interface.

[ASBR2] interface gigabitethernet 3/1/2

[ASBR2-GigabitEthernet3/1/2] ip address 22.2.2.3 24

[ASBR2-GigabitEthernet3/1/2] mpls enable

[ASBR2-GigabitEthernet3/1/2] mpls ldp enable

[ASBR2-GigabitEthernet3/1/2] quit

# Configure GigabitEthernet 3/1/1 (the interface connected to ASBR 1), and enable MPLS on the interface.

[ASBR2] interface gigabitethernet 3/1/1

[ASBR2-GigabitEthernet3/1/1] ip address 26.2.2.3 24

[ASBR2-GigabitEthernet3/1/1] mpls enable

[ASBR2-GigabitEthernet3/1/1] quit

# Configure OSPF for LDP to create LSPs.

[ASBR2] ospf

[ASBR2-ospf-1] area 0

[ASBR2-ospf-1-area-0.0.0.0] network 22.2.2.3 0.0.0.255

[ASBR2-ospf-1-area-0.0.0.0] network 192.3.3.3 0.0.0.0

[ASBR2-ospf-1-area-0.0.0.0] quit

[ASBR2-ospf-1] quit

# Configure BGP to advertise labeled routes on ASBR 2.

[ASBR2] bgp 200

[ASBR2-bgp-default] peer 26.2.2.2 as-number 100

[ASBR2-bgp-default] address-family ipv4 unicast

[ASBR2-bgp-default-ipv4] import-route direct

[ASBR2-bgp-default-ipv4] peer 26.2.2.2 enable

[ASBR2-bgp-default-ipv4] peer 26.2.2.2 route-policy policy1 export

[ASBR2-bgp-default-ipv4] peer 26.2.2.2 label-route-capability

[ASBR2-bgp-default-ipv4] quit

[ASBR2-bgp-default] quit

[ASBR2] route-policy policy1 permit node 1

[ASBR2-route-policy-policy1-1] apply mpls-label

[ASBR2-route-policy-policy1-1] quit

# Create a cross-connect group named vpn1, create a cross-connect named ldp in the group, and create two LDP PWs for the cross-connect to form a multi-segment PW.

[ASBR2] xconnect-group vpn1

[ASBR2-xcg-vpn1] connection ldp

[ASBR2-xcg-vpn1-ldp] peer 192.2.2.2 pw-id 1000

[ASBR2-xcg-vpn1-ldp-192.2.2.2-1000] quit

[ASBR2-xcg-vpn1-ldp] peer 192.4.4.4 pw-id 1000

[ASBR2-xcg-vpn1-ldp-192.4.4.4-1000] quit

[ASBR2-xcg-vpn1-ldp] quit

[ASBR2-xcg-vpn1] quit

5. Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.4.4.4 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.4.4.4

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Configure GigabitEthernet 3/1/2 (the interface connected to ASBR 2), and enable LDP on the interface.

[PE2] interface gigabitethernet 3/1/2

[PE2-GigabitEthernet3/1/2] ip address 22.2.2.1 24

[PE2-GigabitEthernet3/1/2] mpls enable

[PE2-GigabitEthernet3/1/2] mpls ldp enable

[PE2-GigabitEthernet3/1/2] quit

# Configure OSPF for LDP to create LSPs.

[PE2] ospf

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 192.4.4.4 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 22.2.2.1 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] quit

[PE2-ospf-1] quit

# Create a cross-connect group named vpn1, create a cross-connect named ldp in the group, and bind GigabitEthernet 3/1/1 to the cross-connect.

[PE2] xconnect-group vpn1

[PE2-xcg-vpn1] connection ldp

[PE2-xcg-vpn1-ldp] ac interface gigabitethernet 3/1/1

# Create an LDP PW for the cross-connect to bind the AC to the PW.

[PE2-xcg-vpn1-ldp] peer 192.3.3.3 pw-id 1000

[PE2-xcg-vpn1-ldp-192.3.3.3-1000] quit

[PE2-xcg-vpn1-ldp] quit

[PE2-xcg-vpn1] quit

6. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 3/1/1

[CE2-GigabitEthernet3/1/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet3/1/1] quit

Verifying the configuration

# Verify that an LDP PW has been created on PE 1.

[PE1] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.2.2.2 1000 1151/1279 LDP M Up

# Verify that two LDP PWs have been created to form a multi-segment PW on ASBR 1.

[ASBR1] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 2

2 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.1.1.1 1000 1279/1151 LDP M 0 Up

192.3.3.3 1000 1278/1151 LDP M 1 Up

# Verify that two LDP PWs have been created to form a multi-segment PW on ASBR 2.

[ASBR2] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 2

2 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.2.2.2 1000 1151/1278 LDP M 0 Up

192.4.4.4 1000 1150/1279 LDP M 1 Up

# Verify that an LDP PW has been created on PE 2.

[PE2] display l2vpn pw

Flags: M - main, B - backup, E - ecmp, BY - bypass, H - hub link, S - spoke link

N - no split horizon, A - administration, ABY – ac-bypass

PBY – pw-bypass

Total number of PWs: 1

1 up, 0 blocked, 0 down, 0 defect, 0 idle, 0 duplicate

Xconnect-group Name: vpn1

Peer PWID/RmtSite/SrvID In/Out Label Proto Flag Link ID State

192.3.3.3 1000 1279/1150 LDP M 1 Up

# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)

09-MPLS Configuration Guide

PE

AC

PW

Public tunnel

Cross-connect

Site ID

RD

Label block

Route target

Setting up a public tunnel

Setting up a PW

Binding the AC to the PW

PW data encapsulation types

Relationship between AC types and PW data encapsulation types

Ethernet over MPLS

Flow label

Working mechanism

Intra-domain multi-segment PW

Inter-domain multi-segment PW

VCCV

Prerequisites

Procedure

Configuring a Layer 3 interface

Configuring an Ethernet service instance on an interface

About configuring an Ethernet service instance on an interface

Restrictions and guidelines

Procedure

Configuring a cross-connect

Configuring a PW class

About configuring a PW class

Procedure

About configuring an LDP PW

Prerequisites

Procedure

Configuring BGP to advertise MPLS L2VPN label block information

Creating a BGP PW

Configuring BGP L2VPN address family

Resetting BGP sessions of L2VPN address family

Binding an AC to a cross-connect

Binding a Layer 3 interface to a cross-connect

About binding a Layer 3 interface to a cross-connect

Restrictions and guidelines

Binding a Layer 3 interface to a non-BGP cross-connect

Binding an Ethernet service instance to a cross-connect

About binding an Ethernet service instance to a cross-connect

Restrictions and guidelines

Binding an Ethernet service instance to a non-BGP cross-connect

About performing a manual PW switchover

Procedure

About L2VPN packet reflection

Procedure

About bandwidth-based load sharing

Procedure

Enabling SNMP notifications for L2VPN PW

About SNMP notifications for L2VPN PW

Procedure

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Example: Configuring an LDP PW

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Example: Configuring a bypass PW

Network configuration

Procedure

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Intelligent Terminal Products