Starting with VMware Cloud Director 10.5, you can migrate provider gateways from using IP blocks to using IP spaces.

When you prepare to migrate a provider gateway to using IP spaces, you must ensure that all existing IP blocks and static IP pools that are defined on the provider gateway are mapped to IP spaces. After setting up the IP spaces, you associate them to the gateway by creating an IP space uplink. To migrate IP prefixes, you must set up the IP prefixes sequences before starting the migration.

When you start the migration, VMware Cloud Director generates a violation report demonstrating if there are any mapping gaps that can cause the migration to fail.

One to one mappings of IP ranges are not strictly necessary for a successful migration. If a static IP pool was never used for allocating IP addresses, you can leave it out the IP space. However, the IP ranges that you configure as part of the preparation to migrate to IP spaces must match all IP addresses that are allocated from the provider gateway to its attached edge gateways, or the migration fails.

Note:

During the migration, VMware Cloud Director migrates only IP ranges that are mapped to the IP space uplinks on the provider gateway. This means that if any of the IP addresses on the edge gateway or the routed VDC networks associated with the provider gateway match with some private IP space within the organization, these edge gateway and networks IP addresses won't be migrated as part of the provider gateway migration.

VMware Cloud Director will try to migrate such IP addresses or networks only when you attempt to edit or update them. When you do this, this IP address or prefix gets marked as in-use, which results in a block of attempted updates by any other network or service that uses the same IP address or prefix. In this case, all the services and networks that are utilizing those duplicate IP addresses would continue to work without interruption.

Prerequisites

  1. Verify that your role includes the Provider Network:Edit and IP Spaces: Manage System rights.
  2. Create one or more IP spaces with scopes that cover all the IP blocks and static IP pools defined on the provider gateway and allocated to its attached edge gateways. To create the correct mappings, check the gateway's IP allocations and use those to define the necessary ranges and subnets. See Managing IP Spaces in the VMware Cloud Director Service Provider Admin Portal.

Procedure

  1. Add an IP space uplink to the provider gateway that you want to migrate to IP spaces.
    1. From the top navigation bar, select Resources and click Cloud Resources.
    2. In the left pane, click Provider Gateways.
    3. Under Configure, click IP Space Migration Prep.
    4. Click New.
    5. Enter a tenant-facing name for the uplink.
    6. Select the IP space that you created for the uplink and click Next.
    7. Click Finish.
  2. Click Migrate to IP Spaces and follow the prompts. Depending on the results of the static IP pools and network subnet violations checks, choose one of the options.
    Option Description
    No Violations Follow the prompts and finish the migration.
    Static IP Pool Violations
    1. Cancel the migration wizard.
    2. Edit the IP space that you created for the provider gateway to include the all IP addresses and ranges that are allocated to the provider gateway and are listed in violation.
    3. Attempt the migration again.
    Network Subnet Violations
    1. Cancel the migration wizard.
    2. Edit the IP space that you created for the provider gateway to include all IP prefixes that are allocated to the provider gateway and are listed in violation.
    3. Attempt the migration again.

Example: Mapping IP Blocks and Static IP Pools to IP Spaces

The following is an example of how to map the following defined IP blocks and static IP pools on an existing provider gateway to IP spaces.

IP Block Static IP Pools Local Usage of IPs
5.5.0.0/24 5.5.0.1-5.5.0.10, 5.5.0.20-5.5.0.40, 5.5.0.100-5.5.0.200 Internet
172.10.0.0/16 172.10.10.1-172.10.10.100 WAN
10.10.10.0/24 10.10.10.2-10.10.10.3, 10.10.10.100 Backup and other services
These three IP blocks logically map to three IP spaces to define as follows.
Name Description Type Range IP Prefix Sequence Internal IP Scope
Internet IP addresses to be used for accessing the internet Public 5.5.0.1-5.5.0.10, 5.5.0.20-5.5.0.40 - 5.5.0.0/24
WAN IP addresses to be used for accessing your corporate WAN Private 172.10.10.1-172.10.10.100 - 172.10.0.0/24
Services IP addresses to be used for service communication Shared 10.10.10.2-10.10.10.3 - 10.10.10.0/29
Note:
  • For the Internet IP space, the Static IP pool range 5.5.0.100-5.5.0.200 was not used for any IP allocations, so the provider left it out of the new IP space range. There are no networks using this IP Space so no IP prefix sequence was defined. To not include this range in the IP space, the provider must first remove it from the IP block definition.
  • For the WAN IP space, the scope was changed to be more narrow than what was defined in the IP block.
  • For the services IP Space, only one of the Static Pools ranges were used to define the IP space range and the scope was reduced.