<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Maximum theoretical downtime for a website: 30 minutes</title>
	<atom:link href="http://visualwebsiteoptimizer.com/split-testing-blog/maximum-theoretical-downtime-for-a-website-30-minutes/feed/" rel="self" type="application/rss+xml" />
	<link>http://visualwebsiteoptimizer.com/split-testing-blog/maximum-theoretical-downtime-for-a-website-30-minutes/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 10 Feb 2012 10:32:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Service Desk</title>
		<link>http://visualwebsiteoptimizer.com/split-testing-blog/maximum-theoretical-downtime-for-a-website-30-minutes/comment-page-1/#comment-713</link>
		<dc:creator>Service Desk</dc:creator>
		<pubDate>Fri, 23 Jul 2010 06:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://visualwebsiteoptimizer.com/split-testing-blog/?p=503#comment-713</guid>
		<description>Thanks for posting this, I better show this to my system admin so we can also study our website and network.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this, I better show this to my system admin so we can also study our website and network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Reifschneider</title>
		<link>http://visualwebsiteoptimizer.com/split-testing-blog/maximum-theoretical-downtime-for-a-website-30-minutes/comment-page-1/#comment-537</link>
		<dc:creator>Sean Reifschneider</dc:creator>
		<pubDate>Tue, 22 Jun 2010 19:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://visualwebsiteoptimizer.com/split-testing-blog/?p=503#comment-537</guid>
		<description>At tummy.com, we do a lot of Linux high-availability work.  To answer your question about whether the two servers in an IP fail-over situation need to be on the same switch: No, they don&#039;t.

IP fail-over typically is done via sending a gratuitous ARP out when the IP change is done, so that things on that segment get the new MAC address for the IP.  The MAC on each system stays the same, so a layer-2 switch doesn&#039;t see any change -- each  machine&#039;s MAC stays on the same interface as before.

It&#039;s the equipment on that segment (most importantly, usually, the router) that notice the change.  They get the gratuitous ARP message and update their ARP tables, and start sending the traffic for that IP to the new MAC address.

Once you start thinking about what is happening at the MAC level to pass packets around a local network segment, this all becomes pretty clear.

Sean</description>
		<content:encoded><![CDATA[<p>At tummy.com, we do a lot of Linux high-availability work.  To answer your question about whether the two servers in an IP fail-over situation need to be on the same switch: No, they don&#8217;t.</p>
<p>IP fail-over typically is done via sending a gratuitous ARP out when the IP change is done, so that things on that segment get the new MAC address for the IP.  The MAC on each system stays the same, so a layer-2 switch doesn&#8217;t see any change &#8212; each  machine&#8217;s MAC stays on the same interface as before.</p>
<p>It&#8217;s the equipment on that segment (most importantly, usually, the router) that notice the change.  They get the gratuitous ARP message and update their ARP tables, and start sending the traffic for that IP to the new MAC address.</p>
<p>Once you start thinking about what is happening at the MAC level to pass packets around a local network segment, this all becomes pretty clear.</p>
<p>Sean</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.035 seconds -->

