In which configuration mode is no shutdown used?

The no shutdown command is entered in Interface Config mode on Cisco IOS devices.

InterfacesInterface Config

no shutdown

Enables an interface that has been administratively disabled, allowing it to forward traffic and participate in network operations.

Definition: no shutdown is a Cisco IOS interface config command. Enables an interface that has been administratively disabled, allowing it to forward traffic and participate in network operations.

Overview

The 'no shutdown' command is one of the most fundamental yet critical commands in Cisco IOS. It is used to enable an interface that has been administratively disabled via the 'shutdown' command. When an interface is in shutdown state, it does not forward any traffic, does not participate in routing protocols, and appears as 'administratively down' in show commands.

The 'no shutdown' command reverses this state, bringing the interface up and allowing it to send and receive frames, participate in Layer 2 and Layer 3 operations, and become part of the network topology. This command is essential during initial device configuration, after making changes to interface parameters (like IP address or duplex settings), or when troubleshooting connectivity issues. Without it, even correctly configured interfaces remain non-functional.

The concept behind this command is administrative control: network engineers can disable interfaces for security, maintenance, or power-saving purposes without physically disconnecting cables. Alternatives include using 'interface range' to enable multiple interfaces at once, or relying on features like 'errdisable recovery' to automatically re-enable interfaces after error conditions. In the broader workflow, 'no shutdown' is typically one of the final steps after configuring interface parameters such as IP address, speed, duplex, and VLAN membership.

It is also used after replacing hardware or re-cabling. Important IOS behaviors: the command takes effect immediately and is written to the running configuration; it requires privilege level 15 (enable mode) to execute; there is no buffered output—the interface state changes instantly; and the command is available in all IOS modes that support interface configuration (global config, interface config, subinterface config). The 'no shutdown' command is also used on VLAN interfaces (SVI), loopback interfaces, tunnel interfaces, and even on management interfaces like GigabitEthernet0/0.

Understanding its proper use is a cornerstone of Cisco networking.

Syntax·Interface Config

no shutdown

When to Use This Command

After configuring a new interface, use 'no shutdown' to activate it.
When troubleshooting a down interface that shows 'administratively down', re-enable it with this command.
After making configuration changes on an interface that was shut down for maintenance, bring it back online.
When recovering from a security incident where an interface was disabled, re-enable it after verifying the threat is resolved.

Command Examples

Activating a GigabitEthernet interface

interface GigabitEthernet0/1
no shutdown

Router(config-if)#no shutdown
Router(config-if)#
*Mar  1 00:05:23.123: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Mar  1 00:05:24.124: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up

The first syslog message indicates the interface hardware state changed to up. The second message indicates the line protocol (Layer 2) is up, meaning the interface is fully operational.

Re-enabling a VLAN interface after maintenance

interface Vlan10
no shutdown

Router(config-if)#no shutdown
Router(config-if)#
*Mar  1 00:10:45.678: %LINK-3-UPDOWN: Interface Vlan10, changed state to up
*Mar  1 00:10:46.679: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up

Similar to physical interfaces, VLAN interfaces (SVI) also generate link and line protocol up messages when enabled.

Understanding the Output

The 'no shutdown' command itself produces no direct output on the CLI. Instead, the router generates syslog messages indicating the interface state change. The first message '%LINK-3-UPDOWN' shows the physical interface state transitioning to 'up'.

The second message '%LINEPROTO-5-UPDOWN' indicates the line protocol (Layer 2) is up, meaning the interface can pass traffic. If the line protocol does not come up, it suggests a Layer 1 or Layer 2 issue (e.g., cable unplugged, mismatched encapsulation). In a production network, always verify with 'show interfaces' to confirm the interface status is 'up/up'.

Configuration Scenarios

Enable a disabled GigabitEthernet interface on a router

A router's GigabitEthernet0/1 interface is administratively down after a recent configuration change. The interface needs to be enabled to restore connectivity to the adjacent switch.

Topology

R1(Gi0/1)---192.168.1.0/30---(Gi0/1)SW1

Steps

1.Step 1: Enter privileged EXEC mode: Router> enable
2.Step 2: Enter global configuration mode: Router# configure terminal
3.Step 3: Enter interface configuration mode: Router(config)# interface GigabitEthernet0/1
4.Step 4: Enable the interface: Router(config-if)# no shutdown
5.Step 5: Exit configuration mode: Router(config-if)# end
6.Step 6: Verify the interface state: Router# show interfaces GigabitEthernet0/1

Configuration

! Enable GigabitEthernet0/1
Router(config)# interface GigabitEthernet0/1
Router(config-if)# no shutdown
Router(config-if)# end

Verify: Router# show interfaces GigabitEthernet0/1 Expected output: 'GigabitEthernet0/1 is up, line protocol is up'

Watch out: Forgetting to configure an IP address or VLAN before issuing 'no shutdown' may result in the interface coming up but not passing traffic. Always verify Layer 1 and Layer 2 settings first.

Enable a VLAN interface (SVI) on a multilayer switch

A new VLAN 100 has been created on a multilayer switch, and the corresponding SVI (interface Vlan100) needs to be enabled to allow inter-VLAN routing.

Topology

SW1(Vlan100)---10.0.100.0/24---Hosts

Steps

1.Step 1: Enter privileged EXEC mode: Switch> enable
2.Step 2: Enter global configuration mode: Switch# configure terminal
3.Step 3: Enter interface configuration for the SVI: Switch(config)# interface Vlan100
4.Step 4: Assign an IP address: Switch(config-if)# ip address 10.0.100.1 255.255.255.0
5.Step 5: Enable the interface: Switch(config-if)# no shutdown
6.Step 6: Exit and verify: Switch(config-if)# end
7.Step 7: Check interface status: Switch# show interfaces Vlan100

Configuration

! Configure and enable VLAN 100 SVI
Switch(config)# interface Vlan100
Switch(config-if)# ip address 10.0.100.1 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# end

Verify: Switch# show interfaces Vlan100 Expected output: 'Vlan100 is up, line protocol is up'

Watch out: The SVI will remain down if the VLAN is not created or if no ports are assigned to the VLAN. Ensure the VLAN exists and has at least one active access or trunk port.

Troubleshooting with This Command

When troubleshooting interface issues, the 'no shutdown' command is often used to rule out administrative shutdown as the cause of a down interface. A healthy interface after 'no shutdown' will show 'up/up' in 'show interfaces' output. Problem indicators include 'administratively down' (meaning shutdown is applied), 'down/down' (Layer 1 issue), or 'up/down' (Layer 2 issue).

Key fields to focus on in 'show interfaces' are the first line (status and protocol), and counters for errors, CRC, collisions, and input/output drops. Common symptoms that 'no shutdown' helps diagnose: an interface that was previously disabled for maintenance but never re-enabled; a new interface that was configured but left in shutdown state; or an interface that was automatically disabled by errdisable and needs manual re-enablement. A step-by-step diagnostic flow: 1) Check interface status with 'show interfaces' or 'show ip interface brief'.

If status is 'administratively down', proceed to step 2. 2) Enter interface configuration mode and issue 'no shutdown'. 3) Immediately re-check status. If it changes to 'up/up', the issue was administrative shutdown. If it remains 'administratively down', check for a higher-level shutdown (e.g., 'shutdown' applied at the port-channel level).

If it changes to 'down/down', suspect a cable or hardware problem. If it changes to 'up/down', suspect Layer 2 issues like VLAN mismatch or spanning-tree blocking. Correlate with 'show running-config interface' to confirm no shutdown is present, and with 'show interfaces status' for errdisable state.

Use 'debug interface' with caution to see real-time state changes. For errdisable recovery, use 'errdisable recovery cause all' or manually cycle with 'shutdown' followed by 'no shutdown'. In complex scenarios, check the control plane: 'show ip interface brief' gives a quick overview of all Layer 3 interfaces.

Remember that 'no shutdown' does not affect Layer 1 or Layer 2 issues; it only removes the administrative disable. If the interface still does not come up, focus on physical cabling, transceivers, speed/duplex mismatches, or VLAN configuration.

CCNA Exam Tips

Remember that 'shutdown' disables an interface and 'no shutdown' enables it; the default state for most interfaces is 'shutdown'.

On CCNA exam, you may be asked to troubleshoot a down interface; check if it's 'administratively down' and apply 'no shutdown'.

The 'no shutdown' command is available in interface configuration mode for physical interfaces, SVIs, and subinterfaces.

After applying 'no shutdown', always verify with 'show interfaces' or 'show ip interface brief' to confirm the interface is up.

Common Mistakes

Forgetting to enter interface configuration mode before issuing 'no shutdown' (will get '% Invalid input detected').

Typing 'no shutdown' in global configuration mode instead of interface mode.

Assuming 'no shutdown' fixes all interface issues; it only removes administrative disablement, not physical or protocol problems.

no shutdown vs shutdown

The 'shutdown' and 'no shutdown' commands are administrative interface toggles that control operational state. They are commonly paired because 'shutdown' disables an interface while 'no shutdown' re-enables it, making them logical opposites in interface configuration.

Aspect	no shutdown	shutdown
Effect	Brings interface administratively up; allows traffic forwarding.	Takes interface administratively down; stops traffic forwarding.
Configuration Mode	Interface configuration mode (config-if).	Interface configuration mode (config-if).
Persistence	Persists across reloads; saved in running-config.	Persists across reloads; saved in running-config.
Initial State	Not the default on newly created interfaces; default is 'shutdown' for many platforms.	Default state for many physical interfaces (e.g., Ethernet) until explicitly enabled.
Precedence	Overrides any previous 'shutdown' command.	Overrides any previous 'no shutdown' command.
Typical Use	Activate a newly configured interface or restore after maintenance.	Disable an interface for configuration changes, troubleshooting, or security.

Use no shutdown when you need to enable an interface that is administratively down, such as after initial configuration or after resolving an issue.

Use shutdown when you need to temporarily disable an interface without removing its configuration, for example during maintenance or to isolate a problem.

Platform Notes

In IOS-XE (e.g., Catalyst 9000 switches), the 'no shutdown' command syntax and behavior are identical to classic IOS. However, output formatting may differ slightly in 'show interfaces' (e.g., additional fields like 'Auto-MDIX'). In NX-OS (e.g., Nexus switches), the equivalent command is also 'no shutdown' but note that NX-OS uses 'interface ethernet X/Y' instead of 'interface GigabitEthernet X/Y'.

Additionally, NX-OS requires 'feature interface-vlan' to enable SVIs, and the SVI is 'interface vlan X'. On ASA firewalls, the equivalent command is 'no shutdown' under interface configuration mode, but ASA uses 'interface gigabitethernet X' and often requires 'nameif' and 'security-level' before enabling. In IOS-XR (e.g., ASR 9000), the command is 'no shutdown' as well, but the configuration mode is 'interface GigabitEthernet0/0/0/0' (four-level slot notation).

IOS-XR also requires a commit after configuration changes. Between IOS versions (12.x, 15.x, 16.x), the 'no shutdown' command remains unchanged, but newer versions may introduce additional interface types (e.g., 'interface TenGigabitEthernet'). Always verify the exact interface naming convention for your platform.

The command is universally available across all Cisco platforms that support interface configuration.

Related Commands

show interfaces

Displays detailed Layer 1 and Layer 2 statistics for all interfaces or a specific interface: line protocol state, hardware type, MAC address, MTU, bandwidth, duplex, speed, input/output rates, error counters, and queue statistics.

show ip interface brief

Displays a one-line summary of all interfaces showing the IP address assigned, operational status (up/down), and line protocol status. The fastest way to get a device health overview.

shutdown

Disables an interface, preventing it from sending or receiving traffic, typically used for administrative shutdown or troubleshooting.

Practice for the CCNA 200-301

Test your knowledge with practice questions covering all CCNA 200-301 exam domains.

Practice CCNA 200-301 Questions