Fujitsu 2000 SERIES Manual Do Utilizador
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6
4.3 Hot replacement of IOU
4.3 Hot replacement of IOU
71
C122-E175-01EN
ATTR{address}=="00:19:99:d7:36:21", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth2"
# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:19:99:d7:36:22", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth3"
:
:
KERNEL=="eth*", NAME="eth2"
# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:19:99:d7:36:22", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth3"
:
:
The ¥ at the end of a line indicates that there is no line feed.
Example of descriptions in the file after editing
# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:19:99:d7:36:21", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth3"
# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:19:99:d7:36:22", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth2"
:
:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:19:99:d7:36:21", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth3"
# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:19:99:d7:36:22", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth2"
:
:
The ¥ at the end of a line indicates that there is no line feed.
b Execute below command, reflecting the edited rules
# udevadm control --reload-rules
c
Assert uevent to target interfaces (in this case, eth2 and eth3). Note to specify the interface name
before changing at this time. For example, assert uevent with specifying eth2 when changing eth2 to
eth10.
before changing at this time. For example, assert uevent with specifying eth2 when changing eth2 to
eth10.
# echo add > /sys/class/net/eth2/uevent
# echo add > /sys/class/net/eth3/uevent
# echo add > /sys/class/net/eth3/uevent
Interpret properly eth2 or eth3 to appropriate name.
d Check whether the interface name is changed to desired name.
4. Edit the saved interface configuration file.
Write a new hardware address to replace the old one. In "HWADDR," set the hardware address of the
replacement NIC in TABLE 6.4 Example of entered values corresponding to the interface names before
and after NIC replacement or TABLE 6.5 Confirmation of interface names. Also, for SLAVE under
bonding, the file contents are partly different, but the lines to be set are the same.
Example:
replacement NIC in TABLE 6.4 Example of entered values corresponding to the interface names before
and after NIC replacement or TABLE 6.5 Confirmation of interface names. Also, for SLAVE under
bonding, the file contents are partly different, but the lines to be set are the same.
Example:
DEVICE=eth0
NM_CONTROLLED=no
BOOTPROTO=static
HWADDR=2c:d4:44:f1:44:d2
BROADCAST=192.168.16.255
IPADDR=192.168.16.1
NETMASK=255.255.255.0
NETWORK=192.168.16.0
ONBOOT=yes
TYPE=Ethernet
NM_CONTROLLED=no
BOOTPROTO=static
HWADDR=2c:d4:44:f1:44:d2
BROADCAST=192.168.16.255
IPADDR=192.168.16.1
NETMASK=255.255.255.0
NETWORK=192.168.16.0
ONBOOT=yes
TYPE=Ethernet
Do this editing for all the saved interfaces except for the interface with no change of hardware address.
5. Restore the saved interface configuration file to the original file.
Restore the interface configuration file saved to the save directory to the original file by executing the
following command.
following command.
# cd /etc/sysconfig/network-scripts/temp
# mv ifcfg-ethX ..
(following also executed for bonding configuration)
# mv ifcfg-bondX ..
# mv ifcfg-ethX ..
(following also executed for bonding configuration)
# mv ifcfg-bondX ..
6. Activate the replaced interface.
The method for activating a single NIC interface differs from that for activating the SLAVE interfaces