How to use iPing on Cisco ACI

iPing allows you to test reachability from the ACI Nodes (Leafs & Spines) in the different VRFs

Home / Posts / How to use iPing on Cisco ACI

Overview

For troubleshooting and to better understand the network and it’s behaviour, it’s always handy to have access to Ping. On the ACI devices there is a regular Ping as well, but it’s limited to the management VRF. So for troubleshooting in the underlay, with l3 outs, in customer VRFs and so on, you can leverage iPing in Cisco’s ACI.

iPing allows you to ping directly from your Leafs, into the Overlay networks that are connected to them.

iPing

Thankfully there isn’t too much of a difference from a regular Ping to iPing. What you need to know is the VRF you want to ping in. The correct name (Cisco stitches the tenant + VRF together) can be obtained through show vrf.

1
2
3
4
5
6
SPINE101# show vrf
 VRF-Name                           VRF-ID State    Reason
 black-hole                              3 Up       --
 management                              2 Up       --
 mgmt:inb                                5 Up       --
 overlay-1                               4 Up       --

The output looks like that, in a production fabric you will probably have a bit more VRFs. Let’s assume we want to ping in the overlay-1 VRF, which is used for the communication between all the ACI nodes.

Basic syntax is iping -V <VRF> <IP>, example iping -V overlay-1 100.111.184.65. Just remember the capital -V and you are good to go with iPing :)

Full output:

1
2
3
4
5
SPINE101# iping -V overlay-1 100.111.184.65
PING 100.111.184.65 (100.111.184.65) from 100.111.184.66: 56 data bytes
64 bytes from 100.111.184.65: icmp_seq=0 ttl=63 time=0.357 ms
64 bytes from 100.111.184.65: icmp_seq=1 ttl=63 time=0.359 ms
64 bytes from 100.111.184.65: icmp_seq=2 ttl=63 time=0.292 ms

More options with iPing

There are additional options as well. -c, -i, -F and -s can be helpful to do advanced troubleshooting.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
usage: iping     [ -d    set the SO_DEBUG option]
                 [ -D    enable debug information ]
                 [ -F    enable do not fragment bit in IP header ]
                 [ -L    receive packets on supplied interface ]
                 [ -n    enable printing host IP address than resolved name ]
                 [ -q    quiet output ]
                 [ -r    disable routing of the packets, send only to directly connected hosts ]
                 [ -v    output in verbose format ]
                 [ -V    <vrf-name>      name of the VRF through which destination is reachable ]
                 [ -c    <count>         no of packets to send ]
                 [ -i    <wait>                  no of seconds to wait before sending next packet ]
                 [ -p    <pattern>       packet payload pattern ]
                 [ -s    <packetsize>    size of packets to send ]
                 [ -t    <timeout>       wait for seconds to receive reply ]
                 [ -S    <source ip/interface>   send packet with given source-ip or IP of given interface and
                                                 send packet out of that interface ]
                 <host>  destination host-name or ip address
comments powered by Disqus
Built with Hugo
Theme Stack designed by Jimmy