Interface
name
|
Displays
the name of the current interface. For example, TenGigE 0/1/0/1.
|
Interface
state
|
Displays
the state of the interface. For example, the interface is in the
administratively up state.
|
Interface
state transitions
|
Displays
the number of times since the last reload that the interface transitioned from
the administratively up state to the administrative down state and from the
administratively down state to the administratively up state.
|
line
protocol state
|
Displays
the state of the Layer 2 line protocol. This field may be different from the
interface state if, for example, a keepalive failure has brought down the Layer
2.
Note
|
The line
protocol state is not the same as the protocol state displayed in the
show ip
interfaces command, because it is the state of Layer 2 (media)
rather than Layer 3 (IP protocol).
|
|
Hardware
|
Displays
the current hardware type.
|
Internet
address is
n.n.n.n/n
|
Displays
the Layer 2 address (MAC address for Ethernet interfaces).
Note
|
Enter
the
mac-address
command to configure the hardware address.
|
|
bia
|
Displays
the burned-in address (BIA) for the interface. The BIA is the default L2 (MAC)
address for the interface.
Note
|
The BIA
is not configurable.
|
|
description
|
Displays
the user-defined string that is associated with the interface.
Note
|
Enter
the
description
command to configure the description associated with the interface.
|
|
Internet
Address
|
Displays
the Layer 3 (IP) address for the interface.
Note
|
Enter
the
ipv4 address
command to configure the internet address for the interface.
|
|
MTU
|
Displays
the maximum transmission unit (MTU) for the interface. The MTU is the maximum
packet size that can be transmitted over the interface.
Note
|
The MTU
field indicates the interface MTU. Enter the
mtu command
to configure a lower MTU value at the Layer 3 level.
|
|
BW
|
Displays
the bandwidth of the interface in kbps.
|
reliability
|
Displays
the proportion of packets that are not dropped and do not have errors.
Note
|
The
reliability is shown as a fraction of 255.
|
|
txload
|
Indicates
the traffic flowing out of the interface as a proportion of the bandwidth.
Note
|
The
txload is shown as a fraction of 255.
|
|
rxload
|
Indicates
the traffic flowing into the interface as a proportion of the bandwidth.
Note
|
The
rxload is shown as a fraction of 255.
|
|
Encapsulation
|
Layer 2
encapsulation installed on the interface.
|
CRC
|
Indicates
the length of the cyclic redundancy check (CRC), in bytes.
Note
|
The CRC
is not present for all interface types.
|
Note
|
Enter
the
pos crc
command to configure the CRC.
|
|
loopback
or controller loopback
|
Indicates
whether the hardware has been configured to be looped back.
Note
|
Enter
the
loopback
command to configure the loopback or controller loopback.
|
|
keepalive
|
Displays
the configured keepalive value, in seconds.
Note
|
Enter
the
keepalive command to configure the value of the keepalive
field.
|
Note
|
The
keepalive
field may not be present if it is not applicable to the interface type.
|
|
Duplexity
|
Displays
the duplexity of the link.
Note
|
This
field is present only for shared media.
|
Note
|
For some
interface types, you can configure the duplexity by entering the
full-duplex
and
half-duplex
commands.
|
|
Speed
|
Speed and
bandwidth of the link in Mbps. This field is present only when other parts of
the media info line are also displayed (see duplexity and media type).
|
Media Type
|
Media type
of the interface.
|
output
flow control
|
Whether
output flow control is enabled on the interface.
|
input flow
control
|
See output
flow control.
|
ARP type
|
Address
Resolution Protocol (ARP) type used on the interface. This value is not
displayed on interface types that do not use ARP.
|
ARP
timeout
|
ARP
timeout in
hours:mins:secs. This value is configurable using the
arp timeout
command.
|
Last
clearing of counters
|
Time since
the following counters were last cleared using the
clear
counters exec command in
hours:mins:secs.
|
5 minute
input rate
|
Average
number of bits and packets received 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).
Note
|
The
5-minute period referenced in the command output is a load interval that is
configurable under the interface. The default value is 5 minutes.
|
Note
|
The
5-minute input should be used only as an approximation of traffic per second
during a given 5-minute period. This rate is exponentially weighted average
with a time constant of 5 minutes. A period of four time constants must pass
before the average is within two percent of the instantaneous rate of a uniform
stream of traffic over that period.
|
|
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).
Note
|
The
5-minute period referenced in the command output is a load interval that is
configurable under the interface. The default value is 5 minutes.
|
Note
|
The
5-minute output should be used only as an approximation of traffic per second
during a given 5-minute period. This rate is exponentially weighted average
with a time constant of 5 minutes. A period of four time constants must pass
before the average is within two percent of the instantaneous rate of a uniform
stream of traffic over that period.
|
|
packets
input
|
Number of
packets received on the interface that were successfully delivered to higher
layers.
|
bytes
input
|
Total
number of bytes successfully received on the interface
|
total
input drops
|
Total
number of packets that were dropped after they were received. This includes
packets that were dropped due to configured quality of service (QoS)
or
access control list (ACL)
policies.
QoS
drops include policer drops, WRED drops, and tail drops.
This does not include drops due to unknown Layer 3
protocol.
|
drops for
unrecognized upper-level protocol
|
Total
number of packets that could not be delivered because the necessary protocol
was not configured on the interface.
|
Received
broadcast packets
|
Total
number of Layer 2 broadcast packets received on the interface. This is a subset
of the total input packet count.
|
Received
multicast packets
|
Total
number of Layer 2 multicast packets received on the interface. This is a subset
of the total input packet count.
|
runts
|
Number of
received packets that were too small to be handled. This is a subset of the
input errors count.
|
giants
|
Number of
received packets that were too large to be handled. This is a subset of the
input errors count.
|
throttles
|
Number of
packets dropped due to throttling (because the input queue was full).
|
parity
|
Number of
packets dropped because the parity check failed.
|
input
errors
|
Total
number of received packets that contain errors and hence cannot be delivered.
Compare this to total input drops, which counts packets that were not delivered
despite containing no errors.
|
CRC
|
Number of
packets that failed the CRC check.
|
frame
|
Number of
packets with bad framing bytes.
|
overrun
|
Number of
overrun errors experienced by the interface. Overruns represent the number of
times that the receiver hardware is unable to send received data to a hardware
buffer because the input rate exceeds the receiver's ability to handle the
data.
|
ignored
|
Total
number of ignored packet errors. Ignored packets are those that are discarded
because the interface hardware does not have enough internal buffers. Broadcast
storms and bursts of noise can result in an increased number of ignored
packets.
|
abort
|
Total number of terminated errors on the interface.
|
packets
output
|
Number of
packets received on the interface that were successfully delivered to higher
layers.
|
bytes
output
|
Total
number of bytes successfully received on the interface.
|
total
output drops
|
Number of
packets that were dropped before being transmitted. This includes packets that
were dropped due to configured quality of service (QoS), (policer drops, WRED
drops, and tail drops).
|
Received
broadcast packets
|
Number of
Layer 2 broadcast packets transmitted on the interface. This is a subset of the
total input packet count.
|
Received
multicast packets
|
Total
number of Layer 2 multicast packets transmitted on the interface. This is a
subset of the total input packet count.
|
output
errors
|
Number of
times that the receiver hardware was unable to handle received data to a
hardware buffer because the input rate exceeded the receiver's ability to
handle the data.
|
underruns
|
Number of
underrun errors experienced by the interface. Underruns represent the number of
times that the hardware is unable to transmit data to a hardware buffer because
the output rate exceeds the transmitter’s ability to handle the data.
|
applique
|
Number of
applique errors.
|
resets
|
Number of
times that the hardware has been reset. The triggers and effects of this event
are hardware-specifc.
|
output
buffer failures
|
Number of
times that a packet was not output from the output hold queue because of a
shortage of MEMD shared memory.
|
output
buffers swapped out
|
Number of
packets stored in main memory when the output queue is full; swapping buffers
to main memory prevents packets from being dropped when output is congested.
The number is high when traffic is bursty.
|
carrier
transitions
|
Number of
times the carrier detect (CD) signal of a serial interface has changed state.
|