Nokia NRS I: Service Routing Foundations · Service routing

Router architecture and operation: roles, CLI, commit model, hardware and files

Router architecture and operation: roles, CLI, commit model, hardware and files. Reading chapters, hands-on simulator labs, interview questions, scenarios and a quiz.

32 min read9 chapters2 labs12 quiz6 scenarios12 interview Q&A

This first module is free: read the lesson and take the quiz. Labs need an account: sign up free to run up to 3 hands-on labs.

Log inStart free trial
This reading material cannot be printed. Read it on config.nwkings.com.
01

Service routers and where they sit

Service providers use powerful routers to carry customer traffic. This chapter explains what a service router does and where it sits in a provider network.

Analogy: a city bus network

Local stops collect passengers, big interchanges move them between lines and long routes carry them across the city. A provider network has the same layers.

Router roles

RoleJobTypical position
Provider edge (PE)Connects customers and runs servicesEdge of the provider network
Provider (P) or coreMoves traffic quickly between PEsInside the core
AggregationGathers many access linksBetween access and edge
  • A service router carries many customers on one shared network.
  • Services such as pseudowires, VPLS and VPNs are built on top of the same core.
  • Reliability and scale matter more than any single feature.
CustomerPECore

Edge and core.

Two offices of one company connect to different PEs. The core carries their traffic without knowing the customer's own routes.

Common mistake: treating the core like an enterprise LAN. Keep customer detail at the edge.

Customer routes in the core

Every P router carried customer routes and memory ran low. Moving that detail to the PE routers fixed it.

Lesson: keep core simple.

What is a PE router?

A provider edge router that connects customers and runs their services.

Key takeaways

  • PE at the edge.
  • P in the core.
  • Shared network.
  • Services on top.
  • Keep the core simple.

Upgrade to keep reading

The free plan lets you read chapter 1 of this module. Upgrade to open the remaining chapters.

  1. The CLI: classic and model-driven
  2. System basics: name, time and users
  3. Chassis, cards and ports
  4. Configuration files and boot
  5. Monitoring and logging
  6. Securing access to the router
  7. First-line troubleshooting
  8. Putting the architecture together

Join the community