OSPF Loop‑Avoidance Mechanisms: How Different LSA Types Prevent Routing Loops

When discussing OSPF, we often say it can compute loop‑free routes; the article details how OSPF avoids routing loops by relying on the design of different Link‑State Advertisements (LSAs).

1. Type‑1 and Type‑2 LSA loop avoidance – Every OSPF router generates a Type‑1 LSA describing its directly connected interfaces (IP, neighbors, cost) and floods it within its area. In multi‑access networks, the Designated Router (DR) creates a Type‑2 LSA that lists all routers on the network and the network mask.

These LSAs allow each router to reconstruct the complete intra‑area topology and run the Shortest Path First (SPF) algorithm on an identical LSDB, producing a loop‑free shortest‑path tree rooted at the router.

In the example network (R1‑R4 in Area 0), each router floods Type‑1 LSAs, the DR floods a Type‑2 LSA, and after LSDB synchronization every router has the full topology, enabling loop‑free intra‑area routes.

2. Type‑3 and Type‑4 LSA loop avoidance

OSPF requires all non‑zero areas to be directly attached to the backbone (Area 0). Inter‑area routes must pass through the backbone, preventing loops between non‑zero areas and forming a logical star topology.

ABRs inject intra‑area routes from their attached areas into Area 0, but they only inject inter‑area routes into non‑zero areas; they never inject Type‑3 LSAs received from a non‑zero area back into the backbone.

The article illustrates this with R3 acting as an ABR: when R3 has an OSPF neighbor relationship with R2, it stops using the Type‑3 LSA from Area 2 for the 1.1.1.0/24 route, avoiding a potential loop.

RFC 2328 states that only intra‑area routes are advertised into the backbone, while RFC 3509 adds that a router with an active backbone connection can advertise both intra‑ and inter‑area routes into other areas.

3. Additional LSA details

Type‑3 LSAs also contain a DN bit used for loop avoidance in MPLS VPN environments.

4. Type‑5 LSA loop avoidance

When an OSPF router imports an external route, it becomes an ASBR and floods the route as a Type‑5 LSA throughout the OSPF domain. The router can compute the route only if it receives the Type‑5 LSA and knows the ASBR’s location, which is derived from Type‑1 LSAs (in the same area) or Type‑4 LSAs (from other areas). Thus, Type‑5 LSAs rely on the loop‑avoidance mechanisms of Type‑1 and Type‑4 LSAs.

The External Route Tag field in Type‑5 LSAs is also used for loop avoidance in MPLS VPNs.