Vsphere 6.7 - Ip allocation policy not used

[sebastiencalca]

Hi guys,

I need some help/advice to use IP configuration via a Network Protocol Profile configuration and the VAPP options.

As described here 

we configured a Network Protocol Profile with an IP range and assigned it to a network.

Next we enabled the Vapp options with a IP allocation on our VM as follow:

IP protocol: IPv4
IP allocation scheme: OVF environment
IP protocol: IPv4
IP allocation: Static - IP Pool

therefore, a warning message appears even if the policy is assigned to our network : "One or more of the assigned networks do not have an IPv4 range configured for allocating IP addresses. To remove this warning, either configure an IPv4 range in the Network Protocol Profile configuration of the datacenter or choose another IP allocation policy." 

We tried to launch our VM, but no ip is attributed to our nic. Do I miss some configuration point ?

We also tried to add our vm into Vapps (even we don't want to use them if we could). With it the Vapps no warning is showed, but we don't have any IP attribution either.

Thanks for your Help.

Sebastian

[thweber-wu]

We have the exact same warning in our vAPP Options Menu!
We can assign IPs to our VMs via the properties in the vAPP Options, but we want to use Static - IP Pool like stated here:
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-DBF79F52-925A-4... 

g. In the Deployment section, set the IP allocation to Transient - IP Pool or Static - IP Pool.

Our problem is, that our IPs behave like transient, even though it is configured as Static - IP Pool. The IPs increment on every reboot of the VMs.

We use the property key "guestinfo.interface.0.ip.0.address" to setup our VMs with cloud-init like they do in this article:
https://www.virtualthoughts.co.uk/2020/03/29/rancher-vsphere-network-protocol-profiles-and-static-ip... 
The default value for the property then is: ${autoIp:YOUR_PORT_GROUP_HERE}

Cheers!