ESXi 7.x in dual-stack (IPv4 + IPv6) management network configuration cannot be added to to VC 7.0 vDS on IPv6

Products

• VMware vSphere ESXi

Issue/Introduction

If the ESXi 7.x host in dual-stack (IPv4 + IPv6) management network configuration is migrated with its vmnics and management kernel port to a vCenter 7.0 vDS on IPv6, the configuration reverts after within about 1 minute.

vmkernel.log:

    cpu22:2359174 opID=83492235)Tcpip: 749: Adding IPv6 addr xxxx:xxxx:xxxx::y/64 to 'vmk0'
    cpu22:2359174 opID=83492235)Config: 871: "ManagementIface" = "vmk0", Old value: "" (Status: 0x0)
    cpu29:2442030)WARNING: Tcpip: 1333: failed to unset gateway (error = 0x31)  

vpxa.log:

    [/context]' received while invoking commitTransaction on vim.host.NetworkSystem:networkSystem
    2020-09-28T16:27:24.644Z info vpxa[2123915] [Originator@6876 sub=vpxLro opID=62725454] [VpxLRO] -- FINISH lro-136
    2020-09-28T16:27:24.644Z info vpxa[2123915] [Originator@6876 sub=Default opID=62725454] [VpxLRO] -- ERROR lro-136 -- networkSystem -- vim.host.NetworkSystem.commitTransaction: vmodl.fault.SystemError:
    --> Result:
    --> (vmodl.fault.SystemError) {
    --> faultCause = (vmodl.MethodFault) null,
    --> faultMessage = <unset>,
    --> reason = "Transaction has rolled back on the host."


Note: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.

Environment

VMware vSphere 7.0.x

Cause

Internal bug identified - IPv6 configuration on vmkernel interfaces become disconnected when migrated to version 7.0.x vDS. 

 

Resolution

This issue is resolved in vSphere/ESXi version 7.0.3. 

Workaround:
If the vCenter is configured with IPv4, the issue does not occur.

Additional Information

Please note, a vCenter in dual-stack configuration is not supported

Impact/Risks:
ESXi management network cannot be migrated to a vCenter 7.x vDS if the vCenter NIC is IPv6 configured.