[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: load balanced nic


"A. Dreyer" <adreyer@adreyer.de> írta 2008-09-28 13:00-kor:
> > Second, its a bit hard to fix auto-negotiation in a vendors product such
> > as a switch, firewall or router. The sad fact is that not all hardware
> > plays nice with one another and you sometimes need to set the interfaces
> > to prevent problems. Yes that even means Gigabit interfaces. If the
> > interfaces negotiated correctly you would not configure the interface to
> > a set speed, only when they do not detect each other correctly. Maybe
> > that clears things up.
> If a device is sold as Gigabit-Switch/-Router/-Firewall and does not
> understand Gigabit auto-negotiation I would return it to the seller.
Yes! This is the correct attitude! I do not neither allow devices into my
network which doesn't respect standards. IEEE is not just a bunch of
idiots, and they don't do the standards just for enjoy themself.

Common problem, when some moron come to here with bridging enabled in
his/her notebook, and connect to an access port, and then that alternative
OS, whichs name is not spoken - the evil one :-D - starts to send PDUs
towards the access port, and then it's change its state to err-disabled.
When they come to me for complain about the unreliable network, I tell
them, what they did: From my viewpoint, they accross the network policy, so
they can be happy, that I still allow them to connect, and re-allow the
err-disabled port.

> During the specification of Gigabit Ethernet they tried to avoid the
> mistakes they made while defining 100Mbit/s and the auto-negotiation
> process in Gb/s is pretty clear - if any "Gigabit" device can not work
> with it I would expect other problems as well..
Yes! That's another correct observation! If a device doesn't comply a
standard which is so obvios, than what can do wrong too?
And the other observation is also correct: If you do too many hacks on your
network, it's usually undocumented, and it cause many other problems when
you connect devices which works correctly, and comply the standards.

PS.: Otherwise: I recently heard that, in the past few years, those "low
end manufacturers" like HP can create well-working devices which comply
standards ;-)

Summarized: If you make network with cheap devices, you pay it's price in
the TCO, with your many time you spent on debugging instead of operating,
and maybe the secondary consequences of the downtime is even higher if you
have to provide SLA or any kind of high availability.


Reply to: