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

In-band management configuration fails on Bare Metal Edge with Mellanox NICs (75247)

Last Updated: 11/16/2022Categories: TroubleshootingTotal Views: 9848Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following conditions are met

- NSX-T Data Center 2.5.0 with Bare Metal Edge

- An attempt was made to configure in-band management on Mellanox NICs which failed with an error. Out of band management was configured instead.

- On the Edge Transport Nodes UI

Configuration Status is "Success"
Node Status is "Up"
Tunnels are "Not Available"

- On the Edge cli the following commands show no output

bmedge> get tunnel-ports
bmedge> get vteps
bmedge> get logical-router
Logical Router
UUID                  VRF    LR-ID  Name                    Type                Ports

- Edge syslog log messages are similar to this example

2019-10-11T09:11:41 nsx-edge NSX 3631 FABRIC [comp="nsx-edge" level="ERROR" errorCode="EDG0400432"] kni alloc failed.
2019-10-11T09:11:41 nsx-edge NSX 3631 FABRIC [comp="nsx-edge" level="ERROR" errorCode="EDG0400102"] Failed to create kni port eth0

Cause

In-band management is not supported on Mellanox NICs.
If an attempt is made to configure it, an error will be triggered however some stale configuration may block the remaining configuration of the Bare Metal Edge.

Resolution

This issue is resolved in NSX-T Data Center 2.5.1 and above.

Workaround

Clear the stale data claiming the Melannox NIC for management

clear interface ethX.<MGMT_VLAN_ID>
restart service dataplane

Configure out-of-band management on the server or configure in-band management on a non-Mellanox NIC.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
在任一节点上重新启动 Docker 服务后，服务不正常，并且部署失败 (75183)

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

KB
•
如何从 VMware Online Store 购买产品升级 (2033491)

KB
•
HW-120808/HW-121298：iOS で VMware Verify 4.0.1 への更新で、再インストールまたは再登録が必要になることがある (79845)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.5.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant