2.
Connect
the
management
module
10/100-Mbps
Ethernet
port
to
a
separate
layer
2
network
for
security.
If
a
separate
network
is
not
available,
connect
the
Ethernet
ports
of
the
management
modules
and
switch
modules
to
the
same
layer
2
network.
3.
Avoid
network
configurations
that
could
lead
to
data
loops,
if
possible.
Loops
are
created
when
you
connect
multiple
ports
from
the
same
switch
module
to
the
same
layer
2
network
device
without
first
enabling
link
aggregation.
If
you
implement
configurations
that
include
data
loops,
the
spanning
tree
protocol
on
the
switch-module
external
ports
must
remain
enabled.
Using
Remote
Deployment
Manager
Version
4.11
Update
3
or
later
You
can
use
the
Remote
Deployment
Manager
(RDM)
Version
4.11
Update
3
(or
later)
program
to
install
a
supported
Microsoft
Windows
operating
system
or
a
BIOS
update
onto
a
blader
server.
Follow
the
instructions
in
the
documentation
that
comes
with
the
RDM
program
to
install
a
supported
Microsoft
Windows
operating
system,
supported
Red
Hat
Advanced
server
2.1,
or
BIOS
code
update.
Go
to
the
following
Web
site
for
updated
information
about
the
RDM
program
and
information
about
how
to
purchase
the
software
or
download
an
updated:
Using
IBM
Director
For
a
complete
list
of
operating
systems
that
support
IBM
Director,
see
the
IBM
Director
compatibility
document.
This
document
is
at:
www.ibm.com/servers/
eserver/xseries/systems_management/ibm_director/agent/.
This
document
is
updated
every
6
to
8
weeks.
The
IBM
Director
program
is
a
systems-management
product.
Through
the
remote
connection
on
the
management
module,
you
can
use
IBM
Director
on
a
management
console
to
configure
the
BladeCenter
T
unit,
modify
the
configuration,
and
set
up
more
advanced
features.
Notes:
1.
Some
tasks,
such
as
software
distribution,
require
an
in-band
connection
from
IBM
Director
Server
through
a
campus
(public)
LAN
to
a
switch-module
port.
2.
See
the
IBM
Support
Web
site
at:
www.ibm.com/pc/support/
for
the
version
of
IBM
Director
software
that
you
can
use
to
manage
redundant
management
modules.
Communicating
with
the
IBM
Director
software
For
a
complete
list
of
operating
systems
that
support
IBM
Director,
see
the
IBM
Director
compatibility
document.
This
document
is
at:
www.ibm.com/servers/
eserver/xseries/systems_management/ibm_director/agent/.
It
is
updated
every
6
to
8
weeks.
Note:
See
Figure
23
on
page
41
for
an
example
of
a
typical
network
configuration.
To
communicate
with
the
BladeCenter
T
unit,
the
IBM
Director
software
needs
a
managed
object
(in
the
Group
Contents
pane
of
the
IBM
Director
Management
Console
main
window)
that
represents
the
BladeCenter
T
unit.
If
the
BladeCenter
T
management-module
IP
address
is
known,
the
network
administrator
can
create
an
IBM
Director
managed
object
for
the
unit.
If
the
IP
address
is
not
known,
the
IBM
www.ibm.com/servers/eserver/xseries/systems_management/ibm_director/extensions/
rdm.html
42
BladeCenter
T
Types
8720
and
8730:
Planning
and
Installation
Guide
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 ...
