This is going to be a quite long series of posts, so I’d better make this introduction as short and compact as possible. Here is a Q/A approach, just pick up the part you are interested in, and then jump straight to the first vendor in our series.

Why I decided to start this series?

Everyone already knows the revolution the blades had brought to our industry. I’m not going to repeat here what you already know. I’m not going also to promote the blades over the traditional rack servers, or try to answer the eternity question: “scale up or scale out?”. You might have already made you decision to go with blades, or still considering that, in both cases this series should help you to take your next step. My main and only focus here is vSphere. I’ll never try to promote a vendor over another, and I will never try to influence your decision to go with a specific design. Go to the next Q/A to see how can you benefit from this series, or at least how I think you might do.

Who might be interested in this series?

• Consultants or Customers: if you want to have an over whole idea on designing and/or implementing vSphere on specific blade vendors.
• VMware partners: if you are a partner, you may find this series useful to support your presentations to customers. I’ve seen many partners who can talk fluently about their hardware products, however, they can struggle to answer very simple VMware related questions like: how should I map the vSwitches’ uplinks to the blades nics, or how can I have redundancy for my networks, and soon and so forth!
• Knowledge seekers: anyone, like myself, who’s fascinated by VMware and willing to understand how these incredible software technologies can run on different hardware vendors with the same level of flexibility.

What vendors will be covered here, and in which order?

Any blade vendor that is listed in the VMware HCL might be included. I say “might” because it also depends on how fast I’ll be able to learn about this specific vendor technologies given the highly complex and variant architectures from one vendor to another. You should know also that I work on my own here, no help from anyone what so ever. It really takes a lot of blood, sweat and tears to understand each vendor’s approach in doing things.

There is no specific order in this series, I started with IBM because it’s simply the hardware platform that I have worked the most on. If you like the series/concept let me know your thoughts and feedback and based on that I’ll try to prioritize vendors over others. There is no preferences for me personally.

Are you a hardware vendor?

If you work for a blade vendor and stumbled through this series, please take a moment to read the following:

• If you’d like to comment, you are most welcome to add, correct, or amend any details in my posts that are related to your hardware. However, you are not welcome – under any way, shape or form – to bash your competitors in this series.
• I can work with you to highlight anything that can make the vSphere implementation more solid, unique or innovative on your hardware. On the other hand, I will not allow on my blog any vendor to criticize the design and/or implementation options of the other vendors. In short, no FUD please.

Alright then, enough introduction and scary thoughts and let’s get to it. I’ll keep the following list up-to-date to always reflect the new posts of this series.

• vSphere on IBM BladeCenter H

Announcement:

Effective March 1st 2010, I am joining the PSO team at VMware as the first Senior Consultant covering the Middle-east region.

Now that the word is out, I guess everyone reading these lines will say something like: “Here we go again, another blogger joining another vendor. The trend continues.”

Well, you might be right at some level. I am a blogger. VMware is a vendor. What else would be different?

What is different here, at least in my opinion, is the timeline and circumstances that this whole story developed through. My original plan was to write a pretty huge post and tell you everything about it. How the dream started when I was watching the VMworld 2008 opening keynote. How the opportunity represented itself from the least expected way. How I went through the longest, most challenging and exciting interview process I have ever experienced throughout my career.

I said “my original plan” because I had to come up with an alternative. Unfortunately I’m just being hyper-sensitive now towards anything that I want to say or disclose about VMware. You know this feeling when you start in a new place, where you don’t know initially what you can and can’t talk about in public? Hopefully it will be a short period before I start getting the essence of the VMware internal culture and be more comfortable to share with you my experience in this great place. Until then, all what I can tell you is that I was approached by Duncan Epping back in July 2009 for an opportunity in the PSO team.

Yes, it was July 2009, before there was even a trend in the first place. This huge gap between now and then wasn’t really up to me or to VMware. It’s the complicated system of sponsorship that we have in this part of the world and all its related formalities. I was crazy patient, and they were very determined to have me. But I’m not here to bore you about these details. What I want to do instead is to acknowledge the huge efforts by Duncan throughout the process. I would have loved to talk in details about that, but again, I find myself in the same situation where I don’t know if I can elaborate more or not. Regardless of all that, let me take a quick moment here to tell you about this true legend, and why I pride myself on being referred to VMware by him.

I don’t look at Duncan as the number one blogger in the community (three times in a row and counting), or as someone who has an unmatchable visibility and influence (check his IOPS post for example), or even as someone who has a great deal of respect and admiration from everyone I’ve known in (and outside) the community. It’s something completely different than all that. It is simply his “passion” for the technology that really differentiate him from the crowd. This is the one thing that always stands out to me about Duncan.

I know brilliant people, I mean literally “brilliant” people in our community with an incredible experience and knowledge that I might never even achieve any time in my future career. But I have never (I repeat: never) saw someone among those people whom I thought for one second to have more passion than me for the virtualization technology in general or VMware in particular. Duncan was (and still) the only exception to that. Every little blog post, email or even tweet I see from him, I always see someone who has passion and dedication for what he does more than anyone I have ever known.

That is why I will always look up to him for inspiration, and that is why he will always be my number one in VMware.

Now that I’m approaching the end of my post, I’d like to take this chance to thank Deepak Narain for his continued support and for sticking up for me. I wouldn’t have reached this place without all your help, even for the very little logistic things that you were voluntarily taking care of to get me on board as soon as possible. I’d like also to thank Vegard Sagbakken, Frank Denneman and Aaron White. They were among the people in VMware who knew about my delayed recruitment process, and were very kind to follow up with me on its progress.

Lastly, and most importantly, to my dear blog readers: it was through your encouragement and positive feedback that I was able to keep this blog running, and it was through this blog that I got the visibility and exposure for VMware to hire me. With that said, I will always do my very best to keep my content here as unique, informative and educational as possible. Everything you’ve seen and liked on this blog up till this moment was completely gathered on my own, I didn’t even have a partner access or any source of information other than what was available to the public. Imagine the giant leap that I’m taking now where I get to read, learn, try and witness everything directly from the source. I am so excited to start this new journey, and I promise you that I’ll always deliver higher quality posts to you.

Oh, and in case you didn’t get the joke in the subject, the VMware employees are not entitled to the vExpert award!

P.S. This was a last minute thing, and it’s just for fun: (click here)

Motivation

I was having a discussion with one of the large enterprises here in Qatar lately, and I was quite surprised to know from them that they are hesitated to migrate their VI3.5 environment to vSphere because of the associated downtime. What surprised me was not the fact that they can’t afford a downtime, I’ve spent 6 years of my career working in the Telecom sector and I know for a fact that 1 second of downtime could mean a disaster, or even translate to a loss of thousand of $$. What surprised me was that they didn’t know that it is possible to do this migration without any downtime!

In this blog post, I will not only show you (and them) how I was able to perform my upgrade without even this single second of downtime, but I will also show how we were able to migrate our storage from one array to another without any service interruption whatsoever in our equally critical environment. To make things even more exciting, what I’m about to show you here is completely achievable using vSphere’s built-in features like VMware Converter, EVC, vMotion and Storage vMotion. There was no third-party tools used in this entire migration.

A brief environment overview

There is nothing better than diagramming this for easier follow-up. In the diagram below I’m illustrating a small portion of the environment showing the main components of the old ESX 3.5 hosts as well as the ESX 4.0 hosts. In our case, we decided not to go with in-place upgrade, and preferred to have a fresh install for the ESX hosts in the new vSphere environment.

You might have noticed that I included a video inside the diagram, and probably wondering why on earth would someone do something like that? The answer is simple: I’m showing-off! No seriously, I know many people (from VMware and specific storage vendors) who use my diagrams in their internal meetings with customers (really I’m not showing-off), and I thought it would be nice to have such small clip in the diagram that shows both the vMotion & SvMotion easy point-and-click approach.

Note: This is just an illustration not an S/vMotion architecture diagram! Wait for my A3 if you are interested to see the technology behind this…magic!

The Process

Step 1: We are running here vCenter on a physical server, and we want to utilize the same hardware for the new upgrade. The easiest way to achieve that is to P2V the existing vCenter 2.5 to another standalone ESX host in our environment. After the VM is migrated successfully and all the clean-up is done, the switch over from the physical to virtual can happen in a matter of seconds by disconnecting the physical server from the network, and connecting the VM (which has the same IP address of course) to the same subnet.

Step 2: Now that we have the vCenter 2.5 migrated, the next step is to perform a clean install on the freed physical server. Starting with the OS deployment, all the way to the vCenter 4.0 installation, initial configuration and licensing.

Step 3: The third step is to connect the new vCenter 4.0 to the old vCenter 2.5 licensing server. This part is important because the ESX 3.5 hosts do not leverage the new and improved licensing model that was introduced in the 4.0 release. This step is quite easy: you go to the “Administration” menu on your vSphere client, select the “vCenter Server Settings”, and then enter your old vCenter 2.5 hostname into the field as shown in the example below.

Step 4: Now we are ready to create a new cluster for the existing ESX 3.5 hosts on the left side of the diagram. The thing to note here is to create the cluster with the EVC mode enabled as shown below because we will be migrating the VMs between two deferent hardware/CPU generations:

Step 5: We create here a second cluster (EVC enabled as well) and add the new ESX 4.0 hosts to it as shown in the right side of the diagram.

Step6: Now, the trick here is to have one ESX 4.0 host in this cluster connected to both arrays in the environment – the EVA and the V-Max. We achieve that by connecting one HBA to the HP SAN fabric, and the second HBA to the EMC SAN fabric. Once this is done, and all the associated zoning and masking is configured, we can scan the HBAs and have all the datastores/LUNs available on this server that we will call it “Gateway”.

Step7: The fun begins. Since the gateway server is having the same shared storage with the ESX 3.5 hosts, all what you need to do here is to drag and drop your VMs from the old cluster to the new one. The vMotion will kick-in and do it’s magic to live migrate the VMs to the new gateway server. That’s right! We are live migrating virtual machines from ESX 3.5 to ESX 4.0 on the fly.

Step 8: Now to my favorite part in the whole migration process. Here we get to experience one of the most amazing features in vSphere – the Storage vMotion. It has been actually re-written with significant performance improvements that made it one of the most powerful tools for any VMware administrator in my opinion, and the best part is that it’s done now with a few mouse clicks through the GUI (checkout the diagram video, or this detailed post). As I mentioned above, we were migrating our workloads from the HP EVA to the EMC V-Max, and we felt quite confident (after intensively testing this in the lab for a week) that the SvMotion would be the best choice for our storage migration. The other reason for using SvMotion was the ability to thin-provision VMs on the fly. I’m not talking here about everything of course, but rather the development VMs that are hardly ever touched. We had so many VMs for our development department with quite huge space requirements, while in fact they are neither actively used all the time, nor they consume the disk space allocated to them. The thin-provisioning for these VMs saved us literally TBs of storage on the new expensive V-Max SAN.

Things to note:

• After you complete this migration you are not quite done yet. You should typically have your VM tools updated, and also the VM hardware upgraded from v4 to v7. While you will still run fine without these upgrades, it’s always recommended to be up-to-date in that regard, and to also leverage many of the new vSphere featuers like for example memory hot-add (my personal favorite!). The trick here is that you will need a VM reboot to perform that. In our case, for the less critical VMs we scheduled a planned reboots on weekly basis for the upgrades, and for the high-critical VMs, we just wait for the first possible OS reboot and we perform our upgrades along with it.
• Any storage vendor will tell you to do the thin-provisioning on the array directly, and I kinda agree with them on that, but this is not an option to everyone. Not all arrays come with this feature, or even if they do, not everyone can afford the licensing part. In our case, I simply couldn’t rely on the SAN admins for monitoring and maintaining these thin-provisioned LUNs on the array side, and from the other hand, there were some technical limitations associated with that in terms of SRDF replication or FAST v1 (but that is something specific to EMC, and relevant only to the time of writing this post).

Conclusion:

I will finish this post from where I started. The VMware vSphere is a very powerful and a true enterprise class virtualization platform. You’ve seen here how I was able to migrate the entire VI3.5 environment without one single second of downtime, and also how it was an extremely easy process to migrate our complete storage from one array vendor to another without any interruption in the servers/services whatsoever. There is nothing extraordinary in this scenario (except maybe the embedded video in the diagram), and you’ve seen how easy the steps are, and how everything we’ve done here is built in vSphere itself. Just know your requirement, plan your migration ahead, and you will be just fine!

I was going to just tweet this news, but I thought it is too exciting for 140 characters to handle!

I’m a big believer in everything visual as you know, and I think that this kind of video based training is the way to go for anyone learning about something new for the first time. The next step, of course, would be reading full-blown books and product manuals, but again: it is way too easy to start your knowledge journey with this kind of CBTs to get you up to speed with the main concepts and most importantly to see the whole thing in front of you without worrying about setting the labs and related prerequisites.

With that said, I was really excited to know about this new releases coming soon from Trainsignal, and even more excited when I knew about the great instructors of the series: David Davis, Hal Rottenberg and Rick Scherer!

Without further ramblings, here are the main highlights of the videos included, and you can read the full details on the official site here:

VMware View & ThinApp – David Davis

• Video 1 Virtual Desktop Infrastructure Overview – Understanding the Options
• Video 2 Introduction to VMware View
• Video 3 Installing VMware View 4
• Video 4 Deploying Virtual Desktops with View
• Video 5 Automated Virtual Desktop Deployment with View Pools
• Video 6 Adding a Terminal Services Pool in View
• Video 7 Understanding View Composer Linked Clones
• Video 8 Introduction to ThinApp 4
• Video 9 Installing ThinApp
• Video 10 Virtualizing Applications with ThinApp

Managing VMware vSphere with PowerCLI – Hal Rottenberg

• Video 1 Introduction to Power CLI
• Video 2 PowerShell Basics
• Video 3-1 PowerCLI Concepts – Part 1
• Video 3-2 PowerCLI Concepts – Part 2
• Video 4 Power CLI in the Real World
• Video 5 PowerCLI Cmdlet Deep Dives

Cisco Nexus 1000V VMware vSphere Third-Party Virtual Distributed Switch – Rick Scherer

• Video 1 Getting Started with the Nexus 1000V
• Video 2 Integrating the Cisco Nexus 1000V with vCenter Server
• Video 3 High Availability Option for the Cisco Nexus 1000V
• Video 4 Configuring Port Profiles on the Cisco Nexus 1000V

I’m definitely getting a copy of this as soon as it will be released!

Okay, so I’m probably the last person who wrote his VCP-410 exam on the planet, but at least I’ve done it with an awesome score! 481 out of 500!

I’ve been rescheduling this exam since November 2009 due to many factors, but mainly because of the lack of time! Today I had to sit the exam anyways to get the certificate without sitting the ICM course, and voila!

As I see from the VMware community forums, this is not an easy score to achieve, and that it also qualifies me (along with other requirements of course) to become a VMware Certified Instructor! Well, I never considered that before, but after a very recent discussion with one of the VMware’ians in my region, I was kind of enthused about this idea.

Now, I can’t tell you anything about the content itself – as per the agreement that you accept at the beginning of the exam – but I can at least share with you some thoughts about my preparations and the materials I used. I always find these kind of blog post an inspiration and encouragement for me to sit my exams, so I hope it will motivate you in a way or another:

My thoughts:

• The overall exam was way easy than I expected. I remember I had a quite hard time in my VCP-310 exam, but for this one I felt very comfortable.
• The diagrams that I’ve been designing till date gave me an incredible knowledge about the very specific details in the subjects, and consequently helped me a lot to nail down many questions in the exam related to vDS, memory management and HA.
• The blog posts from my fellow bloggers are also very useful; I can tell you that I answered one question about the PVSCSI from Scott Sauer’s awesome article here.
• If you are new to these kinds of IT exams, you have to read the questions extremely careful, especially if English is not your native language. You will get so many tricks in the wordings, and you may also be miss-directed to points that are not essential to the question being asked.
• I saw many blog posts talking about horror stories related to the config maximums questions, but I can tell you that I got only one or two of them, and they were related to information everyone should be aware of. I found Simon Long’s practice tests very useful in that regard and definitely better than reading through a boring flat PDF file.
• I can tell you that 99% of the exam will come from the official VMware documentation. I can’t stress enough on the importance of reading these documentations.

The Materials/facilities I used:

• Hands-on experience on vSphere since its early Beta (lab + production).
• VMware vSphere Documentations (a must, must, MUST read from a-z)
• Scott Lowe’s Mastering VMware vSphere 4.0 book.
• Forbes Guthrie’s vReference Card.
• Uncountable number of VMworld 2007-9 sessions

Congrats to all my fellow VCPs, and good luck for all the candidates. Don’t hesitate to email me if you need any help!