cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
467
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.

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

@moudar123 wrote:
WS-C2960-24TC-L   Version 12.2(55)SE12
C9200L-24P-4G    Version 17.06.03

Wait a second ... I need to know where this problem is occurring most.  Is this issue occurring on a 2960 switch or a 9200 switch. 

It may sound stupid but it is not.  2960 runs on classic IOS and is well-acknowledged as stable, however, 9200 runs on IOS-XE and it is also well-acknowledged to be a "work-in-progress", if anyone gets what I mean.

The "sh log" output above looks like it is coming from a 9200.  I need to know so I can focus my attention to either one.  Troubleshooting issues on classic IOS is easy but IOS-XE is not.

It is happening on both models.

Logs from my post comining from 9200L switch which is about 2 years old was running 16.x.x version and I did updated it last week in hope of finding solution for the problem but upgrading did not help!

025213: Aug 5 21:06:26 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
025214: Aug 5 21:06:27 CET: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
025215: Aug 5 21:06:34 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
025216: Aug 5 21:06:35 CET: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
025217: Aug 5 21:06:43 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
025218: Aug 5 21:06:45 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
025219: Aug 5 21:41:23 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
025220: Aug 5 21:41:24 CET: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
025221: Aug 5 21:41:29 CET: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
025222: Aug 5 21:41:30 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
025223: Aug 5 21:41:39 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
025224: Aug 5 21:41:41 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
025225: Aug 6 06:54:35 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
025226: Aug 6 06:54:36 CET: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
025227: Aug 6 06:54:43 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
025228: Aug 6 06:54:45 CET: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
025229: Aug 6 06:54:53 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down
025230: Aug 6 06:54:55 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up

These logs are from 2960, 

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

On the 9200, post the complete output to the command "sh interface Gi1/0/20 controll".  

Gi1/0/20 and Fa 0/1 are not connected to each other, are they?

sh interface Gi1/0/20 controller

GigabitEthernet1/0/20 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 7488.bb32.1894 (bia 7488.bb32.1894)
MTU 1500 bytes, BW 10000 Kbit/sec, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Mb/s, media type is 10/100/1000BaseTX
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 18:00:37, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 5000 bits/sec, 4 packets/sec
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
7735048 packets output, 4717499376 bytes, 0 underruns
Output 969619 broadcasts (2037082 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
Transmit GigabitEthernet1/0/20 Receive
4717499376 Total bytes 743883857 Total bytes
4728347 Unicast frames 2625664 Unicast frames
4120626210 Unicast bytes 735850215 Unicast bytes
2037082 Multicast frames 33165 Multicast frames
424485568 Multicast bytes 7548627 Multicast bytes
969619 Broadcast frames 3092 Broadcast frames
172387598 Broadcast bytes 485015 Broadcast bytes
0 System FCS error frames 0 IpgViolation frames
0 MacUnderrun frames 0 MacOverrun frames
0 Pause frames 0 Pause frames
0 Cos 0 Pause frames 0 Cos 0 Pause frames
0 Cos 1 Pause frames 0 Cos 1 Pause frames
0 Cos 2 Pause frames 0 Cos 2 Pause frames
0 Cos 3 Pause frames 0 Cos 3 Pause frames
0 Cos 4 Pause frames 0 Cos 4 Pause frames
0 Cos 5 Pause frames 0 Cos 5 Pause frames
0 Cos 6 Pause frames 0 Cos 6 Pause frames
0 Cos 7 Pause frames 0 Cos 7 Pause frames
0 Oam frames 0 OamProcessed frames
0 Oam frames 0 OamDropped frames
1732441 Minimum size frames 1067949 Minimum size frames
962235 65 to 127 byte frames 376813 65 to 127 byte frames
1491118 128 to 255 byte frames 684719 128 to 255 byte frames
782778 256 to 511 byte frames 161988 256 to 511 byte frames
140290 512 to 1023 byte frames 78873 512 to 1023 byte frames
2626208 1024 to 1518 byte frames 291579 1024 to 1518 byte frames
0 1519 to 2047 byte frames 0 1519 to 2047 byte frames
0 2048 to 4095 byte frames 0 2048 to 4095 byte frames
0 4096 to 8191 byte frames 0 4096 to 8191 byte frames
0 8192 to 16383 byte frames 0 8192 to 16383 byte frames
0 16384 to 32767 byte frame 0 16384 to 32767 byte frame
0 > 32768 byte frames 0 > 32768 byte frames
0 Late collision frames 0 SymbolErr frames
0 Excess Defer frames 0 Collision fragments
0 Good (1 coll) frames 0 ValidUnderSize frames
0 Good (>1 coll) frames 0 InvalidOverSize frames
0 Deferred frames 0 ValidOverSize frames
0 Gold frames dropped 0 FcsErr frames
0 Gold frames truncated
1 Gold frames successful
0 1 collision frames
0 2 collision frames
0 3 collision frames
0 4 collision frames
0 5 collision frames
0 6 collision frames
0 7 collision frames
0 8 collision frames
0 9 collision frames
0 10 collision frames
0 11 collision frames
0 12 collision frames
0 13 collision frames
0 14 collision frames
0 15 collision frames
0 Excess collision frames

LAST UPDATE 216 msecs AGO

Gi1/0/20 and Fa 0/1 are not connected to each other, are they?

No, but these to switches are connected to each other with a trunk fiber cable 

Full-duplex, 10Mb/s, media type is 10/100/1000BaseTX<<-- the speed mismatch,
one side config as auto and other side hardcoded.

 

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

@moudar123 wrote:
Full-duplex, 10Mb/s, media type is 10/100/1000BaseTX
Last input 18:00:37, output 00:00:01, output hang never

What is this downstream client?  Is this a Windows-based PC that has gone to sleep/logged-out?

I think it is a PC (laptop) and now under weekend it is sleeping, I will
check this tomorrow and get back with some new information.

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

@moudar123 wrote:
I think it is a PC (laptop) and now under weekend it is sleeping, I will
check this tomorrow and get back with some new information.

If this is indeed a Windows-based machine then the problem is the SOE.  

Look at the systems logs of that machine.  I suspect Wake-On-LAN is misconfigured.

What kind of problem can SOE have?

Wake-On-LAN is active on all PCs, should it be something else?

this problem is happening only on one building, other buildings have no problem. All PCs get their Windows copy from the same SCCM server. I mean all PCs have the same configs!

I will check the logs and get back.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers