[AusNOG] VPLS OSPF question

Steve Lisson SteveL at dedicatedservers.net.au
Wed Apr 17 01:28:34 EST 2013


Along with RR's, would be the option of using confederation, private AS's or a combination of all three (if some major Pop's on the network can see advantages of either using confederation or private AS numbers over just using RR's across the entire network to separate out the local IGP (e.g. OSPF) domains & can then use RR's within those as well if full-mesh isn't desired or practical).

Having said that, it would really depend on the topology, if the core is just one big broadcast domain & there being no or few redundant/alternative paths that traffic can take any of the above would be overkill and then using a number (that number is up to you) of strategically placed RR's under the one AS to give all sites the correct next-hop address is probably the best option, OSPF would have significantly higher overhead than BGP in this instance.

If looking to expand/improve your BGP network have found the book 'BGP Design and Implementation' from Cisco Press to be very useful.

From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Tony
Sent: Tuesday, 16 April 2013 10:13 PM
To: Brad McGinn; ausnog at lists.ausnog.net
Subject: Re: [AusNOG] VPLS OSPF question

Hi Brad,

A bit of a "it depends" kind of question.

Do you have a VPLS setup right now, or moving towards one and wondering how to route across it ? You mention that you've currently got OSPF in your DC and the BGP into an MPLS network. Is the MPLS network provided by an SP, or you're doing that yourself ? If you're moving to VPLS, what are you hoping to gain ?

As someone else said, if using BGP you would want to have an RR setup, otherwise you need to create a full mesh (ie. each of your 200 sites would need 199 BGP sessions configured to each of the other routers -> disaster !). You'll also probably need two RR's for redundancy.

On the topic of large OSPF deployments, if you satisfy the following conditions:
- your links are reasonably stable
- you have a decent amount of bandwidth on all links
- the total number of routes is small
- routers are newish

then you would probably be able to run OSPF across 200 routers.

Taking each point in turn, the stability of links reflects how often each router will be running an OSPF calculation. One link flapping causes ALL routers to run an SPF calculation. If you have a continually flapping link this can cause issues. Bandwidth is important due to the amount of hello's and the size of the routing DB that will be transferred around on any link change. The number of routes and the number of routers are inversely related. If you have a massive number of routes being advertised then you would want a smaller number of routers in each area. If you're only advertising a single prefix from each of your 200 sites (eg. single /24) then that is the best possible option for scaling the size of OSPF. Decent router hardware today can handle a lot more OSPF routers in an area than when OSPF was first designed and the suggestion then was for a max of 30-50 routers per area due to HW limitations. CPU is used for running the OSPF algorithms, RAM is used to hold OSPF DB, you'll need sufficient of each in all routers as each router will be doing exactly the same thing (OSPF-wise anyway).

"Current ISP experience and Cisco testing suggest that it is unwise to have more than about 300 routers in OSPF backbone area 0, depending on all the other complexity factors that have been discussed. As mentioned in the preceding note, 50 or fewer routers is the most optimal design."

( http://www.ciscopress.com/articles/article.asp?p=1763921&seqNum=6)

Breaking it up into smaller areas is probably the best idea to run OSPF. Without any knowledge of where your 200 sites are can you break it up into something like state based areas, or possibly business units ?


regards,
Tony.

________________________________
From: Brad McGinn <the_xorach at yahoo.com<mailto:the_xorach at yahoo.com>>
To: "ausnog at lists.ausnog.net<mailto:ausnog at lists.ausnog.net>" <ausnog at lists.ausnog.net<mailto:ausnog at lists.ausnog.net>>
Sent: Tuesday, 16 April 2013 5:14 PM
Subject: [AusNOG] VPLS OSPF question


Hi AusNog list,

Long time listener, first or second time caller.

I know this list is pretty specific to Service Providers so I'm hoping any of you who not only know carrier networks, but also have an insight into enterprise networks maybe able to help me to get a view (or even help understanding) of the pros and cons of running OSPF or BGP across a VPLS network.

I respectfully ask your advice.

I am an enterprise network engineer, not a service provider however I hope you don't hold that against me.  We run OSPF in our Data Centre and BGP into a MPLS network that all of our sites connect into.

My fairly basic understanding of VPLS is kind of like EoMPLS or even one big broadcast domain.  I assume any IGP could potentially work across it but some factors must be taken into consideration:  eg flapping sites, latency, reference bandwidth, DR/BDR placement, multicast transmission and so on.

So, with that in mind, I'm wondering the following:
-    would it be wise to run an IGP across a VPLS backbone with over 200 sites? or would BGP be better? or even something else?
-    if an IGP is the go, would one use OSPF?
-    if OSPF, do you think it would be wiser to run a separate OSPF process for the VPLS connected sites and a separate OSPF process for the DC?  and then redistribute or just summarise right there? (so as to protect the DC from OSPF recalculations when sites go up and down)
-    if BGP would be the go I'm wondering how one might go about it..  I know that all iBGP neighbours must have a route to the peering IP of all other iBGP routers so I would assume an IGP must be run anyway???
-    cisco say that anything more than 50 routers on an area is a bad idea, so if I have over 200 sites potentially on the VPLS, will OSPF cut it?

I guess i'm just trying to get my head around the different technology.  I'd love to keep the stability that BGP brings, but also would like to be able to make use of the bandwidth that VPLS gives.

Any hints or tips will be gratefully received and thank you for any help.  If you would like to keep from cluttering up subscriber's inboxes, please reply offlist.

Again, thanks for any help.

Regards,

Brad David

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20130416/0768eba0/attachment.html>


More information about the AusNOG mailing list