Implement MP-BGP EVPN VxLAN Control Plane Lab v2

First Published: 2020-11-18

Last Modified: 2022-03-10

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2020 Cisco Systems, Inc. All rights reserved.
 CONTENTS

CHAPTER 1 About 1
About This Demonstration 1
Requirements 1
About This Solution 2
Topology 2
Session Users 3
Get Started 3

CHAPTER 2 Scenarios 7

Establish iBGP Peer between Spine and Leaf Switches 7

Configuring Multicast to Support BUM in VXLAN Fabric 10
Configuring VXLAN Fabric 13
Configuring BGP EVPN Control Plane 16
Verify VXLAN EVPN Control Plane Update 17
Configure Border Leaf to External Entity 20

CHAPTER 3 Appendix 25

Troubleshooting MTPuTTY 25
Troubleshooting – Fix My Demo 26

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

iii
Contents

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

iv
 CHAPTER 1
About
• About This Demonstration, on page 1
• Requirements, on page 1
• About This Solution, on page 2
• Topology, on page 2
• Session Users, on page 3
• Get Started, on page 3

About This Demonstration

This lab introduces students to the industry standard MP-BGP EVPN and Cisco implementation of VXLAN
on NXOSv. Student will use virtual Nexus switches to implement MP-BGP EVPN VXLAN control plane.
Upon completion of this lab, users will able to:
• Manually configure BGP EVPN in a standard Spine-Leaf topology.
• Use command line to verify VXLAN/BGP EVPN.

Some of the terminology that will appear in this Demo Guide:

• VNI / VNID – VXLAN Network Identifier, or VXLAN ID. This replaces VLAN ID.
• VTEP – VXLAN Tunnel End Point, the end point where the box performs VXLAN encap / decap. This
could be physical HW (Nexus9k) or virtual (Nexus 1000v, Nexus 9000v).
• VXLAN Segment - The resulting layer 2 overlay network.
• VXLAN Gateway – Device that forwards traffic between VXLANS. The VXLAN Gateway can be both
L2 and L3 forwarding.
• NVE – Network Virtualization Edge, is the tunnel interface, and represents VTEP.

Requirements
The table below outlines the requirements for this preconfigured demonstration.

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

1
 About
About This Solution

Required Optional
Laptop Cisco AnyConnect

About This Solution

Virtual Extensible Local Area Network (VXLAN) is an L2 overlay scheme on top of an L3 network, also
described as an L2 in L3 tunnel. It runs over the existing networks and provides the means to stretch the L2
network. As a standardized overlay technology, multiple vendors have adopted VXLAN as a datacenter
solution to provide scalability and allow layer 2 across IP network. MP-BGP EVPN as the VXLAN control
plane protocol provides a robust scalable solution to overcome the limitation in VXLAN flood and learn mode.
Only VMs within the same VXLAN segment can communicate with each other. Each VXLAN segment is
identified by a 24 bit segment ID called VXLAN Network Identifier (VNI). This helps to overcome the 4094
VLAN scale limitation and enables extension to 224 segments.
VXLAN uses BGP as its control plane for Overlay. It makes its forwarding decisions at VTEPs (Virtual tunnel
end points) for L2 and L3. Forwarding happens based on MAC or IP learned via the control plane (MP-BGP
EVPN). VXLAN uses IGP, PIM and BGP as its underlay in the fabric.

Topology
This content includes preconfigured users and components to illustrate the scripted scenarios and features of
the solution. Most components are fully configurable with predefined administrative user accounts. You can
see the IP address and user account credentials to use to access a component by clicking the component icon
in the Topology menu of your active session and in the scenario steps that require their use.
dCloud Topology

Demonstration Topology

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

2
 About
Session Users

Session Users
Device IP Address Login Credentials
Spine_1 198.18.134.140 admin/C1sco12345
Spine_2 198.18.134.141 admin/C1sco12345
Leaf_1 198.18.134.142 admin/C1sco12345
Leaf_2 198.18.134.143 admin/C1sco12345
Leaf_3 198.18.134.144 admin/C1sco12345
Leaf_4 198.18.134.145 admin/C1sco12345
Server_1 198.18.134.50 root/C1sco12345
Server_2 198.18.134.100 root/C1sco12345
Server_3 198.18.134.150 root/C1sco12345
WAN 198.18.133.45 admin/C1sco12345
Remote Workstation 198.18.133.36 demouser/C1sco12345

Get Started
Follow the steps to schedule a session of the content and configure your presentation environment.

Step 1 Initiate your dCloud session. [Show Me How]

Note It may take up to 10 minutes for your session to become active.

Step 2 Connect to the demonstration workstation using one of the following connection methods:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

3
 About
Get Started

• Cisco dCloud Remote Desktop client [Show Me How]

• Cisco AnyConnect VPN [Show Me How] and the local RDP client on your laptop [Show Me How] (Workstation
1: 198.18.133.36, Username: DCLOUD\demouser, Password: C1sco12345 – click Yes on the pop-up).

Step 3 Double-click on the desktop to open the application.

Step 4 Open the console connection to all devices, by double-clicking each device in the PuTTY sessions folder.
Important If a connection loss message occurs for any tab, click Reconnect and return to the proper tab before continuing.

Example:

Step 5 If any session displays a security pop-up, click No on the pop-up.

Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

4
 About
Get Started

Step 6 If any session does not display a log in prompt, perform the Troubleshooting procedure.
Note It is best practice to have separate loopback interface for VXLAN VTEP. The point-to-point links and loopback
interfaces are shown in the following table.

Leaf Switch Loopback0 Loopback1 Spine-1 Spine-2 WAN

Leaf-1 192.168.0.8 192.168.0.18 10.0.0.22/30 10.0.128.6/30

Leaf-2 192.168.0.9 192.168.0.19 10.0.0.26/30 10.0.128.10/30

Leaf-3 192.168.0.10 192.168.0.110 10.0.0.30/30 10.0.128.14/30

Leaf-4 192.168.0.11 192.168.0.111 10.0.128.2/30 10.0.128.18/30 10.0.0.18/30

The basic infrastructure connectivity is pre-configured.

Step 7 Check the ospf adjacency by entering show ip ospf neighbor on Spine-1 and Spine-2.
The output shows four OSPF neighbors across four point-to-point links.
Note It is best practice to use a point-to-point OSPF network to avoid DR/BDR election

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

5
 About
Get Started

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

6
 CHAPTER 2
Scenarios
• Establish iBGP Peer between Spine and Leaf Switches, on page 7
• Configuring Multicast to Support BUM in VXLAN Fabric, on page 10
• Configuring VXLAN Fabric, on page 13
• Configuring BGP EVPN Control Plane, on page 16
• Verify VXLAN EVPN Control Plane Update, on page 17
• Configure Border Leaf to External Entity, on page 20

Establish iBGP Peer between Spine and Leaf Switches

The purpose of this scenario is to establish iBGP between the spine and leaf switches. The spine switches will
act as route-reflectors to the leaf switches in the network. This will help move the routes between leaf switches
through the spines and eliminate the need for a full mesh topology design. All the leaf switches will be dual
homed to both spine switches
At the end of this scenario, iBGP will be configured:
• From Spine 1 to all the leaf switches (leaf-1, leaf-2, leaf-3, leaf-4)
• From Spine 2 to all the leaf switches (leaf-1, leaf-2, leaf-3, leaf-4)

Step 1 Enter the following series of commands on Spine-1 to configure the iBGP neighbor template on with the spine switch as
a route reflector, and apply the template to all the leaf switches as iBGP neighbors.
Example:
config t
feature bgp

Wait a moment for the prompt to return after the feature bgp command.
router bgp 65000
router-id 192.168.0.6
address-family ipv4 unicast
template peer LEAF-PEER
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
route-reflector-client
neighbor 192.168.0.8

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

7
 Scenarios
Establish iBGP Peer between Spine and Leaf Switches

inherit peer LEAF-PEER

neighbor 192.168.0.9
inherit peer LEAF-PEER
neighbor 192.168.0.10
inherit peer LEAF-PEER
neighbor 192.168.0.11
inherit peer LEAF-PEER

Step 2 Enter copy run start to save the configuration on Spine-1.

Example:

Step 3 Enter the following commands on Spine-2 to configure iBGP between Spine-2 and all the leaf switches (leaf-1, leaf-2,
leaf-3, and leaf-4).
Example:
config t
feature bgp

Wait a moment for the prompt to return after the feature bgp command.
router bgp 65000
router-id 192.168.0.7
address-family ipv4 unicast
template peer LEAF-PEER
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
route-reflector-client
neighbor 192.168.0.8
inherit peer LEAF-PEER
neighbor 192.168.0.9
inherit peer LEAF-PEER
neighbor 192.168.0.10
inherit peer LEAF-PEER
neighbor 192.168.0.11
inherit peer LEAF-PEER

Step 4 Enter copy run start on Spine-2 to save the configuration.

Example:

Step 5 Enter the following commands to configure BGP on Leaf-1, Leaf-2, Leaf-3 and Leaf-4, which will establish the iBGP
neighbor relationship with Spine-1 and Spine-2 on each leaf.
Note that the copy run start command at the end of each group saves the configuration.
Example:
Leaf 1:
config t
feature bgp

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

8
Scenarios
Establish iBGP Peer between Spine and Leaf Switches

Wait a moment for the prompt to return after the feature bgp command.
router bgp 65000
router-id 192.168.0.8
address-family ipv4 unicast
neighbor 192.168.0.6
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
neighbor 192.168.0.7
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
copy run start

Leaf-2:
config t
feature bgp

Wait a moment for the prompt to return after the feature bgp command.
router bgp 65000
router-id 192.168.0.9
address-family ipv4 unicast
neighbor 192.168.0.6
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
neighbor 192.168.0.7
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
copy run start

Leaf-3:
config t
feature bgp

Wait a moment for the prompt to return after the feature bgp command.
router bgp 65000
router-id 192.168.0.10
address-family ipv4 unicast
neighbor 192.168.0.6
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
neighbor 192.168.0.7
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
copy run start

Leaf-4:
config t
feature bgp

Wait a moment for the prompt to return after the feature bgp command.

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

9
 Scenarios
Configuring Multicast to Support BUM in VXLAN Fabric

router bgp 65000

router-id 192.168.0.11
address-family ipv4 unicast
neighbor 192.168.0.6
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
neighbor 192.168.0.7
remote-as 65000
update-source loopback0
address-family ipv4 unicast
send-community both
copy run start

Step 6 Enter show ip bgp sum on Spine-1 to verify the iBGP neighbors on the spine switches.
Optionally, also run the command on Spine-2. Messages sent and received may vary slightly.
Example:

Configuring Multicast to Support BUM in VXLAN Fabric

The purpose of this scenario is to configure PIM-SM with Anycast RP on the spine switches. The underlay
Multicast infrastructure will be used for Broadcast, Unknown unicast and Multicast traffic (BUM) in the
VXLAN fabric.
RP configuration is not supported on leaf switches. It is only supported on spine switches. It is recommended
to configure RP only on the spine node and use the anycast RP (Rendezvous Point) model for load balancing
and redundancy.
Configuration of PIM-SM with Anycast RP will require the following activities:
• Enable PIM
• Configure Spine and Leaf interfaces for PIM
• Enable router OSPF on loopback interface
• Enable Anycast RP between Spine switches

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

10
 Scenarios
Configuring Multicast to Support BUM in VXLAN Fabric

Step 1 Enter the following commands on Spine-1 and Spine-2 to configure PIM and OSPF on a new loopback interface.
Because this is Anycast, the configuration commands are the same on both servers because they are rendezvous points
(RP). Note that the copy run start command saves the configuration.
Example:
config t
feature pim

Wait a moment for the prompt to return after the feature pim command.
interface loopback1
ip address 192.168.0.100/32
ip pim sparse-mode
ip router ospf 1 area 0.0.0.0
copy run start

Step 2 Enter the following commands on Spine-1 to configure PIM Anycast RP for RP redundancy.
Example:
ip pim rp-address 192.168.0.100
ip pim anycast-rp 192.168.0.100 192.168.0.6
ip pim anycast-rp 192.168.0.100 192.168.0.7
interface E1/1
ip pim sparse-mode
interface E1/2
ip pim sparse-mode
interface E1/3
ip pim sparse-mode
interface E1/4
ip pim sparse-mode
interface loopback0
ip pim sparse-mode
copy run start

Step 3 Repeat on Spine-2 to configure PIM Anycast RP for RP redundancy.

Example:
ip pim rp-address 192.168.0.100
ip pim anycast-rp 192.168.0.100 192.168.0.6
ip pim anycast-rp 192.168.0.100 192.168.0.7
interface E1/1
ip pim sparse-mode
interface E1/2
ip pim sparse-mode
interface E1/3
ip pim sparse-mode
interface E1/4
ip pim sparse-mode
interface loopback0
ip pim sparse-mode
copy run start

Step 4 Configure PIM on the leaf switches by entering the following commands
Example:
Leaf-1:
config t
feature pim

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

11
 Scenarios
Configuring Multicast to Support BUM in VXLAN Fabric

Wait a moment for the prompt to return after the feature pim command.
ip pim rp-address 192.168.0.100
interface E1/1
ip pim sparse-mode
interface E1/2
ip pim sparse-mode
interface loopback0
ip pim sparse-mode
interface loopback1
ip pim sparse-mode
copy run start

Leaf-2:
config t
feature pim

Wait a moment for the prompt to return after the feature pim command.
ip pim rp-address 192.168.0.100
interface E1/1
ip pim sparse-mode
interface E1/2
ip pim sparse-mode
interface loopback0
ip pim sparse-mode
interface loopback1
ip pim sparse-mode
copy run start

Leaf-3:
config t
feature pim

Wait a moment for the prompt to return after the feature pim command.
ip pim rp-address 192.168.0.100
interface E1/1
ip pim sparse-mode
interface E1/2
ip pim sparse-mode
interface loopback0
ip pim sparse-mode
interface loopback1
ip pim sparse-mode
copy run start

Leaf-4:
config t
feature pim

Wait a moment for the prompt to return after the feature pim command.
ip pim rp-address 192.168.0.100
interface E1/1
ip pim sparse-mode
interface E1/2
ip pim sparse-mode
interface loopback0
ip pim sparse-mode
interface loopback1
ip pim sparse-mode
copy run start

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

12
 Scenarios
Configuring VXLAN Fabric

Step 5 Enter show ip pim neighbor on both Spine-1 and Spine-2 to verify PIM neighbors.
Example:

Configuring VXLAN Fabric

The purpose of this scenario is to enable VXLAN features and configure a VLAN/VNI/Multicast Group based
on the table below. The VLAN ID to VNI segment ID should be one to one mapping. One unique multicast
group is mapped to one VNI for BUM traffic inside this L2 VNI. One L3 VNI is created for VXLAN routing.
The completion of this scenario will enable VXLAN in the entire topology.

VLAN ID Name SVI VNI Multicast Group

140 L2-VNI-140-Tenant1 172.21.140.1/24 50140 239.0.0.140

141 L2-VNI-141-Tenant1 172.21.141.1/24 50141 239.0.0.141

999 L3-VNI-999-Tenant1 50999

Note For VXLAN routing, one L3 VNI is required for each Tenant/VRF.

Step 1 Enter the following commands on all leaf and spine switches to enable VXLAN.
Example:
config t
feature nv overlay
feature vn-segment-vlan-based
nv overlay evpn
copy run start

Step 2 Enter the following commands on Leaf-1, Leaf-2, Leaf-3, and Leaf-4 to configure VLAN 140, VLAN 141 and VLAN
999.
Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

13
 Scenarios
Configuring VXLAN Fabric

spanning-tree vlan 1,140,141,999 priority 4096

vlan 140
name L2-VNI-140-Tenant1
vn-segment 50140
vlan 141
name L2-VNI-141-Tenant1
vn-segment 50141
vlan 999
vn-segment 50999
copy run start

Note There will be a warning message after adding VLAN 999: Warning: Enable double-wide arp-ether
tcam carving if igmp snooping is enabled. Ignore if tcam carving is already
configured. This message can be ignored.

Step 3 Enter the following commands on Leaf-1, Leaf-2, Leaf-3, and Leaf-4 to configure VRF for Tenant-1 and SVI for
VLAN/VNI.
Example:
vrf context Tenant-1
vni 50999
rd auto
address-family ipv4 unicast
route-target both auto
route-target both auto evpn
fabric forwarding anycast-gateway-mac 0000.2222.3333
interface Vlan140
no shutdown
vrf member Tenant-1
no ip redirects
ip address 172.21.140.1/24
fabric forwarding mode anycast-gateway
interface Vlan141
no shutdown
vrf member Tenant-1
no ip redirects
ip address 172.21.141.1/24
fabric forwarding mode anycast-gateway
interface vlan999
no shutdown
vrf member Tenant-1
ip forward

Note There will be a warning message after each vrf member Tenant-1 command: Warning: Deleted all
L3 config on interface Vlanxxx. This message can be ignored.

Step 4 Enter the following commands on Leaf-1, Leaf-2, Leaf-3, and Leaf-4 to configure the VXLAN tunnel interface (NVE).
Example:
interface nve1
no shutdown
source-interface loopback1
host-reachability protocol bgp
member vni 50140
mcast-group 239.0.0.140
member vni 50141
mcast-group 239.0.0.141
member vni 50999 associate-vrf
interface nve1
no shutdown
source-interface loopback1
host-reachability protocol bgp

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

14
 Scenarios
Configuring VXLAN Fabric

member vni 50140

mcast-group 239.0.0.140
member vni 50141
mcast-group 239.0.0.141
member vni 50999 associate-vrf

Step 5 Enter show nve vni on Leaf-1, Leaf-2, Leaf-3, and Leaf-4 to verify the VXLAN configuration.

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

15
 Scenarios
Configuring BGP EVPN Control Plane

Configuring BGP EVPN Control Plane

The purpose of this scenario is to configure the new BGP EVPN address family on all leaf and spine switches.
This is a new address family, which is added to BGP to distribute internal host / external routes and reachability
information.
The configuration tasks for this section are:
• Create peer template on both Spine switches
• Create L2vpn evpn address families on all leaf switches
• Configure RD/RT values under evpn VRF

Step 1 Enter the following commands on Spine-1 and Spine-2 to add the l2vpn evpn address family under the existing BGP AS.
Example:
config t
router bgp 65000
address-family l2vpn evpn
retain route-target all
template peer LEAF-PEER
address-family l2vpn evpn
send-community both
route-reflector-client

Step 2 Enter the following commands on Leaf-1, Leaf-2, Leaf-3, and Leaf-4 to add the l2vpn evpn address family under the
existing BGP AS.
Example:
config t
router bgp 65000
address-family l2vpn evpn
retain route-target all
neighbor 192.168.0.6
remote-as 65000
address-family l2vpn evpn
send-community both
neighbor 192.168.0.7
remote-as 65000
address-family l2vpn evpn
send-community both

Step 3 Enter the following commands on Leaf-1, Leaf-2, Leaf-3, and Leaf-4 to configure RD and RT for VXLAN bridging.
Example:
evpn
vni 50140 l2
rd auto
route-target import auto
route-target export auto
vni 50141 l2
rd auto
route-target import auto
route-target export auto

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

16
 Scenarios
Verify VXLAN EVPN Control Plane Update

Note For VXLAN fabric with all Cisco Nexus switches, it is recommended to generate RD/RT automatically. For
VXLAN fabric with multi-vendor VTEP devices, it is recommended to manually configure the RT/RD values.

Verify VXLAN EVPN Control Plane Update

The purpose of this scenario is to initiate traffic across different VXLANs.
• Verify the dynamic tunnel established between VTEPs
• Verify the node mac/IP host route being updated via BGP EVPN control plane.

As per the topology, server-1 is connected to port e1/3 on Leaf1 so the interface must be configured as access
port and assigned a VLAN.

Step 1 Enter the following commands on Leaf-1 to configure Leaf-1 interface E1/3 to be part of VLAN 140.
Example:
int e1/3
description to Server-1
switchport mode access
switchport access vlan 140

Step 2 Click the server-1 tab tab in MTPuTTY.

If the [root@server-1 ~]# prompt is not showing, log in to Server-1 (root/C1sco12345).
Step 3 Enter sudo ifconfig eth1 172.21.140.10 netmask 255.255.255.0 up to configure interface eth1
as part of VLAN140.
Step 4 Type (do not copy/paste) sudo route add –net 172.21.0.0/16 gw 172.21.140.1 dev eth1 to
add the static route for subnet 172.21.0.0/16 to interface Eth1 on Server-1.
Step 5 Enter ping 172.21.140.1 to ping the default gateway from Server-1.
Example:

Note As per the topology, server-2 is connected to port e1/3 on Leaf1, so it has to be configured as access port and
assigned to a VLAN.

Step 6 Enter the following commands on Leaf-3 to configure Leaf-3 interface E1/3 to be part of VLAN 141.
Example:
int e1/3
description to Server-2
switchport mode access
switchport access vlan 141

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

17
 Scenarios
Verify VXLAN EVPN Control Plane Update

Step 7 Click the server-2 tab in MTPuTTY.

If the [root@server-2 ~]# prompt is not showing, log in to Server-2 (root/C1sco12345).
Step 8 Enter sudo ifconfig eth1 172.21.141.10 netmask 255.255.255.0 up to configure interface eth1
to be part of VLAN141.
Step 9 Type (do not copy paste) sudo route add –net 172.21.0.0/16 gw 172.21.141.1 dev eth1 to
add the static route for subnet 172.21.0.0/16 to interface Eth1 on Server-2.
Step 10 Enter ping 172.21.141.1 to ping default gateway 172.21.141.1 from Linux VM Server-2
Example:

Step 11 On Server-1, enter the command ping 172.21.141.10 to perform a ping test between Server-1 and Server-2,
which will trigger an EVPN control plane update.
Example:

Step 12 Enter the following commands on Leaf-4 to verify the VXLAN EVPN control plane update.
a) If the Leaf-4 (config) # prompt is not displayed, enter config t.
b) Enter show nve peers to verify the dynamic tunnel between VTEPs.
If there was a configuration error during the process, there will be no output.
Example:

c) Enter sh ip route vrf Tenant-1 to verify the routing table with the /32 host route learned from BGP.
Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

18
Scenarios
Verify VXLAN EVPN Control Plane Update

d) Enter show bgp l2vpn evpn to verify the EVPN control plane update.
Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

19
 Scenarios
Configure Border Leaf to External Entity

e) Enter show l2route evpn mac-ip all to verify the forwarding table.
Example:

Configure Border Leaf to External Entity

The purpose of this scenario is to establish the connectivity from the VXLAN fabric to external network. Part
of the scenario is to advertise the routes in VXLAN fabric to WAN router via the Border leaf switch, Leaf-4,

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

20
 Scenarios
Configure Border Leaf to External Entity

and to advertise a subnet behind WAN router into the VXLAN fabric. After complete this task, pings from
server-3 to server-1 and server-2 inside the VXLAN fabric will be successful.
Leaf-4 in this lab is a border leaf that connects to the external network outside the fabric. There are a few
options to redistribute the fabric routes to external entity. This scenario explores the option to use IGP between
the border leaf and the WAN, and redistribute the fabric routes in each Tennant.

Step 1 If Leaf-4 is not in config mode, showing the Leaf-4 (config) # prompt, enter config t.
Step 2 Enter the following commands on Leaf-4 to configure IGP under VRF Tenant-1.
Example:
interface Ethernet1/3
mtu 9216
vrf member Tenant-1
ip address 10.0.0.18/30
ip ospf network point-to-point
ip router ospf 1 area 0.0.0.0
no shutdown
router ospf 1
router-id 192.168.0.11
vrf Tenant-1
do copy run start

Note After the vrf Tenant-1 command, an error will be generated: Warning: Deleted all L3 config
on interface Ethernet1/3. This error can be ignored.

Step 3 Configure IGP on WAN (198.18.133.45) using credentials admin/C1sco12345.

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

21
 Scenarios
Configure Border Leaf to External Entity

Example:
config t
int gig2
mtu 9216
description to Leaf-4
ip address 10.0.0.17 255.255.255.252
ip ospf network point-to-point
no shut
exit
router ospf 1
router-id 192.168.0.5
network 10.0.0.16 0.0.0.3 area 0

Step 4 Press Ctrl-Z to exit configuration mode on WAN.

Step 5 Enter show ip ospf neighbor to verify the OSPF neighbor between WAN and Leaf-4.
Example:

Step 6 Enter the following commands on Leaf-4 to configure the border leaf to redistribute Fabric routes into OSPF.
Example:
router bgp 65000
vrf Tenant-1
address-family ipv4 unicast
advertise l2vpn evpn
redistribute ospf 1 route-map permit-ospf-bgp
router ospf 1
vrf Tenant-1
redistribute bgp 65000 route-map permit-bgp-ospf
redistribute direct route-map permit-bgp-ospf
route-map permit-bgp-ospf permit 10
route-map permit-ospf-bgp permit 10

Step 7 Login to Server-3 with username root and password C1sco12345.

Step 8 Enter sudo ifconfig eth1 172.21.1.10 netmask 255.255.255.0 up to configure interface eth1.
Step 9 Type, do not copy/paste, sudo route add –net 172.21.0.0/16 gw 172.21.1.1 dev eth1 to configure
the Linux VM Server-3 static route for 172.21.0.0/16 to interface Eth1.
Example:

Step 10 Enter ping 172.21.141.10 and then, enter ping 172.21.140.10 to verify connectivity from Linux VM
Server-3 to Linux VM Server-1 and Server-2.
Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

22
 Scenarios
Configure Border Leaf to External Entity

Step 11 In the WAN window, enter show ip route ospf to verify the fabric host routes on the WAN router.
Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

23
 Scenarios
Configure Border Leaf to External Entity

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

24
 CHAPTER 3
Appendix
• Troubleshooting MTPuTTY, on page 25
• Troubleshooting – Fix My Demo, on page 26

Troubleshooting MTPuTTY
The purpose of the troubleshooting procedure is to restart any server that does not return a prompt in the
MTPuTTY console session.

Step 1 Open Google Chrome and click the Nexus Fabric Console Access tab.
Step 2 Log in using credentials root/C1sco12345) and then, click Ignore on the resulting certification pop-up.
Step 3 Click Virtual Machines to review the servers list.
Step 4 Right-click the affected server and select Power > Power ON in the resulting menu.
Example:

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

25
 Appendix
Troubleshooting – Fix My Demo

Step 5 Wait until the MTPuTTY session shows a login prompt before proceeding with the demonstration.

Troubleshooting – Fix My Demo

The Fix My Demo script enables common issues to be resolved in the demonstration environment. The script
fully resets the environment back to the start-up configuration, so work done in scenario prior to running the
Fix My Demo script will be lost.

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

26
 Appendix
Troubleshooting – Fix My Demo

Step 1 From the demonstration workstation, click .

Step 2 Enter 5 at the prompt.
Example:

Do not close the command window until the task fully completes.

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

27
 Appendix
Troubleshooting – Fix My Demo

Implement MP-BGP EVPN VxLAN Control Plane Lab v2

28