When most engineers hear “virtualization,” we think of the enterprise. Racks and rows of servers running a hypervisor application so that the business can achieve much larger scale, density, and faster speed of “turnup,” ensuring applications and services can run “at the speed of developers.” In fact, we’d be hard-pressed to think of somewhere that isn’t virtualizing their servers in some way.

This virtualization does have some additional overhead, though. It adds complexity in the administration, resource and capacity planning, network, and data backup, none of which was initially trivial to the administrators and engineers who had to support it. However, the benefit was the cost savings and density and utilization, as well as the speed at which a new database or web server could be instantiated on the network. The shift was worth it, and it’s the reason why it’s the predominant way of running a server today.

It’s no surprise, then, that this same way of thinking has moved from the enterprise and servers to networks, routers, and firewalls. Nowhere is this more apparent than in service provider networks, not just in orchestrating virtualized network services, but also in how we can virtualize the network itself, providing domain separation through things like MPLS and SR, and creating layer-2 and layer-3 overlays with those technologies.

Building SP clouds and ensuring the right connectivity between enterprise clouds (or between enterprise and cloud service providers) is a major part of the SP business today. Thankfully, we’ve got a great way to level up your learning (for free) while earning Continuing Education (CE) credits to keep your existing certs active.

Rev Up to Recert: SP Cloud

Rev Up to Recert: SP Cloud focuses on building, securing, and optimizing the infrastructure behind modern service provider networks, both in the network and on the network.

Let’s get into the details the way any network engineer would—starting with foundational concepts and moving up to advanced operational pieces. Read on to learn more about the Learning Path, and enjoy free access from Monday, October 26, through Thursday, December 10, 2026.

Designing and Implementing Cisco Service Provider Cloud Network Infrastructure | SPCNI

40 CE credits | 35h 20m | 13 courses | 14 labs |  8 assessments

This is a massive opportunity. It’s the only Learning Path in this Rev Up, but don’t let “one path” fool you into thinking it’s light. SPCNI covers the entirety of SP cloud infrastructure, from building and orchestrating VNF or application clouds, to providing robust interconnection options to cloud providers or datacenters, all while ensuring proper priority of business-critical traffic. On top of that, you’ll also learn how to build the networks with high-availability, redundancy, and security as top-of-mind, rather than afterthoughts to be fixed later (usually when a ticket comes in). It’s also your on ramp to the 300-540 SPCNI v1.0 exam, which satisfies the concentration exam requirement for CCNP Service Provider. What a better way to upskill while also preparing you for the SP skills needed today? Plus, the 40 CE credits is enough to recertify an associate or specialist certification.

The SPCNI Learning Path journey

It starts where it should: with the fundamentals. Before you can design anything, you need a solid grip on cloud computing fundamentals and what virtualization actually looks like inside a service provider network. The first course helps lay the groundwork—how virtualized infrastructure differs from the physical-first world a lot of us learned and studied and practiced on, and why that distinction matters when you’re the one designing it (hint: its a whole standardized architecture).

From there, it moves into virtualized network function (VNF) infrastructure. This is the heart of SP virtualization—understanding how VNFs are built, deployed, and supported at the infrastructure level. This goes beyond just spinning up a VM in your hypervisor of choice, because at the SP level, these VNFs need to come on to the network, be chained to services, provide health to a central management system, and turn off when needed, all at scale. Its not a trivial set of operations and if you’ve ever wondered how it works, this is where you’ll get your answers.

The next section: programmability and orchestration. Because managing virtualization cloud infrastructure by hand doesn’t scale—not at the level service providers operate at. This section gets into how programmability and orchestration tools let you manage infrastructure at scale instead of configuring everything individually. This includes both the application and container orchestration mechanisms to build your own application clouds, as well as managing the VNFs at scale using tools like NETCONF, RESTCONF, gRPC, and even NSO. True to form, labs are built in here so you’re not just reading about automation and orchestration—you’re actually doing it (remember, never skip lab day).

Then it’s on to interconnections, both to other clouds as well as other customer datacenters. As an SP engineer, you may be responsible for working within carrier-neutral facilities or working directly with cloud providers to interconnect your network to their cloud. Additionally, for those customers who run their own private clouds, you need to ensure that their internal services are operating expected. This section is very lab heavy, and includes concepts from EVPN-VXLAN, Segment Routing (SR), and even some ACI concepts as well. There’s something for everyone, for every SP network.

The back half of this learning path shifts to high-availability, redundancy, operations, management, and security. When I started in network engineering, I was only concerned about developing the solution and making it a reality, never about how to turn it over. However, as I grew to support other networks and events, I realized that while engineering makes something happen, operations makes it happen for everyone. This section covers everything from how to design networks for failover using things like TI-LFA and SR-TE, but also securing networks at both the data- and control-plane level (concepts like uRPF, RTBH, and LDP and IGP/BGP security make appearances).

Finally, the Learning Path wraps up with monitoring, including tools like model-driven telemetry, gRPC, and even tools like ThousandEyes and Crosswork Network Controller (CNC), which ensures that even after the network is deployed, and the failover and redundancy is performing as expected, that the customer experience is exactly as what is promised. Its these details that separate a “good enough” customer experience to a great one, which really translates into customer satisfaction, retention, and growth.

With 14 labs woven throughout, this isn’t a path where you passively watch slides go by. You’re building, configuring, and troubleshooting along the way. Frankly, doing hands-on work is the only way any of is going to stick anyway (have I mentioned to not skip lab day??!).

Bringing it all together

Like I said, there’s no escaping where SP networks are headed. Virtualization and cloud infrastructure aren’t a specialty track anymore—they’re becoming the baseline expectation for anyone doing serious infrastructure work in the service provider space.

Through this Learning Path, you’ll walk away not just understanding virtualization conceptually, but genuinely equipped to design, implement, secure, and optimize it. And let’s say it again in case you were skimming, you’ll be exam-ready for the 300-540 SPCNI v1.0, checking off the concentration requirement for CCNP Service Provider along the way.

That’s 35+ hours, 14 labs, and 40 CE credits standing between you and being considerably more dangerous (in the good way) with SP cloud infrastructure.

Learning, training, and certifications are rarely a straight line, and this path is a solid stop along the way, whether you’re shoring up skills for your current role or building toward the next one.

Go try SPCNI now.

As always, happy learning—and if you have questions, comments, want to talk SP cloud infrastructure or just ask how I get my beard to look so good, drop a comment below or find me on X (@qsnyder).