| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
OSPF Hierarchical Topology, Areas and Router Roles (Page 2 of 3) Router Roles in OSPF Hierarchical Topology The topology described above is hierarchical because the routers in the AS are no longer all peers in a single group. The two-level hierarchy consists of the lower level containing individual areas, and the higher level that connects them together, which is called the backbone and is designated as Area 0. The routers are no longer all peers, but in fact play different roles depending on where they are located and how they are connected. There are three different labels applied to routers in this configuration:
Okay, I bet you are now wondering what is the point of all this? Well, the point is exactly the same as the point of using autonomous system architecture in the first place. The topology of each area matters only to the devices in that area. This means that changes in that topology only need to be propagated within the area. It also means that internal routers within Area 1 don't need to know about anything that goes on within Area 2, and don't need to maintain information about any area other than their own. Only the backbone routers (which include at least one area border router within each area) need to know the details of the entire autonomous system. These backbone routers condense information about the areas so that only a summary of each area's topology needs to be advertised on the backbone. Routing in a hierarchical topology AS is performed in one of two ways, depending on the location of the devices. If the source and destination are in the same area, then routing occurs only over networks and routers in that area. If they are in a different area, then the datagram is routed from the source to an area border router in the source's area, over the backbone to an area border router in the destination's area, and then finally, delivered to the destination. Again, this is analogous to how routing works between ASes in the big-picture internetwork.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||