• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Upgrading Vshpere Host Hardware

S

sixpac

Limp Gawd
Joined
Jun 8, 2004
Messages
272
I am going to be replacing my hardware for the hosts this coming weekend. I am replacing all 4 of my IBM blades to new dual 6 core cpu's with 72GB memory each. I will leave Vshpere at the current level when I move over to the new blades and then after update to Vsphere 4.1.

Current setup:

Vshpere 4.0.0 294855
IBM Bladecenter with 4 hosts in Cluster (8853G4U)
Dual E5430 Xeon (per blade)
16GB memory per blade
Virtual Center on physical blade Windows 2008 x86

________________________

My question is, will I be able to add the new blades into the cluster and move all the vm's over to the new blades, then one by one and then remove the old blades out of the cluster?

Other then the newer processor and memory the new blades will have the same configuration (6 nic's ) as the old blades have. Although I will be replacing the HBA's on the new blades. (dual HBA per blade).


Thoughts? suggestions?

thank you.
 
Ok, cool. good post about the EVC. I didn't think about that.

One question. When I bring in the new blades after zoning in the new HBA's on the blades I shouldn't have an issue doing vmotion from the old blades to the new. some of the vm's have raw mapped lun's on them that I will moving over.
 
If you're at vCenter 4.1 already, there's no reason not to bring the new boxes already at 4.1 though, it'll save you time in the long run.
 
Ok, sounds good.

Thanks for your help.. will post back next week after I do the updates.
 
ND40oz said:
If you're at vCenter 4.1 already, there's no reason not to bring the new boxes already at 4.1 though, it'll save you time in the long run.
Click to expand...

I am at 4.0.0 as listed in my first post.

I will be going to 4.1 after I bring in all the new blades and remove the old ones. I also will have to update to 64bit VC as well before that.
 
sixpac said:
I am at 4.0.0 as listed in my first post.

I will be going to 4.1 after I bring in all the new blades and remove the old ones. I also will have to update to 64bit VC as well before that.
Click to expand...

Sorry, didn't realize that was your vCenter version listed in the first post, thought you were referring to the host version of vSphere (although the x86 should have given it away).

Either way, you're going to have to go 64-bit and upgrade the VC at some point, I'd do it before you bring all the new hardware in and then just bring the new stuff in at the latest version, but that's because I'm lazy and try to do it in as little steps as possible. :p
 
I'd rather leave it as is (since everything is working fine) and then upgrade to 4.1 afterwards so if any problems arise upgrading I can deal with it then.
 
Well good news.. got the 1st new blade host up and running in the cluster!!

My new host is running Esx(i) update 2 and I was able to move it right into the cluster with HA enabled with no issue what so ever. Such a smooth upgrade.

So right now I am running 3 hosts with the old cpu and memory with ESX and 1 with the new cpu and memory using ESXi.

For us going from 16GB per host to 72GB is a major upgrade.. (never mind the 6cores and hyperthreading).

The vm's on the new host just feel so much snappier now. Can't wait to finish this upgrade next week and then move on to the 4.1 upgrade.
 
You must log in or register to reply here.
Back
Top