topic Some reasons that could cause in Network Security

ASA Failover

timwall01 — Tue, 12 Mar 2019 06:17:02 GMT

We have a pair of 5515 in active/failover.

There is a subinterface inside interface which on the primary ASA shows as Normal, but failed on the Standby. From 'show failover' command

If we access the standby ASA and run the 'show failover' command the same inside interface shows as Normal on the Active and standby.

So why on the primary FW is the inside interface showing as failed on the output of the 'show failover' command on the standby ASA

Some reasons that could cause

Karsten Iwen — Fri, 17 Jul 2015 17:44:54 GMT

Some reasons that could cause this behavior are unidirectional communication or duplicate IP addresses.

Enable "debug icmp trace" and ping the other side to see if your pings reach the other side.

I did try to ping but failed

timwall01 — Fri, 17 Jul 2015 18:47:15 GMT

I did try to ping but failed to respond.

debug showed that pings are

timwall01 — Fri, 17 Jul 2015 18:57:36 GMT

debug showed that pings are not being responded too

It's very likely that your

Karsten Iwen — Fri, 17 Jul 2015 19:36:05 GMT

It's very likely that your problem is caused in your infrastructure and is unrelated to the ASA. Continue troubleshooting the complete way from the primary to the secondary ASA.