The IBM eServer BladeCenter JS20 - IBM Redbooks

More documents

Recommendations

Info

IBM Director Agent for the BladeCenter JS20 Support for the BladeCenter JS20 was introduced in IBM Director Version 4.12. You can learn how to install the IBM Director Agent in 8.1.2, “Installing an IBM Director Agent” on page 145. We recommend that you install the IBM Director Server on an xSeries server. For maximum functionality, this server needs IP connectivity to the Management Module in each BladeCenter chassis and to every blade server. This connectivity can be provided by connecting the IBM Director Server to both the hardware management subnet and operating system management subnets described in 4.1.1, “Minimal network requirements” on page 54. If your environment is primarily comprised of servers running Linux, consider installation of the IBM Director Server under Linux. 4.3.2 IBM Cluster Systems Management IBM Cluster Systems Management is a systems management tool. It simplifies the management of clusters of servers running the AIX and Linux operating systems. This section focuses on the planning considerations that are associated with using CSM to manage BladeCenter JS20s. For more planning information, refer to the IBM Cluster Systems Management for Linux Planning and Installation Guide, SA22-7873, and the IBM Cluster Systems Management for AIX5L Planning and Installation Guide, SA22-7919. Supported CSM and operating system releases Preliminary support for the BladeCenter JS20 was introduced in CSM for Linux Version 1.3.3.1. CSM requires specific support for each operating system version that is running on servers that it manages. Currently (at the time of publication) CSM Version 1.4 supports the following operating systems on the BladeCenter JS20: ► Red Hat Enterprise Linux Version 3 (QU3) ► AIX 5L Version 5.2 and 5.3 ► SUSE LINUX Enterprise Server (SLES) Version 8.1and 9 To check for updates to this list of supported operating systems, refer to the CSM publication site at: http://publib.boulder.ibm.com/clresctr/windows/public/clusterbooks.html 64 The IBM Eserver BladeCenter JS20
Management node selection Each CSM cluster requires a management node, which provides the central point of administration and control for the entire cluster. CSM has complex rules concerning the compatibility of management nodes, non-management nodes (cluster nodes), and the operating system they run. We attempt to simplify these rules by focusing exclusively on the requirements for a management node that only manages BladeCenter JS20s. If your environment is more complex, refer to the CSM planning documents. You can use a CSM management node to both install and manage BladeCenter JS20s, or you can use a management node to manage BladeCenter JS20s that were installed using other mechanisms. Most environments use CSM to both install and manage BladeCenter JS20s, so we focus on that scenario. If you use a management node to both install and manage BladeCenter JS20s running Linux, you must use the same type of Linux distribution on both the management node and the BladeCenter JS20s. However, the management node does not need the same processor architecture that is used in the BladeCenter JS20. For example, if you plan to install SLES on BladeCenter JS20s, you can use the following types of management node and operating system combinations to both install and manage the BladeCenter JS20s: ► A supported xSeries server running SLES ► A supported pSeries server running SLES ► A IBM HS20 Blade Server running SLES ► A IBM BladeCenter JS20 running SLES In large installations, we recommend that you use either an xSeries or pSeries server as a management node. If your environment also contains non-BladeCenter JS20s, such as the HS20 Blade Server, or xSeries cluster nodes, we recommend that you use an xSeries management node such as the xSeries 345. We performed our testing of CSM using an xSeries management node, since many users of the BladeCenter JS20 may have environments that includes HS20 Blade Servers. Chapter 4. Planning considerations 65
Page 1:
The IBM Eserver BladeCenter JS20 Le
Page 4 and 5:
Note: Before using this information
Page 6 and 7:
Chapter 4. Planning considerations
Page 8 and 9:
vi The IBM Eserver BladeCenter JS20
Page 10 and 11:
6-8 Language selection . . . . . .
Page 12 and 13:
x The IBM Eserver BladeCenter JS20
Page 14 and 15:
Trademarks The following terms are
Page 16 and 17:
worked actively with Linux adoption
Page 18 and 19:
xvi The IBM Eserver BladeCenter JS2
Page 20 and 21:
2 The IBM Eserver BladeCenter JS20
Page 22 and 23:
for e-commerce and On Demand Busine
Page 24 and 25:
Page 26 and 27:
2.1 Overview of the BladeCenter inf
Page 28 and 29:
Attention: Nonredundant power is no
Page 30 and 31:
Attention: Power supply modules mus
Page 32 and 33: Figure 2-4 KVM Management Module Th
Page 34 and 35: 2.1.4 I/O modules You use the keybo
Page 36 and 37: Note: The IBM 4-Port Gb Ethernet Sw
Page 38 and 39: The Brocade Enterprise SAN Module c
Page 40 and 41: 2.2 BladeCenter JS20 The BladeCente
Page 42 and 43: 2.2.1 Base features There are two m
Page 44 and 45: You can learn more about the availa
Page 46 and 47: Expansion cards You can install any
Page 48 and 49: 2.3.1 Review of POWER and PowerPC A
Page 50 and 51: In 1993, IBM announced the POWER2 p
Page 52 and 53: These components all interact with
Page 54 and 55: IBM processors implementing PowerPC
Page 56 and 57: PowerPC 970 and PowerPC 970FX proce
Page 58 and 59: capabilities were usually referred
Page 60 and 61: For additional information about th
Page 62 and 63: The major features of the PowerPC 9
Page 64 and 65: the bus interface is slightly lower
Page 66 and 67: 3.1 Operating system support 3.1.1
Page 68 and 69: 3.2.2 IBM Director management, the
Page 70 and 71: 52 The IBM Eserver BladeCenter JS20
Page 72 and 73: 4.1 Network planning Successful ins
Page 74 and 75: Hardware management subnet We recom
Page 76 and 77: Application subnet The primary reas
Page 78 and 79: 4.2 Operating system installation T
Page 80 and 81: When you perform network installati
Page 84 and 85: Network considerations and summary
Page 88 and 89: 5.1 Management Module configuration
Page 90 and 91: PASSW0RD. The 0 in the password is
Page 92 and 93: When a new LAN Switch I/O Module is
Page 94 and 95: At this point, the LAN Switch I/O M
Page 96 and 97: 5.3.2 Setting the boot sequence Set
Page 98 and 99: Figure 5-7 Viewing firmware levels
Page 100 and 101: 4. After you download all the PKT f
Page 102 and 103: 5.4.3 BladeCenter JS20 firmware (BI
Page 104 and 105: 1. Download the firmware update pac
Page 106 and 107: LAN Switch Module in I/O Module Bay
Page 108 and 109: e. Leave the values for User Define
Page 110 and 111: connections. This is sufficient to
Page 112 and 113: minutes, you are disconnected. You
Page 114 and 115: 6. As soon as you type 8, the Open
Page 116 and 117: 5. Select the JS20 blade that you a
Page 120 and 121: 6.1 Installing Linux Both Red Hat E
Page 122 and 123: SuSE sources SuSE installations are
Page 124 and 125: 3. In the next panel as shown in Fi
Page 126 and 127: To build your own zImage.initrd, fo
Page 128 and 129: 6.2.1 BOOTP DHCP is an extension to
Page 130 and 131: 6.3.1 Red Hat Kickstart Red Hat pro
Page 132 and 133:
6.3.2 SuSE AutoYaST SLES provides a
Page 134 and 135:
► System Set the general system i
Page 136 and 137:
The syntax for mkzimage_cmdline is
Page 138 and 139:
3. We select the install option and
Page 140 and 141:
Page 142 and 143:
7.1 Minimal NIM installation Follow
Page 144 and 145:
4. In the next window (Figure 7-4),
Page 146 and 147:
3. In the Configure NIM Environment
Page 148 and 149:
7.3 Adding machine information With
Page 150 and 151:
3. In the next window (Figure 7-12)
Page 152 and 153:
7.4 Preparing the NIM master With a
Page 154 and 155:
1. On the first panel, select the d
Page 156 and 157:
4. As illustrated in Figure 7-19, w
Page 158 and 159:
8.1 IBM Director IBM Director is a
Page 160 and 161:
8.1.1 Setting up an IBM Director Se
Page 162 and 163:
8. Enter the database connection in
Page 164 and 165:
2. With the sources copied to the h
Page 166 and 167:
As CSM was being developed, the Ext
Page 168 and 169:
This is the interface that will be
Page 170 and 171:
version packaged with CSM. And you
Page 172 and 173:
You can verify what user IDs you co
Page 174 and 175:
► PowerMethod: Should always be b
Page 176 and 177:
The csmsetupyast command uses an XM
Page 178 and 179:
RHEL Red Hat Enterprise Linux RISC
Page 180 and 181:
Online resources ► CSM for Linux:
Page 182 and 183:
How to get IBM Redbooks Help from I
Page 184 and 185:
eth0 62 eth1 62 F Fibre Channel Exp
Page 186 and 187:
T translation lookaside buffer (TLB
Page 190:
The IBM Eserver BladeCenter JS20 Le
show all

The IBM eServer BladeCenter JS20 - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?