11-23-2019 09:34 AM
11-23-2019 09:56 AM
We do not have much information about your situation to help us identify the issue. You have told us that there is a 4331 router, an ASA, and an ISP. Is the connection to the ISP to the ASA or to the 4331?
I find this part of your post especially interesting "The problem I have is that not only is the link to the firewall going down, so is the link to the ISP." Could you tell us more about this? How do you detect the interfaces going down?
Is it possible to get any diagnostic information while the problem is happening? I assume that you are not on site, but is there anyone who would be able to execute some commands and gather some output to help identify the issue? Otherwise we may need to depend on what shows up in the logs. Could you send us some of the logs? (the first group of lines of output from the command show log contains information about how logging is set up and this might be helpful - as well as some of the log messages)
HTH
Rick
11-23-2019 01:01 PM
Richard,
Thank you for the quick reply.
Sorry about not explaining the topology properly. Its easy to forget when all my locations are identical and usually don't talk to anyone else but co-workers about it.
In text I'll try and describe it first. I'm sure it will make sense but I can create a quick graphic of it.
AT&T internet comes in on fiber, they have a Ciena switch on site which then connects to my Cisco router on interface 0/0. On that same Cisco router interface 0/1 connects to the Cisco ASA firewall on port 0/1. Beyond that there are just normal switches etc.
So, for PRTG network monitor it uses what they call sensors. SNMP data is requested from the router and is display in the sensors I setup. I monitor bandwidth usage of the router for ports 0/0 and 0/1, but it uses the IP of the interface of 0/1 connected to the firewall. The flaw in doing it this way is that it doesn't guarantee when it says the router is down that it doesn't always mean the ISP is down, because if the firewall is off or down then the link is down which takes down the IP that I monitor. Its a false positive for being down. The ping part of it is that the PRTG system just pings it on an interval to keep an eye on the uptime of the router. As for being down in general, PRTG tells me its down when it stops getting a response for 30 seconds. So, that could mean several things are wrong and that is why I added another PRTG monitor for the IP of interface 0/0 which connects only to the ISP. SO, now that I monitor both I can determine a few things; at least I think. So, my thought is that if the firewall is getting tanked by scans and stops responding or the interface goes down, then my interface 0/1 is down. However, since I now monitor 0/0 it shouldn't necessarily go down too. This is why I now think there is something either A attacking the router or B something is wrong with my router.
You're right, I am not physically there. I would love to see if the links go down, or if consoled into the router if it freezes up or anything that would be helpful, or nothing happens. My plan was to go there Monday morning to see it in person and have a spare router to put in place to see if it stops. Just for a hard test to eliminate the Cisco router. If it still happens with a different router in place then that excludes this router as a culprit here.
Here is the show log that I did get. I'll have to get the top of the command so you can see how its configured.
.1 is the router leading out to the internet, .10 is the router in question. This is a WAN running OSPF, I didn't include that in the description of how things were connected. I'm not 100% sure if this is the cause or a result of links going down and loosing access to the internet etc. My best guess is this the reaction to packet/link loss.
Thanks!
Mike
11-23-2019 01:26 PM
Richard,
Below is the top of the show log output.
Syslog logging: enabled (0 messages dropped, 10 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level critical, 0 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 3663 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 3663 message lines logged
Logging to 207.75.162.11 (udp port 514, audit disabled,
link up),
3662 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging Source-Interface: VRF Name:
GigabitEthernet0/0/0.74
Mike
11-24-2019 08:06 PM
Mike
Thanks for the additional information. The top part of show log does confirm that logging buffered is capturing all log messages (logging level is debugging). So we should be able to see anything that the router is logging. From the original description of the symptoms I thought that it might be an issue with an interface doing down, then back up, then down again, and back up again. But there do not seem to be any messages about interfaces changing state.
I am a bit puzzled about an aspect of these log messages. All of these log messages relate to a subinterface of gig0/0/0.74, which I believe you describe as the connection to the ISP. But there seem to be 2 OSPF neighbors. What is the second neighbor?
Are you doing any monitoring of the ASA? If so does it appear to be stable (and consistently available)? Or does it show some loss of connectivity?
I am not clear from your description whether you are doing monitoring of the interface connecting the router to the ASA. Can you clarify this?
HTH
Rick
11-23-2019 02:13 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide