show interfaces
Shows the full detail for an interface: line status, MAC address, MTU, duplex and speed, traffic rates and error counters.
Written by a working field network engineer · CCNA, Security+, CySA+
The detailed view of one interface. Use it when show ip interface brief says something is wrong, or says everything is fine but traffic is still failing: the error counters, duplex, and last input/output times are here.
Example output
R1#show interfaces GigabitEthernet0/1
GigabitEthernet0/1 is up, line protocol is up
Hardware is iGbE, address is 0050.7966.6815 (bia 0050.7966.6815)
Internet address is 10.0.12.1/30
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1Gbps, media type is RJ45
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:02, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
5 minute input rate 2000 bits/sec, 3 packets/sec
5 minute output rate 2000 bits/sec, 3 packets/sec
18342 packets input, 1904518 bytes, 0 no buffer
Received 1203 broadcasts (1177 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
17955 packets output, 1887240 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
1 lost carrier, 0 no carrierReference output: hand-written in standard Cisco IOS format for this example network, not captured from a device.
Useful variants
show interfaces GigabitEthernet0/1sh int g0/1show interfaces counters errors
What each column or field means
| Field | Meaning |
|---|---|
is up, line protocol is up | Layer 1 and Layer 2 state, the same two values as Status and Protocol in show ip interface brief. |
address is … (bia …) | The MAC address in use and the burned-in address. |
Internet address | The IPv4 address with its prefix length, which show ip interface brief leaves out. |
MTU / BW / DLY | Maximum frame payload, and the bandwidth and delay values routing protocols use for their metrics (OSPF cost is derived from BW). |
Full Duplex, 1Gbps | Negotiated or configured duplex and speed. |
broadcasts (IP multicasts) | Broadcast and multicast frames received; the bracketed figure is the multicast part. On this link it is mostly OSPF hellos to 224.0.0.5, every 10 seconds. |
input errors / CRC | Frames received damaged. Rising CRC errors point to cabling, a bad transceiver or a duplex mismatch. |
late collision | Collisions after the first 64 bytes. On a full-duplex link these should never happen; they are the classic duplex-mismatch signature. |
interface resets / lost carrier | How often the interface reset and lost signal. Climbing counts mean a flapping link. |
When it doesn’t look right
CRC and input errors keep climbing.
Physical layer: replace the cable or patch lead, reseat or swap the transceiver, and check the far end for the same counters.
Late collisions on one side, CRC errors on the other.
Duplex mismatch: one end is half duplex. Set both ends to auto, or hard-code both to the same speed and duplex.
Input queue drops or output drops increasing.
The interface is congested. Look at the 5-minute rates against BW; consider QoS or a faster or bundled link.
Related commands
Try it yourself
- Interface Duplex & Speed Errors (Pro)
- Fixing a Duplex Mismatch (Pro)
- Hard-Coding Interface Speed and Duplex (free)
- Re-Cabled Uplink Lands on an Unconfigured Port (Pro)
Learn it in the CCNA path
- Describe ports and read one interface's configuration (2. Network Access)
- Read detailed interface output and set speed and duplex (2. Network Access)
Topic
Switching Basics — How a switch learns MAC addresses, how to read interface status, and how to fix speed, duplex and administratively down ports.