The experiences of an SMB IT technician
Archive for the ‘Servers’ Category.
The Midrange Wiki is a good way to get started with the IBM i platform. I’ve started writing a short Getting Started guide there, which may be of interest to you.
If you work on the IBM i platform, the Midrange Mailing Lists may also be a place to visit and subscribe. Also, check out the IMHO Midrange Blog.
So, IBM’s x3650 M2 have been out for some time and in the meantime i’ve deployed three of them – two with SBS 2008, and one with Windows Server 2008. No pictures, since the camera in the office is broken.
The x3650 M2 comes with a new IMM (Integrated Management Module) that replaces both the BMC and the RSA II Slimline. In order to get remote KVM capability, a physical licensing key must be installed into the server. Standard features like remote power on/off are available without the licensing key – which is more expensive than the physical RSA II slimline adapter. With the IMM also comes UEFI, as a replacement to the aging BIOS.
The x3650 M2 also gets rid of the Adaptec ServeRAID 8k controllers, and introduces us to the ServeRAID 10 series manufactured by LSI. The ServeRAID 8k series have been plagued by several extremely heavy bugs that never caused me loss of data (but several other people), but nevertheless cost me a lot of my nerves.
The two standard RAID controllers in the x3650 M2 are the ServeRAID BR10i, which is the baseline controller without BBWC and without support for RAID5. The ServeRAID MR10i is the better model, which comes with 256MB BBWC and support for RAID5/RAID6. Unlike the ServeRAID 8k/8k-l story, these are entirely standalone controllers, that are located in a special daughterboard position with a standard PCI-e x8 interface.
Both controllers support only 8 drives – in order to get 12 drives, you need a special enabler kit that comes with a SAS expander hard and several of other stuff that doesn’t look all that trivial. I’ve used such a kit, and so i can’t comment on how it works exactly.
The power supplies have gotten a lot smaller, the server seems to look a lot more organized, the 2.5″ SAS HDDs are no longer as finicky as they were in the x3650 and now fit very well into their slots, the Lightpath diagnostics panel now looks like it belongs to an expensive server and locks into place securely.
Of course, all the usual changes that come with the new Nehalem based Xeons, triple channel DDR-3 memory, both processors needed for using more than 8 slots, using to many memory modules will downgrade the speed, etc.
So much for the general rundown – now for my assorted observations:
That’s it for now. Lot’s of negative stuff in here, but the machines are actually extremely good performers. I hope that IBM will fix those outstanding bugs soon.
With the release of the new generation of System x servers, IBM also revamped it’s tool offering.
Central point of the new IBM offering is the ToolsCenter, which serves as a starting point for all important IBM tools.
The two most important tools, which every admin dealing with IBM System x servers should know are now available in new versions, which offer improved functionality.
UpdateXpress is now available in version 3. Pictured to the right is the new user interface, which offers much needed improvements. The previous versions looked like a leftover from the cold war.
UpdateXpress allows you to update all your System x drives in one automatic swoop, without the need to meticulously check the IBM web site for newly released drivers.
DSA is now available in version 2.20. While the handling of the tool hasn’t changed much, there is now a 64bit version available. A few bugs i’ve encountered on 64bit systems are fixed with this new release.
Today i attended an interesting product presentation from IBM, about their Nehalem product line up. In addition to the information i’ve already gleaned from the IBM web page, i’ve learned several things that are equally important.
If you’ve never heard about the x3650 M2, i suggest you to read my introduction post first.
Planned general availability (GA) of the new x3650 M2 is the the 20th of April, or in pretty much 3 weeks. Orders, configuration and pricing is available – so if you want to buy a new server now and can wait for three weeks, you should order a x3650 M2.
At the end of April, the M2 versions of the x3400 and x3500 will be announced. Judging from the current timeline, this will put GA of those new products near May.
4 CPU machines are planned for Q1 2010. I don’t care much about those since we run all our heavy DB workloads on IBM POWER.
Just like the Core Microarchitecture brought many changes to servers, the new 5500 Xeons bring even more changes. It’s especially important for system administrators to understand the differences, and even more important if you’re selling systems to customers.
Here are a few key differences:
To the right you can see Intel’s official spec sheet. Intel introduces a “garbage bin” of CPUs that you should never use – the E5502 / E5504 / E5506 models. These CPUs do not support HyperThreading, TurboBoost, 1066 Memory and only have 4 instead of 8 megabytes of cache. Make sure to use E5520 or faster CPUs to ensure best performance. The performance difference between an E5506 and an E5520 is 15-20%, while the price difference is much smaller! In my opinion, the E5520 is currently the sweet spot between price and performance.
With FB-DIMMs, memory configuration was simple, because FB-DIMMs were slow no matter which way you put it. However, with the new integrated memory controllers, memory of much higher speed is now available. Now, as a technician or sales things will get more complicated.
I wrote in an earlier post that i didn’t understand why IBM only put 16 DIMM slots into the machine, while HP installed 18 DIMM slots – the reason is that in most cases it makes little sense to populate all DIMM slots, because this will heavily reduce the bandwidth available, as the memory must run at lower speeds.
While HP has decided to offer registered and unregistered memory for their DL3xx G6 models, IBM only offers registered DIMMs. The x3650 M2 COG Guide offers a lot of in terms of possible configurations. The most important thing is keep the numbers of memory modules down – this makes it easier deploy them correctly.
Another important part is that memory is no longer ordered in pairs, but again separately as it was a few generations before. Most servers ship with two 1GB modules standard. This is not an optimal configuration, since you have three channels that could be used.
There are two ways to deal with this: either add a third 1 GB module and then add the rest of the memory you need. Or discard the two memory modules that come with the servers and just install the higher capacity modules you bought. My recommendation would be to discard the 1GB modules and install three 4GB modules – for most SMB environments, 12GB of memory suffices for almost all services.
The onboard RAID-Controller is gone, there is a new specially positioned but otherwise standard PCI-E slot for the RAID controller. The system ships with a non-BBWC controller called the BR10i. In most cases, it makes sense to replace the standard RAID-Controller with a ServeRAID MR10i.
Some configurations also require an enablement kit to drive all 12 disk slots. Only 8 disk slots are standard.
The RSA II Slimline is gone. IMM now offers a lot of the RSA II functionality by default, but the most important functionality, remote KVM still requires a so called “Virtual Media Key” (as it enables Remote Media as well). In general, if a customer has used RSA II Slimline up to now, also include a Virtual Media Key. This enables full IMM functionality.
SSD offerings have also been added. Currently, the pricing for the 50GB SATA SSD is 3970 CHF in SSCT. My assumption would be that this is a pricing error, but i’m not too sure about that.
Pricing hasn’t changed much. DDR3 memory seems to be a bit more expensive than the FB-DIMMs were, but that’ll pass as soon as DDR3 volume ramps up. I’ve created a sample config that is probably valid for most SMB deployments that clocks in at around 10k CHF. This is roughly the same as it was before with the standard x3650, except that the x3650 M2 will deliver a lot more performance for the money.
With yesterdays official announcement of the Nehalem Xeons, all major server manufacturers announced their new product lineup. HPs new announcements are equally interesting as what IBM has announced.
HP DL380 G6 Quickspecs
HP DL360 G6 Quickspecs
There are some interesting things to see there – unlike IBM, HP chose to go with 18 memory slots, allowing each CPU’s three channels to drive three memory modules. HP also offers a flash-based Memory configuration tool, that alleviates having to learn complicated placement rules.
HP also offers more disks per system, allowing a DL 380 G6 configuration with 16 2.5″ drives in 2U server. The DL360 G6 can have up to 8 2.5″ drives – that’s the same number of drives that previous generations had in a 2U form factor!
Having the ability to add lots of local storage is a good thing in smaller businesses. Larger companies probably won’t need that as much. Interestingly, HP choose to stay with a traditional BIOS with their G6 series. IBM is already offering UEFI on their x3550 M2 / x3650 M2.
Another new thing that i gleaned from those documents is the ability to choose a power supply based on the expected load of the server – making it possible to favor higher efficiency (for example, if you do not intend to have local disks in the server, as you’re planning to use your SAN).
A few days ago i bought an i7 920 for my computer at home. The performance is absolutely astonishing, compared to the AMD X2 CPU i had before. Especially VMs perform very well on it.
The first Nehalem-based servers have already been released, and as always IBM is a quiet compared to other server manufacturers. However, today while looking at some support documents i saw that IBM finally offers downloads of IBM x3650 M2 and IBM x3550 M2 documentation:
x3650 M2 Installation Guide
x3650 M2 Service Guide
x3550 M2 Installation Guide
x3550 M2 Service Guide
IMM User Guide (RSA II Successor)
I’ve now skimmed through the documents a few times and found several things worth mentioning – please note that i haven’t seen the actual hardware, so there may be mistakes here. If i’m aware of the, i’ll correct them of course.
The RSA II adapter has been succeded by the IMM. The IMM is integrated into both the x3650 M2 and the x3550 M2, but certain features need to be enabled by purchasing a “Media Key”. This is similar to how HP handles this issue, except with a physical key. The Media key enables additional features, as described in the IMM User Guide:
In addition, IMM Premium has the following features:
- Remote presence, including the remote control of a server
- Operating-system failure screen capture and display through the Web interface
- Remote disk, which enables the attachment of a diskette drive, CD/DVD drive, USB flash drive, or disk image to a server
The x3650 M2 will support up to 12 hard disks. The x3550 M2 will support up to 6 hard disks. Only 2.5″ of course. I currently didn’t see much mention of SSD, but i’m sure both these machines will see SSDs during their lifecycle.
There are also several changes regarding the hard disk controller. The Onboard ServeRAID 8k made by Adaptec is gone. It will be replaced by MR10i and BR10i ServeRAID Adapters, made by LSI Logic. For more details about those controllers, see the ServeRAID Quick Reference. These adapters will fit into a special slot, and are no longer fully integrated into the system board.
This is a good thing – RAID controller troubles in the x3550 and x3650 always meant replacement of the system board, which could be problematic because it changed the various IDs of the system (most notably the MAC adresses).
Nehalem brings CPUs with On-Die memory controllers to Intel-based servers. If you’ve never handled AMD servers before, this means a few changes.
* Memory is local to the CPU, meaning you will need both CPUs if you want to use the full 16 memory slots.
* Nehalem features a triple-channel memory subsystem, making memory placement interesting
* If you’ve wondered how triple-channel and 16 slots works, see the graphic to the right
The x3650 M2 comes with 4 Gigabit ethernet ports. The x3550 M2 with two, but an option for an additional two without requiring a full pci-e slot. This is especially good when you’re using virtualization and need to segregate hosts or need the extra bandwidth.
UEFI is the successor to the common BIOS. This will get interesting – i have no real idea what to expect from this. I only know that WS08 supports UEFI boot directly, and that IBM will provide emulation for legacy operating systems.
There’s also an in-system USB port for running a Hypervisor directly from flash. The system also features an integrated TPM module, which can be used together with Bitlocker to provide full disk encryption in physically insecure servers.
An important Whitepaper from IBM about Transitioning to UEFI is also available.
Both new systems have also appeared in IBMs NOS support list. While full Windows support is offered, it looks like VMware will not be supported, at least initially.
The system board lists an 8 pin power connector for high performance graphics cards. The parts list also lists NVIDIA FX1700 and NVIDIA FX570. This might be needed for CUDA or similar applications.
I want one. According to my sources, they should be available for sale starting on the 21st of April. As of today, the System x New Generation information page is finally online.
The past few days were rather busy – i’ve spent them revamping the current network and infrastructure of a small business – deploying new PCs and the first SBS 2008.
First, lets talk about the hardware. It’s important to know that small businesses handle their infrastructure completely differently than large businesses, and in my opinion there are some things that require “unusual” thinking.
Reliability: an SBS server is extremely critical for operation of a small business and they usually do not replace servers after three years
Maintainability: small businesses do not have dedicated IT personnel. Usually, most “heavy” tasks are done by an IT service provider, and the daily IT tasks are done inhouse by someone as a secondary job
Functionality: small businesses are sometimes just as demanding as larger companies – the small size requires setups that maximize the productivity of each employee
So, there are three main aspects one should focus on when deploying an SBS server.
Reliablity is a key aspect. An SBS server is critical for the business and this requires hardware that is highly capable and reliable. After all, an SBS server can serve a Business for up to five years without replacing the hardware. This is why it makes sense to buy really good hardware that lasts that long, combined with appropriate maintenance contracts to get it back up in case you run into problems.
In this case, we decided to use the following hardware:
IBM System x3500
Intel Quadcore 2.66 Ghz 12M (leaving 1 slot available)
10 GB Memory (leaving 6 slots available)
8 2.5″ 147GB 10kRPM SAS Disks (leaving 4 slots available)
ServeRAID 8k with 256MB BBWC (for the first 8 disks)
ServeRAID 8s with 256MB BBWC (for the other 4 disks)
Disk configuration:
RAID 1 consisting of two 147GB Disks
RAID 5 consisting of five 147GB Disks
Global Hotspare
IBM SAS HBA (for tapedrive)
LTO4 SAS attached HH internal tapedrive
Redundant fans & power
IBM Remote Supervisor Adapter II
5Y of IBM ServicePac with committed service option
As you can see, the system has lots of storage and redundancy. It’s also important to know that the SBS server does not run any third party applications (except those necessary for operation), the ERP runs on an IBM POWER machine. With SBS 2008, i would not recommend running any third party applications on the SBS itself – if necessary to run third party apps on a server, purchase SBS premium and run the third party apps on the second server.
The second aspect is ease of use, for which we should use software that can be automated as well as possible. SBS handles lots of things on his own, but we opted for a third party backup application because we still see tape backups as the best way to fulfill most of a customers needs. Especially since LTO drives have WORM media, that can help to comply with certain local laws.
As for the software, i’ve installed BackupExec 12.5 to handle the backups to tape. Tape backups are easier to handle for customers, offer superior performance, and make archival and external storage of data easy. Unfortunately, BackupExec 12.5 does not integrate with the SBS Console (yet?).
For virus scan, we’ve opted for McAfee VirusScan Enterprise. A central management application was unfortunately not yet available, so we deployed McAfee manually on each client, and on the server.
Exchange is protected using ForeFront for Exchange, which has served me well in the past.
SBS 2008 has a nice reporting function, but there are other important notifications: the RSA Adapter notifies for all hardware failures like power supplies, fans, etc. independently through e-mail (which can contact external adresses and even works if the failure killed the server), and allows remote troubleshooting in case the machine does not boot. ServeRAID manager and BackupExec also send daily reports to be viewed by the customer.
Last, but not least, is functionality. After all, customers aren’t like me that want an SBS because they like technology – no, they want an SBS to fulfill certain needs their business has.
In this case, there were several unique requirements regarding mailflow – thanks to the included Exchange 2007 server, which offers a very flexible transport rule system i was able to implement these requirements without having to purchase third party software or even program event sinks on our own.
So far, i’ve had zero issues with SBS 2008 – it worked without any problems and hardware support wasn’t a problem either. Looks like IBM got all the kinks figured out since the release of Windows Server 2008 at the beginning of the year.
The System x3500 is also very nice hardware – it looks like a tower variant of the x3650, which i also like very much. The only criticism i have for the machine is that installing the redundant fan kit is total pain in the ass, mostly because the documentation covers both the x3400 and x3500, and some parts don’t apply for the x3500 (but aren’t marked as such).
It shows that IBM can still deliver top notch hardware at affordable prices.
In case you couldn’t figure it out from reading this far, i really like SBS 2008, and it’s ready for action in a production environment. In case you’re thinking about deploying a new SBS, go with SBS 2008!
HP recently had a special offering for an ML110 G5 hardware bundle, that consisted of the following parts:
For less than 400 CHF. As i needed a machine to run SBS2008 at home, and my current one wasn’t 64bit capable, this seemed like a good buy, especially because the E200 with BBWC alone is worth around 300 CHF.
Of course, i needed more RAM and disk space. I also ordered 4x 2GB memory modules (with ECC) from a third party memory manufacturer (Transcend) – priced at around 80 CHF each. I also ordered 4x Western Digital 1TB disks that are optimized for 24 hour use, priced at around 180 CHF.
This brought me to a total price of around 1500 CHF. I had two 160GB disks that i didn’t have any use for (except throwing them at people i don’t like).
1500 CHF is a lot of money for me, but for a company it’s nothing – still, this is ideal for experimentation. The free ESXi supports the E200 SAS controller, making it easy to build a test lab based on VMware – also, Windows Server 2008 x64 and Hyper-V also run flawlessly on the machine.
The machine is also very quiet, making it possible to use it in a normal appartment or in your office.
You get what you pay for still applies – the machine has no remote management features, only a single network port, forcing you to use the same port for management and virtual machine traffic, which can be acceptable in a test environment. HP’s System Insight Manager is not supported on this machine, either.
The case is very small, resembling a normal HP client minitower. The mainboard supports ECC memory, which is becoming more and more important with todays memory sizes. Unfortunately, it only offers four memory slots with a maximum capacity of 2GB per stick, maxing the machine out at only 8GB of RAM.
The integrated E200 SAS RAID Controller has a 128MB BBWC card, that allows it to use it as a write cache, and enables licensing to use RAID5. In my case, i used RAID10. The disk performance is better than anticipated, even though i’m using slow consumer drives, the performance for running VMs is acceptable.
The machine has three x8 PCI-E slots and a single PCI slot. One of the x8 slots is used by the E200 controller.
This offer is still available under HP Part# 470064-639, and there are still some companies that are selling it for the lower promotion price.
I’m currently running SBS2008 directly on the hardware, with not virtualization in-between. The performance is good, but i’d still never use such a setup for a production deployment at a customer – the management options, hardware flexibility, redundancy etc. just aren’t fit for production.
Update: I was asked about Linux compatibility on this machine. See the official HP Linux compatibility list. The E200 SAS RAID Controller is supported by the cciss driver, which is in the vanilla linux kernel. So most distributions will be able to install on this box – support is another matter, though.
There is no easy way to get official support for non-corporate versions of Linux, like Ubuntu. My usual way in those scenarios is to run Linux as a VM under ESXi, but that doesn’t work with the ML110 as ESXi is not supported (but works).
I’ve written a bit about ESXi before in a comparison to other free virtualization products from an SMB perspective.
I’ve seen the “big” ESX in a few places and worked a bit with it, but i decided to refresh my knowledge on VMware a bit. For this, i first had to scrounge up a machine that was able to pass the rigorous HCL from VMware.
Unfortunately i didn’t find something that was really a Small Business machine – i used a HS21 Blade from my BladeCenter S testing environment.
The HS21 blade has 4GB RAM, a 2.66 Ghz QuadCore CPU and two 500GB SATA Harddisks attached to an LSI1064 SAS Controller. Fortunately, this configuration is supported.
Similar to the installation of Windows Server 2008 or Windows Vista, the ESXi installation is extremely streamlined. All you have to do is pop the CD in, select the disk where you want to install ESXi and then let it continue. The whole setup took around 15 minutes, most of the delay owed to the extremely slow Laptop CD Drive installed in the BladeCenter S.
After installation, the Blade rebooted and you will be greeted by an extremely simplistic interface that allows you to change basics like the password of ESXi and reconfigure the management network interface and also display a few logfiles. On first startup, it also showed my a Web address where i can download the VI Client that is used to manage ESXi.
A very pleasant experience.
After accessing the ESXi host through HTTP, i could then download the VI Client. Installation on another Blade running WS2008 was smooth. It also installed an Update Service that allows me to upgrade ESXi.
After logging on using the VI Client to ESXi, i was greeted with a nicely detailed instructions that i would need to create a datastore. After few clicks i had a datastore created on the RAID1 that ESXi was installed.
The VI Client looks very impressive and neat. It looks like ESXi can read diagnostic information from the Blade, and can monitor RAID, Fan and other stati easily. One of the things i really like about this is that you get a standardized interface for monitoring your hardware – on Windows you usually have to use tools like IBM Director that are just one big mess to handle. Here, i didn’t have to configure anything – it just worked.
After entering licensing information, configurating a static IP Address, changing hostname and DNS information, i rebooted the blade.
I decided to create a first virtual machine – the blade i killed for running ESXi was previously running Exchange 2007. As this is just a demonstration setup, i decided to recover the preexisting Exchange server into a VM, in order continue having a full featured demo setup.
So i created a new Virtual Machine, configured for running Windows Server 2008 x64. Now, i didn’t have WDS setup in the Demo Environment, so i had to find a way to boot the Blade from an ISO. Previously i used scp to copy the ISO to the ESX Management Partition, but that didn’t work on ESXi. Luckily, the VI Client has a “Datastore Browser” that allowed me to upload files to the vmfs3 filesystem.
After uploading the ISO, i booted from it. The installation was pretty slow, but comparisons to my Hyper-V hosts aren’t fair as those run 10kRPM 147GB SAS Disks in a RAID5 configuration instead of the slow-as-molasses 500GB 7.2kRPM SATA Disks.
After OS installation, i immediately installed the VMware tools. One reboot later, i had a working Windows Server 2008 machine.
One of the things i noticed: When running WS08 virtualized on Hyper-V with 4 virtual CPUs on a Quadcore machine, WS08 thinks i have on Quadcore. On VMware, WS08 thinks i have 4 real CPUs (Sockets). This can bite you if you want to give a WS08 Std Machine more than 4 Cores – as WS08 Std is only licensed to four sockets.
The next step obviously is restoring the Exchange server, but that doesn’t really have to do all that much with ESXi.
ESXi is great. One of the biggest advantages over Hyper-V is the VI Client that consolidates a lot of information that is all strewn about in Windows. For example, it has built-in performance metrics, raid status monitors, etc. You can get all the same information with a machine running Hyper-V, but you’ll have to use other tools for that (of course you can customize a MMC do include Perfmon, but it’s not exactly the same).
VMware shows that they have gained long term experience with Virtual Machines, and the VI Client clearly shows the maturity of their product.
Permission management seems much better than Hyper-V, but i didn’t find a way to use Active Directory integration. Maybe Virtual Center is required to this, or i just wasn’t able to find it in ESXi – it exists, because there are numerous references on the Web.
I’ll certainly consider using Hyper-V when i have to run non-Windows guests. For Windows guests, Hyper-V with it’s VMbus architecture seems better suited. For non-Windows guests, VMware can’t be beaten right now.
Last Friday i received a new toy. An IBM BladeCenter S, with two HS21, one HS21 XM and a JS12 Blade.
The BladeCenter S i received came with 10 500GB SATA Disks and two DSMs, four power supplies, an Advanced Management Module, a Server Connectivity Module and a SAS Connectivity Module. The power supplies use standard 230V type 23 plugs, which do require a little special installation, but much less so than industrial plugs used with the bigger BladeCenters.
The big point about the BladeCenter S is that it does not require an external SAN to provide Storage to the Blade – an integrated SAS Switch that allows very flexible disk configurations is integrated. Configuration can be done using a Webbrowser against the SAS Connectivity Web Interface, using SSH/Telnet to access the SAS Connectivity Commandline, or using a fully graphical interface using IBM’s Storage Configuration Manager. There are some predefined configurations, but none of them suited my configuration – creating new configurations using SCM is easy enough though.
The disks in the BladeCenter’s DSMs (Disk Storage Module) are hot swappable – currently, only 3.5″ DSMs are available, with a 2.5″ DSM in the pipeline. Most of the blades support one or two internal disks, but the problem here is that these disks are not hot swappable. Depending on your Blade loadout, 12 disks might not be enough. For example, the HS21 XM Blades only fit one internal disk, and running without RAID on the System partition seems pointless, so you would be using at least 6 disks (without hotspares) for a basic Exchange deployment.
The Webinterface on the AMM is nicely done, although it lacks a bit of flashiness. That’s not a requirement though, it does a very solid job at what it needs to do.
After powering up the BladeCenter S for the first time, i connected to it using a web browser and upgraded all the firmwares. There are quite a lot of them (AMM, SAS, Server Connectivity), but it all worked out flawlessly. Time to move on to the real course: the Blades.
Starting with the familiar first, i started with the HS21 Intel Blades first. The two HS21 Blades both had a 2.66 Ghz Quadcore and 4GB RAM, the HS21 XM Blade had a 2.5 Ghz Quadcore and 9GB of RAM (more about that later).
When starting the first HS21 Blade, after configuring all the storage using SCM, it failed to POST it’s LSI Logic SAS/RAID Controller. I searched for the error message on the net, assuming that i screwed up the configuration. I didn’t find anything meaningful, so i tried to do what everyone else would do in this situation: Apply every Firmware update for the Blade i could find.
Of course it wasn’t as easy as i wanted it to be. The controller not POSTing was an endless loop, i couldn’t get the machine to start from the AMM virtual floppy drive. I used SCM to disconnect the storage (by disabling the Blade’s SAS port). Now, the blade booted flawlessly, indicating that i probably had a problem with my disks. When browsing the IBM website, it became obvious that only newer firmwares support SATA drives. After upgrading the SAS Firmware, i was able to boot the blade without disabling the Blade’s SAS port. Unfortunately, the onboard SAS controller only supports RAID level 1 and 10. Probably owed to the fact that most blades are using SAN storage – IBM promised that there would be SAS RAID adapter that supports other RAID levels – these are especially important for the cost-conscious SMB market.
I booted a Windows PE 2.0 using WDS, and was able to install Windows Server 2008 x64 without any issues.
The HS21 XM blade on the other hand complained when booted for the first time that it’s memory configuration was invalid – it only supports 2, 4 and 8 DIMM configurations – 6 DIMM configurations are not supported. I removed two 512MB modules and booted the Blade with 8GB – it worked flawlessly and without complaining.
First, read this document about i on Blade. It explains everything better than i ever could.
The JS12 is a POWER6 based blade that is able to run IBM i. The first time i turned on the blade, all the HS21 blades (already running Windows Server 2008) crashed hard. When rebooting, they no longer found their drives. I turned off all the blades, disconnected the JS12′s SAS port and turned everything on again. The Intel blades booted, and after i was sure that they’re up and running again, i powered on the JS12 again. This time, no issue arised. I tried to reproduce the behaviour i’ve seen before, and the same thing happened again.
My current assumption is that the issues were caused by the SAS Controller which does not have a Firmware update yet, and can’t deal with the SATA drives located in the DSMs. Further investigation told me that there’s no firmware upgrade for the SAS Controller in the POWER6 blade, and that SATA drives are not supported when running IBM i on the blade anyway. I ordered 4 147GB SAS drives, disabled the SAS port on the blade, and tried booting the POWER6 blade again. It booted flawlessly again.
The next step was to install VIOS – this is a rather complicated multi-step process. First, you have to turn on “Serial over LAN” aka SOL, then logon to the AMM using SSH, connect to the POWER blade using serial passthrough and then boot the blade from the VIOS CD. The install is pretty self explanatory, but takes forever. Expect 3 to 4 hours.
Next is connecting to the Integrated Virtualization Manager (IVM) running on the VIOS partition. The IVM is basically a HMC light minus the console functionality. The only way to get a console on the JS12 blade is using a LAN console (which can only run on consumer versions of Windows, and is not supported on most of the Blades).
I installed the latest VIOS patches (around 4GB) and enabled mirroring on the two 147GB SAS disks in the blade itself. The next step will be installing IBM i, with which i have to wait until i receive the ordered SAS Disks. Installing the patches also takes quite some time, around 30 minutes.
The BladeCenter S is great. Yep, not everything ran flawlessly from the start, but nobody’s perfect from the beginning. The BladeCenter brings an innovative new perspective to the SMB market. The problems that IBM needs to address are the addition of 2.5″ DSMs (already in the works) and more capable RAID controllers (also in the works). A BladeCenter S with the ability to use around 20-40 disks could prove interesting.
The POWER6 Blade is interesting, and while VIOS adds complexity, it is as streamlined as possible. I’m interested about seeing IBM i running on the machine.
If you have any other question about the BladeCenter S – or anything you would like to see in detail, post a comment. I’ll try to figure it out.
