Director
software
can
automatically
discover
the
BladeCenter
T
unit
(out-of-band,
using
the
Ethernet
port
on
the
management
module)
and
create
a
managed
object
for
the
unit.
For
the
IBM
Director
software
to
discover
the
BladeCenter
T
unit,
your
network
must
initially
provide
connectivity
from
the
IBM
Director
server
to
the
BladeCenter
T
management-module
Ethernet
port.
To
establish
connectivity,
the
management
module
attempts
to
use
DHCP
to
acquire
its
initial
IP
address
for
the
Ethernet
port.
If
the
DHCP
request
fails,
the
management
module
uses
a
static
IP
address.
Therefore,
the
DHCP
server
(if
used)
must
be
on
the
management
LAN
for
the
BladeCenter
T
unit.
Notes:
1.
All
management
modules
are
preconfigured
with
the
same
static
IP
address.
You
can
use
the
management-module
Web
interface
to
assign
a
new
static
IP
address
for
each
BladeCenter
T
unit.
If
DHCP
is
not
used
and
you
do
not
assign
a
new
static
IP
address
for
each
BladeCenter
T
unit
before
attempting
to
communicate
with
the
IBM
Director
software,
only
one
BladeCenter
T
unit
at
a
time
can
be
added
onto
the
network
for
discovery.
Adding
multiple
units
to
the
network
with
a
unique
IP
address
assignment
for
each
BladeCenter
T
unit
results
in
IP
address
conflicts.
2.
For
switch
communication
with
the
IBM
Director
server
through
the
management-module
external
Ethernet
port,
the
switch-module
internal
network
interface
and
the
management-module
internal
and
external
interfaces
must
be
on
the
same
subnet.
Preparing
for
BladeCenter
T
deployment
To
configure
your
BladeCenter
T
unit,
you
need
to:
v
Determine
which
deployment
tools
you
are
going
to
use
v
Set
up
your
deployment
infrastructure
v
Configure
your
BladeCenter
T
unit:
–
Configure
the
management
module
–
Set
the
chassis
policies
–
Configure
the
I/O
modules
This
section
provides
information
about
the
available
deployment
tools
and
setting
up
your
deployment
infrastructure.
Deployment
tools
Before
you
can
begin
using
the
BladeCenter
T
unit,
you
must
configure
each
of
the
components
(management
modules,
I/O
modules,
and
blade
servers).
You
have
a
variety
of
options
available
to
configure
these
components.
For
example,
you
can
access
the
firmware
that
is
embedded
into
each
of
the
components
to
configure
the
component
using
either
of
these
options:
v
Through
a
Web
browser.
To
access
the
components
through
a
Web
browser,
point
the
browser
to
the
IP
address
for
the
component.
The
Web
browser
you
use
must
meet
the
following
requirements:
–
Support
for
Java
™
–
Support
for
JavaScript
™
1.2
–
Minimum
screen
resolution
of
800x600
with
256
colors.
If
you
point
to
the
management
module,
you
will
see
the
System
Status
menu
after
logging
in.
From
this
menu,
you
can
perform
management
module
Chapter
3.
Deployment
considerations
43
Summary of Contents for 87302RU
Page 1: ...BladeCenter T Types 8720 and 8730 Planning and Installation Guide GA27 4339 02 ...
Page 2: ......
Page 3: ...BladeCenter T Types 8720 and 8730 Planning and Installation Guide GA27 4339 02 ...
Page 6: ...iv BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 8: ...vi BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 12: ...Index 121 x BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 14: ...xii BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 102: ...88 BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 130: ...116 BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 134: ...120 BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 138: ...124 BladeCenter T Types 8720 and 8730 Planning and Installation Guide ...
Page 139: ......
Page 140: ... Printed in USA GA27 4339 02 ...