What you will learn, and what Cisco IOS is
What you will learn in this module. By the end of these chapters you will be able to connect to a brand-new Cisco switch or router, move confidently between its command modes, use the built-in help instead of memorising everything, give the device a name, protect it with passwords, put IP addresses on its interfaces, check your work with show commands and save the result so it survives a reboot. You will also know what happens when a device boots, where its configuration lives, and how to troubleshoot the classic first-day problem: "I cannot ping my router".
Prerequisites. You should have finished the Networking from absolute zero module, so you know what a switch, a router, an IP address and a subnet mask are, and why a PC needs a default gateway. You do not need any Cisco experience. Every command in this module is explained the first time it appears, and the three labs let you practise each one on a simulated switch and router.
Start with an analogy: IOS is the reception desk of a secure office building
Imagine a large office building. At the front there is a reception desk. A visitor can ask the receptionist simple questions ("what floor is accounts on?") but cannot change anything. An employee who shows a badge can walk further inside and look at every file. A manager with a master key can enter the control room and change how the whole building works: rename meeting rooms, change door codes, rewire the lifts. Inside the control room there are smaller rooms for specific jobs: one for the lifts, one for the doors, one for the lights.
Cisco IOS (Internetwork Operating System) works the same way. It is the operating system that runs on Cisco routers and switches, and you talk to it through a command-line interface (CLI). The CLI has levels: a visitor level where you can only look (user EXEC), an employee level where you can see everything and run tests (privileged EXEC), a control room where you change the configuration (global configuration), and small rooms for one interface or one line (sub-modes). The prompt at the end of the line tells you which room you are standing in.
Each level lets you do more. The prompt is your "you are here" sign.
Why a command line, and not a web page?
Many devices today also offer a web GUI or are managed by a controller, and you will study automation and controllers later in the CCNA. But the CLI is still the tool every network engineer uses daily, for four reasons:
- It is always there. A device with no IP address and no configuration still has a console port and a CLI. The GUI needs an IP address first.
- It is precise. A command does exactly one thing, and the running configuration is plain text you can read, copy, compare and back up.
- It scales. The same text you type can be pasted into a hundred devices or sent by an automation script.
- It is what the exam and interviews test. CCNA questions show CLI output and ask what it means.
The IOS family
"IOS" is used loosely for several related Cisco operating systems. Classic IOS ran on older ISR routers and Catalyst switches. IOS XE runs on current Catalyst 9000 switches and ISR 4000 / Catalyst 8000 routers; it is Linux-based underneath but gives you the same CLI. NX-OS (Nexus data center switches) and IOS XR (service provider routers) look similar but have their own differences. For the CCNA, everything you learn here applies to IOS and IOS XE, and the habits carry over to the others.
| OS | Where you meet it | CLI feel |
|---|---|---|
| IOS / IOS XE | Campus switches, branch routers | The CLI taught in this module |
| NX-OS | Nexus data center switches | Very similar, features enabled with feature |
| IOS XR | Service provider routers | Similar, but changes need commit |
The lab network you will build
All three labs use the same tiny office: one PC, one switch and one router on the subnet 192.168.10.0/24. The router is the default gateway at 192.168.10.1, the switch gets a management address 192.168.10.2, and the PC is 192.168.10.10.
The same three devices appear in every lab and example in this module.
Worked example. A fresh router boots and shows Router>. You type enable and see Router#. You type configure terminal and see Router(config)#. You type hostname R1 and the prompt instantly becomes R1(config)#. Four prompts, three levels, one change. That tiny sequence is the pattern for everything you will ever configure on IOS.
Common beginner mistake. Treating the CLI like a chat window and typing commands without looking at the prompt. Most "command not working" problems in the first week are simply the right command typed in the wrong mode. Always read the prompt before you type.
Exam trap. Questions often show a prompt and ask which command is possible there. > means user EXEC, # means privileged EXEC, and (config...)# means a configuration mode. Configuration commands never work at > or plain #.
The intern and the "broken" router
On her first day, an intern was asked to check a branch router's interfaces. She typed show running-config and got % Invalid input detected at '^' marker. She reported that the router was faulty. Her senior looked at the screen: the prompt was BR-R1>. She was in user EXEC, where the running configuration is not visible. One enable, one password, and the command worked.
Lesson: the prompt is the first thing to read. Most "errors" in IOS are mode errors.
"What is Cisco IOS and how do you normally interact with it?"
Strong answer: IOS is the operating system on Cisco routers and switches (IOS XE on current platforms). You manage it mainly through a hierarchical CLI, either locally over the console port or remotely over SSH. The CLI has user EXEC, privileged EXEC and configuration modes, and the prompt shows which one you are in. Mention that the active configuration is plain text in RAM (running-config) that must be saved to NVRAM (startup-config).
Key takeaways
- IOS is the operating system of Cisco routers and switches; IOS XE is its modern form with the same CLI.
- You talk to IOS through a command-line interface with levels, like rooms in a secure building.
- The prompt (
>,#,(config)#) tells you which level you are in. - The CLI works even on a device with no IP address, which is why every engineer must know it.
- All labs in this module use PC1, SW1 and R1 on 192.168.10.0/24.