CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Inspecting port settings on a Cisco switch requires distinguishing between what an administrator has configured in memory and how the interface is currently operating on the physical network. Because Cisco IOS and IOS XE store user-defined parameters in the running configuration while tracking real-time link negotiation, VLAN tagging, and security states in separate operational tables, no single command shows every detail at once. Whether you are auditing a single access port, verifying an 802.1Q trunk, diagnosing a shutdown interface, or managing a switch through its web interface, choosing the right verification method ensures you get accurate port data quickly.

Choosing the Right Command: Administrative Config vs. Operational Status

Before running interface commands, it is essential to know whether you need to view the administrative configuration (the commands explicitly typed into the switch) or the operational status (the live state negotiated with the connected device). For example, a port configured with speed auto and duplex auto will not display its actual operating rate in the running configuration; you must query the operational interface state to see if it negotiated 1000 Mbps full-duplex.

CommandPrimary PurposeConfig vs. OperationalKey Data DisplayedScopeBest Used For
show running-config interface <id>Views explicit CLI commands applied to the portAdministrativeNon-default subcommands (VLANs, descriptions, QoS, spanning-tree, ACLs)Single portAuditing exact syntax applied to a port or copying config to another switch
show interfaces statusSummarizes live link state across the switchOperationalPort description, link status (connected/notconnect), VLAN/Trunk indicator, negotiated duplex (a-full), and speed (a-1000)All ports (or single port if specified)Quick health check of port link states, speed/duplex mismatches, and basic VLAN assignments
show interfaces <id> switchportInspects comprehensive Layer 2 parametersBothAdmin vs. Operational mode, Access VLAN, Native VLAN, Voice VLAN, trunk encapsulation, and pruningSingle port (or all if <id> omitted)Verifying access vs. trunk behavior, Dynamic Trunking Protocol (DTP) state, and VLAN tagging rules
show interfaces <id>Displays hardware-level and Layer 1/Layer 2 statisticsOperationalMAC/BIA address, MTU, bandwidth, input/output load, queue drops, CRC errors, and runts/giantsSingle port (or all if <id> omitted)Diagnosing physical cable faults, duplex collisions, and bandwidth saturation

When reading show interfaces status output, pay close attention to the a- prefix under the Duplex and Speed columns (such as a-full and a-1000). The prefix indicates that the values were achieved dynamically via auto-negotiation rather than hard-coded in the configuration.

Viewing the Running Configuration for a Specific Port or Range

Once you know you want to inspect the administrative configuration, use the show running-config interface command in privileged EXEC mode (#) to pull the exact configuration block for a physical port or EtherChannel without scrolling through the entire configuration file.

! 1. View the active configuration of a single physical port
Switch# show running-config interface GigabitEthernet1/0/1

! Shorthand syntax supported across Cisco IOS and IOS XE
Switch# sh run int gi1/0/1

! 2. View the configuration of a logical Port-Channel interface
Switch# show running-config interface Port-channel 1

! 3. View the configuration of a port including all hidden default settings
Switch# show running-config interface GigabitEthernet1/0/1 all

! 4. View the effective configuration (merges manual config with dynamic templates/auto-QoS)
Switch# show derived-config interface GigabitEthernet1/0/1

! 5. View the running configuration for a contiguous range of ports (ports 1 through 5)
Switch# show running-config | section interface GigabitEthernet1/0/[1-5]$

! 6. View the running configuration for multiple non-contiguous ports (ports 1, 3, and 10)
Switch# show running-config | section interface GigabitEthernet1/0/(1|3|10)$

Sample output for show running-config interface GigabitEthernet1/0/1:

Building configuration...

Current configuration : 214 bytes
!
interface GigabitEthernet1/0/1
 description Workstation_Floor2
 switchport access vlan 20
 switchport mode access
 switchport voice vlan 120
 spanning-tree portfast
end

Because standard Cisco IOS only hides unmodified default commands in show running-config interface <id>, appending the all keyword or using regex section filters is the fastest way to audit implicit defaults and multi-port blocks at scale.

How to Verify Port VLANs, Trunking, and Layer 2 Settings

Because the running configuration hides default Layer 2 settings—such as whether a port is dynamically negotiating a trunk via DTP or using the default native VLAN 1—you should follow a structured verification flow to check VLAN and trunking parameters.

Step 1: Inspect Detailed Switchport Parameters

Run show interfaces <interface-id> switchport to examine how the port handles Layer 2 traffic:

Switch# show interfaces GigabitEthernet1/0/1 switchport
Name: Gi1/0/1
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 20 (Users)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: 120 (VoIP)
<output omitted>
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001

Review these critical fields in the output:
1. Administrative Mode vs. Operational Mode: Confirms whether the port is configured as static access, trunk, dynamic auto, or dynamic desirable, and what state it actually resolved to (Operational Mode).
2. Access Mode VLAN: Displays the data VLAN assigned to untagged frames when the port operates in access mode.
3. Trunking Native Mode VLAN: Identifies the VLAN used for untagged traffic if the port operates as an 802.1Q trunk.
4. Voice VLAN: Confirms whether a dedicated auxiliary VLAN is advertised via CDP/LLDP to attached IP phones.
5. Trunking VLANs Enabled: Lists which VLANs are permitted to cross the port when trunking is active.

Step 2: Verify Active Trunk Links and Forwarding State

If a port is operating as a trunk, checking the switchport configuration alone does not guarantee traffic is passing. Run show interfaces trunk to confirm active trunk negotiation and Spanning Tree Protocol (STP) forwarding status:

Switch# show interfaces trunk

Port        Mode             Encapsulation  Status        Native vlan
Gi1/0/24    on               802.1q         trunking      99

Port        Vlans allowed on trunk
Gi1/0/24    10,20,99,120

Port        Vlans allowed and active in management domain
Gi1/0/24    10,20,99,120

Port        Vlans in spanning tree forwarding state and not pruned
Gi1/0/24    10,20,99,120

If a VLAN appears under Vlans allowed on trunk but is missing from Vlans allowed and active in management domain, the VLAN has not been created in the local switch’s VLAN database (show vlan brief). Always verify that your target VLAN reaches the final table (spanning tree forwarding state) to ensure traffic is not blocked by STP.

Troubleshooting Port Security and Error-Disabled Interfaces

When an access port stops passing traffic even though a valid device is plugged in, Layer 2 security policies are often the cause. Follow these steps to inspect port security rules, MAC address limits, and error-disabled states.

Step 1: Check if the Port Is Error-Disabled

Instead of guessing why a port is shut down, query the switch’s error-disabled table to see the exact feature that triggered the outage:

Switch# show interfaces status err-disabled

Port      Name               Status       Reason               Err-disabled Vlans
Gi1/0/5   Printer_Port       err-disabled psecure-violation
Gi1/0/12  Conference_Room    err-disabled bpduguard

The Reason column pinpoints whether the shutdown was caused by a port-security MAC violation (psecure-violation), an unauthorized switch or loop (bpduguard), cable instability (link-flap), or another protective policy.

Step 2: Verify Port Security Settings and Violation Counters

To inspect the security rules and current status on a specific interface, run show port-security interface <interface-id>:

Switch# show port-security interface GigabitEthernet1/0/5
Port Security              : Enabled
Port Status                : Secure-shutdown
Violation Mode             : Shutdown
Aging Time                 : 0 mins
Aging Type                 : Absolute
SecureStatic Address Aging : Disabled
Maximum MAC Addresses      : 1
Total MAC Addresses        : 1
Configured MAC Addresses   : 0
Sticky MAC Addresses       : 1
Last Source Address:Vlan   : 0050.7966.6802:20
Security Violation Count   : 1

Key troubleshooting indicators include:
* Port Status: Shows Secure-up (operating normally), Secure-down (port is administratively down or unplugged), or Secure-shutdown (tripped into an err-disabled state).
* Violation Mode: Indicates whether unauthorized MAC addresses cause the port to shut down completely (Shutdown), drop rogue frames while logging an alert (Restrict), or silently drop rogue frames (Protect).
* Maximum vs. Total MAC Addresses: Shows whether the port has reached its allowed hardware address ceiling.
* Last Source Address:Vlan: Identifies the exact MAC address and VLAN that last communicated on the port—providing the culprit MAC address when Security Violation Count increments.

Step 3: Audit Learned and Sticky MAC Addresses

To see which specific MAC addresses are currently authorized and bound to the interface, run:

Switch# show port-security address interface GigabitEthernet1/0/5
               Secure Mac Address Table
-----------------------------------------------------------------------------
Vlan    Mac Address       Type                          Ports   Remaining Age
                                                                   (mins)
----    -----------       ----                          -----   -------------
  20    001b.54c2.8a11    SecureSticky                  Gi1/0/5        -
-----------------------------------------------------------------------------

Step 4: Check Automatic Recovery Timers

Finally, run show errdisable recovery to verify whether the switch is configured to automatically re-enable error-disabled ports after a timeout interval, or if you must manually reset the port using shutdown followed by no shutdown.

Checking Cisco Switch Port Configuration via the Web GUI

If you prefer not to use the command-line interface, or if you are managing Cisco Small Business (SMB) switches where the web interface is primary, you can inspect all administrative and operational port settings through a browser.

Prerequisite: Connect to the WebUI

Open a web browser, enter https://<switch-management-ip>, and log in with an account that has privilege level 15 (or admin rights).

Method A: Cisco Catalyst Switches (IOS XE WebUI)

For enterprise switches such as the Catalyst 9200, 9300, and 9500 series running IOS XE:
1. Check Live Operational State: In the left navigation pane, click Monitoring > General > Interfaces. The top graphical faceplate displays color-coded link statuses (green for active, gray for down, amber for administrative shutdown or error). Below the graphic, the interface table lists real-time operational status, negotiated speed, duplex, and input/output utilization.
2. Inspect Administrative Port Settings: Navigate to Configuration > Interface > Ethernet.
3. View Individual Port Details: Click the specific port name (e.g., Gi1/0/1) in the table to open the Edit Ethernet Interface panel.
* Under the General tab, verify the Port Type (Access or Trunk), administrative status (Enabled/Disabled), VLAN ID (or Native VLAN and Allowed VLANs for trunks), Speed, and Duplex settings.
* Under the Security tab, review Port Security status, maximum MAC counts, sticky MAC enforcement, and storm control thresholds.
* Under the Advanced tab, check Spanning Tree PortFast and BPDU Guard settings.

Method B: Cisco Business and SMB Switches (CBS250/350 & Catalyst 1200/1300)

For Cisco Business switches using the graphical SMB dashboard:
1. Check Physical Link and Speed Settings: Navigate to Port Management > Port Settings. Here you can compare the Admin Status (Up/Down) against the Operational Status, inspect auto-negotiation state, check current operational speed/duplex, and see if 802.3x Flow Control is active.
2. Check Port VLAN and Trunk Configuration: Navigate to VLAN Management > Interface Settings. This table displays each port’s Interface VLAN Mode (Access, Trunk, or General), Frame Type filtering, and Ingress Filtering state.
3. Verify Tagged and Untagged VLAN Memberships: Go to VLAN Management > Port VLAN Membership. Select a port or port range to see its Administrative and Operational VLAN memberships, including which VLAN ID is marked as U (Untagged), T (Tagged), or P (PVID / Native VLAN).

Cisco IOS Interface Command Reference and Official Documentation

For network engineers requiring exhaustive command syntax definitions, optional keyword flags, SNMP MIB mappings, and release-specific behavior across Cisco operating systems, refer to the authoritative Cisco documentation manuals below.

Authoritative Cisco Command Reference Manuals

  • Cisco IOS Interface and Hardware Component Command Reference: Documents hardware-layer and physical interface verification commands, including show interfaces, show controllers, show running-config interface, and show derived-config.
  • Cisco IOS LAN Switching Command Reference: Documents Layer 2 switching verification commands, including show interfaces switchport, show interfaces trunk, show interfaces status, and show vlan.
  • Cisco IOS Security Command Reference (Commands S to Z): Documents port-level access control and MAC security commands, including show port-security, show port-security interface, and show port-security address.

Command Syntax Specifications

Command: show interfaces
* Syntax: show interfaces [interface-type interface-number] [status [err-disabled] | switchport | trunk | stats | counters [errors |etherchannel | protocol status] | description | capabilities | transceiver]
* Command Mode: User EXEC (>) or Privileged EXEC (#). Note: Certain sub-options and complete configuration outputs require Privileged EXEC mode.
* OS Compatibility: Cisco IOS Release 12.2 and later; Cisco IOS XE Gibraltar 16.10.x, Amsterdam 17.x, and later.

Command: show running-config interface
* Syntax: show running-config interface type number [all]
* Command Mode: Privileged EXEC (#).
* Usage Guidelines: Queries the active configuration in RAM (system:running-config) scoped strictly to the specified physical interface, subinterface, VLAN SVI, or Port-Channel. Appending the all keyword displays both user-configured and system-default interface subcommands.

Official Documentation Lookup Path

To locate platform-specific interface documentation for your exact switch model and software train on cisco.com:
1. Navigate to Support > Product Support > Switches.
2. Select your product family (for example, Cisco Catalyst 9300 Series Switches).
3. Open Command References to look up alphabetical CLI syntax definitions, or open Configuration Guides > Interface and Hardware Components Configuration Guide matching your active Cisco IOS XE release.

Conclusion

Checking port configuration on a Cisco switch is straightforward once you match your verification method to the layer of data you need. Use show running-config interface (as covered above) when you need to audit explicit administrative commands, show interfaces switchport and show interfaces trunk to validate Layer 2 VLAN behavior, and show interfaces status or show port-security interface to diagnose live operational states and security shutdowns. Whether you execute these checks via the CLI or inspect them through the switch’s Web GUI, combining administrative and operational views gives you complete visibility into how every port on your switch is configured and performing.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.