Verifying the operational state of network ports is the first step in diagnosing connectivity issues, auditing switch capacity, or validating new deployments across Cisco routers and switches. Whether you are troubleshooting a single workstation drop or auditing trunk links across a distribution block, Cisco operating systems provide specific command-line utilities to inspect everything from basic link-up indicators to deep hardware queue counters and optical laser levels. Understanding which command to run—and how to interpret the resulting status indicators—lets you isolate Layer 1 physical faults, Layer 2 negotiation mismatches, and Layer 3 addressing issues in seconds.
Table of Contents
Step-by-Step Guide to Checking Interface Status via the Cisco CLI
Checking port states on a Cisco switch or router follows a logical progression from broad summary views down to targeted interface diagnostics. Follow these steps to verify operational status from the command-line interface (CLI).
Access Privileged EXEC Mode
Log in to the device via SSH or console and elevate your session to Privileged EXEC mode. While basic status commands can run in User EXEC mode (>), Privileged EXEC mode (#) unlocks full diagnostic filtering and transceiver details.
ios
Switch> enable
Switch#Check Layer 3 Operational Status and IP Assignments
Runshow ip interface brief(orshow ipv6 interface brieffor IPv6) to view a concise summary of every physical and virtual interface on a router or switch. This command verifies whether an IP address is assigned and displays both the physical state (Status) and data-link state (Protocol).
ios
Switch# show ip interface brief
Interface IP-Address OK? Method Status Protocol
Vlan1 192.168.1.10 YES NVRAM up up
GigabitEthernet1/0/1 unassigned YES unset up up
GigabitEthernet1/0/2 unassigned YES unset down down
GigabitEthernet1/0/3 unassigned YES unset administratively down downView Layer 2 Switchport Status, VLAN, and Speed
On Cisco Catalyst and Nexus switches, executeshow interfaces statusto inspect Layer 2 port attributes. Each line displays the configured port description (Name), connection state, assigned VLAN (ortrunkdesignation), duplex mode, operating speed, and media type.
ios
Switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Gi1/0/1 Uplink-Core-SW1 connected trunk a-full a-1000 10/100/1000BaseTX
Gi1/0/2 User-Desk-42 notconnect 10 auto auto 10/100/1000BaseTX
Gi1/0/3 Unused-Port disabled 999 auto auto 10/100/1000BaseTX
Gi1/0/4 Printer-2F err-disabled 20 auto auto 10/100/1000BaseTXInspect a Specific Interface in Detail
Append the exact interface identifier to narrow your output to a single port. You can apply this to summary commands or runshow interfaces <interface-id>to view MAC addresses, MTU size, encapsulation, and real-time bandwidth utilization.
ios
Switch# show interfaces status interface GigabitEthernet1/0/1
Switch# show interfaces GigabitEthernet1/0/1Filter Output on High-Density Switches
On chassis switches or stacks with hundreds of ports, use the pipe (|) operator withinclude,exclude, orbeginto isolate relevant ports without paging through inactive interfaces.
ios
Switch# show interfaces status | include connected
Switch# show ip interface brief | exclude unassigned
Switch# show interfaces description | include Uplink
Key Takeaway: Start with show ip interface brief on routers or show interfaces status on switches for an immediate health overview before drilling into individual port configurations.
Comparing Cisco Interface Status Commands
While the commands introduced above all report whether a port is active, each queries different layers of the OSI model and targets specific administrative workflows. Choosing the right command depends on whether you are troubleshooting physical cabling, VLAN assignments, or IP routing.
| Command | Primary OSI Layer Focus | Supported Device Types | Key Output Fields | Best Use Case |
|---|---|---|---|---|
show interfaces status | Layer 1 (Physical) & Layer 2 (Data Link) | Catalyst Switches, Nexus Switches (L2/L3 Switchports) | Port, Name (Description), Status, VLAN, Duplex, Speed, Media Type | Auditing access/trunk ports, checking negotiated speed/duplex, and spotting err-disabled switchports. |
show ip interface brief | Layer 1, Layer 2, & Layer 3 (Network) | All Cisco Routers, L3 Switches, and ASA/Firepower appliances | Interface, IP-Address, OK?, Method, Status (L1), Protocol (L2) | Verifying SVIs and routed interfaces, confirming IPv4 assignments, and checking up/up state. |
show interfaces | Layer 1 through Layer 3 (Comprehensive) | All Cisco IOS, IOS XE, IOS XR, and NX-OS devices | Hardware/MAC address, MTU, BW, DLY, Reliability, Tx/Rx Load, Encapsulation, Queue/Error counters | Deep-dive troubleshooting of packet drops, CRC errors, bandwidth saturation, and timer intervals. |
show interfaces description | Layer 1 & Layer 2 + Administrative Metadata | All Cisco Routers and Switches | Interface, Status (L1), Protocol (L2), Complete Description String | Viewing full interface descriptions that get truncated to 18 characters in show interfaces status. |
show interfaces switchport | Layer 2 (Switching & Trunking) | Cisco Catalyst and Nexus Switches | Administrative Mode, Operational Mode, Access VLAN, Native VLAN, Trunking VLANs Enabled, Voice VLAN | Diagnosing DTP negotiation, verifying 802.1Q trunk encapsulation, and auditing allowed VLAN lists. |
Key Takeaway: Use show interfaces status for rapid Layer 2 switchport audits and show ip interface brief whenever IP addressing or routed port states are involved.
Interpreting Cisco Interface Status Codes and Line Protocol States
Running the right command is only half the battle; you also need to decode the status values returned by the CLI. The following frequently asked questions explain the exact meaning behind Cisco’s Layer 1 and Layer 2 state indicators.
What do connected, notconnect, and disabled mean in show interfaces status?
connected: The port is enabled, detects a valid physical Layer 1 carrier signal, and has successfully negotiated link parameters with the attached device.notconnect: The port is administratively enabled (no shutdownis active), but no physical carrier signal is detected. This means nothing is plugged into the port, the remote device is powered off, the patch cable is broken, or the Tx/Rx fiber strands are reversed.disabled: An administrator has manually deactivated the port using theshutdownconfiguration command.
What does err-disabled mean, and why does a Cisco port enter this state?
An err-disabled (error-disabled) status indicates that the Cisco operating system automatically shut down the port to protect the network from a security violation or hardware loop. Common triggers include Port Security MAC address violations, Spanning Tree BPDU Guard detecting an unauthorized switch, link-flapping (rapidly cycling up and down), UniDirectional Link Detection (UDLD) failures, or EtherChannel misconfigurations. You can identify the exact trigger by running show interfaces status err-disabled or show errdisable recovery.
What is the difference between “Status” and “Protocol” in show ip interface brief?
In show ip interface brief (as well as the first line of show interfaces), Cisco separates interface health into two columns:
* Status (first value): Represents Layer 1 (Physical Layer) health. It confirms whether the port is enabled and receiving a physical carrier signal (electrical voltage or optical light).
* Protocol (second value): Represents Layer 2 (Data Link Layer) health. It confirms whether the interface is successfully exchanging keepalives and agreeing on data-link framing with the neighboring device.
What causes an interface to show up / down (Status is up, Line Protocol is down)?
An up / down state means the physical cable is plugged in and passing a signal, but Layer 2 framing has failed. Common causes include:
* Encapsulation mismatches (such as 802.1Q vs. ISL on trunks, or PPP vs. HDLC on WAN serial links).
* Mismatched EtherChannel/LACP modes where one switch is configured for LACP (active) and the neighbor is set to static (on) or unbundled.
* Keepalive failures or severe clock/speed mismatches between connected interfaces.
How does administratively down / down differ from down / down?
administratively down / down: The interface has been intentionally turned off in the configuration with theshutdowncommand. No traffic can pass until an administrator enters interface configuration mode and issuesno shutdown.down / down: The interface is configured to be active (no shutdown), but it lacks a Layer 1 physical link. Because Layer 1 is down, the Layer 2 line protocol automatically remains down as well.
Key Takeaway: Always map the reported state to the OSI model—fix down/down and notconnect at the physical cable or power level, and troubleshoot up/down or err-disabled in the Layer 2 switchport configuration.
How to Check Interface Errors, Packet Drops, and Duplex Mismatches
Sometimes an interface shows connected and up/up (as covered above), yet users still experience sluggish throughput, intermittent disconnects, or corrupted file transfers. When a link is physically up but performing poorly, follow this step-by-step guide to inspect error counters and negotiation settings.
Clear Historical Counters to Establish a Clean Baseline
Interface statistics accumulate continuously since the device’s last reboot or manual reset. Before troubleshooting an active issue, clear the counters on the suspect interface so you are not misled by errors that occurred months ago.
ios
Switch# clear counters GigabitEthernet1/0/1
Clear "show interface" counters on this interface [confirm]Scan All Switchports for Hardware and Framing Errors
Runshow interfaces counters errorsto view a switch-wide matrix of physical and data-link faults. This immediately highlights which port on the switch is incrementing alignment errors (Align-Err), Frame Check Sequence errors (FCS-Err), or collisions.
“`ios
Switch# show interfaces counters errors
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
Gi1/0/1 0 482 0 482 0 0
Gi1/0/2 0 0 0 0 0 14520
“`
- Verify Speed and Duplex Negotiation Settings
Check the negotiated speed and duplex inshow interfaces statusor line 4 ofshow interfaces <interface-id>. A classic duplex mismatch occurs when one device is hardcoded toduplex fullandspeed 100(which disables autonegotiation) while the connected switchport is set toauto, forcing the auto-negotiating side to fall back to half-duplex.
ios
Switch# show interfaces GigabitEthernet1/0/1 | include duplex
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX - Symptom on the Half-Duplex side: Rapidly increasing late collisions and deferred frames.
Symptom on the Full-Duplex side: Rapidly increasing CRC errors, frame errors, and runts.
Inspect Detailed Input Errors (CRC, Runts, and Giants)
Filter the detailed interface output to examine incoming physical layer corruption.
ios
Switch# show interfaces GigabitEthernet1/0/1 | include input errors|CRC|runts|giants
482 input errors, 482 CRC, 0 frame, 0 overrun, 0 ignored
0 runts, 0 giants, 0 throttles- CRC (Cyclic Redundancy Check) Errors: The calculated checksum of an arriving frame does not match its FCS trailer. Apart from duplex mismatches, high CRCs point to damaged CAT5e/CAT6 cables, electromagnetic interference (EMI) near power lines, or dirty fiber optic end-faces.
- Runts: Frames smaller than the 64-byte minimum Ethernet size, typically caused by collisions or a failing network interface card (NIC).
Giants: Frames exceeding the interface’s Maximum Transmission Unit (MTU), usually caused by sending Jumbo Frames (e.g., 9000 bytes) into a switchport configured for the standard 1500-byte MTU.
Check Output Drops and Queue Congestion
If physical errors are zero (0 input errors, 0 CRC) but packet loss persists, inspect the queue drop counters.
ios
Switch# show interfaces GigabitEthernet1/0/2 | includequeue|drops
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 14520- Total Output Drops: The switch is trying to transmit more traffic out of the port than the link speed or egress QoS buffers allow—most commonly seen when a 10 Gbps uplink bursts traffic toward a 1 Gbps access port.
- Input Queue Drops / Overruns: The ingress hardware buffer is overwhelmed and cannot pass frames to the switch fabric fast enough.
Key Takeaway: Always clear counters first; then isolate physical cabling/duplex issues via CRC and late collisions, and isolate bandwidth bottlenecks via Total output drops.
Checking Fiber SFP Transceiver Status and Optical Light Levels
When troubleshooting fiber optic uplinks that remain notconnect or suffer from high CRC errors, you must verify that the SFP, SFP+, or QSFP module is recognized and that its optical transmit (Tx) and receive (Rx) laser power levels fall within acceptable Digital Optical Monitoring (DOM) thresholds. Use the following CLI template across Cisco IOS/IOS XE and NX-OS platforms.
! =====================================================================
! 1. VERIFY SFP HARDWARE INVENTORY AND SERIAL NUMBERS (IOS / IOS XE / NX-OS)
! =====================================================================
show inventory
show interfaces <interface-id> transceiver properties
! =====================================================================
! 2. CHECK OPTICAL LIGHT LEVELS (DOM) ON CISCO IOS / IOS XE
! Replace <interface-id> with your fiber port (e.g., TenGigabitEthernet1/1/1)
! =====================================================================
show interfaces transceiver
show interfaces <interface-id> transceiver detail
! --- Example Output & Threshold Reference ---
! High Alarm High Warn Low Warn Low Alarm
! Temperature Voltage Threshold Threshold Threshold Threshold
! Port (Celsius) (Volts) (dBm) (dBm) (dBm) (dBm)
! --------- ------------------ ------------ ----------- ---------- ---------- ----------
! Te1/1/1 34.2 3.29 -1.0 -1.5 -9.9 -13.9
!
! High Alarm High Warn Low Warn Low Alarm
! Optical Optical Threshold Threshold Threshold Threshold
! Transmit Power Receive Power (dBm) (dBm) (dBm) (dBm)
! Port (dBm) (dBm)
! --------- ------------------ ------------- ----------- ---------- ---------- ----------
! Te1/1/1 -2.4 -4.8 -1.0 -1.5 -9.9 -13.9
!
! NOTE: If Optical Receive Power reads -40.0 dBm, the port is receiving NO light
! (check for broken fiber, unpatched LC connectors, or swapped Tx/Rx strands).
! =====================================================================
! 3. CHECK OPTICAL LIGHT LEVELS (DOM) ON CISCO NEXUS (NX-OS)
! =====================================================================
show interface <interface-id> transceiver details
Key Takeaway: Compare the live Optical Receive Power (dBm) against the module’s Low Warn and Low Alarm thresholds; a reading of -40.0 dBm indicates total loss of optical signal.
Bulk Interface Troubleshooting Cheat Sheet and Ansible Playbook Template
For network administrators auditing multiple switches simultaneously, running manual commands port by port is inefficient. Below is a copy-ready CLI quick-reference cheat sheet covering peripheral port health (PoE, EtherChannel, and neighbor discovery) followed by an Ansible playbook template to automate interface status audits across an entire Cisco fleet.
CLI Quick-Reference Cheat Sheet
! --- Port Status & Layer 2/Layer 3 Summary ---
show interfaces status
show ip interface brief
show ipv6 interface brief
show interfaces description
! --- Error & Traffic Diagnostics ---
show interfaces counters errors
show interfaces <interface-id> | include line protocol|rate|drops|errors|CRC
show interfaces status err-disabled
show errdisable recovery
! --- Power over Ethernet (PoE) Status ---
show power inline
show power inline <interface-id> detail
! --- Connected Neighbor & Port-Channel Verification ---
show cdp neighbors detail
show lldp neighbors detail
show etherchannel summary
Ansible Playbook Template for Bulk Interface Status Audits
Save the template below as audit_cisco_interfaces.yml and run it against your Ansible inventory (ansible-playbook -i inventory.ini audit_cisco_interfaces.yml) to collect and export port status summaries from multiple Cisco switches in parallel.
---
- name: Bulk Audit Cisco IOS Interface Status and Errors
hosts: cisco_switches
gather_facts: false
connection: ansible.netcommon.network_cli
vars:
report_directory: "./interface_reports"
tasks:
- name: Ensure local report directory exists
ansible.builtin.file:
path: "{{ report_directory }}"
state: directory
delegate_to: localhost
run_once: true
- name: Collect interface status, IP brief, and error counters
cisco.ios.ios_command:
commands:
- show interfaces status
- show ip interface brief
- show interfaces counters errors
- show interfaces status err-disabled
register: cli_output
- name: Save consolidated interface report per switch
ansible.builtin.copy:
content: |
============================================================
INTERFACE AUDIT REPORT: {{ inventory_hostname }}
============================================================
--- [1] LAYER 2 PORT STATUS (show interfaces status) ---
{{ cli_output.stdout[0] }}
--- [2] LAYER 3 IP BRIEF (show ip interface brief) ---
{{ cli_output.stdout[1] }}
--- [3] INTERFACE ERROR COUNTERS (show interfaces counters errors) ---
{{ cli_output.stdout[2] }}
--- [4] ERR-DISABLED PORTS (show interfaces status err-disabled) ---
{{ cli_output.stdout[3] }}
dest: "{{ report_directory }}/{{ inventory_hostname }}_interface_status.txt"
delegate_to: localhost
Key Takeaway: Standardize routine audits using the CLI cheat sheet for single-switch checks and the cisco.ios.ios_command Ansible playbook to generate automated baseline reports before and after maintenance windows.
Cisco IOS, IOS XE, and NX-OS Interface Command Reference
To ensure syntax accuracy across different hardware families, consult the formal command specifications and cross-platform distinctions outlined in Cisco’s official technical documentation.
Command Syntax Specification
show interfaces [type number] [status [err-disabled] | counters [errors | protocol status] | switchport | description | transceiver [properties | detail]]
show ip interface [type number] [brief [vlan]]
Command Modes
- User EXEC (
>): Supports standard read-only status queries (show interfaces,show interfaces status,show ip interface brief). - Privileged EXEC (
#): Required on specific software releases to access detailed hardware controller registers, optical transceiver calibration tables, andclear countersoperations.
Cross-Platform Operating System Compatibility
- Cisco IOS & Cisco IOS XE (Catalyst 2960, 3650, 3850, 9200, 9300, 9400, 9500, ISR/ASR Series):
- Interface Naming Convention: Uses full or abbreviated media-speed prefixes followed by chassis/slot/subslot/port numbering (e.g.,
GigabitEthernet1/0/1orGi1/0/1,TwentyFiveGigE1/0/1orTw1/0/1). - Official Documentation Reference: Cisco IOS Interface and Hardware Component Command Reference.
- Cisco NX-OS (Nexus 3000, 5000, 7000, 9000 Series):
- Interface Naming Convention: Standardizes all physical switchports under the
Ethernetprefix regardless of port speed (e.g.,Ethernet1/1orEth1/1). - Syntax Variations: Supports
show interface briefas a native consolidated Layer 2/Layer 3 summary; usesshow interface ethernet <slot/port> transceiver details(note the pluraldetails) for DOM inspection. - Official Documentation Reference: Cisco Nexus 9000 Series NX-OS Interfaces Command Reference.
- Cisco IOS XR (ASR 9000, NCS 540, NCS 5500, CRS Series):
- Interface Naming Convention: Includes rack/slot/instance/port hierarchy (e.g.,
GigabitEthernet0/0/0/0orTenGigE0/1/0/2). - Syntax Variations: Replaces
show ip interface briefwithshow ipv4 interface brief(orshow ipv6 interface brief). Optical transceiver metrics are queried at the controller level usingshow controllers <interface-id> phy. - Official Documentation Reference: Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference.
Key Takeaway: Account for OS-specific syntax variations—specifically Ethernet naming on NX-OS and show ipv4 interface brief on IOS XR—when operating across mixed Cisco environments or writing multi-platform automation scripts.
Conclusion
Checking interface status in Cisco environments is a structured process that scales from quick visual checks to granular hardware diagnostics. By combining show ip interface brief and show interfaces status for rapid Layer 1 through Layer 3 verification, decoding status indicators like notconnect and err-disabled, and inspecting CRC counters, queue drops, and SFP optical power levels when links degrade, you can pinpoint network faults quickly and accurately. Keep the CLI cheat sheet and Ansible template on hand to streamline both daily troubleshooting and large-scale switch audits.











Comments