On Tue, May 4, 2010 at 17:39, Narbik Kocharians <narbikk_at_gmail.com> wrote:
> That is true, the end that is in half Duplex mode should get "late
> collisions" and the end that is in full duplex mode should get "CRC checks",
> whereas, a mismatch in Speed (Which i don't think that could be the problem
> that you are experiencing) should show as "NOTCONNECTED".
Quite right, however, if duplex is not hardcoded, but speed is, it
would not be negotiated in most cases. Cisco used to default to
half-duplex in this case. I've seen quite a few issues caused by
configuring only parts of the speed/duplex pair.
If any of them is set manually, negotiation is disabled. To negotiate
speed and duplex, both need to be set to auto.
As far as recommendation to hardcode them - that would depend on what
exactly is connected to the port. Some things don't handle
negotiation, other things don't handle manual settings (fiber optics
media converters are especially bad).
-- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert YES! We include 400 hours of REAL rack time with our Blended Learning Solution! Mailto: markom_at_ipexpert.com Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Web: http://www.ipexpert.com/ Blogs and organic groups at http://www.ccie.netReceived on Tue May 04 2010 - 18:16:15 ART
This archive was generated by hypermail 2.2.0 : Tue Jun 01 2010 - 07:09:52 ART