This weeks Tips & Tricks is going to be talking about pinging in the firewall CLI, as there can sometimes be confusion and/or issues that arise when trying to ping from the CLI on the Palo Alto Networks firewall.
Let's start off with the basics.
Due to the nature of the Palo Alto Networks firewalls, you have two "planes" of existence: the Management Plane (MP) and the Data Plane (DP). You have the ability to use the Ping command from both depending on how you use the Ping command.
From the MP, you can use the following command to ping a single IP address using the Management Interface IP:
>ping host x.x.x.x
Ping command using the Management interface
From the DP, you can use the following command to use an interface that owns ip y.y.y.y on the firewall to source the Ping command from:
>ping source y.y.y.y host x.x.x.x
Why is this helpful?
You can use this command to help troubleshoot latency and connectivity issues from the management interface to hosts internal or external to your firewall. This is especially nice, as you have the ability to change what your source IP address is.
Common issue 1:
In the event that you receive an error "bind: Cannot assign requested address" on firewall when sourcing ping from any interface other than the management interface, then the cause may be as simple as a checkbox.
Please check the physical interface configuration to ensure that the "untagged subinterface" checkbox is NOT checked.
Common issue 2: Panorama
The ping command only works from the local firewall device, as panorama does not have dataplane interfaces, so you can't add the source from panorama either.
To be able to run the ping from a firewall, you need to connect to the firewalls' CLI.
I want to give a shout out to @reaper for help with this weeks blog, as I used information he has posted to help create this blog.
I hope this helps everyone out with the use of Ping with the Palo Alto Networks Firewall.
Thanks for taking time to read my blog. If you enjoyed this, please hit the Like (thumb up) button, don't forget to subscribe to the LIVEcommunityBlog area.
As always, we welcome all comments and feedback in the comments section below.