12-10-2008 12:04 PM - edited 03-06-2019 02:54 AM
hi all,
our remote site router was not reachable.
after 30 mins it came back up.
ss-eb643r1 uptime is 12 weeks, 1 day, 23 hours, 50 minutes
System returned to ROM by power-on
System restarted at 15:12:57 CDT Mon Sep 15 2008
System image file is "flash:c2600-is-mz.121-8.bin"
it was not power issue.
i chec
*Feb 28 18:03:11: %AAAA-3-DROPACCTSNDFAIL: accounting record dropped,send to server failed: system-start
*Feb 28 18:07:25: %LINK-3-UPDOWN: Interface Serial0/0, changed state to up
*Feb 28 18:07:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to up
ss-eb643r1# sh clock
14:02:50.888 CST Wed Dec 10 2008
ss-eb643r1#sh clock
k the logs
during this 30 mins router was not pingable.
i check the eigrp nei
ss-eb643r1#sh ip eigrp nei
IP-EIGRP neighbors for process 64520
H Address Interface Hold Uptime SRTT RTO Q Seq Type
(sec) (ms) Cnt Num
0 172.20.18.25 Se0/0.100 13 00:09:51 676 4056 0 949039
does anyomne know what has happened
many thanks
mahesh
Solved! Go to Solution.
12-10-2008 12:56 PM
A routing update won't break connectivity. If the circuit goes down, that's another story.
12-10-2008 12:11 PM
Based on the information provided, no - we don't know what happened.
The log is from February 28 so it does not tell us anything and the router has been up for 12 weeks.
It could've been anything.
___
Edison.
12-10-2008 12:34 PM
Hi Edison,
so my question is if any routing protocol
like eigrp ,ospf ,bgp have neighbour refresh
can that can take circuit down?
many thanks
12-10-2008 12:56 PM
A routing update won't break connectivity. If the circuit goes down, that's another story.
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: