02-13-2014 08:31 PM - edited 03-07-2019 06:12 PM
I have a Cisco 3750G with routing enabled. Sometimes, I experience a situation: some clients computers are disconnected from the switch and then reconnected immediately. The whole things happened and ended within 5s. But it often happened, >5 times a day.
The log in switch shows:
Switch#sh log
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 373 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 373 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 377 message lines logged
Log Buffer (4096 bytes):
rface GigabitEthernet1/0/13, changed state to down
1d21h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
1d21h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
2d02h: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
2d02h: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Switch#
I didn't see any problems here, just some interfaces are down and then become up again. This happened not only on this single computer, but on some other devices including a Apple Airport Exterem.
Anyone has any idea about this?
Thanks in advanced.
UPDATE @ Feb 14 20:05 NST:
Configuration on that port is listed below:
Switch#sh run int gi1/0/13
Building configuration...
Current configuration : 66 bytes
!
interface GigabitEthernet1/0/13
switchport access vlan 30
end
Switch#sh int gi1/0/13
GigabitEthernet1/0/13 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 0014.a93b.830d (bia 0014.a93b.830d)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:13:27, output 00:00:01, 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 14000 bits/sec, 7 packets/sec
5 minute output rate 175000 bits/sec, 8 packets/sec
802083047 packets input, 1214885172159 bytes, 0 no buffer
Received 34405 broadcasts (16832 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 16832 multicast, 0 pause input
0 input packets with dribble condition detected
810796080 packets output, 62243896017 bytes, 0 underruns
0 output errors, 0 collisions, 2 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
Switch#sh hard
Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE8, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Wed 26-Jun-13 11:25 by prod_rel_team
Image text-base: 0x01000000, data-base: 0x02F00000
ROM: Bootstrap program is C3750 boot loader
BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.2(44)SE5, RELEASE SOFTWARE (fc1)
Switch uptime is 4 days, 1 hour, 52 minutes
System returned to ROM by power-on
System image file is "flash:c3750-ipservicesk9-mz.122-55.SE8/c3750-ipservicesk9-mz.122-55.SE8.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
Switch#sh ver
Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE8, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Wed 26-Jun-13 11:25 by prod_rel_team
Image text-base: 0x01000000, data-base: 0x02F00000
ROM: Bootstrap program is C3750 boot loader
BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.2(44)SE5, RELEASE SOFTWARE (fc1)
Switch uptime is 4 days, 1 hour, 52 minutes
System returned to ROM by power-on
System image file is "flash:c3750-ipservicesk9-mz.122-55.SE8/c3750-ipservicesk9-mz.122-55.SE8.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
cisco WS-C3750G-24T (PowerPC405) processor (revision J0) with 131072K bytes of memory.
Processor board ID CAT0929Z31B
Last reset from power-on
5 Virtual Ethernet interfaces
24 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 00:14:A9:3B:83:00
Motherboard assembly number : 73-8046-08
Power supply part number : 341-0048-03
Motherboard serial number : CAT09300BFA
Power supply serial number : DTH09262K40
Model revision number : J0
Motherboard revision number : B0
Model number : WS-C3750G-24T-S
System serial number : CAT0929Z31B
Hardware Board Revision Number : 0x05
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 24 WS-C3750G-24T 12.2(55)SE8 C3750-IPSERVICESK9-M
Configuration register is 0xF
Switch#
UPDATE @ Feb 14 20:45 NST
Switch#sh controller e GigabitEthernet1/0/13
Transmit GigabitEthernet1/0/13 Receive
2153682004 Bytes 3714795707 Bytes
810677366 Unicast frames 802082816 Unicast frames
149673 Multicast frames 17023 Multicast frames
18389 Broadcast frames 17786 Broadcast frames
0 Too old frames 3709393103 Unicast bytes
0 Deferred frames 2881529 Multicast bytes
0 MTU exceeded frames 2521075 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 1320039 Minimum size frames
0 8 collision frames 250602 65 to 127 byte frames
0 9 collision frames 165765 128 to 255 byte frames
0 10 collision frames 77695 256 to 511 byte frames
0 11 collision frames 124005 512 to 1023 byte frames
0 12 collision frames 800179519 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 0 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
802135613 64 byte frames 0 Valid frames, too small
243436 127 byte frames
1271533 255 byte frames 0 Too old frames
100832 511 byte frames 0 Valid oversize frames
64915 1023 byte frames 0 System FCS error frames
7029099 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames
Switch#
UPDATE @ Feb 14 21:25 NST
Switch#test cable tdr interface G 1/0/13
TDR test started on interface Gi1/0/13
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.
Switch#sh cable tdr interface G 1/0/13TDR test last run on: March 05 03:07:45
Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/13 1000M Pair A 2 +/- 10 meters Pair B Normal
Pair B 0 +/- 10 meters Pair A Normal
Pair C 0 +/- 10 meters Pair D Normal
Pair D 0 +/- 10 meters Pair C Normal
Switch#
UPDATE @ 14:30 Feb 17 NST
Switch#test cable-diagnostics tdr interface G 1/0/15
TDR test started on interface Gi1/0/15
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.
Switch#show cable-diagnostics tdr int G 1/0/13
TDR test last run on: March 05 03:07:45
Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/13 1000M Pair A 2 +/- 10 meters Pair B Normal
Pair B 0 +/- 10 meters Pair A Normal
Pair C 0 +/- 10 meters Pair D Normal
Pair D 0 +/- 10 meters Pair C Normal
Switch#
02-14-2014 12:17 AM
Hi,
What is the running config if those interfaces
show us the output of :
Show run int x/y
show int x/y
Add 'spanning tree portfast' to the interfaces where you have computers connected.
Thanks
Ankur
"Please rate the post if found useful"
02-14-2014 03:37 PM
Hi,
I updated my original post to contain the information you requested.
Thank you.
02-17-2014 10:06 AM
Hi. The output has been updated to original post.
I didn't add 'spanning tree portfast' to any interface. Every time the computer disconnected, it resume it's connection within 5 seconds, and the port LED in switch keep showing Green. I believe the port does not enter 'down -> blocking -> learning -> forwarding' cycle in this case.
Regards,
Lingfeng Xiong
02-14-2014 07:37 AM
Hi,
i encountered the same your problem on our customer network. Sometimes all uplink freeze and after 5 - 10 seconds replaces itself.
Our platform: 3 x WS-C3750G-24TS-1U stacked:
Software version and image:
12.2(35)SE5 C3750-IPBASE-M
Can you share yours?
Thanks
Pier
02-14-2014 03:38 PM
Hi.
I believe this problem does not occurred before I enable the routing function.
The information you requested has been contained in my original question, I updated it :-) (Only one standalone switch. No stacking)
Thank you.
02-14-2014 04:14 PM
Post the output to the command "sh controller e GigabitEthernet1/0/13".
02-14-2014 04:16 PM
Hi,
Information updated at original post.
02-14-2014 04:22 PM
Ok, no line errors detected for a switch uptime of four (4+) days.
Do this:
1. Command: test cable tdr interface G 1/0/13;
2. Wait for 7 seconds;
3. Command: sh cable tdr interface G 1/0/13; and
4. Post the output to #3 BELOW.
02-14-2014 04:56 PM
I updated my original post to contains complete output of those two commands.
BTW: I recalled this problem does not exist before I enable the routing function of this switch.
I have no idea if this is a coincident or not. Because this switch is currently used in a production environment, I cannot turn routing down for testing.
02-14-2014 08:56 PM
There's nothing wrong with the cable. There's no line errors.
I'm looking at possibly the drivers of your network card could be an issue.
02-15-2014 09:19 AM
Hi.
I'm pretty sure that the NIC and driver is not the problem. This is because:
1. before connecting to this switch, this computer has been connected to other switches without any problem
2. the operating system has been reinstalled but problem still there
and
3. another Apple Airport Extreme which connected to this switch also experiencing this problem.
Thanks
02-15-2014 05:00 PM
I'm pretty sure that the NIC and driver is not the problem.
Back in 2008, I had witnessed first-hand on how a brand new Intel GigabitEthernet NIC card reacts to legacy 3500XL switches. No matter what IOS you've loaded on the switch the links will go down/up between 25 to 45 times per minute. This will cause users very, very slow response. The easiest way to fix this issue is to force the NIC card to negotiate to 100/Full.
I am not saying to you have Intel NIC card but so far all suspects are on the table. Your wired NIC card has not been ruled out.
another Apple Airport Extreme which connected to this switch also experiencing this problem.
Hmmmm ... I'm reviewing the TDR result. What kind of cable is this? Is this a 1 metre cable? Can you please change this?
02-17-2014 09:55 AM
Hi,
It is a one metre cable with text "Cat 5e PATCH --- UTP".
I'll try to replace it and see what happened.
PS: Althouth it's not a cat 6 cable, it works great when transferring files. The speed can exceed 105MB/s :-)
Regards,
Lingfeng Xiong
P.S.: I just updated the original post with Airport Exterme's port test result (Gi 1/0/15)
P.S.: gi 1/0/13 and gi 1/0/15 are different cables.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide