How to manually complete the Configure LACP for VDS task during a VMware Cloud Foundation workload domain creation workflow

Products

• VMware Cloud Foundation

Issue/Introduction

This article provides the steps needed to manually complete the Configure LACP for VDS task in a VMware Cloud Foundation workload domain creation workflow if it fails to complete successfully.

Environment

VMware Cloud Foundation 2.3.x
VMware Cloud Foundation 2.2.x

Resolution

Note: vmnic0 and vmnic1 are used to denote the two physical NICs present on each ESXi host. While these are the most likely names for these NICs, it is possible that they will be named differently. In that scenario, replace vmnic0 and/or vmnic1 with the appropriate physical NIC name.

1. Start the workload domain creation workflow via the SDDC Manger UI in a Chrome web browser.
2. The process will fail on the “Configure LACP for VDS” task.
3. Go the Chrome settings menu, expand the More Tools item and select Developer Tools. This can also be accessed by pressing Ctrl-Shift-I.
4. Go back to the main Workflows page, open the failed workflow and click the Restart Workflow button.
5. In the Developer Tools pane, select the Network tab, select the rerun item and then select the Headers sub-tab and make a note of the following values: Workflow ID, JSESSIONID, and X-CSRF-TOKEN.
6. Open a vSphere Web Client connection to one of the existing vCenter Servers in the VMware Cloud Foundation environment.
7. Click the Networking button. Expand the appropriate vCenter Server. Expand the Distributed Switch.
8. Select the vRack-DPortGroup-vMotion port group. Select the Configure tab and then select Policies.
9. Validate the following information:
   
   Active uplinks: Uplink1 (vmnic0), Uplink2 (vmnic1)
   Standby uplinks: vRack-LAG (no vmnic)
   Unused uplinks: blank
   
   Note: If the configuration does not match the preceding example, click the Edit button, select Teaming and Failover, and move the uplinks into the noted configuration. Click the OK button.
10. Repeat steps 8 and 9 for all other port groups except for the DVUplinks port group.
11. In the Navigator pane, select the appropriate distributed switch. From the Actions menu, select Add and Manage Hosts.
12. Select the Manage host networking radio button. Click the Next button.
13. Click the Attached hosts button. Select all affected hosts and click the OK button and then click the Next button.
14. Ensure only the Manage physical adapters check box is selected and then click the Next button.
15. Select vmnic0 under the first affected host and click the Assign uplink button.
16. Select vRack-LAG-0 and then click the OK button.
    
    Note: Ensure that the Uplink value for vmnic0 under the first affected host is now vRack-LAG-0. The Uplink value for the second vmnic (vmnic1) should be Uplink2.
17. Repeat steps 15 and 16 for any other affected hosts. Click the Next button.
18. Verify that there is no impact on the Analyze impact screen and click the Next button.
19. Click the Finish button on the Ready to complete page.
20. Select the vRack-DPortGroup-vMotion port group. Select the Configure tab and then select Policies. Click the Edit button.
21. Select Teaming and failover. Use the Up/Down arrows to modify the Failover order such that vRack-LAG is the only item under Active uplinks and all other uplinks are under Unused uplinks. Click the OK button.
22. Repeat steps 20 and 21 for all other port groups except for the DVUplinks port group.
23. In the Navigator pane, select the appropriate distributed switch. From the Actions menu, select Add and Manage Hosts.
24. Select the Manage host networking radio button. Click the Next button.
25. Click the Attached hosts button. Select all affected hosts and click the OK button and then click the Next button.
26. Ensure only the Manage physical adapters check box is selected and then click the Next button.
27. Select vmnic1 under the first affected host and click the Assign uplink button.
28. Select vRack-LAG-1 and then click the OK button.
    
    Note: Ensure that the Uplink value for vmnic1 under the first affected host is now vRack-LAG-1. The Uplink value for the first vmnic (vmnic0) should be vRack-LAG-0.
29. Repeat steps 27 and 28 for any other affected hosts. Click the Next button.
30. Verify that there is no impact on the Analyze impact screen and click the Next button.
31. Click the Finish button on the Ready to complete page.
32. Log in the SDDC Manager Controller virtual machine as the root user.
33. Issue a curl command similar to the following use the values noted in Step5:

 

curl -i -H "Accept: application/json" -H "Content-Type: application/json" -H "X-CSRF-TOKEN: <X-CSRF-TOKEN>" -H "Cookie: JSESSIONID=<JSESSIONID>" -X PUT https://<SDDC Manager Controller VM FQDN>:8443/vrm-ui/api/1.0/core/workflow/<Workflow-id>/rerun?skipFailedTask=true -k

Note: The following is an example with the values populated:
 
curl -i -H "Accept: application/json" -H "Content-Type: application/json" -H "X-CSRF-TOKEN: b928bee9-5ddf-4db1-b1ff-ff9be3d381ac" -H "Cookie: JSESSIONID=11FCE3706A3B09D632DEFC3BC245A420" -X PUT https://sddc-manager-controller.vcf.vxrack.local:8443/vrm-ui/api/1.0/core/workflow/35880bad-5b98-4a47-9f65-5421d5a7c32d-0/rerun?skipFailedTask=true -k 

34. The failed workflow should be running again in the SDDC Manager UI.

Additional Information

Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.2.1 environments upgraded from version 2.1.3b
Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.2.1 environments
Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.3.2 environments​