Dell Acceleration Appliances for Databases Instrukcja Użytkownika Pobierz pdf (Strona 70)

SOLVING NETWORK MANAGER AND UDEV ISSUES WITH RHEL 6.4

Problem

When using the Mellanox ConnectX

-3 driver, mlx4_en, in RHEL, the Network Manager and udev

tools will incorrectly reset and set up the network devices. This results in the network devices being

renamed or incorrectly shut down, and possibly incapable of receiving frames.

Solution

Network Manager must be disabled, and one of the udev rules must be modified, as explained

below.

1. Follow the steps in this Red Hat link to stop the Network Manager service:

https://access.redhat.com/site/documentation/en-

US/Red_Hat_Enterprise_Linux_OpenStack_Platform/3/html/Installation_and_Configuration_G

uide/Disabling_Network_Manager.html)

2. Ensure that the Network Manager service is stopped by using the service command:

service NetworkManager stop

4. Ensure that the Network Manager service is disabled at startup by using the chkconfig

command:

chkconfig NetworkManager off

5. Open each interface configuration file on the system in a text editor. Interface configuration

files are found in the

/etc/sysconfig/network-scripts/ directory. They have names

of the form “

ifcfg-X”, where X is replaced by the name of the interface. Valid interface

names include

eth0, p1p5, and em1.

6. In each configuration file, ensure that the

NM_CONTROLLED configuration key is set to no

and the

ON_BOOT configuration key is set to yes.

NM_CONTROLLED=no

ONBOOT=yes

5. Ensure that the network service is started by using the service command:

service network start

6. Ensure that the network service is enabled at startup by using the chkconfig command:

chkconfig network on

7. To prevent udev from creating duplicate eth-X entries in /etc/udev/rules.d/70-

persistent-net.rules

, modify the following udev rule:

1 2 ... 65 66 67 68 69 70 71 72 73 74 75 ... 88 89

Brak uwag

Dell Acceleration Appliances for Databases Instrukcja Użytkownika Strona 70