Guest

Preview Tool

Cisco Bug: CSCsy89178 - ASA - Unable to ping the backup interface used in SLA.

Last Modified

Mar 11, 2017

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases

8.0(4)

Description (partial)

Symptom:

Pinging the backup interface on the ASA with SLA configured will produce the following syslog message and the pings will fail.

%ASA-6-110003: Routing failed to locate next hop for icmp
Conditions:

ASA with a backup interface and SLA configured. Ping destined to the backup interface will fail and produce the following log message. 

"Routing failed to locate next hop for icmp".

SSH/Telnet to the backup interface works fine with the return packets being sent out the interface specified in the default route.

Related Community Discussions

ASA 5505 Dual WAN - Ping inactive wan from outside?
I currently have some small branch offices using ASA 5505 with Security Plus license and dual wan connections. They are configured wil an sla monitor so if the primary WAN goes down the secondary connection becomes active. This works as expected, however... I can't ping the non-active interface from an outside source. I beleive this is by design or due to some limitation on the 5505. The problem is that I don't know if the backup WAN connection is functioning normally without forcing the ASA to make ...
Latest activity: Sep 14, 2017
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.