Interfaces go up and down!

[Moudar]

Hi!

I did ask this quetion before but did not get an answer to the problem, and now i am trying again!

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

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?

two switches are doing this very often:

WS-C2960-24TC-L   Version 12.2(55)SE12

C9200L-24P-4G    Version 17.06.03

these are connected to each other by a fiber trunk.

the ports are configured exactly the same at both switches:

switchport access vlan 533
switchport mode access

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

Spanning tree config is as follows:

spanning-tree mode rapid-pvst
spanning-tree extend system-id
no spanning-tree vlan 1-800

"We don't use redundant ports" 

show spanning-tree summary
Switch is in rapid-pvst mode
Root bridge for: none
Extended system ID is enabled
Portfast Default is disabled
PortFast BPDU Guard Default is disabled
Portfast BPDU Filter Default is disabled
Loopguard Default is disabled
EtherChannel misconfig guard is enabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short

Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
Total 0 0 0 0 0

#sh spanning-tree summary
Switch is in rapid-pvst mode
Root bridge for: none
EtherChannel misconfig guard is enabled
Extended system ID is enabled
Portfast Default is disabled
PortFast BPDU Guard Default is disabled
Portfast BPDU Filter Default is disabled
Loopguard Default is disabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is long

Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
Total 0 0 0 0 0

Logs:

000942: Aug 5 07:11:36 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Down -> Up
000943: Aug 5 07:11:37 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
000944: Aug 5 07:11:38 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
000945: Aug 5 07:11:40 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Up -> Down
000946: Aug 5 07:11:40 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
000947: Aug 5 07:11:41 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
000948: Aug 5 07:11:43 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Down -> Up
000949: Aug 5 07:11:45 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
000950: Aug 5 07:11:46 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
000951: Aug 5 07:12:13 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Up -> Down
000952: Aug 5 07:12:14 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
000953: Aug 5 07:12:15 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
000954: Aug 5 07:12:17 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Down -> Up
000955: Aug 5 07:12:18 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
000956: Aug 5 07:12:19 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
000957: Aug 5 08:21:45 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Up -> Down
000958: Aug 5 08:21:45 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
000959: Aug 5 08:21:46 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
000960: Aug 5 08:21:48 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Down -> Up
000961: Aug 5 08:21:49 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
000962: Aug 5 08:21:50 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
000963: Aug 5 08:34:36 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Up -> Down
000964: Aug 5 08:34:36 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
000965: Aug 5 08:34:37 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
000966: Aug 5 08:34:39 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Down -> Up
000967: Aug 5 08:34:41 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
000968: Aug 5 08:34:42 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
000969: Aug 5 15:54:50 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Up -> Down
000970: Aug 5 15:54:50 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
000971: Aug 5 15:54:51 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
000972: Aug 5 15:54:53 CET: %TRACK-6-STATE: 1 interface Gi1/0/20 line-protocol Down -> Up
000973: Aug 5 15:54:54 CET: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
000974: Aug 5 15:54:55 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up

[Leo Laohoo]

---

@Moudar wrote:
What kind of problem can SOE have?

---

You are asking the wrong person.  I do not work for your company's SOE team. 

---

@Moudar wrote:
Wake-On-LAN is active on all PCs

---

When a computer goes to sleep or logged out, the ports go down/up twice.  That is all.  And when a computer is in sleep or logged out, the ports should never flap.  Never.  Unless someone plays around with the way Wake-On-LAN (mis)behaves.

---

@Moudar wrote:
All PCs get their Windows copy from the same SCCM server. I mean all PCs have the same configs!

---

And?  Every PC and laptop gets the same GP update.  IF the SOE or the scripts is built wrong, EVERYONE gets it and all the ports goes wild.  
  

[paul driver]

Hello

---

@Moudar wrote:

no spanning-tree vlan 1-800

---

Outch! 
Even if you say you don’t use redundant ports i would suggest NOT to turn spanning-tree off, so enable it and see if you network stabilizes

[Rich R]

Further to Leo's questions we need to see the detailed topology between these 2 switches and any other switches they're connected to.

Also I'd suggest upgrading the 2960 to https://software.cisco.com/download/home/279963375/type/280805680/release/15.0.2-SE11 which I've generally found to be better and more compatible with the newer IOS-XE switches.

[Moudar]

2960 and 9200l are connected with each other by a trunk. (switchport mode trunk)

9200l is connected to ISP's MPLS with other trunk.

Upgrading to IOS 15.0.2 is not the recommended option (golden star), i recall a case where i did upgrade to that version and  the switch could not boot (some old 2960 switch).

[MHM Cisco World]

the speed is 10 Mb

there are unknown protocol error 
two indicate there is L2 protocol run and since the speed 10 Mb I think that 
SW is hardcoded and PC run autonego.
may be I am not right 
but check this point 

[pieterh]

not only sleep mode of the whole PC is involved, but also the power mode of the LAN interface of the PC.
it may be the PC is setting the interface to power saving mode, (this mode also results in the 10MHz status)
open LAN interface properties -> configure -> power management
disable "allow the computer to turn off this device to save power"

NB! we all know power saving is "better" but it is either this or all the logging on the switch