HP Server Automation complements HP Insight Control to manage HP BladeSystem servers (487616-001, February 2008)

Figure
12
:
Sample software policy in Server Automation
Hardware
setup
V
irtual Connect Enterprise Manager
The movement of large numbers of servers would normally be done in phases.
With Virtual Connect
technology,
you
can prewire
all enclosures
to designated LAN and SAN addresses at the same time
with minimal physical cabling,
resulting in lower costs and more efficient use of the network and
storage administrators’ time.
Later, during each migration phase, the server administrator
will
install
each new blade quickly using
VCEM
to centrally assign server connection profiles to
all enclosures.
At
this point,
RDP
will
be used to deploy
operating system
images to the new
server
blades.
Migration
—
Consolidation
Rapid
Deployment Pack
R
apid
D
eployment
P
ack
quickly and easily deploys operating systems to server
blade
s and clients
using
either image or script
-
based methods.
The system administrator creates jobs, such as
Deploy
ProLiant ML/DL/BL + Windows 2003 Enterprise
,
containing a series of tasks that
configure the hardware in the preboot environment, install the operating system
,
and
perform any
customization steps.
Sample jobs are included in R
apid
D
eployment
P
ack
to simplify
this
creation.
You
can either launch
jobs
manually or configure
the jobs
to run automatically when a system is first
added to the RDP database (
Figure
13
)
.
Simply
inserting a
server
blade into an enclosure and
turning
the enclosure
on
triggers the correct job to run
.
In this example, the system administrator has
configured R
apid
D
eployment
P
ack
to automatically deploy an o
perating system based on
the
location
of the server blade
within a rack, enclosure
,
and bay.