In addition to the backbone (area 0) and other non-backbone areas described and used in the examples in previous sections of this chapter, the OSPF specification also defines several ‘special’ types of areas. The configuration of these areas is primarily used to reduce the size of the Link State Database on routers residing within those areas by preventing the injection of different types of LSAs (primarily Type 5 LSAs) into certain Areas. These areas are:
- Not-so-stubby Areas
- Totally Not-so-stubby Areas
- Stub Areas
- Totally Stubby Areas
Not-so-stubby Areas (NSSA)
Not-so-stubby Areas (NSSAs) are a type of OSPF stub area that allows the injection of external routing information by an ASBR using an NSSA External LSA (Type 7). As stated in the previous section, Type 4, Type 5, and Type 7 LSAs are used for external route calculation. Type 4 and Type 5 LSAs were described in the previous section. In this section, we will go into detail on Type 7 LSAs and how they are used in NSSAs.
The Type 7 LSA is used for external routing information from the ASBR within the NSSA. The external routing information within the LSA is converted by the ABR into Type 5 LSA at the area boundary. The ABR then floods the Type 5 LSA into the OSPF domain, and other routers in the network are aware of the external networks. Type 7 LSAs have an area flooding scope, so only routers in the NSSA receive the Type 7 LSA. Figure 3-18 illustrates the flooding and conversion of Type 7 LSAs to Type 5 LSAs:
Fig. 3-18. Type 7 LSA to Type 5 LSA Conversion
Referencing Figure 3-18, R2, the ASBR, redistributes EIGRP routes into OSPF. R2 resides in an NSSA and generates Type 7 LSAs for the external routes. These LSAs are flooded only within the NSSA. The Type 7 LSAs are received by R3, the ABR. R3 converts the Type 7 LSAs to Type 5 LSAs and floods them to adjacent areas. These External LSAs are propagated to R4, and ultimately to R5. The Type 7 LSAs never leave area 1. NSSAs have the following characteristics:
- They use Type 7 LSAs to carry external information within the NSSA
- The NSSA ABR converts Type 7 LSAs into Type 5 LSAs
- Type 4 and Type 5 LSAs are not allowed into Not-so-stubby Areas
- Network Summary LSAs are allowed into the NSSA
While Type 5 and Type 7 LSAs are used for external routes, there are some differences between the two types of LSAs that you should be familiar with. The first difference is that while both use a similar packet format, the Type field contains the value 7 instead of 5, indicating that this is a Type 7 LSA and not a Type 5 LSA.
The second important difference is that the Forwarding Address calculation is different for a Type 7 LSA. With Type 5 LSAs, the Forward Address field contains a value of 0 unless one of the following exceptions applies:
- If the ASBRs next-hop interface network type is not P2P or point-to-multipoint
- If OSPF is enabled on the ASBRs next-hop interface
- If the next-hop interface of the ASBR falls into a defined OSPF network range
- If the ASBRs next-hop interface is not a passive OSPF interface
With Type 7 LSAs, if the route has a next-hop address, i.e. it is not a connected network; use the next-hop address in the Forward Address field. This hold true only if the route is an internal OSPF route. In other words, if the network between the NSSA boundary router and the adjacent AS is advertised into OSPF as an internal OSPF route, the forwarding address should be the next-hop address.
However, if the network is not advertised into OSPF as an internal route, the Forward Address should be any of the active interfaces on the router. This means that if there is a Loopback interface enabled for OSPF routing in the area announcing the LSAs on the router, use that interface. If there are no Loopback interfaces, then the address of the first operational interface in that area should be used.
The third difference also pertains to the LSA packet format. The Type 7 LSA Options field is slightly different for NSSAs. For Type 7 LSAs, the N/P bits must be used. The use of these two bits is described in the following section:
The N bit describes the handling and support of NSSA LSAs, mentioned in RFC 1587. It is used in Hello packets and ensures NSSA configuration. When the N-bit is reset in the Hello packet sent out a particular interface, it means that the router will neither send nor receive Type 7 LSAs on that interface. Two routers will not form an adjacency unless they agree on the state of the N-bit. In addition to this, it is imperative to know that if the N-bit is set in the options field, the E-bit must be reset.
As stated earlier in this chapter, the E-bit is used in External (Type 5) LSAs and specifies the type of external metric. NSSAs do not use E1 and E2 external routes, but instead use N1 and N2 external routes. These routes are basically the same as those in External LSAs, but pertain to NSSAs. N1 routes are comparable to E1 routes and N2 routes are comparable to E2 routes. By default, external NSSA routes are N2 in Cisco IOS software.
The P (Propagation) bit is used for propagation control and tells the NSSA ABR whether or not to translate Type 7 LSAs into Type 5 LSAs. If the P bit is set to 0, it means that no Type 7 to Type 5 LSA translation will occur. This typically occurs when the NSSA ASBR is also an NSSA ABR.
However, if the P bit is set to 1, it means that Type 7 to Type 5 LSA translation will occur. In the event that multiple NSSA ABRs are present, the router with the lowest RID will perform the Type 7 to Type 5 LSA translation. NSSA configuration in Cisco IOS software is a straightforward process. The area [area ID] nssa [default-information-originate [metric <value> | metric-type <type> | no-redistribution | no-summary | translate type7 suppress-fa] router configuration command is used to configure an area as an NSSA. The minimal required configuration would simply be the configuration area [area ID] nssa command on all routers within the NSSA.
The default-information-originate [metric | metric-type] keyword may be used on either the ABR or NSSA ASBR. This keyword is used to generate a Type 7 default into the NSSA. The metric keyword is used to specific the metric for the default route and the metric-type keyword is used to specify whether the default route should be N1 or N2. By default, external NSSA routes are N2 in Cisco IOS software.
The no-redistribution keyword is used on the NSSA ABR to prevent external routes into the NSSA, while allowing external routes into other (normal) OSPF areas. The no-summary keyword prevents Summary LSAs from being advertised into the NSSA.
And finally, the translate type7 suppress-fa keyword is used to configure OSPF Forwarding Address Suppression in Translated Type-5 LSAs. This configuration instructs the router to suppress the Forwarding Address in translated Type 5 LSAs. This configuration causes the router to be noncompliant with RFC 1587 – The OSPF NSSA Option. This configuration is beyond the scope of the ROUTE exam and is not illustrated in this chapter.
The topology shown in Figure 3-19 will be used to illustrate NSSA configuration:
Fig. 3-19. Configuring NSSAs
Referencing the topology illustrated in Figure 3-19, area 1 will be configured as an NSSA. R1 will also be configured as an ASBR and will redistribute the following static networks:
- 150.100.254.0/24 – Next Hop 172.16.1.254
- 150.101.254.0/24 – Next Hop 172.16.1.254
- 150.102.254.0/24 – Next Hop 172.16.1.254
- 150.103.254.0/24 – Next Hop 172.16.1.254
NOTE: It should be assumed that basic OSPF configuration has already been implemented on the other routers in the network and all adjacencies are established. The basic configuration on R1 is performed as follows:
| R1(config)#ip route 150.100.254.0 255.255.255.0 172.16.1.254 R1(config)#ip route 150.101.254.0 255.255.255.0 172.16.1.254 R1(config)#ip route 150.102.254.0 255.255.255.0 172.16.1.254 R1(config)#ip route 150.103.254.0 255.255.255.0 172.16.1.254 R1(config)#router ospf 1 R1(config-router)#redistribute static subnets R1(config-router)#area 1 nssa R1(config-router)#exit |
Next, R2, the Area Border Router, is configured so that area 1 is also an NSSA as follows:
| R2(config)#router ospf 2 R2(config-router)#area 1 nssa R2(config-router)#exit |
On R1, the ASBR, the external routes are added to the LSDB as Type 7 External routes:
| R1#show ip ospf database | begin Type-7 Type-7 AS External Link States (Area 1)Link ID ADV Router Age Seq# Checksum Tag 150.100.254.0 1.1.1.1 78 0x80000001 0x00187C 0 150.101.254.0 1.1.1.1 78 0x80000001 0x000C87 0 150.102.254.0 1.1.1.1 78 0x80000001 0x00FF92 0 150.103.254.0 1.1.1.1 78 0x80000001 0x00F39D 0 |
On R2, the same routes are received as N2 external routes, which is the default:
| R2#show ip route ospf | include N2 O N2 150.102.254.0 [110/20] via 10.0.0.1, 00:05:06, Serial0/0 O N2 150.103.254.0 [110/20] via 10.0.0.1, 00:05:06, Serial0/0 O N2 150.100.254.0 [110/20] via 10.0.0.1, 00:05:06, Serial0/0 O N2 150.101.254.0 [110/20] via 10.0.0.1, 00:05:06, Serial0/0 |
As the ABR, R2 adds the Type 7 LSAs to the LSDB and generates Type 5 LSAs for each of the Type 7 LSAs. This is illustrated in the following output:
| R2#show ip ospf database | begin Type-7 Type-7 AS External Link States (Area 1)Link ID ADV Router Age Seq# Checksum Tag 150.100.254.0 1.1.1.1 534 0x80000001 0x0011CA 0 150.101.254.0 1.1.1.1 534 0x80000001 0x0005D5 0 150.102.254.0 1.1.1.1 534 0x80000001 0x00F8E0 0 150.103.254.0 1.1.1.1 534 0x80000001 0x00ECEB 0Type-5 AS External Link States Link ID ADV Router Age Seq# Checksum Tag |
NOTE: The configuration of the NSSA results in a Type 4 LSA being generated for the ABR. In essence, the ABR becomes an ASBR because it is translating the Type 7 LSAs to Type 5 LSAs. The Type 4 LSA is flooded to all adjacent areas announcing the location of the ASBR. This can be verified on R3, for example, which floods the Type 4 LSA into area 2:
| R3#show ip ospf database asbr-summary OSPF Router with ID (3.3.3.3) (Process ID 3)Summary ASB Link States (Area 2)LS age: 1121 Options: (No TOS-capability, DC, Upward) LS Type: Summary Links(AS Boundary Router) Link State ID: 2.2.2.2 (AS Boundary Router address) Advertising Router: 3.3.3.3 LS Seq Number: 80000006 Checksum: 0xC45D Length: 28 Network Mask: /0 TOS: 0 Metric: 1 |
Reverting back to NSSA configuration and validation, the show ip ospf database nssa-external [link state ID]command is used to view detailed information on the Type 7 LSAs. In the following output, the Forward Address field contains the IP address of the next hop because the 172.16.1.0/24 network is advertised by OSPF on R1. This is illustrated below:
| R2#show ip ospf database nssa-external 150.100.254.0OSPF Router with ID (2.2.2.2) (Process ID 2)Type-7 AS External Link States (Area 1)
Routing Bit Set on this LSA |
The same Forward Address is also used in the Type 5 LSAs generated by R2 as shown below:
| R4#show ip ospf database external 150.100.254.0OSPF Router with ID (4.4.4.4) (Process ID 4)Type-5 AS External Link States
Routing Bit Set on this LSA |
However, if the 172.16.1.0/24 subnet was not advertised by OSPF, the Forward Address field would default to the highest Loopback address of R1 for the Type 7 LSA. This value would also be included in the Type 5 LSAs generated by R2 and flooded to the rest of the OSPF domain:
| R2#show ip ospf database nssa-external 150.100.254.0OSPF Router with ID (2.2.2.2) (Process ID 2)Type-7 AS External Link States (Area 1)
Routing Bit Set on this LSA |
The same Forward Address is also used in the Type 5 LSAs generated by R2 as shown below:
| R4#show ip ospf database external 150.100.254.0OSPF Router with ID (4.4.4.4) (Process ID 4)Type-5 AS External Link States
Routing Bit Set on this LSA |
While the ABR translates Type 7 LSAs into Type 5 LSAs and floods the Type 5 LSAs to adjacent areas, because external routes (Type 5) are not permitted in NSSAs, the ABR will not translate Type 5 LSAs into Type 7 LSAs and flood them into the NSSA. For example, referencing the network topology illustrated in Figure 3-19, R4 is configured with an additional Loopback interface which is then redistributed into OSPF to generate a Type 5 LSA. This is performed as illustrated in the following output:
| R4(config)#interface loopback 144 R4(config-if)#ip address 144.144.144.144 255.255.255.255 R4(config-if)#exit R4(config)#router ospf 4 R4(config-router)#redistribute connected subnets R4(config-router)#exit |
The Type 5 LSA is flooded throughout the OSPF domain and is present in the LSDB on R2:
| R2#show ip ospf database | begin Type-7 Type-7 AS External Link States (Area 1)Link ID ADV Router Age Seq# Checksum Tag 150.100.254.0 1.1.1.1 583 0x80000003 0x00147E 0 150.101.254.0 1.1.1.1 583 0x80000003 0x000889 0 150.102.254.0 1.1.1.1 583 0x80000003 0x00FB94 0 150.103.254.0 1.1.1.1 583 0x80000003 0x00EF9F 0Type-5 AS External Link States Link ID ADV Router Age Seq# Checksum Tag |
However, while the ABR (R2) will flood Summary LSAs into the NSSA, R2 will not flood the Type 5 LSA into the NSSA. This is illustrated in the following output on R1:
| R1#show ip ospf databaseOSPF Router with ID (1.1.1.1) (Process ID 1)Router Link States (Area 1)
Link ID ADV Router Age Seq# Checksum Link count Summary Net Link States (Area 1) Link ID ADV Router Age Seq# Checksum Type-7 AS External Link States (Area 1) Link ID ADV Router Age Seq# Checksum Tag |
Based on the contents of the LSDB, R1 will not be able to reach the 144.144.144.4/32 address redistributed into OSPF on R4 for the following reasons:
- Because external routes are not advertised into an Not-so-Stubby-Area (NSSA)
- Because the ABR does not generate a default route for an NSSA by default
The first point is based on the design of the protocol. This cannot be changed. However, the second point is one that can be addressed by issuing the area [area id] default-information-originate [metric | metric-type]configuration command on the ABR. This configuration causes the ABR to generate a Type 7 default route into the NSSA. Referencing the network topology illustrated in Figure 3-18, this configuration would be implemented on R2 as follows:
| R2(config)#router ospf 2 R2(config-router)#area 1 nssa default-information-originate R2(config-router)#exit |
The default route is added to the LSDB on R2 as a Type 7 LSA. This route will be generated as a Type 2 (N2) external route with a route metric of 1 and will be flooded only into the NSSA. In addition to this, the Forward Address will be 0.0.0.0, indicating that the traffic should be forwarded to R2. This is shown in the following output:
| R2#show ip ospf database nssa-external 0.0.0.0OSPF Router with ID (2.2.2.2) (Process ID 2)Type-7 AS External Link States (Area 1)
LS age: 64 |
The same information is also reflected in the LSDB on R1 as illustrated in the following output:
| R1#show ip ospf database nssa-external 0.0.0.0OSPF Router with ID (1.1.1.1) (Process ID 1) Type-7 AS External Link States (Area 1)
Routing Bit Set on this LSA |
The default route is installed into the routing table and R1 is able to ping the external network that was redistributed into OSPF on R4:
| R1#show ip route 0.0.0.0 Routing entry for 0.0.0.0/0, supernet Known via “ospf 1”, distance 110, metric 1, candidate default path, type NSSA extern 2, forward metric 64 Last update from 10.0.0.2 on Serial0/0, 00:05:56 ago Routing Descriptor Blocks: * 10.0.0.2, from 2.2.2.2, 00:05:56 ago, via Serial0/0 Route metric is 1, traffic share count is 1 |
NOTE: The Forward Metric shown in the output above is the cost from R1 to R2. The actual route metric itself never changes for a Type 2 external route.
When the area [area ID] nssa default-information-originate router configuration command is issued on R2, it effectively becomes an ASBR and a Type 4 LSA is generated for this router. A Type 4 LSA would also be generated for R4 because it is redistributing external routes into OSPF. However, a Type 4 LSA will not be generated for the NSSA ASBR. Both Type 4 LSAs will be in listed in the LSDB on R3:
| R3#show ip ospf databaseOSPF Router with ID (3.3.3.3) (Process ID 3)Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count Net Link States (Area 0) Link ID ADV Router Age Seq# Checksum Summary Net Link States (Area 0) Link ID ADV Router Age Seq# Checksum Summary ASB Link States (Area 0) Link ID ADV Router Age Seq# Checksum Router Link States (Area 2) Link ID ADV Router Age Seq# Checksum Link count Summary Net Link States (Area 2) Link ID ADV Router Age Seq# Checksum Summary ASB Link States (Area 2) Link ID ADV Router Age Seq# Checksum Type-5 AS External Link States Link ID ADV Router Age Seq# Checksum Tag |

