Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 05-EVPN L3VPN configuration | 382.16 KB |
Contents
Configuring an EVPN L3VPN network
Enabling MPLS encapsulation for IP prefix advertisement routes
Enabling EVPN to advertise VPN routes
Enabling communication between EVPN L3VPN and MPLS L3VPN
About communication between EVPN L3VPN and MPLS L3VPN
Enabling BGP VPNv4 or VPNv6 route advertisement for the BGP EVPN address family
Enabling BGP EVPN route advertisement for the BGP VPNv4 or VPNv6 address family
Display and maintenance commands for EVPN L3VPN
EVPN L3VPN configuration examples
Example: Configuring IPv4 EVPN L3VPN
Example: Configuring IPv6 EVPN L3VPN
Example: Enabling communication between IPv4 MPLS L3VPN and IPv4 EVPN L3VPN
Example: Enabling communication between IPv6 MPLS L3VPN and IPv6 EVPN L3VPN
Configuring EVPN L3VPN
About EVPN L3VPN
EVPN supports using MPLS L3VPN for traffic forwarding in the data plane, which is called EVPN L3VPN. EVPN L3VPN provides fast deployment of Layer 2 networks and can convey both Layer 2 and Layer 3 VPN services. In an EVPN L3VPN network, VPN routes are advertised through IP prefix advertisement routes.
Route advertisement
As shown in Figure 1, in an EVPN L3VPN network, CEs and PEs advertises VPN routing information. P routers maintain only the routes within the backbone. A PE maintains only routing information for directly connected VPNs, rather than for all VPNs.
VPN routing information is advertised through the path local CE—ingress PE—egress PE—remote CE.
Figure 1 EVPN L3VPN network model
Route advertisement from the local CE to the ingress PE
The CE advertises standard IPv4 or IPv6 routing information to the ingress PE over a static route, RIP route, OSPF route, IS-IS route, EBGP route, or IBGP route.
Route advertisement from the ingress PE to the egress PE
The ingress PE performs the following operations:
1. Adds RDs and route target attributes to these standard IPv4 or IPv6 routes to create VPN-IPv4 or VPN-IPv6 routes.
2. Assigns MPLS private network labels to the routes to create IP prefix advertisement routes.
3. Advertises the IP prefix advertisement routes to the egress PE.
The egress PE then adds the IP prefix advertisement routes to the routing table of the VPN instance of which an import target matches an export target of the routes.
Route advertisement from the egress PE to the remote CE
The remote CE learns VPN routes from the egress PE through static routes, RIP routes, OSPF routes, IS-IS routes, EBGP routes, or IBGP routes.
Traffic forwarding
In an EVPN L3VPN network, a PE adds the following information into VPN packets:
· Outer tag—Identifies the public tunnel from the local PE to the remote PE. Based on the outer tag, a VPN packet can be forwarded along the public tunnel to the remote PE. The public tunnel can be an LSP or MPLS TE tunnel. For an LSP or MPLS TE tunnel, the outer tag is an MPLS label.
· Inner label—Identifies the remote site. The remote PE uses the inner label to forward packets to the target site of the matching VPN instance. PEs advertise the inner labels assigned to private network routes when advertising BGP EVPN routes.
Figure 2 EVPN L3VPN traffic forwarding
As shown in Figure 2, a VPN packet is forwarded from Site 1 to Site 2 by using the following process:
1. Site 1 sends an IP packet with the destination address 1.1.1.2. CE 1 transmits the packet to PE 1.
2. PE 1 performs the following operations:
a. Finds the matching VPN route based on the inbound interface and destination address of the packet.
b. Labels the packet with both the inner label and the outer tag.
c. Forwards the packet to the public tunnel.
3. P devices forward the packet to PE 2 by the outer tag (MPLS label). The MPLS label is removed from the packet at the penultimate hop.
4. PE 2 performs the following operations:
a. Uses the inner label to find the matching VPN instance to which the destination address of the packet belongs.
b. Looks up the routing table of the VPN instance for the outgoing interface.
c. Removes the inner label and forwards the packet out of the interface to CE 2.
5. CE 2 transmits the packet to the destination through IP forwarding.
When two sites of a VPN are connected to the same PE, the PE directly forwards packets between the two sites through the VPN routing table without adding any tag or label.
EVPN L3VPN tasks at a glance
To configure EVPN L3VPN, perform the following tasks:
1. Configuring basic MPLS L3VPN features
¡ Configuring a VPN instance
¡ Configuring routing between a PE and a CE
For more information about configuration of basic MPLS L3VPN features, see MPLS L3VPN configuration in MPLS Configuration Guide.
2. Configuring an EVPN L3VPN network
¡ Enabling MPLS encapsulation for IP prefix advertisement routes
¡ Enabling EVPN to advertise VPN routes
3. Enabling communication between EVPN L3VPN and MPLS L3VPN
¡ Enabling BGP VPNv4 or VPNv6 route advertisement for the BGP EVPN address family
¡ Enabling BGP EVPN route advertisement for the BGP VPNv4 or VPNv6 address family
4. (Optional.) Configuring BGP EVPN FRR
Configuring an EVPN L3VPN network
Enabling MPLS encapsulation for IP prefix advertisement routes
About this task
By default, a PE advertises IP prefix advertisement routes with VXLAN encapsulation to peers and peer groups. In an EVPN L3VPN network, you must perform this task for PEs to advertise VPN routes through IP prefix advertisement routes.
Restrictions and guidelines
Perform this task on the edge nodes of the EVPN L3VPN network and RRs.
Procedure
1. Enter system view.
system-view
2. 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.
3. Specify remote PEs as BGP peers.
peer { group-name | ipv4-address [ mask-length ] } as-number as-number
4. Enter BGP EVPN address family view.
address-family l2vpn evpn
5. Enable MPLS encapsulation for the IP prefix advertisement routes advertised to a peer or peer group.
peer { group name | ipv4-address [ mask-length ] } advertise encap-type mpls
By default, IP prefix advertisement routes use VXLAN encapsulation.
Enabling EVPN to advertise VPN routes
About this task
This feature enables devices to exchange the routes of a VPN instance by using IP prefix advertisement routes with MPLS encapsulation. After you enable this feature for a VPN instance, the device advertises the routes of the VPN instance through IP prefix advertisement routes. When receiving IP prefix advertisement routes with MPLS encapsulation, the device adds the routes that belong to the VPN instance to the routing table.
Procedure
1. Enter system view.
system-view
2. Enter VPN instance view.
ip vpn-instance vpn-instance-name
3. Enter VPN instance IPv4 or IPv6 unicast address family view.
¡ Enter VPN instance IPv4 unicast address family view.
address-family ipv4 unicast
¡ Enter VPN instance IPv6 unicast address family view.
address-family ipv6 unicast
4. Enable EVPN to advertise the routes of the VPN instance.
evpn mpls routing-enable
By default, EVPN does not advertise the routes of VPN instances.
Enabling communication between EVPN L3VPN and MPLS L3VPN
About communication between EVPN L3VPN and MPLS L3VPN
As shown in Figure 3, when you configure an L3VPN network to convey EVPN service, perform the following tasks on PE 3 to enable communication between EVPN L3VPN and MPLS L3VPN:
· Enable BGP VPNv4 or VPNv6 route advertisement for the BGP EVPN address family.
· Enable BGP EVPN route advertisement for the BGP VPNv4 or VPNv6 address family.
Figure 3 Communication between MPLS L3VPN and EVPN L3VPN
Enabling BGP VPNv4 or VPNv6 route advertisement for the BGP EVPN address family
1. Enter system view.
system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Enter BGP EVPN address family view.
address-family l2vpn evpn
4. Enable BGP VPNv4 or VPNv6 route advertisement for the BGP EVPN address family.
advertise l3vpn route [ replace-rt ][ advertise-policy policy-name ]
By default, BGP VPNv4 or VPNv6 routes are not advertised through the BGP EVPN address family.
Enabling BGP EVPN route advertisement for the BGP VPNv4 or VPNv6 address family
1. Enter system view.
system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Enter BGP VPNv4 address family view or BGP VPNv6 address family view.
address-family { vpnv4 | vpnv6 }
4. Enable BGP EVPN route advertisement for the BGP VPNv4 or VPNv6 address family.
advertise evpn route [ replace-rt ][ advertise-policy policy-name ]
By default, BGP EVPN routes are not advertised through the BGP VPNv4 or VPNv6 address family.
After you execute this command, the device advertises IP prefix advertisement routes and MAC/IP advertisement routes that contain host route information through the BGP VPNv4 or VPNv6 address family.
Configuring BGP EVPN FRR
About this task
BGP EVPN FRR enables the device to calculate backup routes for all routes of the BGP EVPN address family to reduce the traffic interruption caused by link or device failures on the MPLS or IP backbone. If the device learns two unequal-cost routes destined for the same network from different peers, the optimal route is backed up by the other route. When the optimal route becomes unavailable, the device uses the backup route to forward traffic. At the same time, the device calculates a new optimal route and then uses it to direct traffic forwarding.
Restrictions and guidelines
This feature might cause routing loops in certain conditions. Make sure you are fully aware of this feature when you use it on a live network.
Procedure
1. Enter system view.
system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Enter BGP EVPN address family view.
address-family l2vpn evpn
4. Enable BGP EVPN FRR.
pic
By default, BGP EVPN FRR is disabled.
For more information about this command, see BGP commands in Layer 3—IP Routing Command Reference.
Display and maintenance commands for EVPN L3VPN
Execute display commands in any view.
|
Task |
Command |
|
Display incoming labels for IP prefix advertisement routes. |
display bgp [ instance instance-name ] l2vpn evpn inlabel |
|
Display BGP VPNv4 peer group information. |
display bgp [ instance instance-name ] group vpnv4 [ vpn-instance vpn-instance-name ] [ group-name group-name ] |
|
Display BGP VPNv6 peer group information. |
display bgp [ instance instance-name ] group vpnv6 [ group-name group-name ] |
|
Display BGP VPNv4 peer information. |
display bgp [ instance instance-name ] peer vpnv4 [ vpn-instance vpn-instance-name ] [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ] |
|
Display BGP VPNv6 peer information. |
display bgp [ instance instance-name ] peer vpnv6 [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ] |
|
Display BGP VPNv4 routes. |
display bgp [ instance instance-name ] routing-table vpnv4 [ [ route-distinguisher route-distinguisher ] [ ipv4-address [ { mask-length | mask } [ longest-match ] ] | ipv4-address [ mask-length | mask ] advertise-info | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } ] | [ vpn-instance vpn-instance-name ] peer ipv4-address { advertised-routes | received-routes } [ ipv4-address [ mask-length | mask ] | statistics ] | statistics ] |
|
Display BGP VPNv6 routes. |
display bgp [ instance instance-name ] routing-table vpnv6 [ [ route-distinguisher route-distinguisher ] [ ipv6-address prefix-length [ advertise-info ] | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } ] | peer ipv4-address { advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ] | statistics ] |
|
Display routing table information for a VPN instance. |
display ip routing-table vpn-instance vpn-instance-name [ statistics | verbose ] |
|
Display information about VPN instances. |
display ip vpn-instance [ instance-name vpn-instance-name ] |
|
|
NOTE: For more information about the display ip routing-table vpn-instance command, see IP routing basics commands in Layer 3—IP Routing Command Reference. |
|
|
NOTE: For more information about the following commands, see MPLS L3VPN commands in MPLS Command Reference: · display bgp group vpnv4. · display bgp peer vpnv4. · display bgp routing-table vpnv4. · display ip vpn-instance |
EVPN L3VPN configuration examples
Example: Configuring IPv4 EVPN L3VPN
Network configuration
As shown in Figure 4:
· Configure IPv4 EVPN L3VPN for different sites of a VPN instance to communicate with each other.
· Configure route target 111:1 for VPN 1 and route target 222:2 for VPN 2 to isolate these VPN instances.
· Configure the CE and the PE of each site to use EBGP to exchange VPN routes.
· Configure the PEs to communicate through OSPF and to exchange BGP EVPN routes through MP-IBGP.
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
CE 1 |
GE1/2/0/1 |
10.1.1.1/24 |
P |
Loop0 |
2.2.2.9/32 |
|
PE 1 |
Loop0 |
1.1.1.9/32 |
|
GE1/2/0/4 |
172.1.1.2/24 |
|
|
GE1/2/0/1 |
10.1.1.2/24 |
|
GE1/2/0/5 |
172.2.1.1/24 |
|
|
GE1/2/0/2 |
10.2.1.2/24 |
PE 2 |
Loop0 |
3.3.3.9/32 |
|
|
GE1/2/0/4 |
172.1.1.1/24 |
|
GE1/2/0/1 |
10.3.1.2/24 |
|
CE 2 |
GE1/2/0/1 |
10.2.1.1/24 |
|
GE1/2/0/2 |
10.4.1.2/24 |
|
CE 3 |
GE1/2/0/1 |
10.3.1.1/24 |
|
GE1/2/0/4 |
172.2.1.2/24 |
|
CE 4 |
GE1/2/0/1 |
10.4.1.1/24 |
|
|
|
Procedure
1. Configure an IGP on the MPLS backbone for the PEs and P device to reach one another:
# Configure PE 1.
<PE1> system-view
[PE1] interface loopback 0
[PE1-LoopBack0] ip address 1.1.1.9 32
[PE1-LoopBack0] quit
[PE1] interface gigabitethernet 1/2/0/4
[PE1-GigabitEthernet1/2/0/4] ip address 172.1.1.1 24
[PE1-GigabitEthernet1/2/0/4] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255
[PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] interface loopback 0
[P-LoopBack0] ip address 2.2.2.9 32
[P-LoopBack0] quit
[P] interface gigabitethernet 1/2/0/4
[P-GigabitEthernet1/2/0/4] ip address 172.1.1.2 24
[P-GigabitEthernet1/2/0/4] quit
[P] interface gigabitethernet 1/2/0/5
[P-GigabitEthernet1/2/0/5] ip address 172.2.1.1 24
[P-GigabitEthernet1/2/0/5] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 172.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE 2.
<PE2> system-view
[PE2] interface loopback 0
[PE2-LoopBack0] ip address 3.3.3.9 32
[PE2-LoopBack0] quit
[PE2] interface gigabitethernet 1/2/0/4
[PE2-GigabitEthernet1/2/0/4] ip address 172.2.1.2 24
[PE2-GigabitEthernet1/2/0/4] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] network 172.2.1.0 0.0.0.255
[PE2-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
# Execute the display ospf peer command to verify that OSPF adjacencies in Full state have been established between PE 1, P, and PE 2. Execute the display ip routing-table command to verify that the PEs have learned the routes to the loopback interfaces of each other. (Details not shown.)
2. Configure basic MPLS and MPLS LDP on the MPLS backbone to establish LDP LSPs:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] quit
[PE1] interface gigabitethernet 1/2/0/4
[PE1-GigabitEthernet1/2/0/4] mpls enable
[PE1-GigabitEthernet1/2/0/4] mpls ldp enable
[PE1-GigabitEthernet1/2/0/4] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] quit
[P] interface gigabitethernet 1/2/0/4
[P-GigabitEthernet1/2/0/4] mpls enable
[P-GigabitEthernet1/2/0/4] mpls ldp enable
[P-GigabitEthernet1/2/0/4] quit
[P] interface gigabitethernet 1/2/0/5
[P-GigabitEthernet1/2/0/5] mpls enable
[P-GigabitEthernet1/2/0/5] mpls ldp enable
[P-GigabitEthernet1/2/0/5] quit
# Configure PE 2.
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls ldp
[PE2-ldp] quit
[PE2] interface gigabitethernet 1/2/0/4
[PE2-GigabitEthernet1/2/0/4] mpls enable
[PE2-GigabitEthernet1/2/0/4] mpls ldp enable
[PE2-GigabitEthernet1/2/0/4] quit
# Execute the display mpls ldp peer command to verify that LDP sessions in Operational state have been established between PE 1, P, and PE 2. Execute the display mpls ldp lsp command to verify that the LSPs have been established by LDP. (Details not shown.)
3. Configure VPN instances on PEs to allow CE access:
# Configure PE 1.
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] route-distinguisher 100:1
[PE1-vpn-instance-vpn1] vpn-target 111:1
[PE1-vpn-instance-vpn1] quit
[PE1] ip vpn-instance vpn2
[PE1-vpn-instance-vpn2] route-distinguisher 100:2
[PE1-vpn-instance-vpn2] vpn-target 222:2
[PE1-vpn-instance-vpn2] quit
[PE1] interface gigabitethernet 1/2/0/1
[PE1-GigabitEthernet1/2/0/1] ip binding vpn-instance vpn1
[PE1-GigabitEthernet1/2/0/1] ip address 10.1.1.2 24
[PE1-GigabitEthernet1/2/0/1] quit
[PE1] interface gigabitethernet 1/2/0/2
[PE1-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn2
[PE1-GigabitEthernet1/2/0/2] ip address 10.2.1.2 24
[PE1-GigabitEthernet1/2/0/2] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] route-distinguisher 200:1
[PE2-vpn-instance-vpn1] vpn-target 111:1
[PE2-vpn-instance-vpn1] quit
[PE2] ip vpn-instance vpn2
[PE2-vpn-instance-vpn2] route-distinguisher 200:2
[PE2-vpn-instance-vpn2] vpn-target 222:2
[PE2-vpn-instance-vpn2] quit
[PE2] interface gigabitethernet 1/2/0/1
[PE2-GigabitEthernet1/2/0/1] ip binding vpn-instance vpn1
[PE2-GigabitEthernet1/2/0/1] ip address 10.3.1.2 24
[PE2-GigabitEthernet1/2/0/1] quit
[PE2] interface gigabitethernet 1/2/0/2
[PE2-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn2
[PE2-GigabitEthernet1/2/0/2] ip address 10.4.1.2 24
[PE2-GigabitEthernet1/2/0/2] quit
# Configure IP addresses for the CEs according to Figure 4. (Details not shown.)
# Execute the display ip vpn-instance command on the PEs to display the configuration of the VPN instance, for example, on PE 1.
[PE1] display ip vpn-instance
Total VPN-Instances configured : 2
Total IPv4 VPN-Instances configured : 2
Total IPv6 VPN-Instances configured : 2
Total IPv4 VPN-Instances EVPN configured : 0
Total IPv6 VPN-Instances EVPN configured : 0
VPN-Instance Name RD Address family Create time
vpn1 100:1 IPv4/IPv6 2020/07/26 08:02:38
vpn2 100:2 IPv4/IPv6 2020/07/26 08:02:38
# Use the ping command on the PEs to verify that the PEs can ping their attached CEs, for example, on PE 1.
[PE1] ping -vpn-instance vpn1 10.1.1.1
Ping 10.1.1.1 (10.1.1.1): 56 data bytes, press CTRL_C to break
56 bytes from 10.1.1.1: icmp_seq=0 ttl=255 time=1.000 ms
56 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=2.000 ms
56 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=0.000 ms
56 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=1.000 ms
56 bytes from 10.1.1.1: icmp_seq=4 ttl=255 time=0.000 ms
--- Ping statistics for 10.1.1.1 in VPN instance vpn1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/0.800/2.000/0.748 ms
4. Establish EBGP peer relationships between PEs and CEs, and redistribute VPN routes into BGP:
# Configure CE 1.
<CE1> system-view
[CE1] bgp 65410
[CE1-bgp-default] peer 10.1.1.2 as-number 100
[CE1-bgp-default] address-family ipv4 unicast
[CE1-bgp-default-ipv4] peer 10.1.1.2 enable
[CE1-bgp-default-ipv4] import-route direct
[CE1-bgp-default-ipv4] quit
[CE1-bgp-default] quit
# Configure the other three CEs in the same way that CE 1 is configured. (Details not shown.)
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] ip vpn-instance vpn1
[PE1-bgp-default-vpn1] peer 10.1.1.1 as-number 65410
[PE1-bgp-default-vpn1] address-family ipv4 unicast
[PE1-bgp-default-ipv4-vpn1] peer 10.1.1.1 enable
[PE1-bgp-default-ipv4-vpn1] quit
[PE1-bgp-default-vpn1] quit
[PE1-bgp-default] ip vpn-instance vpn2
[PE1-bgp-default-vpn2] peer 10.2.1.1 as-number 65420
[PE1-bgp-default-vpn2] address-family ipv4 unicast
[PE1-bgp-default-ipv4-vpn2] peer 10.2.1.1 enable
[PE1-bgp-default-ipv4-vpn2] quit
[PE1-bgp-default-vpn1] quit
[PE1-bgp-default] quit
# Configure PE 2 in the same way that PE 1 is configured. (Details not shown.)
# Execute the display bgp peer ipv4 vpn-instance command on the PEs to verify that a BGP peer relationship in Established state has been established between a PE and a CE. (Details not shown.)
5. Create an MP-IBGP peer relationship between PEs:
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] peer 3.3.3.9 as-number 100
[PE1-bgp-default] peer 3.3.3.9 connect-interface loopback 0
[PE1-bgp-default] address-family l2vpn evpn
[PE1-bgp-default-evpn] peer 3.3.3.9 enable
[PE1-bgp-default-evpn] quit
[PE1-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] peer 1.1.1.9 as-number 100
[PE2-bgp-default] peer 1.1.1.9 connect-interface loopback 0
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 1.1.1.9 enable
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
# Execute the display bgp peer l2vpn evpn command on the PEs to verify that a BGP peer relationship in Established state has been established between the PEs. (Details not shown.)
6. Enable EVPN to advertise VPN routes on the PEs:
# Configure PE 1.
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] address-family ipv4
[PE1-vpn-ipv4-vpn1] evpn mpls routing-enable
[PE1-vpn-ipv4-vpn1] quit
[PE1-vpn-instance-vpn1] quit
[PE1] ip vpn-instance vpn2
[PE1-vpn-instance-vpn2] address-family ipv4
[PE1-vpn-ipv4-vpn2] evpn mpls routing-enable
[PE1-vpn-ipv4-vpn2] quit
[PE1-vpn-instance-vpn2] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] address-family ipv4
[PE2-vpn-ipv4-vpn1] evpn mpls routing-enable
[PE2-vpn-ipv4-vpn1] quit
[PE2-vpn-instance-vpn1] quit
[PE2] ip vpn-instance vpn2
[PE2-vpn-instance-vpn2] address-family ipv4
[PE2-vpn-ipv4-vpn2] evpn mpls routing-enable
[PE2-vpn-ipv4-vpn2] quit
[PE2-vpn-instance-vpn2] quit
# Execute the display bgp l2vpn evpn command on the PEs to verify that the VPN routes received from CEs have been added to the EVPN routing table. (Details not shown.)
7. Enable MPLS encapsulation for the IP prefix advertisement routes on the PEs:
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] address-family l2vpn evpn
[PE1-bgp-default-evpn] peer 3.3.3.9 advertise encap-type mpls
[PE1-bgp-default-evpn] peer 3.3.3.9 next-hop-local
[PE1-bgp-default-evpn] quit
[PE1-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 1.1.1.9 advertise encap-type mpls
[PE2-bgp-default-evpn] peer 1.1.1.9 next-hop-local
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
# Execute the display bgp l2vpn evpn command to verify that the PEs have received IP prefix advertisement routes from one another.
Verifying the configuration
# Verify that a PE has the route to the remote CE in the same VPN instance, for example, PE 1.
[PE1] display ip routing-table vpn-instance vpn1
Destinations : 11 Routes : 11
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.1.1.0/24 Direct 0 0 10.1.1.2 GE1/2/0/1
10.1.1.0/32 Direct 0 0 10.1.1.2 GE1/2/0/1
10.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0
10.1.1.255/32 Direct 0 0 10.1.1.2 GE1/2/0/1
10.3.1.0/24 BGP 255 0 3.3.3.9 GE1/2/0/4
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
# Verify that CEs of the same VPN can ping each other, and CEs of different VPNs cannot. For example, CE 1 can ping CE 3 (10.3.1.1), but it cannot ping CE 4 (10.4.1.1). (Details not shown.)
Example: Configuring IPv6 EVPN L3VPN
Network configuration
As shown in Figure 5:
· Configure IPv6 EVPN L3VPN for different sites of a VPN instance to communicate with each other.
· Configure route target 111:1 for VPN 1 and route target 222:2 for VPN 2 to isolate these VPN instances.
· Configure the CE and the PE of each site to use EBGP to exchange VPN routes.
· Configure the PEs to communicate through OSPF and to exchange BGP EVPN routes through MP-IBGP.
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
CE 1 |
GE1/2/0/1 |
2001:1::1/96 |
P |
Loop0 |
2.2.2.9/32 |
|
PE 1 |
Loop0 |
1.1.1.9/32 |
|
GE1/2/0/4 |
172.1.1.2/24 |
|
|
GE1/2/0/1 |
2001:1::2/96 |
|
GE1/2/0/5 |
172.2.1.1/24 |
|
|
GE1/2/0/2 |
2001:2::2/96 |
PE 2 |
Loop0 |
3.3.3.9/32 |
|
|
GE1/2/0/4 |
172.1.1.1/24 |
|
GE1/2/0/1 |
2001:3::2/96 |
|
CE 2 |
GE1/2/0/1 |
2001:2::1/96 |
|
GE1/2/0/2 |
2001:4::2/96 |
|
CE 3 |
GE1/2/0/1 |
2001:3::1/96 |
|
GE1/2/0/4 |
172.2.1.2/24 |
|
CE 4 |
GE1/2/0/1 |
2001:4::1/96 |
|
|
|
Procedure
1. Configure an IGP on the MPLS backbone for the PEs and P device to reach one another:
# Configure PE 1.
<PE1> system-view
[PE1] interface loopback 0
[PE1-LoopBack0] ip address 1.1.1.9 32
[PE1-LoopBack0] quit
[PE1] interface gigabitethernet 1/2/0/4
[PE1-GigabitEthernet1/2/0/4] ip address 172.1.1.1 24
[PE1-GigabitEthernet1/2/0/4] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255
[PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] interface loopback 0
[P-LoopBack0] ip address 2.2.2.9 32
[P-LoopBack0] quit
[P] interface gigabitethernet 1/2/0/4
[P-GigabitEthernet1/2/0/4] ip address 172.1.1.2 24
[P-GigabitEthernet1/2/0/4] quit
[P] interface gigabitethernet 1/2/0/5
[P-GigabitEthernet1/2/0/5] ip address 172.2.1.1 24
[P-GigabitEthernet1/2/0/5] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0] network 172.1.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 172.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE 2.
<PE2> system-view
[PE2] interface loopback 0
[PE2-LoopBack0] ip address 3.3.3.9 32
[PE2-LoopBack0] quit
[PE2] interface gigabitethernet 1/2/0/4
[PE2-GigabitEthernet1/2/0/4] ip address 172.2.1.2 24
[PE2-GigabitEthernet1/2/0/4] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] network 172.2.1.0 0.0.0.255
[PE2-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
# Execute the display ospf peer command to verify that OSPF adjacencies in Full state have been established between PE 1, P, and PE 2. Execute the display ip routing-table command to verify that the PEs have learned the routes to the loopback interfaces of each other. (Details not shown.)
2. Configure basic MPLS and MPLS LDP on the MPLS backbone to establish LDP LSPs:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] quit
[PE1] interface gigabitethernet 1/2/0/4
[PE1-GigabitEthernet1/2/0/4] mpls enable
[PE1-GigabitEthernet1/2/0/4] mpls ldp enable
[PE1-GigabitEthernet1/2/0/4] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] quit
[P] interface gigabitethernet 1/2/0/4
[P-GigabitEthernet1/2/0/4] mpls enable
[P-GigabitEthernet1/2/0/4] mpls ldp enable
[P-GigabitEthernet1/2/0/4] quit
[P] interface gigabitethernet 1/2/0/5
[P-GigabitEthernet1/2/0/5] mpls enable
[P-GigabitEthernet1/2/0/5] mpls ldp enable
[P-GigabitEthernet1/2/0/5] quit
# Configure PE 2.
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls ldp
[PE2-ldp] quit
[PE2] interface gigabitethernet 1/2/0/4
[PE2-GigabitEthernet1/2/0/4] mpls enable
[PE2-GigabitEthernet1/2/0/4] mpls ldp enable
[PE2-GigabitEthernet1/2/0/4] quit
# Execute the display mpls ldp peer command to verify that LDP sessions in Operational state have been established between PE 1, P, and PE 2. Execute the display mpls ldp lsp command to verify that the LSPs have been established by LDP. (Details not shown.)
3. Configure VPN instances on PEs to allow CE access:
# Configure PE 1.
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] route-distinguisher 100:1
[PE1-vpn-instance-vpn1] vpn-target 111:1
[PE1-vpn-instance-vpn1] quit
[PE1] ip vpn-instance vpn2
[PE1-vpn-instance-vpn2] route-distinguisher 100:2
[PE1-vpn-instance-vpn2] vpn-target 222:2
[PE1-vpn-instance-vpn2] quit
[PE1] interface gigabitethernet 1/2/0/1
[PE1-GigabitEthernet1/2/0/1] ip binding vpn-instance vpn1
[PE1-GigabitEthernet1/2/0/1] ipv6 address 2001:1::2 96
[PE1-GigabitEthernet1/2/0/1] quit
[PE1] interface gigabitethernet 1/2/0/2
[PE1-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn2
[PE1-GigabitEthernet1/2/0/2] ipv6 address 2001:2::2 96
[PE1-GigabitEthernet1/2/0/2] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] route-distinguisher 200:1
[PE2-vpn-instance-vpn1] vpn-target 111:1
[PE2-vpn-instance-vpn1] quit
[PE2] ip vpn-instance vpn2
[PE2-vpn-instance-vpn2] route-distinguisher 200:2
[PE2-vpn-instance-vpn2] vpn-target 222:2
[PE2-vpn-instance-vpn2] quit
[PE2] interface gigabitethernet 1/2/0/1
[PE2-GigabitEthernet1/2/0/1] ip binding vpn-instance vpn1
[PE2-GigabitEthernet1/2/0/1] ipv6 address 2001:3::2 96
[PE2-GigabitEthernet1/2/0/1] quit
[PE2] interface gigabitethernet 1/2/0/2
[PE2-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn2
[PE2-GigabitEthernet1/2/0/2] ipv6 address 2001:4::2 96
[PE2-GigabitEthernet1/2/0/2] quit
# Configure IP addresses for the CEs according to Figure 5. (Details not shown.)
# Execute the display ip vpn-instance command on the PEs to display the configuration of the VPN instance, for example, on PE 1.
[PE1] display ip vpn-instance
Total VPN-Instances configured : 2
Total IPv4 VPN-Instances configured : 2
Total IPv6 VPN-Instances configured : 2
Total IPv4 VPN-Instances EVPN configured : 0
Total IPv6 VPN-Instances EVPN configured : 0
VPN-Instance Name RD Address family Create time
vpn1 100:1 IPv4/IPv6 2020/07/26 08:02:38
vpn2 100:2 IPv4/IPv6 2020/07/26 08:02:38
# Use the ping command on the PEs to verify that the PEs can ping their attached CEs, for example, on PE 1.
[PE1] ping ipv6 -vpn-instance vpn1 2001:1::1
Ping6(56 bytes) 2001:1::2 --> 2001:1::1, press CTRL_C to break
56 bytes from 2001:1::1, icmp_seq=0 hlim=64 time=9.000 ms
56 bytes from 2001:1::1, icmp_seq=1 hlim=64 time=1.000 ms
56 bytes from 2001:1::1, icmp_seq=2 hlim=64 time=0.000 ms
56 bytes from 2001:1::1, icmp_seq=3 hlim=64 time=0.000 ms
56 bytes from 2001:1::1, icmp_seq=4 hlim=64 time=0.000 ms
--- Ping6 statistics for 2001:1::1 in VPN instance vpn1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/2.000/9.000/3.521 ms
4. Establish EBGP peer relationships between PEs and CEs, and redistribute VPN routes into BGP:
# Configure CE 1.
<CE1> system-view
[CE1] bgp 65410
[CE1-bgp-default] peer 2001:1::2 as-number 100
[CE1-bgp-default] address-family ipv6 unicast
[CE1-bgp-default-ipv6] peer 2001:1::2 enable
[CE1-bgp-default-ipv6] import-route direct
[CE1-bgp-default-ipv6] quit
[CE1-bgp-default] quit
# Configure the other three CEs in the same way that CE 1 is configured. (Details not shown.)
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] ip vpn-instance vpn1
[PE1-bgp-default-vpn1] peer 2001:1::1 as-number 65410
[PE1-bgp-default-vpn1] address-family ipv6 unicast
[PE1-bgp-default-ipv6-vpn1] peer 2001:1::1 enable
[PE1-bgp-default-ipv6-vpn1] quit
[PE1-bgp-default-vpn1] quit
[PE1-bgp-default] ip vpn-instance vpn2
[PE1-bgp-default-vpn2] peer 2001:2::1 as-number 65420
[PE1-bgp-default-vpn2] address-family ipv6 unicast
[PE1-bgp-default-ipv6-vpn2] peer 2001:2::1 enable
[PE1-bgp-default-ipv6-vpn2] quit
[PE1-bgp-default-vpn2] quit
[PE1-bgp-default] quit
# Configure PE 2 in the same way that PE 1 is configured. (Details not shown.)
# Execute the display bgp peer ipv6 vpn-instance command on the PEs to verify that a BGP peer relationship in Established state has been established between a PE and a CE. (Details not shown.)
5. Create an MP-IBGP peer relationship between PEs:
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] peer 3.3.3.9 as-number 100
[PE1-bgp-default] peer 3.3.3.9 connect-interface loopback 0
[PE1-bgp-default] address-family l2vpn evpn
[PE1-bgp-default-evpn] peer 3.3.3.9 enable
[PE1-bgp-default-evpn] quit
[PE1-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] peer 1.1.1.9 as-number 100
[PE2-bgp-default] peer 1.1.1.9 connect-interface loopback 0
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 1.1.1.9 enable
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
# Execute the display bgp peer l2vpn evpn command on the PEs to verify that a BGP peer relationship in Established state has been established between the PEs. (Details not shown.)
6. Enable EVPN to advertise VPN routes on the PEs:
# Configure PE 1.
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] address-family ipv6
[PE1-vpn-ipv6-vpn1] evpn mpls routing-enable
[PE1-vpn-ipv6-vpn1] quit
[PE1-vpn-instance-vpn1] quit
[PE1] ip vpn-instance vpn2
[PE1-vpn-instance-vpn2] address-family ipv6
[PE1-vpn-ipv6-vpn2] evpn mpls routing-enable
[PE1-vpn-ipv6-vpn2] quit
[PE1-vpn-instance-vpn2] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] address-family ipv6
[PE2-vpn-ipv6-vpn1] evpn mpls routing-enable
[PE2-vpn-ipv6-vpn1] quit
[PE2-vpn-instance-vpn1] quit
[PE2] ip vpn-instance vpn2
[PE2-vpn-instance-vpn2] address-family ipv6
[PE2-vpn-ipv6-vpn2] evpn mpls routing-enable
[PE2-vpn-ipv6-vpn2] quit
[PE2-vpn-instance-vpn2] quit
# Execute the display bgp l2vpn evpn command on the PEs to verify that the VPN routes received from CEs have been added to the EVPN routing table. (Details not shown.)
7. Enable MPLS encapsulation for the IP prefix advertisement routes on the PEs:
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] address-family l2vpn evpn
[PE1-bgp-default-evpn] peer 3.3.3.9 advertise encap-type mpls
[PE1-bgp-default-evpn] peer 3.3.3.9 next-hop-local
[PE1-bgp-default-evpn] quit
[PE1-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 1.1.1.9 advertise encap-type mpls
[PE2-bgp-default-evpn] peer 1.1.1.9 next-hop-local
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
# Execute the display bgp l2vpn evpn command to verify that the PEs have received IP prefix advertisement routes from one another.
Verifying the configuration
# Verify that a PE has the route to the remote CE in the same VPN instance, for example, PE 1.
[PE1] display ipv6 routing-table vpn-instance vpn1
Destinations : 5 Routes : 5
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2001:1::/96 Protocol : Direct
NextHop : :: Preference: 0
Interface : GE1/2/0/1 Cost : 0
Destination: 2001:1::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2001:3::/96 Protocol : BGP4+
NextHop : ::FFFF:3.3.3.9 Preference: 255
Interface : GE1/2/0/4 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
[PE1] display ipv6 routing-table vpn-instance vpn2
Destinations : 5 Routes : 5
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2001:2::/96 Protocol : Direct
NextHop : :: Preference: 0
Interface : GE1/2/0/2 Cost : 0
Destination: 2001:2::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2001:4::/96 Protocol : BGP4+
NextHop : ::FFFF:3.3.3.9 Preference: 255
Interface : GE1/2/0/4 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
# Verify that CEs of the same VPN can ping each other, and CEs of different VPNs cannot. For example, CE 1 can ping CE 3 (2001:3::1), but it cannot ping CE 4 (2001:4::1). (Details not shown.)
Example: Enabling communication between IPv4 MPLS L3VPN and IPv4 EVPN L3VPN
Network configuration
As shown in Figure 6:
· Configure EVPN for CE 1 and CE 2 of VPN 1 to communicate.
· Configure OSPF as the IGP on the MPLS backbone for the P device and PEs to communicate.
· Configure the CEs to exchange VPN routes through EBGP.
· Configure the P device and PE 1 to exchange VPNv4 routes through MP-IBGP, and configure the P device and PE 2 to exchange BGP EVPN routes through MP-IBGP.
· Configure the P device as an RR to reflect routes between the PEs.
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
PE 1 |
Loop0 |
1.1.1.9/32 |
P |
Loop0 |
2.2.2.9/32 |
|
|
GE1/2/0/1 |
10.1.1.1/24 |
|
GE1/2/0/1 |
10.1.1.2/24 |
|
|
GE1/2/0/2 |
172.1.1.2/24 |
|
GE1/2/0/2 |
10.2.1.2/24 |
|
PE 2 |
Loop0 |
3.3.3.9/32 |
CE 1 |
GE1/2/0/1 |
172.1.1.1/24 |
|
|
GE1/2/0/1 |
10.2.1.1/24 |
CE 2 |
GE1/2/0/1 |
172.2.1.1/24 |
|
|
GE1/2/0/2 |
172.2.1.2/24 |
|
|
|
Procedure
1. Configure an IGP on the MPLS backbone for the PEs and P device to reach one another:
# Configure PE 1.
<PE1> system-view
[PE1] interface loopback 0
[PE1-LoopBack0] ip address 1.1.1.9 32
[PE1-LoopBack0] quit
[PE1] interface gigabitethernet 1/2/0/1
[PE1-GigabitEthernet1/2/0/1] ip address 10.1.1.1 24
[PE1-GigabitEthernet1/2/0/1] quit
[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 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] interface loopback 0
[P-LoopBack0] ip address 2.2.2.9 32
[P-LoopBack0] quit
[P] interface gigabitethernet 1/2/0/1
[P-GigabitEthernet1/2/0/1] ip address 10.1.1.2 24
[P-GigabitEthernet1/2/0/1] quit
[P] interface gigabitethernet 1/2/0/2
[P-GigabitEthernet1/2/0/2] ip address 10.2.1.2 24
[P-GigabitEthernet1/2/0/2] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE 2.
<PE2> system-view
[PE2] interface loopback 0
[PE2-LoopBack0] ip address 3.3.3.9 32
[PE2-LoopBack0] quit
[PE2] interface gigabitethernet 1/2/0/1
[PE2-GigabitEthernet1/2/0/1] ip address 10.2.1.1 24
[PE2-GigabitEthernet1/2/0/1] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[PE2-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
# Execute the display ospf peer command to verify that OSPF adjacencies in Full state have been established between PE 1, P, and PE 2. Execute the display ip routing-table command to verify that the PEs have learned the routes to the loopback interfaces of each other. (Details not shown.)
2. Configure basic MPLS and MPLS LDP on the MPLS backbone to establish LDP LSPs:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] quit
[PE1] interface gigabitethernet 1/2/0/1
[PE1-GigabitEthernet1/2/0/1] mpls enable
[PE1-GigabitEthernet1/2/0/1] mpls ldp enable
[PE1-GigabitEthernet1/2/0/1] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] quit
[P] interface gigabitethernet 1/2/0/1
[P-GigabitEthernet1/2/0/1] mpls enable
[P-GigabitEthernet1/2/0/1] mpls ldp enable
[P-GigabitEthernet1/2/0/1] quit
[P] interface gigabitethernet 1/2/0/2
[P-GigabitEthernet1/2/0/2] mpls enable
[P-GigabitEthernet1/2/0/2] mpls ldp enable
[P-GigabitEthernet1/2/0/2] quit
# Configure PE 2.
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls ldp
[PE2-ldp] quit
[PE2] interface gigabitethernet 1/2/0/1
[PE2-GigabitEthernet1/2/0/1] mpls enable
[PE2-GigabitEthernet1/2/0/1] mpls ldp enable
[PE2-GigabitEthernet1/2/0/1] quit
# Execute the display mpls ldp peer command to verify that LDP sessions in Operational state have been established between PE 1, P, and PE 2. Execute the display mpls ldp lsp command to verify that the LSPs have been established by LDP. (Details not shown.)
3. Configure VPN instances on the PEs to allow CE access, and configure a VPN instance on the P device to allow MPLS L3VPN access and EVPN L3VPN access:
# Configure PE 1.
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] route-distinguisher 100:1
[PE1-vpn-instance-vpn1] vpn-target 111:1
[PE1-vpn-instance-vpn1] quit
[PE1] interface gigabitethernet 1/2/0/2
[PE1-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn1
[PE1-GigabitEthernet1/2/0/2] ip address 172.1.1.2 24
[PE1-GigabitEthernet1/2/0/2] quit
# Configure the P device.
[P] ip vpn-instance vpn1
[P-vpn-instance-vpn1] route-distinguisher 100:1
[P-vpn-instance-vpn1] vpn-target 111:1
[P-vpn-instance-vpn1] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] route-distinguisher 200:1
[PE2-vpn-instance-vpn1] vpn-target 111:1
[PE2-vpn-instance-vpn1] quit
[PE2] interface gigabitethernet 1/2/0/2
[PE2-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn1
[PE2-GigabitEthernet1/2/0/2] ip address 172.2.1.2 24
[PE2-GigabitEthernet1/2/0/2] quit
# Configure IP addresses for the CEs according to Figure 6. (Details not shown.)
# Execute the display ip vpn-instance command on the PEs to display the configuration of the VPN instance, for example, on PE 1.
[PE1] display ip vpn-instance
Total VPN-Instances configured : 1
Total IPv4 VPN-Instances configured : 1
Total IPv6 VPN-Instances configured : 1
Total IPv4 VPN-Instances EVPN configured : 0
Total IPv6 VPN-Instances EVPN configured : 0
VPN-Instance Name RD Address family Create time
vpn1 100:1 IPv4/IPv6 2020/07/26 08:02:38
# Use the ping command on the PEs to verify that the PEs can ping their attached CEs, for example, on PE 1.
[PE1] ping -vpn-instance vpn1 172.1.1.1
Ping 10.1.1.1 (172.1.1.1): 56 data bytes, press CTRL_C to break
56 bytes from 172.1.1.1: icmp_seq=0 ttl=255 time=1.000 ms
56 bytes from 172.1.1.1: icmp_seq=1 ttl=255 time=2.000 ms
56 bytes from 172.1.1.1: icmp_seq=2 ttl=255 time=0.000 ms
56 bytes from 172.1.1.1: icmp_seq=3 ttl=255 time=1.000 ms
56 bytes from 172.1.1.1: icmp_seq=4 ttl=255 time=0.000 ms
--- Ping statistics for 172.1.1.1 in VPN instance vpn1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/0.800/2.000/0.748 ms
4. Establish EBGP peer relationships between PEs and CEs, and redistribute VPN routes into BGP:
# Configure CE 1.
<CE1> system-view
[CE1] bgp 65410
[CE1-bgp-default] peer 172.1.1.2 as-number 100
[CE1-bgp-default] address-family ipv4 unicast
[CE1-bgp-default-ipv4] peer 172.1.1.2 enable
[CE1-bgp-default-ipv4] import-route direct
[CE1-bgp-default-ipv4] quit
[CE1-bgp-default] quit
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] ip vpn-instance vpn1
[PE1-bgp-default-vpn1] peer 172.1.1.1 as-number 65410
[PE1-bgp-default-vpn1] address-family ipv4 unicast
[PE1-bgp-default-ipv4-vpn1] peer 172.1.1.1 enable
[PE1-bgp-default-ipv4-vpn1] quit
[PE1-bgp-default-vpn1] quit
# Configure CE 2.
<CE2> system-view
[CE2] bgp 65420
[CE2-bgp-default] peer 172.2.1.2 as-number 100
[CE2-bgp-default] address-family ipv4 unicast
[CE2-bgp-default-ipv4] peer 172.2.1.2 enable
[CE2-bgp-default-ipv4] import-route direct
[CE2-bgp-default-ipv4] quit
[CE2-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] ip vpn-instance vpn1
[PE2-bgp-default-vpn1] peer 172.2.1.1 as-number 65420
[PE2-bgp-default-vpn1] address-family ipv4 unicast
[PE2-bgp-default-ipv4-vpn1] peer 172.2.1.1 enable
[PE2-bgp-default-ipv4-vpn1] quit
[PE2-bgp-default-vpn1] quit
# Execute the display bgp peer ipv4 vpn-instance command on the PEs to verify that a BGP peer relationship in Established state has been established between a PE and a CE. (Details not shown.)
5. Configure route exchange between the P device and the PEs, and configure the P device as an RR:
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] peer 2.2.2.9 as-number 100
[PE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0
[PE1-bgp-default] address-family vpnv4
[PE1-bgp-default-vpnv4] peer 2.2.2.9 enable
[PE1-bgp-default-vpnv4] quit
[PE1-bgp-default] quit
# Configure the P device.
[P] bgp 100
[P-bgp-default] peer 1.1.1.9 as-number 100
[P-bgp-default] peer 1.1.1.9 connect-interface loopback 0
[P-bgp-default] peer 3.3.3.9 as-number 100
[P-bgp-default] peer 3.3.3.9 connect-interface loopback 0
[P-bgp-default] address-family vpnv4
[P-bgp-default-vpnv4] undo policy vpn-target
[P-bgp-default-vpnv4] peer 1.1.1.9 enable
[P-bgp-default-vpnv4] peer 1.1.1.9 reflect-client
[P-bgp-default-vpnv4] quit
[P-bgp-default] address-family l2vpn evpn
[P-bgp-default-evpn] undo policy vpn-target
[P-bgp-default-evpn] peer 3.3.3.9 enable
[P-bgp-default-evpn] peer 3.3.3.9 reflect-client
[P-bgp-default-evpn] quit
[P-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] peer 2.2.2.9 as-number 100
[PE2-bgp-default] peer 2.2.2.9 connect-interface loopback 0
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 2.2.2.9 enable
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
# Execute the display bgp peer vpnv4 command on PE 1 to verify that a BGP peer relationship in Established state has been established with the P device. Execute the display bgp peer l2vpn evpn command on PE 2 to verify that a BGP peer relationship in Established state has been established with the P device. (Details not shown.)
6. Enable EVPN to advertise VPN routes on PE 2 and the P device:
# Configure the P device.
[P] ip vpn-instance vpn1
[P-vpn-instance-vpn1] address-family ipv4
[P-vpn-ipv4-vpn1] evpn mpls routing-enable
[P-vpn-ipv4-vpn1] quit
[P-vpn-instance-vpn1] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] address-family ipv4
[PE2-vpn-ipv4-vpn1] evpn mpls routing-enable
[PE2-vpn-ipv4-vpn1] quit
[PE2-vpn-instance-vpn1] quit
# Execute the display bgp l2vpn evpn command on PE 2 to verify that the VPN routes received from CE 2 have been added to the EVPN routing table. (Details not shown.)
7. Enable MPLS encapsulation for the IP prefix advertisement routes on PE 2 and the P device:
# Configure the P device.
[P] bgp 100
[P-bgp-default] address-family l2vpn evpn
[P-bgp-default-evpn] peer 3.3.3.9 advertise encap-type mpls
[P-bgp-default-evpn] peer 3.3.3.9 next-hop-local
[P-bgp-default-evpn] quit
[P-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 2.2.2.9 advertise encap-type mpls
[PE2-bgp-default-evpn] peer 2.2.2.9 next-hop-local
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
8. On the P device, enable BGP EVPN route advertisement for the BGP VPNv4 address family, and enable BGP VPNv4 route advertisement for the BGP EVPN address family.
# Configure the P device.
[P] bgp 100
[P-bgp-default] address-family vpnv4
[P-bgp-default-vpnv4] advertise evpn route
[P-bgp-default-vpnv4] quit
[P-bgp-default] address-family l2vpn evpn
[P-bgp-default-evpn] advertise l3vpn route
[P-bgp-default-evpn] quit
[P-bgp-default] quit
# Execute the display bgp routing-table vpnv4 command on the PEs to verify that they have received VPNv4 routes from remote CEs.
Verifying the configuration
# Verify that a PE has the route to the remote CE, for example, PE 1.
[PE1] display ip routing-table vpn-instance vpn1
Destinations : 11 Routes : 11
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
172.1.1.0/24 Direct 0 0 172.1.1.2 GE1/2/0/2
172.1.1.0/32 Direct 0 0 172.1.1.2 GE1/2/0/2
172.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0
172.1.1.255/32 Direct 0 0 172.1.1.2 GE1/2/0/2
172.2.1.0/24 BGP 255 0 2.2.2.9 GE1/2/0/1
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)
Example: Enabling communication between IPv6 MPLS L3VPN and IPv6 EVPN L3VPN
Network configuration
As shown in Figure 7:
· Configure EVPN for CE 1 and CE 2 of VPN 1 to communicate.
· Configure OSPF as the IGP on the MPLS backbone for the P device and PEs to communicate.
· Configure the CEs to exchange VPN routes through EBGP.
· Configure the P device and PE 1 to exchange VPNv6 routes through MP-IBGP, and configure the P device and PE 2 to exchange BGP EVPN routes through MP-IBGP.
· Configure the P device as an RR to reflect routes between the PEs.
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
PE 1 |
Loop0 |
1.1.1.9/32 |
P |
Loop0 |
2.2.2.9/32 |
|
|
GE1/2/0/1 |
10.1.1.1/24 |
|
GE1/2/0/1 |
10.1.1.2/24 |
|
|
GE1/2/0/2 |
2001:1::2/96 |
|
GE1/2/0/2 |
10.2.1.2/24 |
|
PE 2 |
Loop0 |
3.3.3.9/32 |
CE 1 |
GE1/2/0/1 |
2001:1::1/96 |
|
|
GE1/2/0/1 |
10.2.1.1/24 |
CE 2 |
GE1/2/0/1 |
2001:2::1/96 |
|
|
GE1/2/0/2 |
2001:2::2/96 |
|
|
|
Procedure
1. Configure an IGP on the MPLS backbone for the PEs and P device to reach one another:
# Configure PE 1.
<PE1> system-view
[PE1] interface loopback 0
[PE1-LoopBack0] ip address 1.1.1.9 32
[PE1-LoopBack0] quit
[PE1] interface gigabitethernet 1/2/0/1
[PE1-GigabitEthernet1/2/0/1] ip address 10.1.1.1 24
[PE1-GigabitEthernet1/2/0/1] quit
[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 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] interface loopback 0
[P-LoopBack0] ip address 2.2.2.9 32
[P-LoopBack0] quit
[P] interface gigabitethernet 1/2/0/1
[P-GigabitEthernet1/2/0/1] ip address 10.1.1.2 24
[P-GigabitEthernet1/2/0/1] quit
[P] interface gigabitethernet 1/2/0/2
[P-GigabitEthernet1/2/0/2] ip address 10.2.1.2 24
[P-GigabitEthernet1/2/0/2] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE 2.
<PE2> system-view
[PE2] interface loopback 0
[PE2-LoopBack0] ip address 3.3.3.9 32
[PE2-LoopBack0] quit
[PE2] interface gigabitethernet 1/2/0/1
[PE2-GigabitEthernet1/2/0/1] ip address 10.2.1.1 24
[PE2-GigabitEthernet1/2/0/1] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[PE2-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
# Execute the display ospf peer command to verify that OSPF adjacencies in Full state have been established between PE 1, P, and PE 2. Execute the display ip routing-table command to verify that the PEs have learned the routes to the loopback interfaces of each other. (Details not shown.)
2. Configure basic MPLS and MPLS LDP on the MPLS backbone to establish LDP LSPs:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] quit
[PE1] interface gigabitethernet 1/2/0/1
[PE1-GigabitEthernet1/2/0/1] mpls enable
[PE1-GigabitEthernet1/2/0/1] mpls ldp enable
[PE1-GigabitEthernet1/2/0/1] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] quit
[P] interface gigabitethernet 1/2/0/1
[P-GigabitEthernet1/2/0/1] mpls enable
[P-GigabitEthernet1/2/0/1] mpls ldp enable
[P-GigabitEthernet1/2/0/1] quit
[P] interface gigabitethernet 1/2/0/2
[P-GigabitEthernet1/2/0/2] mpls enable
[P-GigabitEthernet1/2/0/2] mpls ldp enable
[P-GigabitEthernet1/2/0/2] quit
# Configure PE 2.
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls ldp
[PE2-ldp] quit
[PE2] interface gigabitethernet 1/2/0/1
[PE2-GigabitEthernet1/2/0/1] mpls enable
[PE2-GigabitEthernet1/2/0/1] mpls ldp enable
[PE2-GigabitEthernet1/2/0/1] quit
# Execute the display mpls ldp peer command to verify that LDP sessions in Operational state have been established between PE 1, P, and PE 2. Execute the display mpls ldp lsp command to verify that the LSPs have been established by LDP. (Details not shown.)
3. Configure VPN instances on the PEs to allow CE access, and configure a VPN instance on the P device to allow MPLS L3VPN access and EVPN L3VPN access:
# Configure PE 1.
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] route-distinguisher 100:1
[PE1-vpn-instance-vpn1] vpn-target 111:1
[PE1-vpn-instance-vpn1] quit
[PE1] interface gigabitethernet 1/2/0/2
[PE1-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn1
[PE1-GigabitEthernet1/2/0/2] ipv6 address 2001:1::2 96
[PE1-GigabitEthernet1/2/0/2] quit
# Configure the P device.
[P] ip vpn-instance vpn1
[P-vpn-instance-vpn1] route-distinguisher 100:1
[P-vpn-instance-vpn1] vpn-target 111:1
[P-vpn-instance-vpn1] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] route-distinguisher 200:1
[PE2-vpn-instance-vpn1] vpn-target 111:1
[PE2-vpn-instance-vpn1] quit
[PE2] interface gigabitethernet 1/2/0/2
[PE2-GigabitEthernet1/2/0/2] ip binding vpn-instance vpn1
[PE2-GigabitEthernet1/2/0/2] ipv6 address 2001:2::2 96
[PE2-GigabitEthernet1/2/0/2] quit
# Configure IP addresses for the CEs according to Figure 7. (Details not shown.)
# Execute the display ip vpn-instance command on the PEs to display the configuration of the VPN instance, for example, on PE 1.
[PE1] display ip vpn-instance
Total VPN-Instances configured : 1
Total IPv4 VPN-Instances configured : 1
Total IPv6 VPN-Instances configured : 1
Total IPv4 VPN-Instances EVPN configured : 0
Total IPv6 VPN-Instances EVPN configured : 0
VPN-Instance Name RD Address family Create time
vpn1 100:1 IPv4/IPv6 2020/07/26 08:02:38
# Use the ping command on the PEs to verify that the PEs can ping their attached CEs, for example, on PE 1.
[PE1] ping ipv6 -vpn-instance vpn1 2001:1::1
Ping6(56 data bytes) 2001:1::2 --> 2001:1::1, press CTRL_C to break
56 bytes from 2001:1::1, icmp_seq=0 hlim=64 time=2.000 ms
56 bytes from 2001:1::1, icmp_seq=1 hlim=64 time=1.000 ms
56 bytes from 2001:1::1, icmp_seq=2 hlim=64 time=0.000 ms
56 bytes from 2001:1::1, icmp_seq=3 hlim=64 time=1.000 ms
56 bytes from 2001:1::1, icmp_seq=4 hlim=64 time=1.000 ms
--- Ping6 statistics for 2001:1::1 in VPN instance vpn1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/1.000/2.000/0.632 ms
4. Establish EBGP peer relationships between PEs and CEs, and redistribute VPN routes into BGP:
# Configure CE 1.
<CE1> system-view
[CE1] bgp 65410
[CE1-bgp-default] router-id 3.3.3.9
[CE1-bgp-default] peer 2001:1::2 as-number 100
[CE1-bgp-default] address-family ipv6 unicast
[CE1-bgp-default-ipv6] peer 2001:1::2 enable
[CE1-bgp-default-ipv6] import-route direct
[CE1-bgp-default-ipv6] quit
[CE1-bgp-default] quit
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] ip vpn-instance vpn1
[PE1-bgp-default-vpn1] peer 2001:1::1 as-number 65410
[PE1-bgp-default-vpn1] address-family ipv6 unicast
[PE1-bgp-default-ipv6-vpn1] peer 2001:1::1 enable
[PE1-bgp-default-ipv6-vpn1] quit
[PE1-bgp-default-vpn1] quit
# Configure CE 2.
<CE2> system-view
[CE2] bgp 65420
[CE2-bgp-default] router-id 4.4.4.9
[CE2-bgp-default] peer 2001:2::2 as-number 100
[CE2-bgp-default] address-family ipv6 unicast
[CE2-bgp-default-ipv6] peer 2001:2::2 enable
[CE2-bgp-default-ipv6] import-route direct
[CE2-bgp-default-ipv6] quit
[CE2-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] ip vpn-instance vpn1
[PE2-bgp-default-vpn1] peer 2001:2::1 as-number 65420
[PE2-bgp-default-vpn1] address-family ipv6 unicast
[PE2-bgp-default-ipv6-vpn1] peer 2001:2::1 enable
[PE2-bgp-default-ipv6-vpn1] quit
[PE2-bgp-default-vpn1] quit
# Execute the display bgp peer ipv6 vpn-instance command on the PEs to verify that a BGP peer relationship in Established state has been established between a PE and a CE. (Details not shown.)
5. Configure route exchange between the P device and the PEs, and configure the P device as an RR:
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp-default] peer 2.2.2.9 as-number 100
[PE1-bgp-default] peer 2.2.2.9 connect-interface loopback 0
[PE1-bgp-default] address-family vpnv6
[PE1-bgp-default-vpnv6] peer 2.2.2.9 enable
[PE1-bgp-default-vpnv6] quit
[PE1-bgp-default] quit
# Configure the P device.
[P] bgp 100
[P-bgp-default] peer 1.1.1.9 as-number 100
[P-bgp-default] peer 1.1.1.9 connect-interface loopback 0
[P-bgp-default] peer 3.3.3.9 as-number 100
[P-bgp-default] peer 3.3.3.9 connect-interface loopback 0
[P-bgp-default] address-family vpnv6
[P-bgp-default-vpnv6] undo policy vpn-target
[P-bgp-default-vpnv6] peer 1.1.1.9 enable
[P-bgp-default-vpnv6] peer 1.1.1.9 reflect-client
[P-bgp-default-vpnv6] quit
[P-bgp-default] address-family l2vpn evpn
[P-bgp-default-evpn] undo policy vpn-target
[P-bgp-default-evpn] peer 3.3.3.9 enable
[P-bgp-default-evpn] peer 3.3.3.9 reflect-client
[P-bgp-default-evpn] quit
[P-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] peer 2.2.2.9 as-number 100
[PE2-bgp-default] peer 2.2.2.9 connect-interface loopback 0
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 2.2.2.9 enable
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
# Execute the display bgp peer vpnv6 command on PE 1 to verify that a BGP peer relationship in Established state has been established with the P device. Execute the display bgp peer l2vpn evpn command on PE 2 to verify that a BGP peer relationship in Established state has been established with the P device. (Details not shown.)
6. Enable EVPN to advertise VPN routes on PE 2 and the P device:
# Configure the P device.
[P] ip vpn-instance vpn1
[P-vpn-instance-vpn1] address-family ipv6
[P-vpn-ipv6-vpn1] evpn mpls routing-enable
[P-vpn-ipv6-vpn1] quit
[P-vpn-instance-vpn1] quit
# Configure PE 2.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] address-family ipv6
[PE2-vpn-ipv6-vpn1] evpn mpls routing-enable
[PE2-vpn-ipv6-vpn1] quit
[PE2-vpn-instance-vpn1] quit
# Execute the display bgp l2vpn evpn command on PE 2 to verify that the VPN routes received from CE 2 have been added to the EVPN routing table. (Details not shown.)
7. Enable MPLS encapsulation for the IP prefix advertisement routes on PE 2 and the P device:
# Configure the P device.
[P] bgp 100
[P-bgp-default] address-family l2vpn evpn
[P-bgp-default-evpn] peer 3.3.3.9 advertise encap-type mpls
[P-bgp-default-evpn] quit
[P-bgp-default] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp-default] address-family l2vpn evpn
[PE2-bgp-default-evpn] peer 2.2.2.9 advertise encap-type mpls
[PE2-bgp-default-evpn] quit
[PE2-bgp-default] quit
8. On the P device, enable BGP EVPN route advertisement for the BGP VPNv6 address family, and enable BGP VPNv6 route advertisement for the BGP EVPN address family.
# Configure the P device.
[P] bgp 100
[P-bgp-default] address-family vpnv6
[P-bgp-default-vpnv6] advertise evpn route
[P-bgp-default-vpnv6] quit
[P-bgp-default] address-family l2vpn evpn
[P-bgp-default-evpn] advertise l3vpn route
[P-bgp-default-evpn] quit
[P-bgp-default] quit
# Execute the display bgp routing-table vpnv6 command on the PEs to verify that they have received VPNv6 routes from remote CEs.
Verifying the configuration
# Verify that a PE has the route to the remote CE, for example, PE 1.
[PE1] display ipv6 routing-table vpn-instance vpn1
Destinations : 5 Routes : 5
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2001:1::/96 Protocol : Direct
NextHop : :: Preference: 0
Interface : GE1/2/0/2 Cost : 0
Destination: 2001:1::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2001:2::/96 Protocol : BGP4+
NextHop : ::FFFF:2.2.2.9 Preference: 255
Interface : GE1/2/0/1 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : InLoop0 Cost : 0
# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)
