Hi Runner,
There is no limitation in the number of hubs that can be on a segment, but
there is a practical limit of where the performance begins to dive. As you
pointed out, the guideline has always been no more than three and this still
holds.
Of course, switches are so cheap and most can handle span/ mirror ports so
there really isn't a use for them in a modern network. I would even argue
against workgroup switches outside of IT's control, but that isn't really a
fight for this forum.
I would seriously evaluate any plans you have to include hubs as you do
increase contention for network resources through collisions and you remove
any ability for full-duplex communication. You'll also note that 100-half
was not part of the original spec and was added later to support legacy
equipment. Though it is claimed to be supported, it simply doesn't perform
consistently.
Finally, the broadcast nature of hubs forces all attached devices to make
forwarding decisions and can lead to switch or server CPU utilization to
increase as they have to make decisions on each packet. This also opens you
up to security problems as the promiscuous nature of hubs make them an east
eavesdropping target.
With all of these problems, it hardly seems worth it.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
www.techsterity.com
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"(E-Mail Removed)" wrote:
> I read somewhere that fast Ethernet (100 mbps) networks only allowed
> for one hub between hosts, whereas with the older 10 mbps Ethernet you
> could have 3. Is there some rule like this for Ethernet switches at
> current network speeds? From reading, I would infer that they can
> possibly be chained, since it appears that network segments can be
> connected by switches, while all the segments can still be in one
> subnet served by one router. What is the best way to connect up
> multiple Ethernet segments in one subnet? Thanks for any leads to
> info on this.
>
>