I will use the same lab in my previous post. I just changed the configuration on the Anopheles router and put the “no-summary” command.

Anopheles#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Anopheles(config)#router ospf 2
Anopheles(config-router)#area 20 nssa no-summ
Anopheles(config-router)#area 20 nssa no-summary
Anopheles(config-router)#end

Aedes(config)#router ospf 3
Aedes(config-router)#no area 20 stub
Aedes(config-router)#
Aedes(config-router)#area 20 nssa

It would be better to check the differences between NSSA and Totally NSSA using the before and after the output of the NSSA configuration.

Unlike NSSA, Totally NSSA once configured on the ABR, will automatically inject the default route to advertise Type 3 LSAs. So, there is no need to explicitly configure it. Am I repeating the same thing?

Just like what happened in the Totally Stubby Area database, Type 3 LSAs are restricted and all that is left is the Type 1 LSA, Type 7 LSA and the default route advertised by 192.168.2.1.

My posts regarding OSPF Area types are not yet done. If you will take a closer look, there are many things that I haven’t touched yet or clarified yet. Like if you check the database output, why some LSAs are missing even though it is allowed in this kind of area? This is going to be another discussion in my future posts.

According to Cisco, OSPF area is a collection of logical OSPF networks (routers and links) that have the same area identification. Depending upon the design of your network, your routers can be part of a single area or multiple areas. Why do we have to complex things and put the router in different areas? Actually, there are many reasons, and one of the many reasons is that it reduces the size of OSPF database when OSPF network is divided into different areas. Think of it this way, dividing the routers into different areas, reduces the size of the database, reduces the frequency of SPF calculation and smaller routing table. Thus, fewer requirements on router memory and CPU. I am not saying that SPF calculation is exhausting the CPU and router memory but the sending and flooding of the new topology information does.

OSPF AREA TYPES

No matter what your OSPF design in your network, all areas you have created should be connected to the backbone area. Backbone area or Area 0 (0.0.0.0) is like the meeting points of all these non-backbone areas. So, it is not just an option or recommendation but a must in every OSPF network design. Although there is an option called virtual link, it is not a good network design but just a remedy to a broken OSPF design.

Now, not all LSA Types are allowed in different areas. Some LSA Types are restricted and depend upon which area type is configured. This further reduces the link state database and routing tables. Injecting too many external routes are also memory intensive. However, all LSA types are allowed in the Normal area. An area which is not configured as Stub, Totally Stub, NSSA, NSSA Totally Stub area is called Standard/Normal Area. We can say that the backbone area is behaving like a Normal /Standard Area as LSA Type 1-5 are not being restricted in this area. When the network is divided into different area numbers (non-zero), an ABR is used to connect the Standard area to the Backbone Area.

On my next post, I will introduce some of the area types which have their own rules in restricting LSA Types.