Table 4.8 Example Of Interface Information About The Replacement Nic - Fujitsu PRIMEQUEST 2000 Series Administration Manual

CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6
4.6 Hot Replacement of PCI Express Cards
[Example of descriptions in the file after editing]
(In the example, eth0 was deleted, and eth1 is commented out.)
# PCI device 0x****:0x**** (e1000)
# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:0e:0c:70:c3:39", ATTR{type}=="1", ¥
KERNEL=="eth*", NAME="eth1"
:
:
The ¥ at the end of a line indicates that there is no line feed.
Do this editing for all the interfaces listed in the table created in step 2.
9. Reflect the edited rules in udev.
udevd reads the rules described in the rule file at its start time and then retains the rules in memory.
Simply changing the rule file does not mean the changed rules are reflected. Take action as follows to
reflect the new rules in udev.
# udevadm control -–reload-rules
10. Power on the PCI Express slot.
See 'Powering on and off PCI Express slots' in
11. Check whether there is an error in added FC card by MMB Maintenance Wizard.
This step is performed by the field engineer in charge of your system.
For details on the operation of replacement, see step 8 to 11 of 'Operation for Hot replacement of PCI
Express card by Maintenance Wizard' in
12. Collect the information associated with an interface on the replacement NIC.
An interface (ethX) is created for the replacement NIC at the power-on time. Make a table with
information about each interface created for the replacement NIC. Such information includes the interface
name, hardware address, and bus address. Use the bus address confirmed in step 1 and the same
procedure as in step 2.

TABLE 4.8 Example of interface information about the replacement NIC

Interface name
eth1
eth0
...
Confirm that a new hardware address is defined for the bus address. Also confirm that the assigned
interface name is the same as that before the NIC replacement.
Also confirm that the relevant entries in the above-described table were automatically added to the udev
function rule file, /etc/udev/rules.d/70-persistent-net.rules.
Note
The correspondence between the bus address and interface name may be different from that before NIC
replacement. In such cases, just proceed with the work. This is explained in step 13.
13. Deactivate each newly created interface.
The interfaces created for the replacement NIC may be active because power is on to the PCI Express
slot. In such cases, you need to deactivate them before changing the interface configuration file.
Execute the following command for all the interface names confirmed in step 11.
Example: eth0
# /sbin/ifconfig eth0 down
14. Confirm the correspondence between the interface names before and after the NIC replacement.
From the interface information created before and after the NIC replacement in steps 2 and 11, confirm
the correspondence between the interface names before replacement and the new interface names.
a. Confirm the correspondence between the bus address and interface name on each line in the table
created in step 2.
b. Likewise, confirm the correspondence between the bus addresses and interface names in the table
created in step 11.
c. Match the interface names to the same bus addresses before and after the NIC replacement.
"4.6.2 PCI Express card replacement procedure in
"4.6.2 PCI Express card replacement procedure in
Hardware address
00:0e:0c:70:c3:40
00:0e:0c:70:c3:41
...
99
Bus address Slot number
0000:0b:01.0 20
0000:0b:01.1 20
... ...
detail".
detail".
C122-E175-02EN