|
Update... All is well operating at 100MB/Full Duplex. Thanks to all for their advice. Thanks too for clarifying that 100MB uses only two pair.. there was some conflicting info in my research on this. We use the 568B standard here; which does appear to be "the" standard being used. - Replaced both CAT5 Ends and retested OK... - Changed both Duplex=*full and Linkspeed=100M on LIND and Switch Port... Something must have been wrong in the cable-ends.....even though they tested OK. The may have been a bit loose. Probably should make it a habit to wiggle them some before testing. The only difference between my attempt yesterday and today was replacing them. We are looking into features of the tester... it is circa 1998, made need a difference module end to test 100MB..It is a Microtest Pentascanner with Module8's. It was mentioned to NOT change linkspeed, but it appears to be working as changed.. Any concerns leaving it as-is? ETHLIND ------- Ethernet standard . . . . . . . . : *ALL Line speed . . . . . . . . . . . . : 100M Current line speed . . . . . . . . : 100M Duplex . . . . . . . . . . . . . . : *FULL Current duplex . . . . . . . . . . : *FULL Maximum frame size . . . . . . . . : 1496 Cisco Switch ------------ FastEthernet0/12 is up, line protocol is up Hardware is Fast Ethernet, address is 0090.b1a5.ae4c (bia 0090.b1a5.ae4c) Description: qs1032cpm MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive not set Full-duplex, 100Mb/s, 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:01, output hang never Last clearing of "show interface" counters 01:57:32 Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 3000 bits/sec, 3 packets/sec 5 minute output rate 2000 bits/sec, 2 packets/sec 13608 packets input, 7458327 bytes, 0 no buffer Received 213 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 watchdog, 0 multicast 0 input packets with dribble condition detected 12400 packets output, 3348427 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 output buffer failures, 0 output buffers swapped out
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.