CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6
4.7 Hot Addition of PCI Express cards
108
C122-E175-01EN
The explanation here assumes, as an example, that a name automatically assigned by the system is
used. To install a new interface, you can use a new interface name different from the one automatically
assigned by the system. Normally, there is no requirement on the name specified for a new interface. To
use an interface name other than the one automatically assigned by the system, follow the instructions in
step 14 of the ‘NIC replacement procedure’ in ‘4.6.4 Network card replacement procedure’.
The contents differ slightly depending on whether the interface is a single NIC interface or a SLAVE
interface of the bonding configuration.
[For a single NIC interface]
(Example)
DEVICE=eth1 <- Specified interface name
confirmed in step g
NM_CONTROLLED=no
BOOTPROTO=static
HWADDR=00:0E:0C:70:C3:40
BROADCAST=192.168.16.255
IPADDR=192.168.16.1
NETMASK=255.255.255.0
NETWORK=192.168.16.0
ONBOOT=yes
TYPE=Ethernet
[SLAVE interface of the bonding configuration]
(Example)
DEVICE=eth1 <- Specified interface name
confirmed in step g
NM_CONTROLLED=no
BOOTPROTO=static
HWADDR=00:0E:0C:70:C3:40
MASTER=bondY
SLAVE=yes
ONBOOT=yes
Note
Adding the bonding interface itself also requires the MASTER interface configuration file of the bonding
configuration.
10. To add a bonding interface, configure the bonding interface driver settings.
If the bonding interface has already been installed, execute the following command to chec k the
descriptions in the configuration file and confirm the setting corresponding to the bonding interface and
driver.
Example: Description in /etc/modprobe.d/bonding.conf
# grep -l bonding /etc/modprobe.d/*
/etc/modprobe.d/bonding.conf
Note
If the configuration file is not found or if you are performing an initial installation of the bonding interface,
create a configuration file with an arbitrary file name with the ".conf" extension (e.g., /etc/modprobe.d/
bonding.conf) in the /etc/modprobe.d directory).
After specifying the target configuration file, add the setting for the newly created bonding interface.
alias bondY bonding <- Add (bondY: Name of the newly
added bonding interface)
You can specify options of the bonding driver in this file. Normally, the BONDING_OPTS line in each
ifcfg- bondY file is used. Options can be specified to the bonding driver.
11. Activate the added interface.
Execute the following command to activate the interface. Activate all the necessary interfaces. The
activation method depends on the configuration.
[For a single NIC interface]
Execute the following command to activate the interface. Activate all the necessary interfaces.
# /sbin/ifup ethX
[For the bonding configuration]
For a SLAVE interface added to an existing bonding configuration, execute the following command to