To enable IPv6 communication between NSX Manager and transport nodes, you can use the following workflow.
Procedure
- Configure the IPv6 address on the management interface of the transport nodes:
- For ESX transport nodes, you can configure the static IP address or with DHCP.
Note: It is recommended to use the static IP address.
-
For NSX Edge transport nodes, you can only manually configure the IPv6 address.
For greenfield deployments, you can:
- Create a new NSX Edge node with static IPv4 and static IPv6.
- Create a new NSX Edge node with DHCPv4 and static IPv6.
For brownfield deployments, you can:
- Configure a static IPv6 NSX Edge node to become dual stack (static IPv4 and IPv6).
See Configure a Brownfield NSX Edge Transport Node with IPv6.
- Configure a DHCP IPv6 NSX Edge node to become dual stack (DHCP IPv4 and static IPv6).
See Configure a Brownfield NSX Edge Transport Node with IPv6.
- In the NSX CLI, edit and remove the NSX Edge node IPv6 address.
Note: You cannot configure NSX Edge transport nodes as IPv6 only.
- For ESX transport nodes, you can configure the static IP address or with DHCP.
- For greenfield NSX Managers, configure the IPv6 address on the management interface of the NSX Manager by creating a new NSX Manager node with static IPv4 and IPv6.
- For brownfield NSX Managers, configure the IPv6 address depending on the brownfield scenario:
- For brownfield NSX Managers configured as IPv4 only from an NSX version prior to NSX 4.1, configure the IPv6 address through the CLI.
- For brownfield NSX Managers configured as dual stack from NSX 4.0.0.1, upgrade the NSX Manager cluster to NSX 4.1.
See the NSX Upgrade Guide.
Important: It is required for all NSX Managers in the cluster to be upgraded to NSX 4.1 or later. If any of the NSX Manager nodes in the cluster are not upgraded to NSX 4.1 or later, then the communication between NSX Manager and transport nodes will use IPv4 and not IPv6.