Professional Documents
Culture Documents
In my opinion, a good network engineer must know the “show interface” in depth;
indeed, this command is useful to obtain various interface information like drop,
duplex mismatch, error, tx/rx load, …
Ciscozine-IOS#
Identify the hardware interface and the interface mac-address; the BIA aka Burned-In
(MAC) Address cannot be changed, while the “address“ can be changed with the
command “mac-address 0000.0000.fd90” under the interface configuration mode.
Remember: When the interface mac address is changed, the arp or mac address table
associated to the interface will be “linked” with the custom mac address!
Define the interface encapsulation; nowadays, you will see only the ARPA. In the past,
there were also SAP and SNAP encapsulation.
Loopbacks are an important part of troubleshooting; they are used to isolate the
fault on and end-to-end circuit (especially when the circuit is down). More
info http://www.cisco.com/…/tech_note09186a00800c93c4.shtml
Keepalives are used on the routers interfaces as hello mechanism to check the end to
end connectivity to the other end.Routers interface used this mechanism to check the
interface status.If you have no keepalive command its means that inerface status check
mechansim in disabled and router will not transmit any keepalive packet on the link.
Define the physical speed of the interface and if it works in half or duplex mode. The last
part of the line defines the type of the media.
ARP type defines the encapsulation type of the interface; tipically, for ethernet interface
is ARPA. The default ARP timeout is 4hours but can be customized using the
command “arp timeout [timeout]”
Last input never, output never, output hang never
Last input, output are the number of hours, minutes, and seconds since the last packet
was successfully received or transmitted by the interface.
Note: This counter is updated only when packets are process switched, not when
packets are fast switched.
It is the last time the clear counters command was issued since the last time the switch
was rebooted. The clear counters command is used to reset interface statistics.
The number of packets in the output queue. Size/max means the current number of
frames in the queue/the max number of frames the queue can hold before it is full and
must start dropping frames.
Input error: Includes runts, giants, no buffer, 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: Cyclic redundancy checksum 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
transmitting bad data.
Frame: Number of packets received incorrectly having 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 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 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 increased.
Watchdog: Number of times watchdog receive timer expired. It happens when receiving
a packet with length greater than 2048.
Pause input: Counter incrementing means that the port is receving pause frame. Pause
frame is a packet that tells the far-end device to stop transmitting packets until the
sender is able to handle all the traffic and clear it’s buffers. It could be caused by a
oversubscription of bandwidth, or a burst traffic pattern.
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.
Output errors: Sum of all errors that prevented the final transmission of datagrams out
of the interface being examined. Note that this may not balance with the sum of the
enumerated output errors, as 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 transmitted 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 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: Babble errors occur due to the transmission of frames in excess of 1518 bytes
in size.
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: Deferred indicates that the chip had to defer while ready to transmit a frame
because the carrier was asserted.
Output buffer failures: Number of failed buffers and number of buffers swapped out.
Output buffers swapped out: If the outbound interface transmit queue is full, then the
packet is copied from a hardware buffer to DRAM, then copied back to the transmit
queue when there is room.
L2 Switched: ucast: 0 pkt, 0 bytes – mcast: 0 pkt, 0 bytes
L3 in Switched: ucast: 0 pkt, 0 bytes – mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes
The output indicates how many packets have been L2 switched on the interface as well
as how many packets have been L3 switched in and out of the interface.
In NX-OS (Nexus device) the “show interface” output is slightly different than the IOS
output, but it is it is easy to understand. Below an example:
Ethernet1/1 is up
Dedicated Interface
Encapsulation ARPA
EtherType is 0x8100
input rate 78.13 Kbps, 9 pps; output rate 113.67 Kbps, 11 pps
RX
0 Rx pause
TX
12574452594 unicast packets 112812737 multicast packets 66330588
broadcast packets
0 Tx pause
9 interface resets
Ciscozine-NX-OS#
References:
http://www.cisco.com/…/reference/irfshoin.html
http://docwiki.cisco.com/…/IOS_Interface_Comparison