Hey Folks,
I'm looking for a little help in implementing a way to make IP management a little easier for a fairly large VM deployment.
I will be deploying approximately 750 VM's over the next few months (hopefully). Up until know I have been managing the relatively small deployment with static IP's, but with the mass deployment that is being planned, this isn't really practical.
At first look, I thought this would be a good problem for IP pools, or Network Protocol Profiles as I believe it is now called. I have implemented a profile as directed in the documentation vSphere 5.5 Documentation Center and have verified the settings against various other mostly outdated blog posts on the topic. I even have a case open with vmware support on the topic, but after nearly 5 days, I haven't heard anything positive back from them yet.
So far I have tried with both Windows 2008 R2, and Windows 2012. The VM's have been in a vApp, with the necessary settings configured, and outside a vApp, but still with the vApp settings configure. No matter how I configure things, I can't get the guest to get an IP through a dynamic method.
Some of the documents I've read have stated that the IP that is assigned should be defined in an environment variable inside the guest using vmtoolsd –cmd “info-get guestinfo.ovfenv”. This returns some information, like the VM mac address, but no information about an IP address.
If IP Pools/NPP aren't the right way to handle this kind of deployment, I can't help but think there is something better than just standard DHCP servers.
We are currently using vSphere with Operations Management 5 Enterprise Plus running the latest patch level of esxi 5.5 and using VCSA at the latest patch level.
Thanks in advance.
Dustin