Network-based pxe deployment, Deployment overview – HP ProLiant BL25p G2 Server-Blade User Manual
Page 39
Configuration and utilities 39
•
Remotely boot a host server blade to a virtual diskette image to perform a ROM upgrade or install
an OS.
•
Send alerts from iLO 2 Advanced regardless of the state of the host server blade.
•
Access advanced troubleshooting features provided by iLO 2 Advanced.
•
Launch a web browser, use SNMP alerting, and diagnose the server blade with HP SIM.
•
Configure static IP bay settings for the dedicated iLO 2 management NICs on each server blade in
an enclosure for faster deployment.
The server blade must be properly cabled for iLO 2 connectivity. Connect to the server blade with one of
the following methods:
•
Through an existing network (in the rack)—This method requires you to install the server blade in its
enclosure and assign it an IP address manually or using DHCP.
•
Through the server blade I/O port
•
In the rack—This method requires you to connect the local I/O cable to the I/O port and a client
PC. Using the static IP address listed on the I/O cable label and the initial access information on
the front of the server blade, you can access the server blade with the iLO 2 Advanced Remote
Console.
•
Out of the rack, with the diagnostic station—This method requires you to power the server blade
with the optional diagnostic station and connect to an external computer using the static IP
address and the local I/O cable. For cabling instructions, refer to the documentation that ships
with the diagnostic station or to the Documentation CD.
•
Through the server blade rear panel connectors (out of the rack, with the diagnostic station)—This
method enables you to configure a server blade out of the rack by powering the server blade
with the diagnostic station and connecting to an existing network through a hub. The IP address
is assigned by a DHCP server on a network.
The p-Class tab enables you to control specific settings for the HP BladeSystem. iLO 2 also provides web-
based status for the HP BladeSystem configuration.
For detailed information about iLO 2 Advanced, refer to the HP Integrated Lights-Out User Guide on the
HP website (
Network-based PXE deployment
PXE is a component of the Intel® WfM specification. The PXE model enables server blades to load and
execute an NBP from a PXE server and to execute a pre-configured image. The image can be an OS
image created by software utilities or a boot diskette image. This feature enables a user to configure a
server blade and install an OS over a network.
Deployment overview
When a PXE-enabled client boots, it obtains an IP address from a DHCP server. The client obtains the
name of the NBP from the appropriate boot server. Then, the client uses TFTP to download the NBP from
the boot server and executes the image.
For each server blade being deployed, the PXE server must be connected to the NIC designated for PXE.
The server blade defaults PXE functions to NIC 1, but any of the two NC series NICs can be designated
for PXE in RBSU. For NIC connector locations on RJ-45 patch panels and interconnect switches, refer to
the documentation included with the server blade.
NOTE: Actual NIC numeration depends on several factors, including the OS installed on the server blade.
To deploy an OS to multiple server blades, install a PXE deployment server on a network.