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

Creating an NSX-T VI workload domain in VMware Cloud Foundation 3.5.x fails (67144)

Last Updated: 4/18/2019Categories: InformationalTotal Views: 3649Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Creating an NSX-T VI workload domain in VMware Cloud Foundation 3.5.x fails on the "Attach pnics and vmknics to nvds" task or on the "Join vSphere hosts to NSX-T Fabric" task.

One or more hosts in the NSX-T VI workload domain does not have a physical NIC named vmnic0.

You see a message similar to the following in the /var/log/vmare/vcf/domainmanager/domainmanager.log file on the SDDC Manager VM:

2019-02-13 22:11:02.292 [vcf_dm,075e83c31e63551f,bc7accecc6341c84] [2-thread-7] ERROR [c.v.e.sddc.orchestrator.model.error.ErrorFactory]   [B44V60] UNABLE_TO_CONFIGURE_HOST_FABRIC Unable to configure fabric for  on nsxmanager-2.vcf.corp.local
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Unable to configure fabric for  on nsxmanager-2.vcf.corp.local

Caused by: com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => {
messages = [],
data = struct => {error_message=Physical NIC vmnic0 was not found on the host., httpStatus=BAD_REQUEST, error_code=9508, module_name=NsxSwitching service}
}

2019-02-13 23:08:39.603 [vcf_dm,1a037c291fa07497,535a14f875faca8a] [2-thread-9] ERROR [c.v.v.c.f.p.n.a.AttachPnicsAndVmknicsToNvdsAction]   UNABLE_TO_UPDATE_TRANSPORT_NODE
java.lang.RuntimeException: Partial physical nic configuration found present. Pnic array: [Pnic (com.vmware.nsx.model.pnic) => {
deviceName = vmnic4,
uplinkName = uplink-1
}], Input Vmnics: [vmnic0, vmnic5], Input Uplinks: [uplink-1, uplink-2]

java.lang.IllegalArgumentException: Number of vmnics and nvds uplinks do not match

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

Resolution

This is a known issue affecting VMware Cloud Foundation 3.5.x. This issue is resolved in VMware Cloud Foundation 3.7.

Workaround

Use the following steps to workaround this issue:

In vsphere client, go to the Networking view.

Expand the new vCenter Server, expand the Datacenter, right-click the Distibuted Switch, select Add and manage hosts.

Select Manage host network, click NEXT.

Click the Attached hosts button, select all affected hosts, click OK.

Click NEXT.

For each affected host, select one uplink (the lowest numbered one that is not named vmnic1) and then click the Unassign adapter link.

Click NEXT.

Click NEXT.

Click NEXT.

Click FINISH.

In the NSX Manager UI, go to Dashboard, click on Hosts.

If the failed task was "Join vSphere hosts to NSX-T Fabric", stay on the Hosts tab and check the box next to one of the affected hosts. Click the Actions dropdown and choose Configure as Transport Node.

Note: If the failed task was "Attach pnics and vmknics to nvds", skip to Step 24.

Enter the host's FQDN in the Name field.

Check the box next to the overlay transport zone in the list of Available Transport Zones. Click the right arrow button to move the overly transport zone into the Selected list.

Click on the N-VDS tab.

Click the dropdown next to N-VDS Name and select the available N-VDS.

Click the dropdown next to NIOC Profile and select nsx-default-nioc-hostswitch-profile.

Click the dropdown next to Uplink Profile and select nsx-default-uplink-hostswitch-profile.

Click the dropdown next to IP Assignment and select Use DHCP.

Click the dropdown next to Physical NICs and choose the NIC that was unassigned in Step 6.

Click the ADD button.

Repeat Steps 12 through 21 for any other affected hosts.

Click the RESTART TASK button next to the failed workflow in SDDC Manager.

Note: It is very likely that the "Attach pnics and vmknics to nvds" will fail as well. Refer to the following section to resolve that issue.

If the failed task was "Attach pnics and vmknics to nvds", go to the Transport Nodes tab. Check the box next to one of the affected hosts. Click the EDIT button.

Click on the N-VDS tab.

Click the dropdown next to Physical NICs and choose the NIC that was unassigned in Step 6.

Click the ADD button.

Repeat Steps 24 through 27 for any other affected hosts

Expand the Tasks pane in the SDDC Manager UI. Click on the Creating domain <domain name> task.

Note: A URL similar to the following is displayed in the browser:

https://sddc-manager.vcf.corp.local/ui/sddc-manager/administration/details/vrealize/vrealize-operations(monitoring-panel:monitoring/tasks/subtasks/a914be10-2fd1-11e9-979a-49712d01d7cc)

Note: In this example, a914be10-2fd1-11e9-979a-49712d01d7cc is the workflow id value.

Log in to the SDDC Manager VM as the vcf user and then issue the su - command to switch to the root user.

Issue a command similar to the following to create a json file with the workflow input:

curl -s http://localhost/domainmanager/internal/vault/a914be10-2fd1-11e9-979a-49712d01d7cc -XGET | json_pp > /tmp/add_vi_with_nsxt_input.json

Note: Replace a914be10-2fd1-11e9-979a-49712d01d7cc with the workflow id value obtained in Step 29.

Open /tmp/add_vi_with_nsxt_input.json with a text editor.

Fine the stanza that begins with MigrateFromVdsToNvds____10__listOfHosts. In this stanza, there will be a com.vmware.evo.sddc.common.plugin.model.contract.nsxt.HostInfo sub-stanza for each host. Update the vmnic# values in each host stanza as appropriate.

Save and close the file.

Issue a command similar to the following to update the input parameters to the workflow:

curl -s http://localhost/domainmanager/internal/vault/a914be10-2fd1-11e9-979a-49712d01d7cc -XPUT -H "Content-type: text/plain" -d @/tmp/add_vi_with_nsxt_input.json

Note: Replace a914be10-2fd1-11e9-979a-49712d01d7cc with the workflow id value obtained in Step 29.

Click the RESTART TASK button next to the failed workflow in SDDC Manager.

Related Information

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.

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)

KB
•
“由于数据库可用空间不足而关闭 VC (Shutting down the VC as there is not enough free space for the Database)”错误 (67017)

KB
•
VMware Horizon 월별 상위 추세 문서 (2087257)

KB
•
VMware View SVGA 驱动程序报告的版本高于安装的 View Agent 版本 (2078739)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-5 of 5

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 3.5.x

Take Our Survey

Support Assistant