Re: errors at NIC
- From: "Chuck Whealton" <chuck_whealton@xxxxxxxxx>
- Date: 16 Mar 2007 15:06:41 -0700
On Mar 5, 3:58 pm, Rick Jones <rick.jon...@xxxxxx> wrote:
pp <p...@xxxxxx> wrote:
1204702 receive failures, reasons include:
32 frame too long
612823 frame check sequence errors
591847 frame error
...
full_duplex = 1
autoneg_enable = 0
What could be the problem in configuring the tu0 interface?
If I were to guess, it would be the hardcoding of the duplex setting.
Here is some boilerplate about 100BT autonegotiation that may be
helpful:
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.
--
Wisdom Teeth are impacted, people are affected by the effects of events.
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...
Yea, I'd have to agree with Rick on this one. When operating at 100BT/
FD, it was my experience it that it was always best to hardset the
speed and duplex on both sides. It just made life so much easier. We
ended up with flipped duplex settings on one side or the other just a
couple too many times out of nowhere.
Never got to use the Alphas by the time gigabit rolled around, but on
HP-UX, yea, for gigabit it had to be set to autonegotiate on both
sides.
I miss the AlphaServers and Tru64 UNIX.
Charles R. Whealton
Charles Whealton @ pleasedontspam.com
.
- References:
- errors at NIC
- From: pp
- Re: errors at NIC
- From: Rick Jones
- errors at NIC
- Prev by Date: Re: NFS-server on Tru64 5.1A b0rks!
- Next by Date: Analysis3
- Previous by thread: Re: errors at NIC
- Next by thread: NFS-server on Tru64 5.1A b0rks!
- Index(es):
Relevant Pages
|
|
