Fujitsu PRIMEQUEST 2000 Series Administration Manual page 175

Primequest 2000 series
Hide thumbs Also See for PRIMEQUEST 2000 Series:
Table of Contents

Advertisement

CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11
5.3 Removing PCI Express cards
# /sbin/vconfig rem ethX.Y
[For the interface under bonding]
If the bonding device is operating in mode 1, use the following steps for safety purposes on the SLAVE
interface to be removed to exclude it from operation. In any other mode, removing it immediately should
not cause any problems. Confirm that the SLAVE interface is the interface currently being used for
communication.
# cat /sys/class/net/bondY/bonding/active_slave
If the displayed interface name corresponds to the SLAVE interface to be removed, execute the following
command to switch to communicating now with the other SLAVE interface.
# /sbin/ifenslave -c bondY ethZ
(ethZ: bondY-configured interface not subject to hot
replacement)
Finally, remove the SLAVE interface being replaced, from the bonding configuration. Immediately after
being removed, the interface is automatically no longer used.
# /sbin/ifenslave -d bondY ethX
To remove the interfaces, including the bonding device, deactivate them collectively by executing the
following command.
# /sbin/ifdown bondY
6. Power off the PCI slot.
See 'Powering on and off PCI Express slots' in
7. After taking of all cables connected to the NIC, remove the NIC from the PCI Express slot.
8. Remove the interface configuration file.
Delete the configuration files of all the interfaces confirmed in step 2, by executing the following command.
# rm /etc/sysconfig/network/ifcfg-ethX
When deleting a bonding device, also delete the related bonding items (ifcfg-bondY files).
9. Edit the settings in the udev function rule file.
The entries of the interface assigned to the removed NIC still remain in the udev function rule file,
/etc/udev/ rules.d/70-persistent-net.rules. Leaving the entries will affect the determination of interface
names for replacement cards or added cards in the future. For this reason, delete or comment out those
entries.
The following example shows editing of the udev function rule file, /etc/udev/rules.d/70-persistent-
net.rules. (In this example, the file is edited when the eth10 interface is removed.)
[Example of descriptions in the file before editing]
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:0e:0c:70:c3:38", ATTR{type}=="1", ¥
KERNEL=="eth*", NAME="eth0"
:
:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:0e:0c:70:c3:40", ATTR{type}=="1", ¥
KERNEL=="eth*", NAME="eth10"
The ¥ at the end of a line indicates that there is no line feed.
[Example of descriptions in the file after editing]
The entries for the eth10 interface are commented out.
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:0e:0c:70:c3:38", ATTR{type}=="1", ¥
KERNEL=="eth*", NAME="eth0"
:
:
# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:0e:0c:70:c3:40", ATTR{type}=="1", ¥
KERNEL=="eth*", NAME="eth10"
"5.1.2 PCI Express card replacement procedure in
151
detail".
C122-E175-02EN

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Primequest 2400ePrimequest 2800ePrimequest 2800b

Table of Contents