reference sheet · offline-friendly

CCNA Cutsheets

Quick-reference tables for ports, IP address classes, private ranges, subnetting math, IPv6 compression, the OSI/TCP-IP models, transport headers, ICMP, MAC addressing, physical media, and administrative distances — built to skim during study or keep open in a second tab during labs.

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.

PortProtocolTransportPurpose
20 / 21FTPTCPFile transfer (data / control)
22SSHTCPSecure remote shell
23TelnetTCPUnencrypted remote shell
25SMTPTCPMail transfer (send)
53DNSTCP/UDPName resolution (UDP queries, TCP zone transfers)
67 / 68DHCPUDPServer (67) / Client (68) address assignment
69TFTPUDPTrivial file transfer — IOS image/config backup
80HTTPTCPWeb traffic, unencrypted
110POP3TCPMail retrieval (download & delete)
123NTPUDPClock synchronization
143IMAPTCPMail retrieval (synced, stays on server)
161 / 162SNMPUDPDevice monitoring / traps
179BGPTCPBorder Gateway Protocol peering
389LDAPTCPDirectory services lookup
443HTTPSTCPWeb traffic, TLS-encrypted
445SMBTCPWindows file/printer sharing
514SyslogUDPLogging to a remote collector
520RIPUDPRouting Information Protocol updates
3389RDPTCPRemote 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 GroupNumber RangeDescription
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.

Class1st Octet RangeDefault MaskDefault /Purpose
A1 – 126255.0.0.0/8Large networks
B128 – 191255.255.0.0/16Medium networks
C192 – 223255.255.255.0/24Small networks
D224 – 239n/aMulticast
E240 – 255n/aExperimental / 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

ClassRangeCIDRHosts
A10.0.0.0 – 10.255.255.25510.0.0.0/816,777,214
B172.16.0.0 – 172.31.255.255172.16.0.0/121,048,574
C192.168.0.0 – 192.168.255.255192.168.0.0/1665,534
RangePurpose
127.0.0.0/8Loopback
169.254.0.0/16APIPA / link-local
224.0.0.0/4Multicast (Class D)
255.255.255.255Limited 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).

CIDRSubnet MaskWildcard MaskUsable Hosts4th-Octet Block Size
/24255.255.255.00.0.0.255254256
/25255.255.255.1280.0.0.127126128
/26255.255.255.1920.0.0.636264
/27255.255.255.2240.0.0.313032
/28255.255.255.2400.0.0.151416
/29255.255.255.2480.0.0.768
/30255.255.255.2520.0.0.324
/31255.255.255.2540.0.0.12 (P2P, RFC 3021)2
/32255.255.255.2550.0.0.01 (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)
DecimalBinaryHex
0–90000–10010–9
101010A
111011B
121100C
131101D
141110E
151111F
Quick Binary Chart (Place Values)
Bit Place12345678
Place Value1286432168421
Custom Subnet Mask (CSM)128192224240248252254255
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
Octet128192224240248252254255
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
  1. Fill in what's given.
  2. Determine the Class of the given IP address.
  3. Fill in the Default Subnet Mask (DSM) for that class.
  4. Bit out the DSM and draw the default line.
  5. Determine # of subnets (BBN) or # of hosts (BBH) using the Power-of-2 chart (2n − 2).
  6. BBN + BBH = free bits.
  7. 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.
  8. Use the last bit turned on to determine which octet the INC applies to.
  9. Solve SubID = IP × CSM (in binary — "ANDing").
  10. Solve BC (broadcast) = (SubID + INC) − 1 in the 4th octet.
  11. 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.

RuleWhat it doesBeforeAfter
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 AddressCompressedNote
fe80:0000:0000:0000:0202:b3ff:fe1e:8329fe80::202:b3ff:fe1e:8329Single zero-run in the middle, plus leading zeros dropped
2001:0db8:0000:0000:0000:0000:0000:00012001:db8::1One long zero-run compressed to ::
0000:0000:0000:0000:0000:0000:0000:0001::1Loopback — 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:00012001:db8:0:1::1Two 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.

PATCH 08

IPv4 & IPv6 Packet Header Fields

The Layer 3 header every routed packet carries. IPv6 was designed to simplify this header for faster router processing — several IPv4 fields were dropped entirely or pushed into optional extension headers.

IPv4 Header (20-byte minimum, variable length)
FieldSizeDescription
Version4 bitsIP version — always 4 for IPv4.
Header Length (IHL)4 bitsLength of the header in 32-bit words; needed because Options makes the header variable-length.
Type of Service (DSCP/ECN)8 bitsMarks the packet for QoS handling (priority/DSCP) and congestion notification (ECN).
Total Length16 bitsEntire packet size (header + data) in bytes.
Identification16 bitsUniquely identifies fragments belonging to the same original packet.
Flags3 bitsControls/reports fragmentation — includes "Don't Fragment" and "More Fragments" bits.
Fragment Offset13 bitsPosition of this fragment within the original, unfragmented packet.
Time to Live (TTL)8 bitsDecremented by each hop; packet is discarded when it hits 0 — prevents routing loops.
Protocol8 bitsIdentifies the encapsulated Layer 4 protocol (e.g. 6 = TCP, 17 = UDP, 1 = ICMP).
Header Checksum16 bitsError-checks the header only (not the payload); recalculated at every hop since TTL changes.
Source Address32 bitsSending device's IPv4 address.
Destination Address32 bitsReceiving device's IPv4 address.
Options + PaddingVariableRarely used (e.g. security, timestamps); padded to keep the header a multiple of 32 bits.
IPv6 Header (fixed 40 bytes)
FieldSizeDescription
Version4 bitsIP version — always 6 for IPv6.
Traffic Class8 bitsEquivalent to IPv4's ToS/DSCP — marks the packet for QoS handling.
Flow Label20 bitsTags packets belonging to the same flow so routers can handle them consistently — new in IPv6.
Payload Length16 bitsSize of the payload only (everything after this 40-byte header), in bytes.
Next Header8 bitsIdentifies the next header — either a Layer 4 protocol (TCP/UDP/ICMPv6) or an IPv6 extension header.
Hop Limit8 bitsSame role as IPv4 TTL — decremented per hop, packet dropped at 0.
Source Address128 bitsSending device's IPv6 address.
Destination Address128 bitsReceiving device's IPv6 address.
What Changed From IPv4 → IPv6
IPv4 FieldIPv6 Treatment
Header Length (IHL)Removed — the base header is a fixed 40 bytes, no length field needed.
Header ChecksumRemoved entirely — relies on Layer 2 and Layer 4 checksums instead, cutting per-hop router overhead.
Identification / Flags / Fragment OffsetRemoved from the base header — routers no longer fragment in transit; the source uses a Fragment extension header if needed (Path MTU Discovery is preferred).
OptionsReplaced by chained extension headers (e.g. Hop-by-Hop, Routing, Fragment, ESP/AH) referenced via Next Header — keeps the base header simple and fixed-size.
Time to LiveRenamed Hop Limit — same function.
Type of ServiceRenamed Traffic Class — same function.
— (new)Flow Label added — no IPv4 equivalent.
Why it matters: a fixed-size, checksum-free base header means every router can process an IPv6 packet's header faster and more predictably than an IPv4 one — a deliberate design trade-off for scale.
PATCH 09

OSI Model vs TCP/IP Model

LayerOSITCP/IP GroupPDUExamples
7ApplicationApplicationDataHTTP, DNS, DHCP, SSH, FTP, SMTP, IMAP
6PresentationApplicationDataTLS, encoding, compression, encryption
5SessionApplicationDataSession establishment, RPC
4TransportTransportSegment (TCP) / Datagram (UDP)TCP, UDP
3NetworkInternetPacketIP, ICMP, routing protocols
2Data LinkNetwork AccessFrameEthernet, MAC, switching
1PhysicalNetwork AccessBitsCabling, 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
MethodDescription
GETClient request for data — a browser sends GET to request HTML pages/resources.
POSTUploads data files to the web server, such as form data.
PUTUploads 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 11

TCP & UDP Header Fields

TCP carries a heavier, connection-oriented header for reliability; UDP strips it down to four fields for speed.

TCP Header Fields
FieldDescription
Source Port16-bit field identifying the source application by port number.
Destination Port16-bit field identifying the destination application by port number.
Sequence Number32-bit field used for data reassembly.
Acknowledgment Number32-bit field indicating data received and the next byte expected from the source.
Header Length4-bit "data offset" field indicating the length of the TCP segment header.
Reserved6-bit field reserved for future use.
Control Bits6-bit field of flags indicating the purpose/function of the segment (SYN, ACK, FIN, etc.).
Window Size16-bit field indicating the number of bytes that can be accepted at one time.
Checksum16-bit field used for error checking of the segment header and data.
Urgent16-bit field indicating whether the contained data is urgent.
UDP Header Fields
FieldDescription
Source Port16-bit field identifying the source application by port number.
Destination Port16-bit field identifying the destination application by port number.
Length16-bit field indicating the length of the UDP datagram header.
Checksum16-bit field used for error checking of the datagram header and data.
Why the difference: TCP's extra fields (sequence/ack numbers, window size, control bits) exist to guarantee delivery and ordering. UDP skips all of that for lower overhead — fire-and-forget.
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.

CodeICMPv4 Meaning
0Net unreachable
1Host unreachable
2Protocol unreachable
3Port unreachable
CodeICMPv6 Meaning
0No route to destination
1Communication administratively prohibited (e.g. firewall)
2Beyond scope of the source address
3Address unreachable
4Port 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
Multicast MAC Addresses
Encapsulated DataDestination MAC Prefix
IPv4 multicast packet01-00-5E
IPv6 multicast packet33-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
TaskIOS Command
Enter global configuration modeconfigure terminal
Create a VLAN with a valid IDvlan vlan-id
Name the VLANname vlan-name
Return to privileged EXECend
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
TaskCommand
Enter global configuration modeconfigure terminal
Enter interface configuration modeinterface interface-id
Set the port to access modeswitchport mode access
Assign the port to a VLANswitchport access vlan vlan-id
Return to privileged EXECend
Trunk Configuration Commands

Trunks are Layer 2 links that carry traffic for all VLANs between switches (or switch-to-router).

TaskCommand
Enter global configuration modeconfigure terminal
Enter interface configuration modeinterface interface-id
Set the port to permanent trunking modeswitchport mode trunk
Set the native VLAN to something other than VLAN 1switchport trunk native vlan vlan-id
Specify which VLANs are allowed on the trunkswitchport trunk allowed vlan vlan-list
Return to privileged EXECend
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.

TaskCommand
Assign the access (data) VLANswitchport access vlan vlan-id
Trust the CoS marking from the phonemls qos trust cos
Assign the voice VLANswitchport voice vlan vlan-id
VLAN Ranges on Catalyst Switches
Normal Range (VLAN 1–1005)Extended Range (VLAN 1006–4095)
Used in small-to-medium businessesUsed 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 deletedSupports fewer VLAN features
Stored in the vlan.dat file in flashRequires 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 AutoDynamic DesirableTrunkAccess
Dynamic AutoAccessTrunkTrunkAccess
Dynamic DesirableTrunkTrunkTrunkAccess
TrunkTrunkTrunkTrunkLimited connectivity
AccessAccessAccessLimited connectivityAccess
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
The Switch Learn & Forward Method (2 Steps)
StepAction
1. LearnExamines 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. ForwardExamines 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.

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
StepElectionRule
1Root BridgeOne per spanning-tree instance — the switch with the lowest BID. All of its ports become designated ports.
2Root PortOne per non-root switch — the port with the lowest internal root path cost back to the root bridge.
3Designated PortOne 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 PortAnything 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 SpeedSTP Cost (IEEE 802.1D-1998)RSTP Cost (IEEE 802.1w-2004)
10 Gbps22,000
1 Gbps420,000
100 Mbps19200,000
10 Mbps1002,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:

  1. Lowest sender BID — compare the BID of the switch sending the BPDU on each path (not your own switch's BID).
  2. Lowest sender port priority — default port priority is 128 on every port; the sender's lower-priority port wins.
  3. 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 StateBPDUMAC Address TableForwarding Data Frames
BlockingReceive onlyNo updateNo
ListeningReceive and sendNo updateNo
LearningReceive and sendUpdating tableNo
ForwardingReceive and sendUpdating tableYes
DisabledNone sent or receivedNo updateNo
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
VarietyDescription
STPOriginal 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-2004Updated 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.
MSTPMultiple Spanning Tree Protocol — an IEEE standard, inspired by Cisco's proprietary MISTP, that maps multiple VLANs into the same spanning-tree instance.
MSTCisco'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 StateRSTP State
DisabledDiscarding
BlockingDiscarding
ListeningDiscarding
LearningLearning
ForwardingForwarding
STP RoleRSTP Role
Root PortRoot Port
Designated PortDesignated 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.

ModeBehavior
OnForces the interface into the channel with no negotiation — no PAgP packets exchanged. Only works if the other side is also set to on.
PAgP desirableActive negotiating state — sends PAgP packets to initiate the negotiation.
PAgP autoPassive negotiating state — responds to PAgP packets but never initiates.
PAgP Mode Combinations
S1 ModeS2 ModeChannel Forms?
OnOnYes
OnDesirable / AutoNo
DesirableDesirableYes
DesirableAutoYes
AutoDesirableYes
AutoAutoNo
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.

ModeBehavior
OnForces the interface into the channel with no negotiation — no LACP packets exchanged.
LACP activeActive negotiating state — initiates negotiation by sending LACP packets.
LACP passivePassive 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)
StepTaskCommand
1Specify the interfaces that make up the channelinterface range interface-id
2Create the port channel, in LACP modechannel-group id mode active
3Configure L2 settings on the resulting port-channel interfaceinterface 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
CommandShows
show interfaces port-channelGeneral status of the port channel interface
show etherchannel summaryOne line of information per port channel — the fastest overall health check
show etherchannel port-channelDetailed information about one specific port channel interface
show interfaces etherchannelThe role of one physical member interface within the EtherChannel
show etherchannel summary Flags
FlagMeaning
DDown
PBundled in port-channel
IStand-alone
sSuspended
HHot-standby (LACP only)
R / SLayer 3 / Layer 2
UIn use
NNot in use, no aggregation
M / mNot in use — minimum links not met (M), or port not aggregated because of it (m)
uUnsuitable for bundling
wWaiting to be aggregated
AFormed 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:

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.

TaskCommand
Enter the subinterfaceinterface g0/0/1.vlan-id
Tag the subinterface to a VLAN (802.1Q)encapsulation dot1Q vlan-id
Assign the default-gateway IP for that VLANip address ip-address subnet-mask
Return, then bring up the parent physical interfaceinterface 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:

StepMessageDirection
1DHCPDISCOVERClient → broadcast: "I would like to request an address."
2DHCPOFFERServer → unicast: "Here is an address offer."
3DHCPREQUESTClient → broadcast: "I accept the IPv4 address offer."
4DHCPACKServer → 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:

StepMessageDirection
1DHCPREQUESTClient → unicast to original server: "I would like to renew my lease."
2DHCPACKServer → 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
StepTaskCommand
1Exclude addresses reserved for static devices (routers, servers, printers)ip dhcp excluded-address low [high]
2Create the pool, entering DHCPv4 config modeip dhcp pool pool-name
3Define the address poolnetwork network-number [mask | /prefix-length]
Optional Pool Commands
TaskCommand
Default gateway routerdefault-router address [address2...address8]
DNS serverdns-server address [address2...address8]
Domain namedomain-name domain
Lease durationlease {days [hours [minutes]] | infinite}
NetBIOS WINS servernetbios-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.

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.

TaskCommand
Relay DHCPv4 broadcasts on this interface to a specific serverip 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:

PortService
37Time
49TACACS
53DNS
67DHCP/BOOTP server
68DHCP/BOOTP client
69TFTP
137NetBIOS name service
138NetBIOS datagram service
Enable / Disable the DHCPv4 Service
TaskCommand
Disable (DHCPv4 is on by default)no service dhcp
Re-enableservice 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
Enabling SLAAC on a Router
TaskCommand
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
MethodDescription
Randomly generatedThe 64-bit interface ID is randomly generated by the OS. Default on Windows 10 hosts.
EUI-64Built 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
MethodHow It Works
SLAAC OnlyRA 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
FlagMeaning
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
MethodAOM
SLAAC Only (default)100
Stateless DHCPv6 (SLAAC + DHCPv6)110
Stateful DHCPv6 Only001
Enable Stateless DHCPv6 on an Interface
TaskCommand
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:

  1. Host sends a Router Solicitation (RS).
  2. Router responds with a Router Advertisement (RA).
  3. Host sends a DHCPv6 SOLICIT message.
  4. DHCPv6 server responds with an ADVERTISE message.
  5. Host responds to the DHCPv6 server (REQUEST or INFORMATION-REQUEST).
  6. 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:

RoleWhat It Does
DHCPv6 ServerProvides stateless or stateful DHCPv6 services.
DHCPv6 ClientThe router interface itself acquires its IPv6 config from a DHCPv6 server.
DHCPv6 Relay AgentForwards DHCPv6 requests when the client and server sit on different networks.
Configure a Stateful DHCPv6 Server (5 Steps)
StepTaskCommand
1Enable IPv6 routingipv6 unicast-routing
2Define a DHCPv6 pool nameipv6 dhcp pool pool-name
3Configure pool options (address prefix, DNS server, domain name, etc.)address prefix prefix/length
4Bind the pool to an interfaceipv6 dhcp server pool-name
5Verify hosts received IPv6 addressingipconfig /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 TypeCommand
Stateful clientipv6 address dhcp
Stateless clientipv6 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:

TaskCommand
Relay DHCPv6 requests to a serveripv6 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
CommandShows
show ipv6 dhcp poolPool name, address allocation prefix, DNS server, domain name, and number of active clients.
show ipv6 dhcp bindingEach 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
ProtocolDescription
HSRPHot 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 IPv6Same 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.
VRRPv2Non-proprietary election protocol for IPv4 — one router is elected virtual router master, others act as backups.
VRRPv3Adds IPv4 and IPv6 support; works in multivendor environments and scales better than VRRPv2.
GLBPGateway 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 IPv6Same load-balancing functionality for IPv6 hosts configured with a single default gateway.
IRDPICMP 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:

  1. The standby router stops seeing Hello messages from the forwarding (active) router.
  2. The standby router assumes the role of forwarding router.
  3. 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
StateDescription
InitialEntered on a configuration change or when the interface first becomes available.
LearnRouter hasn't determined the virtual IP yet and hasn't seen a hello from the active router — it waits.
ListenRouter knows the virtual IP but is neither active nor standby — it listens for hellos from those routers.
SpeakRouter sends periodic hellos and actively participates in the active/standby election.
StandbyRouter 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
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
TaskCommand
Enter global configuration modeconfigure terminal
Set the hostnamehostname name
Set the privileged EXEC (enable) passwordenable secret password
Enter console line configline console 0
Set console password & require loginpassword pw → login
Enter vty (remote) line config, all 5 linesline vty 0 4
Set vty password & require loginpassword pw → login
Encrypt all plaintext passwords in the configservice password-encryption
Configure SSH (6 Steps)
StepActionCommand
1Verify SSH support (fails if IOS lacks crypto features)show ip ssh
2Configure the IP domain nameip domain-name name
3Generate the RSA key pair (this is what actually enables SSH)crypto key generate rsa
4Configure local user authenticationusername user secret pw
5Restrict vty lines to SSH only, require local logintransport input ssh → login local
6Force SSH version 2ip 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.

FilterEffect
sectionShows the entire section that starts with the matching expression
includeIncludes only output lines that match the expression
excludeExcludes output lines that match the expression
beginShows output starting from the first line that matches the expression
PATCH 23

Physical Media — Cabling & Wireless

UTP Cabling
Cable TypeStandardApplication
Ethernet Straight-throughBoth ends T568A or both T568BHost to network device
Ethernet Crossover*One end T568A, other end T568BHost-to-host, switch-to-switch, router-to-router
RolloverCisco proprietaryHost serial port to router/switch console port, via adapter
*Crossover is considered legacy — most modern NICs use Auto-MDIX to sense the cable type and complete the connection automatically.
Fiber-Optic Media
FeatureSingle-Mode FiberMultimode Fiber
Core sizeGlass core ≈ 9 micronsGlass core ≈ 50/62.5 microns
Light pathSingle straight pathMultiple paths for light
Light sourceExpensive lasersLess expensive LEDs, transmitting at different angles
Best forLong-distance applicationsUp to 10 Gbps over 550 meters
Dispersion = the spreading of a light pulse over time/distance, causing signal loss. MMF has greater dispersion than SMF, capping its practical distance around 550 meters.
Wireless Standards
StandardIEEEDescription
Wi-Fi802.11Wireless LAN (WLAN) technology
Bluetooth802.15Wireless Personal Area Network (WPAN) standard
WiMAX802.16Point-to-multipoint topology for broadband wireless access
Zigbee802.15.4Low data-rate, low power — primarily for IoT applications
Physical layer specs for each wireless standard dictate: data-to-radio-signal encoding, frequency/power of transmission, signal reception/decoding, and antenna design.
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
StandardNameCovers
802.1Bridging & ManagementSTP, VLAN tagging (802.1Q), port-based auth (802.1X) — see amendments below
802.2LLCLogical Link Control sublayer of Layer 2
802.3EthernetWired LAN, CSMA/CD, cabling/speed variants
802.5Token RingLegacy token-passing LAN (largely obsolete)
802.11Wi-FiWireless LAN (WLAN) — see generations below
802.15WPAN / BluetoothWireless Personal Area Network standard
802.15.4LR-WPAN / ZigbeeLow-rate, low-power — primarily IoT
802.16WiMAXPoint-to-multipoint broadband wireless (MAN)
802.11 Wi-Fi Generations
AmendmentWi-Fi GenFrequencyMax Data RateNotes
802.11a5 GHz54 MbpsNot compatible with 802.11b (different band)
802.11b2.4 GHz11 MbpsFirst mainstream consumer Wi-Fi
802.11g2.4 GHz54 MbpsBackward compatible with 802.11b
802.11nWi-Fi 42.4 & 5 GHz~600 MbpsIntroduced MIMO (multiple antennas)
802.11acWi-Fi 55 GHz~3.5 GbpsMU-MIMO, wider channels
802.11axWi-Fi 6 / 6E2.4, 5 & 6 GHz*~9.6 GbpsOFDMA — 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)
AmendmentPurpose
802.1QVLAN tagging / trunking between switches
802.1DSpanning Tree Protocol (STP) — loop prevention
802.1wRapid STP (RSTP) — faster convergence
802.1sMultiple STP (MSTP) — maps VLANs to STP instances
802.1XPort-based network access control (authentication)
802.1ABLLDP — vendor-neutral neighbor discovery
802.3 Ethernet Speed Variants
NameSpeedMediaMax Distance
10BASE-T10 MbpsCat3 UTP100 m
100BASE-TX100 Mbps (Fast Ethernet)Cat5 UTP100 m
1000BASE-T1 Gbps (Gigabit Ethernet)Cat5e UTP100 m
10GBASE-T10 GbpsCat6a UTP100 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 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.

DomainWeightWhat 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.

DomainCovered by
1.0 Network FundamentalsPatches 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 AccessPatches 14–17 (VLANs, trunking, DTP, switching concepts, STP, EtherChannel/PAgP/LACP)
3.0 IP ConnectivityPatches 15, 21 (Administrative Distance, FHRP) — routing table/OSPF not yet included
4.0 IP ServicesPatches 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 FundamentalsNot yet covered
6.0 Automation & ProgrammabilityNot yet covered