Interface goes up and down

[Moudar]

I got many users complaining that they are loosing the connection very often.

Here is the logging!

From one switch which shows what happens, the same port is going up and down many times and it is not about one switch or one user. I have checked many switches that are located in different buildings and these had same kind of logs!

the port is going down for like 2 seconds and up again why is this happening

Switches i checked are:

WS-C2960-24TC-L

C9200L-24P-4G

The port's config is as follows:

interface GigabitEthernet0/1
switchport access vlan 533
switchport mode access
media-type rj45
spanning-tree portfast

001605: Jun 16 10:34:53 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001606: Jun 16 10:34:54 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001607: Jun 16 10:50:46 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001608: Jun 16 10:50:47 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001609: Jun 16 10:50:50 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001610: Jun 16 10:50:51 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001611: Jun 16 12:44:32 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001612: Jun 16 12:44:33 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001613: Jun 16 12:44:35 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001614: Jun 16 12:44:36 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001615: Jun 16 13:15:58 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001616: Jun 16 13:15:59 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001617: Jun 16 13:16:02 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001618: Jun 16 13:16:03 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001619: Jun 16 13:51:03 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001620: Jun 16 13:51:04 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001621: Jun 16 13:51:07 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001622: Jun 16 13:51:08 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001623: Jun 16 14:05:14 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001624: Jun 16 14:05:15 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001625: Jun 16 14:05:18 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001626: Jun 16 14:05:19 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001627: Jun 16 14:32:34 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001628: Jun 16 14:32:35 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001629: Jun 16 14:32:38 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001630: Jun 16 14:32:39 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001631: Jun 16 14:42:33 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001632: Jun 16 14:42:34 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001633: Jun 16 14:42:37 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001634: Jun 16 14:42:38 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001635: Jun 16 14:46:32 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001636: Jun 16 14:46:33 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001637: Jun 16 14:46:35 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001638: Jun 16 14:46:36 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
001639: Jun 16 14:54:24 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
001640: Jun 16 14:54:25 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
001641: Jun 16 14:54:28 CET: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
001642: Jun 16 14:54:29 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up

[balaji.bandi]

This odd, first i will check one of the interface with cables are intact.

interface GigabitEthernet0/1
switchport access vlan 533
switchport mode access
media-type rj45      -- not sure why this comand need here, since all the ports are ethernet only ?
spanning-tree portfast

what is the version of IOS code for all device having issue ?

try some common troubleshoot tips :

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/12027-53.html

[Moudar]

the 2960 switch has "Version 12.2(55)SE12" this one cant be upgraded more than 2017

9200 switch has " 16.09.02"

Only 2960 have  media-type rj45 command!!

I have changed all cables with new ones and still have this issue!

[balaji.bandi]

Ok how is your network diagram, how is the switches connected here.

9200 switch has " 16.09.02"

suggest to upgrade to 17.3.X code for better security fix

all the ports are configured vlan 533 having issue ?

where is your spanning-tree root ?

from all devices

show spanning-tree summay

show vlan

[balaji.bandi]

Quick clarity, is this ever worked, or from the begining you having this issue ?

i would request complete show run config - also advise you to upgrade Cat 9200 with latest stable ?

[MHM Cisco World]

can I know the LC number ?

[Moudar]

I can't see it right now because it is a remote site. 

I had a copper between these 2 switches before and had same problem, so the fiber was only a way to test maybe it gets better but it did not.

this problem is not only happening between these 2 switches but many other switches have similar problem.

[MHM Cisco World]

I will wait to check your reply for LC number.

[Flavio Miranda]

Hi

 2 seconds seems something related to spanning tree. Can you take port-fast for one port and monitor?

[Moudar]

I removed "spanning tree portfast" 

Maybe it will take longer time to finish spanning tree steps without portfast!!?

[Moudar]

after i removed portfast, still have problem

*Jun 16 15:57:09 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/24, changed state to down
007091: *Jun 16 15:57:10 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to down
007092: *Jun 16 15:57:12 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to up
007093: *Jun 16 15:57:13 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/24, changed state to up
007094: *Jun 16 15:57:35 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/24, changed state to down
007095: *Jun 16 15:57:36 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to down
007096: *Jun 16 15:57:39 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to up
007097: *Jun 16 15:57:40 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/24, changed state to up

[Flavio Miranda]

Ok. What is it connected on this port GigabitEthernet1/0/24?

[Moudar]

It is a HP laptop with HP docking station

[Flavio Miranda]

Have you tried without doc station? 

This can be a bad contact. 

[Moudar]

It is not only one PC we talk about but there are many different users and computers with same problem