Configuring the PXE and TFTP servers

You can configure or re-configure the PXE and TFTP servers using the PXE/TFTP Server Configuration tool.
With this tool, you can:

• Set or change database connection parameters for the PXE/TFTP server.
• Configure the PXE server.
• Configure the TFTP server.
• Configure the PXE server for a multiple database provisioning environment.
• Run diagnostic tests that check the PXE/TFTP server configurations.

Before you begin

• Network Shell must be installed on the same host computer as the PXE server. See the following tasks:

• The PXE server and TFTP server must be installed. See the following tasks:

• The DHCP server must be installed and configured.
• The TFTP server must be configured. See Setting up the TFTP Server.

To configure the PXE and TFTP servers

1. Start the PXE/TFTP Server Configuration tool by performing one of the following actions:
   • (Windows) At the end of the PXE installation, on the PXE Server Setup panel, check Configure the PXE server.
   • From the Windows Start menu, select Programs => BMC Software*=> BladeLogic Server Automation Suite => PXE Configuration tool*.
   • Start the tool manually. From the directory where the PXE server is installed, run the blpxeconf script:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
     
2. On the Database panel, review the database connection parameters set during PXE server installation and edit them if necessary. To specify information, perform one of the following actions:
   • If you are not providing a custom connection string, provide information for all fields except Advanced.

   • To provide parameters in a custom connection string, provide information for: User ID, Password, and Advanced.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
     

     The following example shows a typical Oracle RAC connection string: 

     
     jdbc:oracle:thin@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)
     (HOST = oraracdb1-vip.ora1.bmc.com)(PORT = 1521))
     (ADDRESS = (PROTOCOL = TCP) (HOST = oraracdb2-vip.ora1.bmc.com)
     (PORT = 1521)) (LOAD_BALANCE = yes)
     (CONNECT_DATA = (SERVER = DEDICATED)
     (SERVICE_NAME = oraracsrv)(FAILOVER_MODE = (TYPE = SELECT)
     (METHOD = BASIC)(RETRIES = 180) (DELAY = 1000))))
     
3. For PXE Options, provide the information listed in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
4. For TFTP Options, provide the information listed in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
5. ( optional ) Configure the PXE server for a multiple-database provisioning environment. Use both the PXE MAS Options and the PXE MAS Data Source tabs. (For information, see Setting up a multiple database provisioning environment.)
6. ( optional ) On the Diagnostics tab, click Run to check configuration parameters on the PXE and TFTP servers.
    The tests check:
   • Database connectivity
   • PXE parameters, such as interface to bind, listening port, and TFTP server address.
   • TFTP parameters, such as tftp root. In addition, the TFTP test checks whether the TFTP server can bind to its port.
   • Whether the DHCP server is already running. (A running DHCP server can be a problem because it keeps the PXE server from binding to bootp.)
   • PXE Multiple Application Server (MAS) configuration --The test checks to see if DHCP scope options are present.
      The Diagnostics Log displays test results and status messages. Test results show the status of the servers, as well as configuration problems and suggested solutions.
      The diagnostics tests also generate a log file: installationDirectory/PXE/br/PxeDiag.log

Where to go from here

1. Set up the TFTP server. See Setting up the TFTP Server.
2. Set up data stores.
    In Windows installations, you have the option to set up a data store on the same host computer as the PXE Server. In this case, you only need to set up the account used to access the data store. However, you can set up multiple data stores on other Windows or Linux servers. For more information, see Setting up a data store.
3. Stock the data store.
    The data store holds all operating system installation files needed for provisioning, as well as Windows plug-and-play drivers and BMC BladeLogic Server Automation RSCD agents. For more information, see Stocking the data store.
4. Set up all necessary agent installations and add them to the data store.
    The BMC BladeLogic Server Automation provisioning process installs an agent on all servers so that they can be managed with BMC BladeLogic Server Automation. For more information, see Preparing agents for provisioning.
5. Create boot image files.
    BMC BladeLogic Server Automation uses Windows PE and Gentoo Linux as boot environments for bare metal provisioning.
   • If you are provisioning Windows computers, use WinPE.
   • If you are provisioning Linux computers, use Gentoo Linux.
      Regardless of your target environment, you must create appropriate bootable image files. For information, see the BMC BladeLogic Server Automation User Guide.
6. (optional) Set up a multi-database provisioning environment.
    In a large, distributed provisioning environment, you may find it more efficient to use multiple Application Servers accessing multiple databases. For information on how to do this, see Setting up a multiple database provisioning environment.