Several commands from the Intel hub device viewer display information in the MIB table window.

IpRouteEntry
The IP Routing Table command, on the Intel device viewer's Agent menu, displays the ipRouteEntry MIB table. This table contains technical information about the path of IP packets sent by this device.

IpNetToMediaEntry
The ARP Table command, on the Intel device viewer's Agent menu, displays the IpNetToMediaEntry MIB table. This table matches up IP addresses with MAC addresses for nearby devices recently contacted.

IfIndex
On a switch or router, the port number. On a hub, IfIndex is usually 1 because all ports in the stack are in the same segment.

NetAddress
The IP address of a nearby device that the selected device has contacted recently.

PhysAddress
The MAC address of the device with the IP address. Occasionally, an IP address appears here instead of a MAC address. There are two ways of showing the MAC address:

• Double-click the IP address and look at the PhysAddress box.

• From the Config menu in Network Manager, choose Options and turn off the Use MAC Address As Node Name option.

Type
The kind of ARP table entry, usually "dynamic". Entries may also be "static", which means they remain in the ARP table even when not used recently.

IcmpInfo
The ICMP Info/Stats command, on the Intel device viewer's Agent menu, displays the icmpInfo MIB table. This table contains technical information about ICMP messages sent to or from the device. IP routing, error handling, and ping functions use ICMP.

SnmpInfo
The SNMP Info/Stats command, on the Intel device viewer's Agent menu, displays the snmpInfo MIB table. This table contains technical information about SNMP messages sent to or from the device.

One of the more useful statistics shown is InBadCommunityNames. Each time a management station tries to access the selected device using an incorrect SNMP community string, this counter increases by 1. A pattern of these errors could indicate attempts at unauthorized access to your network devices.

S5EnPStatEntry
Displays the MAC address of the last device connected to a hub port. This is useful in determining what type of device is connected to the hub.

SourceAddrChngs
The number of times the address connected to the port has changed since the last hub reset. If this number is more than one, a switch or router is probably connected to the port. If the number is one, a workstation or server is connected to the port.

LinkStatusChngs
The number of times the device's link status has changed from on to off or from off to on.

LastSourceAddr
The MAC address of the device last connected to the port. Occasionally, an IP address appears here instead of a MAC address. There are two ways of showing the MAC address:

• Double-click the IP address and look at the PhysAddress box.

• From the Config menu in Network Manager, choose Options and turn off the Use MAC Address As Node Name option.

To view the MAC address attached to a port, select Options from the Config menu and select Use MAC address as node name.

S5EnBStatEntry
Shows the statistics listed below:

SrcIndx
Identifies the port, hub, or stack the statistics pertain to. See Identifying a port in a MIB table for more information.

GoodOctets
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. Use the good octets count to estimate network utilization.

AlignErrors
The number of frames detected that contain partial octets and do not pass the FCS check.

FcsErrors
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.

Colls
The number of receive collisions detected. Collisions are normal in an Ethernet network. They tend to rise as network utilization rises.

LateColls
The number of late receive collisions detected. Usually indicates a network topology problem, such as connecting two Express hubs with UTP cable (instead of with cascade cables in a stack) or using cables longer than 100 meters.

AutoPartitions
The number of times this port was automatically partitioned. This condition occurs when 32 consecutive collisions are detected on the port. These collisions are due to excessive traffic on the segment, a malfunctioning port, or a malfunctioning adapter that is jabbering.

GoodFrms
The number of frames detected without errors. Includes unicast, broadcast, and multicast frames. Does not include frames received with frame-too-long, runt, FCS, or alignment errors.

BcastFrms
The number of frames that are detected without errors and are directed to the broadcast group address. Does not include multicast frames or frames received with frame-too-long, runt, FCS, or alignment errors.

McastFrms The number of frames that are detected without errors and are directed to a non-broadcast group address. Does not include frames received with frame-too-long, runt, FCS, or alignment errors.

Runts
The number of frames detected that are less than the minimum permitted frame size and have a good FCS.

TooLongFrms
The number of frames detected that exceed the maximum permitted frame size.

Fragments
The number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had a bad Frame Check Sequence (FCS) with either an FCS Error or an Alignment Error. This count includes runts (which are normal occurrences due to collisions) and noise hits.

VeryLongEvents
The number of times MAU jabber lockup protection (MJLP) was detected due to transmission of data that exceeded 5 msec in duration (octet count greater than maxFramSize). This information can be useful in identifying faulty devices or ports.

ShortEvents
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 with UTP cable (instead of with cascade cables in a stack) or using cables longer than 100 meters.

RateMismatches
A count of the occurrences of out of specification bit rates. This indicates the number of times the FIFO buffer overruns or underruns due to transmission rate errors.

BackOffFailures
This counter is incremented by one for each frame received on this port with collision and port activity time greater than 552 to 560 bit time.

ShortIPGs
A count of occurrences to a too short IPG (interpacket gap before a good packet) that were detected.

NullFrames
A count of the occurrences of frames received with no collision and whose octet count is equal to 0 and activity time is greater than the valid packet minimum time.

This applies to:

LANDesk* Network Manager