Timeline for Cisco ASA 5505 stop passing traffic randomly
Current License: CC BY-SA 3.0
Post Revisions
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2017 at 5:50 | comment | added | Ron Maupin♦ | Did any answer help you? if so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. | |
| Sep 6, 2015 at 11:02 | comment | added | Chris Balmer | awesome, glad to hear it and thanks for posting the resolution | |
| Sep 6, 2015 at 7:41 | answer | added | Maxim | timeline score: 3 | |
| Sep 6, 2015 at 7:39 | comment | added | Maxim | The issue has been resolved! I have tried to analyze non-working hosts arp tables and found ASA's mac address change. Decreased ASA's log verbosity to Warning level, rebooted it and got a message during boot IP address collision detected between host 192.168.0.1 at f80f.4197.a18d and interface inside, So found host with the MAC noted. Despite it has different IP address and it is separate point to investigate, host's disconnection immediately resolves the issue. | |
| Sep 5, 2015 at 16:45 | comment | added | Maxim | @ChrisBalmer Here is it: pastebin.com/VZNaLG3U | |
| Sep 5, 2015 at 12:58 | comment | added | Chris Balmer |
Also when the problem is occurring try running packet-tracer input inside tcp <ip of computer having trouble> 8000 8.8.8.8 80 detailed and post that output.
|
|
| Sep 5, 2015 at 12:51 | comment | added | Chris Balmer | Looking through the log now. Next time it happens can you post the arp table for the inside interface? | |
| Sep 5, 2015 at 12:50 | comment | added | Maxim |
Just got it again only a few mins after log paste, still nothing unusual in the log, but tried to clear not a whole ARP, but clear arp inside - worked perfectly.
|
|
| Sep 5, 2015 at 12:39 | comment | added | Maxim | @ChrisBalmer, added pastebin.com/3CqXGtuk | |
| Sep 5, 2015 at 12:33 | history | edited | Maxim | CC BY-SA 3.0 |
show logging added
|
| Sep 5, 2015 at 12:11 | comment | added | Maxim | Done, waiting for the issue. I googled a lot and licensing is the first I checked... Thanks! | |
| Sep 5, 2015 at 11:51 | comment | added | Chris Balmer | That rules out my initial thought about limited inside hosts. Can you add 'logging buffered debug' and 'logging buffer-size 52000' to your config? Then when it happens again, do a show logging and post the logs from a couple min before the problem started until you ran the command? | |
| Sep 5, 2015 at 11:44 | comment | added | Maxim | Sure, done it in the main post | |
| Sep 5, 2015 at 11:43 | history | edited | Maxim | CC BY-SA 3.0 |
added 3011 characters in body
|
| Sep 5, 2015 at 11:41 | review | First posts | |||
| Sep 5, 2015 at 15:54 | |||||
| Sep 5, 2015 at 11:39 | comment | added | Chris Balmer | Can you post show version? | |
| Sep 5, 2015 at 11:27 | history | asked | Maxim | CC BY-SA 3.0 |