Virtual-Access ... is {up | down | administratively down}
|
Indicates whether the interface is currently active (whether carrier detect is present), is inactive, or has been taken down
by an administrator.
|
line protocol is {up | down | administratively down}
|
Indicates whether the software processes that handle the line protocol consider the line to be usable (that is, whether keepalives
are successful).
|
Hardware is
|
Type of interface. In this case, the interface is a dynamically created virtual access interface that exists on a vty line.
|
MTU
|
Maximum transmission unit for packets on the virtual access interface.
|
BW
|
Bandwidth of the virtual access interface, in kbps.
|
DLY
|
Delay of the virtual access interface, in microseconds.
|
reliability
|
Reliability of the virtual access interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential
average over five minutes.
|
txload, rxload
|
Load on the virtual access interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential
average over 5 minutes. The calculation uses the value from the
bandwidth interface configuration command.
-
txload-- Transmit load on the virtual access interface as a value of ½55 calculated as an exponential average over 5 minutes.
-
rxload-- Receive load on the virtual access interface as a value of ½55 calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to the virtual access interface.
|
loopback
|
Test in which signals are sent and then directed back toward the source at some point along the communication path. Used
to test network interface usability.
|
DTR
|
Data terminal ready. An RS232-C circuit that is activated to let the DCE know when the DTE is ready to send and receive data.
|
LCP open | closed | req sent
|
Link Control Protocol (for PPP only; not for Serial Line Internet Protocol (SLIP)). LCP must come to the open state before
any useful traffic can cross the link.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by a virtual access interface. This
value indicates when a dead interface failed.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by a virtual access interface.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the virtual access interface was last reset because of a transmission
that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is
displayed. If that field overflows, asterisks are displayed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) 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 lengthy to be displayed.
Zeros (0:00:00) indicate that the counters were cleared more than 231 milliseconds (ms) and less than 232 ms ago.
|
Input queue, drops
|
Number of packets in input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets
dropped because of a full queue.
|
Queueing strategy
|
Type of queueing selected to prioritize network traffic. The options are first-come-first-served (FCFS) queueing, first-in-first-out
queueing (FIFO), weighted fair queueing, priority queueing, and custom queueing.
|
Output queue
|
Packets in output queues. Represented by the maximum size of the queue followed by a slash and the number of packets dropped
because of a full queue. For example, if the output queue is 45/15, 45 is the maximum size of the queue and 15 is the number
of packets dropped.
|
5 minute input rate, 5 minute output rate
|
Average number of bits and packets transmitted per second in the last five 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.
|
broadcasts
|
Total number of broadcast or multicast packets received by the virtual access interface.
|
runts
|
Number of packets that are discarded because they are smaller than the medium's minimum packet size.
|
giants
|
Number of packets that are discarded because they exceed the medium's maximum packet size.
|
input errors
|
Total number of no-buffer, runts, giants, cyclic redundancy checks (CRCs), frame, overrun, ignored, and abort counts. Other
input-related errors can also increment the count, so that this sum might not balance with the other counts.
|
CRC
|
Counter that reflects when the cyclic redundancy checksum generated by the originating LAN station or far-end device does
not match the checksum calculated from data received. On a LAN, this often indicates noise or transmission problems on the
LAN interface or the LAN bus. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
On a serial link, CRCs often indicate noise, gain hits, or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually
the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to send received data to a hardware buffer because the input rate
exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the virtual access interface because the interface hardware ran low on internal buffers.
These buffers are different from the system buffers mentioned in the description of the no buffer field. Broadcast storms
and bursts of noise can cause the ignored count to be incremented.
|
abort
|
Illegal sequence of one bits on a virtual access interface. This usually indicates a clocking problem between the virtual
access interface and the data link equipment.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times the far-end transmitter has been running faster than the near-end communication server's receiver can handle.
Underruns may never be reported on some virtual access interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the virtual access interface being examined.
Note that this might not balance with the sum of the enumerated output errors, because some datagrams might have more than
one error, and others might have errors that do not fall into any of the tabulated categories.
|
collisions
|
Number of packets colliding.
|
interface resets
|
Number of times a virtual access interface has been completely reset. A reset can happen if packets queued for transmission
were not sent within several seconds. Resetting 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 virtual access 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 a virtual access interface is looped back or shut down.
|
output buffer failures
|
Number of outgoing packets dropped from the output buffer.
|
output buffers swapped out
|
Number of times the output buffer was swapped out.
|
carrier transitions
|
Number of times the carrier detect (CD) signal of a virtual access interface has changed state. Indicates modem or line problems
if the CD line changes state often. If data carrier detect (DCD) goes down and comes up, the carrier transition counter increments
two times.
|