Welcome to service provider networking: what you will learn and the big picture
What you will learn in this module. This is the free "Start here" module for the Cisco CCNP Service Provider core exam, SPCOR 350-501. You will learn how an internet service provider (ISP) network is built: the access, aggregation and core layers, the IGP that holds the core together, BGP that carries customer and internet routes, MPLS that switches labels instead of looking up IP addresses, and the VPN services that providers sell on top. You will also learn how the exam domains fit together and how to practise them in the labs, so that your first IS-IS adjacency in the next module is not a surprise.
Prerequisites. You should have finished CCNA and, ideally, ENARSI: OSPF, EIGRP or BGP basics, VLANs, static routes and reading show ip route. Nothing here needs service provider experience.
Analogy: a country's road network
Think of the roads of a large country. Your house sits on a small lane. Lanes join a district road, district roads feed a city ring road, and cities are linked by national highways. Nobody builds a house on a highway, and nobody runs a lorry from Chennai to Delhi over village lanes. A service provider network has the same layers. Access links reach the customer's door. Aggregation collects many access links. The core is the national highway: few devices, huge speed, no customers plugged in. The job of the core is to move traffic between the edges as fast and as reliably as possible, and to stay up even when a link is cut by a road digger.
The layers of a provider network, from the customer to the core.
Why providers are different from enterprises
- Scale. A provider carries traffic for thousands of customers, so the core routing table must stay small and stable. Customer routes do not belong in the IGP.
- Many customers on one network. Two customers can both use 10.0.0.0/8. The provider must keep them apart on shared routers. That is what VPNs and MPLS are for.
- Money is tied to uptime. Service level agreements (SLAs) promise availability, so convergence time, protection and monitoring become exam topics.
- Operations at scale. Hundreds of routers are managed by automation, model-driven telemetry and templates, not by typing on each device.
The five building blocks you will meet
| Block | Question it answers | Where you study it |
|---|---|---|
| IGP (IS-IS, OSPF) | How does every router reach every other router loopback? | spcor-isis, spcor-isis-design |
| MPLS and LDP | How do we forward on labels so the core needs no customer routes? | spcor-mpls-ldp |
| BGP and route reflectors | How do customer and internet routes cross the core? | spcor-bgp |
| L3VPN and L2VPN | How do we sell private networks on shared hardware? | spcor-l3vpn, spcor-l2vpn |
| Operations | How do we protect, secure, automate and monitor it? | spcor-ha, spcor-sp-security, spcor-telemetry |
Worked example. A customer in Pune orders a 100 Mbps internet link and a private link between Pune and Hyderabad. The Pune access router (a CE or the provider's own access node) hands traffic to a PE router. For the internet service the PE sends it over BGP routes to the upstream. For the private link the PE puts the traffic in a VRF, adds two MPLS labels, and sends it across the core to the Hyderabad PE. The same physical routers deliver both services. By the end of this module you will be able to describe every step of that story in your own words.
Common mistake. Treating a provider network as "a very big enterprise network" and putting customer subnets into the IGP. Provider cores keep the IGP tiny (only loopbacks and infrastructure links) and carry customer routes in BGP.
Exam trap. SPCOR questions often describe a symptom in one layer but the cause is in another, for example "VPN route is present but traffic fails" where the cause is a missing label path in the core. Learn each layer and learn which layer to check next.
The core that stayed small
A regional ISP started by putting every customer /30 into OSPF. At 3,000 customers the routing table on the core routers was huge and every flap in a customer link caused an SPF run everywhere. The team moved customer routes into BGP and kept only loopbacks and core links in the IGP. SPF runs dropped sharply and the core became boring, which is exactly what a core should be.
Lesson: the IGP carries infrastructure only; BGP carries customers.
"How is a service provider network different from an enterprise network?"
Describe the layers (access, aggregation, core), then say that providers serve many customers on shared infrastructure, so they use MPLS and VPNs to separate them, keep the IGP small, carry customer routes in BGP, and design for scale and SLA-grade convergence. Mention PE, P and CE roles to show you know the vocabulary.
Key takeaways
- A provider network has access, aggregation and core layers, each built redundant.
- The core carries traffic fast; customers do not plug into it.
- IGP carries infrastructure; BGP carries customer and internet routes.
- MPLS labels and VPNs let many customers share one network safely.
- SPCOR tests architecture, routing, services, automation, assurance and security.