I used to sell switches for Cabletron and one time I was setting up a demo for RMON. I used a flat satin cable between two switches and figured I would get errors. I had none. I then used a four-wire phone handset, the one with the curls, put an RJ45 at each end and still had no errors. I believe you could run 100M over a very short stretch of barbed wire if you had to do it. :)
Jeffrey Reed Classic Networking, Inc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chuck Sent: Sunday, May 19, 2002 5:10 PM To: [EMAIL PROTECTED] Subject: Re: why my gigabit switch port speed only hit 10M? [7:44333] interesting. I had a similar conversation with a customer last week. the customer said they were running 100 megabit on cat 3 wire. I asked them how they knew. The answer was essentially that they had link. ( connectivity ) there are many reasons you may not be getting real ( or perceived ) gigabit on the link. Others have pointed those reasons out - slow disk drives, busy server, or whatever. just cuz you have connectivity doesn't automatically mean you will get the fastest throughput possible. ""Sim, CT (Chee Tong)"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Hi.. I had installed a gigabit switch (Cisco 3550). But I feel the speed > of slow. I connected my two PC in GigabitEthernet0/1 and 0/2. I transfer a > huge file between the two PCs ( the transfer last for 4 mins). But the > maximum speed is only 10Mbit ? Why?? What is wrong?? I thought it should > be go up to 1000M or 1Gbits??? > > ! > interface GigabitEthernet0/1 > no ip address > snmp trap link-status > ! > interface GigabitEthernet0/2 > no ip address > snmp trap link-status > ! > interface GigabitEthernet0/3 > no ip address > snmp trap link-status > ! > interface GigabitEthernet0/4 > no ip address > snmp trap link-status > ! > interface GigabitEthernet0/5 > no ip address > snmp trap link-status > ! > > cat35-L8-1#sh int gi0/1 > GigabitEthernet0/1 is up, line protocol is up > Hardware is Gigabit Ethernet, address is 0005.313e.7581 (bia > 0005.313e.7581) > 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 > input flow-control is off, output flow-control is on > 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, 14 packets/sec > 905784 packets input, 1303109052 bytes, 0 no buffer > Received 66 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 0 input packets with dribble condition detected > 1042863 packets output, 190194068 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 output buffer failures, 0 output buffers swapped out > GigabitEthernet0/2 is up, line protocol is up > Hardware is Gigabit Ethernet, address is 0005.313e.7582 (bia > 0005.313e.7582) > 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 > input flow-control is off, output flow-control is on > 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, 13 packets/sec > 1486 packets input, 179522 bytes, 0 no buffer > Received 1421 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 0 input packets with dribble condition detected > 1948976 packets output, 1493416902 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 output buffer failures, 0 output buffers swapped out > > > > > > ================================================================== > De informatie opgenomen in dit bericht kan vertrouwelijk zijn en > is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht > onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en > de afzender direct te informeren door het bericht te retourneren. > ================================================================== > The information contained in this message may be confidential > and is intended to be exclusively for the addressee. Should you > receive this message unintentionally, please do not use the contents > herein and notify the sender immediately by return e-mail. > > > ================================================================== Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=44518&t=44333 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
