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

NSX-T workload domain creation fails when the ESXi hosts use physical NICs other than vmnic0 and vmnic1 (67413)

Last Updated: 3/31/2020Categories: PatchTotal Views: 3095Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX-T workload domain creation fails when the ESXi hosts use physical NICs other than vmnic0 and vmnic1

You see messages similar to the following in the /var/log/vmware/vcf/domainmanager/domainmanager.log file on the SDDC Manager VM:

2019-02-28 16:50:03.133 [vcf_dm,3ad1ccc782c22a05,4c40fe8456c6f0fc] [1-thread-5] ERROR [c.v.v.c.f.p.n.a.AttachPnicsAndVmknicsToNvdsAction] INPUT_PARAM_ERROR
java.lang.IllegalArgumentException: Number of vmnics and nvds uplinks do not match

2019-02-28 16:50:03.133 [vcf_dm,3ad1ccc782c22a05,4c40fe8456c6f0fc] [1-thread-5] ERROR [c.v.e.sddc.orchestrator.model.error.ErrorFactory] [NS72U7] INPUT_PARAM_ERROR Invalid parameter: {0}
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Invalid parameter: {0}
Caused by: 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

The steps noted in Creating an NSX-T VI workload domain in VMware Cloud Foundation 3.5.x fails (67144) can be used to workaround this issue in VMware Cloud Foundation 3.5.x.

If implementing the steps in Creating an NSX-T VI workload domain in VMware Cloud Foundation 3.5.x fails (67144) is not an option, the following steps can be used to workaround the issue:

Notes:

VMware Cloud Foundation must be at version 3.5.1 prior to installing the domainmanager patch. If the version is currently 3.5.0, upgrade to 3.5.1 before proceeding.

Take a snapshot of the SDDC Manager VM prior to starting this procedure.

Download vcf-domain-manager-3.5.1-12658897.noarch.rpm.

Use a file transfer utility to copy the vcf-domain-manager-3.5.1-12658897.noarch.rpm file to the /tmp folder on the SDDC Manager VM.

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

Issue the following command to install the vcf-domain-manager-3.5.1-12658897.noarch.rpm file:

rpm -Uvh /tmp/vcf-domain-manager-3.5.1-12658897.noarch.rpm

Note: You will see output similar to the following:

Preparing...                          ################################# [100%]
Updating / installing...
1:vcf-domain-manager-3.5.1-12658897################################# [ 50%]
+ test 2 -eq 1
+ systemctl daemon-reload
+ systemctl restart domainmanager.service
Cleaning up / removing...
2:vcf-domain-manager-3.5.0-11215621################################# [100%]

Issue the following command to validate that the version of the domainmanager component is upgraded to 3.5.0-11215621:

curl http://localhost/domainmanager/about

Note: You should see output similar to the following:

{
"id": "1f0a90ad-bf26-4358-a3bf-d217f7e8ffdc",
"name": "DOMAIN_MANAGER",
"version": "3.5.1-RELEASE-12658897",
"status": "ACTIVE",
"serviceUrl": "http://127.0.0.1:7200/domainmanager",
"description": "Domain Manager"

Issue the following command to make a copy of the /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml file:

cp -fp /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml.$(date +%Y%m%d)

Open the /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml file with a text editor.

Add the following to the end of the file:

DOMAIN_MANAGER:
- base: 3.5.1-RELEASE-12050813
alias:
- 3.5.1-RELEASE-12658897

Save and close the file.

Restart the lcm service by issuing the systemctl restart lcm command.

Note: Remove the snapshot of the SDDC Manager VM that was taken previously.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Storage I/O Control のメモリ アドミッション コントロールの問題 (67543)

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

Results 1-2 of 2

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