HP ProLiant BL35p Server Blade User Guide

Configuration and utilities 50
•
NFS repository server (only required for Red Hat Linux deployment)
• Red Hat Linux 7.2 OS installed
• Network connection
• CD-ROM drive
• NFS installed
• 1.5 GB of available disk space
• Windows® repository server (only required for Windows® deployment)
• Windows® 2000 or Windows® 2003 OS installed
• Network connection
• CD-ROM drive
• 1.5 GB of available disk space
• TCP/IP networking and an IP address compatible with one of the following: the iLO Diagnostic
Port IP address or an assigned DHCP or static IP address
• CD-ROM drive and/or diskette drive
• Any of the following Java™ Runtime Environment versions:
1.3.1_02
1.3.1_07
1.3.1_08
1.4.1 for Windows® users only
1.4.2 for Linux users only
Access the Java™ Runtime Environment versions at the HP website
(http://java.sun.com/products/archive/index.html
).
• Network server with an OS installed
Deployment methods
Four primary deployment methods are supported:
IMPORTANT: To deploy a server blade without the RDP, create a bootable diskette or image of a
bootable diskette.
• PXE deployment (on page 50)
• CD-ROM deployment (on page 51)
• Diskette image deployment (on page 52)
• SAN configuration (on page 53)
PXE deployment
PXE enables server blades to load an image over the network from a PXE server, and then execute it in
memory. The first NIC on the server blade is the default PXE boot NIC, but any of the other NC series
NICs can be configured to boot PXE. For more information, refer to "Network-based PXE deployment (on
page 48)."
NOTE: Actual NIC numeration depends on several factors, including the OS installed on the server blade.
HP recommends using one of the following methods for PXE deployment:
• HP ProLiant Essentials RDP ("HP ProLiant Essentials Rapid Deployment Pack" on page 51)
• SmartStart Scripting Toolkit (on page 51)