The network profile information identifies the routed network properties, its underlying external network profile, and other values used in provisioning the network when using a third-party IPAM endpoint.



  1. Select Infrastructure > Reservations > Network Profiles.
  2. Click New and select Routed from the drop-down menu.
  3. Enter a name and, optionally, a description.
  4. If you have configured one or more third-party IPAM provider endpoints, select a third-party IPAM endpoint in the IPAM endpoint drop-down menu.

    When you select a third-party IPAM provider endpoint that you have registered in vRealize Orchestrator, IP addresses are obtained from the specified IPAM service provider. IP specifications such as subnet mask and DNS/WINS options are not available because their functions are controlled by the selected third-party IPAM endpoint.

  5. Select an existing external network profile from the External Network Profile drop-down menu.

    Only external network profiles that are configured to use the specified IPAM endpoint are listed and available to select.

  6. Select a value in the Range subnet mask text box drop-down menu to determine how many network subnets are created for provisioning.

    For example, enter

    The range subnet mask defines how you want to partition that space into individual address blocks that are allocated to every deployment instance of that network profile. When choosing a value for the range subnet mask, consider the number of deployments that you expect to use the routed network.

    A range is used for each deployment that uses a routed network profile. The number of available routed ranges is equal to the subnet mask divide by the range subnet mask, for example = 256.

  7. Click the IP Blocks tab to define an address space and manage one or more named ranges of static IPv4 network addresses.

    The available IP blocks are the source for IP ranges that are created or allocated for on-demand routing.

What to do next

Configure Routed Network Profile IP Ranges with a Third-Party IPAM Endpoint.