penguinroundup
MIS
Hi,
Last night I upgraded my IOS on my 2821 router to a later train that will support MPLS networks (which we are migrating to in the near future). This morning, two of my 3 serial interfaces have started flapping up & down. Here's an excerpt from my syslog server:
07-12-2005 09:51:34 Local7.Notice 192.168.14.10 70: *Jul 12 14:44:25.789 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up
07-12-2005 09:51:31 Local7.Error 192.168.14.10 69: *Jul 12 14:44:22.789 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to up
07-12-2005 09:51:29 Local7.Notice 192.168.14.10 68: *Jul 12 14:44:20.789 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up
07-12-2005 09:46:12 Local7.Notice 192.168.14.10 67: *Jul 12 14:39:03.997 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down
07-12-2005 09:46:12 Local7.Error 192.168.14.10 66: *Jul 12 14:39:02.997 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to down
07-12-2005 09:46:10 Local7.Notice 192.168.14.10 65: *Jul 12 14:39:00.997 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (10 SES)
07-12-2005 09:29:49 Local7.Notice 192.168.14.10 64: *Jul 12 14:22:40.665 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up
07-12-2005 09:29:46 Local7.Error 192.168.14.10 63: *Jul 12 14:22:37.665 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to up
07-12-2005 09:29:44 Local7.Notice 192.168.14.10 62: *Jul 12 14:22:35.665 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up
07-12-2005 09:29:41 Local7.Notice 192.168.14.10 61: *Jul 12 14:22:33.625 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down
07-12-2005 09:29:41 Local7.Error 192.168.14.10 60: *Jul 12 14:22:32.625 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to down
07-12-2005 09:29:39 Local7.Notice 192.168.14.10 59: *Jul 12 14:22:30.625 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (LOF detected)
This IOS was provided to me by Cisco TAC support, and I double-checked it myself, so I know it's a valid image for my router. I am working w/ Cisco tech support on this, and so far he hasn't found anything suspicious.
I ran a hardware loopback test on my free serial interface, and it didn't do so hot, only about 80% of the pings got a reply. I am going to test my other interfaces after hours.
What the he!! is going on with this thing??? About 2 weeks ago, I tried upgrading the IOS to a different image (again, provided by Cisco tech support), and the exact same thing happened. We wound up plugging in our old 2610 router in a panic because the ports were flapping up & down constantly. I also had our ISP test our circuits, and they came back OK.
Sorry this is such a long post, but this is really aggravating!! Something really strange is going on here. TIA for any advice/suggestions!!!
Last night I upgraded my IOS on my 2821 router to a later train that will support MPLS networks (which we are migrating to in the near future). This morning, two of my 3 serial interfaces have started flapping up & down. Here's an excerpt from my syslog server:
07-12-2005 09:51:34 Local7.Notice 192.168.14.10 70: *Jul 12 14:44:25.789 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up
07-12-2005 09:51:31 Local7.Error 192.168.14.10 69: *Jul 12 14:44:22.789 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to up
07-12-2005 09:51:29 Local7.Notice 192.168.14.10 68: *Jul 12 14:44:20.789 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up
07-12-2005 09:46:12 Local7.Notice 192.168.14.10 67: *Jul 12 14:39:03.997 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down
07-12-2005 09:46:12 Local7.Error 192.168.14.10 66: *Jul 12 14:39:02.997 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to down
07-12-2005 09:46:10 Local7.Notice 192.168.14.10 65: *Jul 12 14:39:00.997 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (10 SES)
07-12-2005 09:29:49 Local7.Notice 192.168.14.10 64: *Jul 12 14:22:40.665 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up
07-12-2005 09:29:46 Local7.Error 192.168.14.10 63: *Jul 12 14:22:37.665 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to up
07-12-2005 09:29:44 Local7.Notice 192.168.14.10 62: *Jul 12 14:22:35.665 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up
07-12-2005 09:29:41 Local7.Notice 192.168.14.10 61: *Jul 12 14:22:33.625 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down
07-12-2005 09:29:41 Local7.Error 192.168.14.10 60: *Jul 12 14:22:32.625 UTC: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to down
07-12-2005 09:29:39 Local7.Notice 192.168.14.10 59: *Jul 12 14:22:30.625 UTC: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (LOF detected)
This IOS was provided to me by Cisco TAC support, and I double-checked it myself, so I know it's a valid image for my router. I am working w/ Cisco tech support on this, and so far he hasn't found anything suspicious.
I ran a hardware loopback test on my free serial interface, and it didn't do so hot, only about 80% of the pings got a reply. I am going to test my other interfaces after hours.
What the he!! is going on with this thing??? About 2 weeks ago, I tried upgrading the IOS to a different image (again, provided by Cisco tech support), and the exact same thing happened. We wound up plugging in our old 2610 router in a panic because the ports were flapping up & down constantly. I also had our ISP test our circuits, and they came back OK.
Sorry this is such a long post, but this is really aggravating!! Something really strange is going on here. TIA for any advice/suggestions!!!
