# Day 4: Introduction to the CLI

# CCNA 200-301 Study Guide: Device Management & CLI Fundamentals

Mastering initial device access and Command-Line Interface (CLI) navigation is the foundation for all network configuration, troubleshooting, and security hardening. These skills are central to Domain 1.0 (Network Fundamentals) and Domain 5.0 (Security Fundamentals).

## 1.0 Establishing the Initial Console Connection

Before network-based protocols (SSH/Telnet) can be used, you must establish "out-of-band" access. This is the only reliable method for managing unconfigured devices.

### 1.1 Physical Hardware and Cabling

- Console Port: A dedicated management port (RJ-45 or USB mini-B).
- Rollover Cable: A specialized cable with reversed pinouts designed for serial communication.
- USB-to-Serial Adapter: Required for modern PCs lacking native DB9 serial ports.

Critical Note: A rollover cable is electrically incompatible with standard Ethernet signaling. Using a standard Ethernet cable in a console port will not work and may cause hardware damage.

### 1.2 Terminal Emulator Configuration

Use an application like PuTTY or Tera Term with the following precise serial settings:

<div align="left" dir="ltr" id="bkmrk-setting-value-baud-r"><table><colgroup><col width="159"></col><col width="91"></col></colgroup><tbody><tr><td>Setting

</td><td>Value

</td></tr><tr><td>Baud Rate (Speed)

</td><td>9600 bps

</td></tr><tr><td>Data Bits

</td><td>8

</td></tr><tr><td>Parity

</td><td>None

</td></tr><tr><td>Stop Bits

</td><td>1

</td></tr><tr><td>Flow Control

</td><td>None

</td></tr></tbody></table>

</div>## 2.0 Mastering the Cisco IOS CLI

The Cisco Internetwork Operating System (IOS) uses a hierarchical mode structure to prevent accidental configuration errors by restricting sensitive commands to specific modes.

### 2.1 The Hierarchy of CLI Modes

<div align="left" dir="ltr" id="bkmrk-mode-name-prompt-acc"><table><colgroup><col width="108"></col><col width="152"></col><col width="114"></col><col width="226"></col></colgroup><tbody><tr><td>Mode Name

</td><td>Prompt

</td><td>Access Method

</td><td>Core Function

</td></tr><tr><td>User EXEC

</td><td>Router&gt;

</td><td>Default on login.

</td><td>Basic monitoring/connectivity tests.

</td></tr><tr><td>Privileged EXEC

</td><td>Router#

</td><td>enable

</td><td>Full "show" commands, file mgmt, reloads.

</td></tr><tr><td>Global Config

</td><td>Router(config)#

</td><td>configure terminal

</td><td>Commands affecting the entire device.

</td></tr><tr><td>Interface Config

</td><td>Router(config-if)#

</td><td>interface \[type/id\]

</td><td>Specific interface settings (IP, Speed).

</td></tr></tbody></table>

</div>### 2.2 Navigation &amp; Productivity Shortcuts

<div align="left" dir="ltr" id="bkmrk-command%2Fshortcut-pur"><table><colgroup><col width="167"></col><col width="437"></col></colgroup><tbody><tr><td>Command/Shortcut

</td><td>Purpose and Operational Impact

</td></tr><tr><td>exit

</td><td>Moves back one level in the hierarchy.

</td></tr><tr><td>end or Ctrl+Z

</td><td>Immediately returns to Privileged EXEC mode.

</td></tr><tr><td>?

</td><td>Context-sensitive help; lists available commands/options.

</td></tr><tr><td>Tab

</td><td>Command completion; also verifies correct syntax.

</td></tr><tr><td>do

</td><td>Executes a Privileged EXEC command from configuration modes.

</td></tr></tbody></table>

</div>## 3.0 Core Device Configuration and Security

### 3.1 Establishing Identity and Access

- Hostname: Use hostname \[Name\] in Global Config to identify the device.
- Securing Privileged Access:
- enable password: Insecure. Stores password in plain text. Do not use.
- enable secret: Best Practice. Stores password as a strong cryptographic hash.


Precedence Rule: If both are configured, the device always enforces the enable secret and ignores the plain-text password.

### 3.2 Password Obfuscation &amp; Reversal

- service password-encryption: Applies weak, reversible encryption to plain-text passwords to prevent "shoulder surfing."
- The no Command: Prefix any command with no to remove or reverse it (e.g., no hostname).

## 4.0 Managing and Saving Configuration Files

It is vital to distinguish between active (volatile) memory and permanent storage.

### 4.1 The Two Key Configuration Files

<div align="left" dir="ltr" id="bkmrk-file-type-storage-lo"><table><colgroup><col width="156"></col><col width="118"></col><col width="186"></col><col width="141"></col></colgroup><tbody><tr><td>File Type

</td><td>Storage Location

</td><td>Persistence

</td><td>View Command

</td></tr><tr><td>Running Configuration

</td><td>RAM

</td><td>Volatile: Lost on power loss.

</td><td>show running-config

</td></tr><tr><td>Startup Configuration

</td><td>NVRAM

</td><td>Non-Volatile: Persists on reboot.

</td><td>show startup-config

</td></tr></tbody></table>

</div>### 4.2 Persisting Changes

To save active changes, you must copy the running configuration to the startup configuration:

copy running-config startup-config

## 5.0 Study Summary: Critical Recall

- Console Settings: 9600, 8, N, 1 (8-N-1).
- Access Escalation: User EXEC $\\rightarrow$ enable $\\rightarrow$ Privileged EXEC $\\rightarrow$ conf t $\\rightarrow$ Global Config.
- Encryption Best Practice: Always use enable secret over enable password.
- Final Step: Always perform a copy run start before exiting your session to ensure changes survive a reboot.