Cisco 200-301: IPv4 Addressing, Subnetting and Routing — Study Guide

By Laurynas Brazys · 14 August 2026 · #cisco #200-301 #certification #exam-prep #study-guide

Part of the Cisco CCNA 200-301 — Study Guide. Practice with verified answers in the Cisco exam hub, or take timed practice tests on ExamRoll.io.

Overview

IPv4 addressing and routing underpin how packets are identified, segmented into subnets, and forwarded across networks. Mastering address structures, masks, ARP-based local delivery, and routing decisions (including longest prefix match and recursive resolution) is essential for building scalable and resilient topologies. This section explains how to design subnets, calculate ranges, configure gateways and static routes, verify reachability, and reason about trade-offs between summarization, scale, and fault isolation.

IPv4 Addressing Fundamentals

An IPv4 address is 32 bits, typically shown in dotted decimal. Conceptually, each address consists of a network portion and a host portion, defined by the subnet mask.

• Public vs private space

  • Public addresses are globally unique and routable on the Internet.
  • Private (RFC 1918) ranges are not globally routable and are intended for internal use:
    • 10.0.0.0/8
    • 172.16.0.0/12
    • 192.168.0.0/16
  • Private addressing conserves global space and allows different organizations to reuse the same ranges internally; NAT is typically used for Internet access.

• Special-use ranges and addresses

  • 0.0.0.0/0: the default route (matches any destination).
  • 0.0.0.0/8: “this network” (historical; not used for host assignment).
  • 127.0.0.0/8: loopback addresses (local host testing).
  • 169.254.0.0/16: link-local addresses (APIPA), used when DHCP fails on some hosts.
  • 224.0.0.0/4: multicast.
  • 240.0.0.0/4: reserved (Class E).
  • 255.255.255.255: limited broadcast (local network broadcast).
  • Directed broadcast: network + all-ones host (e.g., 10.1.1.255 for /24); disabled by default on routers to prevent abuse.

Common failure modes

• Using private ranges expecting global Internet reachability without NAT.
• Assigning addresses from special ranges (e.g., 127/8 or 169.254/16) to interfaces.
• Overlapping subnets across sites causing ambiguous routing.

Subnetting, VLSM, and Summarization

Subnet masks define how many bits are network versus host. Classless Inter-Domain Routing (CIDR) uses prefix length notation (/N). Variable-Length Subnet Masks (VLSM) allow different-sized subnets within the same address space to match actual requirements.

• Calculations

  • Block size per octet = 256 − mask value in that octet (for non-255/0 octets).
  • Network address: set host bits to 0.
  • Broadcast address: set host bits to 1.
  • Usable range: from network+1 to broadcast−1 (for subnets with ≥2 host bits).
  • Example: 192.168.10.0/26
    • Mask: 255.255.255.192; block size 64
    • Subnets: .0, .64, .128, .192
    • For 192.168.10.64/26: network .64, broadcast .127, usable .65–.126

• Point-to-point links

  • /30 (255.255.255.252) provides two usable addresses; common between routers.
  • /31 (RFC 3021) allows two endpoints with no broadcast; efficient on modern gear.

• VLSM design steps

  • Inventory required subnets and host counts.
  • Sort by size, assign largest first on clean boundaries.
  • Avoid overlaps; document allocations meticulously.
  • Use route summarization on distribution/edge to compress advertisements.

• Route summarization

  • Aggregate contiguous subnets that share the same high-order bits (e.g., 10.1.8.0/24 through 10.1.15.0/24 → 10.1.8.0/21).
  • Benefits: smaller routing tables, faster convergence, reduced CPU/memory use.
  • Trade-offs: less fault isolation—failures of a component subnet may be masked by a summary still being advertised; use policy or conditional advertisement to mitigate.

Common failure modes

• Miscalculating block sizes and accidentally overlapping VLSM ranges.
• Advertising a summary without ensuring component reachability, causing black holes.
• Discontiguous networks with protocols that assume contiguity unless configured carefully.

Forwarding Basics: ARP, Gateways, and Local vs Remote Delivery

Hosts decide whether a destination is local or remote using their own IP and subnet mask.

• Local delivery

  • If destIP AND mask equals srcIP-network, the host ARPs for the destination MAC and sends an L2 frame directly.
  • Failure modes: ARP cache corruption, duplicate IPs, L2 loops, or stale switch CAM entries can cause intermittent loss.

• Remote delivery

  • If not local, the host sends to its default gateway (router) by ARPing for the gateway’s MAC.
  • The router decrements TTL, rewrites L2 headers, and forwards per the routing table.
  • Failure modes: wrong default gateway, gateway unreachable, missing route on router, host using incorrect mask leading to misclassification of local vs remote.

• Default gateway configuration

  • On end hosts: a single IP next hop in the same subnet.
  • On L2-only switches: ip default-gateway x.x.x.x (management plane).
  • On L3 interfaces (SVIs or routed ports): assign an IP in the VLAN/subnet; downstream hosts use that IP as their gateway.

Useful verifications

• show arp or arp -a to confirm L3-to-L2 resolution.
• ping default-gateway; packet capture to see ARP requests/replies.

Routing and Route Selection, Verification, and Design Trade-offs

Routers forward based on the routing table and choose the best entry by longest prefix match (LPM). If multiple routes have the same prefix length, administrative distance (AD) and, within a single protocol, the protocol metric determine selection.

• Longest prefix match

  • The most specific route (largest /N) that matches the destination wins.
  • Example: For 10.1.2.3, routes 0.0.0.0/0, 10.0.0.0/8, and 10.1.0.0/16 exist; /16 is selected.

• Administrative distance (lower is preferred)

  • Typical values: connected 0, static 1, eBGP 20, EIGRP internal 90, OSPF 110, RIP 120.
  • Floating static routes use a higher AD than the dynamic protocol so they only install if dynamic routes are lost.

• Static routes

  • Next-hop form: ip route 172.16.3.0 255.255.255.0 192.168.2.4
  • Exit-interface form (on point-to-point): ip route 172.16.3.0 255.255.255.0 Serial0/0/0
  • Default route: ip route 0.0.0.0 0.0.0.0 203.0.113.1
  • Floating static: ip route 10.10.0.0 255.255.0.0 192.0.2.2 200
  • Failure modes: pointing to an unreachable next hop (no connected/recursive route), using an exit interface on multiaccess media causing ARP for every destination, static black holes when summaries lack more-specifics.

• Recursive lookup and CEF adjacency

  • If a route points to a next-hop IP, the router must find a connected route to reach that next hop; otherwise, the route is unresolved and not usable.
  • ARP resolves the next-hop MAC on multiaccess links; failure to resolve leads to drops until ARP succeeds.

• First Hop Redundancy Protocols (FHRPs)

  • Purpose: provide a virtual default gateway so hosts remain reachable during an upstream device failure.
  • HSRP (Cisco)
    • Virtual IP shared by group; one active and one standby router.
    • Multicast 224.0.0.2 for hellos; default priority 100; preempt disabled by default.
    • Example:
      • interface Vlan10
      • ip address 10.10.10.2 255.255.255.0
      • standby 10 ip 10.10.10.1
      • standby 10 priority 110
      • standby 10 preempt
  • VRRP (standards-based)
    • Virtual router with one master; uses 224.0.0.18; preempt is effectively on by default.
  • Common pitfalls: mismatched group numbers or authentication, missing preempt where desired, split-brain due to VLAN mismatches.

• Verification and troubleshooting workflow

  • show ip interface brief to confirm interface state and addressing.
  • show ip route to check entries, AD, recursive resolution.
  • show ip cef and show adjacency detail to verify next-hop resolution.
  • ping and traceroute to test reachability and path.
  • show arp to confirm neighbor resolution.
  • On FHRP: show standby brief or show vrrp to verify role and timers.
  • Packet captures to confirm ARP and ICMP behavior; use caution with debugs in production.

• Design trade-offs

  • Summarization reduces table size and convergence time but can hide failures; consider leak of critical more-specifics or use dynamic tracking to withdraw summaries when all components fail.
  • VLSM improves address efficiency but increases planning complexity; errors lead to overlaps and ambiguous routing.
  • Default routes simplify edge deployments but risk unintended traffic attraction; constrain with route filters and ensure symmetry.
  • FHRP adds gateway resilience but can mask upstream routing failures; combine with object tracking to fail over based on reachability.

Practical Problem Scenario

Contoso Manufacturing is collapsing a legacy flat 10.0.0.0/16 network into routed VLANs across two distribution switches, with an ISP uplink on each. Goals are to conserve IPv4 space, provide resilient default gateways, and minimize routing churn upstream.

1. Carve subnets using VLSM based on actual needs.

• Rationale: Allocate /24 for production VLANs with up to 200 hosts, /27 for printers/IoT, and /30 or /31 for point-to-point links between distribution and core. This prevents waste and simplifies ACLs. Sorting by size first avoids overlaps.

2. Implement summaries towards the core and ISP edges.

• Rationale: Summarize 10.0.16.0/20 for production floors and 10.0.32.0/23 for server VLANs. Advertising a few aggregate routes reduces routing table size and convergence time across the WAN. Ensure aggregates align on binary boundaries and are strictly composed of reachable specifics.

3. Build FHRP for user VLAN default gateways on the distribution pair.

• Rationale: Configure HSRP with a consistent virtual IP per VLAN, primary/secondary priorities, and preempt. Example on Dist-A for VLAN20:
  • interface Vlan20
  • ip address 10.0.20.2 255.255.255.0
  • standby 20 ip 10.0.20.1
  • standby 20 priority 110
  • standby 20 preempt This provides a stable gateway MAC/IP to hosts and fast failover if a distribution switch fails.

4. Configure default routing to ISPs with floating backup.

• Rationale: On Dist-A, prefer ISP-A with a primary default; install a floating default via ISP-B with higher AD for failover:
  • ip route 0.0.0.0 0.0.0.0 198.51.100.1 1
  • ip route 0.0.0.0 0.0.0.0 203.0.113.1 200 AD 200 ensures the backup route installs only when the primary is removed. Track ISP next-hop reachability to withdraw the default if the circuit fails beyond Layer 2.

5. Verify ARP and recursive resolution on uplinks.

• Rationale: Use show ip route to confirm the 0/0 next hop is resolved via a connected interface and show arp to ensure the ISP next-hop MAC is learned. This prevents silent black holes due to unresolved next hops.

6. Enforce failure domain boundaries with selective leaking.

• Rationale: Summarize user VLANs to the core, but leak more-specific /32s for critical services (e.g., VIPs) so upstream path selection remains precise during partial failures. This balances scalability with fault isolation.

7. Validate data-plane paths and convergence.

• Rationale: From a user VLAN SVI, ping the gateway, ISP next hop, and public targets. Use traceroute to confirm exit via the intended ISP. During failover tests, observe HSRP state changes (show standby brief) and routing table updates (show ip route) to ensure LPM chooses the correct next hop and the floating default activates only when appropriate.

By combining address efficiency (VLSM), reduced churn (summarization), resilient gateways (HSRP), and deterministic exit selection (primary and floating default routes), Contoso achieves scalable growth while containing failure domains and maintaining predictable forwarding behavior.

← VLANs · All domains · IPv6 Addressing and IPv6 Routing →

Practice these questions → · Timed practice on ExamRoll.io →