Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1228
Views
0
Helpful
7
Replies

C3750 Ports keep changing state

rmiller
Level 1
Level 1

‎10-26-2017 10:50 AM - edited ‎03-08-2019 12:30 PM

I just looked at the diagnostic logs on one of my switches and noticed the state on many of the ports keeps changing up/down and back. What causes this problem and how do I resolve it?

Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 16111 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 16111 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Trap logging: level informational, 16038 message lines logged

Log Buffer (4096 bytes):
nged state to up
016073: .Oct 26 09:08:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to up
016074: .Oct 26 09:23:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to down
016075: .Oct 26 09:23:07: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to down
016076: .Oct 26 09:23:09: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to up
016077: .Oct 26 09:23:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to up
016078: .Oct 26 09:25:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/16, changed state to down
016079: .Oct 26 09:25:57: %LINK-3-UPDOWN: Interface FastEthernet1/0/16, changed state to down
016080: .Oct 26 09:25:59: %LINK-3-UPDOWN: Interface FastEthernet1/0/16, changed state to up
016081: .Oct 26 09:26:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/16, changed state to up
016082: .Oct 26 09:27:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/12, changed state to down
016083: .Oct 26 09:27:55: %LINK-3-UPDOWN: Interface FastEthernet1/0/12, changed state to down
016084: .Oct 26 09:27:58: %LINK-3-UPDOWN: Interface FastEthernet1/0/12, changed state to up
016085: .Oct 26 09:27:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/12, changed state to up
016086: .Oct 26 09:28:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to down
016087: .Oct 26 09:28:43: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to down
016088: .Oct 26 09:28:46: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to up
016089: .Oct 26 09:28:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to up
016090: .Oct 26 09:42:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/12, changed state to down
016091: .Oct 26 09:42:57: %LINK-3-UPDOWN: Interface FastEthernet1/0/12, changed state to down
016092: .Oct 26 09:42:59: %LINK-3-UPDOWN: Interface FastEthernet1/0/12, changed state to up
016093: .Oct 26 09:43:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/12, changed state to up
016094: .Oct 26 09:44:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/16, changed state to down
016095: .Oct 26 09:44:11: %LINK-3-UPDOWN: Interface FastEthernet1/0/16, changed state to down
016096: .Oct 26 09:44:13: %LINK-3-UPDOWN: Interface FastEthernet1/0/16, changed state to up
016097: .Oct 26 09:44:14: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/16, changed state to up
016098: .Oct 26 10:24:15: %DIAG-6-TEST_RUNNING: Switch 1: Running TestPortAsicStackPortLoopback{ID=1} ...
016099: .Oct 26 10:24:16: %DIAG-6-TEST_OK: Switch 1: TestPortAsicStackPortLoopback{ID=1} has completed successfully
016100: .Oct 26 10:25:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to down
016101: .Oct 26 10:25:02: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to down
016102: .Oct 26 10:25:04: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to up
016103: .Oct 26 10:25:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to up
016104: .Oct 26 10:27:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to down
016105: .Oct 26 10:27:25: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to down
016106: .Oct 26 10:27:27: %LINK-3-UPDOWN: Interface FastEthernet1/0/17, changed state to up
016107: .Oct 26 10:27:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/17, changed state to up
016108: .Oct 26 10:30:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/12, changed state to down
016109: .Oct 26 10:30:41: %LINK-3-UPDOWN: Interface FastEthernet1/0/12, changed state to down
016110: .Oct 26 10:30:44: %LINK-3-UPDOWN: Interface FastEthernet1/0/12, changed state to up
016111: .Oct 26 10:30:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/12, changed state to up

--------------------------------------------------------------------------------

 

 

Labels:
0 Helpful
7 Replies 7

Georg Pauwen
VIP
VIP

‎10-26-2017 11:14 AM

Hello,

 

what do you have connected on these ports ?

0 Helpful

rmiller
Level 1
Level 1
In response to Georg Pauwen

‎10-26-2017 07:09 PM

@Georg Pauwen wrote:

Hello,

 

what do you have connected on these ports ?

Interestingly, all three ports are connected to Lexmark printers.

0 Helpful

Georg Pauwen
VIP
VIP
In response to rmiller

‎10-27-2017 12:34 AM

Hello,

 

which Lexmark printer models do you have ? I would check if there is some sort of sleep/power save/Wake-on-Lan mode active on those printers....

0 Helpful

Harsha A.
Level 1
Level 1

‎10-26-2017 12:13 PM

That's interesting....Is this switch connecting endpoints like laptops ? or is it connecting servers/Esxi hosts ?

 

Also can you post the configuration of the switchports.

0 Helpful

Leo Laohoo
Hall of Fame
Hall of Fame

‎10-26-2017 12:52 PM

Post the complete output to the command "sh interface Fa1/0/17 control".
0 Helpful

rmiller
Level 1
Level 1
In response to Leo Laohoo

‎10-26-2017 07:12 PM

@Leo Laohoo wrote:
Post the complete output to the command "sh interface Fa1/0/17 control".

Gateway#sh interface Fa1/0/17 control
FastEthernet1/0/17 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 0013.c390.7d93 (bia 0013.c390.7d93)
Description: Voice and Data
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/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 12000 bits/sec, 11 packets/sec
2123906 packets input, 303093072 bytes, 0 no buffer
Received 2640 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1068 multicast, 0 pause input
0 input packets with dribble condition detected
72794314 packets output, 1222359959 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
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 FastEthernet1/0/17 Receive
1222376378 Bytes 303093072 Bytes
28797762 Unicast frames 2121266 Unicast frames
23046971 Multicast frames 1068 Multicast frames
20949611 Broadcast frames 1572 Broadcast frames
0 Too old frames 302371973 Unicast bytes
0 Deferred frames 620212 Multicast bytes
0 MTU exceeded frames 100608 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 266974 Minimum size frames
0 8 collision frames 536178 65 to 127 byte frames
0 9 collision frames 1289142 128 to 255 byte frames
0 10 collision frames 3568 256 to 511 byte frames
0 11 collision frames 2398 512 to 1023 byte frames
0 12 collision frames 25647 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 1 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
21058352 64 byte frames 0 Valid frames, too small
14169902 127 byte frames
7467402 255 byte frames 0 Too old frames
1168700 511 byte frames 0 Valid oversize frames
7974961 1023 byte frames 0 System FCS error frames
20955027 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames

0 Helpful

Leo Laohoo
Hall of Fame
Hall of Fame
In response to rmiller

‎10-26-2017 11:14 PM

Output is showing me there's nothing wrong. I suspect the flapping is caused by the NIC.
0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card