Multiple ports of multiple cards bouncing randomly on a 6500

kevinzhang · ‎09-22-2006

A couple months ago, on one of my 6500 switch, ports start bouncing randomly. It happened to all the line modules. Here I am including a portion of log from the switch.

Sep 22 04:02:48.479 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/37, changed state to down

Sep 22 04:02:49.935 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/37, changed state to up

Sep 22 04:02:55.855 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/11, changed state to down

Sep 22 04:02:56.063 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/16, changed state to down

Sep 22 04:02:57.891 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/11, changed state to up

Sep 22 04:02:59.379 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/16, changed state to up

Sep 22 04:03:02.311 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/4, changed state to down

Sep 22 04:03:05.471 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/2, changed state to down

Sep 22 04:03:06.155 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/4, changed state to up

Sep 22 04:03:09.311 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/2, changed state to up

Sep 22 04:57:12.943 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/39, changed state to down

Sep 22 04:57:16.167 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/39, changed state to up

Sep 22 04:57:28.311 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/39, changed state to down

Sep 22 04:57:31.235 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/39, changed state to up

Sep 22 04:58:41.176 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/39, changed state to down

Sep 22 04:58:42.368 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/39, changed state to up

Sep 22 05:00:35.417 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/48, changed state to down

Sep 22 05:00:37.133 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/48, changed state to up

Sep 22 05:00:47.753 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/48, changed state to down

Sep 22 05:00:49.361 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/48, changed state to up

Sep 22 05:01:40.285 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/48, changed state to down

Sep 22 05:01:43.205 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/48, changed state to up

Sep 22 05:30:33.899 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2/11, changed state to down

Sep 22 05:30:52.627 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2/11, changed state to up

Sep 22 07:58:22.202 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/8, changed state to down

Sep 22 08:00:44.755 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/8, changed state to up

Sep 22 08:02:35.848 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/8, changed state to down

Sep 22 08:02:38.808 edt: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/8, changed state to up

The frequency of this random bouncing changes from hours to days. There are also some indications that certain ports were bouncing at certain specific time. But, the generally speaking, there is no pattern of these bouncing.

By the way, this switch was running for a couple of years before this happened recently.

Anyone out there has seen similar case like this? Thank your for any suggestion on solving this issue.

thomas.chen · ‎09-28-2006

There could be multiple causes for this.It might be a failure with Hardare itself.Sometimes upgraing the IOS image can help fix this problem.Even if the memory is insufficient this would happen.So try upgrading the RAM.

dabels · ‎09-28-2006

what kind of switch is it? did the logging level chage when you started to see this? this could be just normal people rebooting machines? if you have starte some process to push out patches that require reboots to mahines this could cause this type of message output. have you gone to the device on the ports and checked them out?