Configuring the DHCP server

The BMC BladeLogic 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 task is required to set up a provisioning system.
This section assumes that you understand how to install and configure a DHCP server. This section, however, describes the unique configuration needed so that a DHCP server can support BMC BladeLogic Server Automation's provisioning process.
BMC BladeLogic Server Automation requires you to

  • have the TFTP server and the PXE Server reside on the same host computer
  • provide the IP address of the BMC BladeLogic Server Automation provisioning server
  • define a DHCP option field, which lets the computer being provisioned differentiate between a DHCP server and proxy DHCP servers

Note

As a best practice, BMC recommends that you not configure the next-server and boot file image names on the DHCP server. In BMC BladeLogic Server Automation provisioning, the PXE server handles booting, not the DHCP server.

The process for configuring a DHCP server differs in Windows and Linux, as described in the following tasks:

Configuring a DHCP server on Windows

This section describes how to configure the DHCP server on Windows.
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:

Adding predefined options

This section describes the procedures required to add predefined options on 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 BladeLogic Server Automation provisioning process requires the following scope options:

  • 3
  • 60
  • 211
  • 212

Use this task to add scope options 3, 211 and 212. Use Adding Option 60 to add scope option 60.

Note

  • If you are setting up a multi-database environment, do not add scope options 211 and 212. Instead, specify the IP address or host name of the Application Server as described in Configuring the PXE and TFTP servers.
  • If you are changing from a single-database environment to a multi-database environment, you must remove scope options 211 and 212 from your DHCP configuration.

To add predefined options

  1. Install DHCP, if it is not already installed.
  2. Run DHCP from the Start menu by selecting Programs => Administrative Tools => DHCP. The default server is the server where you have installed DHCP.
  3. If a scope is not already defined, right click on the server and choose New Scope. Use the wizard to define a new scope.
  4. Add options 211 and 212.
    1. Select the default server, right-click, and choose Set Predefined Options.
    2. In the Predefined Options and Values dialog box, click Add.
      The Option Type dialog box opens.

    3. Provide the following information and click OK.

    4. In the Predefined Options and Values dialog box, click Add again.

    5. Provide the following information and click OK.

    6. Click OK again.
  5. Provide values for options 211, 212 and 3:
    1. Expand the hierarchy for the default server and then expand the hierarchy for Scope.
    2. Select Scope Options, right-click, and select Configure Options.
    3. Under Available Options, scroll down and check option 211. Then, for IP address enter the IP address of the BMC BladeLogic Server Automation Application Server.
    4. Check option 212. For Port, enter 9831, which is the port that BMC BladeLogic Server Automation uses by default for SSL communication.
    5. Check option 3(Router)
      • For Server Name, type a valid router IP address. (The system administrator who configured the DHCP Server can provide this value.)
        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. (Note that you should define the correct router address, which may 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.
      • Click Resolve. The value appears in the IP Address field.
      • Click Add. Option 003 appears on the list of addresses. Then click OK.
  6. Click OK.

Adding Option 60

The section describes how to add Option 60.
If the DHCP server and the PXE Server reside on the same host computer, you must use this task to let target computers differentiate between DHCP servers and proxy DHCP servers. You do not have to perform this task if the DHCP server and the PXE Server reside on separate host computers.

To add Option 60

  1. From the command line on the DHCP server, enter netsh.
  2. Enter dhcp.
  3. Enter one of the following commands:
    • {{server
      }} servername
    • server ip_address
       Replace servername with the actual host name of the DHCP server, or ip_address. with the actual IP address.
       The command prompt changes to netsh dhcp server>.
  4. Enter the following command:
    add optiondef 60 PXEClient STRING 0 comment= userDefined
     For userDefined, substitute any comment that you want to add. This information appears in the list of scope options for the DHCP server. If your comment includes spaces, enclose the comment in quotation marks.
  5. Enter the following command:
    set optionvalue 60 STRING PXEClient
  6. To confirm the addition of the scope option, enter the following: command
    show optionvalue all
     The output is similar to the following example:
     General Option Values:
     OptionId: 60
     Option Value:
     Number of Option Elements = 1
     Option Element Type = STRING
     Option Element Value = PXEClient

Configuring a DHCP Server on Linux

This section describes how to configure the DHCP Server on Linux.
BMC BladeLogic Server Automation requires a Linux-based DHCP server to be running version 3.0p2 of the Internet Software Consortium (ISC) DHCP. The ISC provides a freely redistributable version of DHCP. Earlier versions of ISC DHCP are not compatible with BMC BladeLogic Server Automation's provisioning system.
When you configure a DHCP server on Linux, you must configure the dhcpd.conf file. In that file you enter values needed for standard configuration of a DHCP server, including 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.
In addition to all standard configuration, you must include statements that are needed for the BMC BladeLogic Server Automation provisioning process. In the following example of a dhcpd.conf file, the red-shaded text highlights entries that are required or recommended for BMC BladeLogic Server Automation provisioning:

 

In the red-shaded text shown above

  • The authoritative statement is required with the ISC DHCP server configuration.
     BMC BladeLogic Server Automation requires that the DHCP server responding to inquiries for the subnet be authoritative.
  • The option routers statement defines an IP address for the router. (The option routers value shown above is an example; you should define the correct router address.)
     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. (Note that you should define the correct router address, which may 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.
  • The option vendor-class-identifier statement is necessary if the DHCP server and the PXE Server reside on the same host computer.
     This statement lets target computers differentiate between the DHCP server and proxy DHCP servers. Do not include this statement in the dhcpd.conf file if the DHCP server and the PXE Server reside on separate host computers.
  • The option bl-server statement defines an IP address for option 211.
     The IP address is the IP address of the BMC BladeLogic Server Automation Application Server.

  • The option bl-port statement defines a port number for option 212
    You should generally enter a value of 9831, which is the port that the BMC BladeLogic Server Automation Application Server uses by default for SSL communication.

    Note

    If you are setting up a multi-database environment, do not add the statements for options 211 and 212. Instead, specify the IP address or host name of the Application Server as described in Configuring the PXE and TFTP servers. If you are changing from a single-database environment to a multi-database environment, you must remove the statements for options 211 and 212 from dhcpd.conf.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*