If your vApp is set up to allow it, and if you have the required privileges, you can edit how IP addresses are allocated for the vApp.
You cannot configure the IP allocation policy during the vApp creation process.
Before you configure the IP allocation policy, you must specify the IP protocol and the IP allocation scheme that the vApp supports.
If deployed the vApp from an OVF template, the IP allocation policy might still be editable.
Prerequisites
Required privilege:
Procedure
- Right-click a vApp in the inventory and click Edit Settings.
- In the Edit vApp dialogue box, click the IP Allocation tab.
This tab is only available in the
vSphere Client.
- In the Authoring section, define the IP protocol and the IP allocation scheme that the vApp supports.
The IP protocol and the IP allocation scheme determine what options for IP allocation are available.
A vApp can obtain its network configuration through the OVF environment or through a DHCP server. If you do not select any of these options, the IP addresses are manually allocated.
The IP protocols that a vApp can support are IPv4, IPv6, or both.
- In the Deployment section, select an IP allocation policy from the IP allocation drop-down menu.
Option |
Description |
Static - Manual |
IP addresses are manually configured. No automatic allocation is performed. |
Transient - IP Pool |
IP addresses are automatically allocated using IP pools from a specified range when the vApp is powered on. The IP addresses are released when the appliance is powered off. |
DHCP |
A DHCP server is used to allocate the IP addresses. The addresses assigned by the DHCP server are visible in the OVF environments of virtual machines started in the vApp. |
Static - IP Pool |
IP addresses are automatically allocated from the managed IP network range of vCenter Server at power-on, and remain allocated at power-off. |
Static - IP Pool and Transient - IP Pool have in common that IP allocation is done through the range managed by the vSphere platform as specified by the IP pool range in a network protocol profile. The difference is that for a static IP Pool, the IP addresses are allocated at first power-on and remain allocated, while for a transient IP Pool, the IP addresses are allocated when needed, typically at power-on, but released during power-off.
- Click OK.