Re: Force 100 Full Duplex (V210)
- From: Rick Jones <rick.jones2@xxxxxx>
- Date: Fri, 16 Jun 2006 20:04:38 GMT
rahan <rahan@xxxxxxxxx> wrote:
Thank You Thiemo.
I need to force 100 full because by using cisco switches with
auto-negociation parameter, it generate errors packet!! when i force
100 Full, i dont have any errors...
So, i olso force 100 Full on the switche.
Problem collision with half duplex...
What sort of collision? "Normal" collisions in half-duplex are, well,
normal :)
Auto Neg is practical to use only with old network card which no
talk on mode 100 Full...
I tend to disagree. I've had quite a lot of success with autoneg.
So, by forcing 100 Full, it's reduce errors et make network more
fast.
I may have misinterpreted between the lines above, but just in case,
this might be useful information:
How 100Base-T Autoneg is supposed to work:
When both sides of the link are set to autoneg, they will "negotiate"
the duplex setting and select full-duplex if both sides can do
full-duplex.
If one side is hardcoded and not using autoneg, the autoneg process
will "fail" and the side trying to autoneg is required by spec to use
half-duplex mode.
If one side is using half-duplex, and the other is using full-duplex,
sorrow and woe is the usual result.
So, the following table shows what will happen given various settings
on each side:
Auto Half Full
Auto Happiness Lucky Sorrow
Half Lucky Happiness Sorrow
Full Sorrow Sorrow Happiness
Happiness means that there is a good shot of everything going well.
Lucky means that things will likely go well, but not because you did
anything correctly :) Sorrow means that there _will_ be a duplex
mis-match.
When there is a duplex mismatch, on the side running half-duplex you
will see various errors and probably a number of _LATE_ collisions
("normal" collisions don't count here). On the side running
full-duplex you will see things like FCS errors. Note that those
errors are not necessarily conclusive, they are simply indicators.
Further, it is important to keep in mind that a "clean" ping (or the
like - eg "linkloop" or default netperf TCP_RR) test result is
inconclusive here - a duplex mismatch causes lost traffic _only_ when
both sides of the link try to speak at the same time. A typical ping
test, being synchronous, one at a time request/response, never tries
to have both sides talking at the same time.
Finally, when/if you migrate to 1000Base-T, everything has to be set
to auto-neg anyway.
rick jones
--
The glass is neither half-empty nor half-full. The glass has a leak.
The real question is "Can it be patched?"
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
.
- Follow-Ups:
- Re: Force 100 Full Duplex (V210)
- From: Ceri Davies
- Re: Force 100 Full Duplex (V210)
- References:
- Force 100 Full Duplex (V210)
- From: rahan
- Re: Force 100 Full Duplex (V210)
- From: Thiemo Nordenholz
- Re: Force 100 Full Duplex (V210)
- From: rahan
- Force 100 Full Duplex (V210)
- Prev by Date: Re: SMF problems; where to start? Please help!!
- Next by Date: SVM: tearing down and putting back a RAID 5 on the same system?
- Previous by thread: Re: Force 100 Full Duplex (V210)
- Next by thread: Re: Force 100 Full Duplex (V210)
- Index(es):
Relevant Pages
|