Table of Contents
Advertisement
IBM Director 4.2 and RDM 4.11 update 3 provide an easy way to configure the
components of the BladeCenter T unit and allows you to quickly reconfigure your
servers to meet workload and hardware availability requirements. Instructions for
using IBM Director 4.2 and RDM 4.11 update 3 are provided in the BladeCenter T
Types 8720 and 8730 Installation and User's Guide.
Deployment infrastructure
Although the deployment of the BladeCenter T unit does not require you to do so,
you should consider setting up a separate management network to configure and
manage your BladeCenter T unit. By separating the LAN segment used for
production from the LAN segment to which the BladeCenter T management module
(as well as the IBM Director and RDM server, if present) is connected, you can
ensure that unauthorized connections are not possible. Only the administrators'
systems would be connected to this LAN segment.
You should also consider the use of a DHCP server to lease IP addresses on the
management LAN. When powered on, the management module by default
searches for a DHCP server and sets a default static IP address if a DHCP server
is not found. Because the default static IP address is the same for all management
modules, IP address conflicts can result if you do not use a DHCP server.
Figure 24 on page 46 shows an example network that might be used to configure
and manage your BladeCenter T.
distributed systems management solution for nodes of a cluster running Red Hat
7.1 (as distributed and supported by Red Hat). More information about using
CSM is available at the following Web site: www.ibm.com/servers/eserver/
clusters/software/.
Chapter 3. Deployment considerations
45
Advertisement
Table of Contents
