09-16-2013 09:54 AM - edited 03-11-2019 07:39 PM
Correction: SLA had nothing to do with the issue.
I have a customer with a ASA 5505 runing 8.2(5) with a T1 in 0/0 and a wireless connection in 0/1 with SLA setup on 0/0 route to failover to 0/1 route. The wireless connection will go up and down but when this happens it causes a disruption in service on 0/0. I removed the SLA and disabled 0/1 and it has been fine since.
Any help is much appreciated!
~Chad
Solved! Go to Solution.
09-17-2013 02:41 PM
Hello Chad,
Time to open a case with TAC so we can decode the Core Dump.
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-16-2013 10:18 AM
Hello Chad,
So Interface 0/0 is the primary and 0/1 is the secondary.
Then if the secondary fails it should not affect the internet connection as the primary is still up.
Do you have logs from the time of event?
Can you share the running-configuration?
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-16-2013 10:22 AM
This is what I see in the log file:
Sep 12 2013 10:34:10: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:34:10: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:34:10: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:37:38: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:37:38: %ASA-4-411002: Line protocol on Interface out-Vz, changed state to down
Sep 12 2013 10:37:38: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:37:50: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:37:50: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:37:50: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:38:20: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:38:20: %ASA-4-411002: Line protocol on Interface out-Vz, changed state to down
Sep 12 2013 10:38:20: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:38:32: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:38:32: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:38:32: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:41:38: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:41:38: %ASA-4-411002: Line protocol on Interface out-Vz, changed state to down
Sep 12 2013 10:41:38: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:41:51: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:41:51: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:41:51: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:42:21: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:42:21: %ASA-4-411002: Line protocol on Interface out-Vz, changed state to down
Sep 12 2013 10:42:21: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:42:31: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:42:31: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:42:31: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:45:29: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:45:29: %ASA-4-411002: Line protocol on Interface out-Vz, changed state to down
Sep 12 2013 10:45:29: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:45:39: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:45:39: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:45:39: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:46:11: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:46:11: %ASA-4-411002: Line protocol on Interface out-Vz, changed state to down
Sep 12 2013 10:46:11: %ASA-4-411002: Line protocol on Interface Ethernet0/1, changed state to down
Sep 12 2013 10:46:21: %ASA-4-411001: Line protocol on Interface out-Vz, changed state to up
Sep 12 2013 10:46:21: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
Sep 12 2013 10:46:21: %ASA-4-411001: Line protocol on Interface Ethernet0/1, changed state to up
09-16-2013 10:30 AM
Hello Chad,
Is out-Vz the primary one (eth 0/0)?
Can you enable higher loggin level information so we can see a detail logs from the events?
Can you share the configuration (Make the right changes to IP addresses, etc so you can hide the real values)
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-16-2013 10:35 AM
out vz is 0/1 secondary
09-16-2013 10:39 AM
I would have to turn the interface back on for the logging to do any good...and that will cause issues.
09-16-2013 10:34 AM
09-16-2013 10:54 AM
Hello Chad,
I do not see anything related to SLA on the config you attached.
Did you remove it?
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-16-2013 10:57 AM
Yes I had to remove it. I am trying to get permission to turn it back on so I can get some logging detail.
Even if I turned SLA off it would still cause an outage so I had to disable the 0/1 interface to get it to stop.
09-16-2013 11:18 AM
Based on the configuration I cannot find a line of code that could be causing this weird issue,
On the logs you post I can see the backup interface flapping but nothing related to the primary.
Do you know why is the backup interface flapping that much?
What happens when you have both links up and running and you ping from the ASA to 4.2.2.2 via the Primary link?
What's the status of the primary interface when both interfaces are up?
We definetly need some more information to fix this,
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-17-2013 11:13 AM
09-17-2013 11:20 AM
Hello Chad,
What do U mean by started running fine for a while?
I can see the interface backup is still flapping.
Do you still see the problem with the internet access?
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-17-2013 12:20 PM
I mean I turned the wireless back on and setup the SLA and it ran with no issues for awhile. I turned it SLA and 0/1 back off and it has happened again. SO, I guess I was looking in the wrong place. Just so happened that losing internet connectivity would coinside with the flapping.
Welcome back to square one
09-17-2013 01:44 PM
The ASA is rebooting and I am seeing coredump files.
09-17-2013 02:41 PM
Hello Chad,
Time to open a case with TAC so we can decode the Core Dump.
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: