Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
953
Views
0
Helpful
2
Replies

Leafs in POD-2 are showing inactive under fabric membership.

sarabsin
Level 1
Level 1

‎04-12-2018 07:39 AM - edited ‎03-01-2019 05:31 AM

Hi ,

I am setting up multipod POD-1 is all discovered and POD-2 gets DHCP ip address through IPN network.

 

However Leafs of POD-2 are showing as inactive under Fabric membershic under inventory. Spines of POD-2 are showing as Active.

 

On Leafs i can see that Fabric is present ...with all routes  of POD-1 injected coming through IPN 

Spines of POD-2 are 172.25.120.64,172.25.88.64

 

Any help would be appreciated.

 

 

show ip route vrf all on one of the Inactive Leafs of POD-2
IP Route Table for VRF "black-hole"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>


IP Route Table for VRF "overlay-1"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

11.11.11.11/32, ubest/mbest: 2/0
*via 172.25.120.64, eth1/50.18, [115/64], 00:15:32, isis-isis_infra, L1
*via 172.25.88.64, eth1/49.19, [115/64], 00:15:32, isis-isis_infra, L1
22.22.22.22/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
101.101.101.101/32, ubest/mbest: 2/0
*via 172.25.120.64, eth1/50.18, [115/64], 00:15:32, isis-isis_infra, L1
*via 172.25.88.64, eth1/49.19, [115/64], 00:15:32, isis-isis_infra, L1
102.102.102.102/32, ubest/mbest: 2/0
*via 172.25.120.64, eth1/50.18, [115/64], 00:15:32, isis-isis_infra, L1
*via 172.25.88.64, eth1/49.19, [115/64], 00:15:32, isis-isis_infra, L1
172.25.0.33/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.0.34/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.0.35/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.0.65/32, ubest/mbest: 1/0
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.0.66/32, ubest/mbest: 1/0
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.0.67/32, ubest/mbest: 1/0
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.0.69/32, ubest/mbest: 1/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
172.25.0.70/32, ubest/mbest: 1/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
172.25.0.71/32, ubest/mbest: 1/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
172.25.88.64/32, ubest/mbest: 1/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
172.25.88.66/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/3], 00:09:38, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/3], 00:09:38, isis-isis_infra, L1
172.25.120.64/32, ubest/mbest: 1/0
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.25.120.65/32, ubest/mbest: 2/0, attached, direct
*via 172.25.120.65, lo0, [1/0], 00:16:24, local, local
*via 172.25.120.65, lo0, [1/0], 00:16:24, direct
172.26.0.0/16, ubest/mbest: 2/0
*via 172.25.120.64, eth1/50.18, [115/64], 00:15:32, isis-isis_infra, L1
*via 172.25.88.64, eth1/49.19, [115/64], 00:15:32, isis-isis_infra, L1
172.26.0.0/27, ubest/mbest: 1/0, attached, direct
*via 172.26.0.30, vlan15, [1/0], 00:16:42, direct
172.26.0.3/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/12], 00:09:38, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/12], 00:09:38, isis-isis_infra, L1
172.26.0.30/32, ubest/mbest: 1/0, attached
*via 172.26.0.30, vlan15, [1/0], 00:16:42, local, local
172.26.184.64/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.26.184.65/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1
172.26.184.66/32, ubest/mbest: 2/0
*via 172.25.88.64, eth1/49.19, [115/2], 00:13:07, isis-isis_infra, L1
*via 172.25.120.64, eth1/50.18, [115/2], 00:12:57, isis-isis_infra, L1

Labels:
0 Helpful
2 Replies 2

sarabsin
Level 1
Level 1

‎04-12-2018 08:46 AM

One more observations

 

BGP sessions are up between Spines of both Pods.

In Pod-1 , Spines have sessions are up with Pod-1 leafs.

In Pod-2 , there are no BGP sessions between spines and leafs of POD-2.

 

Alos noticed there are no next-hops in the BGP sessions.

0 Helpful

sarabsin
Level 1
Level 1
In response to sarabsin

‎04-12-2018 09:26 AM

The issue is resolved now!

 

It was APIC-3 in POD-2 was not reset.

Its seems its very important that all spine/leafs in POD-2 should be provisioned before doing a setup of APIC-3 in POD-2 otherwise Leafs become inactive.

0 Helpful
Customers Also Viewed These Support Documents

Review Cisco Networking for a $25 gift card

Save 25% on Day-2 Operations Add-On License