PATCH 01
Common Ports
The ports that show up constantly on the exam. Know the transport protocol (TCP vs UDP) as well as the number — several are asked both ways.
| Port | Protocol | Transport | Purpose |
| 20 / 21 | FTP | TCP | File transfer (data / control) |
| 22 | SSH | TCP | Secure remote shell |
| 23 | Telnet | TCP | Unencrypted remote shell |
| 25 | SMTP | TCP | Mail transfer (send) |
| 53 | DNS | TCP/UDP | Name resolution (UDP queries, TCP zone transfers) |
| 67 / 68 | DHCP | UDP | Server (67) / Client (68) address assignment |
| 69 | TFTP | UDP | Trivial file transfer — IOS image/config backup |
| 80 | HTTP | TCP | Web traffic, unencrypted |
| 110 | POP3 | TCP | Mail retrieval (download & delete) |
| 123 | NTP | UDP | Clock synchronization |
| 143 | IMAP | TCP | Mail retrieval (synced, stays on server) |
| 161 / 162 | SNMP | UDP | Device monitoring / traps |
| 179 | BGP | TCP | Border Gateway Protocol peering |
| 389 | LDAP | TCP | Directory services lookup |
| 443 | HTTPS | TCP | Web traffic, TLS-encrypted |
| 445 | SMB | TCP | Windows file/printer sharing |
| 514 | Syslog | UDP | Logging to a remote collector |
| 520 | RIP | UDP | Routing Information Protocol updates |
| 3389 | RDP | TCP | Remote Desktop Protocol |
Memory hook: odd well-known ports below 1024 tend to be the older TCP control-plane protocols (FTP, Telnet, SMTP); UDP shows up wherever speed matters more than reliability (DHCP, TFTP, SNMP, NTP, syslog).
PATCH 02
Port Number Groups
Every port number (0–65,535) falls into one of three IANA-defined ranges. Knowing the boundaries helps you reason about unfamiliar ports on the exam.
| Port Group | Number Range | Description |
| Well-known Ports |
0 – 1,023 |
Reserved for common/popular services (web browsers, email clients, remote access). Lets clients identify the associated service by port alone. |
| Registered Ports |
1,024 – 49,151 |
Assigned by IANA to a requesting entity for a specific process/application — typically individual installed apps rather than universal services. Example: Cisco registered 1812 for RADIUS authentication. |
| Private / Dynamic Ports |
49,152 – 65,535 |
Also called ephemeral ports. The client OS assigns these dynamically when a connection is initiated, to identify the client application during that session. |
PATCH 03
IPv4 Address Classes
Classful addressing is legacy (CIDR replaced it), but the exam still tests it — first octet range and default mask especially.
| Class | 1st Octet Range | Default Mask | Default / | Purpose |
| A | 1 – 126 | 255.0.0.0 | /8 | Large networks |
| B | 128 – 191 | 255.255.0.0 | /16 | Medium networks |
| C | 192 – 223 | 255.255.255.0 | /24 | Small networks |
| D | 224 – 239 | n/a | — | Multicast |
| E | 240 – 255 | n/a | — | Experimental / reserved |
Note: 127.0.0.0/8 sits inside the Class A range but is reserved for loopback (127.0.0.1) — not assignable.
PATCH 04
Private Address Ranges (RFC 1918) & Special-Use
| Class | Range | CIDR | Hosts |
| A | 10.0.0.0 – 10.255.255.255 | 10.0.0.0/8 | 16,777,214 |
| B | 172.16.0.0 – 172.31.255.255 | 172.16.0.0/12 | 1,048,574 |
| C | 192.168.0.0 – 192.168.255.255 | 192.168.0.0/16 | 65,534 |
| Range | Purpose |
| 127.0.0.0/8 | Loopback |
| 169.254.0.0/16 | APIPA / link-local |
| 224.0.0.0/4 | Multicast (Class D) |
| 255.255.255.255 | Limited broadcast |
| 0.0.0.0/8 | "This network" / default route |
PATCH 05
Subnetting / CIDR Cheat Sheet
Usable hosts = 2(host bits) − 2. Number of subnets from a classful base = 2(borrowed bits). The last octet column assumes the mask boundary falls in the 4th octet (a /24 base network).
| CIDR | Subnet Mask | Wildcard Mask | Usable Hosts | 4th-Octet Block Size |
| /24 | 255.255.255.0 | 0.0.0.255 | 254 | 256 |
| /25 | 255.255.255.128 | 0.0.0.127 | 126 | 128 |
| /26 | 255.255.255.192 | 0.0.0.63 | 62 | 64 |
| /27 | 255.255.255.224 | 0.0.0.31 | 30 | 32 |
| /28 | 255.255.255.240 | 0.0.0.15 | 14 | 16 |
| /29 | 255.255.255.248 | 0.0.0.7 | 6 | 8 |
| /30 | 255.255.255.252 | 0.0.0.3 | 2 | 4 |
| /31 | 255.255.255.254 | 0.0.0.1 | 2 (P2P, RFC 3021) | 2 |
| /32 | 255.255.255.255 | 0.0.0.0 | 1 (host route) | 1 |
Fast method: block size = 256 − (last non-255 octet of the mask). Subnets land on multiples of the block size, so a /27 (block 32) gives networks at .0, .32, .64, .96, .128, .160, .192, .224 — first address is the network ID, last is broadcast, everything between is usable.
PATCH 06
Binary, Hex & Quick Subnetting Practice
The manual "by-hand" method for solving subnetting problems on paper (or on the exam) — place values, CIDR-to-octet mapping, and the host table formulas.
Decimal / Binary / Hex (0–15)
| Decimal | Binary | Hex |
| 0–9 | 0000–1001 | 0–9 |
| 10 | 1010 | A |
| 11 | 1011 | B |
| 12 | 1100 | C |
| 13 | 1101 | D |
| 14 | 1110 | E |
| 15 | 1111 | F |
Quick Binary Chart (Place Values)
| Bit Place | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| Place Value | 128 | 64 | 32 | 16 | 8 | 4 | 2 | 1 |
| Custom Subnet Mask (CSM) | 128 | 192 | 224 | 240 | 248 | 252 | 254 | 255 |
Each bit turned on adds its place value to the running total — this is how a CSM (128, 192, 224, 240, 248, 252, 254, 255) is built one bit at a time, and it's the same increment (INC) used to step through subnets.
CIDR by Octet
| Octet | 128 | 192 | 224 | 240 | 248 | 252 | 254 | 255 |
| 1st | /1 | /2 | /3 | /4 | /5 | /6 | /7 | /8 |
| 2nd | /9 | /10 | /11 | /12 | /13 | /14 | /15 | /16 |
| 3rd | /17 | /18 | /19 | /20 | /21 | /22 | /23 | /24 |
| 4th | /25 | /26 | /27 | /28 | /29 | /30 | /31 | /32 |
Steps to Subnetting
- Fill in what's given.
- Determine the Class of the given IP address.
- Fill in the Default Subnet Mask (DSM) for that class.
- Bit out the DSM and draw the default line.
- Determine # of subnets (BBN) or # of hosts (BBH) using the Power-of-2 chart (2n − 2).
- BBN + BBH = free bits.
- Turn on the number of BBN bits after the default line; draw a line under the last bit turned on to get the CSM & INC value.
- Use the last bit turned on to determine which octet the INC applies to.
- Solve SubID = IP × CSM (in binary — "ANDing").
- Solve BC (broadcast) = (SubID + INC) − 1 in the 4th octet.
- Add the INC to every IP address down the host table to fill it in — first usable = SubID + 1, last usable = BC − 1.
Host range formula: first usable = Subnet ID + 1 (4th octet); last usable = Broadcast − 1 (4th octet). Fill the "0" line first, then add the INC equally going down — or multiply INC by the line number and add it to the 0 line to jump straight to any subnet.
PATCH 07
IPv6 Address Compression (Omit-Zero Rules)
A full IPv6 address is 128 bits written as eight 16-bit hextets separated by colons. Two shorthand rules let you compress it — the exam tests both, including where people get them wrong.
| Rule | What it does | Before | After |
| 1. Leading-zero omission |
Drop leading zeros within each hextet. Can be applied to every hextet, as many times as needed. |
2001:0db8:0000:0000:0000:ff00:0042:8329 |
2001:db8:0:0:0:ff00:42:8329 |
| 2. Double-colon (::) compression |
Replace one contiguous run of all-zero hextets with ::. Can only be used once per address. |
2001:db8:0:0:0:ff00:42:8329 |
2001:db8::ff00:42:8329 |
Why only one :: — if two separate zero-runs were both compressed, the address becomes ambiguous: there'd be no way to tell how many zero hextets belong to each gap. The router (or you, on the exam) can't reliably expand it back to 8 hextets. Pick the longest run of zero hextets to compress; if two runs tie for longest, compress the first one.
| Full Address | Compressed | Note |
| fe80:0000:0000:0000:0202:b3ff:fe1e:8329 | fe80::202:b3ff:fe1e:8329 | Single zero-run in the middle, plus leading zeros dropped |
| 2001:0db8:0000:0000:0000:0000:0000:0001 | 2001:db8::1 | One long zero-run compressed to :: |
| 0000:0000:0000:0000:0000:0000:0000:0001 | ::1 | Loopback — entire address is zero except the last bit |
| 0000:0000:0000:0000:0000:0000:0000:0000 | :: | Unspecified address — all 128 bits are zero |
| 2001:0db8:0000:0001:0000:0000:0000:0001 | 2001:db8:0:1::1 | Two zero-runs of unequal length (1 hextet vs 3) — only the longer run (3) gets ::; the shorter run just drops its leading zero |
Common exam trap: 2001:db8::1::1 is invalid — two :: in one address. Always double-check a compressed address has at most one ::.
IPv6 Duplicate Address Detection (DAD)
Before using a global unicast or link-local unicast address, a device may verify the address is unique on the network.
- The device sends a Neighbor Solicitation (NS) message targeting its own IPv6 address.
- If another device already has that address, it responds with a Neighbor Advertisement (NA), notifying the sender the address is in use.
- DAD is not required, but RFC 4861 recommends performing it on unicast addresses.
PATCH 09
OSI Model vs TCP/IP Model
| Layer | OSI | TCP/IP Group | PDU | Examples |
| 7 | Application | Application | Data | HTTP, DNS, DHCP, SSH, FTP, SMTP, IMAP |
| 6 | Presentation | Application | Data | TLS, encoding, compression, encryption |
| 5 | Session | Application | Data | Session establishment, RPC |
| 4 | Transport | Transport | Segment (TCP) / Datagram (UDP) | TCP, UDP |
| 3 | Network | Internet | Packet | IP, ICMP, routing protocols |
| 2 | Data Link | Network Access | Frame | Ethernet, MAC, switching |
| 1 | Physical | Network Access | Bits | Cabling, signaling, hubs |
Mnemonic (top→bottom): "All People Seem To Need Data Processing" — Application, Presentation, Session, Transport, Network, Data Link, Physical.
PATCH 10
Application, Presentation & Session Layers
The upper three OSI layers collapse into a single TCP/IP "Application" layer — the interface between the applications people use and the underlying network.
Presentation Layer — 3 Functions
- Formats/presents data at the source into a format the destination can receive
- Compresses data so it can be decompressed at the destination
- Encrypts data for transmission and decrypts it on receipt
Session Layer — Functions
- Creates and maintains dialogs between source and destination applications
- Initiates dialogs, keeps them active, and restarts sessions that are disrupted or idle too long
Well-Known Application Layer Protocols
DNS, HTTP, SMTP, POP3, DHCP, FTP, TFTP, IMAP — see the Ports section for their port numbers.
HTTP / HTTPS Request Methods
| Method | Description |
| GET | Client request for data — a browser sends GET to request HTML pages/resources. |
| POST | Uploads data files to the web server, such as form data. |
| PUT | Uploads resources or content to the web server, such as an image. |
Note: HTTP is not a secure protocol — use HTTPS for communications sent across the internet.
PATCH 12
ICMP Messages — Destination/Service Unreachable
An ICMP Destination Unreachable message notifies the source that a destination or service is unreachable, and includes a code explaining why.
| Code | ICMPv4 Meaning |
| 0 | Net unreachable |
| 1 | Host unreachable |
| 2 | Protocol unreachable |
| 3 | Port unreachable |
| Code | ICMPv6 Meaning |
| 0 | No route to destination |
| 1 | Communication administratively prohibited (e.g. firewall) |
| 2 | Beyond scope of the source address |
| 3 | Address unreachable |
| 4 | Port unreachable |
ICMPv6 codes are similar in spirit to ICMPv4 but not numbered identically — don't assume the two lists line up code-for-code.
PATCH 13
Ethernet & MAC Addressing
MAC Address Structure
- 48-bit address expressed as 12 hex digits (6 bytes total).
- First 6 hex digits (3 bytes / 24 bits) = OUI — Organizationally Unique Identifier, registered by the vendor with the IEEE.
- Last 6 hex digits (3 bytes / 24 bits) = vendor-assigned value, unique per device.
- MAC addressing provides device identification at the data link layer, since every device on an Ethernet LAN shares the same media.
Multicast MAC Addresses
| Encapsulated Data | Destination MAC Prefix |
| IPv4 multicast packet | 01-00-5E |
| IPv6 multicast packet | 33-33 |
| Non-IP (e.g. STP) | Other reserved multicast MACs |
A multicast frame is flooded out every switch port except the one it arrived on, unless the switch is configured for multicast snooping — and it's not routed unless the router is configured to route multicast. Multicast/broadcast MACs can only ever be a destination; the source of a frame is always a unicast MAC.
PATCH 14
VLANs & Trunking (IOS Commands)
The core switching config workflow: create the VLAN, assign access ports to it, then trunk the link between switches so every VLAN's traffic can cross it.
VLAN Creation Commands
| Task | IOS Command |
| Enter global configuration mode | configure terminal |
| Create a VLAN with a valid ID | vlan vlan-id |
| Name the VLAN | name vlan-name |
| Return to privileged EXEC | end |
VLAN details are stored in vlan.dat in flash. On newer Catalyst switches, assigning a nonexistent VLAN to an interface auto-creates it.
VLAN Port Assignment Commands
| Task | Command |
| Enter global configuration mode | configure terminal |
| Enter interface configuration mode | interface interface-id |
| Set the port to access mode | switchport mode access |
| Assign the port to a VLAN | switchport access vlan vlan-id |
| Return to privileged EXEC | end |
Trunk Configuration Commands
Trunks are Layer 2 links that carry traffic for all VLANs between switches (or switch-to-router).
| Task | Command |
| Enter global configuration mode | configure terminal |
| Enter interface configuration mode | interface interface-id |
| Set the port to permanent trunking mode | switchport mode trunk |
| Set the native VLAN to something other than VLAN 1 | switchport trunk native vlan vlan-id |
| Specify which VLANs are allowed on the trunk | switchport trunk allowed vlan vlan-list |
| Return to privileged EXEC | end |
Data & Voice VLAN Example
A phone+PC on one port needs both a data VLAN and a voice VLAN, with QoS trust turned on so voice traffic gets prioritized.
| Task | Command |
| Assign the access (data) VLAN | switchport access vlan vlan-id |
| Trust the CoS marking from the phone | mls qos trust cos |
| Assign the voice VLAN | switchport voice vlan vlan-id |
VLAN Ranges on Catalyst Switches
| Normal Range (VLAN 1–1005) | Extended Range (VLAN 1006–4095) |
| Used in small-to-medium businesses | Used by service providers |
| 1002–1005 reserved for legacy VLANs (FDDI/Token Ring) | Exist in the running-config |
| 1, 1002–1005 are auto-created and cannot be deleted | Supports fewer VLAN features |
| Stored in the vlan.dat file in flash | Requires VTP configuration to sync |
| VTP can synchronize normal-range VLANs between switches | — |
Catalyst 2960 and 3650 switches support over 4,000 VLANs total across both ranges.
Dynamic Trunking Protocol (DTP) Negotiation Results
The resulting link state when each side of a connection is set to a given DTP mode.
| Dynamic Auto | Dynamic Desirable | Trunk | Access |
| Dynamic Auto | Access | Trunk | Trunk | Access |
| Dynamic Desirable | Trunk | Trunk | Trunk | Access |
| Trunk | Trunk | Trunk | Trunk | Limited connectivity |
| Access | Access | Access | Limited connectivity | Access |
Best practice: manually set switchport mode trunk on intended trunk links rather than relying on DTP — it's more predictable and closes off a VLAN-hopping attack vector.
PATCH 15
Switching Concepts — Learn & Forward
How a switch actually builds and uses its MAC address table for every frame it handles.
Ingress / Egress
- Ingress — a frame entering an interface.
- Egress — a frame exiting an interface.
- A switch forwards based on the ingress interface plus the destination MAC address, using its MAC address table to decide.
The Switch Learn & Forward Method (2 Steps)
| Step | Action |
| 1. Learn | Examines the source address — adds the source MAC to the table if it isn't already there, or resets its 5-minute aging timer if it is. |
| 2. Forward | Examines the destination address — forwards out the specific port if the destination MAC is in the table; floods out every port except the one it arrived on if it isn't. |
Rule: a switch never forwards a frame back out the interface it was received on.
PATCH 16
STP Operations
Spanning Tree builds a loop-free topology in three elections: pick the root bridge, pick each non-root switch's root port, then pick each segment's designated port. Whatever's left over is blocked.
Bridge ID (BID) — Who Becomes Root Bridge
The switch with the lowest BID wins root bridge election. BID = Bridge Priority + Extended System ID + MAC Address.
- Bridge Priority — default is 32768 on every Cisco switch. Range is 0–61440 in increments of 4096; lower is preferred, and a priority of 0 always wins.
- Extended System ID — a decimal value added to the bridge priority to identify which VLAN a given BPDU belongs to.
- MAC Address — the tiebreaker. If two switches share the same priority and extended system ID, the lowest MAC address (hex) wins root bridge.
Why ties happen: since every switch defaults to priority 32768, root bridge elections often come down to MAC address alone unless an admin manually lowers the priority on the switch they want as root.
STP Port Roles — Election Order
| Step | Election | Rule |
| 1 | Root Bridge | One per spanning-tree instance — the switch with the lowest BID. All of its ports become designated ports. |
| 2 | Root Port | One per non-root switch — the port with the lowest internal root path cost back to the root bridge. |
| 3 | Designated Port | One per segment — the port on that segment with the best (lowest-cost) path to the root bridge. If one end of a segment is a root port, the other end is automatically the designated port. |
| — | Alternate / Blocked Port | Anything that's neither a root port nor a designated port — placed in blocking state to prevent a loop. |
All ports attached to end devices (PCs, servers) are automatically designated ports — they're never in contention for root or blocking.
Internal Root Path Cost
Equal to the sum of all port costs along the path to the root bridge. Lower total cost wins; the losing (higher-cost) redundant path gets blocked.
| Link Speed | STP Cost (IEEE 802.1D-1998) | RSTP Cost (IEEE 802.1w-2004) |
| 10 Gbps | 2 | 2,000 |
| 1 Gbps | 4 | 20,000 |
| 100 Mbps | 19 | 200,000 |
| 10 Mbps | 100 | 2,000,000 |
Cisco switches default to the 802.1D "short path cost" values for both STP and RSTP. Port cost is configurable per-interface, letting an admin manually steer which path spanning tree prefers.
Root Port Tiebreakers (Multiple Equal-Cost Paths)
When a switch has more than one equal-cost path to the root bridge, it works down this list in order until the tie breaks:
- Lowest sender BID — compare the BID of the switch sending the BPDU on each path (not your own switch's BID).
- Lowest sender port priority — default port priority is 128 on every port; the sender's lower-priority port wins.
- Lowest sender port ID — the final tiebreaker, based on the sending switch's port number (e.g. F0/1 beats F0/2), not the receiving switch's port.
All three criteria look at the sender's side of the link, never the receiver's — a common exam trap.
STP Port States
| Port State | BPDU | MAC Address Table | Forwarding Data Frames |
| Blocking | Receive only | No update | No |
| Listening | Receive and send | No update | No |
| Learning | Receive and send | Updating table | No |
| Forwarding | Receive and send | Updating table | Yes |
| Disabled | None sent or received | No update | No |
Transition path: Blocking (Max Age = 20s) → Listening (Forward Delay = 15s) → Learning (Forward Delay = 15s) → Forwarding. A port never jumps straight from blocking to forwarding — that's what would let a temporary loop form during the transition, so STP paces it out over roughly 30–50 seconds total. This slow convergence is the whole reason RSTP was developed.
Evolution of STP — Varieties
| Variety | Description |
| STP | Original IEEE 802.1D (1998 and earlier). Also called Common Spanning Tree (CST) — one spanning-tree instance for the entire bridged network, regardless of VLAN count. |
| PVST+ | Cisco enhancement — a separate 802.1D instance per VLAN. Supports PortFast, UplinkFast, BackboneFast, BPDU guard, BPDU filter, root guard, and loop guard. |
| 802.1D-2004 | Updated STP standard that folds in IEEE 802.1w. |
| RSTP (802.1w) | Rapid Spanning Tree — an evolution of STP providing much faster convergence. |
| Rapid PVST+ | Cisco enhancement combining RSTP with PVST+ — a separate 802.1w instance per VLAN, each supporting PortFast, BPDU guard, BPDU filter, root guard, and loop guard. |
| MSTP | Multiple Spanning Tree Protocol — an IEEE standard, inspired by Cisco's proprietary MISTP, that maps multiple VLANs into the same spanning-tree instance. |
| MST | Cisco's implementation of MSTP — up to 16 RSTP instances, combining VLANs that share the same physical/logical topology into a common instance. |
RSTP vs STP — Port States & Roles
| STP State | RSTP State |
| Disabled | Discarding |
| Blocking | Discarding |
| Listening | Discarding |
| Learning | Learning |
| Forwarding | Forwarding |
| STP Role | RSTP Role |
| Root Port | Root Port |
| Designated Port | Designated Port |
| Blocked (Non-Designated) | Backup Port |
| — | Alternate Port |
RSTP collapses STP's five port states into three (merging Disabled/Blocking/Listening into one Discarding state), and splits STP's single "blocked" role into two: an Alternate Port (a backup path to the root bridge via a different switch) and a Backup Port (a redundant path to the same segment via the same switch).
PATCH 17
EtherChannel (PAgP / LACP)
EtherChannel bundles multiple physical links into one logical link — more bandwidth, and since spanning tree sees the whole bundle as a single port, none of the redundant links get blocked.
PAgP (Cisco-Proprietary)
Port Aggregation Protocol negotiates the bundle by exchanging PAgP packets every 30 seconds, checking that both sides are configured consistently before enabling the channel.
| Mode | Behavior |
| On | Forces the interface into the channel with no negotiation — no PAgP packets exchanged. Only works if the other side is also set to on. |
| PAgP desirable | Active negotiating state — sends PAgP packets to initiate the negotiation. |
| PAgP auto | Passive negotiating state — responds to PAgP packets but never initiates. |
PAgP Mode Combinations
| S1 Mode | S2 Mode | Channel Forms? |
| On | On | Yes |
| On | Desirable / Auto | No |
| Desirable | Desirable | Yes |
| Desirable | Auto | Yes |
| Auto | Desirable | Yes |
| Auto | Auto | No |
The pattern: two passive/auto sides never form a channel (nobody initiates), and on only works with another on — it doesn't negotiate at all, so it can't detect a mismatched or auto/desirable partner.
LACP (IEEE 802.3ad — Multivendor)
Link Aggregation Control Protocol does the same job as PAgP, but as an open IEEE standard it works across vendors, not just Cisco-to-Cisco.
| Mode | Behavior |
| On | Forces the interface into the channel with no negotiation — no LACP packets exchanged. |
| LACP active | Active negotiating state — initiates negotiation by sending LACP packets. |
| LACP passive | Passive negotiating state — responds to LACP packets but never initiates. |
Mirrors PAgP's negotiation logic: active+active and active+passive both form a channel; passive+passive does not, since neither side initiates. Cisco switches support both PAgP and LACP.
EtherChannel requirement: every port in the bundle must share the same speed, duplex setting, and VLAN configuration. Changing one port's config after the channel forms changes every other port in that channel to match.
LACP Configuration (3 Steps)
| Step | Task | Command |
| 1 | Specify the interfaces that make up the channel | interface range interface-id |
| 2 | Create the port channel, in LACP mode | channel-group id mode active |
| 3 | Configure L2 settings on the resulting port-channel interface | interface port-channel id → switchport mode trunk → switchport trunk allowed vlan list |
Once created, Layer 2 settings (trunking, allowed VLANs) are configured on the logical port-channel interface itself — not on the individual member ports.
Verify EtherChannel
| Command | Shows |
| show interfaces port-channel | General status of the port channel interface |
| show etherchannel summary | One line of information per port channel — the fastest overall health check |
| show etherchannel port-channel | Detailed information about one specific port channel interface |
| show interfaces etherchannel | The role of one physical member interface within the EtherChannel |
show etherchannel summary Flags
| Flag | Meaning |
| D | Down |
| P | Bundled in port-channel |
| I | Stand-alone |
| s | Suspended |
| H | Hot-standby (LACP only) |
| R / S | Layer 3 / Layer 2 |
| U | In use |
| N | Not in use, no aggregation |
| M / m | Not in use — minimum links not met (M), or port not aggregated because of it (m) |
| u | Unsuitable for bundling |
| w | Waiting to be aggregated |
| A | Formed by Auto LAG |
Fastest read: in Po1(SU), the first letter is layer (S = Layer 2), the second is status (U = in use / working). Po1(SD) — Layer 2, Down — means the channel isn't up.
Troubleshooting Example: Mismatched PAgP Modes
A classic failure: show etherchannel summary shows Po1(SD) with both member ports flagged (D) — down. show run | begin interface port-channel reveals why: S1's ports are set to channel-group 1 mode on while S2's are set to mode desirable — an incompatible PAgP combination (see the mode table above), so no channel forms.
Fix: change both sides to a compatible mode (e.g. desirable on both). Critically, the port-channel interface is removed and re-added rather than edited directly:
- no interface port-channel 1
- interface range fa0/1 - 2 → channel-group 1 mode desirable → no shutdown
- interface port-channel 1 → switchport mode trunk
Why the removal step matters: EtherChannel and STP must interoperate, so editing the mode directly (without removing and re-adding the port-channel) causes STP errors — the affected ports can drop into blocking or err-disabled state instead of cleanly renegotiating. Once corrected, show etherchannel summary confirms Po1(SU) — up, both member ports (P) bundled.
PATCH 18
Router-on-a-Stick (Inter-VLAN Routing)
One physical router interface, divided into logical subinterfaces — one per VLAN — so a single link can route between every VLAN on the trunk.
| Task | Command |
| Enter the subinterface | interface g0/0/1.vlan-id |
| Tag the subinterface to a VLAN (802.1Q) | encapsulation dot1Q vlan-id |
| Assign the default-gateway IP for that VLAN | ip address ip-address subnet-mask |
| Return, then bring up the parent physical interface | interface g0/0/1 → no shutdown |
Key point: the parent physical interface itself gets no IP address — it's just enabled with no shutdown. Each subinterface acts as the default gateway for its own VLAN, and the switch side of that link must be configured as a trunk.
PATCH 19
DHCPv4
How a client obtains and renews an IPv4 lease, how to stand up a Cisco IOS router as the DHCPv4 server, and how to relay requests to a server on another subnet.
Steps to Obtain a Lease — DORA
A four-step process when a client boots or joins a network:
| Step | Message | Direction |
| 1 | DHCPDISCOVER | Client → broadcast: "I would like to request an address." |
| 2 | DHCPOFFER | Server → unicast: "Here is an address offer." |
| 3 | DHCPREQUEST | Client → broadcast: "I accept the IPv4 address offer." |
| 4 | DHCPACK | Server → unicast: "Your acceptance is acknowledged." |
Easy to remember as DORA — Discover, Offer, Request, Acknowledge.
Steps to Renew a Lease
Before the lease expires, a shorter two-step exchange — both sent directly (unicast) to the server that originally offered the address:
| Step | Message | Direction |
| 1 | DHCPREQUEST | Client → unicast to original server: "I would like to renew my lease." |
| 2 | DHCPACK | Server → unicast: "Your request is acknowledged." |
If no DHCPACK arrives in time, the client falls back to broadcasting a new DHCPREQUEST so any other DHCPv4 server can extend the lease. Per RFC 2131, DHCPOFFER/DHCPACK can be unicast or broadcast.
Steps to Configure a Cisco IOS DHCPv4 Server
| Step | Task | Command |
| 1 | Exclude addresses reserved for static devices (routers, servers, printers) | ip dhcp excluded-address low [high] |
| 2 | Create the pool, entering DHCPv4 config mode | ip dhcp pool pool-name |
| 3 | Define the address pool | network network-number [mask | /prefix-length] |
Optional Pool Commands
| Task | Command |
| Default gateway router | default-router address [address2...address8] |
| DNS server | dns-server address [address2...address8] |
| Domain name | domain-name domain |
| Lease duration | lease {days [hours [minutes]] | infinite} |
| NetBIOS WINS server | netbios-name-server address [address2...address8] |
Configuration Example
Excludes the router/DNS-facing addresses, then builds the pool with a gateway and DNS server reachable through another interface.
- ip dhcp excluded-address 192.168.10.1 192.168.10.9
- ip dhcp excluded-address 192.168.10.254
- ip dhcp pool LAN-POOL-1
- network 192.168.10.0 255.255.255.0
- default-router 192.168.10.1
- dns-server 192.168.11.5
- domain-name example.com
Verify: show running-config | section dhcp filters output down to just the DHCPv4-related lines.
DHCPv4 Relay
If the DHCPv4 server sits on a different subnet than the client, the router in between needs to relay the broadcast as a unicast to the server.
| Task | Command |
| Relay DHCPv4 broadcasts on this interface to a specific server | ip helper-address address |
Verify: show ip interface on the relaying interface shows a "Helper address is..." line.
Other Services Relayed by ip helper-address
By default the command forwards eight UDP services, not just DHCP:
| Port | Service |
| 37 | Time |
| 49 | TACACS |
| 53 | DNS |
| 67 | DHCP/BOOTP server |
| 68 | DHCP/BOOTP client |
| 69 | TFTP |
| 137 | NetBIOS name service |
| 138 | NetBIOS datagram service |
Enable / Disable the DHCPv4 Service
| Task | Command |
| Disable (DHCPv4 is on by default) | no service dhcp |
| Re-enable | service dhcp |
Caution: clearing DHCP bindings or stopping/restarting the service can temporarily hand out duplicate IP addresses on the network.
PATCH 20
SLAAC & DHCPv6
IPv6's equivalent of DHCP — except every device can build its own address without a server at all, via SLAAC. RA message flags decide how much (if any) DHCPv6 gets involved.
SLAAC Overview
- Stateless — no server tracks which IPv6 addresses are in use or available.
- The router sends periodic ICMPv6 Router Advertisement (RA) messages (every 200 seconds by default) with addressing info for hosts to self-configure.
- A host can also send a Router Solicitation (RS) to request an RA immediately, instead of waiting.
- Deployable as SLAAC only, or SLAAC combined with DHCPv6.
Enabling SLAAC on a Router
| Task | Command |
| Enable IPv6 routing (required for RA messages to be sent) | ipv6 unicast-routing |
show ipv6 interface confirms the link-local address, the GUA/subnet, and the multicast groups the interface has joined: FF02::1 (all-nodes — where RAs are sent every 200s) and FF02::2 (all-routers).
Host Interface ID Generation
| Method | Description |
| Randomly generated | The 64-bit interface ID is randomly generated by the OS. Default on Windows 10 hosts. |
| EUI-64 | Built from the host's 48-bit MAC address, with the hex value fffe inserted in the middle. |
Random generation is often preferred over EUI-64 for privacy — EUI-64 embeds the actual hardware MAC address in every IPv6 address the host uses. Windows, Linux, and macOS all let the user choose either method.
IPv6 GUA Assignment — Stateless vs Stateful
| Method | How It Works |
| SLAAC Only | RA provides network prefix, prefix length, and default gateway. Host uses the RA exclusively, creating its own GUA. |
| SLAAC with DHCP (Stateless DHCPv6) | RA provides addressing info and tells the host to contact a stateless DHCPv6 server for additional config (DNS, etc.) — the host still builds its own GUA via SLAAC. |
| DHCPv6 Server (Stateful DHCPv6) | RA tells the host to contact a stateful DHCPv6 server for everything except the default gateway (which still comes from the RA). The server tracks address bindings. |
Host operating systems generally follow the RA's suggestion, but the actual decision is ultimately up to the host.
Three RA Message Flags
| Flag | Meaning |
| A (Address Autoconfiguration) | Use SLAAC to create an IPv6 GUA. |
| O (Other Configuration) | Additional info (DNS, etc.) is available from a stateless DHCPv6 server. |
| M (Managed Address Configuration) | Use a stateful DHCPv6 server to obtain the GUA itself. |
Flag Combinations by Method
| Method | A | O | M |
| SLAAC Only (default) | 1 | 0 | 0 |
| Stateless DHCPv6 (SLAAC + DHCPv6) | 1 | 1 | 0 |
| Stateful DHCPv6 Only | 0 | 0 | 1 |
Enable Stateless DHCPv6 on an Interface
| Task | Command |
| Set the O flag to 1 (SLAAC + stateless DHCPv6) | ipv6 nd other-config-flag |
| Reset back to SLAAC-only default (O flag = 0) | no ipv6 nd other-config-flag |
Verify: show ipv6 interface id | begin ND confirms with plain-language lines: "Hosts use stateless autoconfig for addresses" / "Hosts use DHCP to obtain other configuration."
DHCPv6 Operation Steps
Whenever an RA indicates DHCPv6 (stateless or stateful) is in play, the same six-step exchange follows the initial RS/RA:
- Host sends a Router Solicitation (RS).
- Router responds with a Router Advertisement (RA).
- Host sends a DHCPv6 SOLICIT message.
- DHCPv6 server responds with an ADVERTISE message.
- Host responds to the DHCPv6 server (REQUEST or INFORMATION-REQUEST).
- DHCPv6 server sends a REPLY message.
Stateful DHCPv6 doesn't require SLAAC first; stateless DHCPv6 does. Server→client DHCPv6 messages use UDP destination port 546; client→server messages use UDP destination port 547.
DHCPv6 Router Roles
A single Cisco IOS router can be configured as any of the three:
| Role | What It Does |
| DHCPv6 Server | Provides stateless or stateful DHCPv6 services. |
| DHCPv6 Client | The router interface itself acquires its IPv6 config from a DHCPv6 server. |
| DHCPv6 Relay Agent | Forwards DHCPv6 requests when the client and server sit on different networks. |
Configure a Stateful DHCPv6 Server (5 Steps)
| Step | Task | Command |
| 1 | Enable IPv6 routing | ipv6 unicast-routing |
| 2 | Define a DHCPv6 pool name | ipv6 dhcp pool pool-name |
| 3 | Configure pool options (address prefix, DNS server, domain name, etc.) | address prefix prefix/length |
| 4 | Bind the pool to an interface | ipv6 dhcp server pool-name |
| 5 | Verify hosts received IPv6 addressing | ipconfig /all |
Stateful specifically requires two manual flag changes on the interface: ipv6 nd managed-config-flag sets M from 0 to 1, and ipv6 nd prefix default no-autoconfig sets A from 1 to 0 (telling clients not to use SLAAC). show ipv6 interface | begin ND confirms with "Hosts use DHCP to obtain routable addresses."
Configure a Stateless DHCPv6 Server (5 Steps)
Same overall flow as stateful, with two differences: pool options are typically just dns-server and domain-name (no address prefix, since SLAAC handles that), and the flag change is ipv6 nd other-config-flag (O flag 0→1) instead — the A flag stays at its default of 1, since hosts still use SLAAC for the GUA itself.
Configure a DHCPv6 Client (Router)
A router can be a DHCPv6 client too — it needs ipv6 unicast-routing and a link-local address to send/receive IPv6 messages (Cisco IOS builds the LLA with EUI-64).
| Client Type | Command |
| Stateful client | ipv6 address dhcp |
| Stateless client | ipv6 address autoconfig |
Verify: show ipv6 interface brief confirms the assigned GUA; show ipv6 dhcp interface id confirms other DHCPv6 info (DNS, domain name) was received.
Configure & Verify a DHCPv6 Relay Agent
Same idea as the IPv4 helper address — configured on the interface facing the clients, pointing at the DHCPv6 server:
| Task | Command |
| Relay DHCPv6 requests to a server | ipv6 dhcp relay destination address [egress-interface] |
The egress interface is only required when the next-hop address is a link-local address (LLA), since an LLA alone isn't enough to determine the outbound interface. Verify: show ipv6 dhcp interface on the relay confirms "in relay mode" with the relay destination(s); show ipv6 dhcp binding on the server shows the client's bound address.
DHCPv6 Server Verification Commands
| Command | Shows |
| show ipv6 dhcp pool | Pool name, address allocation prefix, DNS server, domain name, and number of active clients. |
| show ipv6 dhcp binding | Each client's link-local address, DUID, and the GUA the server assigned it — maintained only by a stateful server. A stateless server doesn't track this. |
PATCH 21
First Hop Redundancy Protocols (FHRP)
The ability of a network to dynamically recover from the failure of the device acting as the default gateway. A redundancy protocol decides which router is active and when a standby must take over — invisibly to the end hosts.
FHRP Options
| Protocol | Description |
| HSRP | Hot Standby Router Protocol — Cisco-proprietary. A group elects an active and a standby device; the active forwards traffic, the standby takes over on failure or preset conditions. |
| HSRP for IPv6 | Same functionality in an IPv6 environment. The group's virtual MAC derives from the HSRP group number, and its virtual LLA derives from that virtual MAC. |
| VRRPv2 | Non-proprietary election protocol for IPv4 — one router is elected virtual router master, others act as backups. |
| VRRPv3 | Adds IPv4 and IPv6 support; works in multivendor environments and scales better than VRRPv2. |
| GLBP | Gateway Load Balancing Protocol — Cisco-proprietary. Protects traffic like HSRP/VRRP, but also load-balances across a group of redundant routers instead of leaving backups idle. |
| GLBP for IPv6 | Same load-balancing functionality for IPv6 hosts configured with a single default gateway. |
| IRDP | ICMP Router Discovery Protocol (RFC 1256) — a legacy FHRP letting IPv4 hosts locate routers to nonlocal networks. |
Steps for Router Failover
What happens when the active router fails:
- The standby router stops seeing Hello messages from the forwarding (active) router.
- The standby router assumes the role of forwarding router.
- The new forwarding router takes over both the IPv4 and MAC addresses of the virtual router — so host devices see no disruption in service.
HSRP States & Timers
| State | Description |
| Initial | Entered on a configuration change or when the interface first becomes available. |
| Learn | Router hasn't determined the virtual IP yet and hasn't seen a hello from the active router — it waits. |
| Listen | Router knows the virtual IP but is neither active nor standby — it listens for hellos from those routers. |
| Speak | Router sends periodic hellos and actively participates in the active/standby election. |
| Standby | Router is a candidate to become the next active router and sends periodic hellos. |
Active and standby routers send hellos to the HSRP group multicast address every 3 seconds by default; the standby becomes active if it hears nothing for 10 seconds. These are tunable to speed up failover, but don't go below a 1-second hello timer or a 4-second hold timer — lower risks unnecessary standby-state flapping and higher CPU load.
HSRP Priority & Preemption
- By default, the router with the numerically highest IPv4 address becomes active — but explicit priority gives predictable control instead of leaving it to chance.
- Default HSRP priority is 100; range is 0–255. Highest priority wins the active role.
- If priorities tie, the numerically highest IPv4 address is the tiebreaker.
- Set priority with the interface command standby priority value.
Preemption: by default, once a router becomes active it stays active even if a higher-priority router later comes online. standby preempt (interface command) lets a newly-online higher-priority router trigger a re-election and take over. Without preemption enabled, whichever router boots first simply becomes — and remains — active.
PATCH 22
IOS Device Basics & Secure Remote Access
Routers and switches share the same modal CLI, command structure, and initial setup steps — name the device, then lock down access.
Basic Device Configuration
| Task | Command |
| Enter global configuration mode | configure terminal |
| Set the hostname | hostname name |
| Set the privileged EXEC (enable) password | enable secret password |
| Enter console line config | line console 0 |
| Set console password & require login | password pw → login |
| Enter vty (remote) line config, all 5 lines | line vty 0 4 |
| Set vty password & require login | password pw → login |
| Encrypt all plaintext passwords in the config | service password-encryption |
Configure SSH (6 Steps)
| Step | Action | Command |
| 1 | Verify SSH support (fails if IOS lacks crypto features) | show ip ssh |
| 2 | Configure the IP domain name | ip domain-name name |
| 3 | Generate the RSA key pair (this is what actually enables SSH) | crypto key generate rsa |
| 4 | Configure local user authentication | username user secret pw |
| 5 | Restrict vty lines to SSH only, require local login | transport input ssh → login local |
| 6 | Force SSH version 2 | ip ssh version 2 |
Deleting the RSA key pair (crypto key zeroize rsa) automatically disables the SSH server.
Filtering show Command Output
Long output pauses every 24 lines by default (--More--). terminal length 0 disables paging entirely. Add a pipe | after any show command to filter what's returned.
| Filter | Effect |
| section | Shows the entire section that starts with the matching expression |
| include | Includes only output lines that match the expression |
| exclude | Excludes output lines that match the expression |
| begin | Shows output starting from the first line that matches the expression |
PATCH 24
IEEE 802.x Standards Family
"802" is the IEEE working group for LAN/MAN standards. Each sub-number covers a different piece of the stack — mostly Layer 1–2. These show up throughout the exam even when the question doesn't say "802" out loud.
802 Family Overview
| Standard | Name | Covers |
| 802.1 | Bridging & Management | STP, VLAN tagging (802.1Q), port-based auth (802.1X) — see amendments below |
| 802.2 | LLC | Logical Link Control sublayer of Layer 2 |
| 802.3 | Ethernet | Wired LAN, CSMA/CD, cabling/speed variants |
| 802.5 | Token Ring | Legacy token-passing LAN (largely obsolete) |
| 802.11 | Wi-Fi | Wireless LAN (WLAN) — see generations below |
| 802.15 | WPAN / Bluetooth | Wireless Personal Area Network standard |
| 802.15.4 | LR-WPAN / Zigbee | Low-rate, low-power — primarily IoT |
| 802.16 | WiMAX | Point-to-multipoint broadband wireless (MAN) |
802.11 Wi-Fi Generations
| Amendment | Wi-Fi Gen | Frequency | Max Data Rate | Notes |
| 802.11a | — | 5 GHz | 54 Mbps | Not compatible with 802.11b (different band) |
| 802.11b | — | 2.4 GHz | 11 Mbps | First mainstream consumer Wi-Fi |
| 802.11g | — | 2.4 GHz | 54 Mbps | Backward compatible with 802.11b |
| 802.11n | Wi-Fi 4 | 2.4 & 5 GHz | ~600 Mbps | Introduced MIMO (multiple antennas) |
| 802.11ac | Wi-Fi 5 | 5 GHz | ~3.5 Gbps | MU-MIMO, wider channels |
| 802.11ax | Wi-Fi 6 / 6E | 2.4, 5 & 6 GHz* | ~9.6 Gbps | OFDMA — better efficiency in dense/congested environments |
*6 GHz band applies to Wi-Fi 6E specifically. Higher frequencies (5/6 GHz) carry more bandwidth but shorter range/worse wall penetration than 2.4 GHz.
Key 802.1 Amendments (Switching)
| Amendment | Purpose |
| 802.1Q | VLAN tagging / trunking between switches |
| 802.1D | Spanning Tree Protocol (STP) — loop prevention |
| 802.1w | Rapid STP (RSTP) — faster convergence |
| 802.1s | Multiple STP (MSTP) — maps VLANs to STP instances |
| 802.1X | Port-based network access control (authentication) |
| 802.1AB | LLDP — vendor-neutral neighbor discovery |
802.3 Ethernet Speed Variants
| Name | Speed | Media | Max Distance |
| 10BASE-T | 10 Mbps | Cat3 UTP | 100 m |
| 100BASE-TX | 100 Mbps (Fast Ethernet) | Cat5 UTP | 100 m |
| 1000BASE-T | 1 Gbps (Gigabit Ethernet) | Cat5e UTP | 100 m |
| 10GBASE-T | 10 Gbps | Cat6a UTP | 100 m |
Memory hook: in 802.11 lettering, later letters ≠ newer in a straight line (b → a → g → n → ac → ax chronologically, not alphabetically) — go by the Wi-Fi generation number when you can.
PATCH 25
Default Administrative Distances
Lower AD wins when the same route is learned from multiple sources.
| AD | Route Source |
| 0 | Directly connected / static to a directly-connected next hop |
| 1 | Static route (with next-hop IP) |
| 5 | EIGRP summary route |
| 20 | External BGP |
| 90 | Internal EIGRP |
| 100 | IGRP |
| 110 | OSPF |
| 115 | IS-IS |
| 120 | RIP |
| 170 | External EIGRP |
| 200 | Internal BGP |
| 255 | Unknown / unusable — route not installed |
PATCH 26
What's On the CCNA 200-301 Exam
The current blueprint is v1.1, live through February 2, 2027 (v2.0 takes over the same 200-301 exam number on Feb 3, 2027 — check for an updated topic list if your test date lands after that). Cisco runs it as a single 120-minute exam, roughly 100–120 questions, across six weighted domains.
| Domain | Weight | What It Covers |
| 1.0 Network Fundamentals |
20% |
Devices (routers, L2/L3 switches, firewalls, APs), topology types, cabling, TCP vs UDP, IPv4/IPv6 addressing & subnetting, wireless basics, virtualization/VRFs, switching concepts (MAC table, flooding) |
| 2.0 Network Access |
20% |
VLANs & trunking (802.1Q), EtherChannel/LACP, Spanning Tree (Rapid PVST+, guards), CDP/LLDP, wireless architectures & AP modes, device management access methods |
| 3.0 IP Connectivity |
25% |
Reading the routing table, forwarding decisions (longest match, AD, metric), IPv4/IPv6 static routing, single-area OSPFv2, first-hop redundancy (HSRP/VRRP/GLBP) |
| 4.0 IP Services |
10% |
NAT/PAT, NTP, DHCP & DNS roles, SNMP, syslog severity levels, QoS per-hop behavior, SSH remote access, TFTP/FTP |
| 5.0 Security Fundamentals |
15% |
Core security concepts, device hardening & password policy, site-to-site/remote-access VPNs, ACLs, Layer 2 security (port security, DHCP snooping, DAI), AAA, wireless security (WPA/WPA2/WPA3) |
| 6.0 Automation & Programmability |
10% |
How automation changes network management, controller-based/SDN architecture (overlay/underlay/fabric), AI & ML in network ops, REST API basics, config management (Ansible/Terraform), reading JSON |
Where the points are: Domains 1–3 alone are 65% of the exam, and all three lean on the same two skills — fast subnetting and reading show command output. Domain 3 (IP Connectivity) outweighs Domains 4 and 6 combined, so if something has to give in your study time, don't let routing/OSPF slip.
What This Cutsheet Covers
This page is strongest on Domain 1 and touches Domain 2/3 — it does not cover Domain 5 (Security) or Domain 6 (Automation) yet.
| Domain | Covered by |
| 1.0 Network Fundamentals | Patches 01–08, 12–14 (ports, IP classes/private ranges, subnetting, binary practice, IPv6, OSI/TCP-IP, MAC addressing, physical media, 802.11/802.3) |
| 2.0 Network Access | Patches 14–17 (VLANs, trunking, DTP, switching concepts, STP, EtherChannel/PAgP/LACP) |
| 3.0 IP Connectivity | Patches 15, 21 (Administrative Distance, FHRP) — routing table/OSPF not yet included |
| 4.0 IP Services | Patches 01–02, 10–11, 19–20 (ports, port groups, TCP/UDP headers, ICMP, DHCPv4, SLAAC/DHCPv6) — NAT/NTP/QoS not yet included |
| 5.0 Security Fundamentals | Not yet covered |
| 6.0 Automation & Programmability | Not yet covered |