OSPF Stub area, totally stubby and NSSA

multiple-area OSPF on a router

 

this is standard ospf out put from sho ip osp neighbor and router and if you look at R2 they are no inter-area routes

Now we are Using  configure a OSPF are 23 as a STUB and do the show ip ospf on R2. As you see area 23 now is shows as stub area . Lets do a show ip route command on R3, you can see that R3 now has a default route pointing toward R2. A stub area does not receive any external routes. It receives a default route and OSPF inter-area routes.

The command to configure stubby area is as follow:

R2(config)# router ospf 1
R2(config-router)# area 23 stub
R3(config)# router ospf 1
R3(config-router)# area 23 stub

On R2 we are going to do show ip ospf database to examine the LSA's. As you see we have only 2 LAS's for each area.

In this next senario we configured OSPF as totally stubby area , look at the out put of sho ip ospf database and look at the LSA for area 23 . you see that the default route was injected and when you issue the command sho ip route you can only see the incoming route from ospf .

The command to configure totally stubby areais as follow:

Enter the stub no-summary command on R2 (the ABR) under the OSPF process. 
R2(config)# router ospf 1
R2(config-router)# area 23 stub no-summary

Now will discus NSSA. 

To generate an external route into the NSSA, use the redistribute connected subnets command on R3. This adds the previously unreachable loopback 20 into OSPF. Be sure to include the subnets keyword; otherwise, only classful networks are redistributed.

R2(config)# router ospf 1
R2(config-router)# no area 23 stub
R2(config-router)# area 23 nssa

R3(config)# router ospf 1
R3(config-router)# no area 23 stub
R3(config-router)# area 23 nssa
R3(config-router)# redistribute connected subnets
after the config on R2 and R3 as ASSA we come up w/ the following out out when sho ip osp command is typed on R2 (it will be the same on R3) :

Nlet look at routing table for each router and see what happen . lets type show ip route on R2. Notice that the external route comes in as type N2 from R3. This is because it is a special NSSA external route

Now lets do  show ip route output on R1. Notice that the route is now a regular E2 external route, because R2 has performed the type 7 to type 5 translation and R3 no longer has a default route in it, but inter-area routes are coming in.
Note: An NSSA does not have the default route injected by the ABR (R2) automatically. It is possible to make the ABR inject the default route into the NSSA using the area 23 nssa default-information-originate command on R2