CCNA 200-301 IPv4 Subnetting Cheat Sheet & CLI Troubleshooting: Stop Memorizing, Start Solving

Over on r/ccna, there’s a thread that’s been blowing up. Someone posted “One thing about the CCNA that you should consider,” and the comments are brutal. The exam covers way too much — IPv4 subnetting, QoS DSCP values, 802.3 standards — and you never know how many subnet questions you’ll actually get.

I remember sitting for the CCNA 200-301. The worst part wasn’t the difficulty — it was the speed. You’re burning precious exam time drawing out binary on scratch paper while the clock keeps ticking. Meanwhile, some people are already past the subnet questions, using CLI commands to troubleshoot real problems.

This isn’t another theory lecture. Here’s a cheat sheet you can copy-paste and real router commands that actually work in production. Read this, and you’ll calculate any subnet in under 10 seconds. More importantly, you’ll never freeze up in front of a show ip route output again.

The Cheat Sheet: CIDR, Subnet Masks, Wildcards, Host Counts

I printed this table and stuck it to my monitor during lab practice. You can’t bring it into the exam, but memorize it and you’re golden.

How to use this table:
Given IP 192.168.1.55/27. Don’t calculate. Look up: /27 block size is 32. 55 falls between 32-63. Network address: 192.168.1.32. Broadcast: 192.168.1.63. Usable hosts: 33-62. Done in 10 seconds.

Troubleshooting Commands: Stop Using Just Ping

Last month, a junior engineer misconfigured a /29 subnet. He set the gateway to the broadcast address. The whole segment went dark. He spent 30 minutes pinging random IPs. I walked over, ran one command, and found the problem instantly.

1. show ip interface brief — Check Interface Status

Router# show ip interface brief
Interface          IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0 192.168.1.33    YES manual up                    up
GigabitEthernet0/1 192.168.1.65    YES manual up                    up

If Protocol is down, don’t touch the IP config. Check physical layer first. I’ve seen too many people waste time recalculating subnets when the cable was unplugged.

2. show ip route — Check the Routing Table

Router# show ip route
Codes: C - connected, S - static, O - OSPF, B - BGP
C    192.168.1.32/27 is directly connected, GigabitEthernet0/0
C    192.168.1.64/27 is directly connected, GigabitEthernet0/1

This command shows you exactly what subnet you configured. If it says /27 but you wanted /28, you’ve got a config error. This is the most overlooked troubleshooting step — everyone stares at the IP address and forgets to check the prefix length.

3. show ip protocols — Check Routing Protocol Config

Router# show ip protocols
Routing Protocol is "ospf 1"
  Router ID 1.1.1.1
  Number of areas in this router is 1. 1 normal 0 stub 0 nssa
  Maximum path: 4
  Routing for Networks:
    192.168.1.32/27
    192.168.1.64/27

OSPF neighbors not coming up? Check what networks you’re advertising. I once saw someone advertise 192.168.1.0/24 into OSPF while the interface was configured as /27. Neighbors never formed.

4. ping and traceroute — Basic Connectivity

Router# ping 192.168.1.34
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.34, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5)

Router# traceroute 10.0.0.1
Type escape sequence to abort.
Tracing the route to 10.0.0.1
  1 192.168.1.33 1 msec 0 msec 1 msec
  2 10.0.0.1 2 msec 2 msec 1 msec

Ping success doesn’t mean routing is correct. Traceroute tells you the actual path. We once had a core switch routing traffic through an extra hop — caught it instantly with traceroute.

5. show ip arp — Check the ARP Table

Router# show ip arp
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  192.168.1.33            -   aabb.cc00.0100  ARPA   GigabitEthernet0/0
Internet  192.168.1.34          12   aabb.cc00.0200  ARPA   GigabitEthernet0/0

ARP tells you if Layer 2 resolution works. Ping fails but ARP has the entry? Problem’s at Layer 3. No ARP entry? The host thinks the destination isn’t on the same subnet — bad mask config.

Real Case Study: The /27 That Broke Production

We were setting up a new office. Requirement: 30 devices. I assigned 192.168.1.32/27. The field engineer configured 255.255.255.0 (/24) instead. All devices could ping the gateway, but couldn’t reach the corporate network (10.0.0.0/8).

Troubleshooting steps:

1. show ip route — only showed the direct /24. No route to 10.0.0.0/8.
2. Checked OSPF — neighbors weren’t forming.
3. show ip ospf neighbor — stuck in INIT state.
4. Root cause: Interface was 192.168.1.33/24, neighbor was 192.168.1.34/27. Mismatched masks. OSPF refused to form adjacency.

Fix: Changed mask to 255.255.255.224 (/27). OSPF neighbors came up instantly.

FAQ

Q: Why is usable host count always minus 2?

A: Network address (all host bits 0) and broadcast address (all host bits 1) are reserved. For 192.168.1.32/27, 32 is network, 63 is broadcast. Usable: 33-62.

Q: What’s the relationship between wildcard mask and subnet mask?

A: Wildcard mask = 255.255.255.255 - subnet mask. For /27 (255.255.255.224), wildcard is 0.0.0.31. Used in ACLs and OSPF network statements.

Q: show ip route shows two identical networks with different prefix lengths. Which one wins?

A: Longest prefix match. Router always prefers the most specific mask. If 192.168.1.0/24 and 192.168.1.32/27 both exist, traffic to 192.168.1.33 takes the /27 route.

Q: Why does /30 only give 2 usable IPs?

A: Block size is 4. Subtract network and broadcast addresses. That’s why /30 is standard for point-to-point links — maximum efficiency.

Q: Does CCNA test VLSM?

A: Absolutely. Variable Length Subnet Masking is a core CCNA 200-301 topic. You need to carve different-sized subnets from one major network. For example, splitting 192.168.1.0/24 into one /27 (30 hosts), two /28s (14 hosts each), and one /30 (2 hosts).

Final Thoughts

Subnetting is pure muscle memory. Memorize the cheat sheet, lab it up in Packet Tracer or GNS3, and the exam becomes easy pickings.

Don’t brute-force memorize the troubleshooting commands either. Understand what each one tells you. I’ve seen people confuse show ip route output with show ip protocols — that’s what happens when you only read theory and never touch a real router.

That Reddit thread said it best: “You never know how many subnet questions you’ll get.” But if you’re prepared, it doesn’t matter how many they throw at you.

Next time someone tells you subnetting is hard, send them this article.

References & Community Insights

The following authoritative resources were referenced for architectural best practices and specifications:

• Cisco Validated Design (CVD) Guides
• IETF RFC Datatracker
• Cloudflare Learning Center