The IBM eServer BladeCenter JS20 - IBM Redbooks

More documents

Recommendations

Info

for e-commerce and On Demand Business can achieve speed while ensuring flexibility, scalability, and availability. For such enterprise requirements as file-and-print and collaboration, BladeCenter is designed to offer reliability, flexibility for growth, and cost effectiveness. And clients with compute-intensive applications that need highly available clustering can use the BladeCenter to help achieve high degrees of scalability and performance. Benefits of the IBM Eserver BladeCenter family The IBM Eserver BladeCenter family of products features a modular design that integrates multiple computing resources into a cost-effective, high-density enclosure for a platform that provides: ► Lower cost in certain configurations: Due to efficiencies in power usage, heat emissions, and data center floor space utilization, when a configuration of other servers exceeds one rack, it is often less expensive over a multi-year period to use a single rack of BladeCenter chassis and BladeCenter JS20s. ► Physical server consolidation: A BladeCenter server is an ideal way to replace many uniprocessor or 2-way servers to save space. 14U of rack space for 14 1U servers can be replaced with one 7U BladeCenter chassis. Additional rack space that is normally taken for Ethernet, Fibre Channel, and other switches is eliminated by the integrated switches in the BladeCenter chassis. ► High availability: The BladeCenter chassis offers redundant and hot-swap components that can prevent failure of the chassis or blade servers when one of those components fail. The chassis has redundant, hot-swap cooling, power, midplane features, management, and I/O switches. It also has a hot-swap media tray, with CD-ROM and floppy drive, that can be removed and serviced while all blade servers are operating. ► Integrated switch technology: All service is from the front and rear of BladeCenter. There is no need to slide the chassis out of the rack and remove the top cover for service. Also, numerous cables are eliminated, reducing both cabling cost and servicer or administrator time. ► More integrated systems management features: The BladeCenter chassis includes a management module. This module eliminates the need for individual management adapters, such as the Remote Supervisor Adapter I or II, in each blade server for remote control. It also eliminates the need for RS485 interconnect cabling between the blade servers. ► SAN optimization: A Fibre Channel switch module installed in a BladeCenter chassis provides storage area network (SAN) access to all blade servers in the chassis without internal cabling. 4 The IBM Eserver BladeCenter JS20
BladeCenter versus an IBM rack server BladeCenter is an ideal solution for certain environments. In other environments, an IBM rack server may be a better fit: ► Need for a small number of servers: A BladeCenter chassis is required for one blade to be cost effective compared to some stand-alone servers. Therefore, a chassis should be full or nearly full. ► Need for existing Peripheral Component Interconnect (PCI) adapters: BladeCenter does not include adapter slots as shipped. An optional I/O Expansion Card feature offers one PCI slot per blade, limiting the blade to one integrated development environment (IDE) drive. The expansion feature supports PCI cards designed for BladeCenter. Therefore, a mix of BladeCenter and traditional rack-optimized servers may be appropriate. ► Need for large internal storage or external SCSI storage: BladeCenter supports a maximum of 80 GB of IDE or 146.8 GB of SCSI storage internally. While there is no provision for external SCSI storage, there is an external Fibre Channel SAN storage option. Using the optional internal SCSI storage feature doubles the space requirement of the blade, cutting in half the number of blade servers that can be installed in a chassis. For large internal storage, the IBM Eserver xSeries® 345 is capable of holding up to 880.8 GB of hot-swap SCSI storage. All rack-mounted xSeries servers can support, either natively or via an optional ServeRAID adapter, external SCSI arrays. ► Need for re-installation or repurposing at end of original: Stand-alone uniprocessor and 2-way servers can be distributed individually for use as departmental file/print servers and other low-horsepower uses. Because blade servers cannot be used without a chassis, the entire chassis-and-blades combo needs to stay together. The original chassis may be useful if older blade servers are discarded and newer, faster ones take their places in the chassis. ► Power requirements: The data center is wired for 110-120 V power. BladeCenter requires 220-240 V power. Learn more about IBM Eserver BladeCenter and its components in the IBM Redpaper The Cutting Edge: IBM Eserver BladeCenter, REDP-3581. The following chapters address the descriptions and considerations of the hardware and software components. Chapter 1. Introduction to BladeCenter and blade server technology 5
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 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 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:
68 The IBM Eserver BladeCenter JS20
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:
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?