Auto-Segmentation
These hubs will automatically disable (auto-segment) a port if it experiences excessive
collisions (greater than 30 consecutive collisions). The port will automatically return to
operation if the excessive collision condition is removed and normal traffic is restored.
Auto-segmentation can also be caused by improper termination of cabling attached to the
AUI or ThinLAN ports, or by having nothing attached to the ThinLAN port when it is
enabled.
If a port is auto-segmented, its port LED and the Fault LEDs will flash. A segmented
ThinLAN port will not cause the Fault LED to flash unless Thinwatch has been explicitly
enabled with the Thinwatch console command. The Thinwatch command is described in
chapter 3.
If a port is auto-segmented, only the LAN segment attached to that port is affected. The
other LAN segments will operate normally.
If a port is disabled explicitly, by using the console port, or from an HP network
management station, (HP 28688B and HP 28699A only) it must be enabled explicitly. It
will not be enabled automatically.
Link Beat
Type 10Base-T devices use a signal called link test pulse (link beat in HP documentation).
This signal informs a hub of the presence of a device connected to it over twisted-pair cable
and the integrity of the twisted-pair link between them. If your network has a mixture of
10Base-T and non-10Base-T products, you may have to disable link beat on some of them.
For the HP EtherTwist hubs, disable link beat on any port that is connected to a
non-10Base-T device. You can do this through the Link beat console command (see
chapter 3, “Operation”, in this manual for command details), or from an HP network
management station (HP 28688B and HP 28699A only — see the network management
product documentation for instructions).
The hub will not transmit packets out ports that do not sense the link beat signal unless
link beat is disabled on that port.
Introducing the HP EtherTwist Hub/12, Hub Plus, and Hub Plus/48 1-7
Commenti su questo manuale