OSPF is a link-state routing protocol used within a single autonomous system (AS). Here are the core characteristics:
Link-State Protocol:
Autonomous System Operation:
Classless Routing Support:
OSPF networks are organized into areas to enhance scalability and reduce processing overhead. Here's how they work:
Backbone Area (Area 0):
Non-Backbone Areas:
LSAs are the building blocks of OSPF's network representation. Each router exchanges LSAs to build the topology.
Type 1 (Router LSA):
Type 2 (Network LSA):
Type 3 (Summary LSA):
Type 4 (ASBR Summary LSA):
Type 5 (External LSA):
OSPF routers form adjacencies with their neighbors to exchange LSAs. For a successful adjacency:
Hello Packets:
Neighbor States:
DR and BDR:
OSPF supports various network types to adapt to different environments:
Broadcast Networks (e.g., Ethernet):
Point-to-Point Networks:
Non-Broadcast Multi-Access (NBMA) Networks:
Ensures secure communication between OSPF routers:
Used to reduce the size of routing tables:
Enable OSPF on an Interface:
set protocols ospf area 0 interface ge-0/0/1
Configure a Stub Area:
set protocols ospf area 1 stub
Set MD5 Authentication:
set interfaces ge-0/0/1 ospf authentication md5 key 1 secret-key
IS-IS (Intermediate System to Intermediate System) is another link-state routing protocol used in IP and MPLS networks. It operates at Layer 2 and is primarily used in large-scale service provider networks.
Layer 2 Operation:
Hierarchy and Scalability:
Example NSAP:
49.0001.1921.6800.1001.00
49.00011921.6800.100100Cost as a Metric:
Equal-Cost Multi-Path (ECMP):
Enable IS-IS on a Router:
set protocols isis level 2 interface ge-0/0/1
Configure Wide Metrics:
set protocols isis level 2 wide-metrics-only
Set NSAP Address:
set protocols isis router-id 49.0001.1921.6800.1001.00
Neighbor Relationship Issues:
Troubleshooting commands:
show ospf neighbor
show ospf interface ge-0/0/1
Route Propagation Problems:
LSA Flooding Issues:
show ospf database
Route Summarization Errors:
Designated Router (DR) Problems:
Misconfigurations may lead to multiple DRs or no DR.
Verify DR/BDR status:
show ospf interface ge-0/0/1
Single Area OSPF Configuration:
set protocols ospf area 0 interface ge-0/0/1
set protocols ospf area 0 interface ge-0/0/2
Multi-Area OSPF Configuration:
set protocols ospf area 0 interface ge-0/0/1
set protocols ospf area 1 interface ge-0/0/2
set protocols ospf area 1 stub
Route Redistribution:
set protocols ospf export external-routes
set policy-options policy-statement external-routes term 1 from protocol bgp
set policy-options policy-statement external-routes term 1 then accept
OSPF with Authentication:
set interfaces ge-0/0/1 ospf authentication md5 key 1 key "securekey"
set protocols ospf area 0 interface ge-0/0/1
OSPFv3 is the version of OSPF designed to support IPv6. It is an essential topic in many certifications, especially those involving dual-stack or IPv6-native environments.
Address Family Support:
OSPFv2 supports only IPv4.
OSPFv3 supports IPv6 natively.
Interface-Based Configuration:
Instance ID:
Security:
OSPFv3 does not use OSPF authentication fields.
Instead, it relies on IPsec for authentication and encryption, which is enabled by default in Junos.
set protocols ospf3 area 0.0.0.0 interface ge-0/0/0.0
This enables OSPFv3 on interface ge-0/0/0.0 for area 0 in Junos.
While IS-IS is covered in basic form, it's important to emphasize Junos-specific behavior and advanced concepts:
set protocols isis interface ge-0/0/1 family inet6
family inet6, IS-IS will not advertise IPv6 routes.DIS is the equivalent of OSPF's Designated Router (DR) for IS-IS on broadcast networks.
Only one router acts as the DIS per LAN.
Unlike OSPF, the DIS in IS-IS is not required to form adjacencies; it is only responsible for generating the pseudo-node LSPs for the LAN.
In Junos, redistribution between routing protocols requires explicit policy configuration, which is often overlooked:
Redistribution will not occur unless a policy is defined and applied.
Use policy-options to define route import/export rules.
Common mistake: defining export under OSPF but forgetting to create the actual policy-statement.
set policy-options policy-statement export-bgp-to-ospf term 1 from protocol bgp
set policy-options policy-statement export-bgp-to-ospf term 1 then accept
set protocols ospf export export-bgp-to-ospf
Metric manipulation is critical—redistributed routes can have very high or default metrics that disrupt routing decisions.
Improper redistribution may create routing loops, especially in designs involving mutual redistribution.
Understanding metric systems is essential for optimizing routing and troubleshooting path selection.
| Protocol | Metric Type | Range/Scalability | ECMP Support |
|---|---|---|---|
| OSPF | Cost (inverse of bandwidth) | 1–65535 (standard metric) | Yes |
| IS-IS | Custom Cost (integer) | Supports wide metrics for values > 63K | Yes |
OSPF:
Metric is usually derived from interface bandwidth (default cost = 100,000,000 / bandwidth in bps).
Static unless manually overridden.
IS-IS:
Uses integer-based costs, more flexible.
Wide metrics are widely supported, allowing for very large networks and better scaling.
Both:
Support ECMP (Equal-Cost Multi-Path).
Use SPF algorithms but have slightly different implementation logics.
| Area | Key Takeaway |
|---|---|
| OSPFv3 | Designed for IPv6, interface-based, uses IPsec |
| IS-IS in Junos | Level 2-only is common; requires per-family config |
| Redistribution | Always policy-controlled in Junos, avoid loops |
| Metrics | IS-IS has more flexible cost system than OSPF |
Why do many service provider networks prefer IS-IS instead of OSPF as their Interior Gateway Protocol?
IS-IS scales better in large service provider environments and integrates more cleanly with MPLS and IPv6 deployments.
Service provider networks often operate thousands of routers and multiple protocol extensions. IS-IS was originally designed for large carrier environments and has architectural advantages:
TLV-based design makes protocol extensions easier to add without redesigning packet formats.
Runs directly over Layer 2, not IP, which removes dependency on IP reachability during neighbor formation.
Better scaling for large topologies due to Level-1 / Level-2 hierarchy.
Operational simplicity when adding IPv6 or MPLS extensions.
OSPF can support similar functions but often requires additional LSAs and configuration complexity. Because of these factors, many carriers standardize on IS-IS as the core IGP.
Demand Score: 78
Exam Relevance Score: 84
An IS-IS adjacency between two routers remains stuck in the INIT state. What is the most likely cause?
The routers are receiving Hello packets but not forming a two-way adjacency, often due to mismatched authentication or interface configuration.
In the INIT state, a router has received a Hello packet but has not seen its own system ID listed in the neighbor's Hello packet. This usually indicates that the neighbor has not accepted the adjacency.
Common causes include:
Authentication mismatch
Different IS-IS levels configured
Passive interface configuration
MTU mismatch
Circuit type mismatch
Troubleshooting typically involves checking:
show isis adjacency
show isis interface
monitor traffic interface
Ensuring consistent authentication settings and interface parameters usually resolves the issue.
Demand Score: 74
Exam Relevance Score: 82
What is the purpose of Level-1 and Level-2 areas in IS-IS?
They provide hierarchical routing that improves scalability in large networks.
IS-IS divides networks into two levels:
Level-1
Intra-area routing
Routers know routes only within their own area
Level-2
Inter-area backbone routing
Connects multiple Level-1 areas together
Routers operating as Level-1-2 routers connect areas and act as gateways between them. This hierarchy reduces routing table size and limits flooding of link-state information.
In service provider networks, the Level-2 backbone is commonly used to interconnect multiple regions of the network while Level-1 areas isolate local routing changes.
Demand Score: 69
Exam Relevance Score: 80
What operational advantage does IS-IS provide when deploying IPv6 in service provider networks?
IPv6 support can be added without changing the base protocol operation.
IS-IS uses a TLV (Type-Length-Value) encoding structure for protocol extensions. Because of this design, IPv6 routes can be carried using new TLV types without modifying the core protocol.
Operational benefits include:
IPv4 and IPv6 routes advertised in the same protocol instance
No need for a separate routing process
Simplified configuration and operations
In contrast, OSPF requires a separate protocol instance (OSPFv3) to support IPv6. The flexibility of IS-IS TLVs has made it a preferred protocol for networks adopting new technologies such as IPv6, MPLS, and traffic engineering.
Demand Score: 70
Exam Relevance Score: 83