Overview
Provides examples of the DAG-bridged overlay network configuration.
This section provides examples to verify the DAG-bridged overlay network configuration and states of VTEPs.
The command output may be truncated to focus on critical information for a Day-2 operation and troubleshooting.
IP VRF networks: Verifies the locally configured IP VRF and the associated physical or logical interface bindings to a virtual network on VTEPs including leaf and border devices. The interface binding includes the network edge VLANs connecting to endpoints, and 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.101:101 ipv4 Vl11
Vl211
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 sessions between Cisco Catalyst 9000 series switches in EVPN multihoming mode, and iBGP peering to a pair of spine systems are operational.
The following command output shows iBGP peering with a pair of spines 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 in EVPN multihoming mode is operational.
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 the VTEP in leaf or border roles implemented in EVPN multihoming mode is configured with a route-map and an outbound policy is applied to each spine, 10.200.255.3.
The spine policy configuration on border switches is optional and not required if the switches are 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 the 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 the applied route-map policy.
The following command output from leaf and border switches confirms the advertising of RT-2-MAC-IP EVPN prefixes, and that 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:111
*> [2][10.200.255.101:111][0][48][00CCFC4ED1C3][32][10.111.1.1]/24
0.0.0.0 32768 ?
Route Distinguisher: 10.200.255.101:111
*> [2][10.200.255.101:111][0][48][00CCFC4ED1C4][32][10.111.1.2]/24
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.255.1:101 (default for vrf green)
*> [5][10.100.255.1:101][0][0][0.0.0.0]/17
21.1.1.1 0 0 65001 ?
*> [5][10.100.255.1:101][0][16][111.1.0.0]/17
21.1.1.1 0 0 65001 ?
MAC-VRF manual route-target: Verifies that the stretched IP-subnet VLAN is limited to import and export of the MAC or IP route matching the local cluster EVPN multihoming peer switch. With auto route-target disabled, the import and export route-target only lists the manual configuration settings.
The following command output confirms that the bidirectional MAC route policy with route-target 1.1.1.1:12 and the default auto-generated ASN instance ID 65101:211 is not listed along with the manual configuration.
ES-1# show l2vpn evpn evi 211 detail
EVPN instance: 211 (VLAN Based)
RD: 10.200.255.101:211 (auto)
Import-RTs: 1.1.1.1:211 1.1.1.2:211
Export-RTs: 1.1.1.1:211
Per-EVI Label: none
State: Established
Replication Type: Static
<snip>
VRF IP routing table: Verifies that the leaf implemented in EVPN multihoming mode is advertising the EVPN prefixes to the spine switch 10.200.255.3 based on the applied route-map policy.
The following command output from the border switch confirms that the pair of EVPN multihoming leaf systems configured in DAG routed overlay, each with two hosts are advertising RT2-MAC-IP. Border switches have a dual-path ECMP to each host to support load-sharing and redundancy for overlay network prefixes. And leaf switches receive the RT-5 network prefix from the IP routing table of IP VRFs in the border systems that confirm the advertising of RT-5 EVPN prefixes.
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.111.1.1/32 [200/0] via 10.200.255.102, 00:01:33, Vlan1101
[200/0] via 10.200.255.101, 00:01:33, Vlan1101
B 10.111.1.2/32 [200/0] via 10.200.255.102, 00:01:33, Vlan1101
[200/0] via 10.200.255.101, 00:01:33, Vlan1101
B 10.111.1.3/32 [200/0] via 10.200.255.104, 00:01:33, Vlan1101
[200/0] via 10.200.255.103, 00:01:33, Vlan1101
B 10.111.1.4/32 [200/0] via 10.200.255.104, 00:01:33, Vlan1101
[200/0] via 10.200.255.103, 00:01:33, Vlan1101