Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 4/3/2019Categories: How toTotal Views: 3330Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

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.

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.

Start the workload domain creation workflow via the SDDC Manger UI in a Chrome web browser.

The process will fail on the “Configure LACP for VDS” task.

Go the Chrome settings menu, expand the More Tools item and select Developer Tools. This can also be accessed by pressing Ctrl-Shift-I.

Go back to the main Workflows page, open the failed workflow and click the Restart Workflow button.

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.

Open a vSphere Web Client connection to one of the existing vCenter Servers in the VMware Cloud Foundation environment.

Click the Networking button. Expand the appropriate vCenter Server. Expand the Distributed Switch.

Select the vRack-DPortGroup-vMotion port group. Select the Configure tab and then select Policies.

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.

Repeat steps 8 and 9 for all other port groups except for the DVUplinks port group.

In the Navigator pane, select the appropriate distributed switch. From the Actions menu, select Add and Manage Hosts.

Select the Manage host networking radio button. Click the Next button.

Click the Attached hosts button. Select all affected hosts and click the OK button and then click the Next button.

Ensure only the Manage physical adapters check box is selected and then click the Next button.

Select vmnic0 under the first affected host and click the Assign uplink button.

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.

Repeat steps 15 and 16 for any other affected hosts. Click the Next button.

Verify that there is no impact on the Analyze impact screen and click the Next button.

Click the Finish button on the Ready to complete page.

Select the vRack-DPortGroup-vMotion port group. Select the Configure tab and then select Policies. Click the Edit button.

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.

Repeat steps 20 and 21 for all other port groups except for the DVUplinks port group.

In the Navigator pane, select the appropriate distributed switch. From the Actions menu, select Add and Manage Hosts.

Select the Manage host networking radio button. Click the Next button.

Click the Attached hosts button. Select all affected hosts and click the OK button and then click the Next button.

Ensure only the Manage physical adapters check box is selected and then click the Next button.

Select vmnic1 under the first affected host and click the Assign uplink button.

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.

Repeat steps 27 and 28 for any other affected hosts. Click the Next button.

Verify that there is no impact on the Analyze impact screen and click the Next button.

Click the Finish button on the Ready to complete page.

Log in the SDDC Manager Controller virtual machine as the root user.

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

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

Related 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​

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 2.3.x

VMware Cloud Foundation 2.2.x

Take Our Survey

Support Assistant