--biYV.44/i3UnYU.1sZrha.CGnyCtq
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
content-class: urn:content-classes:message
Thanks Ed!
Took the words out of my mouth.....fought this fight with networks group
here.
One fellow argued up and down that Cisco says all connections should be
hardcoded.....when I pushed back turns out his info was from like 1997
and was relevant only to 100Mb/s switches....He went back to Cisco and
they said to set everything to Auto/Auto.
Also, even in 100Mb/s world, hardcoded or auto is irrelevant if
connections are coming up properly at FULL Duplex.
Only issue is when connection are coming up at HALF Duplex.
IIRC, GigE requires Auto Neg in order to establish proper flow control,
so you'll actually get degraded performance if duplex is hardcoded on
GigE ports......
Also, on the switches and iSOS levels we had here, you could not
actually hard code the switch port to 1000/FULL. You could hardcode to
1000/Auto only for forced GigE, or 10/100 in HALF, FULL, or AUTO, but
there was a bug in the iSOS that the Networks guys were exploiting, that
if you hard code a port to 100/FULL, then change the speed to 1000
without changing the duplex mode, it would stay as 1000/FULL.
So, Cisco was attempting to force all GigE connections to Auto Negotiate
Duplex mode.
Paul
--=20
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu=20
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
> Sent: May 15, 2006 9:43 AM
> To: Martin, Jonathan (Contractor)
> Cc: Justin Piszcz; Biju Krishnan; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Error status 13 for Windows 2003
>=20
>=20
> On Mon, May 15, 2006 at 09:35:57AM -0400, Martin, Jonathan=20
> (Contractor) wrote:
> >=20
>=20
> 2 out of 3 isn't bad... Step 3 is only relevant for 100mbps=20
> connections,
> not GigE. I've never heard of a GigE connection negotiating=20
> incorrectly.=20
--biYV.44/i3UnYU.1sZrha.CGnyCtq
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
La version fran=C3=A7aise suit le texte anglais.
---------------------------------------------------------------------------=
---------
This email may contain privileged and/or confidential information, and the =
Bank of
Canada does not waive any related rights. Any distribution, use, or copying=
of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediat=
ely from
your system and notify the sender promptly by email that you have done so.=20
---------------------------------------------------------------------------=
---------
Le pr=C3=A9sent courriel peut contenir de l'information privil=C3=A9gi=C3=
=A9e ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute dif=
fusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient pa=
r une
personne autre que le ou les destinataires d=C3=A9sign=C3=A9s est interdite=
Si vous recevez
ce courriel par erreur, veuillez le supprimer imm=C3=A9diatement et envoyer=
sans d=C3=A9lai =C3=A0
l'exp=C3=A9diteur un message =C3=A9lectronique pour l'aviser que vous avez =
=C3=A9limin=C3=A9 de votre
ordinateur toute copie du courriel re=C3=A7u.
--biYV.44/i3UnYU.1sZrha.CGnyCtq--
|
