Port-channel1
is up, line protocol is up
|
Indicates the
bundle interface is currently active and can transmit and receive or it has
been taken down by an administrator.
|
Hardware is
|
Hardware type
(Gigabit EtherChannel).
|
address is
|
Address being
used by the interface.
|
MTU
|
Maximum
transmission unit of the interface.
|
BW
|
Bandwidth of
the interface, in kilobits per second.
|
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.
|
tx load
rxload
|
Transmit and
receive load on the 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.
|
Encapsulation
|
Encapsulation
type assigned to the interface.
|
loopback
|
Indicates if
loopbacks are set.
|
keepalive
|
Indicates if
keepalives are set.
|
ARP type
|
Address
Resolution Protocol (ARP) type on the interface.
|
ARP Timeout
|
Number of
hours, minutes, and seconds an ARP cache entry stays in the cache.
|
No. of active
members in this channel
|
Number of
bundled ports (members) currently active and part of the port channel group.
|
Member
<no. > Gigabit
Ethernet: <no. /no. /no. >
|
Number of the
bundled port and associated Gigabit Ethernet port channel interface.
|
Last input
|
Number of
hours, minutes, and seconds since the last packet was successfully received by
an interface and processed locally on the Device. Useful for knowing when a
dead interface failed. This counter is updated only when packets are
process-switched, not when packets are fast-switched.
|
output
|
Number of
hours, minutes, and seconds since the last packet was successfully transmitted
by an interface. This counter is updated only when packets are
process-switched, not when packets are fast-switched.
|
output hang
|
Number of
hours, minutes, and seconds since the 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 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.
Variables that might affect routing (for example, load and reliability) are not
cleared when the counters are cleared.
***
indicates that the elapsed time is too long to be displayed.
0:00:00
indicates that the counters were cleared more than 231 ms and less than 232 ms
ago.
|
Input queue
|
Number of
packets in the input queue and the maximum size of the queue.
|
Queueing
strategy
|
First-in,
first-out queueing strategy (other queueing strategies you might see are
priority-list, custom-list, and weighted fair).
|
Output
queue
|
Number of
packets in the output queue and the maximum size of the queue.
|
5 minute
input rate 5 minute output rate
|
Average
number of bits and packets received or transmitted per second in the last 5
minutes.
|
packets
input
|
Total
number of error-free packets received by the system.
|
bytes
(input)
|
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. Broadcast storms on Ethernet lines 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 interface.
|
runts
|
Number of
packets that are discarded because they are smaller than the minimum packet
size for the medium.
|
giants
|
Number of
packets that are discarded because they exceed the maximum packet size for the
medium.
|
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
|
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. A high
number of CRCs is usually the result of collisions or a station transmitting
bad data. On a serial link, CRCs usually 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 pass received data to a
hardware buffer because the input rate exceeded the receiver’s capacity for
handling the data.
|
ignored
|
Number of
received packets ignored by the interface because the interface hardware ran
low on internal buffers. These buffers are different than the system buffers
mentioned previously in the buffer description. Broadcast storms and bursts of
noise can cause the ignored count to be incremented.
|
watchdog
|
Number of
times the watchdog receive timer expired.
|
multicast
|
Number of
multicast packets received.
|
packets
output
|
Total
number of messages transmitted by the system.
|
bytes
(output)
|
Total
number of bytes, including data and MAC encapsulation, transmitted by the
system.
|
underruns
|
Number of
times that the far-end transmitter has been running faster than the near-end
Device’s receiver can handle.
|
output
errors
|
Sum of all
errors that prevented the final transmission of datagrams out of the interface
being examined. Note that this might not balance with the sum of the enumerated
output errors, as some datagrams can have more than one error, and others can
have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of
messages retransmitted because of an Ethernet collision. 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 queued
for transmission were not sent within a certain interval. If the system notices
that the carrier detect line of an interface is up but the line protocol is
down, the system periodically resets the interface in an effort to restart that
interface. Interface resets can also occur when an unrecoverable interface
processor error occurred, or when an interface is looped back or shut down.
|
babbles
|
The
transmit jabber timer expired.
|
late
collision
|
Number of
late collisions. Late collision happens when a collision occurs after
transmitting the preamble. The most common cause of late collisions is that
your Ethernet cable segments are too long for the speed at which you are
transmitting.
|
deferred
|
Indicates
that the chip had to defer while ready to transmit a frame because the carrier
was asserted.
|
lost
carrier
|
Number of
times the carrier was lost during transmission.
|
no carrier
|
Number of
times the carrier was not present during the transmission.
|
PAUSE
output
|
Not
supported.
|
output
buffer failures
|
Number of
times that a packet was not output from the output hold queue because of a
shortage of 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.
|