AT&T Metro E services are generally hard set and personally, I generally go
this route as well. I find a lot of problems with autonegotiation between
vendors. Company J handles this pretty well on their switching and almost
always negotiations set up correctly and company C generally in my
experience gets it wrong and likes to fall in to half duplex even though the
far end is negotiated to full. Never had any issues though after hard
setting both sides so it just became a matter of habbit. Maybe its
something I should revisit.
-----Original Message-----
From: Mark Tinka
Sent: Tuesday, August 02, 2011 6:45 AM
To: [email protected]
Cc: Gert Doering
Subject: Re: [c-nsp] does duplex mismatch affect UDP throughput?
On Sunday, July 31, 2011 02:47:38 PM Gert Doering wrote:
If you order a cross-city ethernet link from a telco,
they usually force duplex/speed settings on their gear
and turn off autonegotiation.
Funny, we tend to do the opposite these days :-).
I can understand closed networks and enterprise/corporate
networks still going the "hard-coding" route, but it'd be
interesting to learn if a vast majority of service providers
are still doing the same these days (yes, it's still common
to find hard-coding in service provider environments as well
these days, but I just wonder whether the number is falling,
rising or stagnant).
I suspect thoughts on this are bound to be academic :-).
Mark.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
