CCNA Show Commands Cheat Sheet: Choose the Command That Answers Your Question
A CCNA show commands cheat sheet should start with a troubleshooting question. You might need to know whether an interface has an address, whether a switch has a VLAN, or whether the router has a path to a destination. Each observation comes from a different part of the device state.
Cisco's CCNA certification guide includes verification commands. The small selection below organizes them by purpose. Exact syntax and available fields can vary by device and software, so use the reference for your lab platform.
Start with addressing and interface state
Use show ip interface brief for a compact view of IPv4 interface addresses and status. It is a starting point when a configured link does not appear to work.
Suppose a lab diagram assigns an interface 192.0.2.1, but the output shows a different address. That mismatch is concrete evidence. It is more useful than assuming the routing protocol must be broken. Conversely, an interface being up does not prove the whole remote path works.
Check recall with CCNA practice questions after reviewing the command purposes, keeping the reference closed on the first attempt.
Inspect the switching context
Use show vlan brief to inspect VLAN information and access-port membership on a switch. If a workstation belongs in VLAN 20, check its intended switch port rather than assuming the physical cable places it in the right logical network.
A port list does not answer every trunking question. Keep “which access VLAN?” separate from “which VLANs can cross this inter-switch link?” Your next command should follow the unresolved question, not simply be the next line on a memorized list.
Inspect the forwarding decision
Use show ip route to examine the IPv4 routing table. A routing-protocol configuration statement and an installed route are different kinds of evidence.
In an original lab scenario, a learner enables a protocol but cannot find the expected destination prefix. The useful follow-up is to investigate why that route is absent. Repeating that the protocol is enabled does not explain the missing forwarding information.
Compare active and saved configuration
The running configuration describes the active configuration, while the startup configuration describes what is saved for a subsequent boot. When a lab behaves differently after a restart, comparing those states can reveal whether the intended changes were saved.
Record the relevant lines and the time of inspection. A screenshot without the device name or the context of the problem can become difficult to interpret later.
Make a four-column personal reference
Keep a reference containing the question, command, field to inspect, and limitation of the evidence. Use CCNA quick reference to support that review.
For example, “Is the expected route installed?” belongs beside the routing-table command, a destination prefix, and the reminder that a route alone does not prove application availability. Practise choosing the command before seeing the answer. A short reference that helps you ask precise questions is more useful than a long command list you cannot connect to an observation.