03-12-2013 09:46 AM - edited 03-07-2019 12:12 PM
Hello,
I have an odd situation where I cannot get a device connected to a built in switchport with out input and crc errors. When connecting to a GLC-T sfp it works fine.
Here is my test layout
Outdoor wireless AP --- 10' of cat6 cable --- Gigabit POE injector --- 10' Cat6 cable --- 3560G port 48. (input and crc errors)
When I do this there are input and crc errors on the switch port. This has been confirmed on three different switches and three different outdoor AP's. We though at first it was the injector, but when we run the same setup, but instead connect the device to port 49 with a GLC-T sfp there are no errors.
Outdoor wireless AP --- 10' of cat6 cable --- Gigabit POE injector --- 10' Cat6 cable --- 3560G port 49 (GLC-T). (No errors)
I have upgraded the 3560G to the latest ios and still it has the same problem. If I run the same setup to a 2960 there are no errors at all.
Outdoor wireless AP --- 10' of cat6 cable --- Gigabit POE injector --- 10' Cat6 cable --- 2960 port g0/1 (No errors)
I have also tried manually setting the speed on the 3560G with no sucess. Has anyone else run into a problem like this?
Thanks
Dan.
03-12-2013 10:39 AM
Is this on every port on the 3560G, or is it localized to a port/group of ports? It seams you have ruled out everything but the actual switch. It could be a problem with the ASICs in it.
03-12-2013 11:21 AM
I have tried this on 3 different 3560G's. All have the same result.
Dan.
03-12-2013 11:26 AM
Wow, that is impressive. Have you tried setting the port to 100Mbps? I know this is not desirable long term, I am just suggesting it as a test.
03-12-2013 12:46 PM
I have tried that yes. I would really like to know if there is a way to debug this....I can't seem to find anything that shows physical errors.
03-12-2013 05:00 PM
Can you please post the following outputs:
1. sh interface
2. sh controller ethernet
03-12-2013 05:17 PM
GigabitEthernet0/45 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 0023.349f.f0ad (bia 0023.349f.f0ad)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 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:00:04, output 00:00:00, output hang never
Last clearing of "show interface" counters 1d03h
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 0 bits/sec, 0 packets/sec
752627 packets input, 289692707 bytes, 0 no buffer
Received 14572 broadcasts (7469 multicasts)
0 runts, 0 giants, 0 throttles
2139 input errors, 215 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 7469 multicast, 0 pause input
0 input packets with dribble condition detected
1123721 packets output, 1197404428 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 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
ecs-rs-aa-3560g#show run i
ecs-rs-aa-3560g#show run int
ecs-rs-aa-3560g#show run interface g0/45
Building configuration...
Current configuration : 155 bytes
!
interface GigabitEthernet0/45
switchport access vlan 790
switchport mode access
speed 1000
duplex full
spanning-tree portfast
end
ecs-rs-aa-3560g#show controllers ethernet-controller gigabitEthernet 0/45
Transmit GigabitEthernet0/45 Receive
31826575 Bytes 106355697 Bytes
358020629 Unicast frames 214690782 Unicast frames
8854565 Multicast frames 1412128 Multicast frames
2111 Broadcast frames 916874 Broadcast frames
0 Too old frames 3848003978 Unicast bytes
26 Deferred frames 290192790 Multicast bytes
0 MTU exceeded frames 109668925 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 70760 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 209 Collision fragments
0 6 collision frames
1 7 collision frames 39840292 Minimum size frames
0 8 collision frames 107043743 65 to 127 byte frames
0 9 collision frames 20536258 128 to 255 byte frames
0 10 collision frames 9938376 256 to 511 byte frames
0 11 collision frames 5548619 512 to 1023 byte frames
0 12 collision frames 34268227 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 86705 Symbol error frames
1 Late collisions 671 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 1272 Invalid frames, too small
12465074 64 byte frames 0 Valid frames, too small
73799789 127 byte frames
42468519 255 byte frames 0 Too old frames
10948874 511 byte frames 0 Valid oversize frames
5782475 1023 byte frames 0 System FCS error frames
221412575 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
1 Good (>1 coll) frames
03-12-2013 05:39 PM
Dan,
I think this is pointing to duplex speed negotiation issues
See this link
http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015bfd6.shtml
Symbol error frames | Gigabit Ethernet (1000 Base-X) uses 8B/10B Encoding to translate 8bit data from the MAC sublayer(layer 2) to a 10bit Symbol to send over the wire. When a port receives a Symbol, it extracts the 8 bit data from the Symbol (10 bits). | A Symbol error means the interface detects an undefined (invalid) Symbol received. Small amounts of symbol errors can be ignored. Large amounts of symbol errors can indicate a bad device, cable, or hardware. |
Invalid frames, too large | Giant frames or frames received that exceed the maximum IEEE 802.3 frame size (1518 bytes for non-jumbo Ethernet) and have a bad Frame Check Sequence (FCS). | In many cases, this is the result of a bad NIC. Try to find the offending device and remove it from the network. |
Invalid frames, too small | Runt frames or frames received that are less than 64 bytes (which includes the FCS bits and excludes the frame header) and have either an FCS error or an alignment error. | This can be caused by a duplex mismatch and physical problems, such as a bad cable, port, or NIC on the attached device. |
When you are using the fixed SFP ports there is no negotiation as they are only for GIG
Can you try reconfiguring int g0/45
!
!
interface GigabitEthernet0/45
shut
switchport access vlan 790
switchport mode access
speed auto
duplex auto
spanning-tree portfast
no shut
end
Does that make any difference.
Can you post a show int g0/45 after setting to auto
Regards,
Alex.
Please rate useful posts.
03-12-2013 05:48 PM
By default the port is already setup like this:
speed auto
duplex auto
I had changed it to:
speed 1000
duplex full
and to:
speed 100
duplex full
No matter what combination I get the same results. But if I connect it to the SFP or to the 2960 both of which are 1Gbps only it works. So possibly the wireless AP has trouble negotiating speed and therefore doesn't work on a 10/100/1000 switchport? I can try again tomorrow to see if I manually set the wireless AP to 1000 Full and check to see if it works again on the 3560G port 48.
Dan.
03-12-2013 05:50 PM
I agree with Alex. The two outputs are indicative of your ports speed and duplex being hard-coded.
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