- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 02:11 AM - edited 03-07-2019 01:05 AM
Hi all,
Hope someone can help, over the past few weeks one of switches (3500xl) has started showing a large number of input errors on the uplink interface(shown below) and the users connected experience a great deal of slow down. I've checked all the phsical connections and can't see a problem and port mirroring doesnt show me too much (although Im not really a network guy so I could be missing something..)
Interface Output:
MAI-SW41#sh int gig0/1
GigabitEthernet0/1 is up, line protocol is up
Hardware is Gigabit Ethernet, address is 0002.b98f.90f1 (bia 0002.b98f.90f1)
Description: Uplink MAI-SW01
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), 1000Mb/s, media type is SX
output flow-control is off, input flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 20:28:53
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 692000 bits/sec, 130 packets/sec
5 minute output rate 392000 bits/sec, 105 packets/sec
11771432 packets input, 3219529600 bytes, 0 no buffer
Received 1761184 broadcasts, 0 runts, 0 giants, 0 throttles
32519 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1656571 multicast, 0 pause input
8413972 packets output, 1785575097 bytes, 0 underruns
0 output errors, 0 collisions, 0 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
Controller output:
Transmit Receive
731682836 Bytes 2410818600 Bytes
3141487 Unicast frames 3592201 Unicast frames
3128 Multicast frames 181944 Multicast frames
2228 Broadcast frames 20086 Broadcast frames
0 Discarded frames 0 No bandwidth frames
0 Too old frames 0 No buffers frames
0 Deferred frames 1648 No dest, unicast
0 1 collision frames 102514 No dest, multicast
0 2 collision frames 1729 No dest, broadcast
0 3 collision frames 0 Alignment errors
0 4 collision frames 0 FCS errors
0 5 collision frames 44 Collision fragments
0 6 collision frames
0 7 collision frames 0 Undersize frames
0 8 collision frames 221018 Minimum size frames
0 9 collision frames 1964824 65 to 127 byte frames
0 10 collision frames 130397 128 to 255 byte frames
0 11 collision frames 47975 256 to 511 byte frames
0 12 collision frames 48491 512 to 1023 byte frames
0 13 collision frames 1497444 1024 to 1518 byte frames
0 14 collision frames 0 Oversize frames
0 15 collision frames 30295 Flooded frames
0 Excessive collisions 0 Overrun frames
0 Late collisions 0 VLAN filtered frames
0 Good (1 coll) frames 1 Source routed frames
0 Good(>1 coll) frames 0 Valid oversize frames
0 Pause frames 0 Pause frames
0 VLAN discard frames 10027 Symbol error frames
0 Excess defer frames 38 Invalid frames, too large
0 Too large frames 0 Valid frames, too large
766484 64 byte frames 6 Invalid frames, too small
307326 127 byte frames 0 Valid frames, too small
1701857 255 byte frames 767 0 Addr Cmp frames
75802 511 byte frames 314941 1 Addr Cmp frames
66319 1023 byte frames 3594478 2 Addr Cmp frames
229055 1518 byte frames 0 3 Addr Cmp frames
0 4 Addr Cmp frames
0 5 Addr Cmp frames
0 6 Addr Cmp frames
0 7 Addr Cmp frames
0 8 Addr Cmp frames
0 9 Addr Cmp frames
0 10 Addr Cmp frames
0 11 Addr Cmp frames
0 12 Addr Cmp frames
0 13 Addr Cmp frames
0 14 Addr Cmp frames
0 15 Addr Cmp frames
All counters were cleared first thing this morning.
Please let me know if I need to provide more info, have to confess Im a little lost on this one!
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 03:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 06:45 PM
Input errors are generally because of layer 1 issues, mostly bad media (cable/gbics).
Check for the cable or GBICs on both the ends.
Hope thet helps.
Sweta
p.s. please rate the helpful answers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 03:05 PM
In order to isolate the issue, enable UDLD on that interface and check whether the interface is going error-disabled or not.
I don't believe UDLD is supported on 3500XL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 08:52 AM
Hi Mike,
Try to hardcode same speed and duplex on both ends of your switches. Was there any duplex mismatch in syslog?
Sent from Cisco Technical Support iPhone App
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 06:45 PM
Input errors are generally because of layer 1 issues, mostly bad media (cable/gbics).
Check for the cable or GBICs on both the ends.
Hope thet helps.
Sweta
p.s. please rate the helpful answers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 03:09 PM
10027 Symbol error frames
That's too high.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 11:19 PM
I can see from the output that the media type used is SX. It could be possible that either the port, SFP, cable having issue.
have you tried changing the cable, SFP and the port.
In order to isolate the issue, enable UDLD on that interface and check whether the interface is going error-disabled or not.
To enable udld globally:
=================
config t
udld enable
To enable in interface level:
===================
conf ter
inter gig 0/1
udld mode aggressive.
check this link for more details
Hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 03:05 PM
In order to isolate the issue, enable UDLD on that interface and check whether the interface is going error-disabled or not.
I don't believe UDLD is supported on 3500XL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 12:33 AM
Hi All,
Thanks for the replies I am going to look into your suggestions today (sadly being a production switch it is difficult to work on in hours despite the problems).
johnlloyd_13 - No there are no duplex mismatches in the syslog (or any messages related to this interface)
I am going to check all the physical media again later. I'll report back and rate, thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2011 06:19 AM
Hi All,
Thanks for the help, this is definatly a physical problem I have now bypassed this link and am temporarily linking this switch through another. I now have to try and find out whether its the fibre cable itself or the GBIC's which will be interesting with no fibre testing equipment!
Mike
