OSPF Forwarding Address Explained: NSSA Translation and Missing External Routes
Short answer: A nonzero OSPF forwarding address needs internal OSPF reachability; an external LSA alone does not make its route usable.[1]
This guide focuses on that dependency in OSPFv2, including NSSA translation. It is not a general introduction to LSA types. The lab below is a proposed, isolated experiment; its configuration has not been executed on routers.
Three fields to read before changing a metric
Zero means resolve through the ASBR; nonzero means resolve through an intra-area or inter-area path to the forwarding address.[1]
That address need not equal the local immediate next hop.[1]
Operational consequence: collect the complete LSA before changing costs. A missing dependency and a less-preferred valid route require different remedies.
Why a nonzero forwarding address exists
Cisco explains the original purpose as avoiding an unnecessary hop through a redistributing router when a better forwarding path exists. Its classic Type-5 example ties nonzero address selection to the next-hop interface's OSPF participation, passive state and network type. Do not extend those classic conditions into a universal NSSA selection rule.[3]
That Cisco document also flags an old redistribution behavior change around IOS 12.1(3). Treat its historical failure topology as explanation, not evidence that a current IOS XE release has the same bug.[3]
NSSA: the translating router is not always the forwarding target
An eligible NSSA ABR translates Type-7 LSAs into Type-5 LSAs; individual translations normally preserve nonzero forwarding addresses.[2] A set P-bit requires a nonzero address at Type-7 origination; aggregated translations have separate rules.[2]
Preservation supports efficient forwarding with multiple border routers.[2] Hiding internal reachability to that address can break the translated route despite LSA visibility.[4]
Proposed lab: make the dependency visible
Use disposable routers with no production connectivity. The addressing and test prefix below are documentation examples. Interface names must match your platform. Start without summaries, filtering or forwarding-address suppression.
R1 (core) -- area 0 -- R2 (NSSA ABR) -- area 10 -- R3 (ASBR)
R1 Gi0/0: 192.0.2.1/30 R2 Gi0/0: 192.0.2.2/30
R2 Gi0/1: 198.51.100.1/30 R3 Gi0/0: 198.51.100.2/30
R3 Loopback0: 192.0.2.33/32 (advertised in area 10)
External test prefix on R3: 203.0.113.0/24 -> Null0
Router IDs: R1 10.255.0.1, R2 10.255.0.2, R3 10.255.0.3
Cisco-style baseline
The proposed redistribution is deliberately restricted to one static test prefix. Null0 makes this a control-plane exercise: successful route installation will not make that destination respond to ping. This configuration is original lab material, not captured output.
! R1
interface GigabitEthernet0/0
ip address 192.0.2.1 255.255.255.252
ip ospf 10 area 0
no shutdown
router ospf 10
router-id 10.255.0.1
! R2
interface GigabitEthernet0/0
ip address 192.0.2.2 255.255.255.252
ip ospf 10 area 0
no shutdown
interface GigabitEthernet0/1
ip address 198.51.100.1 255.255.255.252
ip ospf 10 area 10
no shutdown
router ospf 10
router-id 10.255.0.2
area 10 nssa
! R3
interface GigabitEthernet0/0
ip address 198.51.100.2 255.255.255.252
ip ospf 10 area 10
no shutdown
interface Loopback0
ip address 192.0.2.33 255.255.255.255
ip ospf 10 area 10
ip route 203.0.113.0 255.255.255.0 Null0
ip prefix-list LAB-EXTERNAL seq 10 permit 203.0.113.0/24
route-map LAB-STATIC permit 10
match ip address prefix-list LAB-EXTERNAL
router ospf 10
router-id 10.255.0.3
area 10 nssa
redistribute static subnets metric 20 metric-type 2 route-map LAB-STATIC
Record the actual forwarding address in R3's Type-7 and R1's translated Type-5 LSA. Do not assume a specific interface wins address selection. The proposed failure experiment hides both candidate internal prefixes, so first confirm that the actual address is covered.
Controlled failure: hide the internal dependency
On the lab ABR only, apply this outbound Type-3 filter for area 10. The filter is intended to remove the loopback and transit-prefix advertisements toward the core, not to filter the external LSA itself.[5] Compare behavior with the related OSPF filtering article before adapting this to another platform.
ip prefix-list LAB-HIDE-FA seq 5 deny 192.0.2.33/32
ip prefix-list LAB-HIDE-FA seq 10 deny 198.51.100.0/30
ip prefix-list LAB-HIDE-FA seq 100 permit 0.0.0.0/0 le 32
router ospf 10
area 10 filter-list prefix LAB-HIDE-FA out
Expected, not measured: remove every eligible internal path to a nonzero forwarding address, and its external route becomes ineligible.[1]
Rollback the experiment on R2:
router ospf 10
no area 10 filter-list prefix LAB-HIDE-FA out
An external route to the forwarding address cannot replace the required internal path.[1] Restore the intended advertisement, then repeat the checks.
Verification: database, routing table, forwarding table
Use this proposed worksheet on Cisco-style CLIs; confirm syntax on the installed release. Substitute the address actually observed in the LSA.
! R3: inspect NSSA origination
show ip ospf database nssa-external 203.0.113.0
! R1: inspect translated LSA and installed routes
show ip ospf database external 203.0.113.0
show ip route 203.0.113.0
show ip route 192.0.2.33
show ip route 198.51.100.2
show ip ospf border-routers
show ip cef 203.0.113.1 detail
Save three snapshots: baseline, filter applied, and rollback. For each, record advertising router, forwarding address, route type to that address, selected next hop, and whether the external route reaches the forwarding table. FRRouting documents comparable OSPF database inspection, including the external LSA's forwarding-address field.[5]
A packet capture can supplement these records, but do not describe traffic to the Null0 test prefix as a reachability test. For a later data-plane exercise, replace the discard route with a real isolated destination and explicitly provide its return path.
Suppression: a scoped design option, not the first repair
Cisco IOS XE's translator option zeros the translated Type-5 forwarding address and directs forwarding toward the translating ABR.[4] Cisco warns of suboptimal routing and noncompliance with RFC 1587.[4] This is also a departure from RFC 3101's normal individual-translation preservation.[2]
! Optional alternative on R2; not part of the baseline or rollback
router ospf 10
area 10 nssa translate type7 suppress-fa
This is not a command to erase every forwarding address in the OSPF domain, nor does it rewrite the original Type-7 field. Keep it out of a troubleshooting change until the intended forwarding path and translator redundancy are understood.[4]
FRRouting uses different syntax. Its documentation specifically requires that the router be the elected translator for the setting to take effect.[5]
! FRRouting alternative on the NSSA translator
router ospf
area 10 nssa suppress-fa
Traffic control and modern boundaries
- Outbound forwarding: a nonzero address makes its internal path relevant, rather than simply the originator's path.[1] Use the worksheet to establish the actual egress.
- Inbound influence: this mechanism provides no policy signal to a remote ISP. Treat return routing, firewall state and NAT as separate acceptance checks; do not claim symmetry from a successful outbound test.
- What it cannot do: forwarding-address suppression is not BGP LOCAL_PREF, a provider community, or a per-application traffic policy. Do not use it as a substitute for an explicit edge-routing design.
- Modern use: apply this diagnostic at an OSPF redistribution boundary, including a cloud-edge or data-center border when that design actually uses OSPF. It is not a general description of an EVPN control plane or of Cisco ACI internals.
Troubleshooting checklist
- Confirm the external prefix and advertising router in the LSA, not only a neighbor's Full state.
- Read the forwarding address before changing external metrics.
- If nonzero, prove internal OSPF reachability.[1]
- Compare Type-7 and translated Type-5 fields at the NSSA boundary.[2]
- Review Type-3 filters and summaries; a usable covering internal summary is different from removing every internal path.
- Verify which ABR is translating before interpreting suppression behavior.[5]
- Inspect RIB and forwarding-table results separately, then validate the independent return path.
- Roll back the lab filter and require baseline behavior to return before adding another variable.
Interview answer
A nonzero forwarding address needs an intra-area or inter-area path.[1] For NSSA troubleshooting, compare the Type-7 and translated Type-5 fields, then trace that dependency.
Summary: read the field, trace its internal dependency, and test one change at a time. Prefer repairing the intended route advertisement over hiding the symptom with a translator-specific feature.
Related reading
- OSPF Route Filtering Explained: Distribute Lists vs ABR Filter Lists
- OSPF Stub vs Totally Stubby vs NSSA: Differences and Default Routes
- OSPF Router ID Explained: Duplicate IDs, Selection and Safe Changes
- OSPF Summarization Explained: ABR area range, ASBR Summaries and Blackholes
Sources
- https://www.rfc-editor.org/rfc/rfc2328.html
- https://www.rfc-editor.org/rfc/rfc3101.html
- https://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/13682-10.html
- https://www.cisco.com/c/en/us/td/docs/routers/ios-xe/ip-routing/b-ip-routing/m_iro-for-add-supp.html
- https://docs.frrouting.org/en/latest/ospfd.html
Try it: CCNP Practice Quiz - free, runs in your browser. Full reading order: CCNP ENCOR & ENARSI Study Path. Also try: CIDR to IP Range - free, runs in your browser.
Related reading
- OSPF Summarization Explained: ABR area range, ASBR Summaries and Blackholes
- OSPF Router ID Explained: Duplicate IDs, Selection and Safe Changes
- OSPF ECMP Explained: Equal-Cost Routes, Load Sharing and Troubleshooting
- OSPF Passive Interface Explained: Advertise Subnets Without Neighbors
- OSPF Default Route Origination: Always, E1/E2 and IP SLA
- OSPF Route Filtering Explained: Distribute Lists vs ABR Filter Lists
Comments
Post a Comment