(Updated 7/27/2010 – 11 am EST – added info on power and tower options)
When you think about blade servers, you probably think, “they are too expensive.” When you think about doing a VMware project, you probably think, “my servers are too old” or “I can’t afford new servers.” For $8 per GB, you can have blade servers preloaded with VMware ESXi 4.1 AND 4TB of storage! Want to know how? Keep reading.
No, I’m not smoking something. I’ve done the configuration and I can show you how to achieve a 4 TB SAN and 3 ESX hosts on blade servers with the IBM BladeCenter S. Before I can explain what I’ve done, let me give you the basics of the IBM BladeCenter S.
At 7U high, the chassis of the IBM BladeCenter S is the same height as the original IBM BladeCenter (now called the BladeCenter E). The chassis uses the same blade servers as the rest of the IBM blade chassis family, but the chassis holds only 6 blade servers – primarily due to the addition of locally attached storage drives. In addition, the chassis has the option to add a DVD drive for access to local media.
The IBM BladeCenter S has the ability to host up to 12 drives via Disk Storage Modules (IBM part # 43W3581) located to the right and left of the blade servers. These modules allow for each server have access, either dedicated or SHARED. Each DSM holds 6 x 3.5″ SAS, Near-Line SAS or SATA drives with drive sizes ranging up to 2TB. It is important to note, though, with the blade servers using 2.5″ hot-swap drives you may find yourself needing to stock two different types of drives. The DSM’s are sold separately, so if you only need to use 4 drives, you can wait and invest the additional $795 (U.S. List) at a later date, when you need the additional drive capacity.
As mentioned above, the blade servers can have either dedicated or shared access to the drives located in the DSM. The type of access depends on the type of SAS module used in the chassis. IBM offers both a SAS Connectivity Module and a SAS RAID Controller Module. The SAS Connectivity Module (IBM part # 39Y9195) is a module provides the ability to match up a blade server with the local drives. For example, if you have 6 drives and 2 blade servers, the SAS Connectivity Module would give the ability to map 3 drives to each blade server. The key here is that this is dedicated access – like having direct attached storage for each blade server. Each blade server needing access also need a SAS Connectivity Card. The SAS Connectivity Module also has 4 external SAS ports that can enable you to access IBM EXP3000 storage arrays providing additional storage capacity per blade server. This requires the blade servers to have the ServeRAID-MR10ie card installed instead of the SAS Connectivity Card and only one EXP3000 is allowed per blade server, however this is a great way to expand your storage if you outgrow the capabilities of the Disk Storage Modules.
In contrast, the SAS RAID Controller Module (IBM part #43W3584) allows for you to pool the storage and offer access to these arrays to each blade server that has the SAS Connectivity Card installed. Volumes that are created can be assigned to a specific blade or shared by several blade servers. The IBM SAS RAID Controller Module supports RAID levels 0, 1, 5 and 10 and each module also comes with RAID battery backup module. There are some caveats to be aware of: only SAS or NL SAS drives are supported (no SATA); the maximum volume size is currently limited to 2TB and the maximum number volumes each blade server can have is 8 (for a total of 48 volumes per chassis.) Another important thing to take note is that you must have 2 x SAS RAID Controller Modules, which sit in I/O Bays #3 and #4. This provides a redundant connection for each blade server with the SAS Connectivity Card. In fact, since I brought it up, let’s take a closer look at how the modules work in the IBM BladeCenter S.
BladeCenter S a Look From BehindWhen you look at the back of the IBM BladeCenter S, it may look confusing, but don’t worry – it’s pretty straight forward. The chassis comes standard with 2 x 1450w power supplies standard and a single Advanced Management Module. If you are using high wattage blade servers or using the second DSM, you probably will need the 2nd set of power supplies (IBM part # 46C7438). If your budget is tight and you can’t afford to pony up the additional $599 U.S. list I recommend you take advantage of IBM’s Power Calculator prior to purchase to see if you need the 2nd set of power supplies. Following the design of the other IBM BladeCenter chassis, the IBM BladeCenter is cooled by a set of 4 redundant hot-swap blower modules. Don’t bother looking for any other fans or cooling devices, because you won’t find them. These four blowers cool the entire chassis, modules and blade servers.
The Advanced Management Module (AMM) is the device that provides you with LOCAL keyboard, video and mouse connectivity (although only USB for keyboard and mouse) as well as an ethernet port to connect into your management network. The AMM gives you the ability to manage / monitor all of the chassis’ thermals as well as remotely control the blade servers and the I/O modules. In all honesty, the AMM is feature rich, so if you want to take a peek at what it can do, take at look at this IBM BladeCenter S Advanced Management Module simulator. Unlike the other IBM blade chassis, there is not an option for a redundant AMM, however in the event of a failure your blade servers, I/O modules, fans and blowers will continue to function without penalty.
The biggest technical confusion I see from engineers and customers alike is around the I/O layout of the blade chassis. The IBM BladeCenter S is a bit dissimilar to the other IBM chassis in the BladeCenter family so let me explain how it works. There are 4 I/O bays in the IBM BladeCenter S. The 1st I/O bay maps to the NICs that come on the motherboard of each blade server. If you are familiar with rack-mount servers, you know they typically have 2 x 1Gb Ethernet ports. The IBM Blade servers are no different – they also have 2 x 1Gb Ethernet NICs. In order for them to be “lit up” you need to have a module in bay 1 that can allow the signal from the blade server to extend out of the chassis. To simplify things – think of having a power outlet in the wall at home and connecting an extension cord to it so you can turn on a light that is a few feet away. The same rudimentary concept is how it works in the blade infrastructure. The only difference is, with the IBM BladeCenter S, both NIC ports 0 and 1 go to the I/O Module Bay #1. This means if that module has an issue, then those 2 NICs located on the motherboard of each blade server will be dead. There is no redundancy with the onboard NICs in the IBM BladeCenter S (unlike the other IBM BladeCenter chassis.) Why did IBM design it this way? Well, the original target market for the IBM BladeCenter S was small businesses and remote offices. When you look at those environments – how many have redundant NICs for the rack / tower server NICs? Odds are none. With that in mind, IBM designed the BladeCenter S to only have a single I/O module for both onboard NICs. Never fear, though. After a few months, IBM revised the design to allow for I/O Module #2 to provide an additional 2 NICs, using the 2/4 port Ethernet adapter (IBM part # 44W4479) on each blade server. The card is designed to provide 4 Ethernet Ports, however with the BladeCenter S, only 2 ports are connected. Therefore with network modules in I/O Module Bay 1 and 2 you can get 4 NICs. Add this to the 2 x SAS storage cards that we mentioned in the sections above and you “should” have adequate architecture to provide a VMware environment.
The $32,000 Design
Now that I’ve spent a few moments telling you what the IBM BladeCenter S is all about, perhaps you understand the potential. So how did I get to the $32,000 design that enables you to have 4 TB and 3 ESX hosts? I won’t devulge in the actual bill of materials, but here’s what I came up with:
- 1 x IBM BladeCenter S chassis
- 1 x Disk Storage Module
- 4 x 1 TB Near Line Storage Disk Drives
- 1 set of 1450W Power Supplies
- 2 x Server Connectivity (Ethernet) Modules
- 2 x SAS RAID Connectivity Modules
- 1 x DVD
- 3 x HS22 blade servers – each with 2 x Intel E5620 Xeon Processors, 24GB RAM, SAS Connectivity Card, ESXi 4.1 USB Memory Key
Total U.S. List Price (as of 7/26/2010): $30,768.00
Yes, I also know that HP has an offering (the BladeSystem C3000) that could compete to this design – however IBM is the only blade server vendor that offers dedicated local disk storage. HP’s design takes up a blade server slot. Perhaps I’ll write up something on this in the future.
THIS SECTION ADDED ON 7/27/2010 – I’ve added this section to cover a couple of pieces that I left off in the original post.
A really valuable feature of the IBM BladeCenter S is the ability to run on 110 v or 220 v. Use of 110 v is ideal for remote or small offices. The BladeCenter S power supplies are auto-sensing so you can use the same power supplies. There are a few power categories to choose from with the BladeCenter S:
- Redundant AC Power Source – in this policy, the power limit is set to equal the capacity of N power modules. According to IBM’s Implementing the IBM
BladeCenter S Chassis Redbook, this policy is the most conservative approach and is recommended when all four power modules are installed. When the chassis is correctly wired with dual AC power sources, one AC power source can fail without affecting your blade server operation.
- Redundant Power Module Policy – in this policy, the power limit equals the capacity of one less than the number of power modules installed (more than one power module must be present). One power module can fail without affecting blade server operation. If a single power module fails, all the blade servers that are powered on will continue to operate at normal performance levels.
- No Redundancy – all power modules are used, there is no redundancy and if you lose a power supply and the power demands exceed the capacity of the available power modules, the chassis will power down… Not recommended.
Office Enablement Kit
For those environments where a standard server rack is not ideal, IBM offers the Office Enablement Kit (part # 201886X). This adds an additional few hundred dollars, but it gives you an 11u rack enclosure, complete with front and rear locking doors and wheels. It also comes with an acoustic attenuation module that helps muffle the sound. (YouTube video on this can be seen here.) As mentioned above, the IBM BladeCenter S is only 7U tall, so the additional 4U can be used for an optional Flat Panel Monitor kit (shown in the image to the left) or perhaps additional storage or networking. This kit really helps to finalize an “all-in-one” solution for small or remote environments.
Yes, I know it’s only 4 x 1TB drives, and I know it’s Near-Line SAS drives, however it is enough resources to help YOU create that VMware infrastructure that you need. Of course, the VMware licensing will be extra, but I just saved you a ton of money – now you can afford it…
So – what do you think? Is this appealing, or is this just a pipe dream? Let me know your thoughts. I’m really interested in getting an idea of whether this design would really work in your world.
Founder of BladesMadeSimple.com. I have over 15 years of experience in the x86 server and virtualization marketplace. Since 1997 I've worked at several resellers in the Atlanta area, including Solarcom (Presidio), Canvas Systems, Optimus Solutions (Softchoice) and Corus360. I have a vast array of competitive x86 server knowledge and certifications as well as an in-depth understanding of VMware and Citrix virtualization. Since 2011 I have been working for Dell as a Server Sales Engineer covering the Global 500 market in the midwest and east.
Follow me on TwitterMy Tweets
- AMD (1)
- ARM (1)
- Cisco (57)
- Citrix (1)
- Cloud Computing (1)
- Comdex (1)
- Dell (78)
- Fujitsu (1)
- Future Technologies (10)
- Gartner (3)
- History (5)
- HP (78)
- HPC (2)
- IBM (76)
- IDC (21)
- Intel (16)
- Market Analysis (7)
- Microserver (1)
- Microsoft (1)
- Networking (1)
- News (2)
- Performance (4)
- Power (4)
- Reviews (2)
- Server Comparisons (18)
- Uncategorized (12)
- Virtualization (2)
- VMmark (2)
- VMware (12)