VMware Cloud Community
Kristian_SKF
Contributor
Contributor

Physical upgrade to vSphere 4 u1 from 3.5 u2

We are planning an upgrade to vSphere 4 u1 from 3.5 u2 with new hardware also.

We currently have two dual quad Xeons with 24 GB RAM and upgrading to two new dual Quad Nahelm with 96 GB ram each. Storage is SAN.

Please confirm the steps.

1. Upgrade Vcenter 3.5u4 to version 4 u1.

I have tried to install a fresh Vcenter 4 u1 an a new server and letting that one manage our existing 3.5 servers but I'm getting an licensing error. One resolution might be creating a fresh install of Vcenter 3.5u4 and manage my servers through this one. I know that I will be missing historical data, and HA and DRS will be lost.

2. Install esx on the new servers. Using Costum setup

Setting swap file to 1600 MB ETC.

3. Setup network. My new servers got 8 Gigabit ports.1 port for service console

1 Vmotion using crossover cable ?

1 Service Console - Is this one necessary when the SC is running on a VM?

1 DMZ

1 subsidiary

3 for Internal networking - two DELL 48 ports switches. Do I need to be aware of anything?

4. Connect SAN cables when install is complete.

My new server shold be able to see existing VMs right?

5. Upgrade VmTools and Vm Hardware

Any feedback is appreciated

0 Kudos
4 Replies
AndreTheGiant
Immortal
Immortal

1. Upgrade Vcenter 3.5u4 to version 4 u1.

I have tried to install a fresh Vcenter 4 u1 an a new server and letting that one manage our existing 3.5 servers but I'm getting an licensing error.

Be sure that old license server is still running, and check license configuration on ESX 3.5.

2. Install esx on the new servers. Using Costum setup

ok

*3. Setup network. My new servers got 8 Gigabit ports

I suggest:

1 vSwitch with 2 pNIC for SC (yes is still necessary!) and VMotion

1 vSwitch with 1 or 2 pNIC for DMZ

1 vSwitch with 3 or 4 pNIC for VM portgroup

If you plan to use FT, consider add 1 pNIC in first vSwitch

4. Connect SAN cables when install is complete.

My new server shold be able to see existing VMs right?

Yes, if SAN zoning and masking is fine

5. Upgrade VmTools and Vm Hardware

First VMware Tools, then virtual hardware (and remember that you cannot run v7 on ESX 3.x)

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
depping
Leadership
Leadership

I agree with mr Giant. Change the NIC/vSwitch config. You could even work with a single vSwitch if your network design is based on VLANs and not on physical seperation.

Duncan

VMware Communities User Moderator | VCP | VCDX

-


Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

Kristian_SKF
Contributor
Contributor

Our DMZ is a seperate Physical network. No VLAN here

0 Kudos
Kristian_SKF
Contributor
Contributor

Just another quick question.

We just received our new server - they are blazing fast. :smileygrin:

We were planning on using a 4 port netcard from our existing servers and put it into out new servers, so It will have the total of 8 Pnic.

Current config:

1 Pnic for SC and VM network

1 Pnic for DMZ (6 vm's)

2 Pnic for Domain Network (40 VM's)

I need to enable Vmotion and VMkernel. Can I use ( for a short time) the same Pnic that is hosting the SC and VM Network. And if yes what should the gateway be?

EDIT: Enabled Vmotion on the same vSwitch that hosts the SC and it is working fine.

0 Kudos