Hi.
We have 2 servers running Windows Server 2012, with DHCP role , and many scopes added in Failover Cluster.Cluster is configured in Hot Standby mode for fault tolerance, StateSwitchInterval set to 1 min, MaxClientLeadTime for 2 min, ReservePercent - 0%. These values were chosen for quick capture all scopes by the second server and most painless and transparently move between servers.Percentage of addresses reserved for the second server left zero because we have many scopes and they degree of congestion are different and sometimes they have very little free addresses. The problem actually lies in the fact that when the first server is down - the second takes control over thescopes in (StateSwitchInterval + MaxClientLeadTime = 3 min.) And gives an address lease time MaxClientLeadTime equal to 2 minutes - which is very little, if these customers are every 2 minutes request an extension of the lease term will be about 1000 I think the server does not survive, the parameter MaxClientLeadTime we can not increase because it is tied to the capture time of the second server.
Perhaps you have any ideas how to get out of this situation?Is there a possibility to change the parameter MaxClientLeadTime on the second server when the first server is unavailable.
Thanks in advance.
We have 2 servers running Windows Server 2012, with DHCP role , and many scopes added in Failover Cluster.Cluster is configured in Hot Standby mode for fault tolerance, StateSwitchInterval set to 1 min, MaxClientLeadTime for 2 min, ReservePercent - 0%. These values were chosen for quick capture all scopes by the second server and most painless and transparently move between servers.Percentage of addresses reserved for the second server left zero because we have many scopes and they degree of congestion are different and sometimes they have very little free addresses. The problem actually lies in the fact that when the first server is down - the second takes control over thescopes in (StateSwitchInterval + MaxClientLeadTime = 3 min.) And gives an address lease time MaxClientLeadTime equal to 2 minutes - which is very little, if these customers are every 2 minutes request an extension of the lease term will be about 1000 I think the server does not survive, the parameter MaxClientLeadTime we can not increase because it is tied to the capture time of the second server.
Perhaps you have any ideas how to get out of this situation?Is there a possibility to change the parameter MaxClientLeadTime on the second server when the first server is unavailable.
Thanks in advance.