What single technology ensures that data sent from a video streaming service in California reaches you in London without getting lost or stuck, even if a cable is cut under the Atlantic Ocean? The answer lies in routing protocols, specifically OSPF and IS-IS, which act as the internet's internal GPS for service providers. If you are studying for the 350-501 exam, mastering these two protocols is non-negotiable because they form the foundation of every large-scale service provider network, and the exam will test your ability to implement and verify them under realistic scenarios.
Jump to a section
A simple way to picture OSPF and IS-IS in Service Provider Environments
How does a city's bus network keep running when a major road suddenly closes for construction? In a city, buses follow set routes to connect neighbourhoods. If the city only had one central planner who drew a map, and that planner's office burned down, the whole system would stop. That's why most cities use a smarter approach: each bus driver shares local road conditions with nearby drivers, and together they figure out the best detours without waiting for a central order. In a service provider's network, routers do the same thing. Instead of relying on one main router to know every path (which would fail if that router went down), protocols like OSPF (Open Shortest Path First) and IS-IS (Intermediate System to Intermediate System) let every router talk to its neighbours. They shout out, 'Hey, I can reach this street (network) using this path.' All routers listen and build their own mental map. When a cable breaks or a new link is added, they automatically recalculate the fastest route, just like a bus driver hearing about a closure from a colleague and rerouting through side streets. This self-organising, decentralised gossip system is what makes the internet's backbone reliable even when parts fail.
In the bus analogy, OSPF is like the driver who only communicates with drivers on directly connected streets, while IS-IS is like the driver who also talks to drivers two streets away, using a slightly different radio channel. Both achieve the same goal: a resilient, automatically updating route map without a single point of failure.
Let's start with a big picture. The internet is a network of networks. Your home internet, a bank's private system, and a streaming service's servers are all separate 'networks'. What ties them all together are connections made by companies called Service Providers (SPs) – think of names like Verizon, AT&T, or BT. These SPs run enormous backbones, a massive web of fibre optic cables and routers that stretch across continents.
Inside one of these SP backbones, the routers need a way to talk to each other to figure out the best path for your data. This internal communication is handled by an Interior Gateway Protocol (IGP). Think of an IGP as the internal company email system used only by employees to coordinate work. The two main IGPs you must know for the 350-501 exam are OSPF (Open Shortest Path First) and IS-IS (Intermediate System to Intermediate System).
How do these protocols actually work?
Both OSPF and IS-IS use a method called a 'link-state algorithm'. This is a fancy term that simply means: every router builds a complete map of the network.
Step 1: Discovery. When a router boots up, it sends out a 'Hello' message on each of its connected cables. It's like a new employee introducing themselves to everyone in the office. Any router that receives this 'Hello' and sends one back becomes a 'neighbour'. They establish a relationship.
Step 2: Information Sharing. Once routers are neighbours, they don't just share their whole route table at once (that would be chaotic). Instead, they share information about their direct connections – which networks they can reach and the 'cost' (usually based on the speed of the link) to get there. This information is called a Link State Advertisement (LSA) in OSPF or a Link State PDU (LSP) in IS-IS.
Step 3: Building the Database. Every router receives LSAs from all the other routers in the network. It stores these in a Link State Database (LSDB). Every router in the same 'area' (more on that below) has the exact same LSDB. It's as if every employee gets a copy of the complete company org chart.
Step 4: Calculating the Best Path. Each router then runs the Shortest Path First (SPF) algorithm (created by a computer scientist named Edsger Dijkstra) on its LSDB. This algorithm calculates the shortest, cheapest path from itself to every other destination in the network. The result is put into the Routing Information Base (RIB) – the router's personal route map.
The Key Difference: OSPF vs. IS-IS
Why does the industry have two protocols that do almost the same thing? History and design philosophy.
OSPF was created by the Internet Engineering Task Force (IETF) specifically for IP (Internet Protocol) networks. It is widely used and was designed from the ground up to run on top of IP. It has a 'backbone area' (Area 0) that all other areas must connect to. This is a hierarchical design, like a star.
IS-IS was originally created by the International Organization for Standardization (ISO) for a different protocol suite called CLNS. Later, it was adapted to support IP. This means IS-IS is 'protocol independent' – it can carry routing information for IP and non-IP protocols. Its hierarchy is more flexible: it uses 'Level 1' (inside an area) and 'Level 2' (between areas), but Level 2 routers don't have to be in a single central area. This makes IS-IS very popular in very large, complex service provider networks because it is often seen as more scalable and easier to troubleshoot.
Important Concepts to Know
Areas: Both protocols divide the network into areas to make it manageable. Routers inside an area only need to know the perfect path to destinations inside that area. To get to another area, they just send it to a 'border' router that knows the general direction. This reduces the number of routes each router has to remember. In OSPF, these are called 'OSPF areas' (like Area 0, Area 1). In IS-IS, they are simply 'Level 1 areas'.
Neighbours vs. Adjacencies: Just establishing a neighbour relationship isn't enough. To exchange LSAs, routers must form a 'full adjacency'. In OSPF on a broadcast network (like Ethernet), they use a process of electing a Designated Router (DR) and a Backup Designated Router (BDR) to reduce the amount of 'chatter'. IS-IS uses a simpler method and elects a Designated Intermediate System (DIS) but doesn't have a backup.
Metrics: The 'cost' of a link. In OSPF, the cost is typically derived from bandwidth (the faster the link, the lower the cost). In IS-IS, the default cost is a fixed value (10 on all links) unless you manually set it, though you can change this.
What does this replace? Before these modern link-state protocols, networks used older protocols like Routing Information Protocol (RIP). RIP was like a postal worker who only knew the next step, not the whole journey. It used 'hop count' (how many routers a packet must go through) as its metric, which was very simplistic and often led to bad routing decisions. RIP was also slow to recover from failures, taking minutes to update. OSPF and IS-IS are far superior because they have a complete map and can recalculate a new path in seconds after a failure.
Configuring OSPF on an Interface
You enter global configuration mode, run `router ospf 1` to start the OSPF process, and then use the `network` command to specify which interfaces should participate in OSPF and which area they belong to. For example, `network 10.0.0.0 0.255.255.255 area 0` tells OSPF to advertise any interface with an IP starting in 10.x.x.x into Area 0. This step is critical for defining the OSPF domain.
Verifying OSPF Neighbour Relationships
Use the command `show ip ospf neighbors` to see a list of all routers that have formed an adjacency (a formal relationship) with this router. The output shows the neighbour's Router ID, the interface they are connected on, and the state of the relationship (e.g., 'FULL'). If state is not FULL, something is wrong – mismatched timers, area IDs, or authentication keys.
Configuring IS-IS on an Interface
First, you enable IS-IS on the router with `router isis [tag]`, then set a unique Network Entity Title (NET) like `net 49.0001.1921.6800.1001.00`. Then, on each interface, you run `ip router isis` (for IPv4) to activate IS-IS on that link. This step binds the interface to the IS-IS process and defines the area (Level 1/Level 2) for that interface.
Verifying IS-IS Adjacencies
Run `show isis neighbors` to check if you have formed a level 1 or level 2 adjacency with peer routers. The output shows the neighbour's system ID, the interface, and the state ('UP' or 'INIT'). If the state is 'INIT', the router has received a Hello but not yet confirmed a two-way relationship, often due to mismatched authentication or area identifiers.
Configuring Route Redistribution between OSPF and IS-IS
On a border router running both protocols, you enter OSPF configuration and use `redistribute isis [tag] subnets` to inject IS-IS routes into OSPF. Similarly, in IS-IS configuration, use `redistribute ospf 1 metric 20` to inject OSPF routes into IS-IS. A route map is applied to filter specific routes and prevent loops. This step merges two routing domains.
Troubleshooting Missing Routes with Debug Commands
When a destination is unreachable, use `show ip route [destination]` to see if the route exists. If it does not, use `debug ip ospf events` or `debug isis adj-packets` to see if Hello messages are being exchanged. This step isolates whether the problem is an adjacency failure (Layer 2) or a route advertisement issue (Layer 3).
You are a network engineer at a Tier-1 service provider, let's call it 'GlobalConnect'. Your job this week is to integrate a newly acquired regional ISP, 'CityNet', into GlobalConnect's backbone. The CTO has demanded complete redundancy – if any single cable is cut, traffic must automatically reroute without any manual intervention.
Step-by-step scenario:
Initial Meeting and Design: Your lead architect hands you a design document. CityNet runs OSPF in a single area. GlobalConnect's massive backbone runs IS-IS. Your first task is to decide how to connect them. You cannot mix the two protocols on the same link without a special translation process called route redistribution.
Route Redistribution Planning: You decide to configure 'redistribution' on the border router that connects the two networks. This means the IS-IS router will take the OSPF routes it learns from CityNet, translate them into IS-IS format, and then advertise them into the wider GlobalConnect backbone.
Configuring OSPF on the New Links: You get on the console of the border router. You enter OSPF configuration mode. You tell OSPF which networks (in CIDR notation – a way to write a range of IP addresses) belong to CityNet. You set the 'router-id', which is a unique identifier for the router, often its highest loopback IP address. You then ensure the interfaces connecting to CityNet's routers are activated in OSPF.
Configuring IS-IS on the Same Router: On the same router, you also enter IS-IS configuration. You set the 'NET' (Network Entity Title), which is IS-IS's unique address, something like 49.0001.1921.6800.1001.00. You configure the router to operate at Level 1/Level 2 (L1/L2), meaning it will route traffic inside the new area (L1) and between areas (L2).
Implementing Redistribution: You write the redistribution policy. You tell IS-IS to embed OSPF routes, but you also apply a 'route-map' to control which specific OSPF routes are allowed in. You want to prevent any 'backdoor' paths or routing loops. You also need to handle the reverse direction: from IS-IS into OSPF, so CityNet knows about the rest of the world.
Verification and Troubleshooting: After saving the configuration, you run commands. In a live production network, you use show ip ospf neighbors to confirm GlobalConnect's routers are 'FULL' with CityNet's. You use show isis neighbors to see the same for the IS-IS side. You then run show ip route to verify that routes from both sides appear in the routing table. You test with a ping and a traceroute to a destination on CityNet's network from a server in GlobalConnect's core.
Scaling Considerations: You notice the LSDB is getting large. CityNet's network has 500 routers. In OSPF, you consider splitting it into multiple areas to reduce the SPF calculation load. This is a common design pattern: use a backbone area (Area 0) and attach stub areas (which have limited routing information) to it. In IS-IS, you ensure your Level 1 routers only know about their local area, and Level 2 routers handle the inter-area traffic.
The key tool you use daily in this process is the CLI (Command Line Interface). You will type commands like:
- router ospf 1 — to start OSPF process.
- network 10.0.0.0 0.255.255.255 area 0 — to advertise a range of addresses.
- log-adjacency-changes — to log when router relationships change, critical for troubleshooting.
This real-world task is the essence of what the 350-501 exam tests: the ability to configure, verify, and troubleshoot these protocols in a complex, multi-vendor environment.
The 350-501 exam, SPCOR, is a beast. For the OSPF and IS-IS section, you need to be brutally specific. The exam is not asking you to write a configuration from memory; it is testing your understanding of how the protocols operate and your ability to recognise the correct configuration or troubleshooting step from a set of multiple-choice answers.
What exact concepts will the exam test?
- OSPF LSA Types: This is a goldmine for exam question writers. They love to ask about the different Link State Advertisement types. - Type 1: Router LSA – describes a router's own links. - Type 2: Network LSA – generated by the Designated Router (DR) on a broadcast segment. - Type 3: Summary LSA – used between areas to advertise routes. - Type 4: ASBR Summary LSA – points to an Autonomous System Boundary Router. - Type 5: External LSA – for routes from outside the OSPF domain. - Type 7: NSSA External LSA – used in a special type of area called Not-So-Stubby Area (NSSA). The trap: they will ask which LSA is used for a specific purpose, e.g., 'What LSA type does an ABR (Area Border Router) use to advertise routes from one area to another?' The answer is Type 3. They will try to confuse you with Type 4 (which is for the ASBR, not inter-area routes) or Type 5 (which is for external routes).
OSPF Network Types: The exam tests your knowledge of how OSPF behaves on different link types: Broadcast, Point-to-Point, Non-Broadcast Multi-Access (NBMA), Point-to-Multipoint. The trap: they might give a scenario where you have two routers connected back-to-back but set the network type to Broadcast. OSPF will try to elect a DR and BDR, which is unnecessary and wastes time. The correct answer (and configuration) is to set the interface to 'point-to-point' to avoid the election process.
IS-IS Areas and Levels: The exam loves the IS-IS hierarchy. You must know:
- Level 1 (L1): Intra-area routing (routing within an area). - Level 2 (L2): Inter-area routing (routing between areas). - Level 1-2 (L1/L2): A router that does both and acts as a border router. The trap: they will ask 'If you configure a router as L1 only, will it learn routes from other areas?' The answer is no, unless you configure a default route. They will try to trick you into thinking L2 is for local routing.
Adjacency Formation: The exam will test the states of OSPF neighbor adjacency. You must memorise the sequence: Down, Init, 2-Way, ExStart, Exchange, Loading, Full. The trap: they will ask 'What state indicates a router has received a Hello but has not seen its own Router ID in the Hello?' The answer is Init. They might also ask about the 'DROTHER' state – routers that are not the DR or BDR on a segment.
SPF Calculation: They test your understanding of what triggers an SPF calculation: a change in the topology (link up/down) or a change in a metric. Merely receiving a new route (Type 3 LSA) does not trigger a full SPF in OSPF; it triggers a partial route calculation (PRC). The trap: they ask what happens when a router receives a Type 1 LSA – this triggers a full SPF because the topology changed.
Comparing OSPF and IS-IS: Expect a question directly asking 'Which of the following is a key difference between OSPF and IS-IS?' The exam loves to highlight that IS-IS is protocol independent and operates at Layer 2, while OSPF runs over IP (Layer 3). Another common comparison: OSPF requires multiple LSA types for different functions, whereas IS-IS uses a simpler structure (Link State PDUs).
Trap Patterns to Watch For:
- The exam will offer 'show' commands that sound correct but use the wrong keyword. For example, show ip ospf database is correct for LSDB, but they might offer show ip ospf routes. That is wrong.
- They will mix up the format of an IS-IS NET address. A valid NET is something like 49.0001.1921.6800.1001.00. The trap is an address with a missing byte (it must be an even number of hex digits) or an extra field.
- They will present a scenario where a route is missing, and the cause is a mismatched 'area ID' or 'authentication key' between neighbours. OSPF neighbours must agree on certain parameters (area, hello/dead intervals, authentication, network type) to form an adjacency.
What to Practise: - Memorise the OSPF LSA types 1-5 and 7. - Learn the IS-IS DIS election process (it is simpler than OSPF DR/BDR – no backup). - Understand route redistribution (how to import routes from OSPF to IS-IS and vice versa). - Know the default metrics: OSPF cost = reference bandwidth / interface bandwidth; IS-IS default metric is 10 (or 20 for default).
Being blunt: if you cannot list the seven OSPF neighbor states in order from your head, you are not ready. If you confuse a Type 3 LSA with a Type 5, you will fail that question. This section is about precision.
OSPF and IS-IS both use link-state advertisements (LSAs/LSPs) to build a complete network topology in every router's Link State Database (LSDB).
The Shortest Path First (SPF) algorithm calculates the optimal route based on cumulative cost, with OSPF deriving cost from bandwidth and IS-IS using a default metric of 10 per link.
OSPF requires a backbone area (Area 0) for multi-area routing, while IS-IS uses Level 1 and Level 2 routers without a mandatory central area.
The Designated Router (DR) in OSPF has a backup (BDR), whereas the Designated Intermediate System (DIS) in IS-IS does not use a backup.
Route redistribution allows OSPF and IS-IS to exchange routing information, but it must be carefully configured with route maps to avoid routing loops.
IS-IS operates at Layer 2 of the OSI model and can carry non-IP protocols, making it more flexible than OSPF in legacy or mixed-protocol environments.
The OSPF neighbor state machine proceeds through Down, Init, 2-Way, ExStart, Exchange, Loading, and Full; knowing this sequence is critical for troubleshooting adjacency issues.
These come up on the exam all the time. Here's how to tell them apart.
OSPF
Operates at Layer 3 (over IP).
Uses a mandatory backbone area (Area 0).
Has a Backup Designated Router (BDR) for fast failover.
IS-IS
Operates at Layer 2 (directly on the data link).
Does not require a single backbone area; uses Level 2 routers flexibly.
Does not have a backup DIS; re-election happens on failure.
OSPF DR
Elected using router priority and Router ID.
Has a BDR that takes over if the DR fails.
DR generates Type 2 (Network) LSAs for the segment.
IS-IS DIS
Elected using a simple priority value; highest MAC address often wins tie.
No backup; if DIS fails, a new election happens immediately.
DIS generates pseudonode LSPs to represent the broadcast network.
OSPF Metric (Cost)
Cost = 100 Mbps / interface bandwidth (configurable).
Lower cost indicates a faster link.
A 10 Gbps link defaults to cost 1.
IS-IS Metric (Default)
Default metric is 10 on all links (manual tuning required).
A 10 Gbps link and a 100 Mbps link both have a default cost of 10.
True path selection requires manual metric assignment to reflect speed.
Mistake
OSPF and IS-IS are completely different protocols that cannot work together.
Correct
They are different protocols with similar logic, and they can easily exchange routes through route redistribution on a border router.
Beginners see two different names and assume they are incompatible. In reality, service providers often run both and use redistribution to connect them.
Mistake
The Designated Router (DR) in OSPF is the same as the Designated Intermediate System (DIS) in IS-IS.
Correct
While both serve to manage adjacencies on a broadcast segment, the DR in OSPF has a Backup DR (BDR) and uses a complex election. The DIS in IS-IS has no backup; if the DIS fails, a new election happens immediately.
The names sound similar, and both are elected per segment. But IS-IS purposely avoids a backup to reduce complexity, while OSPF includes one for faster failover.
Mistake
IS-IS only works with IP networks.
Correct
IS-IS is protocol-agnostic. It was originally designed for the OSI protocol suite (CLNS) and later extended to support IP. It can carry routing information for multiple network layer protocols on the same router.
Most modern networks use IP, so people assume IS-IS is just another IP routing protocol like OSPF. Its history as a multi-protocol protocol is often overlooked.
Mistake
A higher OSPF cost means a better path.
Correct
The lowest cost path is the best. OSPF selects the route with the smallest cumulative cost. A higher cost indicates a less preferred link (e.g., a slower connection).
Newcomers often think 'higher is better' because they associate high numbers with performance. In OSPF, cost is inversely related to bandwidth: fast links = low cost, slow links = high cost.
Mistake
Both OSPF and IS-IS require a backbone area (Area 0) to function.
Correct
Only OSPF requires a backbone area (Area 0) for multi-area operation. IS-IS does not have a designated backbone area; it simply uses Level 2 routers to connect Level 1 areas.
The term 'backbone area' is so deeply associated with OSPF that learners assume IS-IS has an equivalent. But IS-IS's hierarchy is different and more flexible.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The main difference is that OSPF runs directly over IP (Layer 3), while IS-IS runs over the data link layer (Layer 2). IS-IS is protocol-independent and can carry non-IP routes, and it does not require a backbone area (Area 0) like OSPF does.
The EXSTART state means the routers are negotiating which one will be the master for the Database Description (DD) packet exchange. This usually happens due to a mismatch in the interface MTU size or a problem with the router ID (e.g., duplicate router IDs).
A stub area is an OSPF area that does not accept external route advertisements (Type 5 LSAs). Instead, it relies on a default route (0.0.0.0/0) to reach destinations outside the area. You use it to reduce the size of the LSDB and the number of SPF calculations on routers inside that area.
You must use route maps to control which routes are redistributed in each direction. A common technique is to set a high administrative distance on redistributed routes (e.g., `distance 200`) so they are less preferred than internally learned routes, preventing mutual redistribution feedback loops.
IS-IS uses a Designated Intermediate System (DIS). Unlike OSPF, there is no backup DIS. If the DIS fails, a new election is triggered immediately. The DIS is responsible for generating pseudonode LSAs on broadcast segments.
The states are: Down, Init, 2-Way, ExStart, Exchange, Loading, and Full. The '2-Way' state indicates a bidirectional communication has been established, and 'Full' means the routers have fully exchanged their link-state databases.
You've finished OSPF and IS-IS in Service Provider Environments. Continue through the 350-501 study guide to build a complete picture of the exam.
Done with this chapter?