Static ip bay configuration, Deployment methods, Pxe deployment – HP ProLiant BL20p G4 Server-Blade User Manual

Page 40

Advertising
background image

Configuration and utilities 40

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

Static IP bay configuration

Static IP bay configuration, implemented using the new Static IP Bay Settings on the BL p-Class tab, eases

the initial deployment of an entire enclosure or the subsequent deployment of blades within an existing

enclosure. While the preferred method for assigning IP addresses the iLO 2 to each blade is through

DHCP and DNS, these protocols are not always available on non-production networks.
Static IP bay configuration automates the first step of BL p-Class blade deployment by enabling the iLO 2

management processor in each blade slot to obtain a predefined IP address without relying on DHCP. iLO

2 is immediately accessible for server deployment using Virtual Media and other remote administration

functions.
Static IP bay configuration uses the Static IP Bay Configuration addressing method which enables you to

assign IP addresses to each iLO based on slot location in the respective server enclosure. By providing a

set of IP addresses in the enclosure, you gain the advantages of a static IP bay configuration, without

requiring each individual iLO 2 to be configured locally.
Using iLO 2 static IP bay configuration:

Helps avoid the costs of a DHCP infrastructure to support the blade environment

Provides easier setup with automatic iLO 2 address generation for all or a few selected bays

For detailed information about iLO configurations, refer to the HP Integrated Lights-Out User Guide on the

Documentation CD or to the HP website (

http://www.hp.com/servers/lights-out

).

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

40

)

CD-ROM deployment (on page

41

)

Diskette image deployment (on page

42

)

SAN configuration (on page

43

)

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

38

)."

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

41

)

SmartStart Scripting Toolkit (on page

41

)

Advertising