Redundant Data Center Internet Connectivity – Problem Overview

During one of my ExpertExpress consulting engagements I encountered an interesting challenge:

We have a network with two data centers (connected with a DCI link). How could we ensure the applications in a data center stay reachable even if all local Internet links fail?

On the face of it, the problem seems trivial; after all, you already have the DCI link in place, so what’s the big deal ... but we quickly figured out the problem is trickier than it seems.

In the following short video I’m trying to explain what the problem is, and what a potential solution might look like. You'll find more details here.

Related blog posts

Todd Hoff wrote a great in-depth commentary of this video that you absolutely have to read.

And here are a few other relevant blog posts:

Related webinars

5 comments:

  1. What about TCP timeout ? According to the proposed design, if Internet fails at DC1, DC2 will route back to DC1 using the same firewalls.

    If you had TCP timeout issues before, you'll still have issues during the Internet fails scenario.


    I challenge the need of dual Internet connectivity per DC added by non-stretch firewalls (I have read the article of stretch firewalls).

    The 2 Internet links failure should be as rarely as the 2 routers failure. And If the 2 routers fails, the stretch firewalls is the solution.

    In the proposed design, I would still use the WAN backbone for private and public networks and achieve something close to load balance (lets leverage Load Balancers here ?) the traffic between both Internet link located in each DC with the use of a "stretch clustering Firewall"

    ReplyDelete
    Replies
    1. If your firewalls cause TCP timeout issues, you might want to replace them. Also, you'll only catch that problem (automatically) if it's a systemic problem affecting all sessions AND you run BGP _across_ the firewall.

      As for "links fail as rarely as routers", I can only refer you to Section 2.4 of RFC 1925. You might also want to consider that a link usually traverses more than one device ;), not to mention the potential impact of "cable finders" (aka backhoes).

      See also http://blog.ioshints.info/2012/10/if-something-can-fail-it-will.html

      Delete
  2. You pretty much described the way I'd do it, but although you mentioned "these may be dark fibre" you missed offering DWDM as the separation (and seiously, if you're only running 10g on dark fibre you're wasting money)

    ReplyDelete
    Replies
    1. Absolutely agree, thanks for the feedback!

      However, you do have to run pretty big data centers to need a dedicated "outside" link. In that case, it might be better to go for full-blown ISP design and do optimal IBGP routing on the outside as well.

      Delete
  3. Great presentation. Very clear explanation of design decisions.

    ReplyDelete

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

Ivan Pepelnjak, CCIE#1354, is the chief technology advisor for NIL Data Communications. He has been designing and implementing large-scale data communications networks as well as teaching and writing books about advanced technologies since 1990. See his full profile, contact him or follow @ioshints on Twitter.