Provisioning process for Windows and Linux
For provisioning Microsoft Windows and Linux servers, the BMC Server Automation system uses the Pre-boot Execution Environment (PXE) technology. This topic describes the phases of provisioning with PXE.
Designed to work in conjunction with established protocols like DHCP, TFTP, and TCP/IP, this PXE-based approach to provisioning allows Intel computers to boot from a PXE-compliant Network Interface Card (NIC) and retrieve their operating system installation instructions and files over the network, instead of relying on floppy disks and CD-ROMs.
Click the thumbnail below for a full-size image depicting the provisioning process for Windows and Linux.
The following numbered steps correspond to numbers in the image shown above.
- Preparation of the target machine
Prepare all necessary cabling and install a PXE-enabled NIC card in the machine to be provisioned. Configure the machine's BIOS so it boots to network first and reboot the target machine. Ensure that both the NIC and the BIOS firmware are up-to-date. - Target machine broadcasts to network
The target machine broadcasts a DHCP packet with its MAC address to the network requesting an IP address for itself and the IP address of the PXE Server. - DHCP server replies
The DHCP server replies, giving the target machine an IP address. If the DHCP server and the PXE server are running on the same physical device, the DHCP server tells the target server that it is also running the PXE server. If the DHCP server and the PXE server are running on separate physical devices, the PXE server replies to the initial broadcast, letting the target server know that it is the PXE server. - Target machine contacts PXE server
Using the supplied IP address, the target machine contacts the PXE server using either a multicast or a broadcast. - PXE server checks database
Using the MAC address of the machine, the PXE server checks a database that contains server configuration information. The database provides instructions for provisioning the server. - PXE server delivers instructions for bootstrap program
Based on information obtained from the database, the PXE server responds with DHCP scope options 43, 66, and 67 (pxe menu, next-server, and file name), instructing the target to boot either from its local disk or a boot image obtained from the TFTP server. The PXE server provides the TFTP server address and location of the boot image to the target server. Target machine runs bootstrap and connects to the Application Server
The target machine boots from the boot image and contacts the BMC Server Automation Application Server for instructions.- Application Server checks database
Using the MAC Address of the target machine, the Application Server checks its database to obtain instructions for the target machine. - Application Server delivers provisioning instructions
Based on information obtained from the database, the Application Server sends a set of provisioning instructions, called a system package, to the target machine. - Target machine requests OS files
Using the instructions from the Application Server, the target machine requests the full operating system files from an HTTP server for Linux or an SMB server for Windows. - RSCD agent is Installed
Optionally, the RSCD agent is installed, which is necessary for managing the server with BMC Server Automation. A registration event occurs to enter the target machine's information into the BMC Server Automation system so the server can be managed from the BMC Server Automation Console. - Provisioning runs Batch Job for additional configuration
Optionally, the provisioning process can run a job that performs additional provisioning of the target machine. For example, a Batch Job can install and configure all necessary applications on the target machine.