o
10-Mb/s network adapter
•
o
d
o
vailable disk space
o
orking and an IP address compatible with one of the following: the iLO 2 Diagnostic
ress or an assigned DHCP or static IP address
o
ive
o
Runtime Environment versions:
users only
sions at the HP website
(
h
o
CD-ROM drive
Windows® repository server (Windows® or Linux deployment)
Windows® 2000 or Windows Server® 2003 OS installe
o
Network connection
o
CD-ROM drive
1.5 GB of a
TCP/IP netw
Port IP add
CD-ROM drive and/or diskette dr
Any of the following Java™
1.3.1_02
1.3.1_07
1.3.1_08
1.4.1 for Windows®
1.4.2 for Linux users only
Access the Java™ Runtime Environment ver
ttp://java.sun.com/products/archive/index.html
).
ork server with an OS in
•
Netw
stalled
Deplo m
ree
ed:
y ent methods
Th
primary deployment methods are support
of a
IMPORTANT:
To deploy a server blade without the RDP, create a bootable diskette or image
bootable diskette.
•
PXE deployment (on page
36
)
•
CD-ROM deployment (on page
37
)
•
Diskette image deployment (on page
38
)
PXE deployme
t any of the other NC series
ment (on
nt
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, bu
NICs can be configured to boot PXE. For more information, refer to "Network-based PXE deploy
page
34
)."
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:
apid Deployment Pack
" on page
37
)
•
SmartStart Scripting Toolkit (on page
37
)
•
HP ProLiant Essentials RDP ("
HP ProLiant Essentials R
Software and configuration utilities 36
