Multihoming in a BGP EVPN VXLAN Fabric Configuration Guide, Cisco IOS XE 26.x.x and Later

PDF

Verify the routed overlay network configuration

Updated: April 10, 2026

Want to summarize with AI?

Log in

Overview

Provides examples of commands and their typical outputs to verify the routed overlay network configuration and the states of the VTEPs.

This section lists the commands and the output of these commands to verify the routed overlay network configuration and the states of the VTEPs.

The command output may be truncated to focus on critical information useful for Day Two operations and troubleshooting.

IP VRF networks: Verifies the locally configured IP VRFs and the associated physical or logical interface bindings to a virtual network on VTEPs, including leaf and border devices.

The interface bindings displayed in this command output include the network edge VLANs connecting to endpoints, network devices along with a single core VLAN (VLAN 101) of an IP VRF. 

 
ES-1# show vrf green 

  Name          Default RD            Protocols	Interfaces 
  green         10.200.255.103:101     ipv4		Vl11 
                                                        Vl101 

BORDER-1# show vrf green 

  Name           Default RD            Protocols	Interfaces 
  green          10.200.255.1:101	ipv4		Vl101 
                                                         Vl1101

BGP L2VPN EVPN neighbors: Verifies that the two-tier hierarchical iBGP session between a pair of Cisco Catalyst 9000 series switches in EVPN multihoming mode and the iBGP peering to a pair of spine systems are operational.

The following output displays iBGP peering between a pair of spine switches, 10.100.255.3 and 10.100.255.4 and direct iBGP peering between ES-1 local 10.100.255.101 and ES-2 10.100.255.102 switches are operational and in EVPN multihoming mode. 


ES-1# show bgp l2vpn evpn all summary 

BGP router identifier 10.100.255.101, local AS number 65101 
<snip> 
 
Neighbor           V        AS      MsgRcvd MsgSent   TblVer  InQ     OutQ    Up/Down   State/PfxRcd 
10.100.255.3       4        65101      18     20      104      0        0     00:04:35        2 
10.100.255.4       4        65101      23     25      106      0        0     00:05:19        2 
10.100.255.102     4        65101      51     65      104      0        0     00:04:26        28

Spine policy: Verifies that a VTEP in leaf or border roles implemented in EVPN multihoming mode is configured with a route map and has an outbound policy applied to each spine, such as 10.200.255.3. The spine policy configuration on the border switch is optional and not required if the switch is not implemented in EVPN multihoming mode to connect to external network devices, such as firewalls. 


ES-1# show bgp l2vpn evpn neighbor 10.200.255.3 policy 
  
 Neighbor: 10.200.255.3, Address-Family: L2VPN E-VPN 
 Locally configured policies: 
  send-community extended 
 Inherited polices: 
  route-map EVPN-SPINE-ROUTE-POLICY-OUT out

L2VPN advertised routes: Verifies that a VTEP in leaf or border roles implemented in EVPN multihoming mode is advertising EVPN prefixes to the spine (10.200.255.3) based on the applied route-map policy.

The following output shows that the RT-5 EVPN prefix is advertised, and no additional EVPN route-types are advertised to the spine switches. 


ES-1# show bgp l2vpn evpn neighbor 10.200.255.3 advertised-route 
  
BGP table version is 7179, local router ID is 10.200.255.101 
<snip> 
     Network          	Next Hop            Metric 	LocPrf 	Weight 	Path 
Route Distinguisher: 10.200.255.101:101 (default for vrf green) 
 *>   [5][10.200.255.101:101][0][24][10.1.11.0]/17 
                      	0.0.0.0                  0         		32768 	? 
 *>   [5][10.200.255.101:101][0][24][10.1.12.0]/17 
                      	0.0.0.0                  0         		32768 	? 
 *>   [5][10.200.255.101:101][0][24][10.1.13.0]/17 
                      	0.0.0.0                  0         		32768 	? 
 

Border-1# show bgp l2vpn evpn neighbors 10.200.255.3 advertised-routes  

BGP table version is 2895, local router ID is 10.200.255.1 
<snip> 
     Network          Next Hop            Metric	LocPrf	Weight	Path 
Route Distinguisher: 10.100.253.23:1101 (default for vrf green) 
 *>   [5][10.100.253.23:1101][0][0][0.0.0.0]/17 
                      	21.1.1.1                 0             	0 	65001	? 
 *>   [5][10.100.253.23:1101][0][16][111.1.0.0]/17 
                      	21.1.1.1                 0             	0 	65001	?

VRF IP routing table: Verifies that a VTEP in leaf or border roles implemented in EVPN multihoming mode is advertising the EVPN prefixes to the spine, 10.200.255.3 based on applied route-map policy.

The following outputs from leaf and border roles confirm that only RT-5 EVPN prefix is advertised, and no additional EVPN route types are advertised to the spine switches. 


ES-1# show ip route vrf green bgp 
 
Routing Table: green 
<snip> 
 
Gateway of last resort is 10.200.255.2 to network 0.0.0.0 
B*    0.0.0.0/0    [200/0] via 10.200.255.1, 00:00:32, Vlan101 
                   [200/0] via 10.200.255.2, 00:00:32, Vlan101 
 

Border-1# show ip route vrf green bgp  
Routing Table: green 
<snip> 
Gateway of last resort is 21.1.1.1 to network 0.0.0.0 
 
B*    0.0.0.0/0 [20/0] via 21.1.1.1, 6w0d 
      10.0.0.0/24 is subnetted, 95 subnets 
B     10.11.1.0    [200/0] via 10.200.255.104, 00:04:25, Vlan1101 
                   [200/0] via 10.200.255.103, 00:04:25, Vlan1101