<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>DHCP Failover Load Balance Mode</title><link>http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx</link><description>As described in the blog on DHCP failover , there are two types of DHCP Failover relations &amp;ndash; Load Balance which provides Active-Active configuration and Hot Standby which provides Active-Passive configuration. This blog article elaborates on the</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: DHCP Failover Load Balance Mode</title><link>http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx#3568214</link><pubDate>Mon, 22 Apr 2013 10:14:04 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3568214</guid><dc:creator>teamdhcp</dc:creator><description>&lt;p&gt;When a client sends a request for a new lease, it will get lease for MCLT duration. When the client attempts to renew the lease at half the lease period i.e. MCLT/2, it will be given the scope lease duration if DHCP failover is in NORMAL state.&lt;/p&gt;
&lt;p&gt;This is as per the DHCP failover protocol. This does increase the traffic from new clients but given the scalability of Windows DHCP server, this should not pose any deployment problem.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3568214" width="1" height="1"&gt;</description></item><item><title>re: DHCP Failover Load Balance Mode</title><link>http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx#3568157</link><pubDate>Mon, 22 Apr 2013 03:28:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3568157</guid><dc:creator>Hi, teamdhcp</dc:creator><description>&lt;p&gt;I got a question here.&lt;/p&gt;
&lt;p&gt;If the failover pair stay in Normal status, which lease time will the client obtain? MCLT or the time defined in the Scope configuration.&lt;/p&gt;
&lt;p&gt;My test result is MCLT, I think it is unreasonable as it double the request traffic of DHCP.&lt;/p&gt;
&lt;p&gt;According most of document of failover, MCLT should and ONLY be actived when failover enter COMMUITCATE-INTERRPUT or PARTER-DOWN status.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m confused. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3568157" width="1" height="1"&gt;</description></item><item><title>re: DHCP Failover Load Balance Mode</title><link>http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx#3520707</link><pubDate>Tue, 18 Sep 2012 05:11:09 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3520707</guid><dc:creator>teamdhcp</dc:creator><description>&lt;p&gt;Joe, yes, client 1 will get the same IP address again. There are two cases possible -&lt;/p&gt;
&lt;p&gt;1. DHCP 1 synced the IP address 10.2.3.4 to DHCP2 before it went down.&lt;/p&gt;
&lt;p&gt;In this case, the client will given the full lease duration which has been configured for the scope.&lt;/p&gt;
&lt;p&gt;2. DHCP 1 went down before syncing the IP address 10.2.3.4 to DHCP2&lt;/p&gt;
&lt;p&gt;In this case also, the client will be able to renew but the lease duration will be shorter - same as the value configured for MCLT.&lt;/p&gt;
&lt;p&gt;There is another client behavior to be aware of here - at half the lease period, the client will attempt to renew the lease. This is just normal DHCP client behavior as per the DHCP protocol. The renew message is unicast. So in the scenario above, it will be directed to DHCP 1 which is down and so there will be no response. At 7/8th of the lease period, the client will broadcast the renew request message. This message will be seen by DHCP2 which will respond to the renew request.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3520707" width="1" height="1"&gt;</description></item><item><title>re: DHCP Failover Load Balance Mode</title><link>http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx#3520595</link><pubDate>Mon, 17 Sep 2012 16:12:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3520595</guid><dc:creator>Joe</dc:creator><description>&lt;p&gt;Question:&lt;/p&gt;
&lt;p&gt;If client1 gets an IP address of 10.2.3.4 from DHCP1 and then DHCP1 goes down but is in a load balance failover pair with DHCP2 and client1 does a renew - will client1 get the same IP address again?&lt;/p&gt;
&lt;p&gt;In other words - Does DHCP2 have IP to MAC address mapping for both pairs in the load balance?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3520595" width="1" height="1"&gt;</description></item><item><title>re: DHCP Failover Load Balance Mode</title><link>http://blogs.technet.com/b/teamdhcp/archive/2012/08/06/dhcp-failover-load-balancing-mode.aspx#3512880</link><pubDate>Tue, 07 Aug 2012 05:54:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3512880</guid><dc:creator>Web blog of Janine Patterson</dc:creator><description>&lt;p&gt;I was looking through some of your blog posts on this site and I believe this web site is really informative! Keep on putting up.This site is really helpful for us.&lt;/p&gt;
&lt;p&gt; &lt;a rel="nofollow" target="_new" href="http://janinepatterson.com/"&gt;http://janinepatterson.com/&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3512880" width="1" height="1"&gt;</description></item></channel></rss>