Migrating vSphere 5.1 Environment from one IP range to another

So basically SSO, Web, Inventory and vCenter are all on separate VMS and they are wanting to migrate the management network from one IP range to another.

From what I have been reading this sounds like a disaster as everything will need to be re pointed?

Has anyone done this kind of work, and can point me to some stuff etc.

There is also a task to upgrade the environment to 5.5, and I wrong in thinking just installing everything a fresh might be a good idea? Running both side by side and migrating over to 5.5?  I am not sure if that is even an option here either way.

Should the upgrade be done first before the ip migration or before?

1. http://www.getshifting.com/wiki/changeipvcenter51?&#comment_a4e4f889a575d3d5a01d67177d27debe

2. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033620#Re-register vCenter Server with the Inventory Service

3. http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1008030

Also in article 3 it says to check you vCenter IP, when I do he box is blank as per the screenshot attached? What is with that?
Capture-vcenter.PNG
LVL 2
piedthepiperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you are using FQDN, should not be any issues here.

Also in article 3 it says to check you vCenter IP, when I do he box is blank as per the screenshot attached? What is with that?

not populated by default!

to be honest with you, if you have a tasks to Upgrade to 5.5.....(5.1 to 5.5 upgrades can be troublesome!).

I would recommend, a new 5.5 vCenter Server installation.
1
Zephyr ICTCloud ArchitectCommented:
If it were me and I had the choice, I'd go for setting up the 5.5 version from scratch and migrate everything like that, just need to make sure that you can reach the new ip-address range from the current range naturally. If an upgrade is in the pipeline, why not combine the two?

Start with either upgrading your current vcenter server or install a new one if history is not that important. Then upgrade your ESXi hosts one by one and add them to the new vCenter server, migrate your VM's, do the next hosts... And so on.

While it's certainly possible to migrate everything to a new IP, it will be quite the challenge to do it with limited downtime, and can indeed cause some headaches.

Regarding the vCenter Managed IP, did you verify it via the vSphere Web Client? Maybe it's set there and not showing in the old client?
1
piedthepiperAuthor Commented:
If you are using FQDN, should not be any issues here.
How do I double check this is the case?


Am I right in thinking, the only thing about doing a fresh install would be the vcenter database?All I do is install everything a fresh and point vcenter to the old database?

If you have any links on the subject please share!

I would recommend, a new 5.5 vCenter Server installation.
I take it you mean SSO Web Inventroy and vCenter Server not just vCenter?

Start with either upgrading your current vcenter server or install a new one if history is not that important

Isn't the history all in the database, so it should transfer across?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
can you ping ALL ESXi servers and vCenter server by FQDN ?

have FQDN been used all through the setup programs.

Can you use trace route to confirm FQDN....

FQDNs should always really be used, in a vSphere installation.

I would complete with a new installation of EVERYTHING!

How many hosts do you have?

How many VMs ?

Will you be using SQL Express of Full Edition ?
1
Zephyr ICTCloud ArchitectCommented:
Isn't the history all in the database, so it should transfer across?
Sure, also a possibility to migrate the database to the new host with vCenter 5.5, it's like migrating your 5.1 vCenter to a new host running vCenter 5.5

A nice walkthrough can be found here
0
piedthepiperAuthor Commented:
Yes everything is pingable with the FQDN!

Hosts are just under 50, 40 on 5.1 the rest on 4.1

External SQL 2008 r2 database, running on a VM

Just over 900 VMs including all management
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You will want to check the "VMware Matrix" to check if 5.5 is compatible with your host versions and builds.

http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php
1
piedthepiperAuthor Commented:
I have tried using that to find out if the current databse SQL Server 200 (90) compatibility mode is supported in 5.5 U2. It is running on SQL 2008 R2 RTM

I cant seem to tell?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
SQL 2008 R2 SP supported
Supported, see above SQL 2008 R2 SP2!

You didn't mention, Sp2, if you are just RTM, you'll need a SP2.
1
piedthepiperAuthor Commented:
SQL Server 2008 R2 RTM      10.50.1600.1 is what we are running, so I guess thatll need upgrading o SP2.

But what about the actual database compatibility mode, it is set to 2005 (90) ? Can that remain the same?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
this document suggest, it should be fine. I assume this is a legacy database ?

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2053132
1
piedthepiperAuthor Commented:
To use a newly supported Microsoft SQL database, such as Microsoft SQL 2008, you do not need to perform a clean installation of vCenter Server if your existing database is also Microsoft SQL Server. For example, you can upgrade a Microsoft SQL Server 2000 database to Microsoft SQL Server 2005 or Microsoft SQL Server 2008 and then upgrade vCenter Server 4.0 or higher to vCenter Server 5.5. When you migrate the database from Microsoft SQL Server 2000 to Microsoft SQL Server 2005 or higher, set the compatibility level of the database to 90.

I take it Andrew you are referencing this bit? Yes the environment was originally a 4.x and then went to 5.0 and is now at 5.1
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Correct.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.