Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

ASA 5515 Empty Routing Table

We have an odd issue which began by being unable to remotely connect to the ASA via ASDM or SSH.  SSH prompts for username and password, but returns 'access denied' even when using the correct password.  Logging into the console to troubleshoot, we find that the routing table is empty despite have multiple static routes in the config.  Re-adding a route helps not at all.  Attempt to ping something on the inside returns 'no route to host'.  Even the connected interfaces are not showing in the routing table.

Oddly, the firewall is functioning and passing traffic.  It has been rebooted at least once since this problem began.  No changes between the time this was working and when it started.

The firewall is an ASA-5515X running 8.4.6.

Anyone else seen this issue?

 

 

 

3 REPLIES
Super Bronze

Hi, Can't say that I have

Hi,

 

Can't say that I have ever seen this happen.

 

Are you saying that the "show route" doesnt show any output?

 

Its kind of strange that a reboot would have not helped with this situation at all. Even more strange is the fact that you are saying that its passing traffic normally. Starts sounding like something you need help from Cisco TAC possibly.

 

Actually, now that I read your post, are you sure you are running 8.4(6). To my understanding your ASA model (the new X-series except for the ASA5585-X models) dont support that software.

 

Here is the list and it indeed does list that its not supported on your hardware

http://www.cisco.com/c/en/us/td/docs/security/asa/compatibility/asamatrx.html

 

So if for some odd reason you are actually running this software then I would probably suggest upgrading the software and considering the nature of the problem set a side a long enough maintanance window incase something doesnt go quite as expected.

 

Though I would assume you just mistaken the software level?

 

Other than that I would probably check the current configuration and an older backup on separate text documents and compare possible differences. For example using Microsoft Word or something else that can easily compare the 2 different texts for differences.

 

Hope this helps :)

 

- Jouni

New Member

Thanks for the response.  The

Thanks for the response.  The local tech on-site had the console cable plugged into the wrong (old) firewall :D.

 

Check layer 1 first still applies.....

 

 

Super Bronze

Hi, Good to hear :)I guess

Hi,

 

Good to hear :)


I guess you could also call it a Layer 8 problem ;)

 

- Jouni

142
Views
0
Helpful
3
Replies