· PE—A provider edge device connects one or more CEs to the service provider network. A PE implements VPN access by mapping and forwarding packets between private networks and public network tunnels. A PE can be a UPE or NPE in a hierarchical VPLS.

· AC—An attachment circuit, physical or virtual, connects a CE and a PE, such as an Ethernet link or a VLAN.

· PW—A pseudowire is a bidirectional virtual connection between two PEs. An MPLS PW consists of two unidirectional MPLS LSPs in opposite directions.

· Tunnel—A tunnel can be an LSP tunnel, an MPLS TE tunnel, or a GRE tunnel. It carries one or more PWs over an IP/MPLS backbone. If a PW is carried on an LSP or MPLS TE tunnel, each packet on the PW contains two labels. The inner label is the PW label, which identifies the PW and ensures that the packet is forwarded to the correct VSI. The outer label is the public LSP or MPLS TE tunnel label, which ensures that the packet is correctly forwarded to the remote PE.

· VPLS instance—A customer network might contain multiple geographically dispersed sites (such as site 1 and site 3 in Figure 1.) The service provider uses VPLS to connect all the sites to create a single Layer 2 VPN, which is referred to as a VPLS instance. Sites in different VPLS instances cannot communicate with each other at Layer 2.

· VSI—A virtual switch instance provides Layer 2 switching services for a VPLS instance on a PE. A VSI acts as a virtual switch that has all the functions of a conventional Ethernet switch, including source MAC address learning, MAC address aging, and flooding. VPLS uses VSIs to forward Layer 2 data packets in VPLS instances.

Creating a PW

In a VPLS network, PEs use PWs to forward packets among VPN sites.

A PW is created as follow:

1. Specify the address of the remote PE or configure an auto-discovery protocol to automatically find the remote PE. BGP is the most commonly used auto-discovery protocol.

2. Specify the incoming label and the outgoing label for the PW on the two PEs to create the PW. You can also use LDP or BGP to advertise the PW-label binding to the remote PE to establish the unidirectional LSPs. The PW is created once the two unidirectional LSPs are created.

PW types

PEs use PWs to forward packets among VPN sites. PWs include static PWs, LDP PWs, BGP PWs, and BGP auto-discovery LDP PWs.

Static PW

To create a static PW, specify the address of the remote PE, the incoming label, and the outgoing label.

LDP PW

To create an LDP PW, specify the address of the remote PE, and use LDP to advertise the PW-label binding to the remote PE. After the two PEs receive the PW-label binding from each other, they establish an LDP PW. The FEC type in the LDP message is PWid FEC Element that includes the PW ID field (FEC 128). The PW ID identifies the PW bound to the PW label.

BGP PW

To create a BGP PW, configure BGP to advertise label block information to the remote PE. After the two PEs receive label block information from each other, they use the label block information to calculate the incoming and outgoing labels and create the BGP PW. A PE also uses the received label block information to automatically find the remote PE.

BGP auto-discovery LDP PW

To create a BGP auto-discovery LDP PW, configure BGP to automatically find the remote PE, and use LDP to advertise the PW-label binding to the remote PE. After the two PEs receive the PW-label binding from each other, they establish a BGP auto-discovery LDP PW.

The information advertised by BGP includes the ID (for example, LSR ID) and VPLS ID of the advertising PE. The receiving PE compares the received VPLS ID with its own VPLS ID. If the two VPLS IDs are identical, the two PEs use LDP to establish a PW. If not, the PEs do not establish a PW. The FEC type in the LDP message is Generalized PWid FEC Element (FEC 129), which contains the VPLS ID, Source Attachment Individual Identifier (SAII), and Target Attachment Individual Identifier (TAII). The SAII is the LSR ID of the advertising PE. The TAII identifies the remote PE and is advertised by the remote PE. VPLS ID+SAII+TAII uniquely identifies a PW in a VPLS instance.

MAC address learning, aging, and withdrawal

Source MAC address learning

VPLS provides reachability through source MAC learning. A PE maintains a MAC address table for each VSI.

As shown in Figure 2, a PE learns source MAC addresses in the following ways:

· Learning the source MAC addresses of directly connected sites.

If the source MAC address of a packet from a CE does not exist in the MAC address table, the PE learns the source MAC address of the AC connected to the CE.

· Learning the source MAC addresses of remote sites connected through PWs.

A VSI regards a PW as a logical Ethernet interface. If the source MAC address of a packet from a PW does not exist in the MAC address table, the PE learns the source MAC address on the PW of the VSI.

Figure 2 Source MAC address learning on a PE

‌

MAC address aging

The MAC address table uses an aging timer for each dynamic MAC address entry. If no packet is received from a MAC address before the aging timer expires, VPLS deletes the MAC address.

MAC address withdrawal

When an AC or a PW goes down, the PE deletes MAC addresses on the AC or PW. Then it sends an LDP address withdrawal message to notify all other PEs in the VPLS instance to delete those MAC addresses.

Traffic forwarding and flooding

Unicast traffic forwarding and flooding

After a PE receives a unicast packet from an AC, the PE searches the MAC address table of the VSI bound to the AC for packet forwarding.

· If a match is found, the PE forwards the packet according to the matching entry.

¡ If the outgoing interface in the entry is a PW, the PE inserts the PW label to the packet, and adds the public tunnel header to the packet. It then forwards the packet to the remote PE over the PW. If the PW is carried on an LSP or MPLS TE tunnel, each packet on the PW contains two labels. The inner label is the PW label, which identifies the PW and ensures that the packet is forwarded to the correct VSI. The outer label is the public LSP or MPLS TE tunnel label, which ensures that the packet is correctly forwarded to the remote PE.

¡ If the outgoing interface in the entry is a local interface, the PE directly forwards the packet to the local interface.

· If no match is found, the PE floods the packet to all other ACs and PWs in the VSI.

After a PE receives a unicast packet from a PW, the PE searches the MAC address table of the VSI bound to the PW for packet forwarding.

· If a match is found, the PE forwards the packet through the outgoing interface in the matching entry.

· If no match is found, the PE floods the packet to all ACs in the VSI.

Multicast and broadcast traffic forwarding and flooding

After a PE receives a multicast or broadcast packet from an AC, the PE floods the packet to all other ACs and the PWs in the VSI bound to the AC.

After a PE receives a multicast or broadcast packet from a PW, the PE floods the packet to all ACs in the VSI bound to the PW.

PW full mesh and split horizon

A Layer 2 network requires a loop prevention protocol such as STP to avoid loops. However, a loop prevention protocol on PEs brings management and maintenance difficulties. Therefore, VPLS uses the following methods to prevent loops:

· Full mesh—Every two PEs in a VPLS instance must establish a PW. The PWs form a full mesh among PEs in the VPLS instance.

· Split horizon—A PE does not forward packets received from a PW to any other PWs in the same VSI but only forwards those packets to ACs.

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 3, 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 3 PW redundancy

‌

VPLS 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.

LDP PWs support the independent and master/slave PW redundancy operation modes.

· Independent mode—The two PEs of a PW use LDP to advertise their respective PW active/standby state to each other. A PW can forward traffic only when it is up and active at both ends of the PW. In this mode, make sure both PEs of a PW use the independent PW redundancy operation mode.

· Master/slave mode—One PE of a PW operates as the master node and the other PE operates as the slave node. The master PE determines the PW active/standby state and then uses LDP to advertise the PW state to the slave PE. The slave PE uses the same PW state as the master PE based on the information received from the master PE. In this way, the master and slave PEs for the set of redundant PWs can use the same active PW to forward user packets.

A slave node does not advertise the PW active/standby state to the master node, and the master node ignores the PW active/standby state received from the slave nodes.

Interconnecting an EVPN VXLAN network with a VPLS network

This task applies to the following scenarios:

· A newly deployed EVPN VXLAN network in one data center needs to communicate with an existing VPLS network in another data center.

· Two data centers with EVPN VXLAN networks deployed need to communicate over a WAN VPLS network.

As shown in Figure 4, for an EVPN VXLAN network and a VPLS network to communicate over a WAN VPLS network, configure the intermediate border devices GW 1 and GW 2 as follows:

· Configure EVPN VXLAN and VPLS.

· Interconnect the EVPN VXLAN network with the VPLS network by mapping the LDP PWs or static PWs on the VPLS network to the VXLAN tunnels.

On the intermediate border devices, the LDP PWs or static PWs of VPLS act as ACs of EVPN VXLAN. These PWs are called UPWs. The intermediate border devices can forward traffic between the VXLAN tunnels and the UPWs to enable communication between the EVPN VXLAN network and the VPLS network.

Figure 4 Interconnection between an EVPN VXLAN network and a VPLS network

‌

As shown in Figure 4, the VTEP sets up VXLAN tunnels with GW 1 and GW 2, the gateways set up UPWs over the WAN VPLS network as follows:

· GW 1 sets up a main UPW and a backup UPW with GW 3 and GW 4, respectively.

· GW 2 sets up a main UPW and a backup UPW with GW 4 and GW 3, respectively.

When GW 1 or GW 2 receives a packet from a UPW, the gateway performs the following actions:

1. Removes the MPLS encapsulation.

2. Looks up the MAC address table for an outgoing VXLAN tunnel interface.

3. Adds VXLAN encapsulation to the packet.

4. Forwards the packet to the VTEP over the matching VXLAN tunnel.

When receiving a packet from a VXLAN tunnel, GW 1 or GW 2 uses a similar workflow to forward the packet over a UPW to the VPLS network.

For more information about interconnecting an EVPN VXLAN network with a VPLS network, see EVPN VXLAN configuration in EVPN Configuration Guide.

Restrictions: Hardware compatibility with VPLS

The S9825 switch series does not support VPLS.

Restrictions and guidelines: VPLS configuration

The device supports VPLS only when the routing mode is specified using the hardware-resource switch-mode command. For more information about the hardware-resource switch-mode command, see System Command Reference.

VPLS tasks at a glance

Perform the following configuration tasks on a PE :

1. Enabling L2VPN

2. Configuring an AC Configuring a VSI

3. Configuring a PW

Choose the following tasks as needed:

¡ (Optional.) Configuring a PW class

¡ Configuring a static PW

¡ Configuring an LDP PW

¡ Configuring a BGP PW

¡ Configuring a BGP auto-discovery LDP PW

¡ (Optional.) Configuring the BGP L2VPN address family

You can configure this task to control route advertisement and selection in BGP L2VPN address family when you configure a BGP PW or BGP auto-discovery LDP PW.

4. Binding an AC to a VSI

5. (Optional.) Configuring PW redundancy

6. (Optional.) Enabling VPLS statistics

7. (Optional.) Enabling SNMP notifications for L2VPN PW

Prerequisites for VPLS

To configure a VPLS network, perform the following tasks:

· Configure an IGP to ensure IP connectivity within the backbone.

· Configure basic MPLS, LDP, GRE, or MPLS TE to establish public tunnels on the backbone network.

If the public tunnel is a GRE tunnel, perform the following tasks:

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

· Enable MPLS with the mpls enable command on the backbone interface of the PE.

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

Enabling L2VPN

1. Enter system view.

system-view

2. Enable L2VPN.

l2vpn enable

By default, L2VPN is disabled.

Configuring an AC

Configuring a Layer 3 interface

When the PE is connected to a CE through a Layer 3 interface, you must configure the Layer 3 interface to establish an AC to the CE.

The Layer 3 interface can be a Layer 3 Ethernet interface (including physical Layer 3 Ethernet interface, Layer 3 virtual Ethernet interface, and VE-L2VPN interface) or Layer 3 Ethernet subinterface.

For more information about Ethernet interfaces, see Interface Configuration Guide. For more information about Layer 3 virtual Ethernet interfaces, see Layer 2—WAN Configuration Guide. For more information about VE-L2VPN interfaces, see "Configuring L2VPN access to L3VPN or IP backbone."

Configuring a VSI

1. Enter system view.

system-view

2. Create a VSI and enter VSI view.

vsi vsi-name

3. (Optional.) Configure a description for the VSI.

description text

By default, no description is configured for a VSI.

4. (Optional.) Set the default PW ID for the VSI.

default-pw-id default-pw-id

By default, no default PW ID is configured for the VSI.

5. Set an MTU for the VSI.

mtu size

By default, the MTU of a VSI is 1500 bytes.

6. (Optional.) Enable the VSI.

undo shutdown

By default, a VSI is enabled.

Configuring a PW

Configuring a PW class

About this task

In a PW class, you can configure PW attributes such as the PW data encapsulation type, and whether to enable control word. To simplify PW configuration, you can configure PWs with the same attributes by referencing 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 } [ force-for-vpls ]

By default, the PW data encapsulation type is VLAN.

Configuring a static PW

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Specify static signaling for PWs, and enter VSI static view.

pwsignaling static

By default, no PW signaling protocol is specified.

4. Configure a static PW, and enter VSI static PW view.

peer ip-address [ pw-id pw-id ] in-label label-value out-label label-value [ dci | hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] *

Parameter	Description
pw-id pw-id	If both the default PW ID in the default-pw-id command and a PW ID in the peer command are configured, the PW ID in the peer command is used. If only the default PW ID is configured, the default PW ID is used. If no default PW ID is configured, you must provide a PW ID in the peer command.
dci	Specify this keyword to establish a DCI PW between EDs in a DCI network. DCI PWs use split horizon for packet forwarding to avoid loops. If you do not specify this keyword, the PW is established within the data center.
hub	If a VSI is enabled with the hub-spoke capability (the hub-spoke keyword in the vsi command), PWs in the VSI are spoke links by default. You can use the hub keyword in this command to specify the static PW as the hub link in the VSI.
no-split-horizon	You must specify the no-split-horizon keyword to disable split horizon when you configure an NPE to establish a U-PW with a UPE.

‌

Configuring an LDP PW

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 VSI view.

vsi vsi-name

3. Specify LDP signaling for PWs, and enter VSI LDP signaling view.

pwsignaling ldp

By default, no PW signaling protocol is specified.

4. Configure an LDP PW, and enter VSI LDP PW view.

Parameter	Description
pw-id pw-id	If both the default PW ID in the default-pw-id command and a PW ID in the peer command are configured, the PW ID in the peer command is used. If only the default PW ID is configured, the default PW ID is used. If no default PW ID is configured, you must provide a PW ID in the peer command.
dci	Specify this keyword to establish a DCI PW between EDs in a DCI network. DCI PWs use split horizon for packet forwarding to avoid loops. If you do not specify this keyword, the PW is established within the data center.
hub	If a VSI is enabled with the hub-spoke capability (the hub-spoke keyword in the vsi command), PWs in the VSI are spoke links by default. You can use the hub keyword in this command to specify the static PW as the hub link in the VSI.
no-split-horizon	You must specify the no-split-horizon keyword to disable split horizon when you configure an NPE to establish a U-PW with a UPE.

‌

Configuring a BGP PW

Configuring BGP to advertise VPLS 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.

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

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 BGP in 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 L2VPN information with the specified peer or peer group.

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

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

For more information about this command, see BGP in 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

By default, BGP can exchange label block information with a BGP L2VPN peer or peer group.

7. (Optional.) Configure the BGP L2VPN address family.

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

8. (Optional.) Maintain BGP sessions.

For more information, see "."

Creating a BGP PW

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Configure the VSI to automatically discover neighbors through BGP and enter auto-discovery VSI view.

auto-discovery bgp

By default, a VSI does not automatically discover neighbors through BGP.

4. Configure an RD for the auto-discovery VSI.

route-distinguisher route-distinguisher

By default, no RD is configured for the auto-discovery VSI.

5. Configure route targets for the auto-discovery VSI.

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

By default, no route targets are configured for the auto-discovery VSI.

6. (Optional.) Specify a PW class for the auto-discovery VSI.

pw-class class-name

By default, no PW class is specified.

7. (Optional.) Specify a tunnel policy for the auto-discovery VSI.

tunnel-policy tunnel-policy-name

By default, no tunnel policy is specified.

8. Use BGP to create a PW to an automatically discovered remote PE and enter auto-discovery VSI BGP signaling view.

signaling-protocol bgp

By default, no signaling protocol is specified.

9. Create a local site.

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

Configuring a BGP auto-discovery LDP PW

Prerequisites for configuring a BGP auto-discovery LDP PW

Before you perform this configuration, enable MPLS LDP on interfaces and globally. For more information, see "Configuring LDP."

Configuring BGP to advertise VPLS PE 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.

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

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 BGP in 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 VPLS PE information with the specified peer or peer group.

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

By default, BGP cannot exchange VPLS PE information with a peer or peer group.

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

6. Enable BGP to exchange VPLS PE information with the specified peer or peer group.

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

By default, BGP can exchange VPLS PE information with a BGP L2VPN peer or peer group by using RFC 6074 MP_REACH_NLRI.

7. (Optional.) Configure the BGP L2VPN address family.

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

Creating a BGP auto-discovery LDP PW

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Configure the VSI to automatically discover neighbors through BGP and enter auto-discovery VSI view.

auto-discovery bgp

By default, a VSI does not automatically discover neighbors through BGP.

4. Configure an RD for the auto-discovery VSI.

route-distinguisher route-distinguisher

By default, no RD is configured for the auto-discovery VSI.

5. Configure route targets for the auto-discovery VSI.

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

By default, no route targets are configured for the auto-discovery VSI.

6. (Optional.) Specify a PW class for the auto-discovery VSI.

pw-class class-name

By default, no PW class is specified.

7. (Optional.) Specify a tunnel policy for the auto-discovery VSI.

tunnel-policy tunnel-policy-name

By default, no tunnel policy is specified.

8. Use LDP to create a PW to an automatically discovered remote PE and enter auto-discovery VSI LDP signaling view.

signaling-protocol ldp

By default, no signaling protocol is specified.

9. Configure a VPLS ID for the VSI.

vpls-id vpls-id

By default, no VPLS ID is configured.

Configuring the BGP L2VPN address family

About this task

When you configure a BGP PW or a BGP auto-discovery LDP PW, you can perform this task to control route advertisement and selection in the BGP L2VPN address family.

Procedure

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 maximum number of the appearances.

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.

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.

¡ Configure the device 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.

¡ Enable L2VPN information reflection between clients.

reflect between-clients

By default, L2VPN information reflection is enabled between clients.

¡ 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.

¡ Configure the route reflector to filter reflected L2VPN information.

rr-filter ext-comm-list-number

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

7. (Optional.) Configure the device to not change the next hop of routes advertised to a peer or peer group.

peer { group-name | ipv4-address [ mask-length ] } next-hop-invariable

By default, the device uses its address as the next hop for routes advertised to EBGP peers or peer groups and it does not change the next hop of routes advertised to an IBGP peer or peer group.

8. (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.

Binding an AC to a VSI

About binding an AC to a VSI

After you bind a Layer 3 interface to a VSI, packets received from the Layer 3 interface are forwarded based on the MAC address table of the VSI.

Restrictions and guidelines for binding an AC to a VSI

If a Layer 2 or Layer 3 Ethernet interface has been added to a link aggregation group, you cannot bind that Layer 2 or Layer 3 interface to a VSI, and vice versa.

Binding a Layer 3 interface to a VSI

1. Enter system view.

system-view

2. Enter Layer 3 interface view.

interface interface-type interface-number

3. Bind the interface to a VSI.

xconnect vsi vsi-name [ access-mode { ethernet | vlan } ]

By default, an interface is not bound to any VSI.

Parameter	Description
access-mode { ethernet \| vlan }	The AC access mode determines how the device (PE) considers the VLAN tag in Ethernet frames received from the CE and how the PE forwards Ethernet frames to the CE. · VLAN access mode—Ethernet frames received from the CE must carry a VLAN tag in the Ethernet header. The PE considers the VLAN tag as a P-tag assigned by the service provider. Ethernet frames sent to the CE must also carry the P-tag. · Ethernet access mode—If Ethernet frames from the CE have a VLAN tag in the header, the PE considers it as a U-tag and ignores it. Ethernet frames sent to the CE do not carry the P-tag.

Parameter

Description

access-mode { ethernet | vlan }

The AC access mode determines how the device (PE) considers the VLAN tag in Ethernet frames received from the CE and how the PE forwards Ethernet frames to the CE.

· VLAN access mode—Ethernet frames received from the CE must carry a VLAN tag in the Ethernet header. The PE considers the VLAN tag as a P-tag assigned by the service provider. Ethernet frames sent to the CE must also carry the P-tag.

· Ethernet access mode—If Ethernet frames from the CE have a VLAN tag in the header, the PE considers it as a U-tag and ignores it. Ethernet frames sent to the CE do not carry the P-tag.

‌

Configuring PW redundancy

Configuring static PW redundancy

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Specify static signaling for PWs, and enter VSI static view.

pwsignaling static

By default, no PW signaling protocol is specified for the VSI.

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. Configure a static PW and enter VSI static PW view.

peer ip-address [ pw-id pw-id ] [ in-label label-value out-label label-value ] [ dci | hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] *

6. Configure a backup static PW and enter VSI static backup 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 ] *

If both the default PW ID in the default-pw-id command and a PW ID in the backup-peer command are configured, the PW ID in the backup-peer command is used. If only the default PW ID is configured, the default PW ID is used. If no default PW ID is configured, you must provide a PW ID in the backup-peer command.

7. (Optional.) Manually switch the traffic:

a. Return to user view.

return

b. Manually switch traffic of the PW to its backup PW.

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

Configuring LDP PW redundancy

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Specify LDP signaling for PWs, and enter VSI LDP signaling view.

pwsignaling ldp

By default, no PW signaling protocol is specified for the VSI.

4. (Optional.) Specify a PW redundancy operation mode.

pw-redundancy { independent | master }

By default, the PW redundancy operation mode is master/slave and the local PE operates as the slave node.

Do not configure this command on the local PE if the remote PE does not support the PW redundancy operation mode configuration.

5. (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.

6. Configure an LDP PW and enter VSI LDP PW view.

7. Configure a backup LDP PW and enter VSI LDP backup PW view.

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

8. (Optional.) Manually switch the traffic:

a. Return to user view.

return

b. Manually switch traffic of the PW to its backup PW.

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

Enabling VPLS statistics

Enabling packet statistics for a PW

Restrictions and guidelines for enabling packet statistics for a PW

Perform this task to enable packet statistics for a static PW or an LDP PW. To display packet statistics for the PW, use the display l2vpn pw verbose command. To clear packet statistics for the PW, use the reset l2vpn statistics pw command.

Enabling packet statistics for a static PW

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Enter VSI static configuration view.

pwsignaling static

4. Enter VSI static PW view.

peer ip-address [ pw-id pw-id ] [ in-label label-value out-label label-value [ dci | hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] * ]

5. Enable packet statistics for the PW.

statistics enable

By default, packet statistics is disabled for PWs created from the CLI, and is enabled for PWs created from the MIB. For more information about MIBs, see SNMP in Network Management and Monitoring Configuration Guide.

Enabling packet statistics for an LDP PW

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Enter VSI LDP signaling view.

pwsignaling ldp

4. Enter VSI LDP PW view.

5. Enable packet statistics for the PW.

statistics enable

By default, packet statistics is disabled for PWs created from the CLI, and is enabled for PWs from the MIB. For more information about MIBs, see SNMP in Network Management and Monitoring Configuration Guide.

Enabling SNMP notifications for L2VPN PW

About this task

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.

Verifying and maintaining VPLS

Verifying BGP L2VPN configuration and running status

Perform display tasks in any view.

· Display BGP L2VPN peer group information.

display bgp [ instance instance-name ] group l2vpn [ group-name group-name ]

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

· Display VPLS PE information discovered by BGP.

display bgp [ instance instance-name ] l2vpn auto-discovery [ peer ip-address { advertised | received } [ statistics ] | route-distinguisher route-distinguisher [ pe-address ip-address [ advertise-info ] ] | statistics ]

· Display VPLS 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 ]

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

· Display BGP L2VPN update group information.

display bgp [ instance instance-name ] update-group l2vpn [ ip-address ]

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

· Display information about automatically discovered VPLS PEs.

display l2vpn auto-discovery [ peer ip-address ] [ vsi vsi-name ]

· Display VPLS label block information.

display l2vpn bgp [ instance instance-name ] [ peer ip-address | local ] [ vsi vsi-name ] [ verbose ]

Resetting BGP sessions

About this task

If BGP configuration is changed, you can reset or soft-reset BGP sessions to validate the new configuration for BGP PWs and BGP auto-discovery LDP PWs.

A soft reset updates BGP routing information without tearing down BGP connections. A reset operation updates BGP routing information by tearing down, and then re-establishing BGP connections. Soft reset requires that BGP peers have route refresh capability (support the ROUTE-REFRESH message).

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

Procedure

To reset BGP sessions, execute one of the following commands in user view:

· Soft-reset L2VPN BGP sessions.

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

· Reset L2VPN BGP sessions.

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

Verifying VSI configuration and running status

To display VSI information, execute the following command in any view:

display l2vpn vsi[ name vsi-name | vpls ] [ count | verbose ]

Verifying AC configuration and running status

Perform display tasks in any view.

· Display AC forwarding information.

display l2vpn forwarding ac [ vsi vsi-name ] [ slot slot-number ] [ verbose ]

· Display L2VPN information for Layer 3 interfaces bound to VSIs.

display l2vpn interface [ vsi vsi-name | interface-type interface-number ] [ verbose ]

Verifying PW configuration and running status

Perform display tasks in any view.

· Display PW forwarding information.

display l2vpn forwarding pw [ vsi vsi-name ] [ slot slot-number ] [ verbose ]

· Display LDP PW label information.

display l2vpn ldp [ peer ip-address [ pw-id pw-id | vpls-id vpls-id ] | vsi vsi-name ] [ verbose ]

· Display L2VPN PW information.

display l2vpn pw [ vsi vsi-name ] [ protocol { bgp | ldp | static } ] [ verbose ]

· Display L2VPN PW state machine information.

display l2vpn pw state-machine [ vsi vsi-name ]

· Display PW class information.

display l2vpn pw-class [ class-name ] [ verbose ]

Verifying and clearing MAC address entries

To display MAC address entries, execute the following command in any view:

display l2vpn mac-address [ vsi vsi-name ] [ dynamic ] [ count | verbose ]

To clear MAC address entries, execute the following command in user view:

reset l2vpn mac-address [ vsi vsi-name ]

Clearing VPLS packet statistics

Perform reset tasks in any view.

· Clear packet statistics for PWs.

reset l2vpn statistics pw [ vsi vsi-name [ link link-id ] ]

08-MPLS Configuration Guide

Configuring VPLS

Static PW

LDP PW

BGP PW

BGP auto-discovery LDP PW

Source MAC address learning

MAC address aging

MAC address withdrawal

Unicast traffic forwarding and flooding

Multicast and broadcast traffic forwarding and flooding

PW redundancy

Interconnecting an EVPN VXLAN network with a VPLS network

Configuring a Layer 3 interface

About this task

Procedure

Prerequisites

Procedure

Configuring BGP to advertise VPLS label block information

Creating a BGP PW

Prerequisites for configuring a BGP auto-discovery LDP PW

Configuring BGP to advertise VPLS PE information

Creating a BGP auto-discovery LDP PW

About this task

Procedure

Binding a Layer 3 interface to a VSI

Configuring static PW redundancy

Restrictions and guidelines for enabling packet statistics for a PW

Enabling packet statistics for a static PW

Enabling SNMP notifications for L2VPN PW

About this task

Procedure

Verifying and maintaining VPLS

Resetting BGP sessions

About this task

Procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us