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 Bare metal Edge node cannot claim datapath interfaces (51726)

Last Updated: 2/16/2018Categories: TroubleshootingTotal Views: 7701Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Expected fastpath interfaces (fp-ethx) are not visible using the get interfaces command.

In the /var/log/syslog file, you see entries similar to:

<30>1 2017-11-21T03:06:13.204651+00:00 nsx-edge datapathd 9632 - -  EAL:   probe driver: 8086:1528 rte_ixgbe_pmd
<4>1 2017-11-21T03:06:13.204678+00:00 nsx-edge kernel - - - [ 1938.704675] vfio-pci 0000:04:00.0: Device is ineligible for IOMMU domain attach due to platform RMRR requirement.  Contact your platform vendor.     <<<--------
<30>1 2017-11-21T03:06:13.205030+00:00 nsx-edge datapathd 9632 - -  EAL:   set IOMMU type 1 (Type 1) failed, error 1 (Operation not permitted)
<30>1 2017-11-21T03:06:13.205075+00:00 nsx-edge datapathd 9632 - -  EAL:   set IOMMU type 8 (No-IOMMU) failed, error 19 (No such device)
<30>1 2017-11-21T03:06:13.205116+00:00 nsx-edge datapathd 9632 - -  EAL:   0000:04:00.0 failed to select IOMMU type
<30>1 2017-11-21T03:06:13.205157+00:00 nsx-edge datapathd 9632 - -  EAL: Error - exiting with code: 1
<30>1 2017-11-21T03:06:13.205197+00:00 nsx-edge datapathd 9632 - -    Cause: Requested device 0000:04:00.0 cannot be used
<31>1 2017-11-21T03:06:13.205386+00:00 nsx-edge datapathd 9636 - -  EAL: lcore 2 is ready (tid=6240a700;cpuset=[2])
<31>1 2017-11-21T03:06:13.205500+00:00 nsx-edge datapathd 9636 - -  EAL: lcore 7 is ready (tid=5fc05700;cpuset=[7])
<31>1 2017-11-21T03:06:13.205605+00:00 nsx-edge datapathd 9636 - -  EAL: lcore 4 is ready (tid=61408700;cpuset=[4])
<31>1 2017-11-21T03:06:13.205710+00:00 nsx-edge datapathd 9636 - -  EAL: PCI device 0000:04:00.0 on NUMA socket 0
<31>1 2017-11-21T03:06:13.205812+00:00 nsx-edge datapathd 9636 - -  EAL:   probe driver: 8086:1528 rte_ixgbe_pmd
<31>1 2017-11-21T03:06:13.205913+00:00 nsx-edge datapathd 9636 - -  EAL:   set IOMMU type 1 (Type 1) failed, error 1 (Operation not permitted)
<31>1 2017-11-21T03:06:13.206015+00:00 nsx-edge datapathd 9636 - -  EAL:   set IOMMU type 8 (No-IOMMU) failed, error 19 (No such device)
<27>1 2017-11-21T03:06:13.206116+00:00 nsx-edge datapathd 9636 - -  EAL:   0000:04:00.0 failed to select IOMMU type
<26>1 2017-11-21T03:06:13.206258+00:00 nsx-edge datapathd 9636 - -  EAL: Error - exiting with code: 1#012  Cause:
<26>1 2017-11-21T03:06:13.206356+00:00 nsx-edge datapathd 9636 - -  Requested device 0000:04:00.0 cannot be used
<29>1 2017-11-21T03:06:13.207573+00:00 nsx-edge systemd 1 - -  nsx-edge-datapath.service: Main process exited, code=exited, status=1/FAILURE
<30>1 2017-11-21T03:06:13.227255+00:00 nsx-edge datapath-systemd-helper 9663 - -  # Stopping at 2017-11-21T03:06:13.227098034Z

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

Cause

This issue occurs because some server vendors use Reserved Memory Range Reporting (RMRR) for healthcheck and direct access to some hardware. This prevents DPDK to claim the server physical NICs. This issue is known to affect at least the HP Proliant server series.

Resolution

Because RMRR is reliant on VT-d extensions being enabled, disabling VT-d in the BIOS allows the datapath to claim the expected interfaces normally. Disabling RMRR for specific interfaces differs depending on the platform and can be convoluted.  Disabling VT-d is a simpler approach applicable to the NSX Edge.

To resolve this issue, disable VT-d in the BIOS.

To disable on VT-D on HPE ProLiant GEN 10:

From the RBSU > System Utilties > System Configuration > BIOS/Platform Configuration (RBSU) > Virtualization Options.

Select Intel(R) VT-D to “Disabled”.

To Disable VT-d on an HPE ProLiant Gen 9 Server:

RBUS > System Options > Virtualization Options.

Select Intel(R) VT-d to “Disabled”.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Related Information

Because RMRR is reliant on VT-d extensions being enabled, disabling VT-d in the BIOS allows the datapath to claim the expected interfaces normally. For more information, see Advisory: (Revision) Linux - KVM Virtual Machine Does Not Start and Displays "Device is ineligible for IOMMU domain attach due to platform RMRR requirement" Message on HPE ProLiant Systems with an Intel Processor.

This article describes the exact same behavior when KVM is used to try to enable PCI passthrough on a NIC on specific HPE ProLiant Servers. The article also provides information on how to disable RMRR for specific interfaces, but they differ for different platforms and can be convoluted.  Disabling VT-d is a simpler approach applicable to the NSX Edge.

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
•
Download and Install VMware Fusion (2014097)

KB
•
ブランチ ターゲット インジェクションに対するハイパーバイザーアシストによるゲストの軽減 (52085)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T

Take Our Survey

Support Assistant