15-EVPN Configuration Guide

HomeSupportResource CenterSwitchesS12500X-AF SeriesS12500X-AF SeriesTechnical DocumentsConfigure & DeployConfiguration GuidesH3C S12500X-AF Switch Series Configuration Guides(R3606)-6W10015-EVPN Configuration Guide
03-EVPN VPWS configuration
Title Size Download
03-EVPN VPWS configuration 756.83 KB

Contents

Configuring EVPN VPWS·· 1

About EVPN VPWS· 1

EVPN VPWS network model 1

Remote connection establishment 1

EVPN VPWS multihoming· 2

FRR for EVPN VPWS· 4

Control word· 4

PW concatenation· 5

Inter-AS communication of EVPN VPWS· 6

EVPN VPWS tasks at a glance· 8

Configuring a remote connection· 8

Configuring PW concatenation· 9

Prerequisites for EVPN VPWS· 9

Enabling L2VPN· 9

Configuring a Layer 3 interface with Ethernet or VLAN encapsulation· 10

Configuring an Ethernet service instance on an interface· 10

Configuring EVPN route advertisement 11

Restrictions and guidelines for EVPN route advertisement configuration· 11

Enabling BGP to advertise BGP EVPN routes· 11

Configuring optimal route selection and route advertisement settings· 12

Maintaining BGP sessions· 13

Configuring a cross-connect 14

Configuring a PW·· 14

Configuring a PW class· 14

Configuring an EVPN PW·· 15

Mapping an AC to a cross-connect 16

About mapping an AC to a cross-connect 16

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

Mapping a Layer 3 interface to a cross-connect 16

Mapping an Ethernet service instance to a cross-connect 16

Configuring EVPN VPWS multihoming· 17

Restrictions and guidelines for EVPN VPWS multihoming· 17

Assigning an ESI to an interface· 17

Setting the redundancy mode on an interface· 17

Setting the DF election delay· 18

Enabling fast DF/BDF switchover 18

Disabling advertisement of EVPN multihoming routes· 19

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

Configuring FRR for EVPN VPWS· 21

Configuring local FRR· 21

Configuring remote FRR· 21

Display and maintenance commands for EVPN VPWS· 22

EVPN VPWS configuration examples· 23

Example: Configuring a remote connection between singlehomed sites· 23

Example: Configuring EVPN VPWS multihoming· 28

Example: Configuring PW concatenation· 35

Example: Configuring inter-AS option A· 39

Example: Configuring inter-AS option B· 45

Example: Configuring inter-AS option C· 52

Example: Configure FRR for EVPN VPWS· 59

 


Configuring EVPN VPWS

About EVPN VPWS

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. Typical ACs include Ethernet interfaces and VLANs.

·     Pseudowire (PW)—A virtual bidirectional connection between two PEs. A PW comprises a pair of virtual links 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 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 or MPLS TE 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 local service ID through Ethernet auto-discovery routes and compares received local service IDs with its remote service ID. A PE establishes a unidirectional virtual link to a peer If the local service ID advertised by the peer matches the remote service ID. PW establishment is finished when two virtual links 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, Layer 3 Ethernet subinterface, or Ethernet service instance on a PE. An Ethernet service instance is created on a Layer 2 Ethernet interface to match incoming customer traffic on that interface based on a frame match criterion.

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 "DF election". To ensure quick failover, EAA CLI-defined monitor policies and Track are configured on the CE-facing physical interface and the transport-facing physical interface used for establishing the main PW on PE 1. When the underlay network is disconnected, PE 1 shuts down the CE-facing physical interface so all traffic of CE 1 is forwarded through PE 2. For more information about EAA, see Network Management and Monitoring Configuration Guide.

Figure 3 Single-active mode

 

·     All-active mode—This mode allows all redundant PWs to a multihomed site to load share traffic. To ensure quick failover, EAA CLI-defined monitor policies and Track are configured on the CE-facing physical interface and the transport-facing physical interface used for establishing a PW on each redundant PE.

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 by using the following procedure:

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 4 as an example to explain the DF election procedure:

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

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

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

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

Figure 4 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 remote 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 5, 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.

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

PW concatenation

As shown in Figure 6, EVPN VPWS supports concatenating two or more PWs into one PW. PW concatenation allows two PEs that do not have an end-to-end public tunnel between them to communicate. An intermediate PE forwards packets between two concatenated PWs as follows:

1.     Removes the tunnel identifier and PW label from the packets received on one PW.

2.     Encapsulates the packets with the label of another PW and forwards them through the public tunnel that conveys this PW.

Two PWs are concatenated by creating them on the same cross-connect. For example, to concatenate PW 1 and PW 2 in Figure 6, create them on the same cross-connect on PE 2.

Figure 6 PW concatenation

 

PW concatenation includes intra-AS PW concatenation and inter-AS PW concatenation.

·     Intra-AS PW concatenation—Concatenates PWs within an AS. As shown in Figure 7, all PEs are in the same AS, and no end-to-end public tunnel exists between PE 1 and PE 4. By concatenating PW 1 and PW 2, you can enable PE 1 and PE 4 to communicate through the existing public tunnels instead of creating a new one.

Figure 7 Intra-AS PW concatenation

 

·     Inter-AS PW concatenation—Concatenates PWs in different ASs. For more information, see "Inter-AS option B."

Inter-AS communication of EVPN VPWS

In an inter-AS networking scenario, multiple sites of an EVPN VPWS network are connected to multiple ISPs in different ASs, or to multiple ASs of an ISP.

EVPN VPWS provides the following inter-AS communication solutions:

·     Inter-AS option A—Associates the AC between ASBRs with each EVPN PW established between a PE and ASBR pair.

·     Inter-AS option B—Establishes an EVPN PW between ASBRs and concatenates it with the EVPN PWs established between PE and ASBR pairs.

·     Inter-AS option C—Establishes an EVPN PW between PEs in different ASs through a multihop MP-EGBP session.

Inter-AS option A

As shown in Figure 8, in this solution, PEs of two ASs are directly connected, and each PE is also the ASBR of its AS. Each PE treats the other as a CE and associates its EVPN PW with the interface facing the peer PE for inter-AS communication.

This solution features simple implementation. You need to configure only EVPN PW and AC associations for each site on the PEs that act as ASBRs. However, the management workload increases if more sites are attached to the ASBRs.

Figure 8 Inter-AS option A network model

 

Inter-AS option B

As shown in Figure 9, in this solution, an EVPN PW is established between the ASBRs for inter-AS communication. The ASBRs uses MP-EBGP to exchange BGP EVPN routes to establish the EVPN PW. The PE and the ASBR in each AS use MP-IBGP to establish an EVPN PW. The EVPN PWs between the ASBRs and between each PE and ASBR pair are concatenated to forward inter-AS traffic.

This solution provides better scalability than inter-AS option A. To use this solution, you need to configure PW concatenation for each pair of sites.

Figure 9 Inter-AS option B network model

 

Inter-AS option C

As shown in Figure 10, in this solution, PEs in different ASs establish a multihop MP-EGBP session to exchange BGP EVPN routes and create an EVPN PW. Each PE must have a route to the peer PE and a label for the route so that the inter-AS public tunnel can be set up between the PEs. Inter-AS option C sets up a public tunnel by using the following methods:

·     A label distribution protocol within the AS, for example, LDP.

·     Labeled IPv4 unicast route advertisement by ASBRs through BGP.

Labeled IPv4 unicast route advertisement refers to the process of assigning MPLS labels to IPv4 unicast routes and advertising IPv4 unicast routes and their labels.

Figure 10 Inter-AS option C network model

 

The following is the process for setting up a public tunnel between PE 1 and PE 2 in Figure 10:

1.     Within AS 100, the public tunnel from ASBR 1 to PE 1 is set up by using a label distribution protocol, for example, LDP.

Assume that the outgoing label for the public tunnel on ASBR 1 is L1.

2.     ASBR 1 advertises labeled IPv4 unicast routes to ASBR 2 through EBGP.

The route destined for PE 1 and the label (L2) assigned by ASBR 1 to the route are advertised from ASBR 1 to ASBR 2. The next hop of the route is ASBR 1. The public tunnel from ASBR 2 to ASBR 1 is set up. The incoming label for the public tunnel on ASBR 1 is L2.

3.     ASBR 2 advertises labeled IPv4 unicast routes to PE 2 through IBGP.

The route destined for PE 1 and the label (L3) assigned by ASBR 2 to the route are advertised from ASBR 2 to PE 2. The next hop for the route is ASBR 2. The public tunnel from PE 2 to ASBR 2 is set up. The incoming label for the public tunnel on ASBR 2 is L3, and the outgoing label is L2.

4.     MPLS packets cannot be forwarded directly from PE 2 to ASBR 2. Within AS 200, the public tunnel from PE 2 to ASBR 2 is required to be set up hop by hop through a label distribution protocol, for example, LDP.

Assume that the outgoing label for the public tunnel on PE 3 is Lv.

After route advertisement and public tunnel setup, PE 1 and PE 2 set up a multihop MP-EBGP session to establish an EVPN PW. You must associate the EVPN PW with an AC on PE 1 and PE 2 to enable inter-AS forwarding.

To improve scalability, you can specify a RR in each AS to exchange BGP EVPN routes with PEs in the same AS. The RR in each AS maintains all BGP EVPN routes. The RRs in two ASs establish a multihop MP-EBGP session to advertise BGP EVPN routes.

Inter-AS option C features the best scalability. It allows PEs to directly exchange BGP EVPN routes. The ASBRs do not maintain or advertise BGP EVPN routes.

EVPN VPWS tasks at a glance

Configuring a remote connection

To configure a remote connection, perform the following tasks:

1.     Enabling L2VPN

2.     Configure an AC

¡     Configuring a Layer 3 interface with Ethernet or VLAN encapsulation

¡     Configuring an Ethernet service instance on an interface

3.     Configuring EVPN route advertisement

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.     Setting the redundancy mode on an interface

c.     (Optional.) Setting the DF election delay

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

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

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

8.     (Optional.) Configuring FRR for EVPN VPWS

¡     Configuring local FRR

¡     Configuring remote FRR

Configuring PW concatenation

To configure PW concatenation, perform the following tasks:

1.     Enabling L2VPN

2.     Configuring a cross-connect

3.     Configuring a PW

To concatenate two PWs, create them on the same cross-connect.

a.     (Optional.) Configuring a PW class

b.     Configuring 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, 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 an Ethernet service instance on an interface

About this task

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

Restrictions and guidelines

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

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

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

Procedure

1.     Enter system view.

system-view

2.     Enter interface view.

¡     Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

¡     Enter Layer 2 aggregate interface view.

interface bridge-aggregation interface-number

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

service-instance instance-id

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

¡     Match packets with the specified outer VLAN IDs.

encapsulation s-vid vlan-id-list

¡     Match packets with the specified outer and inner VLAN IDs.

encapsulation s-vid vlan-id-list c-vid vlan-id-list

¡     Match packets that do not have a VLAN tag.

encapsulation untagged

¡     Match packets that do not match any other Ethernet service instances on the interface.

encapsulation default

On an interface, you can configure the default criterion for only one Ethernet service instance. The Ethernet service instance matches all packets if it is the only instance on the interface.

By default, no frame match criterion is configured.

Configuring EVPN route advertisement

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.

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.     (Optional.) Set the optimal route selection delay timer.

route-select delay delay-value

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

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

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

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

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

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

12.     Configure the BGP Add-Path feature:

¡     Configure the BGP additional path capabilities.

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

By default, no BGP additional path capabilities are configured.

¡     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 number of one Add-Path optimal route can be advertised to a peer or peer group.

¡     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 number of one Add-Path optimal route can be advertised to all peers.

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 }

The default PW data encapsulation type varies by the device operating mode.

¡     For the Bridgee operating mode, the default PW data encapsulation type is VLAN.

¡     For the Standard operating mode, the default PW data encapsulation type is Ethernet.

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.

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.     Enter cross-connect view.

connection connection-name

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

mtu size

The default MTU is 1500 bytes.

8.     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 a Layer 3 interface to a cross-connect, packets received from the Layer 3 interface are forwarded to the PW or another AC bound to the cross-connect.

After you map an Ethernet service instance to a cross-connect, packets received from the Ethernet service instance are forwarded to the PW or another AC bound to the cross-connect. An Ethernet service instance matches a list of VLANs on a site-facing interface. The PE assigns customer traffic from the VLANs to a cross-connect by mapping the Ethernet service instance 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 2 or Layer 3 Ethernet interface has been added to a link aggregation group, you cannot map the Layer 3 interface or an Ethernet service instance on the Layer 2 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.

Mapping an Ethernet service instance 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 an Ethernet service instance to the cross-connect.

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

By default, no Ethernet service instance is mapped to a 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.

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.

Restrictions and guidelines

When EVPN VPWS multihoming is used together with S-Trunk, follow these restrictions and guidelines:

·     If EVPN VPWS multihoming is in single-active redundancy mode, use the s-trunk port-role auto command to set the role of smart trunk member interfaces to auto.

·     If EVPN VPWS multihoming is in all-active redundancy mode, use the s-trunk port-role primary command to set the role of smart trunk member interfaces to primary.

For more information about S-Trunk, see High Availability Configuration Guide.

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.     Set the redundancy mode.

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

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

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 fast DF/BDF switchover

About this task

As shown in Figure 11, 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 11 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

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 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 a delay timer 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-address

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

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.

Display and maintenance commands for EVPN VPWS

Execute display commands in any view.

For more information about the following BGP commands, see Layer 3—IP Routing Command Reference:

·     display bgp group.

·     display bgp peer.

·     display bgp update-group.

For more information about the following MPLS L2VPN commands, see MPLS Command Reference:

·     display l2vpn forwarding.

·     display l2vpn interface.

·     display l2vpn pw.

·     display l2vpn pw-class.

·     display l2vpn service-instance.

·     reset l2vpn statistics ac.

·     reset l2vpn statistics pw.

For more information about the display l2vpn pw bfd command, see MPLS OAM commands in MPLS Command Reference.

 

Task

Command

Display BGP peer group information.

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

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 ]

Display information about BGP update groups.

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

Display EVPN ES information.

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

Display EVPN routing table information.

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

Display cross-connect forwarding information.

display l2vpn forwarding { ac | pw } [ xconnect-group group-name ] [ slot slot-number ] [ verbose ]

Display L2VPN information for Layer 3 interfaces mapped to cross-connects.

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

Display L2VPN PW information.

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

Display BFD information for PWs.

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

Display PW class information.

display l2vpn pw-class [ class-name ]

Display Ethernet service instance information.

display l2vpn service-instance [ interface interface-type interface-number [ service-instance instance-id ] ] [ verbose ]

Display EVPN information about cross-connects.

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

 

EVPN VPWS configuration examples

Example: Configuring a remote connection between singlehomed sites

Network configuration

As shown in Figure 12, 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 12 Network diagram

Device

Interface

IP address

Device

Interface

IP address

CE 1

HGE1/0/1

10.1.1.10/24

P

Loop0

3.3.3.3/32

PE 1

Loop0

1.1.1.1/32

 

HGE1/0/1

11.1.1.2/24

 

HGE1/0/1

N/A

 

HGE1/0/2

11.1.2.2/24

 

HGE1/0/2

11.1.1.1/24

PE 2

Loop0

2.2.2.2/32

CE 2

HGE1/0/1

10.1.1.20/24

 

HGE1/0/1

N/A

 

 

 

 

HGE1/0/2

11.1.2.1/24

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure CE 1.

<CE1> system-view

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/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 HundredGigE 1/0/2 (the interface connected to the P device), and enable LDP on the interface.

[PE1] interface hundredgige 1/0/2

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

[PE1-HundredGigE1/0/2] mpls enable

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

[PE1-HundredGigE1/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] 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 HundredGigE 1/0/1 to it. Create an EVPN PW on the cross-connect.

[PE1-xcg-vpna] connection pw1

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

[PE1-xcg-vpna-pw1-HundredGigE1/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 HundredGigE 1/0/1 (the interface connected to PE 1), and enable LDP on the interface.

[P] interface hundredgige 1/0/1

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

[P-HundredGigE1/0/1] mpls enable

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

[P-HundredGigE1/0/1] quit

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

[P] interface hundredgige 1/0/2

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

[P-HundredGigE1/0/2] mpls enable

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

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

[PE2] interface hundredgige 1/0/2

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

[PE2-HundredGigE1/0/2] mpls enable

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

[PE2-HundredGigE1/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] 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 HundredGigE 1/0/1 to it. Create an EVPN PW on the cross-connect.

[PE2-xcg-vpna] connection pw1

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

[PE2-xcg-vpna-pw1-HundredGigE1/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 hundredgige 1/0/1

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

[CE2-HundredGigE1/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.

<Sysname> display evpn route 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            : 502

  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 13, configure EVPN VPWS for dualhomed site 1 and singlehomed site 2 to communicate over the MPLS or IP backbone network.

Figure 13 Network diagram

Device

Interface

IP address

Device

Interface

IP address

PE 1

Loop0

192.1.1.1/32

CE 1

RAGG1

100.1.1.1/24

 

HGE1/0/1

N/A

CE 2

HGE1/0/1

100.1.1.2/24

 

HGE1/0/2

10.1.1.1/24

PE 3

Loop0

192.3.3.3/32

 

HGE1/0/3

10.1.3.1/24

 

HGE1/0/1

N/A

PE 2

Loop0

192.2.2.2/32

 

HGE1/0/2

10.1.1.2/24

 

HGE1/0/1

N/A

 

HGE1/0/2

10.1.2.2/24

 

HGE1/0/2

10.1.2.1/24

 

 

 

 

HGE1/0/3

10.1.3.2/24

 

 

 

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

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 HundredGigE 1/0/1 and HundredGigE 1/0/2 to aggregation group 1.

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/0/1] quit

[CE1] interface hundredgige 1/0/2

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

[CE1-HundredGigE1/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 HundredGigE 1/0/2 (the interface connected to PE 3), and enable LDP on the interface.

[PE1] interface hundredgige 1/0/2

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

[PE1-HundredGigE1/0/2] mpls enable

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

[PE1-HundredGigE1/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 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] quit

[PE1-bgp-default] quit

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

[PE1] interface hundredgige 1/0/1

[PE1-HundredGigE1/0/1] esi 1.1.1.1.1

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

[PE1-HundredGigE1/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 HundredGigE 1/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 hundredgige 1/0/1

[PE1-xcg-vpna-pw1-HundredGigE1/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 HundredGigE 1/0/2 with track entry 1.

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

[PE1-track-1] quit

# Configure CLI-defined monitor policy 1 to associate HundredGigE 1/0/2 with HundredGigE 1/0/1. This setting allows PE 1 to shut down HundredGigE 1/0/1 when HundredGigE 1/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 hundredgige 1/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 HundredGigE 1/0/2 (the interface connected to PE 3), and enable LDP on the interface.

[PE2] interface hundredgige 1/0/2

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

[PE2-HundredGigE1/0/2] mpls enable

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

[PE2-HundredGigE1/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 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] quit

[PE2-bgp-default] quit

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

[PE2] interface hundredgige 1/0/1

[PE2-HundredGigE1/0/1] esi 1.1.1.1.1

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

[PE2-HundredGigE1/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 HundredGigE 1/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 hundredgige 1/0/1

[PE2-xcg-vpna-pw1-HundredGigE1/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 HundredGigE 1/0/2 with track entry 1.

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

[PE2-track-1] quit

# Configure CLI-defined monitor policy 1 to associate HundredGigE 1/0/2 with HundredGigE 1/0/1. This setting allows PE 2 to shut down HundredGigE 1/0/1 when HundredGigE 1/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 hundredgige 1/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 HundredGigE 1/0/2 (the interface connected to PE 1) and HundredGigE 1/0/3 (the interface connected to PE 2), and enable LDP on the interfaces.

[PE3] interface hundredgige 1/0/2

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

[PE3-HundredGigE1/0/2] mpls enable

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

[PE3-HundredGigE1/0/2] quit

[PE3] interface hundredgige 1/0/3

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

[PE3-HundredGigE1/0/3] mpls enable

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

[PE3-HundredGigE1/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] 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 HundredGigE 1/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 hundredgige 1/0/1

[PE3-xcg-vpna-pw1-HundredGigE1/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 hundredgige 1/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: 2

1 up, 1 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 route 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

    192.2.2.2        0001.0001.0001.0001.0001  710264     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.

<Sysname> 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        P

# 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: 2

1 up, 1 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 14:

·     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 14 Network diagram

Device

Interface

IP address

Device

Interface

IP address

CE 1

HGE1/0/1

100.1.1.1/24

P

Loop0

192.4.4.4/32

PE 1

Loop0

192.2.2.2/32

 

HGE1/0/1

23.1.1.2/24

 

HGE1/0/2

23.1.1.1/24

 

HGE1/0/2

26.2.2.2/24

CE 2

HGE1/0/1

100.1.1.2/24

PE 2

Loop0

192.3.3.3/32

 

 

 

 

HGE1/0/2

26.2.2.1/24

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure CE 1.

<CE1> system-view

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/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

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# 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 HundredGigE 1/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 hundredgige 1/0/1

[PE1-xcg-vpna-pw1-HundredGigE1/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 194.4.4.4 enable

[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

# Enable global LDP.

[P] mpls ldp

[P-ldp] quit

# 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] 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

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# 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 HundredGigE 1/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 hundredgige 1/0/1

[PE2-xcg-vpna-pw1-HundredGigE1/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] quit

[PE2-bgp-default] quit

5.     Configure CE 2.

<CE2> system-view

[CE2] interface hundredgige 1/0/1

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

[CE2-HundredGigE1/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.)

Example: Configuring inter-AS option A

Network configuration

As shown in Figure 15:

·     Establish an EVPN PW between the PE and the ASBR in each AS.

·     Associate HundredGigE 1/0/1 with the EVPN PW on each ASBR.

·     Associate HundredGigE 1/0/1 with the EVPN PW on each PE.

·     Run OSPF on the MPLS backbone of each AS.

Figure 15 Network diagram

Device

Interface

IP address

Device

Interface

IP address

CE 1

HGE1/0/1

100.1.1.1/24

ASBR 1

Loop0

192.2.2.2/32

PE 1

Loop0

192.1.1.1/32

 

HGE1/0/2

23.1.1.2/24

 

HGE1/0/2

23.1.1.1/24

 

HGE1/0/1

26.2.2.2/24

PE 2

Loop0

192.4.4.4/32

ASBR 2

Loop0

192.3.3.3/32

 

HGE1/0/2

22.2.2.1/24

 

HGE1/0/1

26.2.2.3/24

CE 2

HGE1/0/1

100.1.1.2/24

 

HGE1/0/2

22.2.2.3/24

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure CE 1.

<CE1> system-view

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/0/1] 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

# Enable LDP on HundredGigE 1/0/2, the interface connected to ASBR 1.

[PE1] interface hundredgige 1/0/2

[PE1-HundredGigE1/0/2] ip address 23.1.1.1 24

[PE1-HundredGigE1/0/2] mpls enable

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

[PE1-HundredGigE1/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 23.1.1.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 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 HundredGigE 1/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 hundredgige 1/0/1

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

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

# Create an IBGP connection to ASBR 1, and enable BGP to advertise BGP EVPN routes to ASBR 1.

[PE1] bgp 100

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

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

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

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

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

3.     Configure ASBR 1:

# Configure the LSR ID.

<ASBR1> system-view

[ASBR1] interface loopback 0

[ASBR1-LoopBack0] ip address 192.2.2.2 32

[ASBR1-LoopBack0] quit

[ASBR1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[ASBR1] l2vpn enable

# Enable global LDP.

[ASBR1] mpls ldp

[ASBR1-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to PE 1.

[ASBR1] interface hundredgige 1/0/2

[ASBR1-HundredGigE1/0/2] ip address 23.1.1.2 24

[ASBR1-HundredGigE1/0/2] mpls enable

[ASBR1-HundredGigE1/0/2] mpls ldp enable

[ASBR1-HundredGigE1/0/2] quit

# Configure OSPF for LDP to create LSPs.

[ASBR1] ospf

[ASBR1-ospf-1] area 0

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

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

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

[ASBR1-ospf-1] quit

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

[ASBR1] xconnect-group vpna

[ASBR1-xcg-vpna] evpn encapsulation mpls

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

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

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

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

# Create cross-connect pw1 and map HundredGigE 1/0/1 (the interface connected to ASBR 2) to it. Create an EVPN PW on the cross-connect.

[ASBR1-xcg-vpna] connection pw1

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

[ASBR1-xcg-vpna-pw1] ac interface hundredgige 1/0/1

[ASBR1-xcg-vpna-pw1-HundredGigE1/0/1] quit

[ASBR1-xcg-vpna-pw1] quit

[ASBR1-xcg-vpna] quit

# Create an IBGP connection to PE 1, and enable BGP to advertise BGP EVPN routes to PE 1.

[ASBR1] bgp 100

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

[ASBR1-bgp-default] peer 192.1.1.1 connect-interface LoopBack0

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

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

[ASBR1-bgp-default-evpn] quit

[ASBR1-bgp-default] quit

4.     Configure ASBR 2:

# Configure the LSR ID.

<ASBR2> system-view

[ASBR2] interface loopback 0

[ASBR2-LoopBack0] ip address 192.3.3.3 32

[ASBR2-LoopBack0] quit

[ASBR2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[ASBR2] l2vpn enable

# Enable global LDP.

[ASBR2] mpls ldp

[ASBR2-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to PE 2.

[ASBR2] interface hundredgige 1/0/2

[ASBR2-HundredGigE1/0/2] ip address 22.2.2.3 24

[ASBR2-HundredGigE1/0/2] mpls enable

[ASBR2-HundredGigE1/0/2] mpls ldp enable

[ASBR2-HundredGigE1/0/2] quit

# Configure OSPF for LDP to create LSPs.

[ASBR2] ospf

[ASBR2-ospf-1] area 0

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

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

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

[ASBR2-ospf-1] quit

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

[ASBR2] xconnect-group vpna

[ASBR2-xcg-vpna] evpn encapsulation mpls

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

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

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

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

# Create cross-connect pw1 and map HundredGigE 1/0/1 (the interface connected to ASBR 1) to it. Create an EVPN PW on the cross-connect.

[ASBR2-xcg-vpna] connection pw1

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

[ASBR2-xcg-vpna-pw1] ac interface hundredgige 1/0/1

[ASBR2-xcg-vpna-pw1-HundredGigE1/0/1] quit

[ASBR2-xcg-vpna-pw1] quit

[ASBR2-xcg-vpna] quit

# Create an IBGP connection to PE 2, and enable BGP to advertise BGP EVPN routes to PE 2.

[ASBR2] bgp 200

[ASBR2-bgp-default] peer 192.4.4.4 as-number 200

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

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

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

[ASBR2-bgp-default-evpn] quit

[ASBR2-bgp-default] quit

5.     Configure PE 2:

# Configure the LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.4.4.4 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.4.4.4

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to ASBR 2.

[PE2] interface hundredgige 1/0/2

[PE2-HundredGigE1/0/2] ip address 22.2.2.1 24

[PE2-HundredGigE1/0/2] mpls enable

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

[PE2-HundredGigE1/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 192.4.4.4 0.0.0.0

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

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

[PE2-ospf-1] quit

# Create a cross-connect group named vpna, create 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 2:1 export-extcommunity

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

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

# Create cross-connect pw1 and map HundredGigE 1/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 hundredgige 1/0/1

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

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

# Create an IBGP connection to ASBR 2, and enable BGP to advertise BGP EVPN routes to ASBR 2.

[PE2] bgp 200

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

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

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

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

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

6.     Configure CE 2.

<CE2> system-view

[CE2] interface hundredgige 1/0/1

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

[CE2-HundredGigE1/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.2.2.2       1                  710127/710126  EVPN   M    0        Up

# Verify that an EVPN PW has been established on ASBR 1.

[ASBR1] display l2vpn pw

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

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

       PBY - pw-bypass

Total number of PWs: 2

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

 

Xconnect-group Name: vpn1

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

192.1.1.1       2                  710126/710127  EVPN   M    0        Up

# Verify that an EVPN PW has been established on ASBR 2.

[ASBR2] display l2vpn pw

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

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

       PBY - pw-bypass

Total number of PWs: 2

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

 

Xconnect-group Name: vpna

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

192.4.4.4       4                  710127/710127  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: vpna

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

192.3.3.3       3                  710127/710127  EVPN   M    0        Up

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

Example: Configuring inter-AS option B

Network configuration

As shown in Figure 16:

·     Establish an EVPN PW between the PE and the ASBR in each AS, and use LDP to establish the public tunnels that convey the EVPN PWs.

·     Establish an EVPN PW between the ASBRs, and configure BGP to advertise labeled IPv4 unicast routes to establish the public tunnel that conveys the EVPN PW.

·     Concatenate the EVPN PWs on the ASBRs.

Figure 16 Network diagram

Device

Interface

IP address

Device

Interface

IP address

CE 1

HGE1/0/1

100.1.1.1/24

ASBR 1

Loop0

192.2.2.2/32

PE 1

Loop0

192.1.1.1/32

 

HGE1/0/2

23.1.1.2/24

 

HGE1/0/2

23.1.1.1/24

 

HGE1/0/1

26.2.2.2/24

PE 2

Loop0

192.4.4.4/32

ASBR 2

Loop0

192.3.3.3/32

 

HGE1/0/2

22.2.2.1/24

 

HGE1/0/1

26.2.2.3/24

CE 2

HGE1/0/1

100.1.1.2/24

 

HGE1/0/2

22.2.2.3/24

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure CE 1.

<CE1> system-view

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/0/1] 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

# Enable LDP on HundredGigE 1/0/2, the interface connected to ASBR 1.

[PE1] interface hundredgige 1/0/2

[PE1-HundredGigE1/0/2] ip address 23.1.1.1 24

[PE1-HundredGigE1/0/2] mpls enable

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

[PE1-HundredGigE1/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 23.1.1.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 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 HundredGigE 1/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 hundredgige 1/0/1

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

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

# Create an IBGP connection to ASBR 1, and enable BGP to advertise BGP EVPN routes to ASBR 1.

[PE1] bgp 100

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

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

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

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

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

3.     Configure ASBR 1:

# Configure the LSR ID.

<ASBR1> system-view

[ASBR1] interface loopback 0

[ASBR1-LoopBack0] ip address 192.2.2.2 32

[ASBR1-LoopBack0] quit

[ASBR1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[ASBR1] l2vpn enable

# Enable global LDP.

[ASBR1] mpls ldp

[ASBR1-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to PE 1.

[ASBR1] interface hundredgige 1/0/2

[ASBR1-HundredGigE1/0/2] ip address 23.1.1.2 24

[ASBR1-HundredGigE1/0/2] mpls enable

[ASBR1-HundredGigE1/0/2] mpls ldp enable

[ASBR1-HundredGigE1/0/2] quit

# Enable MPLS on HundredGigE 1/0/1, the interface connected to ASBR 2.

[ASBR1] interface hundredgige 1/0/1

[ASBR1-HundredGigE1/0/1] ip address 26.2.2.2 24

[ASBR1-HundredGigE1/0/1] mpls enable

[ASBR1-HundredGigE1/0/1] quit

# Configure OSPF for LDP to create LSPs.

[ASBR1] ospf

[ASBR1-ospf-1] area 0

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

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

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

[ASBR1-ospf-1] quit

# Create an IBGP connection to PE 1, and enable BGP to advertise BGP EVPN routes to PE 1.

[ASBR1] bgp 100

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

[ASBR1-bgp-default] peer 192.1.1.1 connect-interface LoopBack0

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

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

[ASBR1-bgp-default-evpn] quit

# Create an EBGP connection to ASBR 2, and enable BGP to advertise BGP EVPN routes and labeled unicast routes to ASBR 2.

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

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

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

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

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

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

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

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

[ASBR1-bgp-default-evpn] quit

[ASBR1-bgp-default] quit

[ASBR1] route-policy policy1 permit node 1

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

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

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

[ASBR1] xconnect-group vpna

[ASBR1-xcg-vpna] evpn encapsulation mpls

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

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

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

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

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

[ASBR1-xcg-vpna] connection pw1

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

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

[ASBR1-xcg-vpna-pw1] quit

[ASBR1-xcg-vpna] quit

4.     Configure ASBR 2:

# Configure the LSR ID.

<ASBR2> system-view

[ASBR2] interface loopback 0

[ASBR2-LoopBack0] ip address 192.3.3.3 32

[ASBR2-LoopBack0] quit

[ASBR2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[ASBR2] l2vpn enable

# Enable global LDP.

[ASBR2] mpls ldp

[ASBR2-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to PE 2.

[ASBR2] interface hundredgige 1/0/2

[ASBR2-HundredGigE1/0/2] ip address 22.2.2.3 24

[ASBR2-HundredGigE1/0/2] mpls enable

[ASBR2-HundredGigE1/0/2] mpls ldp enable

[ASBR2-HundredGigE1/0/2] quit

# Enable MPLS on HundredGigE 1/0/1, the interface connected to ASBR 1.

[ASBR2] interface hundredgige 1/0/1

[ASBR2-HundredGigE1/0/1] ip address 26.2.2.3 24

[ASBR2-HundredGigE1/0/1] mpls enable

[ASBR2-HundredGigE1/0/1] quit

# Configure OSPF for LDP to create LSPs.

[ASBR2] ospf

[ASBR2-ospf-1] area 0

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

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

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

[ASBR2-ospf-1] quit

# Create an IBGP connection to PE 2, and enable BGP to advertise BGP EVPN routes to PE 2.

[ASBR2] bgp 200

[ASBR2-bgp-default] peer 192.4.4.4 as-number 200

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

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

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

[ASBR2-bgp-default-evpn] quit

# Create an EBGP connection to ASBR 1, and enable BGP to advertise BGP EVPN routes and labeled unicast routes to ASBR 1.

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

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

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

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

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

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

[ASBR2-bgp-default-ipv4] quit

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

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

[ASBR2-bgp-default-evpn] quit

[ASBR2-bgp-default] quit

[ASBR2] route-policy policy1 permit node 1

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

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

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

[ASBR2] xconnect-group vpna

[ASBR2-xcg-vpna] evpn encapsulation mpls

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

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

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

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

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

[ASBR2-xcg-vpna] connection pw1

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

[ASBR2-xcg-vpna-pw1] evpn local-service-id 5 remote-service-id 6

[ASBR2-xcg-vpna-pw1] quit

[ASBR2-xcg-vpna] quit

5.     Configure PE 2:

# Configure the LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.4.4.4 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.4.4.4

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to ASBR 2.

[PE2] interface hundredgige 1/0/2

[PE2-HundredGigE1/0/2] ip address 22.2.2.1 24

[PE2-HundredGigE1/0/2] mpls enable

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

[PE2-HundredGigE1/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 192.4.4.4 0.0.0.0

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

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

[PE2-ospf-1] quit

# Create a cross-connect group named vpna, create 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 2:1 export-extcommunity

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

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

# Create cross-connect pw1 and map HundredGigE 1/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 6 remote-service-id 5

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

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

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

# Create an IBGP connection to ASBR 2, and enable BGP to advertise BGP EVPN routes to ASBR 2.

[PE2] bgp 200

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

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

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

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

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

6.     Configure CE 2.

<CE2> system-view

[CE2] interface hundredgige 1/0/1

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

[CE2-HundredGigE1/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.2.2.2       1                  710127/710126  EVPN   M    0        Up

# Verify that two EVPN PWs are concatenated on ASBR 1.

[ASBR1] display l2vpn pw

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

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

       PBY - pw-bypass

Total number of PWs: 2

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

 

Xconnect-group Name: vpn1

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

192.1.1.1       2                  710126/710127  EVPN   M    0        Up

26.2.2.3        4                  710127/710126  EVPN   M    1        Up

# Verify that two EVPN PWs are concatenated on ASBR 2.

[ASBR2] display l2vpn pw

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

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

       PBY - pw-bypass

Total number of PWs: 2

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

 

Xconnect-group Name: vpna

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

26.2.2.2        3                  710126/710127  EVPN   M    0        Up

192.4.4.4       6                  710127/710127  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: vpna

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

192.3.3.3       5                  710127/710127  EVPN   M    0        Up

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

Example: Configuring inter-AS option C

Network configuration

As shown in Figure 17:

·     Configure the PE and the ASBR in each AS to use IBGP to exchange labeled IPv4 routes.

·     Configure the PEs to exchange BGP EVPN routes to establish an EVPN PW.

·     Establish an EVPN PW between the ASBRs, and configure BGP to advertise labeled IPv4 unicast routes to establish the public tunnel that conveys the EVPN PW.

·     Configure a PBR policy on each ASBR for it to insert labels into received routes.

·     Configure the ASBRs to exchange labeled IPv4 routes through EBGP.

Figure 17 Network diagram

Device

Interface

IP address

Device

Interface

IP address

CE 1

HGE1/0/1

100.1.1.1/24

ASBR 1

Loop0

192.2.2.2/32

PE 1

Loop0

192.1.1.1/32

 

HGE1/0/2

23.1.1.2/24

 

HGE1/0/2

23.1.1.1/24

 

HGE1/0/1

26.2.2.2/24

PE 2

Loop0

192.4.4.4/32

ASBR 2

Loop0

192.3.3.3/32

 

HGE1/0/2

22.2.2.1/24

 

HGE1/0/1

26.2.2.3/24

CE 2

HGE1/0/1

100.1.1.2/24

 

HGE1/0/2

22.2.2.3/24

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure CE 1.

<CE1> system-view

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/0/1] 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

# Enable LDP on HundredGigE 1/0/2, the interface connected to ASBR 1.

[PE1] interface hundredgige 1/0/2

[PE1-HundredGigE1/0/2] ip address 23.1.1.1 24

[PE1-HundredGigE1/0/2] mpls enable

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

[PE1-HundredGigE1/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 23.1.1.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 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 2:2 import-extcommunity

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

# Create cross-connect pw1 and map HundredGigE 1/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 hundredgige 1/0/1

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

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

# Create an IBGP connection to ASBR 1, and enable BGP to advertise BGP EVPN routes and labeled unicast routes to ASBR 1.

[PE1] bgp 100

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

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

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

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

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

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

[PE1-bgp-default-ipv4] peer 192.2.2.2 label-route-capability

[PE1-bgp-default-ipv4] quit

[PE1-bgp-default] quit

# Configure BGP to advertise BGP EVPN routes to PE 2 to establish an EVPN PW.

[PE1] bgp 100

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

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

[PE1-bgp-default] peer 192.4.4.4 ebgp-max-hop 10

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

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

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

3.     Configure ASBR 1:

# Configure the LSR ID.

<ASBR1> system-view

[ASBR1] interface loopback 0

[ASBR1-LoopBack0] ip address 192.2.2.2 32

[ASBR1-LoopBack0] quit

[ASBR1] mpls lsr-id 192.2.2.2

# Enable L2VPN.

[ASBR1] l2vpn enable

# Enable global LDP.

[ASBR1] mpls ldp

[ASBR1-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to PE 1.

[ASBR1] interface hundredgige 1/0/2

[ASBR1-HundredGigE1/0/2] ip address 23.1.1.2 24

[ASBR1-HundredGigE1/0/2] mpls enable

[ASBR1-HundredGigE1/0/2] mpls ldp enable

[ASBR1-HundredGigE1/0/2] quit

# Enable MPLS on HundredGigE 1/0/1, the interface connected to ASBR 2.

[ASBR1] interface hundredgige 1/0/1

[ASBR1-HundredGigE1/0/1] ip address 26.2.2.2 24

[ASBR1-HundredGigE1/0/1] mpls enable

[ASBR1-HundredGigE1/0/1] quit

# Configure OSPF for LDP to create LSPs.

[ASBR1] ospf

[ASBR1-ospf-1] area 0

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

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

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

[ASBR1-ospf-1] quit

# Create routing policies.

[ASBR1] route-policy policy1 permit node 1

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

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

[ASBR1] route-policy policy2 permit node 1

[ASBR1-route-policy-policy2-1] if-match mpls-label

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

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

# Enable BGP on ASBR 1, and apply the routing policy policy2 to routes advertised to IBGP peer 192.1.1.1.

[ASBR1] bgp 100

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

[ASBR1-bgp-default] peer 192.1.1.1 connect-interface LoopBack0

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

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

[ASBR1-bgp-default-ipv4] peer 192.1.1.1 route-policy policy2 export

# Enable the capability to advertise labeled routes to IBGP peer 192.1.1.1 and to receive labeled routes from the peer.

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

# Redistribute routes from OSPF process 1 to BGP.

[ASBR1-bgp-default-ipv4] import-route ospf 1

[ASBR1-bgp-default-ipv4] quit

# Advertise BGP EVPN routes to IBGP peer 192.1.1.1.

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

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

[ASBR1-bgp-default-evpn] quit

# Apply routing policy policy1 to routes advertised to EBGP peer 26.2.2.3.

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

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

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

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

# Enable the capability to advertise labeled routes to EBGP peer 26.2.2.3 and to receive labeled routes from the peer.

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

[ASBR1-bgp-default-ipv4] quit

# Advertise BGP EVPN routes to EBGP peer 26.2.2.3.

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

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

[ASBR1-bgp-default-evpn] quit

[ASBR1-bgp-default] quit

4.     Configure ASBR 2:

# Configure the LSR ID.

<ASBR2> system-view

[ASBR2] interface loopback 0

[ASBR2-LoopBack0] ip address 192.3.3.3 32

[ASBR2-LoopBack0] quit

[ASBR2] mpls lsr-id 192.3.3.3

# Enable L2VPN.

[ASBR2] l2vpn enable

# Enable global LDP.

[ASBR2] mpls ldp

[ASBR2-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to PE 2.

[ASBR2] interface hundredgige 1/0/2

[ASBR2-HundredGigE1/0/2] ip address 22.2.2.3 24

[ASBR2-HundredGigE1/0/2] mpls enable

[ASBR2-HundredGigE1/0/2] mpls ldp enable

[ASBR2-HundredGigE1/0/2] quit

# Enable MPLS on HundredGigE 1/0/1, the interface connected to ASBR 1.

[ASBR2] interface hundredgige 1/0/1

[ASBR2-HundredGigE1/0/1] ip address 26.2.2.3 24

[ASBR2-HundredGigE1/0/1] mpls enable

[ASBR2-HundredGigE1/0/1] quit

# Configure OSPF for LDP to create LSPs.

[ASBR2] ospf

[ASBR2-ospf-1] area 0

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

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

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

[ASBR2-ospf-1] quit

# Create routing policies.

[ASBR2] route-policy policy1 permit node 1

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

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

[ASBR2] route-policy policy2 permit node 1

[ASBR2-route-policy-policy2-1] if-match mpls-label

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

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

# Enable BGP on ASBR 2, and apply the routing policy policy2 to routes advertised to IBGP peer 192.4.4.4.

[ASBR2] bgp 200

[ASBR2-bgp-default] peer 192.4.4.4 as-number 200

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

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

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

[ASBR2-bgp-default-ipv4] peer 192.4.4.4 route-policy policy2 export

# Enable the capability to advertise labeled routes to IBGP peer 192.4.4.4 and to receive labeled routes from the peer.

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

# Redistribute routes from OSPF process 1 to BGP.

[ASBR2-bgp-default-ipv4] import-route ospf 1

[ASBR2-bgp-default-ipv4] quit

# Advertise BGP EVPN routes to IBGP peer 192.4.4.4.

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

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

[ASBR2-bgp-default-evpn] quit

# Apply routing policy policy1 to routes advertised to EBGP peer 26.2.2.2.

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

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

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

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

# Enable the capability to advertise labeled routes to EBGP peer 26.2.2.2 and to receive labeled routes from the peer.

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

[ASBR2-bgp-default-ipv4] quit

# Advertise BGP EVPN routes to EBGP peer 26.2.2.2.

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

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

[ASBR2-bgp-default-evpn] quit

[ASBR2-bgp-default] quit

5.     Configure PE 2:

# Configure the LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 192.4.4.4 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 192.4.4.4

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Enable LDP on HundredGigE 1/0/2, the interface connected to ASBR 2.

[PE2] interface hundredgige 1/0/2

[PE2-HundredGigE1/0/2] ip address 22.2.2.1 24

[PE2-HundredGigE1/0/2] mpls enable

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

[PE2-HundredGigE1/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 192.4.4.4 0.0.0.0

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

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

[PE2-ospf-1] quit

# Create a cross-connect group named vpna, create 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 2:2 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 HundredGigE 1/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 1 remote-service-id 2

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

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

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

# Create an IBGP connection to ASBR 2, and enable BGP to advertise BGP EVPN routes and labeled unicast routes to ASBR 2.

[PE2] bgp 200

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

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

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

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

[PE2-bgp-default-evpn] quit

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

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

[PE2-bgp-default-ipv4] peer 192.3.3.3 label-route-capability

[PE2-bgp-default-ipv4] quit

[PE1-bgp-default] quit

# Configure BGP to advertise BGP EVPN routes to PE 1 to establish an EVPN PW.

[PE2] bgp 200

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

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

[PE2-bgp-default] peer 192.1.1.1 ebgp-max-hop 10

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

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

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

6.     Configure CE 2.

<CE2> system-view

[CE2] interface hundredgige 1/0/1

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

[CE2-HundredGigE1/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                  710127/710126  EVPN   M    0        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: vpna

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

192.1.1.1       2                  710126/710127  EVPN   M    0        Up

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

Example: Configure FRR for EVPN VPWS

Network configuration

As shown in Figure 18:

·     Assign the links that connect CE 1 to PE 1 and PE 2 to a smart trunk.

·     Configure EVPN VPWS on PE 1, PE 2, and PE 3.

·     Establish a bypass PW between PE 1 and PE 2, and configure LDP to set up a public tunnel for the bypass PW.

·     Establish a primary PW and a backup PW between PE 1 and PE 3, and establish a primary PW and a backup PW between PE 2 and PE 3,

·     Configure RR 1 and RR 2 to modify the next hop attribute of routes and reassign MPLS labels to them when they reflect routes for PE 1 and PE 2.

·     Configure RR 1 and RR 2 to modify route attributes by using routing policies for route selection.

·     Assign PE 1, PE 2, and PE 3 to AS 100, and configure the AS to use OSPF as the IGP.

Figure 18 Network diagram

Table 1 Interface and IP address assignment

Device

Interface

IP address

Device

Interface

IP address

PE 1

Loop0

1.1.1.1/32

PE 3

Loop0

3.3.3.3/32

 

HGE1/0/1

-

 

HGE1/0/1

-

 

HGE1/0/2

10.1.1.1/24

 

HGE1/0/2

10.1.6.3/24

 

HGE1/0/3

10.1.2.1/24

 

HGE1/0/3

10.1.7.3/24

 

HGE1/0/4

10.1.3.1/24

RR 1

Loop0

4.4.4.4/32

PE 2

Loop0

2.2.2.2/32

 

HGE1/0/1

10.1.1.4/24

 

HGE1/0/1

-

 

HGE1/0/2

10.1.6.4/24

 

HGE1/0/2

10.1.4.2/24

 

HGE1/0/4

10.1.5.4/24

 

HGE1/0/3

10.1.2.2/24

RR 2

Loop0

5.5.5.5/32

 

HGE1/0/4

10.1.5.2/24

 

HGE1/0/1

10.1.4.5/24

CE 1

RAGG1

100.1.1.1/24

 

HGE1/0/2

10.1.7.5/24

CE 2

HGE1/0/1

100.1.1.2/24

 

HGE1/0/4

10.1.3.5/24

 

Procedure

 

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure CE 1:

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

<CE1> system-view

[CE1] interface route-aggregation 1

[CE1-Route-Aggregation1] link-aggregation mode dynamic

[CE1-Route-Aggregation1] ip address 100.1.1.1 24

[CE1-Route-Aggregation1] quit

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

[CE1] interface hundredgige 1/0/1

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

[CE1-HundredGigE1/0/1] quit

[CE1] interface hundredgige 1/0/2

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

[CE1-HundredGigE1/0/2] quit

2.     Configure PE 1:

# Configure an LSR ID.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 1.1.1.1 32

[PE1-LoopBack0] quit

[PE1] mpls lsr-id 1.1.1.1

# Enable L2VPN.

[PE1] l2vpn enable

# Enable global LDP.

[PE1] mpls ldp

[PE1-ldp] quit

# Enable local FRR for EVPN VPWS globally.

[PE1] evpn multihoming vpws-frr local

# Configure HundredGigE 1/0/2 (the interface connected to RR 1), and enable MPLS and LDP on the interface.

[PE1] interface hundredgige 1/0/2

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

[PE1-HundredGigE1/0/2] mpls enable

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

[PE1-HundredGigE1/0/2] quit

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

[PE1] interface hundredgige 1/0/3

[PE1-HundredGigE1/0/3] ip address 10.1.2.1 24

[PE1-HundredGigE1/0/3] mpls enable

[PE1-HundredGigE1/0/3] mpls ldp enable

[PE1-HundredGigE1/0/3] quit

#Configure HundredGigE 1/0/4 (the interface connected to RR 2), and enable MPLS and LDP on the interface.

[PE1] interface hundredgige 1/0/4

[PE1-HundredGigE1/0/4] ip address 10.1.3.1 24

[PE1-HundredGigE1/0/4] mpls enable

[PE1-HundredGigE1/0/4] mpls ldp enable

[PE1-HundredGigE1/0/4] 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.2.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 1.1.1.1 0.0.0.0

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

[PE1-ospf-1] quit

# Configure PE 1 to establish IBGP peer relationships with RR 1 and RR 2, and configure BGP to advertise BGP EVPN routes.

[PE1] bgp 100

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

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

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

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

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

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

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

[PE1-bgp-default-evpn] quit

[PE1-bgp-default] quit

# Configure S-Trunk for CE 1 to be dual-homed to PE 1 and PE 2.

[PE1] lacp system-priority 10

[PE1] lacp system-mac 1-1-1

[PE1] lacp system-number 1

[PE1] s-trunk id 1

[PE1-s-trunk1] s-trunk ip destination 10.1.2.2 source 10.1.2.1

[PE1-s-trunk1] quit

[PE1] interface route-aggregation 1

[PE1-Route-Aggregation1] link-aggregation mode dynamic

[PE1-Route-Aggregation1] s-trunk 1

[PE1-Route-Aggregation1] s-trunk port-role primary

[PE1-Route-Aggregation1] quit

[PE1] interface hundredgige 1/0/1

[PE1-HundredGigE1/0/1] port link-aggregation group 1

[PE1-HundredGigE1/0/1] quit

# Assign an ESI to Route-Aggregation 1 and set its redundancy mode to all-active.

[PE1] interface route-aggregation 1

[PE1-Route-Aggregation1] esi 1.1.1.1.1

[PE1-Route-Aggregation1] evpn redundancy-mode all-active

[PE1-Route-Aggregation1] 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 Route-Aggregation 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 route-aggregation 1

[PE1-xcg-vpna-pw1-Route-Aggregation1] quit

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

[PE1-xcg-vpna-pw1] quit

[PE1-xcg-vpna] quit

# Enable remote FRR for EVPN VPWS globally.

[PE1] evpn vpws-frr remote

3.     Configure PE 2:

# Configure an LSR ID.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 2.2.2.2 32

[PE2-LoopBack0] quit

[PE2] mpls lsr-id 2.2.2.2

# Enable L2VPN.

[PE2] l2vpn enable

# Enable global LDP.

[PE2] mpls ldp

[PE2-ldp] quit

# Enable local FRR for EVPN VPWS globally.

[PE2] evpn multihoming vpws-frr local

# Configure HundredGigE 1/0/2 (the interface connected to RR 2), and enable MPLS and LDP on the interface.

[PE2] interface hundredgige 1/0/2

[PE2-HundredGigE1/0/2] ip address 10.1.4.2 24

[PE2-HundredGigE1/0/2] mpls enable

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

[PE2-HundredGigE1/0/2] quit

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

[PE2] interface hundredgige 1/0/3

[PE2-HundredGigE1/0/3] ip address 10.1.2.2 24

[PE2-HundredGigE1/0/3] mpls enable

[PE2-HundredGigE1/0/3] mpls ldp enable

[PE2-HundredGigE1/0/3] quit

# Configure HundredGigE 1/0/4 (the interface connected to RR 1), and enable MPLS and LDP on the interface.

[PE2] interface hundredgige 1/0/4

[PE2-HundredGigE1/0/4] ip address 10.1.5.2 24

[PE2-HundredGigE1/0/4] mpls enable

[PE2-HundredGigE1/0/4] mpls ldp enable

[PE2-HundredGigE1/0/4] 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.4.0 0.0.0.255

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

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

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

[PE2-ospf-1] quit

# Configure PE 2 to establish IBGP peer relationships with RR 1 and RR 2, and configure BGP to advertise BGP EVPN routes.

[PE2] bgp 100

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

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

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

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

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

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

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

[PE2-bgp-default-evpn] quit

[PE2-bgp-default] quit

# Configure S-Trunk for CE 1 to be dual-homed to PE 1 and PE 2.

[PE2] lacp system-priority 10

[PE2] lacp system-mac 1-1-1

[PE2] lacp system-number 2

[PE2] s-trunk id 1

[PE2-s-trunk1] s-trunk ip destination 10.1.2.1 source 10.1.2.2

[PE2-s-trunk1] quit

[PE2] interface route-aggregation 1

[PE2-Route-Aggregation1] link-aggregation mode dynamic

[PE2-Route-Aggregation1] s-trunk 1

[PE2-Route-Aggregation1] s-trunk port-role primary

[PE2-Route-Aggregation1] quit

[PE2] interface hundredgige 1/0/1

[PE2-HundredGigE1/0/1] port link-aggregation group 1

[PE2-HundredGigE1/0/1] quit

# Assign an ESI to Route-Aggregation 1 and set its redundancy mode to all-active.

[PE2] interface route-aggregation 1

[PE2-Route-Aggregation1] esi 1.1.1.1.1

[PE2-Route-Aggregation1] evpn redundancy-mode all-active

[PE2-Route-Aggregation1] 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 Route-Aggregation 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 route-aggregation 1

[PE2-xcg-vpna-pw1-Route-Aggregation1] quit

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

[PE2-xcg-vpna-pw1] quit

[PE2-xcg-vpna] quit

# Enable remote FRR for EVPN VPWS globally.

[PE2] evpn vpws-frr remote

4.     Configure RR 1:

# Configure an LSR ID.

<RR1> system-view

[RR1] interface loopback 0

[RR1-LoopBack0] ip address 4.4.4.4 32

[RR1-LoopBack0] quit

[RR1] mpls lsr-id 4.4.4.4

# Enable L2VPN.

[RR1] l2vpn enable

# Enable global LDP.

[RR1] mpls ldp

[RR1-ldp] quit

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

[RR1] interface hundredgige 1/0/1

[RR1-HundredGigE1/0/1] ip address 10.1.1.4 24

[RR1-HundredGigE1/0/1] mpls enable

[RR1-HundredGigE1/0/1] mpls ldp enable

[RR1-HundredGigE1/0/1] quit

# Configure HundredGigE 1/0/4 (the interface connected to PE 2), and enable MPLS and LDP on the interface.

[RR1] interface hundredgige 1/0/4

[RR1-HundredGigE1/0/4] ip address 10.1.5.4 24

[RR1-HundredGigE1/0/4] mpls enable

[RR1-HundredGigE1/0/4] mpls ldp enable

[RR1-HundredGigE1/0/4] quit

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

[RR1] interface hundredgige 1/0/2

[RR1-HundredGigE1/0/2] ip address 10.1.6.4 24

[RR1-HundredGigE1/0/2] mpls enable

[RR1-HundredGigE1/0/2] mpls ldp enable

[RR1-HundredGigE1/0/2] quit

# Configure OSPF for LDP to create LSPs.

[RR1] ospf

[RR1-ospf-1] area 0

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

[RR1-ospf-1-area-0.0.0.0] network 10.1.5.0 0.0.0.255

[RR1-ospf-1-area-0.0.0.0] network 10.1.6.0 0.0.0.255

[RR1-ospf-1-area-0.0.0.0] network 4.4.4.4 0.0.0.0

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

[RR1-ospf-1] quit

# Configure routing policies used for modifying the costs of routes.

[RR1] route-policy policy1 permit node 10

[RR1-route-policy-policy1-10] if-match route-type bgp-evpn-ad

[RR1-route-policy-policy1-10] apply cost 200

[RR1-route-policy-policy1-10] quit

[RR1] route-policy policy2 permite node 20

[RR1-route-policy-policy2-10] if-match route-type bgp-evpn-ad

[RR1-route-policy-policy2-10] apply cost 500

[RR1-route-policy-policy2-10] quit

# Configure RR 1 to establish IBGP peer relationships with PE 1, PE 2, and PE 3.

[RR1] bgp 100

[RR1-bgp-default] peer 1.1.1.1 as-number 100

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

[RR1-bgp-default] peer 3.3.3.3 as-number 100

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

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

[RR1-bgp-default] peer 3.3.3.3 connect-interface loopback 0

# Configure BGP to advertise BGP EVPN routes, and disable route target filtering for BGP EVPN routes.

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

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

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

[RR1-bgp-default-evpn] peer 3.3.3.3 enable

[RR1-bgp-default-evpn] undo policy vpn-target

# Configure RR 1 as an RR.

[RR1-bgp-default-evpn] peer 1.1.1.1 reflect-client

[RR1-bgp-default-evpn] peer 2.2.2.2 reflect-client

[RR1-bgp-default-evpn] peer 3.3.3.3 reflect-client

# Enable RR to change the attributes of routes to be reflected.

[RR1-bgp-default-evpn] reflect change-path-attribute

# Set the local router as the next hop for routes sent to PE 1 and PE 2.

[RR1-bgp-default-evpn] peer 1.1.1.1 next-hop-local

[RR1-bgp-default-evpn] peer 2.2.2.2 next-hop-local

# Add PE 1 and PE 2 to the nearby cluster.

[RR1-bgp-default-evpn] peer 1.1.1.1 reflect-nearby-group

[RR1-bgp-default-evpn] peer 2.2.2.2 reflect-nearby-group

# Apply routing policy policy1 to routes advertised to IBGP peer 1.1.1.1.

[RR1-bgp-default-evpn] peer 1.1.1.1 route-policy policy1 export

# Apply routing policy policy2 to routes advertised to IBGP peer 2.2.2.2.

[RR1-bgp-default-evpn] peer 2.2.2.2 route-policy policy2 export

[RR1-bgp-default-evpn] quit

[RR1-bgp-default] quit

5.     Configure RR 2:

# Configure an LSR ID.

<RR2> system-view

[RR2] interface loopback 0

[RR2-LoopBack0] ip address 5.5.5.5 32

[RR2-LoopBack0] quit

[RR2] mpls lsr-id 5.5.5.5

# Enable L2VPN.

[RR2] l2vpn enable

# Enable global LDP.

[RR2] mpls ldp

[RR2-ldp] quit

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

[RR2] interface hundredgige 1/0/4

[RR2-HundredGigE1/0/4] ip address 10.1.7.5 24

[RR2-HundredGigE1/0/4] mpls enable

[RR2-HundredGigE1/0/4] mpls ldp enable

[RR2-HundredGigE1/0/4] quit

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

[RR2] interface hundredgige 1/0/1

[RR2-HundredGigE1/0/1] ip address 10.1.4.5 24

[RR2-HundredGigE1/0/1] mpls enable

[RR2-HundredGigE1/0/1] mpls ldp enable

[RR2-HundredGigE1/0/1] quit

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

[RR2] interface hundredgige 1/0/2

[RR2-HundredGigE1/0/2] ip address 10.1.3.5 24

[RR2-HundredGigE1/0/2] mpls enable

[RR2-HundredGigE1/0/2] mpls ldp enable

[RR2-HundredGigE1/0/2] quit

# Configure OSPF for LDP to create LSPs.

[RR2] ospf

[RR2-ospf-1] area 0

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

[RR2-ospf-1-area-0.0.0.0] network 10.1.4.0 0.0.0.255

[RR2-ospf-1-area-0.0.0.0] network 10.1.7.0 0.0.0.255

[RR2-ospf-1-area-0.0.0.0] network 5.5.5.5 0.0.0.0

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

[RR2-ospf-1] quit

# Configure routing policies used for modifying the costs of routes.

[RR2] route-policy policy1 permit node 10

[RR2-route-policy-policy1-10] if-match route-type bgp-evpn-ad

[RR2-route-policy-policy1-10] apply cost 200

[RR2-route-policy-policy1-10] quit

[RR2] route-policy policy2 permit node 20

[RR2-route-policy-policy2-10] if-match route-type bgp-evpn-ad

[RR2-route-policy-policy2-10] apply cost 500

[RR2-route-policy-policy2-10] quit

# Configure RR 2 to establish IBGP peer relationships with PE 1, PE 2, and PE 3.

[RR2] bgp 100

[RR2-bgp-default] peer 1.1.1.1 as-number 100

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

[RR2-bgp-default] peer 3.3.3.3 as-number 100

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

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

[RR2-bgp-default] peer 3.3.3.3 connect-interface loopback 0

# Configure BGP to advertise BGP EVPN routes, and disable route target filtering for BGP EVPN routes.

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

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

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

[RR2-bgp-default-evpn] peer 3.3.3.3 enable

[RR2-bgp-default-evpn] undo policy vpn-target

# Configure RR 2 as an RR.

[RR2-bgp-default-evpn] peer 1.1.1.1 reflect-client

[RR2-bgp-default-evpn] peer 2.2.2.2 reflect-client

[RR2-bgp-default-evpn] peer 3.3.3.3 reflect-client

# Enable the RR to change the attributes of routes to be reflected.

[RR2-bgp-default-evpn] reflect change-path-attribute

# Set the local router as the next hop for routes sent to PE 1 and PE 2.

[RR2-bgp-default-evpn] peer 1.1.1.1 next-hop-local

[RR2-bgp-default-evpn] peer 2.2.2.2 next-hop-local

# Add PE 1 and PE 2 to the nearby cluster.

[RR2-bgp-default-evpn] peer 1.1.1.1 reflect-nearby-group

[RR2-bgp-default-evpn] peer 2.2.2.2 reflect-nearby-group

# Apply routing policy policy1 to routes advertised to IBGP peer 1.1.1.1.

[RR2-bgp-default-evpn] peer 1.1.1.1 route-policy policy1 export

# Apply routing policy policy2 to routes advertised to IBGP peer 2.2.2.2.

[RR2-bgp-default-evpn] peer 2.2.2.2 route-policy policy2 export

[RR2-bgp-default-evpn] quit

[RR2-bgp-default] quit

6.     Configure PE 3:

# Configure an LSR ID.

<PE3> system-view

[PE3] interface loopback 0

[PE3-LoopBack0] ip address 3.3.3.3 32

[PE3-LoopBack0] quit

[PE3] mpls lsr-id 3.3.3.3

# Enable L2VPN.

[PE3] l2vpn enable

# Enable global LDP.

[PE3] mpls ldp

[PE3-ldp] quit

# Enable local FRR for EVPN VPWS globally.

[PE3] evpn multihoming vpws-frr local

# Configure HundredGigE 1/0/2 (the interface connected to RR 1), and enable MPLS and LDP on the interface.

[PE3] interface hundredgige 1/0/2

[PE3-HundredGigE1/0/2] ip address 10.1.6.3 24

[PE3-HundredGigE1/0/2] mpls enable

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

[PE3-HundredGigE1/0/2] quit

# Configure HundredGigE 1/0/3 (the interface connected to RR 2), and enable MPLS and LDP on the interface.

[PE3] interface hundredgige 1/0/3

[PE3-HundredGigE1/0/3] ip address 10.1.7.3 24

[PE3-HundredGigE1/0/3] mpls enable

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

[PE3-HundredGigE1/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 10.1.6.0 0.0.0.255

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

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

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

[PE3-ospf-1] quit

# Configure PE 3 to establish IBGP peer relationships with RR 1 and RR 2, and configure BGP to advertise EVPN routes.

[PE3] bgp 100

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

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

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

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

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

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

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

[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 HundredGigE 1/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 hundredgige 1/0/1

[PE3-xcg-vpna-pw1-HundredGigE1/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

7.     Configure CE 2.

<CE2> system-view

[CE2] interface hundredgige 1/0/1

[CE2-Vlan-interface10] ip address 100.1.1.2 24

[CE2-Vlan-interface10] quit

Verifying the configuration

1.     Verify PW information.

# Verify that PE 1 has established a primary PW and a backup PW with PE 3 and has established a bypass PW with 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: 3

1 up, 2 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

4.4.4.4         2                  1151/1403      EVPN   M    0        Up

5.5.5.5         2                  1151/1275      EVPN   B    0        Blocked

2.2.2.2         1                  1151/1151      EVPN   ABY  1        Blocked

# Verify that PE 2 has established a primary PW and a backup PW with PE 3 and has established a bypass PW with PE 1.

<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: 3

1 up, 2 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

5.5.5.5         2                  1152/1404      EVPN   M    0        Up

4.4.4.4         2                  1152/1276      EVPN   B    0        Blocked

1.1.1.1         1                  1152/1152      EVPN   ABY  1        Blocked

2.     Verify that CE 1 and CE 2 can ping each other.

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网