EVPN Virtual Private Wire Service (VPWS) is a Layer 2 VPN technology that uses MP-BGP for BGP EVPN route advertisement in the control plane and MPLS for forwarding in the data plane. EVPN VPWS provides point-to-point forwarding services for users by using ACs and PWs associated with cross-connects without MAC address table lookup.

EVPN VPWS network model

As shown in Figure 1, an EVPN VPWS network contains the following devices:

· Customer edge (CE)—Customer device directly connected to the service provider network.

· Provider edge (PE)—Service provider device connected to CEs. PEs provide access to the EVPN VPWS network and forward traffic between customer network sites by using public tunnels.

A PE uses ACs, PWs, tunnels, and cross-connects to provide EVPN VPWS services.

· Attachment circuit (AC)—A physical or virtual link between a CE and a PE.

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

· Public tunnel—A connection that carries one or more PWs across the MPLS or IP backbone. A public tunnel can be an LSP, GRE tunnel, or MPLS TE tunnel.

· Cross-connect—A connection formed by 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 and AC to PW cross-connect.

Figure 1 EVPN VPWS network

Remote connection establishment

EVPN VPWS remote connection provides point-to-point Layer 2 connectivity between customer network sites by using PWs over an IP or MPLS backbone.

To set up a remote EVPN VPWS 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.

Public tunnel establishment

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

If multiple public tunnels are set up between two PEs, you can configure a tunnel policy to control tunnel selection. For more information about tunnel policies, see MPLS Configuration Guide.

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.

PW establishment

A PW is established between two PEs based on the local and remote service IDs configured on the PEs. In an EVPN VPWS network, each PE advertises its remote service ID through Ethernet auto-discovery routes and compares received remote service IDs with its local service ID. A PE establishes a unidirectional LSP to a peer If the remote service ID advertised by the peer matches the local service ID. PW establishment is finished when two LSPs in opposite directions are established between two PEs.

AC establishment

For EVPN VPWS, an AC is associated with a cross-connect and can be a Layer 3 Ethernet interface or Layer 3 Ethernet subinterface on a PE.

AC-to-PW bindings

For PEs to forward packets between an AC and a PW, bind the AC to the PW.

EVPN VPWS multihoming

About this task

As shown in Figure 2, EVPN VPWS supports deploying multiple PEs at a site for redundancy and high availability. On the redundant PEs, Ethernet links connected to the site form an ES that is uniquely identified by an ESI. EVPN VPWS supports only dualhoming.

Figure 2 EVPN VPWS multihoming

Redundancy mode

The device supports single-active redundancy mode and all-active redundancy mode of EVPN VPWS multihoming.

· Single-active mode—This mode allows one of the redundant PWs to forward traffic, as shown in Figure 3. When the main PW becomes unavailable because of device failure or link failure, traffic is switched to the backup PW for forwarding. The redundant PEs elect the main PW as described in "About DF election."

Figure 3 Single-active mode

· All-active mode—This mode allows all redundant PWs to a multihomed site to load share traffic.

About DF election

In single-active mode, a DF is elected from the redundant PEs to determine the main PW. PEs that fail the election are assigned the BDF role. The PWs on BDFs do not forward traffic.

Redundant PEs at a site send Ethernet segment routes to one another to advertise ES and PE IP mappings. A PE accepts the Ethernet segment routes only when it is configured with an ESI. Then, the PEs select a DF based on the ES and PE IP mappings. DF election can be performed by using a VLAN tag-based algorithm or preference-based algorithm.

Figure 4 DF election

VLAN tag-based DF election

PEs select a DF for each AC based on the VLAN tag and PE IP address as follows:

1. Arrange source IP addresses in Ethernet segment routes with the same ESI in ascending order and assign a sequence number to each IP address, starting from 0.

2. Divide the lowest VLAN ID permitted on an AC by the number of the redundant PEs, and match the reminder to the sequence numbers of IP addresses.

3. Assign the DF role to the PE that uses the IP address with the matching sequence number.

The following uses PE 1 and PE 2 in Figure 5 as an example to explain the DF election procedure:

4. PE 1 and PE 2 send Ethernet segment routes to each other.

5. The PEs assign sequence numbers 0 and 1 to IP addresses 1.1.1.1 and 2.2.2.2 in the Ethernet segment routes, respectively.

6. The PEs divide 4 (the lowest VLAN ID permitted by the ACs) by 2 (the number of redundant PEs), and match the reminder 0 to the sequence numbers of the IP addresses.

7. The DF role is assigned to PE 1 at 1.1.1.1.

Figure 5 VLAN tag-based DF election

Preference-based DF election

PEs select a DF for each ES based on the DF election preference, the Don't Preempt Me (DP) bit in Ethernet segment routes, and PE IP address. The DP bit can be set to one of the following values:

· 1—DF preemption is disabled. A DF retains its role when a new DF is elected.

· 0—DF preemption is enabled.

Preference-based DF election uses the following rules to select a DF for an ES:

· The PE with higher preference becomes the DF.

· If two PEs have the same preference, the PE with the DP bit set to 1 becomes the DF. If both of the PEs have the DP bit set to 1, the PE with a lower IP address becomes the DF.

As shown in Figure 6, PE 2 is the DF for ES 1, and PE 1 is the DF for ES 2.

Figure 6 Preference-based DF election

FRR for EVPN VPWS

About FRR

Fast reroute (FRR) helps reduce the traffic loss caused by AC or PW failure on an EVPN VPWS network. FRR includes local FRR and remote FRR.

Local FRR

Local FRR enables two PEs at a multihomed EVPN VPWS network site to set up a bypass PW between them.

As shown in Figure 7, CE 2 is dualhomed to PE 2 and PE 3. When the AC on PE 2 fails, PE 2 advertises the local unreachable event to PE 1 and PE 3 for PE 1 to switch traffic to the PW to PE 3. In this situation, PE 3 drops the packets that PE 1 sends before it is notified of the local unreachable event. To resolve this issue, enable local FRR on PE 2 and PE 3. When receiving packets from PE 1 after PE 2's AC fails, PE 2 forwards the packets to PE 3 over the bypass PW to prevent traffic loss.

Figure 7 Local FRR

Remote FRR

Remote FRR enables two PEs on an EVPN VPWS network to set up a primary PW and a backup PW between them to ensure high availability. This feature is applicable to both multihoming and singlehoming scenarios.

As shown in Figure 8, PE 1 and PE 2 are connected by RR 1 and RR 2. The RRs change the next hop attribute of routes and reassign MPLS labels to them based on routing policies when reflecting the routes. PE 1 and PE 2 select only RR 1 or RR 2 when establishing a PW. For high availability, you can enable remote FRR on PE 1 for it to set up PWs to both RRs. PE 1 uses the primary PW to forward traffic as long as it is available. When the primary PW fails, PE 1 switches traffic to the backup PW. For more information about optimal route selection on PE 1, see BGP configuration in Layer 3—IP Routing Configuration Guide.

Figure 8 Remote FRR

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.

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

The control word field is optional for EVPN PWs. 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.

L2VPN 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 9.

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 9 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 PEs to successfully negotiate the flow label capabilities, make sure one end has the sending capability and the other end has the receiving capability.

For EVPN VPWS PWs, you must manually configure flow label capabilities for the local and remote PEs.

EVPN VPWS tasks at a glance

To configure EVPN VPWS, perform the following tasks:

1. Enabling L2VPN

2. Configure an AC

¡ Configuring a Layer 3 interface with Ethernet or VLAN encapsulation

3. Configuring BGP EVPN routes

a. Enabling BGP to advertise BGP EVPN routes

b. Enabling the device to advertise MPLS-encapsulated BGP EVPN routes

c. (Optional.) Configuring optimal route selection and route advertisement settings

d. (Optional.) Configuring routing policy-based recursive lookup

e. (Optional.) Maintaining BGP sessions

4. Configuring a cross-connect

5. Configuring a PW

a. (Optional.) Configuring a PW class

b. Configuring an EVPN PW

6. Mapping an AC to a cross-connect

7. (Optional.) Configuring EVPN VPWS multihoming

a. Assigning an ESI to an interface

b. (Optional.) Setting the redundancy mode on an interface

c. (Optional.) Configuring the DF election algorithm

d. (Optional.) Enabling AC state-based DF election

e. (Optional.) Setting the DF election delay

f. (Optional.) Enabling non-revertive mode for preference-based DF election

g. (Optional.) Configuring Ethernet segment route advertisement delay

h. (Optional.) Enabling fast DF/BDF switchover

i. (Optional.) Disabling advertisement of EVPN multihoming routes

j. (Optional.) Enabling cross-connects to ignore the state of ACs

k. (Optional.) Enabling the device to monitor the BGP peer status of another local edge device

8. (Optional.) Configuring FRR for EVPN VPWS

9. (Optional.) Testing the connectivity of an EVPN PW

Prerequisites for EVPN VPWS

To configure EVPN VPWS, 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 by using the mpls lsr-id command.

· Enable MPLS by using the mpls enable command on the transport-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 with Ethernet or VLAN encapsulation

About this task

Configure a Layer 3 interface on a PE to establish an AC to the CE. On a Layer 3 Ethernet interface (including Layer 3 Ethernet interface, Layer 3 virtual 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.

Restrictions and guidelines

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.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

Configuring BGP EVPN routes

Restrictions and guidelines for EVPN route advertisement configuration

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

Enabling BGP to advertise BGP EVPN routes

1. Enter system view.

system-view

2. Configure a global router ID.

router id router-id

By default, no global router ID is configured.

3. Enable a BGP instance and enter BGP instance view.

bgp as-number [ instance instance-name ]

By default, BGP is disabled and no BGP instances exist.

4. Specify remote PEs as BGP peers.

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

5. Create the BGP EVPN address family and enter BGP EVPN address family view.

address-family l2vpn evpn

6. Enable BGP to exchange BGP EVPN routes with a peer or peer group.

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

By default, BGP does not exchange BGP EVPN routes with peers.

Enabling the device to advertise MPLS-encapsulated BGP EVPN routes

About this task

Perform this task on PEs for them to establish PWs.

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP EVPN address family view.

address-family l2vpn evpn

4. Enable MPLS encapsulation for the BGP EVPN routes advertised to a peer or peer group.

peer { group name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise encap-type mpls

By default, BGP EVPN routes use VXLAN encapsulation.

Configuring optimal route selection and route advertisement settings

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP EVPN address family view.

address-family l2vpn evpn

4. Permit the local AS number to appear in routes from a peer or peer group and set the number of appearances.

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

By default, the local AS number is not allowed in routes from peers.

5. Enable route target filtering for BGP EVPN routes.

policy vpn-target

By default, route target filtering is enabled for BGP EVPN routes.

6. Enable the device to filter advertised objects based on the first AS number in EBGP routes.

peer-as-check enable

By default, the device advertises a received EBGP route to all BGP peers except the peer that sends the EBGP route.

After you execute this command, the device checks the first AS number in the AS_Path attribute of an EBGP route when advertising the EBGP route to EBGP peers. The device will not advertise the EBGP route to the EBGP peers in that AS.

7. (Optional.) Set the optimal route selection delay timer. Choose one of the following tasks or both:

¡ Set the optimal route selection delay timer for all BGP routes in the current address family.

route-select delay delay-value

¡ Delay optimal route selection for a peer in the specified duration after the peer comes up.

route-select suppress on-peer-up milliseconds

By default, optimal route selection is not delayed.

8. (Optional.) Set the delay time for responding to recursive next hop changes.

nexthop recursive-lookup [ non-critical-event ] delay [ delay-value ]

By default, BGP responds to recursive next hop changes immediately.

9. Configure BGP route reflection settings:

a. Configure the device as an RR and specify a peer or peer group as its client.

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

By default, no RR or client is configured.

b. (Optional.) Enable BGP EVPN route reflection between clients.

reflect between-clients

By default, BGP EVPN route reflection between clients is enabled.

c. (Optional.) Configure the cluster ID of the RR.

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

By default, an RR uses its own router ID as the cluster ID.

d. (Optional.) Create a reflection policy for the RR to filter reflected BGP EVPN routes.

rr-filter { ext-comm-list-number | ext-comm-list-name }

By default, an RR does not filter reflected BGP EVPN routes.

e. (Optional.) Create a reflection policy for the RR to filter reflected BGP EVPN routes.

reflect change-path-attribute

By default, an RR does not filter reflected BGP EVPN routes.

f. (Optional.) Add a peer or peer group to the nearby cluster.

peer { group-name | ipv4-address [ mask-length ] } reflect-nearby-group

By default, the nearby cluster does not have any peers or peer groups.

The RR does not change the next hop of routes reflected to peers and peer groups in the nearby cluster.

10. Configure the device to not change the next hop of routes advertised to an EBGP 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 of routes advertised to EBGP peers.

11. Set a preferred value for routes received from a peer or peer group.

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } preferred-value value

By default, the preferred value is 0 for routes received from a peer or peer group.

12. Prefer routes learned from the specified peer or peer group during optimal route selection.

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } high-priority

By default, BGP does not prefer routes learned from any peer or peer groups during optimal route selection.

13. Apply a routing policy to routes received from or advertised to a peer or peer group.

peer { group-name | ipv4-address [ mask-length ] } route-policy route-policy-name { export | import }

By default, no routing policies are applied to routes received from or advertised to peers or peer groups.

14. Advertise the COMMUNITY attribute to a peer or peer group.

peer { group-name | ipv4-address [ mask-length ] } advertise-community

By default, the device does not advertise the COMMUNITY attribute to peers or peer groups.

15. Configure the BGP Additional Paths feature:

a. Configure the BGP Additional Paths capabilities.

peer { group-name | ipv4-address [ mask-length ] } additional-paths { receive | send } *

By default, no BGP Additional Paths capabilities are configured.

b. Set the maximum number of Add-Path optimal routes that can be advertised to a peer or peer group.

peer { group-name | ipv4-address [ mask-length ] } advertise additional-paths best number

By default, a maximum of one Add-Path optimal route can be advertised to a peer or peer group.

c. Set the maximum number of Add-Path optimal routes that can be advertised to all peers.

additional-paths select-best best-number

By default, a maximum of one Add-Path optimal route can be advertised to all peers.

Configuring routing policy-based recursive lookup

About this task

Configure routing policy-based recursive lookup to control route recursion results, such as to prefer a path during route recursion or to ensure correctness of recursive routes.

If routing policy-based recursive lookup is configured, all recursive routes are filtered by using the specified routing policy. If no recursive route for a route matches a permit node in the routing policy, that route is considered unreachable and invalid.

To disable routing policy-based recursive lookup for the BGP routes learned from a specific peer or peer group, use the peer nexthop-recursive-policy disable command.

Restrictions and guidelines

The nexthop recursive-lookup route-policy command does not take effect on the routes learned from directly connected EBGP peers.

The protocol nexthop recursive-lookup command executed in RIB IPv4 or IPv6 address family view also takes effect on BGP routes of the BGP EVPN address family. If you execute both the nexthop recursive-lookup route-policy and protocol nexthop recursive-lookup commands, the nexthop recursive-lookup route-policy command is preferred for BGP EVPN routes.

For more information about the nexthop recursive-lookup route-policy and peer nexthop-recursive-policy disable commands, see BGP commands in Layer 3—IP Routing Command Reference.

For more information about the protocol nexthop recursive-lookup command, see IP routing basics commands in Layer 3—IP Routing Command Reference.

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP EVPN address family view.

address-family l2vpn evpn

4. Configure routing policy-based recursive lookup.

nexthop recursive-lookup route-policy route-policy-name

By default, BGP does not perform routing policy-based recursive lookup.

IMPORTANT:

If no recursive route of the BGP EVPN address family matches a permit node in the specified routing policy, all BGP routes of this address family will become unreachable. To avoid traffic interruption, plan your desired recursive routes and configure the routing policy accordingly.

5. (Optional.) Disable routing policy-based recursive lookup for the BGP routes learned from a peer or peer group.

a. Return to BGP instance view.

quit

b. Exempt a peer or peer group from routing policy-based recursive lookup.

peer { group-name | ipv4-address [ mask-length ] } nexthop-recursive-policy disable

By default, routing policy-based recursive lookup takes effect on routes learned from all peers and peer groups.

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

The nexthop recursive-lookup route-policy and protocol nexthop recursive-lookup commands do not take effect on the exempted peers and peer groups.

Maintaining BGP sessions

Perform the following tasks in user view:

· Reset BGP sessions of the BGP EVPN address family.

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

· Soft-reset BGP sessions of the BGP EVPN address family.

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

Configuring a cross-connect

Restrictions and guidelines

For more information about the cross-connect commands used in this task, see MPLS L2VPN commands in MPLS Command Reference.

Procedure

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

Configuring a PW

Configuring a PW class

About this task

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.

Restrictions and guidelines

For more information about the PW class commands used in this task, see MPLS L2VPN commands in MPLS Command Reference.

You must configure the same data encapsulation type on two PEs that are connected by the same PW.

For correct PW setup, make sure the status of the control word feature is the same on the two PEs that are connected by the same PW.

Procedure

1. Enter system view.

system-view

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

pw-class class-name

3. Enable control word.

control-word enable

By default, control word is disabled.

4. Specify the PW data encapsulation type.

pw-type { ethernet | vlan }

By default, the PW data encapsulation type is VLAN.

5. Enable the flow label feature and configure flow label capabilities.

flow-label { both | receive | send } static

By default, the flow label feature is disabled.

EVPN VPWS does not support flow label capability negotiation for dynamic PWs in the current software version. For this command to take effect, you must specify the static keyword.

Configuring an EVPN PW

About this task

To establish an EVPN PW between two PEs, specify a local service ID and a remote service ID on both PEs. The local service ID specified on one PE must be the same as the remote service ID specified on the other PE.

You can configure routing policies in cross-connect group EVPN instance view. An import routing policy is used for filtering the BGP EVPN routes received by the EVPN instance, and an export routing policy is used for filtering the BGP EVPN routes advertised by the EVPN instance.

Restrictions and guidelines

To modify an EVPN PW, first use the undo evpn local-service-id remote-service-id command to delete the original EVPN PW.

Procedure

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Create an EVPN instance for the cross-connect group and enter its view.

evpn encapsulation mpls

4. Configure an RD for the EVPN instance.

route-distinguisher route-distinguisher

By default, no RD is configured for the EVPN instance of a cross-connect group.

5. Configure route targets for the EVPN instance.

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

By default, no route targets are configured for the EVPN instance of a cross-connect group.

Make sure the following requirements are met:

¡ The import targets of the EVPN instance of a cross-connect group do not match the export targets of a VPN instance, the public instance, or the EVPN instance of a VSI.

¡ The export targets of the EVPN instance of a cross-connect group do not match the import targets of a VPN instance, the public instance, or the EVPN instance of a VSI.

6. (Optional.) Apply an export routing policy to EVPN.

export route-policy route-policy

By default, no export routing policy is applied to EVPN.

7. (Optional.) Apply an import routing policy to EVPN.

import route-policy route-policy

By default, no import routing policy is applied to EVPN. A VPN instance accepts a route when the route targets of the route match local import route targets.

8. Return to cross-connect group view.

quit

9. Enter cross-connect view.

connection connection-name

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

mtu size

The default MTU is 1500 bytes.

11. Configure an EVPN PW.

evpn local-service-id local-service-id remote-service-id remote-service-id [ tunnel-policy tunnel-policy-name ] [ pw-class class-name ]

Do not use this command together with the peer command for a cross-connect.

Mapping an AC to a cross-connect

About mapping an AC to a cross-connect

After you map an AC to a cross-connect, packets received from the mapped AC are forwarded to the PW or another AC bound to the cross-connect.

When you map 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.

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

This task is mutually exclusive with Ethernet link aggregation. If a Layer 3 Ethernet interface has been added to a link aggregation group, you cannot map the Layer 3 interface to a cross-connect, and vice versa.

Mapping a Layer 3 interface to a 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. Map a Layer 3 interface to the cross-connect.

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

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

Configuring EVPN VPWS multihoming

Restrictions and guidelines for EVPN VPWS multihoming

You must configure the same local and remote service IDs on the redundant PEs at a multihomed site.

As a best practice, set the same redundancy mode on the interfaces that act as ACs or are configured with ACs on the redundant PEs at a multihomed site.

You can assign ESIs to a main interface and its subinterfaces.

· If you assign an ESI to a subinterface, the subinterface-specific ESI and ES configuration take precedence over those configured on the main interface. The ES configuration includes the following:

¡ evpn df-election algorithm.

¡ evpn df-election preference.

¡ evpn df-election preference non-revertive.

¡ evpn timer es-delay.

· If you do not assign an ESI to a subinterface, it inherits the ESI and ES configuration (if configured) of the main interface. In this scenario, the ES configuration on the subinterface does not take effect.

If you set up an EVPN PW with a redundant PE at the local site, the device uses the BFD configuration in the PW class specified in the evpn local-service-id remote-service-id command.

· If the EVPN PW is a primary EVPN PW, the device establishes a dynamic BFD session for the EVPN PW.

· If the EVPN PW is a backup or ECMP EVPN PW, the device does not establish a dynamic BFD session for the EVPN PW.

Assigning an ESI to an interface

About this task

An ESI uniquely identifies an ES. The links on interfaces with the same ESI belong to the same ES. Traffic of the ES can be distributed among the links for load sharing.

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

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Assign an ESI to the interface.

esi esi-id

By default, no ESI is assigned to an interface.

Setting the redundancy mode on an interface

About this task

EVPN VPWS multihoming provides the single-active redundancy mode and all-active redundancy mode.

The redundant PEs at a dualhomed site each establish an EVPN PW to a remote PE. To use one PW as a backup of the other PW, use the single-active mode. To distribute traffic across the PWs for load sharing, use the all-active mode.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Set the redundancy mode.

evpn redundancy-mode { all-active | single-active }

By default, the all-active redundancy mode is used.

Configuring the DF election algorithm

About this task

At a multihomed EVPN network site, you can modify the DF election algorithm to control the DF election result.

Restrictions and guidelines

If ambiguous VLAN termination is enabled on a subinterface acting as an AC, do not configure the VLAN tag-based algorithm for DF election on the subinterface. Otherwise, traffic forwarding errors will occur.

You can configure the DF election algorithm in system view and in interface view. The global DF election algorithm takes effect on all ESs, and the interface-specific DF election algorithm takes effect only on the ESs on an interface. The interface-specific DF election algorithm takes precedence over the global DF election algorithm.

Configuring the DF election algorithm globally

1. Enter system view.

system-view

2. Configure the DF election algorithm.

evpn df-election algorithm algorithm

By default, the VLAN tag-based algorithm is used for DF election.

Configuring the DF election algorithm on an interface

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

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Configure the DF election algorithm.

evpn df-election algorithm algorithm

By default, the DF election algorithm specified in system view takes effect.

Configuring preference-based DF election

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

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Set the DF election preference.

evpn df-election preference preference

By default, the DF election preference is 32767.

The larger the value, the higher the preference.

Enabling AC state-based DF election

About this task

At a multihomed EVPN network site, all PEs in an ES participate in DF election by default, regardless of their AC states. If the AC on the PE elected as the DF is down, traffic forwarding will fail. You can configure this feature to resolve this issue.

After you configure this feature, a PE participates in DF election only when the AC on the PE is up. A PE determines that the AC on the remote PE is up only when it receives AD per ES and AD per EVI routes from the remote PE.

Restrictions and guidelines

This feature takes effect only when you enable this feature on all PEs in an ES.

Procedure

1. Enter system view.

system-view

2. Enable AC state-based DF election.

evpn df-election ac-influence enable

By default, AC state-based DF election is disabled.

Setting the DF election delay

About this task

The DF election can be triggered by site-facing interface status changes, redundant PE membership changes, and interface ESI changes. To prevent frequent DF elections from degrading network performance, set the DF election delay. The DF election delay defines the minimum interval allowed between two DF elections.

Procedure

1. Enter system view.

system-view

2. Set the DF election delay.

evpn multihoming timer df-delay delay-value

By default, the DF election delay is 3 seconds.

Enabling non-revertive mode for preference-based DF election

About this task

At a multihomed EVPN network site, configuration changes, device restarts, or process restarts will trigger DF re-election, and DF switchover might cause packet loss. You can configure this feature to resolve this issue.

For example, PE 1 and PE 2 are in the same ES, and PE 1 is the DF. When PE 1 restarts and PE 2 becomes the new DF, non-revertive mode for preference-based DF election works as follows:

· If PE 1 receives Ethernet segment routes from PE 2 after the restart, PE 1 compares the DF election preference in the Ethernet segment routes with the local DF election preference.

¡ If the local DF election preference is smaller than that in the received Ethernet segment routes, PE 1 uses the local DF election preference in the advertised Ethernet segment routes.

¡ If the local DF election preference is equivalent to that in the received Ethernet segment routes, PE 1 compares the IP addresses as follows:

- If PE 1's IP address is lower than PE 2's IP address, PE 1 uses the local DF election preference and the DP value of 0 in the advertised Ethernet segment routes.

- If PE 1's IP address is higher than PE 2's IP address, PE 1 uses the local DF election preference and the DP value of 1 in the advertised Ethernet segment routes.

¡ If the local DF election preference is larger than that in the received Ethernet segment routes, PE 1 uses the DF election preference in the received Ethernet segment routes and the DP value of 0 when advertising Ethernet segment routes.

· If PE 1 does not receive Ethernet segment routes from PE 2 after the restart, PE 1 uses the local DF election preference in the advertised Ethernet segment routes.

Restrictions and guidelines

As a best practice, configure this feature when the all-active redundancy mode is used, and do not configure this feature when the single-active redundancy mode is used.

When the DF restarts or the process restarts and a new DF is elected, the original DF will immediately advertise Ethernet segment routes after the restart to become the DF again. However, access-side connections restore slowly and packet loss might occur after DF switchover. To resolve this issue, configure this feature together with the Ethernet segment route advertisement delay feature on all PEs in an ES.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Enable non-revertive mode for preference-based DF election.

evpn df-election preference non-revertive

By default, non-revertive mode is disabled for preference-based DF election.

Configuring Ethernet segment route advertisement delay

About this task

When the DF restarts or the process restarts and a new DF is elected, the original DF will immediately advertise Ethernet segment routes after the restart to become the DF again. However, access-side connections restore slowly and packet loss might occur after DF switchover. To resolve this issue, perform this task to configure a PE to delay the advertisement of Ethernet segment routes.

Restrictions and guidelines

As a best practice, configure this feature when the all-active redundancy mode is used, and do not configure this feature when the single-active redundancy mode is used.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Configure Ethernet segment route advertisement delay when preference-based DF election is used.

evpn timer es-recovery recovery-time

By default, Ethernet segment route advertisement delay is disabled when preference-based DF election is used.

Enabling fast DF/BDF switchover

About this task

As shown in Figure 10, CE 1 is dualhomed to PE 1 (DF) and PE 2 (BDF) in an EVPN VPWS network. PE 2 cannot take over the DF role immediately when the AC on PE 1 fails, and traffic loss will occur as a result. To resolve this issue, set up a static BFD session between PE 1 and PE 2. You must configure the static BFD session to monitor the status of the local AC on PE 1 and enable PE 2 to monitor the status of the session. When the AC on PE 1 fails, the static BFD session goes down, and PE 2 can fast take over the DF role to reduce traffic loss.

Figure 10 Application scenario for fast DF/BDF switchover

Configuring the DF

1. Enter system view.

system-view

2. Create a static BFD session and configure it to monitor an AC-side interface.

bfd static session-name peer-ip ipv4-address [ vpn-instance vpn-instance-name ] source-ip ipv4-address discriminator local local-value remote remote-value track-interface interface-type interface-number

For more information about this command, see High Availability Command Reference.

Configuring the BDF

1. Enter system view.

system-view

2. Create a static BFD session.

bfd static session-name peer-ip ipv4-address [ vpn-instance vpn-instance-name ] source-ip ipv4-address discriminator local local-value remote remote-value

For more information about this command, see High Availability Command Reference.

3. Enter interface view.

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

¡ Enter FlexE logical interface view.

interface flexe interface-number

4. Enable the device to monitor the status of the static BFD session.

evpn track bfd session-name

By default, the device does not monitor the status of static BFD sessions.

Disabling advertisement of EVPN multihoming routes

About this task

EVPN multihoming routes include Ethernet auto-discovery routes and Ethernet segment routes.

In a multihomed EVPN network, perform this task on a redundant PE before you reboot it. This operation allows other PEs to refresh their EVPN routing table to prevent traffic interruption caused by the reboot.

Procedure

1. Enter system view.

system-view

2. Disable advertisement of EVPN multihoming routes and withdraw the EVPN multihoming routes that have been advertised to remote sites.

evpn multihoming advertise disable

By default, the device advertises EVPN multihoming routes.

Enabling cross-connects to ignore the state of ACs

About this task

This task helps reduce the traffic loss caused by AC failure at a multihomed EVPN VPWS network site that uses single-active redundancy mode.

At a multihomed EVPN VPWS network site that uses single-active redundancy mode, CE 1 is dualhomed to PE 1 and PE 2 through a smart trunk. PE 1 is the primary PE, and PE 2 is the secondary PE. When the AC on PE 1 fails, PE 1 and PE 2 act as follows:

· PE 1 withdraws advertised Ethernet auto-discovery routes.

· PE 2 brings up its AC and advertises Ethernet auto-discovery routes to remote PEs.

The remote PEs switch traffic to the paths to PE 2 only after receiving the Ethernet auto-discovery routes advertised by PE 2, and traffic loss occurs during path switchover. To resolve this issue, enable cross-connects to ignore the state of ACs on PE 2. This feature allows PE 2 to advertise Ethernet auto-discovery routes to remote PEs regardless of the state of ACs and speeds up path switchover when the AC on PE 1 fails.

Restrictions and guidelines for AC state ignore configuration

On a cross-connect, cross-connect-specific AC state ignore configuration takes precedence over global AC state ignore configuration.

Enabling cross-connects to ignore the state of ACs globally

1. Enter system view.

system-view

2. Enable cross-connects to ignore the state of ACs globally.

l2vpn ignore-ac-state [ evpn-vpws ]

By default, cross-connects does not ignore the state of ACs.

Configuring a cross-connect to ignore the state of ACs

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. Enable the cross-connect to ignore the state of ACs or disable a cross-connect from ignoring the state of ACs.

ignore-ac-state { enable | disable }

By default, a cross-connect uses the global AC state ignore configuration.

Enabling the device to monitor the BGP peer status of another local edge device

About this task

Perform this task on the CE-facing interfaces of the edge devices multihomed to a site to prevent device reboots from causing inter-site forwarding failure.

This task excludes unavailable edge devices from DF election at a multihomed site. After an edge device recovers from failure and brings up its CE-facing interface, it starts the advertisement delay timer for Ethernet segment routes and checks the status of the BGP peer specified in the evpn track peer command. If the BGP peer comes up before the timer expires, the edge device advertises Ethernet segment routes to the peer. If the BGP peer is still down when the timer expires, the edge device does not advertise Ethernet segment routes to the peer. The edge devices then perform DF election based on the Ethernet segment routes they have received.

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

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Enable the device to monitor the BGP peer status of another local edge device.

evpn track peer { peer-ipv4-address | peer-ipv6-address }

By default, the device does not monitor the BGP peer status of the other edge devices at a multihomed site.

4. Set the advertisement delay timer for Ethernet segment routes.

evpn timer es-delay delay-time

By default, advertisement of Ethernet segment routes is not delayed.

Configuring FRR for EVPN VPWS

Configuring local FRR

About this task

Local FRR enables two PEs at a multihomed EVPN VPWS network site to set up a bypass PW between them. This feature helps reduce the traffic loss caused by AC failure.

Restrictions and guidelines

On an EVPN instance, EVPN instance-specific local FRR configuration takes precedence over global local FRR configuration.

If you have executed the evpn frr local enable command on an EVPN instance, the undo evpn multihoming vpws-frr local command does not delete the bypass PW of the EVPN instance.

Enabling local FRR globally

1. Enter system view.

system-view

2. Enable local FRR globally.

evpn multihoming vpws-frr local

By default, local FRR is disabled globally.

Configuring local FRR on an EVPN instance

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter EVPN instance view.

evpn encapsulation mpls

4. Configure local FRR.

evpn frr local { disable | enable }

By default, an EVPN instance uses the global local FRR configuration of EVPN VPWS.

Configuring remote FRR

About this task

Remote FRR enables two PEs on an EVPN VPWS network to set up a primary PW and a backup PW between them to ensure high availability. The PEs use the primary PW to forward traffic as long as it is available. When the primary PW fails, the PEs switch traffic to the backup PW.

Restrictions and guidelines

On an EVPN instance, EVPN instance-specific remote FRR configuration takes precedence over global remote FRR configuration.

If you have executed the evpn frr remote enable command on an EVPN instance, the undo evpn vpws-frr remote command does not delete the backup PWs of the EVPN instance.

Enabling remote FRR globally

1. Enter system view.

system-view

2. Enable remote FRR globally.

evpn vpws-frr remote

By default, remote FRR is disabled globally.

Configuring remote FRR on an EVPN instance

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter EVPN instance view.

evpn encapsulation mpls

4. Configure remote FRR.

evpn frr remote { disable | enable }

By default, an EVPN instance uses the global remote FRR configuration of EVPN VPWS.

Testing the connectivity of an EVPN PW

Prerequisites for EVPN PW connectivity test

Before you ping or tracert a PW destination, make sure the specified PW has referenced a PW class for which the VCCV CC type is configured by using the vccv cc command.

Pinging a PW destination

About this task

Perform this task to test the connectivity of a PW when the PW has traffic loss or interruption issues in an EVPN VPWS network. The process of a ping operation is as follows:

1. The PW source PE sends MPLS echo requests to the PW destination PE based on the cross-connect group, and local and remote service IDs you specify.

2. The PW destination PE responds with MPLS echo replies.

3. The PW source PE outputs packet statistics and the test result based on the received MPLS echo replies.

Procecure

Execute the following command in any view.

Tracing the path to a PW destination

About this task

Perform this task to locate failed nodes on the path for a PW that has traffic loss or interruption issues in an EVPN VPWS network. The process of a tracert operation is as follows:

1. The PW source PE sends MPLS echo requests to the PW destination PE based on the cross-connect group, and local and remote service IDs you specify. The TTL in the IP header of the requests is set to 1.

2. The first hop on the path responds to the PW source PE with a TTL-expired ICMP error message.

3. The PW source PE sends MPLS echo requests with the TTL set to 2 if the PE receives the TTL-expired ICMP error message or has not received any packets within the timeout period.

4. The second hop responds with a TTL-expired ICMP error message.

5. This process continues until an MPLS echo request reaches the PW destination PE or the maximum TTL value is reached. If an MPLS echo request reaches the PW destination PE, the PW destination PE sends an MPLS echo reply to the PW source PE.

6. The PW source PE outputs packet statistics and the test result based on the received ICMP error messages and whether an MPLS echo reply is received.

Procecure

Execute the following command in any view.

Verifying and maintaining EVPN VPWS

Displaying EVPN running status and statistics

Perform display tasks in any view.

· Display BGP 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 BGP peer or peer group information.

display bgp [ instance instance-name ] peer l2vpn evpn [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ]

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

· Display information about BGP update groups.

display bgp [ instance instance-name ] update-group l2vpn evpn [ ipv4-address ]

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

· Display BGP EVPN routes.

display bgp [ instance instance-name ] l2vpn evpn [ peer { ipv4-address | ipv6-address } { advertised-routes | received-routes } [ statistics ] | [ route-distinguisher route-distinguisher | route-type { auto-discovery | es | imet | mac-ip } ] * [ { evpn-route route-length | evpn-prefix } [ advertise-info | as-path | cluster-list | community | ext-community ] | ipv4-address | ipv6-address | mac-address ] | statistics ]

display bgp [ instance instance-name ] l2vpn evpn [ route-distinguisher route-distinguisher ] [ statistics ] community [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] [ whole-match ]

display bgp [ instance instance-name ] l2vpn evpn [ route-distinguisher route-distinguisher ] [ statistics ] community-list { basic-community-list-number | comm-list-name | adv-community-list-number } [ whole-match ]

display bgp [ instance instance-name ] l2vpn evpn [ route-distinguisher route-distinguisher ] [ statistics ] ext-community [ bandwidth link-bandwidth-value | rt route-target | soo site-of-origin | color color ]&<1-32> [ whole-match ]

· Display EVPN routing table information.

display evpn routing-table [ ipv6 ] { public-instance | vpn-instance vpn-instance-name } [ count ]

· Display EVPN ES information.

display evpn es { local [ count | [ xconnect-group group-name ] [ esi esi-id ] [ verbose ] ] | remote [ xconnect-group group-name ] [ esi esi-id ] [ nexthop next-hop ] [ verbose ] }

· Display DF election information.

display evpn df-election [ xconnect-group group-name ] [ esi esi-id ]

Displaying cross-connect group configuration and running status

To display EVPN information about cross-connects, execute the following command in any view:

display evpn xconnect-group [ name group-name [ connection connection-name ] ] [ count ]

Displaying AC configuration and running status

Perform display tasks in any view.

· Display AC forwarding information.

display l2vpn forwarding ac [ xconnect-group group-name ] [ slot slot-number ] [ verbose ]

For more information about this command, see MPLS L2VPN commands in MPLS Command Reference.

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

display l2vpn interface [ xconnect-group group-name | interface-type interface-number ] [ verbose ]

For more information about this command, see MPLS L2VPN commands in MPLS Command Reference.

Displaying PW configuration and running status

Perform display tasks in any view.

· Display PW forwarding information.

display l2vpn forwarding pw [ xconnect-group group-name ] [ slot slot-number ] [ verbose ]

For more information about this command, see MPLS L2VPN commands in MPLS Command Reference.

· Display L2VPN PW information.

display l2vpn pw [ xconnect-group group-name ] [ protocol { bgp | evpn | ldp | static } ] [ verbose ]

For more information about this command, see MPLS L2VPN commands in MPLS Command Reference.

· Display PW class information.

display l2vpn pw-class [ class-name ]

For more information about this command, see MPLS L2VPN commands in MPLS Command Reference.

· Display BFD information for PWs.

display l2vpn pw bfd [ peer peer-ip remote-service-id remote-service-id ]

For more information about this command, see MPLS OAM commands in MPLS Command Reference.

EVPN VPWS configuration examples

Example: Configuring a remote connection between singlehomed sites

Network configuration

As shown in Figure 11, set up a remote connection between CE 1 and CE 2 for users in site 1 and site 2 to communicate through EVPN VPWS over the MPLS or IP backbone network.

Figure 11 Network diagram

‌

Device	Interface	IP address	Device	Interface	IP address
CE 1	GE0/0/1	10.1.1.10/24	P	Loop0	3.3.3.3/32
PE 1	Loop0	1.1.1.1/32		GE0/0/1	11.1.1.2/24
	GE0/0/1	N/A		GE0/0/2	11.1.2.2/24
	GE0/0/2	11.1.1.1/24	PE 2	Loop0	2.2.2.2/32
CE 2	GE0/0/1	10.1.1.20/24		GE0/0/1	N/A
				GE0/0/2	11.1.2.1/24

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 0/0/1

[CE1-GigabitEthernet0/0/1] ip address 10.1.1.10 24

[CE1-GigabitEthernet0/0/1] quit

2. Configure PE 1:

# Configure the 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 0/0/2 (the interface connected to the P device), and enable LDP on the interface.

[PE1] interface gigabitethernet 0/0/2

[PE1-GigabitEthernet0/0/2] ip address 11.1.1.1 24

[PE1-GigabitEthernet0/0/2] mpls enable

[PE1-GigabitEthernet0/0/2] mpls ldp enable

[PE1-GigabitEthernet0/0/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 11.1.1.0 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 an IBGP connection to PE 2, and enable BGP to advertise L2VPN information to PE 2.

[PE1] bgp 100

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

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

[PE1-bgp-default] address-family l2vpn evpn

[PE1-bgp-default-evpn] peer 2.2.2.2 enable

[PE1-bgp-default-evpn] peer 2.2.2.2 advertise encap-type mpls

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] evpn encapsulation mpls

[PE1-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE1-xcg-vpna-evpn-mpls] vpn-target 1:1 export-extcommunity

[PE1-xcg-vpna-evpn-mpls] vpn-target 1:1 import-extcommunity

[PE1-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE1-xcg-vpna] connection pw1

[PE1-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE1-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE1-xcg-vpna-pw1] evpn local-service-id 1 remote-service-id 2

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

3. Configure the P device:

# Configure the LSR ID.

<P> system-view

[P] interface loopback 0

[P-LoopBack0] ip address 3.3.3.3 32

[P-LoopBack0] quit

[P] mpls lsr-id 3.3.3.3

# Enable global LDP.

[P] mpls ldp

[P-ldp] quit

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

[P] interface gigabitethernet 0/0/1

[P-GigabitEthernet0/0/1] ip address 11.1.1.2 24

[P-GigabitEthernet0/0/1] mpls enable

[P-GigabitEthernet0/0/1] mpls ldp enable

[P-GigabitEthernet0/0/1] quit

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

[P] interface gigabitethernet 0/0/2

[P-GigabitEthernet0/0/2] ip address 11.1.2.2 24

[P-GigabitEthernet0/0/2] mpls enable

[P-GigabitEthernet0/0/2] mpls ldp enable

[P-GigabitEthernet0/0/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 11.1.1.0 0.0.0.255

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

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

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

[P-ospf-1] quit

4. Configure PE 2:

# Configure the 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 0/0/2 (the interface connected to the P device), and enable LDP on the interface.

[PE2] interface gigabitethernet 0/0/2

[PE2-GigabitEthernet0/0/2] ip address 11.1.2.1 24

[PE2-GigabitEthernet0/0/2] mpls enable

[PE2-GigabitEthernet0/0/2] mpls ldp enable

[PE2-GigabitEthernet0/0/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 2.2.2.2 0.0.0.0

[PE2-ospf-1-area-0.0.0.0] network 11.1.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 1.1.1.1 as-number 100

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

[PE2-bgp-default] address-family l2vpn evpn

[PE2-bgp-default-evpn] peer 1.1.1.1 enable

[PE2-bgp-default-evpn] peer 1.1.1.1 advertise encap-type mpls

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] evpn encapsulation mpls

[PE2-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE2-xcg-vpna-evpn-mpls] vpn-target 1:1 export-extcommunity

[PE2-xcg-vpna-evpn-mpls] vpn-target 1:1 import-extcommunity

[PE2-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE2-xcg-vpna] connection pw1

[PE2-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE2-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE2-xcg-vpna-pw1] evpn local-service-id 2 remote-service-id 1

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 0/0/1

[CE2-GigabitEthernet0/0/1] ip address 10.1.1.20 24

[CE2-GigabitEthernet0/0/1] quit

Verifying the configuration

# Verify that an EVPN PW has been established between PE 1 and PE 2.

[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

2.2.2.2 2 710127/710127 EVPN M 0 Up

# Verify that the EVPN information about the cross-connect on PE 1 is correct.

[PE1] display evpn xconnect-group

Flags: P - Primary, B - Backup, C - Control word

Xconnect group name: vpna

Connection Name: pw1

ESI : 0000.0000.0000.0000.0000

Local service ID : 1

Remote service ID : 2

Control word : Disable

In label : 710127

Local MTU : 1500

AC state : Up

PW type : Ethernet

Nexthop ESI Out label Flags MTU State

2.2.2.2 0000.0000.0000.0000.0000 710127 P 1500 Up

# Verify that the EVPN information about the cross-connect on PE 2 is correct.

[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

1.1.1.1 1 710127/710127 EVPN M 0 Up

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

Example: Configuring EVPN VPWS multihoming

Network configuration

As shown in Figure 12, configure EVPN VPWS for dualhomed site 1 and singlehomed site 2 to communicate over the MPLS or IP backbone network.

Figure 12 Network diagram

‌

Device	Interface	IP address	Device	Interface	IP address
PE 1	Loop0	192.1.1.1/32	CE 1	GE0/0/1	100.1.1.1/24
	GE0/0/1	N/A	CE 2	GE0/0/1	100.1.1.2/24
	GE0/0/2	10.1.1.1/24	PE 3	Loop0	192.3.3.3/32
	GE0/0/3	10.1.3.1/24		GE0/0/1	N/A
PE 2	Loop0	192.2.2.2/32		GE0/0/2	10.1.1.2/24
	GE0/0/1	N/A		GE0/0/3	10.1.2.2/24
	GE0/0/2	10.1.2.1/24
	GE0/0/3	10.1.3.2/24

Procedure

1. Configure CE 1:

# Create dynamic Layer 3 aggregate interface 1 and assign it an IP address.

<CE1> system-view

[CE1] interface route-aggregation 1

[CE1-Route-Aggregation1] ip address 100.1.1.1 24

[CE1-Route-Aggregation1] quit

# Assign GigabitEthernet 0/0/1 and GigabitEthernet 0/0/2 to aggregation group 1.

[CE1] interface gigabitethernet 0/0/1

[CE1-GigabitEthernet0/0/1] port link-aggregation group 1

[CE1-GigabitEthernet0/0/1] quit

[CE1] interface gigabitethernet 0/0/2

[CE1-GigabitEthernet0/0/2] port link-aggregation group 1

[CE1-GigabitEthernet0/0/2] quit

2. Configure PE 1:

# Configure the 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 0/0/2 (the interface connected to PE 3), and enable LDP on the interface.

[PE1] interface gigabitethernet 0/0/2

[PE1-GigabitEthernet0/0/2] ip address 10.1.1.1 24

[PE1-GigabitEthernet0/0/2] mpls enable

[PE1-GigabitEthernet0/0/2] mpls ldp enable

[PE1-GigabitEthernet0/0/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.0 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 10.1.3.0 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 IBGP connections to PE 2 and PE 3, and enable BGP to advertise routes to PE 2 and PE 3.

[PE1] bgp 100

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

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

[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 evpn

[PE1-bgp-default-evpn] peer 192.2.2.2 enable

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

[PE1-bgp-default-evpn] peer 192.2.2.2 advertise encap-type mpls

[PE1-bgp-default-evpn] peer 192.3.3.3 advertise encap-type mpls

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

# Assign an ESI to GigabitEthernet 0/0/1 and set its redundancy mode to all-active.

[PE1] interface gigabitethernet 0/0/1

[PE1-GigabitEthernet0/0/1] esi 1.1.1.1.1

[PE1-GigabitEthernet0/0/1] evpn redundancy-mode all-active

[PE1-GigabitEthernet0/0/1] quit

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] evpn encapsulation mpls

[PE1-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE1-xcg-vpna-evpn-mpls] vpn-target 1:1 export-extcommunity

[PE1-xcg-vpna-evpn-mpls] vpn-target 1:1 import-extcommunity

[PE1-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] connection pw1

[PE1-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE1-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE1-xcg-vpna-pw1] evpn local-service-id 1 remote-service-id 2

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

# Associate GigabitEthernet 0/0/2 with track entry 1.

[PE1] track 1 interface gigabitethernet 0/0/2

[PE1-track-1] quit

# Configure CLI-defined monitor policy 1 to associate GigabitEthernet 0/0/2 with GigabitEthernet 0/0/1. This setting allows PE 1 to shut down GigabitEthernet 0/0/1 when GigabitEthernet 0/0/2 goes down.

[PE1] rtm cli-policy policy1

[PE1-rtm-policy1] event track 1 state negative

[PE1-rtm-policy1] action 0 cli system-view

[PE1-rtm-policy1] action 1 cli interface gigabitethernet 0/0/1

[PE1-rtm-policy1] action 2 cli shutdown

[PE1-rtm-policy1] user-role network-admin

[PE1-rtm-policy1] commit

[PE1-rtm-policy1] quit

3. Configure PE 2:

# Configure the LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.2.2.2 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

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

[PE2] interface gigabitethernet 0/0/2

[PE2-GigabitEthernet0/0/2] ip address 10.1.2.1 24

[PE2-GigabitEthernet0/0/2] mpls enable

[PE2-GigabitEthernet0/0/2] mpls ldp enable

[PE2-GigabitEthernet0/0/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.1.2.0 0.0.0.255

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

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

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

[PE2-ospf-1] quit

# Create IBGP connections to PE 1 and PE 3, and enable BGP to advertise routes to PE 1 and PE 3.

[PE2] bgp 100

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

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

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

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

[PE2-bgp-default] address-family l2vpn evpn

[PE2-bgp-default-evpn] peer 192.1.1.1 enable

[PE2-bgp-default-evpn] peer 192.3.3.3 enable

[PE2-bgp-default-evpn] peer 192.1.1.1 advertise encap-type mpls

[PE2-bgp-default-evpn] peer 192.3.3.3 advertise encap-type mpls

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

# Assign an ESI to GigabitEthernet 0/0/1 and set its redundancy mode to all-active.

[PE2] interface gigabitethernet 0/0/1

[PE2-GigabitEthernet0/0/1] esi 1.1.1.1.1

[PE2-GigabitEthernet0/0/1] evpn redundancy-mode all-active

[PE2-GigabitEthernet0/0/1] quit

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] evpn encapsulation mpls

[PE2-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE2-xcg-vpna-evpn-mpls] vpn-target 1:1 export-extcommunity

[PE2-xcg-vpna-evpn-mpls] vpn-target 1:1 import-extcommunity

[PE2-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] connection pw1

[PE2-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE2-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE2-xcg-vpna-pw1] evpn local-service-id 1 remote-service-id 2

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

# Associate GigabitEthernet 0/0/2 with track entry 1.

[PE2] track 1 interface gigabitethernet 0/0/2

[PE2-track-1] quit

# Configure CLI-defined monitor policy 1 to associate GigabitEthernet 0/0/2 with GigabitEthernet 0/0/1. This setting allows PE 2 to shut down GigabitEthernet 0/0/1 when GigabitEthernet 0/0/2 goes down.

[PE2] rtm cli-policy policy1

[PE2-rtm-policy1] event track 1 state negative

[PE2-rtm-policy1] action 0 cli system-view

[PE2-rtm-policy1] action 1 cli interface gigabitethernet 0/0/1

[PE2-rtm-policy1] action 2 cli shutdown

[PE2-rtm-policy1] user-role network-admin

[PE2-rtm-policy1] commit

[PE2-rtm-policy1] quit

4. Configure PE 3:

# Configure the LSR ID.

<PE3> system-view

[PE3] interface loopback 0

[PE3-LoopBack0] ip address 192.3.3.3 32

[PE3-LoopBack0] quit

[PE3] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[PE3] l2vpn enable

# Enable global LDP.

[PE3] mpls ldp

[PE3-ldp] quit

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

[PE3] interface gigabitethernet 0/0/2

[PE3-GigabitEthernet0/0/2] ip address 10.1.1.2 24

[PE3-GigabitEthernet0/0/2] mpls enable

[PE3-GigabitEthernet0/0/2] mpls ldp enable

[PE3-GigabitEthernet0/0/2] quit

[PE3] interface gigabitethernet 0/0/3

[PE3-GigabitEthernet0/0/3] ip address 10.1.2.2 24

[PE3-GigabitEthernet0/0/3] mpls enable

[PE3-GigabitEthernet0/0/3] mpls ldp enable

[PE3-GigabitEthernet0/0/3] quit

# Configure OSPF for LDP to create LSPs.

[PE3] ospf

[PE3-ospf-1] area 0

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

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

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

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

[PE3-ospf-1] quit

# Create IBGP connections to PE 1 and PE 2, and enable BGP to advertise routes to PE 1 and PE 2.

[PE3] bgp 100

[PE3-bgp-default] peer 192.1.1.1 as-number 100

[PE3-bgp-default] peer 192.1.1.1 connect-interface loopback 0

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

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

[PE3-bgp-default] address-family l2vpn evpn

[PE3-bgp-default-evpn] peer 192.1.1.1 enable

[PE3-bgp-default-evpn] peer 192.2.2.2 enable

[PE3-bgp-default-evpn] peer 192.1.1.1 advertise encap-type mpls

[PE3-bgp-default-evpn] peer 192.2.2.2 advertise encap-type mpls

[PE3-bgp-default-evpn] quit

[PE3-bgp-default] quit

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE3] xconnect-group vpna

[PE3-xcg-vpna] evpn encapsulation mpls

[PE3-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE3-xcg-vpna-evpn-mpls] vpn-target 1:1 export-extcommunity

[PE3-xcg-vpna-evpn-mpls] vpn-target 1:1 import-extcommunity

[PE3-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE3] xconnect-group vpna

[PE3-xcg-vpna] connection pw1

[PE3-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE3-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE3-xcg-vpna-pw1] evpn local-service-id 2 remote-service-id 1

[PE3-xcg-vpna-pw1] quit

[PE3-xcg-vpna] quit

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 0/0/1

[CE2-Vlan-interface10] ip address 100.1.1.2 24

[CE2-Vlan-interface10] quit

Verifying the configuration

# Verify that PE 1 has established EVPN PWs to PE 2 and PE 3.

<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 2 710263/710265 EVPN M 0 Up

# Verify that the EVPN information about the cross-connect on PE 1 is correct.

<PE1> display evpn xconnect-group

Flags: P - Primary, B - Backup, C - Control word

Xconnect group name: vpna

Connection name: 1

ESI : 0001.0001.0001.0001.0001

Local service ID : 1

Remote service ID : 2

Control word : Disabled

In label : 710263

Local MTU : 1500

AC state : Up

PW type : Ethernet

Nexthop ESI Out label Flags MTU state

192.3.3.3 0000.0000.0000.0000.0000 710265 P 1500 Up

# Verify that PE 1 has local ES information.

<PE1> display evpn es local

Redundancy mode: A - All-active, S - Single-active

Xconnect-group name : vpna

ESI Tag ID DF address Mode State ESI label

0001.0001.0001.0001.0001 - 192.1.1.1 A Up -

# Verify that PE 1 has remote ES information.

<PE1> display evpn es remote

Control Flags: P - Primary, B - Backup, C - Control word

Xconnect group name : vpna

ESI : 0001.0001.0001.0001.0001

Ethernet segment routes :

192.2.2.2

A-D per ES routes :

Peer IP Remote Redundancy mode

192.2.2.2 All-active

A-D per EVI routes :

Tag ID Peer IP Control Flags

1 192.2.2.2 B

# Verify that PE 2 has established EVPN PWs to PE 1 and PE 3.

<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.3.3.3 2 710124/710265 EVPN M 1 Up

# Verify that PE 3 has established EVPN PWs to PE 1 and PE 2.

<PE3> 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: vpna

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

192.1.1.1 1 710265/710263 EVPN E 0 Up

192.2.2.2 1 710265/710124 EVPN E 0 Up

# Verify that CE 1 and CE 2 can ping each other when the PW on PE 1 or PE 2 fails. (Details not shown.)

Example: Configuring PW concatenation

Network configuration

As shown in Figure 13:

· Set up an MPLS TE tunnel between each PE and the P device, and configure each MPLS TE tunnel to convey an EVPN PW.

· Concatenate the EVPN PWs on the P device for the CEs to communicate at Layer 2 over the MPLS backbone.

Figure 13 Network diagram

‌

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

Procedure

1. Configure CE 1.

<CE1> system-view

[CE1] interface gigabitethernet 0/0/1

[CE1-GigabitEthernet0/0/1] ip address 100.1.1.1 24

[CE1-GigabitEthernet0/0/1] quit

2. Configure PE 1:

# Configure the 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

# Set up an MPLS TE tunnel between PE 1 and the P device as described in MPLS TE configuration in MPLS Configuration Guide.

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE1] xconnect-group vpna

[PE1-xcg-vpna] evpn encapsulation mpls

[PE1-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE1-xcg-vpna-evpn-mpls] vpn-target 1:1 export-extcommunity

[PE1-xcg-vpna-evpn-mpls] vpn-target 1:2 import-extcommunity

[PE1-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE1-xcg-vpna] connection pw1

[PE1-xcg-vpna-pw1] evpn local-service-id 2 remote-service-id 1

[PE1-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE1-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

# Create an IBGP connection to the P device, and enable BGP to advertise BGP EVPN routes to the P device.

[PE1] bgp 100

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

[PE1-bgp-default] peer 192.4.4.4 connect-interface LoopBack0

[PE1-bgp-default] address-family l2vpn evpn

[PE1-bgp-default-evpn] peer 192.4.4.4 enable

[PE1-bgp-default-evpn] peer 192.4.4.4 advertise encap-type mpls

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

3. Configure the P device:

# Configure the 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

# Set up an MPLS TE tunnel to each PE as described in MPLS TE configuration in MPLS Configuration Guide.

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[P] xconnect-group vpna

[P-xcg-vpna] evpn encapsulation mpls

[P-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[P-xcg-vpna-evpn-mpls] vpn-target 1:2 export-extcommunity

[P-xcg-vpna-evpn-mpls] vpn-target 1:1 1:3 import-extcommunity

[P-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and create two EVPN PWs on the cross-connect.

[P-xcg-vpna] connection pw1

[P-xcg-vpna-pw1] evpn local-service-id 1 remote-service-id 2

[P-xcg-vpna-pw1] evpn local-service-id 3 remote-service-id 4

[P-xcg-vpna-pw1] quit

[P-xcg-vpna] quit

# Create an IBGP connection to each PE, and enable BGP to advertise BGP EVPN routes to the PEs.

[P] bgp 100

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

[P-bgp-default] peer 192.2.2.2 connect-interface LoopBack0

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

[P-bgp-default] peer 192.3.3.3 connect-interface LoopBack0

[P-bgp-default] address-family l2vpn evpn

[P-bgp-default-evpn] peer 192.2.2.2 enable

[P-bgp-default-evpn] peer 192.3.3.3 enable

[P-bgp-default-evpn] peer 192.2.2.2 advertise encap-type mpls

[P-bgp-default-evpn] peer 192.3.3.3 advertise encap-type mpls

[P-bgp-default-evpn] quit

[P-bgp-default] quit

4. Configure PE 2:

# Configure the 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

# Set up an MPLS TE tunnel between PE 2 and the P device as described in MPLS TE configuration in MPLS Configuration Guide.

# Create a cross-connect group named vpna, create an EVPN instance for it, and enable MPLS encapsulation. Configure an RD and route targets for the EVPN instance.

[PE2] xconnect-group vpna

[PE2-xcg-vpna] evpn encapsulation mpls

[PE2-xcg-vpna-evpn-mpls] route-distinguisher 1:1

[PE2-xcg-vpna-evpn-mpls] vpn-target 1:3 export-extcommunity

[PE2-xcg-vpna-evpn-mpls] vpn-target 1:2 import-extcommunity

[PE2-xcg-vpna-evpn-mpls] quit

# Create cross-connect pw1 and map GigabitEthernet 0/0/1 to it. Create an EVPN PW on the cross-connect.

[PE2-xcg-vpna] connection pw1

[PE2-xcg-vpna-pw1] evpn local-service-id 4 remote-service-id 3

[PE2-xcg-vpna-pw1] ac interface gigabitethernet 0/0/1

[PE2-xcg-vpna-pw1-GigabitEthernet0/0/1] quit

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

# Create an IBGP connection to the P device, and enable BGP to advertise BGP EVPN routes to the P device.

[PE2] bgp 100

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

[PE2-bgp-default] peer 192.4.4.4 connect-interface LoopBack0

[PE2-bgp-default] address-family l2vpn evpn

[PE2-bgp-default-evpn] peer 192.4.4.4 enable

[PE2-bgp-default-evpn] peer 192.4.4.4 advertise encap-type mpls

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

5. Configure CE 2.

<CE2> system-view

[CE2] interface gigabitethernet 0/0/1

[CE2-GigabitEthernet0/0/1] ip address 100.1.1.2 24

[CE2-GigabitEthernet0/0/1] quit

Verifying the configuration

# Verify that an EVPN 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.4.4.4 1 1151/1150 EVPN M 0 Up

# Verify that two EVPN PWs are concatenated 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: vpna

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

192.2.2.2 2 1150/1151 EVPN M 0 Up

192.3.3.3 4 1151/1151 EVPN M 1 Up

# Verify that an EVPN 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: vpn1a

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

192.4.4.4 3 1151/1151 EVPN M 0 Up

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

13-EVPN Configuration Guide

Public tunnel establishment

PW establishment

AC establishment

About this task

Redundancy mode

VLAN tag-based DF election

Preference-based DF election

About FRR

Local FRR

Remote FRR

Prerequisites for EVPN VPWS

Prerequisites

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Configuring a cross-connect

Restrictions and guidelines

Procedure

Configuring a PW class

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Mapping a Layer 3 interface to a cross-connect

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Configuring the DF election algorithm globally

Configuring the DF election algorithm on an interface

Configuring preference-based DF election

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Configuring the DF

Configuring the BDF

About this task

Procedure

About this task

Restrictions and guidelines for AC state ignore configuration

Enabling cross-connects to ignore the state of ACs globally

Configuring a cross-connect to ignore the state of ACs

About this task

Procedure

About this task

Restrictions and guidelines

Enabling local FRR globally

Configuring local FRR on an EVPN instance

About this task

Restrictions and guidelines

Enabling remote FRR globally

Configuring remote FRR on an EVPN instance

About this task

Procecure

About this task

Procecure

Displaying AC configuration and running status

EVPN VPWS configuration examples

Network configuration

Procedure