shielded twisted pair - 3560cg

[Thomas Mikkelsen]

Hi
When we use shielded twisted pair cat 6 cables in our 3560-cg switches, we get input errors and crc errors. The hardware installation guide from Cisco says the following
"
The 10/100/1000 PoE ports use RJ-45 connectors with Ethernet pinouts. The maximum cable length is 328 feet (100 meters). The 100BASE-TX and 1000BASE-T traffic requires Category 5, Category 5e, or Category 6 unshielded twisted pair (UTP) cable. The 10BASE-T traffic can use Category 3 or Category 4 UTP cable.
"
Does this mean that shielded twistet pair is not supported?

Regards
Thomas

Sent from Cisco Technical Support iPad App

[Leo Laohoo]

Can you post the output to the following commands please:

sh interface ; and

sh controll e

[Milan Rai]

Dont think that can be due to Cable...........May i know what do you do to access the switch??? i mean to say SSH or telnet??????

And dont forget if you are using SSH........that may cause CRC error.....as we know all the work is encrypted......
What about using Telnet???? did you tried..that..???

And as told by Leo ....why dont you give us the outputs>>>>

[Thomas Mikkelsen]

Hi

Thanks for your input, here is some output:

"

Transmit GigabitEthernet0/10             Receive

93393354 Bytes                       2308705497 Bytes

  424083 Unicast frames                66285373 Unicast frames

   10152 Multicast frames               1826501 Multicast frames

   60962 Broadcast frames                 86443 Broadcast frames

       0 Too old frames              1901726165 Unicast bytes

       0 Deferred frames              128370606 Multicast bytes

       0 MTU exceeded frames            5847601 Broadcast bytes

       0 1 collision frames                   0 Alignment errors

       0 2 collision frames                  31 FCS errors

       0 3 collision frames                   0 Oversize frames

       0 4 collision frames                   0 Undersize frames

       0 5 collision frames                 109 Collision fragments

       0 6 collision frames

       0 7 collision frames                   4 Minimum size frames

       0 8 collision frames             2781293 65 to 127 byte frames

       0 9 collision frames            32021924 128 to 255 byte frames

       0 10 collision frames           17908731 256 to 511 byte frames

       0 11 collision frames           13026396 512 to 1023 byte frames

       0 12 collision frames            2459999 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                  1 Valid frames, too large

       0 Excess defer frames                109 Invalid frames, too small

       0 64 byte frames                       0 Valid frames, too small

   47487 127 byte frames

  365800 255 byte frames                      0 Too old frames

   58649 511 byte frames                      0 Valid oversize frames

   22568 1023 byte frames                     0 System FCS error frames

     693 1518 byte frames                     0 RxPortFifoFull drop frame

       0 Too large frames

       0 Good (1 coll) frames

       0 Good (>1 coll) frames

"

"

GigabitEthernet0/10 is up, line protocol is up (connected)

  Hardware is Gigabit Ethernet, address is 5897.1e0e.838a (bia 5897.1e0e.838a)

  Description: < **************** >

  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

  Full-duplex, 1000Mb/s, link type is auto, 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:00, output 00:00:09, 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 1450000 bits/sec, 515 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     68247131 packets input, 23800727873 bytes, 0 no buffer

     Received 1913248 broadcasts (1826792 multicasts)

     0 runts, 0 giants, 0 throttles

     31 input errors, 31 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 1826792 multicast, 0 pause input

     0 input packets with dribble condition detected

     495288 packets output, 93414042 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

"

We have links which are worse. But I don't have access to these switches right now.

And we access the switches with telnet.

Regards

Thomas

[Leo Laohoo]

Cable don't always give you single-direction line errors like CRC.  Judging from your output above, the "sh controller e" is telling me of very minute amount of CRC being RECEIVED by the switch.

Your output to the command "sh interface" also does not show anything heart-stopping.

Because of this, I do not believe it's a local cable issue.  I believe it's an issue at the remote end.