Advanced Configuration and Management Guide
The HP implementation of NSSA is based on RFC 1587.
Figure 8.5 shows an example of an OSPF network containing an NSSA.
RIP Domain
|
|
|
|
|
| NSSA Area 1.1.1.1 | OSPF Area 0 | |
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
| |||
|
|
|
|
|
|
|
| Backbone |
|
|
|
|
|
|
|
|
|
Internal ASBR | OSPF ABR |
Figure 8.5 OSPF network containing an NSSA
This example shows two routing domains, a RIP domain and an OSPF domain. The ASBR inside the NSSA imports external routes from RIP into the NSSA as
The ABR translates the
Since the NSSA is partially “stubby” the ABR does not flood external LSAs from the backbone into the NSSA. To provide access to the rest of the Autonomous System (AS), the ABR generates a default
8 - 12