|
The following MIB variables are the ones you will most often encounter and use. If you are looking for information about other MIB variables not listed here, find the information in Network Manager.
- Select part or all of the MIB table and click Edit. The Edit Table Entry dialog box is displayed.
- Select the MIB variable, then click Expand.
AlignErrors
The number of frames detected that contain partial octets and do not pass the FCS check.
AutoPartitions
The number of times this port was automatically partitioned. Auto partitioning occurs when 32 consecutive collisions are detected on the port. If a single port is partitioned, a network adapter connected to the port is probably malfunctioning. If several ports are partitioned, traffic on the segment is probably too high.
SrcIndx
Because a single NMM can manage a stack of hubs, each of which have multiple ports and a media adapter, a special numbering scheme identifies each port. SrcIndx is the label for that 6-digit number.
The first digit of the SrcIndx number shows which statistics that row or column displays:
SrcIndx Meaning
| 1xxxxx |
Shows how many hubs are in the stack, using the second digit of SrcIndx. The other digits can be ignored. For example, 132001 means there are 3 hubs in the stack. |
|
2xxxxx |
Shows statistics for a single port of a single hub. The second digit of SrcIndx shows which hub, and the last two digits show which port. The other digits can be ignored. For example, 240012 shows statistics for port 12 of hub 4 in a stack of hubs. |
|
4xxxxx |
Shows total statistics for a single hub, excluding the media adapter (if any). The second digit of SrcIndx specifies hub. The other digits can be ignored. For example, 450001 shows totals for hub 5, not including the media adapter. |
|
6xxxxx |
Shows total statistics for a single hub, including the media adapter (if any). The second digit of SrcIndx specifies the hub. The other digits can be ignored. For example, 620001 shows totals for hub 1, including the media adapter. |
|
8xxxxx |
Shows total statistics for an entire stack of hubs. The other digits can be ignored. For example, 802001 shows totals for the stack. |
Normally, the hub units are numbered 1, 2, 3, and so on rom the top of a stack. If you've renumbered the hubs from the NMM's management console (through the NMM serial port), hub units may be numbered 2, 3, 4, and so on. To be sure, scan the SrcIndx numbers in the hub statistics table.
If the first SrcIndx number beginning with 2 has another 2 as the second digit (22xxxx), then hubs are numbered 2, 3, 4, and so on. If the first SrcIndx number beginning with 2 has a 1 as the second digit (21xxxx), then hubs are numbered 1, 2, 3, and so on.
CRCAlignErrors
A combined count of FCS errors and align errors. Possible causes include bad cables and adapter underrun.
LateColls
The number of late receive collisions detected. Usually indicates a duplex mismatch between the switch and the workstation or a network topology problem, such as daisy-chaining Class I repeaters, cables longer than 100 meters, or bad cables.
VeryLongEvents
The number of times MAU jabber lockup protection (MJLP) was detected. MJLP occurs when transmission of data exceeds five msec in duration (OctetCount greater than maxFramSize). Very long events can be caused by a bad node, bad port, or an incorrect speed setting (for example, a 10BASE-T adapter on a 100BASE-T network).
FcsErrors
The number of frames detected that are free of partial octets but 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.
This applies to:
| 
