Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 199)

Multi-Service IronWare Routing Configuration Guide 171
53-1003033-02
Configuring OSPF
Figure 12 shows an example of an OSPF network containing an NSSA.
FIGURE 12 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 Type-7 LSAs, which the ASBR floods
throughout the NSSA.
The ABR translates the Type-7 LSAs into Type-5 LSAs. If an area range is configured for the NSSA,
the ABR also summarizes the LSAs into an aggregate LSA before flooding the Type-5 LSAs into the
backbone.
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 Type-7 LSA into the NSSA.
Configuring an NSSA
To configure OSPF area 10.1.1.1 as an NSSA, enter the following commands.
Brocade(config)# router ospf
Brocade(config-ospf-router)# area 10.1.1.1 nssa 1
Brocade(config-ospf-router)# write memory
Syntax: [no] area area-id nssa [[nssa-ext-metric] [default-information-originate [metric
metric-value | metric-type type-value]] [no-redistribution] [translator-always]
[translator-interval stability-interval]]
The area-id parameter specifies the area and has the format xx or xx.xxxx. For example, 49 and
49.2211 are valid area IDs.
The nssa-ext-metric parameter specifies the NSSA's advertised external route metric.