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.
Statistic: Use ASor zto select the type of port statistics to view. Traffic is the other type of statistic option you can view (see page 31).
Update interval: Use AS or zto select the time period between updates. For example, an update interval of 5 sec. means the Console Manager collects and displays information from the Management Module every five seconds.
Speed: Displays the current speed of the hub in the Hub: field.
Type: Displays the
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. 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.
Frames too long: The number of frames detected that exceed the maximum permitted frame size of 1518 octets.
Short events: The number of fragments detected with ActivityDuration less than ShortEventMaxTime (greater than 74 bit times and less than 82 bit times). Usually indicates a network topology problem, such as connecting two Express hubs running at 100 Mbps with UTP cable (instead of Intel Cascade Cables in a stack), or using cables longer than 100 meters.
34
