Migration of NSX-T TEPs to Static IP pool from DHCP on VCF 4.2

Products

• VMware Cloud Foundation

Issue/Introduction

VCF 4.2 supports bring up and workload domain deployment with Static IP pool for NSX-T TEPs instead of DHCP. The customers who have upgraded to VCF 4.2 and want to utilize this new feature it is preferable to deploy a new workload domain with Static IP pool so that VCF can manage the process including future cluster expansions.

The following is a manual procedure to move the existing cluster TEPs to Static IP from DHCP. The TEP IP assignment for future cluster expansion workflows needs to be done manually. If you use a cluster based TNP you will not need to manually assign TEP IP's for future cluster expansion, it will automatically select available IP's from your IP pool.

This is applicable to both VCF on Ready Nodes and VCF on VxRail on version 4.2 and for non-stretched clusters.

For VCF 5.2, please refer to Migration of NSX TEPs to Static IP pool from DHCP on VCF 5.2.

Environment

VMware Cloud Foundation 4.2

Resolution

Currently, there is no resolution.

PRE-REQUISITES

1. The VCF system management and workload domains has been completely upgraded to VCF 4.2.
2. There is no VCF workflow in progress or failed state.
3. This change will cause traffic disruption for the cluster and should only be performed during a maintenance window.

Steps to create a new IP Pool:

Use the following steps to create a new IP Pool in NSX Manager and assign a static IP address to these hosts:

1. Create an IP Pool in NSX Manager Networking -> IP Address Pools -> Add IP Address Pool.
2. Enter a Name (e.g. Static-TEP-Pool-A), then click on the Set link under the Subnets column.
3. At the Set Subnets properties page, click the Add Subnet button and choose an IP Ranges.
4. In the IP Ranges / Block Column click on the Select IP Ranges property box, then enter an IP Range (e.g. 172.16.14.101 – 172.16.14.108).
5. In the CIDR property box enter the CIDR (e.g. 172.16.14.0/24).
6. At the Gateway IP enter the default gateway address (e.g. 172.16.14.253).
7. When finished click Add, then Apply at the Set Subnets properties page.
8. At the IP Address Pools page, click Save.
9. Verify that the IP Address Pool Status column indicates Success for the newly created IP Address Pool.
10. Select the Transport Node Profile (System → Fabric → Profiles → Transport Node Profiles) associated with cluster to change IP Assignment from DHCP to IP Pool, and click Edit.
11. At the Edit Transport Node Profile properties page scroll down to the IP Assignment field, click on the drop-down box and select Use IP Pool.
12. At the IP Pool drop down box, select the newly create IP Pool then chose save.
13. Apply the Transport Node Profile on the cluster (System → Fabric → Nodes). Click on the Managed by drop down box to select your vCenter Server.
14. Click the check box to select the cluster being modified from DHCP to the new Static IP Pool, then click "Configure NSX".
15. At the NSX Installation properties page, click on the Transport Node Profile drop down box and select your Transport Node Profile, then click Apply.
16. Verify that IPs from the IP Pool have been assigned to transport nodes (System → Fabric → Nodes). Click on the Managed by drop down box to select your vCenter Server. On the Host Transport Nodes page, expand the cluster and examine the TEP IP Addresses column.
17. Click the check box to select the cluster for which the IP pool was modified. Click on Actions -> Detach Transport Node Profile.
18. For cluster expansion workflows like Add-Host use SDDC Manager to complete the Add-Host workflow. Then reapply Steps 10-17 mentioned above.