Troubleshoot Like a CCIE | Insider's Field Manuals
The 200-301 v1.1 exam retires Feb 2, 2027. v2.0 pushes troubleshooting to ~30% of the exam — get ahead of it now.
From a 2× CCIE · Troubleshooting Series

Never stare at a
broken network again.

Know exactly where to look the moment something breaks — on the exam or on the job — and work the fault like a 2× CCIE instead of guessing under the clock. These three Field Manuals give you 111 real fault fixes across CCNA and both CCNP Enterprise exams, each laid out symptom → root cause → fix. Get the whole series, or start with the cert you're on now.

Get the series → $98 one-time · all three guides
~/cisco/the-path
# three troubleshooting manuals, one method
$ ls ./troubleshooting-series
CCNA_200-301_TS.pdf 44 fixes
CCNP_ENCOR_350-401_TS.pdf 41 fixes
CCNP_ENARSI_300-410_TS.pdf26 fixes
$ echo "111 fault fixes, 0 filler"
$ _
2× CCIE
Enterprise & Security — every line author-tested
Free
Full-topic sample before you ever pay
111
Real fault fixes across all three guides
Lifetime
Free updates to your edition
Let's be honest about where you are

You know the commands.
It's the 2 a.m. fault that gets you.

Config questions you can study for. But troubleshooting items drop you into a broken topology and expect you to isolate the fault under time pressure — and that's exactly where candidates freeze. The exam is moving toward more of it, not less.

The real gap
~30%

Troubleshooting is already a graded skill on ENARSI and a growing share of CCNA v2.0 — roughly 30%. You can't memorize your way through a fault you've never learned to isolate.

On the job
Live

The exam ends; the broken networks don't. The same isolation method that passes the troubleshooting items is the one you'll use on a real outage. Learn it once, use it for a career.

If you wait
Feb 2

The 200-301 v1.1 exam retires February 2, 2027. v2.0 rebuilds around troubleshooting — ~30% of the exam. Build the skill now, on either blueprint, before the target gets harder.

The v1.1 window closes in
Last day to test 200-301 v1.1 · February 2, 2027

The panic doesn't go away by memorizing more commands. It goes away when you have a repeatable way to find the fault — the same one a CCIE uses.

WHAT READERS ARE SAYING...
YouTube comment: The guides are fire. Even if you been in the game.
▲ Real comment from a working engineer — “even if you been in the game.”
Message from a verified customer: The CCNA guide is really jogging my memory recall and testing my knowledge deeply. Thank you for creating the cliff-notes version of the CCNA OCG books by Wendell.
▲ Verified customer — picked up the troubleshooting bundle too.
No mystery

See the method for yourself.

Most guides ask you to trust a sales page. These are real pages from the manuals — the seven-part fault structure, the representative CLI, the common-trap callouts. Judge the depth yourself.

Seven-part fault structure page from the CCNA Troubleshooting Field Manual
The fault structure. Symptom → layer → first look → root cause → trap → fix → escalate — every time.
Representative CLI first-look page from the CCNA Troubleshooting Field Manual
Representative CLI + first look. The one or two commands that confirm or kill the theory fast.
Common-trap callout page from the CCNA Troubleshooting Field Manual
Common-trap callouts. The thing that fools people and wastes the most time on a fault.

▲ Actual pages from the CCNA Troubleshooting manual. All three guides are built to the same standard.

Why this works when textbooks don't

Built the way a CCIE actually troubleshoots.

Every fault in every guide is laid out the same way — so under pressure you already know how to read it and where to look next.

// Start from what you actually see

Symptom first, not topic first

Real faults don't announce their chapter. Each entry starts from the symptom a ticket would use — “subnet dark, adjacency full” — then names the layer so you know which way to bisect. You learn to move from what you see to where it lives, which is the whole game.

// The one or two commands that matter

A first look that confirms or kills it

You don't need twenty commands — you need the one or two that prove or disprove the theory fast. Each fault names them, shows representative output, and reads the result the way an experienced engineer would. Syntax varies by IOS version; the method doesn't.

! adjacency won't come up — one look tells you why
R1# show ip ospf neighbor
   10.0.0.2  EXSTART   ! stuck — not FULL
R1# show interface g0/0 | include MTU
   MTU 1500  ! neighbor 9000 -> mismatch
// The same rhythm every time

Seven parts, in the same order

Every fault follows one structure: symptom, layer, first look, root cause, common trap, fix, escalate. Once your brain knows the rhythm, a new fault isn't a blank page — it's the same seven questions you already know how to answer. That's what holds up when the pressure's on.

// The trap that wastes the most time

The wrong turn, called out in advance

Most faults have a predictable trap — the thing that looks like the cause but isn't: MTU mismatch two hops upstream, an AD-shadowed route, OSPF stuck in ExStart. Every entry flags its common trap explicitly, so you don't burn twenty minutes proving the obvious-but-wrong theory. The fault points you the wrong way; the guide points you back.

The complete path

One method. Three altitudes.

The three guides share one reference system: the same fault appears at CCNA, ENCOR, and ENARSI depth — layer-first, then domain-first, then symptom-first. Follow a problem up the ladder and watch the method deepen. The series is the whole path in one purchase.

You never buy blind.

Read a full fault walkthrough free first — same structure, same depth as the rest of the guide. What you see in the sample is exactly what you get.

Read a free CCNA sample →

A quick note from the author: I'm Don. I hold two CCIEs, I've sat these exams, and I've coached engineers through them. I built these manuals because I was tired of watching sharp engineers freeze on a fault — not for lack of knowledge, but because nobody ever taught them a repeatable way to isolate it. This is that method, one fault at a time.

— Donald C. Heslop Jr. · 2× CCIE Enterprise & Security
★ THE COMPLETE SERIES

The complete troubleshooting series

  • CCNA 200-301 Troubleshooting — 44 fault fixes, layer-first
  • CCNP ENCOR 350-401 Troubleshooting — 41 fault fixes, domain-first
  • CCNP ENARSI 300-410 Troubleshooting — 26 fault fixes, symptom-first
  • One shared reference system — the same fault at three depths
  • Seven-part fault structure + representative CLI throughout
  • Lifetime access — yours to keep
  • Free updates to your editions, for the blueprint versions you bought
1 exam retake $300bootcamp $1,500+
$98
Complete Troubleshooting Series
Instant Download DRM Protected
Get the bundle →
Instant PDF download · representative CLI · lifetime access
Didn't match the free sample? Email me within 14 days and I'll make it right. You read it before you buy it — there's nothing to lose.
— or start with just the guide you need —
CCNA 200-301 Troubleshooting Field Manual cover
Tier 1 · Layer-first

CCNA

200-301 Troubleshooting

Faults organized layer by layer, Physical to Services. Builds the bisection instinct the exam rewards.

44fault fixes
Layer First
$27 one-time
Instant Download DRM Protected
Get CCNA → or read a free sample
CCNP ENCOR 350-401 Troubleshooting Field Manual cover
Tier 2 · Domain-first

CCNP ENCOR

350-401 Troubleshooting

Enterprise-core faults across all six domains — routing, fabric, SD-WAN, security, automation.

41fault fixes
Domain First
$37 one-time
Instant Download DRM Protected
Get ENCOR → or read a free sample
CCNP ENARSI 300-410 Troubleshooting Field Manual cover
Tier 3 · Symptom-first

CCNP ENARSI

300-410 Troubleshooting

Advanced-routing faults organized by symptom — the way real incidents arrive. The capstone.

26fault fixes
Symptom First
$34 one-time
Instant Download DRM Protected
Get ENARSI → or read a free sample
Honest fit check

Make sure this is actually for you.

✓ This is for you if…
  • You can configure a feature but freeze when you have to find why it broke
  • You want a repeatable method for isolating faults, not a pile of commands
  • You're preparing for a troubleshooting-heavy exam like ENARSI — or getting ahead of CCNA v2.0 before it lands in Feb 2027
✕ It's not for you if…
  • You want video lectures or step-by-step hand-holding
  • You're after brain-dumps or leaked questions (not here — and they'll get you banned)
  • You only want config recipes and never expect to troubleshoot a live network
Before you buy

The honest fine print.

$Can I print the guide or read it on more than one device?+

The Field Manuals are DRM-protected, watermarked PDFs. Your purchase unlocks the guide on one device, and printing is disabled — that's how I keep the material from being copied and passed around.

Studying across two machines? Add an additional-device license for $9.97 one-time and the same guide opens on a second device too.

$Are these aligned to the latest Cisco blueprints?+

Yes — every guide is aligned to the blueprint Cisco publishes for that exam: CCNA 200-301 v1.1, ENCOR 350-401 v1.2, ENARSI 300-410 v1.1. Each guide carries an edition line stating its blueprint version so you know exactly what you're getting.

One honest note: the CLI in these guides is representative. Command syntax and output vary across IOS, IOS-XE, and NX-OS versions — so the guides teach the diagnostic method with representative output. The approach carries across versions; confirm exact syntax against your own equipment.

If I correct or improve a guide, existing customers of that edition get the update free. When Cisco releases a new exam version, that's a new, separate guide — a new purchase, not a free upgrade.

$Should I get the series or a single guide?+

The three guides share one reference system — the same fault at CCNA, ENCOR, and ENARSI depth — so they're built to be used together across the whole CCNA → CCNP path. If you're only studying one cert right now, start with that guide; if you're on the full path, the series gives you all three in one purchase.

$Why is it this cheap?+

Because I'd rather every engineer afford it before payday than price it like a $2,000 bootcamp. It's dense, method-driven reference, priced to be a no-brainer — not because it's thin. Read the free sample and judge the depth for yourself.

$How do I get the guide after I buy?+

You get the guide instantly — your download is ready the moment checkout completes. Your DRM license follows shortly after by email: each copy is watermarked and keyed to you (that's what stops it being copied and resold), so the license is what activates your personal copy. You'll also receive a separate email that walks you through how to access and open your guide.

$What do I need to open the guide? (Viewer requirements)+

The guides open in the free Locklizard Safeguard Viewer. You install it once, activate your license, and from then on the guide opens with a double-click. Minimum versions:

  • Windows — Windows 10 or later. Viewer v3.0.2. You need Administrator rights to install it and to activate the license.
  • macOS — macOS 11.5 (Big Sur) or later, 64-bit Intel or Apple Silicon. Viewer v2.5.95. Admin rights required, and you'll need to grant the Viewer Full Disk Access under Privacy & Security.
  • iPhone / iPad — iOS or iPadOS 15.6 or later. Safeguard Viewer 1.0.31 from the App Store. It will not run on a jailbroken device.
  • Android — Android 6.0 (Marshmallow) or later. Safeguard Viewer 2.0.7 from Google Play. It will not run on custom ROMs or in an emulator.

Two things cause most of the "my license won't activate" emails I get. First: activate on the machine itself — not over VPN, RDP, Citrix, or a terminal-server session, which Locklizard blocks by design. Second: the Viewer needs outbound access on ports 80 and 443 to reach the licensing server, so a strict corporate firewall or endpoint agent can stall it. Activating from home usually clears both.

There is no Linux build of the installed Viewer. If a Linux box or a Chromebook is your only machine, email me before you buy and I'll tell you straight whether I can get you running.

Requirements checked against Locklizard's published downloads page and the current App Store / Google Play listings — August 2026.

Last thing

Learn to find the fault before the exam does.

Picture the broken topology on exam morning — and you already know the seven questions to ask. Three guides, 111 fault fixes, one method across the whole CCNA → CCNP Enterprise path.

$98 one-time · all three guides · lifetime access