InterfacesCCNA 200-301

Interface Accidentally Shut Down — How to Detect and Fix

Presenting Symptom

A host on VLAN 10 cannot ping its default gateway, and the interface on the switch shows 'administratively down'.

Network Context

A small branch office with a single Cisco Catalyst 2960 switch (IOS 15.x) connecting 20 PCs in VLAN 10 to a router-on-a-stick. The switchport GigabitEthernet0/1 is configured as an access port in VLAN 10 and connects to the router. The network engineer notices connectivity loss after a recent maintenance window.

Diagnostic Steps

Check interface status

show interfaces GigabitEthernet0/1

GigabitEthernet0/1 is administratively down, line protocol is down

The interface is administratively down, meaning it was manually shut down via the 'shutdown' command. This is the root cause indicator.

Verify running configuration

show running-config interface GigabitEthernet0/1

interface GigabitEthernet0/1
 switchport access vlan 10
 switchport mode access
 shutdown

The 'shutdown' command is present in the interface configuration. This confirms the interface was intentionally disabled.

Check for any recent configuration changes

show archive log config all | include GigabitEthernet0/1

! Executed at 14:23:45 UTC Mon Mar 1 2021 by user 'admin' via 'vty0'
 configure terminal
 interface GigabitEthernet0/1
 shutdown

This shows the exact time and user who issued the 'shutdown' command, helping identify accidental or unauthorized changes.

Verify no other issues (optional)

show interfaces status | include GigabitEthernet0/1

Gi0/1            notconnect   1        auto   auto  10/100/1000  -

The status 'notconnect' is expected when administratively down; no physical or VLAN mismatch issues.

Root Cause

The interface GigabitEthernet0/1 was accidentally shut down by a network administrator during a maintenance window, likely via the 'shutdown' command in interface configuration mode.

Resolution

Re-enable the interface by removing the shutdown command: 1. Enter global configuration mode: configure terminal 2. Enter interface configuration mode: interface GigabitEthernet0/1 3. Issue the 'no shutdown' command: no shutdown 4. Exit and save configuration: end write memory

Verification

Run 'show interfaces GigabitEthernet0/1' again. Expected output: GigabitEthernet0/1 is up, line protocol is up Also verify connectivity: ping from a host to the default gateway should succeed.

Prevention

1. Use role-based access control (RBAC) to limit who can issue 'shutdown' commands. 2. Implement change management procedures with peer review before interface changes. 3. Use 'reload in' before making changes to allow automatic rollback if connectivity is lost.

CCNA Exam Relevance

On the CCNA 200-301 exam, this scenario appears in troubleshooting questions where you must identify why an interface is down. The exam tests your ability to use 'show interfaces' and 'show running-config' to distinguish between administratively down and physical layer issues. Key fact: 'administratively down' always means the 'shutdown' command was applied.

Exam Tips

Remember that 'administratively down' is always a configuration issue, not a hardware problem.

The 'show interfaces' output line 'GigabitEthernet0/1 is administratively down' is the definitive clue.

The 'no shutdown' command is the fix; know that it must be entered in interface configuration mode.

Commands Used in This Scenario

show interfaces

Displays detailed status and statistics for all interfaces or a specific interface, used to verify interface operational state, errors, and performance.

show running-config

Displays the current active configuration in DRAM, showing all non-default settings.

Test Your CCNA Knowledge

Practice with scenario-based questions to prepare for the CCNA 200-301 exam.

Practice CCNA Questions