Cisco IOS Fundamentals

Cisco IOS is the operating software behind the command-line experience on many Cisco routers and switches. Cisco IOS XE documentation uses the same core administrative model. Exact features vary by product and release.

You use the command-line interface, or CLI, to monitor a device, change its configuration, and investigate problems. The CLI is organized into command modes. Each mode limits which commands you can run and shows a distinct prompt. That structure helps you see both your current privilege and the part of the configuration you are editing.

The central mental model

Think of an IOS device as three connected views:

1. Operational state tells you what the device is doing now. Interfaces, routes, counters, and protocol neighbors belong here.
2. Running configuration contains the commands currently controlling the device. Most configuration changes take effect here as you enter them.
3. Startup configuration supplies configuration commands during startup. It can differ from the running configuration until you save.

This distinction prevents a common mistake. A working change in the running configuration is not necessarily durable. If the device restarts before you copy the running configuration to the startup configuration, that change may disappear.

Command modes

You normally enter user EXEC mode after login. Its prompt ends with a greater-than sign. This mode supports limited monitoring.

The enable command enters privileged EXEC mode, whose prompt ends with a number sign. Privileged EXEC mode gives you broader inspection and management commands. It is also the gateway to configuration modes.

From privileged EXEC mode, configure terminal enters global configuration mode. Commands here change device-wide settings. A command such as interface GigabitEthernet0/0/0 moves you into interface configuration mode. Commands then apply to that interface until you exit or select another context.

The prompt is a location marker:

Device>              user EXEC
Device#              privileged EXEC
Device(config)#      global configuration
Device(config-if)#   interface configuration

Use exit to move back one level. Use end to return directly to privileged EXEC mode.

Reading before changing

Start with observation. show running-config displays the active configuration. show startup-config displays the startup configuration. show ip interface brief gives a compact view of interface addresses and status.

IOS includes contextual help. Enter a question mark to list valid commands or arguments at your current position. Use the Tab key to complete an unambiguous command. These tools are safer than guessing syntax because available commands depend on the mode, platform, feature set, and software release.

A representative change

An interface configuration follows the IOS mode hierarchy:

Device# configure terminal
Device(config)# interface GigabitEthernet0/0/0
Device(config-if)# ip address 192.0.2.1 255.255.255.0
Device(config-if)# no shutdown
Device(config-if)# end
Device# show ip interface brief

The interface command selects the object. The ip address command configures its IPv4 address and mask. The no shutdown command administratively enables it. The final show command verifies interface state instead of assuming success.

Interface names and supported commands differ across devices. Check the product and release documentation before applying an example to production equipment.

Negation and defaults

Many configuration commands have a no form. The no form usually removes a configured command or restores its default behavior. It does not mean the same thing in every context, so inspect command help and the relevant command reference before using it.

This command-oriented model makes a configuration readable as a sequence of statements. It also means that small edits can affect live traffic immediately. Plan a rollback, understand your access path, and verify after each meaningful change.

Saving and recovering intent

After verification, copy running-config startup-config saves the active configuration for the next startup. Saving is a deliberate step, not proof that the change is correct.

Before a risky remote change, consider how you will recover if management connectivity fails. A console connection or an approved out-of-band path can provide access when the production network cannot. Follow your organization's change, backup, and credential procedures.

Security baseline

Administrative privilege needs explicit protection. Cisco recommends enable secret instead of the older enable password command because the older mechanism uses weak encryption. Treat configuration output as sensitive because it can contain credentials, keys, addressing, and other operational details.

Hardening is wider than setting one password. Restrict management access, use approved secure remote access, remove unneeded services, and follow the security guidance for the exact platform and release.

Where this course ends

This course gives you the shared IOS operating model: modes, prompts, configuration state, interfaces, verification, saving, and safe change habits. It does not cover routing protocols, switching design, access control lists, automation APIs, high availability, or platform-specific deployment.

Your next step is a lab on equipment or a simulator that matches the documentation you are studying. Practice moving between modes, reading state, making one reversible change, verifying it, and saving only after the result is correct.