The BMC Server Automation provisioning process requires a DHCP server, which gives the computer being provisioned an IP address and (in a single-database environment) the location of the Application Server. This topic provides instructions for configuring the DHCP server on Microsoft Windows platforms.
In addition to standard configuration of the DHCP server, which includes defining a scope, you must set some scope options. Use the following tasks to configure the DHCP server on Windows:
This topic provides instructions for adding predefined options on Microsoft Windows.
A standard DHCP configuration should include the definition of a scope, which sets a start and end of the range of IP addresses being distributed. This range determines the number of servers that can simultaneously access the DHCP server.
The BMC Server Automation provisioning process requires the following scope options:
In the Option Type dialog box, provide the following information and click OK.
Select IP Address.
Provide the following information and click OK.
Provide values for options 211, 212, and 3:
If you need to direct a PXE client such as a Citrix Xen guest VM to the PXE boot file, add also options 66 and 67. Use option 66 to specify the boot server host name and option 67 to specify the boot file name. The data type for both options is String.
9831, which is the default port that BMC Server Automation uses for SSL communication.
For Server Name, type a valid router IP address. (The system administrator who configured the DHCP server can provide this value.) Then click Resolve. The value appears in the IP Address field.
If you do not have a valid router IP address — for example, if you are provisioning in a local LAN — you can use a router IP address that is not real, for example, x.x.x.1. (You should define the correct router address, which might not align with the .1 host ID.) In the case of provisioning in a local LAN, the value can be any valid IP address within the subnet (or subnet mask) that is not in the range of IP addresses to be distributed by the DHCP server.
If the DHCP server and the PXE server reside on the same host computer, you must add option 60 to let target computers differentiate between DHCP servers and proxy DHCP servers. If the DHCP server and the PXE Server reside on separate host computers, you do not have to perform this task.
netsh. (This command runs the Microsoft Windows network shell.)
netsh dhcp server>.
add optiondef 60 PXEClient STRING 0 comment=<userDefined>
set optionvalue 60 STRING PXEClient
To confirm the addition of the scope option, enter the following command:
show optionvalue all
The output is similar to the following example:
When finished, restart the DHCP server.