Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

PDF

Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

Verify L3Out-to-L3Out communication by using the CLI

Updated: April 17, 2026

Want to summarize with AI?

Log in

Use this procedure to verify L3Out-to-L3Out communication by checking the BGP VPNv4 routing table and IP route information.

Switch1 learns the 209.165.201.0/24 prefix locally through an L3Out, and Switch6 learns the 209.165.202.0/24 prefix locally through an L3Out. Switch1 receives the 209.165.202.0/24 prefix through VPNv4 BGP peering and uses the DP-PTEP IP address of Switch6, 209.165.200.229, as the next hop. Similarly, Switch6 receives the 209.165.201.0/24 prefix through VPNv4 BGP peering and uses the DP-PTEP IP address of Switch1, 209.165.200.225, as the next hop.

L3Out-to-L3Out communication between Switch1 and Switch6

Procedure

  1. Run the show bgp vpnv4 unicast vrf overlay command to verify the BGP VPNv4 routing table entry for the remote prefix on Switch1.

    Example:

    
                        Switch1# show bgp vpnv4 unicast 209.165.202.0/24 vrf overlay-1
                        BGP routing table information for VRF overlay-1, address family VPNv4 Unicast
                        Route Distinguisher: 105:2490424    (VRF ARL_Scale:ctx-1)
                        BGP routing table entry for 209.165.202.0/24, version 1946 dest ptr 0x8b3963b8
                        Paths: (1 available, best #1)
                        Flags: (0x00000000000c001a 0000000000) on xmit-list, is in urib, is best urib route, is in HW, exported
                        vpn: version 145728, (0x0000000000100002) on xmit-list
                        Multipath: eBGP iBGP
                        Advertised path-id 1, VPN AF advertised path-id 1
                        Path type (0x173c502c): internal 0xc0000018 0x440 ref 0 adv path ref 2, path is valid, is best path, in rib
                        Imported from (0x164de938) 108:2490424:209.165.202.0/24
                        AS-Path: 65001 , path sourced external to AS
                        209.165.200.229 (metric 3) from 209.165.200.229 (108.1.1.1)
                        Origin IGP, MED not set, localpref 100, weight 0 tag 0, propagate 0, floating svi 0, tunnel resolved 0
                        Received label 0
                        Received path-id 1
                        Extcommunity:
                        RT:100:2490424
                        VNID:2490424
                        VRF advertise information:
                        Path-id 1 advertised to peers:
                        21.2.1.1           21.2.1.10
                        VPN AF advertise information:
                        Path-id 1 not advertised to any peer
                        BGP routing table information for VRF overlay-1, address family VPNv4 Unicast
                        Route Distinguisher: 108:2490424
                        BGP routing table entry for 209.165.202.0/24, version 144468 dest ptr 0x173596e8
                        Paths: (1 available, best #1)
                        Flags: (0x0000000000000002 0000000000) on xmit-list, is not in urib, is not in HW, is locked
                        Multipath: eBGP iBGP
                        Advertised path-id 1
                        Path type (0x164de938): internal 0x40000018 0x40 ref 1 adv path ref 1, path is valid, is best path
                        Imported to 1 destination(s)
                        AS-Path: 65001 , path sourced external to AS
                        209.165.200.229 (metric 3) from 209.165.200.229 (108.1.1.1)
                        Origin IGP, MED not set, localpref 100, weight 0 tag 0, propagate 0, floating svi 0, tunnel resolved 0
                        Received label 0
                        Received path-id 1
                        Extcommunity:
                        RT:100:2490424
                        VNID:2490424
                        Path-id 1 not advertised to any peer

  2. Run the show ip route command to verify the IP route and next-hop information for the remote prefix on Switch1.

    Example:

    
                        Switch1# show ip route 209.165.202.13 vrf ARL_Scale:ctx-1
                        IP Route Table for VRF "ARL_Scale:ctx-1"
                        '*' denotes best ucast next-hop
                        '**' denotes best mcast next-hop
                        '[x/y]' denotes [preference/metric]
                        '%<string>' in via output denotes VRF <string>
                        209.165.202.0/24, ubest/mbest: 1/0
                        *via 209.165.200.229%overlay-1, [200/0], 00:23:41, bgp-100, internal, tag 65001
                        recursive next hop: 209.165.200.229/32%overlay-1