I have network consists of HQ and 50 Branches .I'd like to use OSPF .the HQ will be in Area 0 .My question is that should i put each beanch in a separate area (Non Area 0) or i should put all the branches in one non area zero .
What size routers, how many routes, what size links, etc? Typically, you should be okay with all 50 spokes in a single area, unless they are really small routers, and you have a lot of routes, and you have tight convergence requirements. I would make the area you put these spokes in the "most stub possible." A totally stubby area is going to be best, but, failing that, a stubby area, or a not-so-stubby area. Reducing the information flowing between area 0 and the hub and spoke area will help keep things stable on both sides when there are major outages of any sort.
Basically to reduce the LSA advertisment is OSPF protocol is key point. so if you imeplement all the branch office in single area that will increase your LSA Advertisment in backbone. so my suggestion is to implement "Not-So-Stub area " technology this will help to reduce you LSA advertisment.
Not So Stubby Area is a very good thing if there is a need to redistirbute routes into OSPF. But I have not seen anything from the original poster that indicates a need for redistribution into OSPF. If there is no need for redistribution then I believe that Totally Stubby areas are better for the network, if I understand the network environment correctly.
I worked with a customer whose network environment was very similar to what is described: there was a HQ with 2 core routers, there were many remotes with each remote dual connected back to HQ, most remotes were in separate areas. They were running the remote areas as normal OSPF areas and were experiencing some performance issues. When they changed all the remote areas to Totally Stubby areas there was a marked improvement in the operation of their network. Given what I think I understand of the network described here I would suggest that each remote in its own area and each remote area defined as Totally Stubby is a pretty optimum way to do it.
Optimum in terms of what? There is not any single "optimum" design that fits everywhere. Each design must consider the environment of the network for which it is the design. As Russ White indicated some of the variables include what kind of routers are you running, how many routes (prefixes) on each router and how many routes in the network. You may also need to consider the convergence requirements that Russ mentioned. I believe that it is also important to consider what the traffic patterns are also (is the traffic almost always from a spoke to the hub and response, or is there significant spoke to spoke traffic?
Russ suggested that you would probably be fine in having a single area for the remote spoke routers. And I agree with that. And from the standpoint of simplicity that would be optimum. I also suggested that there would be some potential benefit in reducing the number of LSAs flooded to each remote spoke if you put each remote spoke into its own area and made all the remote areas totally stubby. From the standpoint of reducing LSA flooding this would probably be optimum.
You are the only person in this discussion that knows enough about your network environment to be able to choose which approach is the "optimum".
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...