cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4926
Views
5
Helpful
7
Replies

WS-C2960x %LINEPROTO-5-UPDOWN

eduardo.oropeza
Level 1
Level 1

Does anyone have a explanation for this problem. Since these model switches were introduced to our network, logs report a never-ending Up-Down on random interfaces. I included a screen shot of the log under body message. I found this reference in cisco to a bug in the OS that suggests  a fix by running this work around:

Workaround:
Disable Energy-Efficient Ethernet (EEE) by below CLI command:
2960X(config-if)#no power efficient-ethernet

Even though the described bug matches my symptoms the workaround did not solve the problem. Any suggestions or help is appreciated thanks. 

 

 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCus35889/?referring_site=bugquickviewclick

 

Log Buffer (4096 bytes):
N: Line protocol on Interface GigabitEthernet1/0/28, changed state to up
049334: Apr  9 08:13:33.300 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049335: Apr  9 08:13:34.303 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17,
049336: Apr  9 08:13:41.861 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17,
049337: Apr  9 08:13:42.860 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049338: Apr  9 08:14:33.663 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049339: Apr  9 08:14:34.670 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17,
049340: Apr  9 08:14:41.346 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17,
049341: Apr  9 08:14:42.349 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049342: Apr  9 08:15:11.508 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049343: Apr  9 08:15:12.508 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33,
049344: Apr  9 08:15:19.391 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33,
049345: Apr  9 08:15:20.390 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049346: Apr  9 08:15:27.787 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049347: Apr  9 08:15:28.790 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6, c
049348: Apr  9 08:15:29.510 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface G
049349: Apr  9 08:15:30.513 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/9,
049350: Apr  9 08:15:35.271 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049351: Apr  9 08:15:35.631 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6,
049352: Apr  9 08:15:36.274 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/34,
049353: Apr  9 08:15:36.634 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049354: Apr  9 08:15:37.350 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/9,
049355: Apr  9 08:15:38.353 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049356: Apr  9 08:15:42.992 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/34,
049357: Apr  9 08:15:43.995 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049358: Apr  9 08:21:34.089 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049359: Apr  9 08:21:35.089 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28,
049360: Apr  9 08:21:42.049 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28,
049361: Apr  9 08:21:43.052 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049362: Apr  9 08:43:09.138 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049363: Apr  9 08:43:10.144 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/30,
049364: Apr  9 08:43:17.055 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/30,
049365: Apr  9 08:43:18.058 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049366: Apr  9 08:44:40.579 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface
049367: Apr  9 08:44:41.582 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/30,
049368: Apr  9 08:44:48.419 U: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/30,
049369: Apr  9 08:44:49.422 U: %LINEPROTO-5-UPDOWN: Line protocol on Interface

1 Accepted Solution

Accepted Solutions

Thanks for the tip, today I will go the site where I will test the IOS upgrade fix and will report back the results later this afternoon. I will first try to apply the suggested released IOS from cisco. Its the next release from the build were running. 

 

c2960x-universalk9-mz.152-4.E7.bin

View solution in original post

7 Replies 7

luis_cordova
VIP Alumni
VIP Alumni

Hi @eduardo.oropeza ,

 

What is your IOS version?
Have you tried updating your IOS?

 

Regards

IOS - c2960x-universalk9-mz.152-2.E.bin

 

I have not tried that yet I suppose I could see if there is a more current version. Thanks for the idea. 

I would not recommend using version "0" of 15.2(2)E.
Upgrade the firmware of the switch first and see if there are any improvements.

Thanks for the tip, today I will go the site where I will test the IOS upgrade fix and will report back the results later this afternoon. I will first try to apply the suggested released IOS from cisco. Its the next release from the build were running. 

 

c2960x-universalk9-mz.152-4.E7.bin

Deepak Kumar
VIP Alumni
VIP Alumni

Hi,

I hope you verified everything on remote end. If there is no issue then try to upgrade the ios

Regards,
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!

cmarva
Level 4
Level 4

by default, interface status logging is enabled, so you will see these every time someone shuts down for the day, or any time the connected device reboots. You can stop this by entering "no logging event link-status" on the interfaces, typically only end user interfaces. Ports that have APs, interswitch links, etc. (IE-important ports) you'd typically want to leave this enabled.

Yes I understand the status logging however having interfaces go up/down repeatedly seconds apart for the whole day is not normal behavior. I have tracked down some of the end devices connected to these problem ports and they could be anything. From IP phones, desktops, printers, the behavior does not replicate to one specific device. And other model switches 3560x in same IDF do not produce that behavior.

Review Cisco Networking for a $25 gift card