Earlier this week I was actually faced with my first challenging task at my new job. The QA department wanted to stress test a new database platform called “Cache” from a company called InterSystems. So around 9:30 am Tuesday, a mountainous project was more or less dumped into my lap… But its ok. This is the stuff that I enjoy/am good at.
My task was to take a IBM Blade Server that was not in use, and install Windows Server 2003 R2 Standard to each of the 14 blades. Well that might not seem like a difficult task. But after a laundry list of problems, I’ll get to those next, I was able to get about 2/3’s of the blades ready for the stress test.
First I was told that I had to use an IBM Resource disk to “partition” and setup the blade for the Server2k3 install… Well after three failed attempts at trying to use the “Resource Disk”, I decided to try an install with just the Server 2003 disk. It worked… Not a big surprise. Kinda caught a few people off guard who had been using the resource cd to setup the partitions forever. Oh and by the way… Tuesday just happened to be a Charity Dress Down day. This just means you can donate $3 to a charity and you can wear whatever you want. Just happens that in my ultimate wisdom, I decided to wear shorts.
Why is this a bad thing you ask? Well for those of you who have never worked in IT, all of the services that you connect to while you work, phone, fax, web sites, etc; are usually housed in a server room for that company or the particular location. The size of the room usually depends on the size of the company, but my works is about size of a small elementary school classroom. It is literally filed with hundreds of servers and thousands of hard drives. All these devices generate massive amounts of heat. That heat has to be removed, usually by some BIG ASS AIR CONDITIONERS…
It just so happens that the blade server that I would be setting up was directly in front of the two main vents to the server room. So I got to freeze my ass off for about 5 hours that day. Bye bye productivity…
I ended up getting two (out of 14) Blades setup with Server 2003 before I had to leave Tuesday. Before I left I started an install so one could run while I was away and it would be ready for the cd-key or whatever the next day. So I come in Wednesday morning, set the static ip and clicked next. Then I mozzied over to my cube and decided to start on my morning tasks… About 20 minutes later I decided to check on the server. Had a lovely Blue Screen of Death. I reset the blade and was going to try again. But somehow the BIOS was in some weird ass infinite loop… So I started on the next blade because I didn’t want to waste time. I got about three more blades successfully done when I started having another issue. The stupid ass cd-rom drive on the Blade Center decided that it was not going to be reading from any burned disks any more….
After an hour or so of fiddling with it, I was able to get it to install 2003 on one more blade before it completely gave out. I began some basic trouble shooting tasks and soon found out that it was still able to read factory imaged copies of disks. So I began the hunt of finding a factory copy of Server 2003 R2 Standard Edition. This may sound really easy, but its not… No one has an actual copy of 2003. Luckily, after a good hour of going through cd spindles, someone finally found one for me.
I got a couple more machines finished that day and headed home. I came to work the next day and started on another Blade. I got through another two blades before it completely crapped out on me. After an hour on the phone with IBM tech support I finally got another drive ordered. Next began the fun task of actually setting up the virtual machines.
But I’ll leave that pain for another day.