Practical tools for system, network, security, and operations administrators.

NET-C0288 · Career & Certification

CCNP Enterprise Roadmap

Sketch a lab path toward CCNP Enterprise topics, and do not call this page the exam or a certification.

Updated 25 October 2026 · Career

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

Cisco publishes the exam blueprint. This page does not replace it, does not include exam questions, and does not promise a result. The work is a lab you administer: subnetting, a routing choice, a switching choice, and a change you can roll back.

Use documentation prefixes. Do not practice on a production network and do not practice on a network you do not administer. One topic a week is enough. A purchased dump of questions is not a plan this page will help you use.

This page names no browser tool. The pillar links the calculators. You still read the official blueprint yourself.

Write this week's topic, the lab device, and the rollback. Then stop.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. Read the official blueprint yourself.
  2. Pick one topic for this week.
  3. Name a lab you administer.
  4. Use documentation prefixes.
  5. Do not touch production.
  6. Stop.

Mistakes that outlive the command

CCNP Enterprise Roadmap goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for CCNP Enterprise Roadmap: The blueprint is the official list. This page is a lab sketch. The lab is yours. Production is untouched. And no result is promised.

Checks before you call it done

Confirm this before you call the change done: This week's topic is written. The lab device is written. Documentation prefixes are the examples. No production device was changed. And no certification was claimed. If one of those fails, stop.

This is not the CCNP exam and not a certification.
Practice on a lab you administer.
192.0.2.0/24 is documentation.

Before you leave the device

CCNP Enterprise Roadmap ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

This guide does not name a browser tool. The pillar it belongs to links the calculators for the neighbouring work.

More in this cluster

The pillar for this page, and the next published pages filed with it.