Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 700
  • Last Modified:

Changing IP address scheme

Hello Experts -

We're getting ready to move our company to a new location and have decided to change our whole address scheme.  We're planning to do this all over a weekend.  We use a 2003 active directory domain with about 25 physical statically assigned servers, we have Vsphere 4.0 running about 25 servers with statically assigned addresses, we use Lefthand for our san solution, dhcp for the desktops and vmware view machines.

Obviously this is a big undertaking...  Would anyone have any advice for best practices on tackling this undertaking?  Possibly some steps to take or gotchas to look out for?

Any help or leads to good reference material would be greatly appreciated.

Thanks
0
MMIC
Asked:
MMIC
1 Solution
 
bgoeringCommented:
Is it because you are using public IP addresses everywhere? If so I would recommend you switch to private addressing wherever possible as part of the conversion.

The only other advice I might be able to tender is to start using DHCP wherever possible to allocate addresses. With what you have it won't be difficult, just tedious.

Good Luck
0
 
ragijshahCommented:
I am assuming that you are using Windows based DHCP server (Windows 2003).

You might want to consider following things before changing IP scheme.

1) Assign secondary IP to servers and ensure routing is done.
2) Change lease time for scope in existing DHCP configuration
3) Once ready to change over IP scheme create new scope for DHCP keeping two IPs on static serves (one from old network and 2nd from new ip scheme)
4) Leave initial IP on server for few days and then remove them from server

Also its advised to run DHCP best practice analyzer to avoid any known issues.

http://blogs.technet.com/b/teamdhcp/archive/2010/05/01/dhcp-server-best-practice-analyzer-available-for-download.aspx

Regards,
0
 
bgoeringCommented:
Another observation to look out for - if you have subnets set up in active directory sites and services then make sure you have a subnet defined for the new ip range before you change the DC address.
0
 
Lee OsborneCommented:
We've just changed our subnet from a public class C to a private class B. One reason because it was public, and the second because we were almost out of IP's. We changed ours when we virtualised the infrastructure and haven't looked back since!

We started by putting a temporary router in to send traffic from one (new) subnet to another (old) and vice-versa, and act as a temporary gateway address. When we put a new DC VM in place, this was the first DC in the new subnet to hold the new DHCP scope, DNS and WINS. The old scope was deactivated and the new one was activated for the workstations to pick up a new lease. Then all the printers (which are static) were changed.

Once we had done this part, the servers were migrated from P2V and assigned a new class B IP on reboot. Lastly, we changed the WAN routers IP's and routes, and finally changed the firewall address (which is the default 0.0.0.0 route for all other traffic). Once everything had moved, we removed the temporary router.

One thing we ended up being aware of were routes on routers, switches and firewalls, NAT translations, static ARP entries, and firewall rules.

If I think of anything else, I'll let you know!

Lee
0
 
MMICAuthor Commented:
Thanks for all your suggestions.  We actaully decided against changing our IP's since there wasnt a real need to do so.
0
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.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now