<?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>Net Data Design, LLC Blog &#187; routing</title>
	<atom:link href="http://blog.nddllc.com/tag/routing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nddllc.com</link>
	<description>Software and Database Development Blog</description>
	<lastBuildDate>Fri, 20 Aug 2010 16:33:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
		<item>
		<title>When ISPs lose your Peering</title>
		<link>http://blog.nddllc.com/2009/10/20/when-isps-lose-your-peering/</link>
		<comments>http://blog.nddllc.com/2009/10/20/when-isps-lose-your-peering/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 22:36:59 +0000</pubDate>
		<dc:creator>Chris Smith</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[fiewall]]></category>
		<category><![CDATA[ISP]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[routing]]></category>

		<guid isPermaLink="false">http://blog.nddllc.com/?p=13</guid>
		<description><![CDATA[We had a freak occurrence this morning. One of our ISP was doing some network maintenance, and this normally does not cause an issue in our case. However, somewhere during the network &#8220;upgrade&#8221; some routing policies and peering agreements information was lost. That&#8217;s the bad news. Worse than that, we called tech support after the [...]]]></description>
			<content:encoded><![CDATA[<p>We had a freak occurrence this morning. One of our ISP was doing some network maintenance, and this normally does not cause an issue in our case. However, somewhere during the network &#8220;upgrade&#8221; some routing policies and peering agreements information was lost.</p>
<p>That&#8217;s the bad news. Worse than that, we called tech support after the outage went longer than we where told it would, they informed us that our firewall or gateway was misconfiguration. Now, I can attest to some pretty strange occurances, but a switch or firewall reconfigured by itself, is a little much to swallow.</p>
<p>Good news is the issue was identified by their NOC and corrected with 2 hours. The lesson learned is to never take routine maintenance for granted. Be vigilant in keeping backup images of all network equipment, just in case.</p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save"><img src="http://blog.nddllc.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://blog.nddllc.com/2009/10/20/when-isps-lose-your-peering/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
