|
Field |
Description |
|
Network-Analyzer |
Indicates whether the analysis module interface hardware is currently active. The analysis module interface is the router-side interface for the internal Ethernet segment between the router and the NAM network module.
If the analysis module interface hardware is operational, the output states that the "Network-Analyzer 1/0 is up." If the interface has been taken down by an administrator, the output states that the "Network-Analyzer 1/0 is administratively down." |
|
line protocol is |
Indicates whether the software processes that handle the line protocol consider the line usable or whether the line has been taken down by an administrator. |
|
Hardware is...address is |
Hardware type and address. |
|
MTU |
Maximum transmission unit (MTU) of the analysis module interface. |
|
BW |
Bandwidth of the interface, in kbps. |
|
DLY |
Delay of the interface, in microseconds. |
|
reliability |
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes. |
|
txload |
Transmit load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. |
|
rxload |
Receive load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. |
|
Encapsulation |
Encapsulation method assigned to the interface. |
|
loopback |
Indicates whether or not loopback is set. |
|
Keepalive |
Indicates whether or not keepalives are set and the interval between keepalives if they have been set. |
|
ARP type...ARP Timeout |
Type of Address Resolution Protocol (ARP) assigned and length of timeout. |
|
Last input |
Number of hours, minutes, and seconds since the last packet was successfully received by the interface and processed locally on the router. This field is useful for detecting when a dead interface failed.
Note  This field is not updated by fast-switched traffic. |
|
output |
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. This field is useful for detecting when a dead interface failed. |
|
output hang |
Number of hours, minutes, and seconds (or never) since the interface was last reset because a transmission took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed. |
|
Last clearing |
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
Asterisks (***) indicate that the elapsed time is too large to be displayed. |
|
Input queue |
Number of packets in the input queue. Each number is followed by a slash, the maximum size of the queue, the number of packets dropped because of a full queue, and the number of times that queued packets have been discarded. |
|
Total output drops |
Number of packets in the output queue that have been dropped because of a full queue. |
|
Queueing strategy |
Queueing strategy applied to the interface, which is configurable under the interface. The default is FIFO (first-in, first-out). |
|
Output queue |
Number of packets in the output queue, and the maximum size of the queue. Each number is followed by a slash. |
|
5 minute input rate, 5 minute output rate |
Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic that it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within 2 percent of the instantaneous rate of a uniform stream of traffic over that period.
Note The 5-minute period referenced in this output is a load interval that is configurable under the interface. The default value is
5 minutes. |
|
packets input |
Total number of error-free packets received by the system. |
|
bytes |
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. |
|
no buffer |
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events. |
|
Received...broadcasts |
Number of broadcasts received. |
|
runts |
Number of packets that are discarded because they are smaller than the minimum packet size of the medium. For instance, any Ethernet packet that is less than 64 bytes is considered a runt. |
|
giants |
Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant. |
|
throttles |
Number of times that the interface requested another interface within the router to slow down. |
|
input errors |
Errors that include runts, giants, no buffer, cyclic redundancy checksum (CRC), frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts. |
|
CRC |
Errors created when the CRC generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station that is transmitting bad data. |
|
frame |
Number of packets received incorrectly that have a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device. |
|
overrun |
Number of times that the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. |
|
ignored |
Number of received packets that were ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from system buffer space described. Broadcast storms and bursts of noise can cause the ignored count to increase. |
|
input packets with dribble condition detected |
Number of packets with dribble condition. Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame. |
|
packets output |
Total number of messages that have been transmitted by the system. |
|
bytes |
Total number of bytes, including data and MAC encapsulation, that have been transmitted by the system. |
|
underruns |
Number of times that the transmitter has run faster than the router could handle. This may never be reported on some interfaces. |
|
output errors |
Sum of all errors that prevented the final transmission of datagrams out of the interface that is being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories. |
|
collisions |
Number of messages that have been retransmitted because of an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets. |
|
interface resets |
Number of times an interface has been completely reset. This can happen if packets that were queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down. |
|
babbles |
Count of frames greater than 1518 bytes that have been transmitted, indicating that the transmitter has been on the interface longer than the time necessary to transmit the largest frame. |
|
late collision |
Number of late collisions. A collision becomes a late collision when it occurs after the preamble has been transmitted. |
|
deferred |
Deferred indicates that the chip, while ready to transmit a frame, had to defer because the carrier was asserted. |
|
lost carrier |
Number of times that the carrier was lost during transmission. |
|
no carrier |
Number of times that the carrier was not present during the transmission. |
|
output buffer failures, output buffers swapped out |
Number of failed buffers and number of buffers swapped out. |
