• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Network Application Monitoring /
  • NAM Open Q&A /
avatar image
Question by Gomez H. · Oct 03, 2014 at 03:45 PM ·

How to check that a NIC is supported by AMD's custom driver

First of all you better have a recommended NIC card from the "Hardware Recomendation" manual provided with DCRUM Documentation.

But, inside the technical, here is what DCRUM AMD does under the hood.

The supported (*1) NIC info is located at the file /usr/lib/perl5/site_perl/supported_devs.pm

(*1 = supported by the hardware and RHEL (Red Hat), not by AMD, yet. Keep reading)

The data is listed in the way:

$pciid_drivers{"8086:10da"}= ["e1000e", "e1000e_rtm"];

where

  • {"8086:10da"}

is the PCI vendor ID and the device ID (this is NOT the MAC Address Vendor ID !!!)  and

  • ["e1000e", "e1000e_rtm"];

is the list of available drivers when the NIC is supported (*1, remember).

So, how can we get the right PCI Vendor ID and device ID ? (we need this info to check later with AMD supported NICs)

Currently the only way I know to get this info is to ask directly to the card while installed on AMD.

Run the commands lspci and lspci -nn to get this info.

  • lspci will list all PCI devices connected to the AMD. Look for the NIC description and take note of the first digits on the left like 4c:00.0.
  • lspci -nn will give you the PCI vendor ID and the device ID like 4c:00.1 8086:10fb, and will be listed exactly as before so you just need to mach both listings.

So, having the PCI Vendor ID and device ID of your NIC, look for it in the supported_devs.pm

Be careful when reading that file because some cards are supported only in 64 bits. Check the code of the file to understand if your NIC is supported in your 32 or 64 bits environment and depending on the version of your RHEL.

Additional notes:

  • You can check your RHEL version running: cat /etc/redhat-release
  • Finally here is an interesting link to check PCI Vendor IDs and device IDs: http://www.pcidatabase.com/
  • Another link for PCI devices recognition on Debian: https://wiki.debian.org/HowToIdentifyADevice/PCI

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

4 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Tomasz N. · Nov 18, 2014 at 10:14 PM

Small update - supported_devs.pm file may be also located in

/usr/local/share/perl5/

You may also do

find / -name supported_devs.pm 

to locate it.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Chris Z. · Nov 19, 2014 at 07:49 AM

Hello,

Please check the list from "Data Center Real User Monitoring Hardware Recommendations"

https://community.compuwareapm.com/community/download/attachments/146114077/DCRUM_HardwareRecommendations.pdf?version=4&modificationDate=1394758167700&api=v2

 

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Gomez H. · Nov 19, 2014 at 01:29 PM

Great comments, guys! Thanks!

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Grzegorz S. · Nov 25, 2014 at 09:04 PM

Just a slight correction to the lines below:

The supported (*1) NIC info is located at the file /usr/lib/perl5/site_perl/supported_devs.pm

(*1 = supported by the hardware and RHEL (Red Hat), not by AMD, yet. Keep reading)

In fact if the device ID is found in the supported_devs.pm it indicates that the NIC is supported by the AMD (rtm custom driver can be used).

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

4 People are following this question.

avatar image avatar image avatar image avatar image

Forum Tags

esm siebel Dynatrace Managed license nam probe wan citrix dna rest api configuration mq alerting NAM 2018 dashboard dcrumadvisory reports css nam universal decode database mobileapp RUM ads sap nam console scripting nam server sequence transactions nam 2019 upgrade
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A