Windows Server, DHCP failover

Today our topic is a new feature in Windows Server 2012, DHCP failover, DHCP is not too much to introduce this is a very basic knowledge, DHCP in Windows Server 2012 In fact there are three major new features, namely:

DHCP Fail-Over

Policy-based allocation

PowerShell for DHCP

In Windows server R2, two high-availability options are available for DHCP server deployment. Each of these options is related to a number of questions.

DHCP in Windows failover cluster . This option places the DHCP server in a cluster that has an additional server that is configured by the DHCP service to assume the load when the primary DHCP server fails. The clustering deployment option uses a separate shared storage. This makes the memory a single point of failure and requires additional investment in memory redundancy. In addition, the cluster involves relatively complex setup and maintenance.

splitting the scope of DHCP . Split-scope DHCP uses two separate DHCP servers to share responsibility for scopes. Typically 70% of the addresses in the scope are assigned to the primary server, and the remaining 30% is assigned to the backup server. If clients cannot reach the primary server, they can obtain an IP configuration from the secondary server. Split-scope deployments do not provide IP address continuity and are not available in scenarios where the scope is already running in an efficient way to utilize the address space. This scenario is common in Internet Protocol version 4 (IPV4).

DHCP failover protects us from the task of assigning IP addresses to another DHCP server after a DHCP outage, and the assigned IP address remains the same network segment, because the DHCP failover itself is set up with an IP address segment for the object. To configure DHCP failover is simple, here's an introduction to the experimental environment

Server:	IP Address	Role
DC01	192.168.0.1	DC, DHCP, DNS
DC02	192.168.0.2	DC, DHCP, DNS

In this experiment, DC01 has a DHCP scope, but only the DHCP role is installed in DC02 and the scope is not configured, and we now want to synchronize the scope of the DC01 to DC02 through the DHCP failover feature.

1) First in DC01, right click on IPv4, select Configure failover

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/3F/9C/wKiom1PLYhaxKwSsAAIPApnkW5w544.jpg "style=" float: none; "title=" Image 1.png "alt=" Wkiom1plyhaxkwssaaipapnkw5w544.jpg "/>

2) The scope of the available scopes is listed here, and I've simply configured a 192.168.0.0 network segment because of the experimental environmental relationship.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/3F/9C/wKioL1PLYzHC5ax5AAKFsEZmjWU160.jpg "style=" float: none; "title=" Image 2.png "alt=" Wkiol1plyzhc5ax5aakfsezmjwu160.jpg "/>

3) Select Add Server

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/3F/9C/wKiom1PLYheyX6PlAAGuQG89QHg659.jpg "style=" float: none; "title=" Image 3.png "alt=" Wkiom1plyheyx6plaaguqg89qhg659.jpg "/>

4) Here we select the DC02 server, which is the target server where we set up the failover

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/3F/9C/wKioL1PLYzHwxGFJAAH98t6kPDs419.jpg "style=" float: none; "title=" Image 4.png "alt=" Wkiol1plyzhwxgfjaah98t6kpds419.jpg "/>

5) Next

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/3F/9C/wKiom1PLYhfDx8Z1AAG41i8QDfs627.jpg "style=" float: none; "title=" Image 5.png "alt=" Wkiom1plyhfdx8z1aag41i8qdfs627.jpg "/>

6) Create a new failover relationship where you can set the percentage of failover

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/3F/9C/wKiom1PLYhfTAEs0AAG5kYYQNNQ904.jpg "style=" float: none; "title=" Image 6.png "alt=" Wkiom1plyhftaes0aag5kyyqnnq904.jpg "/>

7) After the configuration is complete in DC02 this server we can already see the scope of the DC01 just now

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/3F/9C/wKioL1PLYzKAn2K0AAH6EchZCYs600.jpg "style=" float: none; "title=" Image 7.png "alt=" Wkiol1plyzkan2k0aah6echzcys600.jpg "/>

This article is from the IT Technology sharing blog, so be sure to keep this source http://mxyit.blog.51cto.com/4308871/1440504

Windows Server, DHCP failover