cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
420
Views
0
Helpful
1
Replies

ACI new pod, spine failed to ping

HenrikHansen87
Level 1
Level 1

Good Evening,

we just deployed 2 new ACI Pods in our existing multipod environment. We see for every new spine a F1360 ->
topology/pod-4/node-142/sys/coop/inst/dom-overlay-1/oracle-[100.67.0.64/32] Operational state is down, reason:Route not reachable. After checking, we found out, that the the ospf network is distributing the ptap addresses, but the spine is not adding the route to his routing table.

SPINE131 - Ptap 100.66.208.64
SPINE132 - Ptap 100.66.208.65

On Spine131:
SPINE131# show ip ospf route 100.66.208.65/32 vrf overlay-1
OSPF Process ID default VRF overlay-1, Routing Table
(D) denotes route is directly attached (R) denotes route is in RIB
100.66.208.65/32 (intra) area backbone
via 172.31.245.84/Eth1/57.57 , cost 2 distance 110

SPINE131# show ip route 100.66.208.65/32 vrf overlay-1
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>

Route not found




1 Reply 1

M02@rt37
VIP
VIP

Hello @HenrikHansen87 

Do you check distribution route filters (If you have it) to see if anything is blocking the distribution of ptap routes ?

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card