You may observe a Windows Server 2008 or 2008 R2 computer configured to boot from an iSCSI target querying DHCP and having�an additional�IP address assigned to the iSCSI boot adapter. This occurs even though your server is configured using a static IP address in�the iSCSI Boot Firmware Table (iBFT) and results in two IP addresses assigned to the adapter.
↑ Back to the top
Windows Server 2008 and later does not change whether DHCP is enabled on an�adapter used in an iSCSI boot scenario.�Since Windows enables DHCP on all network adapters by default,�if the iSCSI adapter is assigned a static IP in the iBFT and there is a DHCP server configured to provide�IP addresses on the iSCSI adapters' network, the iSCSI adapter can�be assigned additional�IP addresses via DHCP.�
↑ Back to the top
Windows Server will correctly use the IP configuration from the iBFT for communications with the iSCSI target; therefore, no corrective action is required. However, if you do not want the iSCSI boot adapter to obtain an IP address from a DHCP Server, configure the adapter in Windows to not use DHCP�by using the same static IP�configuration as was used to�configure the adapter in your iBFT configuration.
↑ Back to the top
Starting in Windows Server 2008 and later,�IP�configuration from the iBFT is not considered persistent over reboots since that�iBFT configuration can be changed using the�iSCSI vendor's configuration application for the boot adapter when your Windows Server is not running.�Since the IP configuration can be changed outside of Windows Server, Windows Server ensures that it obtains your most�recent IP configuration�by reading from�the iBFT at every boot.
↑ Back to the top