Filter
Top Products
29
Collision domain:
Selects which collision domain (10 or 100
Mbps hubs) to view. All hubs in the stack running at the same speed
are in the same collision domain.
Change hub speed
Green (left)
Solid = Link
Blink = Activity
Amber (right)
Solid = Disabled
Blink = Wrong Speed
Intel Express
10/100 Stackable Hub
Collision
Managed
Status
Power10BASE-T
100BASE-TX
12345678 910111213141516 17 18 19 20 21 22 23 24
Amber (right)
Solid = Disabled
Blink = Wrong Speed
Intel Express
10/100 Stackable Hub
Change hub speed
Collision
Managed
Status
Power10BASE-T
100BASE-TX
Green (left)
Solid = Link
Blink = Activity
12345678 9101112
Management Module
Main Menu:
Stats Config >
Reset
Esc
Change hub speed
Green (left)
Solid = Link
Blink = Activity
Amber (right)
Solid = Disabled
Blink = Wrong Speed
Intel Express
10/100 Stackable Hub
Collision
Managed
Status
Power10BASE-T
100BASE-TX
12345678 910111213141516 17 18 19 20 21 22 23 24
Change hub speed
Green (left)
Solid = Link
Blink = Activity
Amber (right)
Solid = Disabled
Blink = Wrong Speed
Intel Express
10/100 Stackable Hub
Collision
Managed
Status
Power10BASE-T
100BASE-TX
12345678 910111213141516 17 18 19 20 21 22 23 24
100 Mbps
100 Mbps
10 Mbps
10 Mbps
100 Mbps
collision domain
10 Mbps
collision domain
Utilization:
The percentage of Ethernet bandwidth (10 or 100
Mbps) being used by devices attached to the hubs. All hubs in the
stack running at the same speed are in the same collision domain and
share either 10 or 100 Mbps of bandwidth.
Collisions:
The number of collisions detected. Collisions are
normal in an Ethernet network. They tend to rise as network
utilization rises.
Frames:
The number of frames detected without errors. Includes
unicast, broadcast, and multicast frames. It does not include frames
received with frames too long, runt, FCS, or alignment errors.
Octets:
The number of octets (bytes) contained in frames received
that had no errors. This includes octets in unicast, broadcast, and
multicast frames. It also includes octets after the start frame delimiter
up to FCS, but not including FCS octets.
FCS errors:
The number of frames detected that are free of partial
octets and do not pass the FCS check. Usually caused by adapter
underrun (when the adapter can’t get enough PCI bandwidth). FCS
errors do not necessarily indicate that data has been lost.
Alignment errors:
The number of frames detected that contain
partial octets and do not pass the FCS check. This is usually caused
by a faulty adapter or poor quality cabling.
NOTE
Since frames vary in length,
it’s best to look at the octet
count to see how much traffic
is passing through the hubs.