cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
466
Views
5
Helpful
20
Replies

Interfaces go up and down!

moudar123
Beginner
Beginner

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

20 Replies 20

marce1000
VIP Mentor VIP Mentor
VIP Mentor

 

 - Check error counters on the involved ports , also look at the logs of all involved switches, make sure no other networking events are  causing this.

 M.

2661921 packets input, 743883857 bytes, 0 no buffer
Received 36257 broadcasts (33165 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 33165 multicast, 0 pause input
0 input packets with dribble condition detected
7720244 packets output, 4714423435 bytes, 0 underruns
Output 965500 broadcasts (2026953 multicasts)
0 output errors, 0 collisions, 2 interface resets
1071 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

 

ce 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

 

there is no other logs than these, other ports do send same logs i will put them here when i catch them

N-Chan
Beginner
Beginner

I'm still kinda new at this. Correct me if I'm wrong, but shouldn't the ports between them be "switchport mode trunk"?

 

     - You only need trunk ports for connecting switches and or if more then one vlan needs to be connected in between.

 M.

W-ALI
Beginner
Beginner

I faced same issue before with Catalyst 3750 ,

but the issue was in capacitors of power supply of controllers.