Re: Duplex negotiation problems info
- From: roberson@xxxxxxxxxxxx (Walter Roberson)
- Date: Tue, 04 Jul 2006 22:45:22 GMT
In article <Rp6dnfsCjdH8QjfZnZ2dnUVZ_oidnZ2d@xxxxxxxxxxx>,
thrill5 <nospam@xxxxxxxxxxx> wrote:
Either your standard is to hardcode EVERYTHING or leave EVERYTHING Auto.
Many people espouse hardcoding infrastructure and servers, and
leaving desktops auto.
Auto-negotiation did not work 100% when it first came out which is why a lot
of places hard code the settings, but now it is not an issue any more.
Unfortunately, it -is- still an issue. There are still autonegotiation
failures, including some known to involve Cisco equipment.
(e.g., I seem to recall mixing Cat6500 + some 3COM switches is
a problem.) The failures these days -mostly- involve older equipment,
but "older" might mean in terms of design rather than manufacturing
date -- and there is still a lot of equipment in the field that was
manufactured several years ago. Also, I read about autonegotiation
failures involving some of the cheap consumer-level switches.
.
- References:
- Duplex negotiation problems info
- From: Blue Frog
- Re: Duplex negotiation problems info
- From: thrill5
- Duplex negotiation problems info
- Prev by Date: Re: Cisco Catalyst 4006 as VMPS server.
- Next by Date: Re: OSPF SNMP-Trap Mib
- Previous by thread: Re: Duplex negotiation problems info
- Next by thread: Re: Duplex negotiation problems info
- Index(es):
Relevant Pages
|