<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ill communications &#187; fail over</title>
	<atom:link href="http://illcommunications.com/tag/fail-over/feed/" rel="self" type="application/rss+xml" />
	<link>http://illcommunications.com</link>
	<description></description>
	<lastBuildDate>Wed, 08 Sep 2010 04:12:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>MPLS Redundancy solutions</title>
		<link>http://illcommunications.com/mpls-redundancy-solutions/</link>
		<comments>http://illcommunications.com/mpls-redundancy-solutions/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 03:39:57 +0000</pubDate>
		<dc:creator>Jeff Dimond</dc:creator>
				<category><![CDATA[networking]]></category>
		<category><![CDATA[broadband]]></category>
		<category><![CDATA[cheap]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[fail over]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[ipsec]]></category>
		<category><![CDATA[mpls]]></category>
		<category><![CDATA[redundancy]]></category>
		<category><![CDATA[solutions]]></category>
		<category><![CDATA[vpn]]></category>

		<guid isPermaLink="false">http://illcommunications.com/?p=125</guid>
		<description><![CDATA[A popular network solution a lot of companies who have branch offices are using is MPLS (Multiprotocol Label Switching). There are several MPLS redundancy solutions ranging from costly to cost effective. We won&#8217;t go into the technical details of setting it up, but more or less explain the solutions out there.
The ideal solution would be [...]]]></description>
			<content:encoded><![CDATA[<p>A popular network solution a lot of companies who have branch offices are using is MPLS (Multiprotocol Label Switching). There are several MPLS redundancy solutions ranging from costly to cost effective. We won&#8217;t go into the technical details of setting it up, but more or less explain the solutions out there.</p>
<p>The ideal solution would be setting up a complete MPLS network using another service provider. This is probably the most costly solution however will give you the greatest results.</p>
<p>Another solution is to have point to point connections to the branch offices. This can be costly as well depending on how many branch offices there are and what other offices they need to have connectivity to.</p>
<p>The most cost effect solution will only give marginal performance depending on the load. You can set up an IPSEC VPN between offices using your typical broadband connections (cable, DSL). I&#8217;m actually currently in the process of setting this up for a small office that needs connectivity to a main office in the event that their MPLS link goes down.</p>
<p>Automating the fail-over process for these solutions should be no different than doing it for a dedicated circuit. There are multiple ways of going about it. Dynamic routing, load balancing, and setting different metrics for the 2 different routes are a few ways to do it.</p>
<p>This was just to give you an idea of what types of solutions are out there. In a later post, I will go into detail about the equipment that can be used and some example configurations of the scenarios given the different equipment.</p>
]]></content:encoded>
			<wfw:commentRss>http://illcommunications.com/mpls-redundancy-solutions/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
