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

Figure
9
:
HP Server Automation: Per Server Compliance View
Now that the performance and availability of the database cluster
is
assured, the administrator can
further investig
ate the underlying problem.
After verifying various server hardware logs and verifying
the temperature in the data center,
the administrator
goes into the data
center to investigate
the issue
.
The administrator
finds that boxes
are covering the cooling ven
ts that supply cool air to the
server
blades
.
The administrator
moves the boxes to an appropriate location along the outer wall
. B
y the
time
the administrator
gets back to the HP SIM console
,
the server
blade
s have returned to a normal
operating temperatur
e.
Example 3: Server
consolidation
In an effort to reduce IT expenses, a company has decided to move the majority of its existing rack
-
based servers to HP BladeSystem
server
blade
s
.
Some server
blade
s are running commercial
applications like Microsoft Exc
hange and Citrix,
while
others run applications that were developed in
-
house.
First, the system administrator uses HP
SIM
and
PMP
to understand the current hardware
inventory, software
inventory,
and performance of the existing systems.
Based on this infor
mation,
the
administrator develops
a
plan
that
specif
ies
which server workloads can be consolidated onto a
single
server
blade and which
workloads
should be migrated directly to a new
server blade
as is.
HP BladeSystem c
-
C
lass enclosure hardware, which in
cludes Virtual Connect Ethernet and Fibre
Channel modules, is installed.
The LAN and SAN administrators preprovision the network segments
and
uplink connections and required LUNs (boot and data LUNs) for each BladeSystem enclosure.
Using
VCEM
, the server a
dministrator creates server
blade
connection profiles that contain LAN
and
SAN connections and
operating system
boot locations for each new server
. T
hen
, the server
administrator
assigns them to enclosure bays.
The administrator must configure a
unique ser
ver
connection profile for each bay, but
the administrator can
quickly create
a profile
by copying an
existing profile and giving
the profile
a new name.
As each
server
blade is installed in an enclosure
bay, Virtual Connect uses the information in the con
nection profile to automatically connect the server
to the defined communication and storage networks without additional help from the network and
storage administrators.
Then
, the administrator uses
R
apid
D
eployment
P
ack
to deploy the operating