Unsolved

This post is more than 5 years old

1329

December 29th, 2018 09:00

2 x Dell r720 server showing different naming with same NIC

I am using 2 Dell r720 with Intel X540/I350 Quad Port x2 10Gb x2 1Gb for tripleo overcloud compute deployment but facing a challenge because of different naming of NICs in each server. 1 server shows name as eno1... eno2 ..eno3 and eno4 and other server shows nic names as em1 --em2,,,em3 and em4.. Although I can use nic1 ,, nic2 ,, nic3 ,, nic4 in nic template and puppet maps nic2 to eno2 / em2 .. nic3 ...eno3/ em3 etc but nic which is eno1 and em1 is used for sriov in each server and re-naming of sriov nic is not supported. How I can make same names in both servers (even pr-os installation stage nics are being shown as em1 and eno1 in each server)

12 Elder

 • 

6.2K Posts

December 31st, 2018 10:00

Hello

The names used are determined by the OS. Based on the names being used it does not appear the two systems have identical configurations. If the hardware configuration or the operating system is different then you can get different naming conventions for the NICs.

Thanks

January 2nd, 2019 11:00

Hi; Thanks for your reply, I am using RHEL 7.5 in both servers. Apparently both R720 have same hardware configuration but one server showing eno1 and other is using em1 like notation.

January 3rd, 2019 02:00

[root@overcloud-novacompute-0 ~]# biosdevname -i eno1
em1

we can see biosdevname is returning em1 for nic which is named as eno1 ( how we can make it consistent as shown below for 2nd server)

[root@overcloud-contraildpdk-0 ~]# biosdevname -i em1
em1

12 Elder

 • 

6.2K Posts

January 3rd, 2019 09:00

If no one in the community wants to assist with configuring your OS then I suggest that you search knowledge articles for your OS. When I search for RHEL network device naming there are several relevant results. Here is an article that should help to get you started.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_device_renaming_procedure

No Events found!

Top