07-08-2018 06:47 PM - edited 03-01-2019 05:35 AM
Good day
I'm setup up the inband management and pump into issue that APIC is not able to ping to any SPINE node but only leaf nodes via the inband management.
I had follow below link to specific the source interface on APIC in order to ping SPINE however still not pingable.
Testing:
A simple ping to a spine switch will fail if it generates an ARP request, because spine switches do not respond to ARP requests. When pinging a spine switch from APIC, you must specify the source interface/address so that APIC does not send an ARP request.
Have anyone have the experience on inband management and face similar issue? Anyway could make it reachable.
Thank you
MK
Solved! Go to Solution.
07-10-2018 01:56 AM
The workaround is to specify the source IP address when execute ping, and now the SPINE is reachable from APIC.
ping -I (SPINE IP) (destination IP), example as below.
APIC1#ping 172.0.0.129 -I 172.0.0.122
PING 172.0.0.129 (172.0.0.129) from 172.0.0.122 : 56(84) bytes of data.
64 bytes from 172.0.0.129: icmp_seq=1 ttl=63 time=0.196 ms
64 bytes from 172.0.0.129: icmp_seq=2 ttl=63 time=0.190 ms
07-10-2018 01:56 AM
The workaround is to specify the source IP address when execute ping, and now the SPINE is reachable from APIC.
ping -I (SPINE IP) (destination IP), example as below.
APIC1#ping 172.0.0.129 -I 172.0.0.122
PING 172.0.0.129 (172.0.0.129) from 172.0.0.122 : 56(84) bytes of data.
64 bytes from 172.0.0.129: icmp_seq=1 ttl=63 time=0.196 ms
64 bytes from 172.0.0.129: icmp_seq=2 ttl=63 time=0.190 ms
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide