cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1062
Views
5
Helpful
3
Replies

OSPF - Layer 3 to Access design

Alex Willoughby
Level 1
Level 1

Hi all,

Im after some second opinions on our OSPF area design...

Brief:

The access layer switches may have one or fice 3650s in a stack
Each DIST is a pair of 4500-Xs in VSS
An access switch will be connected to one of the two switches in each pair

OPT 1 - an area per stack with the both DIST in area 0 along with the core

OPT 2 - all DIST and access in area 1

Looking at best practice docs, i believe Cisco would recommend option 2? but that to me makes a busy area 1? thoughts?

Thanks

3 Replies 3

Ganesh Hariharan
VIP Alumni
VIP Alumni

Hi,

Normal OSPF deign best practice recommends that you should consider the following,

Below are some highlted recommended and there a lot based on your design...:)

Summarizing intra-area routes is recommended in most cases.

•If an area has multiple ABRs, then the summarization for the same range of routes should be configured on all the ABRs in the area.

•Since summarization for the same range of addresses on multiple ABRs in some topologies (typically hub and spoke topologies) can, in some    situations, cause  routing black holes it is generally best to have at least one link between two ABRs summarizing the same address space within the  non-backbone area.

•Make sure that the ‘null 0’ route (discard route) is installed for the summarized address ranges to avoid routing loops in some scenarios.

•It is preferable to set manually the cost of the summary route, or use a loopback interface in the summarized IP address range to prevent the  summary cost  from changing due to network changes within the area.

•Having more than one ABR for areas is recommended for redundancy.

•Summarize externally learned routes at the redistribution point (ASBR) to reduce the external LSAs where possible, since external LSAs are flooded  throughout the OSPF domain.

•Avoid configuring redistribute connected under the OSPF routing process. Instead, use the network statement under OSPF process and mark those  interfaces as passive.

•If redistribution is required, limit it to as fewer routers as possible.

•Where Possible, Avoid mutual redistribution at multiple points

•Configure administrative distance in such a way that each prefix native to each protocol or process is reached via the corresponding domain’s protocol  or process.

•Control the prefixes (using distance or/and prefix-list  / tag combination) in a way that the same prefix is not advertised back to the originating  domain.

Hope it Helps..

-GI

thanks, ive read these best practice a few times, they dont really cover area design (im still reading other sources) its the area design im trying to work out at the moment.

Thanks

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

For OSPF area design, first you keep in mind it's for OSPF scalability.  An (very) old rule of thumb, was no more than about 50 routers per OSPF area.  However, how many routers can be safely used within an OSPF area depends on many factors, and today even a couple of hundred routers within an OSPF area might be okay.

How may routers will there be in your topology?

BTW, you mention you're using VSS.  If you're using L3 to the edge, why VSS?

Review Cisco Networking products for a $25 gift card