The IBM eServer BladeCenter JS20 - IBM Redbooks

More documents

Recommendations

Info

As CSM was being developed, the Extreme Cluster Administration Toolkit (xCAT), a script-based package, was developed by IBM’s advanced technical sales support team. It was provided to clients who purchase Linux clusters based on IBM servers. It was also used by IBM Global Services to address their need for tools to deploy and manage Linux clusters. In the interim, xCAT became a proving ground for new concepts and practices centered on the management of Linux clusters. It can be a model for collaborative development between IBM and our clients. At the time of the development of this book, CSM was available in its fourth release (V1.4.0.4) with expanded scalability and hardware support. Many xCAT functions have been integrated into CSM, along with utilities to automate the process of migrating from xCAT to CSM. Through the use of CSM, clients who have implemented xCAT can now have many of these functions with full product support from IBM. The key benefits of CSM can help to reduce costs, provide higher availability of the cluster for productive use, and improve system utilization. Customers who have existing AIX 5L operating system-based cluster systems can leverage those skills to manage their Linux clusters. System administrators can automate repetitive installation and configuration tasks and automate problem determination and recovery. They can monitor and report health information and resource utilization, and automatically recover from node, storage, or network failures. This can lead to overall simplification of cluster administration. This section describes a fast-path CSM implementation to install and manage BladeCenter JS20s. For a more comprehensive view, refer to the CSM for Linux Planning and Installation Guide, SA22-7853. Our implementation of CSM assumes the type of network configuration described in 4.1.1, “Minimal network requirements” on page 54. Review this along with other CSM planning considerations described in 4.3.2, “IBM Cluster Systems Management” on page 64. 8.2.1 Setting up a CSM management node The first step in installing CSM is to set up a management node. We focus on how to set up a management node based on an xSeries server. We believe this is a common scenario for users of BladeCenter JS20s, particularly if they also have other blade servers that use Intel central processing units (CPUs). Using an xSeries server to install and manage BladeCenter JS20s cluster nodes introduces some complications that are not required when the management 148 The IBM Eserver BladeCenter JS20
node is the same architecture as the compute nodes. We focus our discussion around these issues. We use CSM to both install and manage BladeCenter JS20s. Therefore, we must use a compatible operating system on both the management node and the BladeCenter JS20 cluster nodes. The steps we require to set up the CSM management node are: 1. Install a supported operating system. 2. Configure network interfaces and set up host name resolution. 3. Obtain the latest CSM software and prerequisites. 4. Install the CSM base RPM. 5. Run the CSM installation program. 6. Copy the operating system, service packs, CSM code, and prerequisites for BladeCenter JS20 compute nodes. 7. Accept the CSM license. 8. Set up hardware control point passwords. 9. Verify the installation. We review each of these steps in the sections that follow. For our tests, we performed a standard installation of SUSE LINUX Enterprise Server (SLES) 9 for x86 on our management node directly from the distribution CDs. The management node network configuration Our implementation of CSM assumes the type of network configuration described in 4.1.1, “Minimal network requirements” on page 54. The CSM management node is connected to both the hardware management subnet and the operating system management subnet using separate network interfaces. You can use additional network interfaces to connect the management node to other networks if required. In our scenario, we used the IP address ranges 9.3.5/24 for the hardware management subnet and 192.168.1/24 for the operating system management subnet. There should be no other active DHCP servers on the operating system management subnet, because the CSM management node performs the DHCP server function on that subnet. Define host names and allocate IP addresses for the following interfaces before you attempt to use CSM: ► The management node network interface that connects to the operating system management subnet Chapter 8. System management scenarios 149
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:
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 82 and 83:
IBM Director Agent for the BladeCen
Page 84 and 85:
Network considerations and summary
Page 86 and 87:
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 118 and 119: 100 The IBM Eserver BladeCenter JS2
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: 122 The IBM Eserver BladeCenter JS2
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 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?