I tried to import MS DHCP Server 2008 Data to Infoblox vNIOS 6.5, but through DIW its not importing, tried several time but it shows error.
As i assume DIW is not supporting for MS DHCP migration 2008 onwards, can any help me in this.
01-04-2013 07:06 AM
I use the DIW to migrate from 2008 and 2003 Microsoft servers to Infoblox 6.5.x regularly and it is working well.
There are a few things I've learned. Do not use 2008\Windows 7 versions of netsh to export 2003 DHCP servers. Netsh will exit without errors but not give you a valid export.
Editing the export text file in notepad down to just the subnets you want to import before ever open the DIW sometimes make it easier to track down any configuration 'errors' in the Microsoft config that the DIW \ Infoblox will not process. Sometimes find and replace in notepad is much faster than making the changes in the Microsoft or DIW GUI. It takes a couple tries to figure out what header and footer info the DIW requires to still see it as a good config file but once you have that down its smooth sailing.
01-04-2013 07:18 AM
Hi, Thanks for this information...
But can you elaborate this "Do not use 2008\Windows 7 versions of netsh to export 2003 DHCP servers. Netsh will exit without errors but not give you a valid export."
As Infoblox reference export command from Server 2008/2012 is as "netsh dhcp server <ip address> dump > <name>.netsh
And the same is not able to import to Infoblox vNios 6.5 through DIW, so please if possible can you elaborate and explain details or step wise.
this will help me to resove this issue.
01-07-2013 07:56 AM
I have a Windows 2003 DHCP server that I keep around to run all the netsh DHCP dump commands on. The 2008 \ Windows 7 netsh command seems to only work well against 2008 servers. If you point newer versions of netsh at older versions of the OS's you get an incomplete export file. I don't know if DIW will recognize the incomplete export file that results from a version miss match or not but you will realize it for sure as you will have no valid networks or scopes to import as you get to the last page of the DIW. I opened a bug report with Microsoft, they verified the issue but have no intention of fixing the bug.
Basically, use 2003 to do all your dumps if you are doing them remotely as it seems to work up through 2008 R2 for sure or do them locally on the server that is running DHCP so that you do not run into any version miss matches.
01-09-2013 09:59 AM
The diw won't work well with an incomplete export file. so yes, you need to use an older version of netsh with older win servers.
I would suggest opening a support case and sending them a copy of the incomplete export file. Infoblox should be able to patch the DIW so that at least it tells you the file is bad.
Hi, Thanks to all...
The MS DHCP Migration is successfully working with DIW and I did it, actually at the time of migration there is line parsing error coming.
And we need to delete those lines which raise error and after that you'll be able to import MS DHCP data to Infoblox.
Anyway thanks to all, because your input helps me in this.
08-04-2014 02:06 PM
08-06-2014 02:00 AM
I am not sure why you want to import the leases. I did some migrations for customers myself and never even thought of doing that.
Infoblox will try to ping the emty lease before it serves the address to the client device, therefore you wont get duplicates.
The ipam scan can provide another usefull insight.
Any reason on why you want to import the leases?
11-19-2014 12:25 AM
You can't migrate a Microsoft DHCP lease information from one Microsoft DHCP to another Microsoft DHCP. So the same applies that you can not migrate a Microsoft DHCP lease information from one Microsoft DHCP to an Infoblox DHCP.
Typically a DHCP migration would involve the steps below (but the order may differ from case to case based on your environment and how you setup DHCP):
- reduce the DHCP lease on Microsoft DHCP server to something short (maybe 1 hour)
- add the Infoblox DHCP into your IP Helper or DHCP relay
- export Microsoft DHCP server configuration using netsh dhcp server dump > msdhcp.txt (note that it is also possible to export Microsoft DHCP configuration direct from the DIW tool if you wish)
- use DIW to import the msdhcp.txt configuration into Infoblox DHCP as disabled scope
- when ready for cut over, disable the dhcp scope on Microsoft DHCP side and enable the dhcp scope on Infoblox DHCP
- once confirm clients are getting IP from Infoblox then remove the IP Helper or DHCP relay to Microsoft DHCP server AND reset the DHCP scope lease time on Infoblox DHCP side back to original value
- remove the DHCP scope from Microsoft DHCP side
If the steps above sounds jargon to you then I suggest you engage a good partner or Infoblox Professional services to finetune the steps to your environment.