CCNP Routing & Switching Is Retired: The Current CCNP Enterprise Path

CCNP Routing & Switching is retired. Cisco replaced the old ROUTE, SWITCH, and TSHOOT-era structure in 2020 with CCNP Enterprise, a professional certification built around one core exam plus a concentration exam. The durable routing and switching concepts still matter, but the certification map has changed.

Today, the enterprise path centers on CCNP Enterprise. The core is 350-401 ENCOR, which covers enterprise architecture, virtualization, infrastructure, assurance, security, and automation. Candidates then choose a concentration that matches the work they want to deepen.

For professionals whose interest is closest to the old advanced routing and troubleshooting identity, 300-410 ENARSI is usually the most natural concentration. The important move is to preserve useful R&S knowledge while rebuilding the study plan around current enterprise networking.

What happened to CCNP Routing & Switching

The old CCNP Routing & Switching track treated routing, switching, and troubleshooting as separate certification exams. That structure reflected the way enterprise networking was taught at the time, but it became too narrow as virtualization, SD-WAN, controller-based networking, automation, wireless, and security became ordinary enterprise concerns.

Cisco retired that track and consolidated professional-level enterprise breadth into ENCOR, then allowed candidates to add role-specific depth through concentrations. That means old course names and exam codes should be treated as historical, not as current certification targets.

If you still have old ROUTE, SWITCH, or TSHOOT books, keep the sections that teach durable protocol behavior. Replace the exam-planning sections, command assumptions, platform details, and certification pathway with current material.

A useful migration map is concept-first. Old SWITCH material maps into campus infrastructure, Layer 2 design, redundancy, and enterprise access. Old ROUTE material maps into advanced routing, policy, and service reachability. Old TSHOOT habits map into assurance and diagnosis. The certification labels disappeared, but much of the engineering reasoning remains valuable.

What must be added is equally important: virtualization, software-defined architecture, APIs, automation, telemetry, controller-based operations, and modern security expectations now sit inside the professional baseline.

ENCOR provides the modern enterprise core

350-401 ENCOR is the core exam for CCNP Enterprise. Its purpose is broader than the old switching-plus-routing identity. A professional enterprise engineer needs to understand architecture, infrastructure, virtualization, network assurance, security, and automation as parts of one operating environment.

That breadth matters because modern incidents do not stay inside a chapter boundary. A routing symptom may be caused by an overlay, a policy, a controller, a security control, or a bad automation change. A wireless problem may involve identity, switching, IP services, and assurance data at the same time.

ENCOR also serves as a shared core for multiple Cisco professional and expert pathways, so studying it should feel like building enterprise breadth rather than chasing a narrow exam trick. The concentration is where the candidate chooses deeper specialization.

That structure rewards engineers who can cross boundaries. You may troubleshoot BGP one hour and interpret telemetry or an automated change the next. The certification map now reflects that reality more clearly than the old R&S label did.

Study ENCOR by connecting domains. Ask how the architecture changes packet flow, how telemetry reveals state, how security controls affect reachability, and how automation changes operational risk.

ENARSI is the closest current path for advanced routing depth

The 300-410 ENARSI concentration focuses on advanced routing and services. It is the natural choice for candidates who enjoyed the routing and troubleshooting depth of the old R&S track.

Preparation should go beyond memorizing protocol commands. Build environments where routing state can fail in several plausible ways. Work with OSPF, EIGRP, BGP, redistribution, route policy, VPN-related services, and infrastructure security in a way that makes you diagnose the control plane from evidence.

The OSPF fundamentals remain essential, but professional-level work requires deeper reasoning about adjacency, topology information, route selection, summarization, filtering, and failure behavior.

Switching knowledge is still foundational even though the track name changed

Retiring “Routing & Switching” did not make Layer 2 knowledge obsolete. VLANs, trunks, Spanning Tree, EtherChannel, first-hop redundancy, and campus design still influence enterprise reliability and troubleshooting.

The difference is that these technologies now live inside a wider architecture. A switching decision may affect wireless access, segmentation, automation, controller behavior, and network assurance. That is why switching fundamentals should be learned as part of system behavior rather than as a collection of configuration commands.

When revising legacy material, keep packet-flow logic and protocol principles. Recheck platform-specific defaults and current blueprint depth before assuming an old lab still maps directly to the exam.

Automation and assurance are now part of the professional baseline

One of the clearest differences between the old track and CCNP Enterprise is the expectation that engineers understand automation and operational visibility. APIs, structured data, controllers, telemetry, and programmable workflows now sit alongside CLI-based configuration.

You do not need to become a full-time developer to pass ENCOR, but you should understand why automation changes how networks are operated. A change can be repeated consistently across many devices, but a bad template or incorrect source data can also distribute an error quickly.

Network assurance matters for the same reason. Professional troubleshooting increasingly combines device state, logs, telemetry, path information, and controller insight rather than relying on one command from one box.

CCNP Enterprise gives you concentration choices

ENARSI is only one concentration. Cisco’s enterprise portfolio also includes design, SD-WAN, automation, and cloud-connectivity options, while wireless moved into dedicated certification paths in the 2026 portfolio changes.

This lets candidates build professional depth around the work they actually perform. An engineer focused on complex routing may choose ENARSI. Someone designing enterprise networks may prefer ENSLD. An automation-heavy role may need a different concentration or a dedicated Automation certification path.

The current CCNA-to-CCNP Enterprise progression is therefore better understood as broad associate foundations followed by professional core knowledge and deliberate specialization.

Use old R&S material as a concept library, not an exam plan

Legacy CCNP books can still be excellent explanations of spanning tree, OSPF, EIGRP, BGP, redistribution, route filtering, first-hop redundancy, and troubleshooting methodology. Those concepts did not expire when the certification did.

However, old material can also preserve obsolete exam codes, outdated platform behavior, commands that are no longer emphasized, and a certification structure that no longer exists. Mark legacy notes clearly so they do not silently become current facts.

A good modernization workflow is to map every useful legacy chapter to the current ENCOR or concentration blueprint. Keep the technical explanation where it remains accurate, add current automation and assurance context, and discard exam-specific advice that belongs to the retired track.

Build professional-level troubleshooting skill

CCNP preparation should force you to diagnose ambiguous faults. Create topologies with several routing protocols, redundant paths, route policies, VPNs, access controls, and monitoring. Introduce one or two faults and collect evidence before changing configuration.

Explain each fix in terms of state: what was expected, what was observed, which control-plane or forwarding decision was wrong, and why the change corrected it. This is more valuable than memorizing a list of “show” commands.

Professional-level confidence comes from repeated troubleshooting across different symptoms. The certification should validate that reasoning, not replace it.

Keep a lab journal that records the failure, evidence collected, false hypotheses, root cause, and final verification. Over time, this becomes more useful than a command cheat sheet because it shows how you think when the obvious explanation is wrong.

Mix technologies in the same scenario. Add route filtering to a redundant campus, inject a redistribution error, break an adjacency with an authentication mismatch, or place an ACL where it changes a control-plane dependency. Professional exams and production networks both reward the ability to reason across layers.

The current destination is CCNP Enterprise

If your old goal was CCNP Routing & Switching, do not try to recreate the retired certification. Move the durable skills into the current architecture. Use ENCOR for professional enterprise breadth and choose the concentration that matches your role.

For advanced routing, ENARSI is the closest continuation. For other enterprise specialties, use the concentration or dedicated certification that reflects the work you want to own.

The name change is ultimately less important than the change in professional scope. Enterprise networking now expects routing and switching knowledge to coexist with virtualization, security, assurance, controllers, and automation. That is the skill model a current CCNP candidate should prepare for.

Plan the transition in three layers. First, preserve associate-level fundamentals: addressing, packet forwarding, VLANs, routing tables, IP services, and security basics. Second, build ENCOR breadth across architecture, virtualization, assurance, and automation. Third, choose a concentration and create labs deep enough to match the problems that specialization owns.

This sequence prevents a common mistake: jumping directly into advanced routing syntax while foundational packet-path reasoning remains weak. Professional-level protocols become much easier to troubleshoot when the underlying addressing, route selection, and Layer 2 behavior are automatic.

It also creates a better career narrative. Instead of saying you “upgraded from the old CCNP,” you can explain that your skills moved from traditional routing and switching into the broader enterprise stack and then into a chosen specialty.

When reviewing job descriptions, look beyond certification names. Employers may ask for BGP, OSPF, SD-WAN, Catalyst Center, automation, wireless, cloud connectivity, or network assurance. Use those recurring responsibilities to decide which concentration and labs will create the most useful depth.

Build ENCOR and concentration study as one architecture. For example, an ENARSI lab can still include segmentation, security controls, telemetry, and automated configuration validation. This prevents the concentration from becoming an isolated protocol course and reinforces the professional-level breadth Cisco expects.

Review current exam versions before buying old R&S bundles marketed as “equivalent.” A resource may teach excellent routing while omitting half of the modern core. Use it for the part it teaches well, not as proof that your CCNP Enterprise coverage is complete.

If you already hold strong legacy CCNP knowledge, spend less time relearning basic protocol syntax and more time on what changed around it: software-defined architecture, assurance, APIs, programmable workflows, and the current enterprise design context. That is where the modernization work usually lives.

Professional-level study should also include change safety. A technically correct routing change can still be operationally poor if it is introduced without validation, rollback, monitoring, or awareness of dependencies. Modern enterprise engineering is as much about controlled change as protocol knowledge.

That operational mindset is one of the best ways to distinguish current CCNP preparation from nostalgic study of the retired R&S track.