A network protocol profile contains a pool of IPv4 and IPv6 addresses. vCenter Server assigns those resources to vApps or to the virtual machines with vApp functionality that are connected to the port groups associated with the profile.

You can configure network protocol profile ranges for IPv4, IPv6, or both. vCenter Server uses these ranges to dynamically allocate IP addresses to the virtual machines within a vApp, when the vApp uses transient IP allocation policy.

Network protocol profiles also contain settings for the IP subnet, the DNS, and HTTP proxy servers.

Note: If you move a vApp or a virtual machine that retrieves its network settings from a protocol profile to another data center, to power on the vApp or virtual machine you must assign a protocol profile to the connected port group on the destination data center.

Procedure

  1. Navigate to a data center that is associated with a vApp.
  2. On the Configure tab, select More > Network Protocol Profiles.
    Existing network protocol profiles are listed.
  3. Click the Add button.
    The Add Network Protocol Profile wizard opens.
  4. On the Name and network page, enter the name of the network protocol profile and select the networks that use this profile. Click Next.
    A network can be associated with one network protocol profile at a time.
  5. On the IPv4 page, configure the relevant IPv4 settings.
    1. In the Subnet and the Gateway text boxes, enter the IP subnet and gateway.
    2. Select the DHCP Present radio button to indicate that the DHCP server is available on this network.
    3. In the DNS server addresses text box, enter the DNS server information.
    4. Enable the IP Pool option to specify an IP pool range.
    5. If you enable IP pools, enter a comma-separated list of host address ranges in the IP pool range text box.
      A range consists of an IP address, a pound sign (#), and a number indicating the length of the range.

      For example, 10.20.60.4#10, 10.20.61.0#2 indicates that the IPv4 addresses can range from 10.20.60.4 to 10.20.60.13 and 10.20.61.0 to 10.20.61.1.

      The gateway and the ranges must be within the subnet. The ranges that you enter in the IP pool range text box cannot include the gateway address.
    6. Click Next.
  6. On the IPv6 page, configure the relevant IPv6 settings.
    1. In the Subnet and the Gateway text boxes, enter the IP subnet and gateway.
    2. Select the DHCP Present radio button to indicate that the DHCP server is available on this network.
    3. In the DNS server addresses, enter the DNS server information.
    4. Enable the IP Pool option to specify an IP pool range.
    5. If you enable IP pools, enter a comma-separated list of host address ranges in the IP pool range text box.
      A range consists of an IP address, a pound sign (#), and a number indicating the length of the range.

      For example, assume that you specify the following IP pool range: fe80:0:0:0:2bff:fe59:5a:2b#10, fe80:0:0:0:2bff:fe59:5f:b1#2. Then the addresses are in this range:

      fe80:0:0:0:2bff:fe59:5a:2b - fe80:0:0:0:2bff:fe59:5a:34

      and

      fe80:0:0:0:2bff:fe59:5f:b1 - fe80:0:0:0:2bff:fe59:5f:b2 .

      The gateway and the ranges must be within the subnet. The ranges that you enter in the IP pool range text box cannot include the gateway address.
    6. Click Next.
  7. On the Other network configurations page, specify additional network configurations.
    1. Enter the DNS domain.
    2. Enter the host prefix.
    3. Enter the DNS search path.
      The search paths are specified as a list of DNS domains separated by commas, semi-colons, or spaces.
    4. Enter the server name and port number for the proxy server.
      The server name must include a colon and a port number. For example, web-proxy:3912 is a valid proxy server.
    5. Click Next.
  8. On the Name and Network Assignment page, review the settings and click Finish.

What to do next

You can now associate a prot group with a network protocol profile. For more details, see Associate a Port Group with a Network Protocol Profile in the vSphere Web Client.