[Webinar] Streamline your web hosting managementRegister Today

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

VMWare 5.5 IP Pools vs Hyper-V VMM IP Pools

Could anyone summarize for me VMWare 5.5 IP Pools vs Hyper-V VMM IP Pools? I have been comparing the two, but I have not seen any good table or list that does this clearly for me. I know that Ip addresses allocated via transient IP address allocation are returned to the IP pool when a VMWare VM is turned off, does the same address get assigned to the VM if it is available when it is turned on? Hyper-V with VMM has the capablity to assign from a static IP address pool, where the VM is given a static IP address that it keeps as it should even if it is rebooted or migrated. It seems that VMWare has no such solution? This solution is great for automating the deployment of virtual machines in large hosting environments where virtual machines are being created frequently (this might look like unintented Hyper-V commercial, for the record; there are certain drawbacks in Hyper-V also in my opinion, depending on what is being evaluated).
0
itnifl
Asked:
itnifl
  • 2
2 Solutions
 
Uni KittyCommented:
Hi there! I cannot speak to the Hyper-V side, but from the VMware side you should be able to set up a static IP Pool, as of version 5.x you would use VMware's Network Protocol Profiles.

You can only use this from teh vSphere Web Client. This is an excerpt from their 5.5 Documentation Guide. 5.5 Documentation Guide.

Configure a Virtual Machine or vApp to Use a Network Protocol Profile in the vSphere Web Client
After you associate a protocol profile to a port group of a standard switch or a distributed switch, enable the usage of profile on a virtual machine that is connected to the port group and is associated with a vApp or has the vApp options enabled.
Prerequisites
Verify that the virtual machine is connected to a port group that is associated with the network protocol profile.
Procedure
1 Navigate to the virtual machine or the vApp in the inventory of the vSphere Web Client.
2 In the vSphere Web Client, open the settings of the vApp or the vApp Options tab of the virtual machine.
          ■ Right-click a vApp and select Edit settings.
          ■ Right-click a virtual machine, select Edit settings, and in the Edit Settings dialog box, click the vApp Options tab.
3 Click Enable vApp options.
4 Under Authoring, expand IP allocation and set the IP allocation scheme to OVF environment.
5 Under Deployment, expand IP allocation and set IP allocation to Transient - IP Pool or Static - IP Pool.
  Both the Static - IP Pool and Transient - IP Pool options allocate an IP address from the range in the network protocol      profile that is associated with the port group. If you select Static - IP Pool, the IP address is assigned the first time the virtual machine or vApp is powered on and the address persists across restarts. If you select Transient - IP Pool, an IP address is assigned every time the virtual machine or vApp is powered on.
6 Click OK.
When the virtual machine is powered on, the adapters connected to the port group receive IP addresses from the range in the protocol profile. When the virtual machine is powered off, the IP addresses are released.

I hope that helps!
Melly
0
 
itniflAuthor Commented:
Thank you for your information. I have been aware of vmwares IP pools, which I assume is what they call Network Protocol Profile here.  Going through the link you sent me, and the topics related to it, it seems that IP pools in vmware are something intended for use with vApps mainly. The same obvious direct intention is not found in Hyper-V/VMM.

Since it is the comparrison between Hyper-V/VMM in regards to VMWare IP Pools that I am looking for it would also be interesting to know how VMWare handles the assignment if IP addresses throughet the life-time of the VM. What happens when the VM is migratet or rebooted? Can you trust that the IP remains the same, or is the VMWare IP pool not consistent in its handouts of IPs under any circumstance?

In our Hyper-V/VMM environment, static IP's are handed out to new virtual machines  from a static IP-Pool. The vmm integration services will on boot set a static ip to the vm in the OS of the vm and mark the ip as taken in the pool. Would a similar usage be possible for any type of vm in vmware, or is there some caveat in regards to vApp being mentioned all over the menu selections when I configer a VM to use a IP pool?
0
 
Uni KittyCommented:
Since it is the comparrison between Hyper-V/VMM in regards to VMWare IP Pools that I am looking for it would also be interesting to know how VMWare handles the assignment if IP addresses throughet the life-time of the VM. What happens when the VM is migratet or rebooted? Can you trust that the IP remains the same, or is the VMWare IP pool not consistent in its handouts of IPs under any circumstance?

Yes  it is a similar functionality

Static - IP Pool
IP addresses are automaticaly allocated from the managed IP network range of vCenter Server at power-on, and remain allocated at power-off.

Regarding the second question
Would a similar usage be possible for any type of vm in vmware, or is there some caveat in regards to vApp being mentioned all over the menu selections when I configer a VM to use a IP pool?

It's seems a bit confusing because a vApp can be a single virtual appliance but it also can be a resource pool with multiple VMs.
https://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vm_admin.doc/GUID-E6E9D2A9-D358-4996-9BC7-F8D9D9645290.html

 In this documentation and example, I am referencing the latter. You would set up a resource pool (vApp) of VMs then set up static IP Pools using Network Protocol Profiles.  


Yes the IPs would be static even if powered off.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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