Troubleshooting the Cisco Dynamic Fabric Automation (DFA) Migration

Troubleshooting the Migration

This chapter contains the following sections:

Troubleshooting the Cisco Dynamic Fabric Automation (DFA) Migration

Troubleshooting the Cisco Dynamic Fabric Automation (DFA) Migration

After you completed the software and topology migration from FabricPath to the Cisco Dynamic Fabric Automation (DFA) solution, you can use the following checklist to troubleshoot problems with the migration. For more information on troubleshooting, see Cisco Dynamic Fabric Automation Troubleshooting Guide.

Checklist	Complete?
Verifying That Unicast Connectivity Is Established
Verifying That BGP Sessions Are Established
Verifying the VNI
Verifying That the Host Is Learned from ARP and That the Adjacency Table is Properly Updated
Verifying That the HSRP Is Up and ARP Entries Are Updated on Both vPC Peers
Verifying the Port and Virtual Port-Channel Status
Verifying the RIB Entry
Verifying That the BGP Configuration is Enabled on the Remote Leaf
Verifying the Proper IS-IS FabricPath Adjacency
Verifying the IS-IS FabricPath Topology and Database
Verifying That Leafs and Border Leafs Have RP Reachability
Verifying That Multicast Routes Are Properly Propagated
Verifying the PIM on the SVI and the DR and DF on the Host-Facing SVI Are Autoenabled
Verifying That Unique IP Address Per Leaf is Configured

Verifying That Unicast Connectivity Is Established
Verifying That BGP Sessions Are Established
Verifying the VNI
Verifying That the Host Is Learned from ARP and That the Adjacency Table is Properly Updated
Verifying That the HSRP Is Up and ARP Entries Are Updated on Both vPC Peers
Verifying the Port and Virtual Port-Channel Status
Verifying the RIB Entry
Verifying That the BGP Configuration is Enabled on the Remote Leaf
Verifying the Proper IS-IS FabricPath Adjacency
Verifying the IS-IS FabricPath Topology and Database
Verifying That Leafs and Border Leafs Have RP Reachability
Verifying That Multicast Routes Are Properly Propagated
Verifying the PIM on the SVI and the DR and DF on the Host-Facing SVI Are Autoenabled
Verifying That Unique IP Address Per Leaf is Configured

Verifying That Unicast Connectivity Is Established

You can verify that the unicast connectivity is established.

Step 1

On the leaf or border leaf that connects to the sources, send a unicast ping command to the receiver. In this example, vpn1 is the name of the vrf, 188.0.0.1 is the unicast address where the receiver is located, and 199.0.0.2 is the local address on this leaf under vrf vpn1.

Example:

leaf # ping 188.0.0.1 vrf vpn1 source 199.0.0.2
PING 188.0.0.1 (188.0.0.1) from 199.0.0.2: 56 data bytes
64 bytes from 188.0.0.1: icmp_seq=0 ttl=253 time=1.541 ms
64 bytes from 188.0.0.1: icmp_seq=1 ttl=253 time=1.237 ms
64 bytes from 188.0.0.1: icmp_seq=2 ttl=253 time=1.204 ms
64 bytes from 188.0.0.1: icmp_seq=3 ttl=253 time=1.179 ms
64 bytes from 188.0.0.1: icmp_seq=4 ttl=253 time=1.183 ms
--- 188.0.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 1.179/1.268/1.541 ms

Step 2

If the ping fails, verify if the unicast route is present on the leaf or border leaf.

Example:

leaf #  show ip route vrf vpn1
IP Route Table for VRF "vpn1"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
0.0.0.0/0, ubest/mbest: 2/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
1.1.0.0/24, ubest/mbest: 1/0, attached
    *via 1.1.0.1, Vlan10, [0/0], 4d17h, direct
1.1.0.1/32, ubest/mbest: 1/0, attached
    *via 1.1.0.1, Vlan10, [0/0], 4d17h, local
19.19.19.19/32, ubest/mbest: 1/0
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
155.0.0.0/24, ubest/mbest: 2/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
166.0.0.0/24, ubest/mbest: 1/0
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
166.0.0.1/32, ubest/mbest: 1/0
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
177.0.0.0/24, ubest/mbest: 1/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
177.0.0.1/32, ubest/mbest: 1/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
188.0.0.0/24, ubest/mbest: 1/0
    *via 1.1.0.2%default, [200/0], 4d17h, BGP-100, internal, tag 100
188.0.0.1/32, ubest/mbest: 1/0
    *via 1.1.0.2%default, [200/0], 4d16h, BGP-100, internal, tag 100
199.0.0.0/24, ubest/mbest: 1/0, attached
    *via 199.0.0.2, Vlan110, [0/0], 4d17h, direct
199.0.0.1/32, ubest/mbest: 1/0, attached
    *via 199.0.0.1, Vlan110, [190/0], 4d16h, hmm
199.0.0.2/32, ubest/mbest: 1/0, attached
    *via 199.0.0.2, Vlan110, [0/0], 4d17h, local

leaf #  sh ip route vrf vpn1
IP Route Table for VRF "vpn1"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
0.0.0.0/0, ubest/mbest: 2/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
1.1.0.0/24, ubest/mbest: 1/0, attached
    *via 1.1.0.2, Vlan10, [0/0], 4d17h, direct
1.1.0.2/32, ubest/mbest: 1/0, attached
    *via 1.1.0.2, Vlan10, [0/0], 4d17h, local
19.19.19.19/32, ubest/mbest: 1/0
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
155.0.0.0/24, ubest/mbest: 2/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
166.0.0.0/24, ubest/mbest: 1/0
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
166.0.0.1/32, ubest/mbest: 1/0
    *via 1.1.0.4%default, [200/0], 4d17h, BGP-100, internal, tag 100
177.0.0.0/24, ubest/mbest: 1/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
177.0.0.1/32, ubest/mbest: 1/0
    *via 1.1.0.3%default, [200/0], 4d17h, BGP-100, internal, tag 100
188.0.0.0/24, ubest/mbest: 1/0, attached
    *via 188.0.0.2, Vlan110, [0/0], 4d17h, direct
188.0.0.1/32, ubest/mbest: 1/0, attached
    *via 188.0.0.1, Vlan110, [190/0], 4d16h, hmm
188.0.0.2/32, ubest/mbest: 1/0, attached
    *via 188.0.0.2, Vlan110, [0/0], 4d17h, local
199.0.0.0/24, ubest/mbest: 1/0
    *via 1.1.0.1%default, [200/0], 4d17h, BGP-100, internal, tag 100
199.0.0.1/32, ubest/mbest: 1/0
    *via 1.1.0.1%default, [200/0], 4d16h, BGP-100, internal, tag 100

What to Do Next

Verify that the BGP sessions are established.

Verifying That BGP Sessions Are Established

You can verify that the Border Gateway Protocol (BGP) session is established.

Before You Begin

Verify that unicast connectivity is established.

Step 1

Verify that the BGP session on the leaf is attached to the source and verify that the session with the route reflector is established.

Example:

leaf #  show BGP session
Total peers 1, established peers 1
ASN 100
VRF default, local ASN 100
peers 1, established peers 1, local router-id 1.1.0.1
State: I-Idle, A-Active, O-Open, E-Established, C-Closing, S-Shutdown
Neighbor        ASN    Flaps LastUpDn|LastRead|LastWrit St Port(L/R)  Notif(S/R)
1.1.0.5           100 0     4d17h   |00:00:05|00:00:35 E  22421/179  0/0

Step 2

Verify the BGP session on the spine route reflector and verify that the session with the leafs/border leafs are established.

Example:

spine_route reflector #  show BGP session
Total peers 4, established peers 4
ASN 100
VRF default, local ASN 100
peers 4, established peers 4, local router-id 1.1.0.5
State: I-Idle, A-Active, O-Open, E-Established, C-Closing, S-Shutdown
Neighbor        ASN    Flaps LastUpDn|LastRead|LastWrit St Port(L/R)  Notif(S/R)
1.1.0.1           100 0     4d17h   |00:00:46|00:00:15 E  179/22421  0/0
1.1.0.2           100 0     4d17h   |00:00:20|00:00:31 E  179/34401  0/0
1.1.0.3           100 0     4d17h   |00:00:49|00:00:46 E  179/14080  0/0
1.1.0.4	          100 0     4d17h   |00:00:26|00:00:15 E  179/7980   0/0

What to Do Next

Verify that the correct virtual network identifier (VNI) is being used.

Verifying the VNI

You can verify that the correct virtual network identifier (VNI) is being used.

Because of a limitation with a Cisco Nexus 7000 Series spine switch that is running in transit mode, the segment-ID and VNI range that you can use on the leafs/border leafs are determined by the VLAN configured on the spine switch.

VLAN is configured on spine for the following reasons:

Control-segment SVI for BGP route reflector termination on the spine (not applicable if running route reflector on leaf)
Flooding of BUM traffic only to leaf nodes where the VLAN is defined. If VLAN is not configured in spine, BUM traffic are flooded to all leaf nodes. For Cisco Nexus 6000 Series Switches, config VLAN in 'fabricpath mode'. For Cisco Nexus 7000 Series Switches, config VLAN in 'fabricpath mode' and underlying SVI in no-shut state. 4K VNIs are reserved for each VLAN configured on the Spine (not usable as VLAN segment IDs). Reserved VNIs are from <vlan-id>*4096 to (<vlan-id>*4096)+4095.

Before You Begin

Verify that the unicast connectivity is established.
Verify that the Border Gateway Protocol (BGP) sessions are established.

Step 1	Determine which VLANs are configured on the Cisco Nexus 7000 Series spines. In the following example, VLAN 2 is configured on the spine route reflector (RR). Example: spine_rr # `show run \| inc vlan` feature interface-vlan vlan 1
Step 2	Determine which vn-segment and VNI are configured on the leafs and border leafs. In the following example, VNI and vn-segment 9000 are configured on this leaf. Example: source_leaf # `show run \| i vn-segment` feature vn-segment-vlan-based vn-segment 9000 source_leaf # `show run \| i vni` vni 9000 receiver_leaf # `show run \| i vn-segment` feature vn-segment-vlan-based vn-segment 9000 source_leaf# `show run \| i vni` vni 9000
Step 3	Verify if the VNI/vn-segment can be used. If the VLAN you found in Step 1 is "n", you cannot use VNI/vn-segment from n4096 to (n4096)+4095. In this example, you cannot use VNIs 4096 to 8191. In Step 2, you determined that you are using VNI/vn-segment 9000, which is outside the forbidden range. Therefore, the configuration is correct.

What to Do Next

Verify that the host is learned through Address Resolution Protocol (ARP) and that the adjacency table is properly updated.

Verifying That the Host Is Learned from ARP and That the Adjacency Table is Properly Updated

You can verify that the host is learned from address resolution protocol (ARP) and that the adjacency table is properly update.

Before You Begin

Verify that the unicast connectivity is established.
Verify that the border gateway protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used .

Step 1

Verify that the adjacency table is updated properly.

Example:

leaf #  show ip arp vrf default<<< Make sure to check for valid vrf
Flags: * - Adjacencies learnt on non-active FHRP router
       + - Adjacencies synced via CFSoE
       # - Adjacencies Throttled for Glean
       D - Static Adjacencies attached to down interface
IP ARP Table for context default
Total number of entries: 1
Address         Age       MAC Address     Interface
90.99.0.1	      00:00:12  000c.29e2.104b  Vlan90   <<< shows 90.99.0.1 is learnt

Step 2

Verify that the IP adjacency table is properly populated.

Example:

switch # show ip adjacency vrf default<<< Make sure to check for valid vrf
Flags: # - Adjacencies Throttled for Glean
       G - Adjacencies of vPC peer with G/W bit
IP Adjacency Table for VRF default
Total number of entries: 10
Address         MAC Address     Pref Source     Interface
90.99.0.1	      000c.29e2.104b  50   arp        Vlan90

What to Do Next

Verify that the Hot Standby Router Protocol (HSRP) is up and Address Resolution Protocol (ARP) entries are updated on both vPC peers.

Verifying That the HSRP Is Up and ARP Entries Are Updated on Both vPC Peers

You can verify that the Hot Standby Router Protocol (HSRP) is up and that the Address Resolution Protocol (ARP) entries are updated on both virtual port channels (vPCs).

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.

Step 1

Verify the Hot Standby Router Protocol (HSRP) status.

Example:

leaf #  show hsrp
Vlan13 - Group 13 (HSRP-V1) (IPv4)
  Local state is Active, priority 90 (Cfged 90), may preempt
    Forwarding threshold(for vPC), lower: 1 upper: 90
  Hellotime 3 sec, holdtime 10 sec
  Virtual IP address is 10.75.13.1 (Cfged)
  Active router is local
  Standby router is 10.75.13.5, priority 80 expires in 8.607000 sec(s)
  Authentication text "cisco"
  Virtual mac address is 0000.0c07.ac0d (Default MAC)
  0 state changes, last state change never
  IP redundancy name is hsrp-Vlan13-13 (default)

Step 2

Verify the vPC port status.

Example:

leaf #  show vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id                     : 1
vPC+ switch id                    : 1001
Peer status                       : peer adjacency formed ok
vPC keep-alive status             : peer is alive
vPC fabricpath status             : peer is reachable through fabricpath
Configuration consistency status  : success
Per-vlan consistency status       : success
Type-2 consistency status         : success
vPC role                          : secondary
Number of vPCs configured         : 1
Peer Gateway                      : Enabled
Peer gateway excluded VLANs     : -
Dual-active excluded VLANs        : -
Graceful Consistency Check        : Enabled
Auto-recovery status              : Enabled (timeout = 240 seconds)
vPC Peer-link status
---------------------------------------------------------------------
id   Port   Status Active vlans
--   ----   ------ --------------------------------------------------
1    Po100  up     1,90,100,121-122,125-126,1201-1202,1205-1206
vPC status
---------------------------------------------------------------------------
id     Port        Status Consistency Reason       Active vlans vPC+ Attrib
--     ----------  ------ ----------- ------       ------------ -----------
20     Po1         up*  success     success      -            DF: No, FP
                                                                MAC: 1001.0.0

What to Do Next

Verify the member port status and that the vPC leg port channel is up.

Verifying the Port and Virtual Port-Channel Status

You can verify that the both port and that the vPC port-channel are up.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port channel (vPC) peers.

Step 1

Determine the port-channel status.

Example:

leaf #  show port-channel summary interface port-channel 1
Flags:  D - Down        P - Up in port-channel (members)
        I - Individual  H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
        M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port-       Type     Protocol  Member Ports
      Channel
--------------------------------------------------------------------------------
1     Po1(SD)     Eth      LACP      Eth1/35(D)
switch#

Step 2

Determine the interface status. If it is down due to a peer link, it might require an autorecovery to timeout before the interface status is up. The default autorecovery timeout default is 240 seconds.

Example:

leaf # show int eth 1/35 | head
Ethernet1/35 is up (vpc peerlink is up)
 Dedicated Interface
  Belongs to Po1
  Hardware: 1000/10000 Ethernet, address: 002a.6a22.c1ca (bia 002a.6a22.c1ca)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
  reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA
  Port mode is trunk
  auto-duplex, 1000 Mb/s, media type is 1G
  Beacon is turned off

What to Do Next

Verify the route in the Routing Information Base (RIB) entry and that the RIB is properly populated.

Verifying the RIB Entry

You can verify that the route in the routing information base (RIB) entry is correct and that the RIB is properly populated .

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port channel (vPC) peers.
Verify the port and vPC port channel status.

Step 1

Verify the RIB local route and ensure to check for HMM route in RIB.

Example:

leaf # show ip route vrf vrf2 2.10.1.2/32
IP Route Table for VRF "vrf2"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
2.10.1.2/32, ubest/mbest: 1/0, attached
    *via 2.10.1.2, Vlan2, [190/0], 2d17h, hmm

Step 2

Verify that the Border Gateway Protocol (BGP) configuration exists.

Example:

leaf #show run BGP 100
  router-id 1.1.100.22
neighbor 1.1.100.11
    remote-as 200
vrf vrf10
    address-family ipv4 unicast
      redistribute hmm route-map hmm-to-BGP <<< Make sure to check  that the hmm routes are being redistibuted

leaf #  show run rpm
!Command: show running-config rpm
!Time: Fri Mar  7 23:04:31 2014
version 7.0(1)N1(1)
route-map hmm-to-BGP permit 10 <<< Make sure to check for route-map exist

What to Do Next

Verify that the remote hosts route appears in both the RIB and the BGP RIB.

Verifying That the BGP Configuration is Enabled on the Remote Leaf

If the remote Border Gateway Protocol (BGP) routes do not appear in the BGP routing information base (RIB), you can verify that the BGP configuration is properly enabled on the remote leaf.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port channel (vPC) peers.
Verify the port and vPC port-channel status.
Verify the routing information base (RIB) entry.

Step 1

If the remote BGP routes are not seen in BRIB, verify that the BGP configuration is properly enabled on the remote leaf.

Example:

leaf # show run BGP
  !Command: show running-config bgp
!Time: Tue May 19 18:08:45 2015

version 7.2(0)N1(1)
feature bgp

router bgp 65000
  router-id 1.1.1.64
  address-family ipv4 unicast
    redistribute hmm route-map AM
    maximum-paths ibgp 2
    additional-paths receive
  address-family ipv6 unicast
    redistribute hmm route-map hosts-v6
    maximum-paths ibgp 2
    additional-paths receive
  address-family vpnv4 unicast
    additional-paths receive
  address-family vpnv6 unicast
    additional-paths receive
  neighbor 1.1.1.61 remote-as 65000
    address-family ipv4 unicast
      send-community both
    address-family ipv6 unicast
      send-community both
    address-family vpnv4 unicast
      send-community extended
      capability additional-paths receive
    address-family vpnv6 unicast
      send-community both
  vrf vrf1
    address-family ipv4 unicast
      redistribute hmm route-map AM
    address-family ipv6 unicast
      redistribute hmm route-map hosts-v6
  vrf vrf2
    address-family ipv4 unicast
      redistribute hmm route-map AM
    address-family ipv6 unicast
      redistribute hmm route-map hosts-v6 vrf context vrf1
  rd auto
  address-family ipv4 unicast
    route-target import 5000:1
    route-target export 5000:1
  address-family ipv6 unicast
    route-target import 5000:1
    route-target export 5000:1
vrf context vrf2
  rd auto
  address-family ipv4 unicast
    route-target import 7000:1
    route-target export 7000:1
  address-family ipv6 unicast
    route-target import 7000:1
    route-target export 7000:1

Step 2

Verify that the virtual route forwarding (VRF) instance has the route-target configured as auto or export on the other end.

Example:

leaf # show run vrf vrf2
!Command: show running-config vrf vrf2
!Time: Tue May 19 18:09:26 2015

version 7.2(0)N1(1)
vrf context vrf2
  rd auto
  address-family ipv4 unicast
    route-target import 7000:1
    route-target export 7000:1
  address-family ipv6 unicast
    route-target import 7000:1
    route-target export 7000:1
  vni 7000
router bgp 65000
  vrf vrf2
    address-family ipv4 unicast
      redistribute hmm route-map AM
    address-family ipv6 unicast
      redistribute hmm route-map hosts-v6

What to Do Next

Verify the proper Intermediate-system-to-intermediate-system (ISIS) FabricPath adjacency operation.

Verifying the Proper IS-IS FabricPath Adjacency

You can verify the proper Intermediate-system to intermediate-system (ISIS) FabricPath Adjacency operation.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port-channel (vPC) peers.
Verify the port and vPC port channel status.
Verify the Routing Information Base (RIB) entry.
Verify that the remote host appears in both the RIB and the BGP RIB.

Step 1	Verify the FabricPath IS-IS adjacency on the spine for all the attached leaf nodes. Example: spine # `show fabricpath isis adjacency` Fabricpath IS-IS domain: default Fabricpath IS-IS adjacency database: System ID SNPA Level State Hold Time Interface ln1 N/A 1 UP 00:00:30 Ethernet2/1 ln2 N/A 1 UP 00:00:22 Ethernet2/2 ln3 N/A 1 UP 00:00:24 Ethernet2/3
Step 2	Verify the FabricPath IS-IS unique switch ID. Example: leaf # `show fabricpath isis switch-id` Fabricpath IS-IS domain: default Fabricpath IS-IS Switch-ID Database Legend: C - Confirmed, T - tentative, W - swap S - sticky, E - Emulated Switch A - Anycast Switch '' - this system System-ID Primary Secondary Reachable Bcast-Priority FtagRootCapable? MT-0 000e.0100.0030 3479[C] 0[C] Yes 64 Y 000e.0101.0030 1599[C] 0[C] Yes 64 Y 000f.0100.0030 374 [C] 0[C] Yes 64 Y 000f.0101.0030 1533[C] 0[C] Yes 64 Y 000f.0102.0030 692 [C] 0[C] Yes 64 Y # 3479 is the local switch-id
Step 3	Verify FabricPath IS-IS routes. Example: leaf # `show fabricpath isis route` Fabricpath IS-IS domain: default MT-0 Topology 0, Tree 0, Swid routing table 374, L1 via Ethernet2/1, metric 400 692, L1 via Ethernet2/3, metric 400 1533, L1 via Ethernet2/2, metric 400 1599, L1 via Ethernet2/1, metric 800 via Ethernet2/2, metric 800 via Ethernet2/3, metric 800
Step 4	Verify the FabricPath IS-IS interface. Example: leaf # `show fabricpath isis interface` Fabricpath IS-IS domain: default Interface: Ethernet2/1 Status: protocol-up/link-up/admin-up Index: 0x0001, Local Circuit ID: 0x01, Circuit Type: L1 No authentication type/keychain configured Authentication check specified Extended Local Circuit ID: 0x1A080000, P2P Circuit ID: 0000.0000.0000.00 Retx interval: 10, Retx throttle interval: 666 ms LSP interval: 33 ms, MTU: 1500 P2P Adjs: 1, AdjsUp: 1, Priority 64 Hello Interval: 10, Multi: 3, Next IIH: 00:00:04 Level Adjs AdjsUp Metric CSNP Next CSNP Last LSP ID 1 1 1 400 60 Inactive ffff.ffff.ffff.ff-ff Topologies enabled: Topology Metric MetricConfig Forwarding 0 400 no UP Interface: Ethernet2/2 Status: protocol-up/link-up/admin-up Index: 0x0002, Local Circuit ID: 0x01, Circuit Type: L1 No authentication type/keychain configured Authentication check specified Extended Local Circuit ID: 0x1A081000, P2P Circuit ID: 0000.0000.0000.00 Retx interval: 10, Retx throttle interval: 666 ms LSP interval: 33 ms, MTU: 1500 P2P Adjs: 1, AdjsUp: 1, Priority 64 Hello Interval: 10, Multi: 3, Next IIH: 00:00:06 Level Adjs AdjsUp Metric CSNP Next CSNP Last LSP ID 1 1 1 400 60 Inactive ffff.ffff.ffff.ff-ff Topologies enabled: Topology Metric MetricConfig Forwarding 0 400 no UP Interface: Ethernet2/3 Status: protocol-up/link-up/admin-up Index: 0x0003, Local Circuit ID: 0x01, Circuit Type: L1 No authentication type/keychain configured Authentication check specified Extended Local Circuit ID: 0x1A082000, P2P Circuit ID: 0000.0000.0000.00 Retx interval: 10, Retx throttle interval: 666 ms LSP interval: 33 ms, MTU: 1500 P2P Adjs: 1, AdjsUp: 1, Priority 64 Hello Interval: 10, Multi: 3, Next IIH: 00:00:02 Level Adjs AdjsUp Metric CSNP Next CSNP Last LSP ID 1 1 1 400 60 Inactive ffff.ffff.ffff.ff-ff Topologies enabled: Topology Metric MetricConfig Forwarding 0 400 no UP leaf # `show ip adjacency` Flags: # - Adjacencies Throttled for Glean G - Adjacencies of vPC peer with G/W bit IP Adjacency Table for VRF default Total number of entries: 4 Address MAC Address Pref Source Interface 1.1.1.61 002a.6a1e.acbc 1 ISIS Vlan1 1.1.1.62 002a.6afe.33bc 1 ISIS Vlan1 1.1.1.63 002a.6afe.32c1 1 ISIS Vlan1 1.1.1.65 5897.1ef0.780c 1 ISIS Vlan1

What to Do Next

Verify the FabricPath ISIS topology and database and verify that the Unicast Routing Information Base (uRIB) and Unicast Forwarding Information Base (uFIB) are properly populated.

Verifying the IS-IS FabricPath Topology and Database

You can verify that the IS-IS FabricPath topology and database are properly configured and verify that the Unicast Routing Information Base (uRIB) and Unicast Forwarding Information Base (uFIB) are properly populated.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port channel (vPC) peers.
Verify the port and vPC port-channel status.
Verify the routing information base (RIB) entry.
Verify that the remote host appears in both the RIB and the BGP RIB.
Verify the proper FabricPath Intermediate-System-to-Intermediate-System (ISIS) adjacency.

Step 1

Determine the FabricPath IS-IS topology.

Example:

leaf # show fabricpath isis topology summary
Summary is set!.
FabricPath IS-IS Topology Summary
Fabricpath IS-IS domain: default
MT-0
  Configured interfaces:  Ethernet2/1  Ethernet2/2  Ethernet2/3
Max number of trees: 2  Number of trees supported: 2
    Tree id: 1, ftag: 1, root system: 000f.0100.0030, 2084
    Tree id: 2, ftag: 2, root system: 000f.0102.0030, 3154
Ftag Proxy Root: 000f.0100.0030

Step 2

Verify the FabricPath IS-IS database.

Example:

leaf #  show fabricpath isis database
Fabricpath IS-IS domain: default LSP database
  LSPID                 Seq Number   Checksum  Lifetime   A/P/O/T
  sn1.00-00           * 0x00000008   0xF4BB    707        0/0/0/1
  sn2.00-00             0x00000008   0x4B7E    705        0/0/0/1
  ln1.00-00             0x00000005   0x1C01    711        0/0/0/1
  ln2.00-00             0x00000006   0x0173    766        0/0/0/1
  ln3.00-00             0x00000004   0x0C46    766        0/0/0/1
sn1# term len 0

Step 3

Display the FabricPath IS-IS database detail and verify that the uRIB and uFIB are properly populated.

Example:

sn1 # show fabricpath isis database detail
Fabricpath IS-IS domain: default LSP database
  LSPID                 Seq Number   Checksum  Lifetime   A/P/O/T
  sn1.00-00           * 0x00000009   0xF2BC    1029       0/0/0/1
    Instance      :  0x00000009
    Area Address  :  00
    NLPID         :  0xCC 0x8E 0xC0
    Hostname      :  sn1                Length : 3
    Extended IS   :            ln3.00             Metric : 400
    Extended IS   :            ln2.00             Metric : 400
    Extended IS   :            ln1.00             Metric : 400
    Capability    : Device Id: 3479 Base Topology
      Version         :
       Version: 1 Flags: 0
      Nickname        :
       Priority: 0 Nickname: 3479 BcastPriority: 64
      IP to MAC Mapping :
       MAC: 000e.0100.0030, # IPv4 addr 1, # IPv6 addr 1
         IPv4 address: 110.1.1.1
         IPv6 address: 2110::1
      Nickname Migration :
       Swid: 3479 Sec. Swid: 0
      Base Topo Trees :
       Trees desired: 2  Trees computed: 2  Trees usable: 2
    Digest Offset :  0
  sn2.00-00             0x00000009   0x497F    1059       0/0/0/1
    Instance      :  0x00000004
    Area Address  :  00
    NLPID         :  0xCC 0x8E 0xC0
    Hostname      :  sn2                Length : 3
    Extended IS   :            ln3.00             Metric : 400
    Extended IS   :            ln2.00             Metric : 400
    Extended IS   :            ln1.00             Metric : 400
    Capability    : Device Id: 1599 Base Topology
      Version         :
       Version: 1 Flags: 0
      Nickname        :
       Priority: 0 Nickname: 1599 BcastPriority: 64
      IP to MAC Mapping :
       MAC: 000e.0101.0030, # IPv4 addr 1, # IPv6 addr 1
         IPv4 address: 110.1.1.2
         IPv6 address: 2110::2
      Nickname Migration :
       Swid: 1599 Sec. Swid: 0
      Base Topo Trees :
       Trees desired: 2  Trees computed: 2  Trees usable: 2
    Digest Offset :  0
  ln1.00-00             0x00000006   0x1A02    1068       0/0/0/1
    Instance      :  0x00000003
    Area Address  :  00
    NLPID         :  0xCC 0x8E 0xC0
    Hostname      :  ln1                Length : 3
    Extended IS   :            sn2.00             Metric : 400
    Extended IS   :            sn1.00             Metric : 400
    Capability    : Device Id: 374 Base Topology
      Version         :
       Version: 1 Flags: 0

What to Do Next

Verify that leafs and borders leafs have rendezvous point (RP) reachability.

Verifying That Leafs and Border Leafs Have RP Reachability

You can verify that the leafs and border leafs have rendezvous point (RP) reachability.

Note

If you are running Source Specific Multicast (SSM) only, you can skip this step.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port-channel (vPC) peers.
Verify the port and vPC port channel status.
Verify the Routing Information Base (RIB) entry.
Verify that the remote host appears in both the RIB and the BGP RIB.
Verify the proper FabricPath intermediate-system-to-intermediate-system (IS-IS) adjacency.
Verify the FabricPath IS-IS topology and database.

Step 1

Verify that RP information exists on leafs and border leafs. In this example, vpn1 is the name of the vrf that you are investigating and RP 19.19.19.19 corresponds to a sparse mode group range 239.0.0.0/16.

Example:

source_leaf # show ip pim rp vrf vpn1
PIM RP Status Information for VRF "vpn1"
BSR disabled
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None
RP: 19.19.19.19, (0), uptime: 4d20h, expires: never,
  priority: 0, RP-source: (local), group ranges:
      239.0.0.0/16 

receiver_leaf # show  ip pim rp vrf vpn1
PIM RP Status Information for VRF "vpn1"
BSR disabled
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None
RP: 19.19.19.19, (0), uptime: 4d20h, expires: never,
  priority: 0, RP-source: (local), group ranges:
      239.0.0.0/16

Step 2

Verify that you can ping the RP from leafs and border leafs.

Example:

source_leaf # ping 19.19.19.19 vrf vpn1 source 199.0.0.2
PING 19.19.19.19 (19.19.19.19) from 199.0.0.2: 56 data bytes
64 bytes from 19.19.19.19: icmp_seq=0 ttl=254 time=1.829 ms
64 bytes from 19.19.19.19: icmp_seq=1 ttl=254 time=1.092 ms
64 bytes from 19.19.19.19: icmp_seq=2 ttl=254 time=1.075 ms
64 bytes from 19.19.19.19: icmp_seq=3 ttl=254 time=1.078 ms
64 bytes from 19.19.19.19: icmp_seq=4 ttl=254 time=1.07 ms

Receiver_leaf # ping 19.19.19.19 vrf vpn1 source 188.0.0.2
PING 19.19.19.19 (19.19.19.19) from 188.0.0.2: 56 data bytes
64 bytes from 19.19.19.19: icmp_seq=0 ttl=254 time=2.037 ms
64 bytes from 19.19.19.19: icmp_seq=1 ttl=254 time=1.028 ms
64 bytes from 19.19.19.19: icmp_seq=2 ttl=254 time=1.025 ms
64 bytes from 19.19.19.19: icmp_seq=3 ttl=254 time=1.015 ms
64	bytes from 19.19.19.19: icmp_seq=4 ttl=254 time=0.954 ms

What to Do Next

Verify that multicast routes are properly propagated.

Verifying That Multicast Routes Are Properly Propagated

You can verify that multicast routes have been properly propagated.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both vPC peers.
Verify the port and vPC port-channel status.
Verify the Routing Information Base (RIB) entry.
Verify that the remote host appears in both the RIB and the BGP RIB.
Verify the proper FabricPath intermediate-system-to-intermediate-system (ISIS) adjacency.
Verify the FabricPath IS-IS topology and database.
Verify that leafs and borders leafs have rendezvous point (RP) reachability.

For SSM streams, verify the mroute states on leafs connect to both the source and the receiver. In this example, the host-facing switch virtual interface (SVI) is VLAN 110, and the fabric-facing SVI is VLAN 10. For sparse mode streams, which source actively sending traffic, check the mroute states on both leafs that connect to the source and receiver. For bidirectional streams, check the mroute states on leafs that connect to the source and the receiver.

Step 1	Verify the mroute on the source. Example: source_leaf # `show ip mroute vrf vpn1` IP Multicast Routing Table for VRF "vpn1" (, 232.0.0.0/8), uptime: 4d21h, pim ip Incoming interface: Null, RPF nbr: 0.0.0.0 Outgoing interface list: (count: 0) (199.0.0.1/32, 232.1.1.1/32), uptime: 18:40:02, fabric_mcast ip pim Incoming interface: Vlan110, RPF nbr: 199.0.0.1 Outgoing interface list: (count: 1) (Fabric OIF) Vlan10*, uptime: 18:40:02, fabric_mcast For the leaf that attaches to the source, verify that incoming interface is the host-facing SVI, while the outgoing interface is the fabric-facing SVI.
Step 2	Verify the mroute on the receiver. Example: receiver_leaf # `show ip mroute vrf vpn1` IP Multicast Routing Table for VRF "vpn1" (, 232.0.0.0/8), uptime: 4d21h, pim ip Incoming interface: Null, RPF nbr: 0.0.0.0 Outgoing interface list: (count: 0) (199.0.0.1/32, 232.1.1.1/32), uptime: 18:40:10, igmp ip pim Incoming interface: Vlan10, RPF nbr: 1.1.0.1 Outgoing interface list: (count: 1) Vlan110*, uptime: 18:40:10, igmp feature interface-vlan For the leaf that attaches to the receiver, verify that the incoming interface is the fabric-facing SVI, while the outgoing interface is the host-facing SVI.
Step 3	Verify the mroute on the source. Example: source_leaf # `show ip mroute vrf vpn1` IP Multicast Routing Table for VRF "vpn1" (199.0.0.1/32, 239.0.0.1/32), uptime: 00:00:11, ip pim fabric_mcast Incoming interface: Vlan110, RPF nbr: 199.0.0.1 Outgoing interface list: (count: 1) (Fabric OIF) Vlan10, uptime: 00:00:11, fabric_mcast For the leaf attaching to the source, make sure the incoming interface is the host facing SVI, while the outgoing interface is the fabric facing SVI.
Step 4	Use the show ip mroute vrf command to verify the mroute on the receiver. Example: receiver_leaf # `show ip mroute vrf vpn1` IP Multicast Routing Table for VRF "vpn1" (, 239.0.0.1/32), uptime: 00:00:29, igmp ip pim Incoming interface: Vlan10, RPF nbr: 1.1.0.4 Outgoing interface list: (count: 1) Vlan110, uptime: 00:00:29, igmp (199.0.0.1/32, 239.0.0.1/32), uptime: 00:00:19, ip mrib pim Incoming interface: Vlan10, RPF nbr: 1.1.0.1 Outgoing interface list: (count: 1) Vlan110*, uptime: 00:00:19, mrib For the leaf attaching to the receiver, make sure the incoming interface is the fabric facing SVI, while the outgoing interface is the host facing SVI.
Step 5	Verify the mroute on the source . Example: Source_leaf # `show ip mroute vrf vpn1` IP Multicast Routing Table for VRF "vpn1" *(, 238.0.0.0/16), bidir, uptime: 4d22h, pim ip Incoming interface: Vlan10, RPF nbr: 1.1.0.4 Outgoing interface list: (count: 1) Vlan10*, uptime: 4d22h, pim, (RPF) For the leaf that attaches to the source, you do not see the exact group the receiver joined. Verify that (,G/m) which matches the joined group. Both incoming and outgoing interfaces should be the fabric- facing SVI.
Step 6	Verify the mroute on the receiver. Example: receiver_leaf # `show ip mroute vrf vpn1` IP Multicast Routing Table for VRF "vpn1" (, 238.0.0.0/16), bidir, uptime: 4d22h, pim ip Incoming interface: Vlan10, RPF nbr: 1.1.0.4 Outgoing interface list: (count: 1) Vlan10, uptime: 4d22h, pim, (RPF) (, 238.0.0.1/32), bidir, uptime: 00:00:06, igmp ip pim Incoming interface: Vlan10, RPF nbr: 1.1.0.4 Outgoing interface list: (count: 2) Vlan10, uptime: 00:00:06, pim, (RPF) Vlan110*, uptime: 00:00:06, igmp For the leaf that attaches to the receiver, verify that the same (,G/m) entry exist. Also, verify the receiver joined group exists. For this (*,G), the incoming interface is the fabric-facing SVI, while the outgoing interface are both the host-facing SVI and fabric-facing SVI.

What to Do Next

Verify that PIM is autoenabled and that the Designated Router (DR)/Designated Forwarder (DF) is on the SVIs.

Verifying the PIM on the SVI and the DR and DF on the Host-Facing SVI Are Autoenabled

You can verify that the Protocol Independent Multicast (PIM) on the Switch Virtual Interfaces (SVIs) are configured properly and that the Designated Router (DR) and Designated Forwarder (DF) on the host-facing SVI are autoenabled.

Before You Begin

Verify that unicast connectivity is established.
Verify that Border Gateway Protocol (BGP) sessions are established.
Verify that the correct virtual network identifier (VNI) is being used.
Verify that the host is learned from the Address Resolution Protocol (ARP) and that the adjacency table is properly updated.
Verify that the Hot Standby Route Protocol (HSRP) is up and ARP entries for the host are updated on both virtual port-channel (vPC) peers.
Verify the port and vPC port channel status.
Verify the Routing Information Base (RIB) entry.
Verify that the remote host appears in both the RIB and the BGP RIB.
Verify the proper FabricPath intermediate-system to intermediate-system (IS-IS) adjacency.
Verify the FabricPath IS-IS topology and database.
Verify that leafs and borders leafs have rendezvous point (RP) reachability.
Verify that multicast routes are properly propagated.

Step 1

Verify the PIM on the source leaf.

Example:

source_leaf #  show ip pim int vrf vpn1
PIM Interface Status for VRF "vpn1"
Vlan10, Interface status: protocol-up/link-up/admin-up
  IP address: 1.1.0.1, IP subnet: 1.1.0.0/24
  PIM DR: 1.1.0.1, DR's priority: 1
  PIM neighbor count: 0
  PIM hello interval: 30 secs, next hello sent in: 0.000000
  PIM neighbor holdtime: 105 secs
  PIM configured DR priority: 1
  PIM configured DR delay: 3 secs
  PIM border interface: no
  PIM GenID sent in Hellos: 0x2bf9d0c3
  PIM Hello MD5-AH Authentication: disabled
  PIM Neighbor policy: none configured
  PIM Join-Prune inbound policy: none configured
  PIM Join-Prune outbound policy: none configured
  PIM Join-Prune interval: 1 minutes
  PIM Join-Prune next sending: 1 minutes
  PIM BFD enabled: no
  PIM passive interface: yes
  PIM VPC SVI: no
  PIM Auto Enabled: yes
  PIM Interface Statistics, last reset: never
    General (sent/received):
      Hellos: 0/0 (early: 0), JPs: 0/0, Asserts: 0/0
      Grafts: 0/0, Graft-Acks: 0/0
      DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0
    Errors:
      Checksum errors: 0, Invalid packet types/DF subtypes: 0/0
      Authentication failed: 0
      Packet length errors: 0, Bad version packets: 0, Packets from self: 0
      Packets from non-neighbors: 0
          Packets received on passiveinterface: 0
      JPs received on RPF-interface: 0
      (*,G) Joins received with no/wrong RP: 0/0
      (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0
      JPs filtered by inbound policy: 0
      JPs filtered by outbound policy: 0
Vlan110, Interface status: protocol-up/link-up/admin-up
  IP address: 199.0.0.2, IP subnet: 199.0.0.0/24
  PIM DR: 199.0.0.2, DR's priority: 1
  PIM neighbor count: 0
  PIM hello interval: 30 secs, next hello sent in: 0.000000
  PIM neighbor holdtime: 105 secs
  PIM configured DR priority: 1
  PIM configured DR delay: 3 secs
  PIM border interface: no
  PIM GenID sent in Hellos: 0x0ce78912
  PIM Hello MD5-AH Authentication: disabled
  PIM Neighbor policy: none configured
  PIM Join-Prune inbound policy: none configured
  PIM Join-Prune outbound policy: none configured
  PIM Join-Prune interval: 1 minutes
  PIM Join-Prune next sending: 1 minutes
  PIM BFD enabled: no
  PIM passive interface: yes
  PIM VPC SVI: no
  PIM Auto Enabled: yes
  PIM Interface Statistics, last reset: never
    General (sent/received):
      Hellos: 14330/13827 (early: 0), JPs: 831/0, Asserts: 0/0
      Grafts: 0/0, Graft-Acks: 0/0
      DF-Offers: 0/0, DF-Winners: 13616/0, DF-Backoffs: 0/0, DF-Passes: 0/0
    Errors:
      Checksum errors: 0, Invalid packet types/DF subtypes: 0/0
      Authentication failed: 0
      Packet length errors: 0, Bad version packets: 0, Packets from self: 0
      Packets from non-neighbors: 0
          Packets received on passiveinterface: 595
      JPs received on RPF-interface: 0
      (*,G) Joins received with no/wrong RP: 0/0
      (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0
      JPs filtered by inbound policy: 0
      JPs filtered by outbound policy: 0

Step 2

Verify the PIM on the receiver leaf.

Example:

receiver_leaf #  show ip pim int vrf vpn1
PIM Interface Status for VRF "vpn1"
Vlan10, Interface status: protocol-up/link-up/admin-up
  IP address: 1.1.0.2, IP subnet: 1.1.0.0/24
  PIM DR: 1.1.0.2, DR's priority: 1
  PIM neighbor count: 0
  PIM hello interval: 30 secs, next hello sent in: 0.000000
  PIM neighbor holdtime: 105 secs
  PIM configured DR priority: 1
  PIM configured DR delay: 3 secs
  PIM border interface: no
  PIM GenID sent in Hellos: 0x26bf8eb9
  PIM Hello MD5-AH Authentication: disabled
  PIM Neighbor policy: none configured
  PIM Join-Prune inbound policy: none configured
  PIM Join-Prune outbound policy: none configured
  PIM Join-Prune interval: 1 minutes
  PIM Join-Prune next sending: 1 minutes
  PIM BFD enabled: no
  PIM passive interface: yes
  PIM VPC SVI: no
  PIM Auto Enabled: yes
  PIM Interface Statistics, last reset: never
    General (sent/received):
      Hellos: 0/0 (early: 0), JPs: 0/0, Asserts: 0/0
      Grafts: 0/0, Graft-Acks: 0/0
      DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0
    Errors:
      Checksum errors: 0, Invalid packet types/DF subtypes: 0/0
      Authentication failed: 0
      Packet length errors: 0, Bad version packets: 0, Packets from self: 0
      Packets from non-neighbors: 0
          Packets received on passiveinterface: 0
      JPs received on RPF-interface: 0
      (*,G) Joins received with no/wrong RP: 0/0
      (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0
      JPs filtered by inbound policy: 0
      JPs filtered by outbound policy: 0
Vlan110, Interface status: protocol-up/link-up/admin-up
  IP address: 188.0.0.2, IP subnet: 188.0.0.0/24
  PIM DR: 188.0.0.2, DR's priority: 1
  PIM neighbor count: 0
  PIM hello interval: 30 secs, next hello sent in: 0.000000
  PIM neighbor holdtime: 105 secs
  PIM configured DR priority: 1
  PIM configured DR delay: 3 secs
  PIM border interface: no
  PIM GenID sent in Hellos: 0x1f81e5a1
  PIM Hello MD5-AH Authentication: disabled
  PIM Neighbor policy: none configured
  PIM Join-Prune inbound policy: none configured
  PIM Join-Prune outbound policy: none configured
  PIM Join-Prune interval: 1 minutes
  PIM Join-Prune next sending: 1 minutes
  PIM BFD enabled: no
  PIM passive interface: yes
  PIM VPC SVI: no
  PIM Auto Enabled: yes
  PIM Interface Statistics, last reset: never
    General (sent/received):
      Hellos: 14264/13767 (early: 0), JPs: 0/0, Asserts: 0/0
      Grafts: 0/0, Graft-Acks: 0/0
      DF-Offers: 0/0, DF-Winners: 13558/0, DF-Backoffs: 0/0, DF-Passes: 0/0
    Errors:
      Checksum errors: 0, Invalid packet types/DF subtypes: 0/0
      Authentication failed: 0
      Packet length errors: 0, Bad version packets: 0, Packets from self: 0
      Packets from non-neighbors: 0
          Packets received on passiveinterface: 652
      JPs received on RPF-interface: 0
      (*,G) Joins received with no/wrong RP: 0/0
      (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0
      JPs filtered by inbound policy: 0
      JPs filtered by outbound policy: 0

For both leafs attaching to source and receiver, make sure both fabric and host facing SVIs are DR,  PIM passive, and PIM Auto Enabled.

Step 3

Verify that both the host and fabric SVIs are DF Winners.

Example:

source_leaf # show ip pim df vrf vpn1
Bidir-PIM Designated Forwarder Information for VRF "vpn1"
RP Address (ordinal)   RP Metric        Group Range
18.18.18.18 (2)        [200/0]          238.0.0.0/16
  Interface            DF Address       DF State   DF Metric    DF Uptime
  Vlan10               1.1.0.1          Winner     [0/0]        4d23h     (RPF)
  Vlan110              199.0.0.2        Winner     [200/0]      4d23h   

Receiver_leaf #  show ip pim df vrf vpn1
Bidir-PIM Designated Forwarder Information for VRF "vpn1"
RP Address (ordinal)   RP Metric        Group Range
18.18.18.18 (2)        [200/0]          238.0.0.0/16
  Interface            DF Address       DF State   DF Metric    DF Uptime
  Vlan10               1.1.0.2          Winner     [0/0]        4d23h     (RPF)
  Vlan110              188.0.0.2        Winner     [200/0]      4d23h

Verifying That Unique IP Address Per Leaf is Configured

The profile configures a unique IP address per leaf on each VRF and advertises it via MP-BGP to all the leaf nodes. For troubleshooting, any host can ping any leaf in that VRF and vice-versa.

The following is an example for vrf-common-loopback-universal configuration profile:

configure profile vrf-common-loopback-universal interface loopback 
interface loopback $system_auto_loopbackId
vrf member $vrfName
  ip address $system_auto_backboneIpAddress/32 tag 12345
vrf context $vrfName
vni $include_vrfSegmentId
rd auto
ip route 0.0.0.0/0 $include_serviceNodeIpAddress
address-family ipv4 unicast
  route-target both auto
address-family ipv6 unicast
  route-target both auto
router bgp $asn
vrf $vrfName
  address-family ipv4 unicast
   redistribute hmm route-map FABRIC-RMAP-REDIST-HOST
   redistribute direct route-map FABRIC-RMAP-REDIST-SUBNET
   maximum-paths ibgp 2
  address-family ipv6 unicast
   redistribute hmm route-map FABRIC-RMAP-REDIST-V6HOST
   redistribute direct route-map FABRIC-RMAP-REDIST-SUBNET
   maximum-paths ibgp 2

Cisco Dynamic Fabric Automation Migration Guide

Bias-Free Language

Book Title

Cisco Dynamic Fabric Automation Migration Guide

Chapter Title