To create an isolation-backed network pool, create a VMWNetworkPool element whose type attribute has the value FencePoolType, and POST the element to your cloud's add link for networkPools.

An isolation-backed network pool is backed by one or more vCenter isolated networks, and provides traffic isolation from other hosts. The system provisions isolated networks automatically. Before creating an isolation-backed network pool, consider using the VXLAN pool that is created automatically when you create a Provider vDC

vSphere VXLAN networks are based on the IETF draft VXLAN standard. These networks support local-domain isolation equivalent to what is supported by vSphere isolation-backed networks. In addition, they provide:

■

logical networks spanning layer 3 boundaries

■

logical networks spanning multiple racks on a single layer 2

■

broadcast containment

■

higher performance

■

greater scale (up to 16 million network addresses)

Prerequisites
■

Verify that you are logged in to the vCloud API as a system administrator.

■

Verify that you know your cloud's add URL for networkPools. See Create a Network Pool.

■

Verify that at least one vCenter server attached to your cloud has network resources available. See Retrieve a List of Available Portgroups and Switches from a vCenter Server

Procedure
1

Choose a vCenter server to provide a switch for the network pool.

2

Create a VMWNetworkPool element that specifies the properties of the network pool.

3

POST the VMWNetworkPool element you created in Step 2 to your cloud's add URL for networkPools.

See the request portion of Example: Create an Isolation-Backed Network Pool.

Example: Create an Isolation-Backed Network Pool

Request:

POST https://vcloud.example.com/api/admin/extension/networkPools
Content-Type: application/vnd.vmware.admin.networkPool+xml
...
<?xml version="1.0" encoding="UTF-8"?>
<vmext:VMWNetworkPool
   xmlns:vmext="http://www.vmware.com/vcloud/extension/v1.5"
   xmlns:vcloud="http://www.vmware.com/vcloud/v1.5"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:type="vmext:FencePoolType"
   name="example-isolation-pool"
   type="application/vnd.vmware.admin.networkPool+xml">
   <vcloud:Description>Example Isolation-backed network pool</vcloud:Description>
   <vmext:FenceIdCount>5</vmext:FenceIdCount>
   <vmext:VlanId>0</vmext:VlanId>
   <vmext:VimSwitchRef>
      <vmext:VimServerRef
         type="application/vnd.vmware.admin.vmwvirtualcenter+xml"
         href="https://vcloud.example.com/api/admin/extension/vimServer/9" />
      <vmext:MoRef>dvs-39</vmext:MoRef>
      <vmext:VimObjectType>DV_SWITCH</vmext:VimObjectType>
   </vmext:VimSwitchRef>
</vmext:VMWNetworkPool>

The response includes a Task that tracks the creation of the network pool, and a set of Link elements that you can use to operate on or modify it.

Response:

201 Created
Content-Type: application/vnd.vmware.admin.networkPool+xml
...
<vmext:VMWNetworkPool
   xmlns:vmext="http://www.vmware.com/vcloud/extension/v1.5"
   xmlns:vcloud="http://www.vmware.com/vcloud/v1.5"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:type="vmext:FencePoolType"
   name="example-isolation-pool"
   id="urn:vcloud:networkpool:70"
   type="application/vnd.vmware.admin.networkPool+xml"
   href="https://vcloud.example.com/api/admin/extension/networkPool/70" ... >
   <vcloud:Link
      rel="up"
      type="application/vnd.vmware.admin.vmwNetworkPoolReferences+xml"
      href="https://vcloud.example.com/api/admin/extension/networkPoolReferences" />
   <vcloud:Link
      rel="edit"
      type="application/vnd.vmware.admin.networkPool+xml"
      href="https://vcloud.example.com/api/admin/extension/networkPool/70" />
   <vcloud:Link
      rel="remove"
      href="https://vcloud.example.com/api/admin/extension/networkPool/70" />
   <vcloud:Description>Example isolation-backed network pool</vcloud:Description>
   <vcloud:Tasks>
      <vcloud:Task
         status="running"
         ...
         operation="Creating Network Pool 70 ..."
         ...
      </vcloud:Task>
   </vcloud:Tasks>
   ...
</vmext:VMWNetworkPool>