It is highly unlikely that crypto (or not crypto) has anything to do with this issue. I suspect that the issue is that to get to 172.16.100.1 you must go through the firewall at 10.10.40.2. I suspect that the firewall is not allowing the ping to go through. Can you check on the firewall and see if it sees the ping? And if it sees the ping does it permit it through or does it deny the ping?
I have the firewall to allow "any any" between the two interfaces, I can ping the serial interfaces and even the distant Gi interface, from one firewall I can even ping the interface on the firewall, Just not through )10.10.40.1 and 10.10.40.2) going the other way, I can only ping 10.10.30.1. I am befuddles.
There is no routing issue on these routers as the routes are properly configured , also there are no access lists to block any traffic .
You mentioned that you cannot ping 30.2 interface of firewall , there could be either routing issue or firewalls are not properly configured to handle the traffic.Are these cisco based firewalls PIX or ASA ? Can you post firewall configs?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...