Table 4.7 Hardware Address Description Examples - Fujitsu PRIMEQUEST 2000 Series Administration Manual

CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6
4.6 Hot Replacement of PCI Express Cards
hardware address.
Example: eth0 [For a single interface]
# cat /sys/class/net/eth0/address
00:0e:0c:70:c3:38
Example: eth0 [For a bonding interface]
The bonding driver rewrites the values for the slave interface of the bonding device. Confirm the
hardware address by executing the following command.
# cat /proc/net/bonding/bondY
Ethernet Channel Bonding Driver .........
.
.
Slave interface: eth0
.
Permanent HW addr: 00:0e:0c:70:c3:38
.
.
You can use this procedure only when the bonding device is active. If the bonding device is not active
or the slave has not been incorporated, use the same procedure as for a single interface.
Also, the correspondence between the interface name and hardware address is automatically
registered by the system in the udev function rule file, /etc/udev/rules.d/70-persistent-net.rules.
Confirm that the ATTR{address} and NAME items have the same definitions as in the above output.
Example: eth0
grep eth0 /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥
ATTR{address}=="00:0e:0c:70:c3:38", ATTR{type}=="1", ¥
KERNEL=="eth*", NAME="eth0"
The ¥ at the end of a line indicates that there is no line feed.
You can always obtain the correct hardware address from the description in etc/udev/rules.d/70-
persistent-net.rules regardless of whether the interface is incorporated in bonding.
Confirm the hardware address of other interfaces by repeating the operation with the same command.
The following table lists examples of descriptions.
Interface name
eth0
eth1
...
The step above is used in creating the correspondence table in step 13. Prepare a table here so that
you can reference it later.
Note
In a replacement due to a device failure, the information in the table showing the correspondence
between the interface and the hardware address, bus address, and slot number may be inaccessible
depending on the failure condition. We strongly recommend that a table showing the correspondence
between the interface and the hardware address, bus address, and slot number be created for all
interfaces at system installation.
3. Execute the higher-level application processing required before NIC replacement.
Stop all access to the interface as follows. Stop the application that was confirmed in step 2 as using the
interface, or exclude the interface from the target of use by the application.
4. Deactivate the NIC.
Execute the following command to deactivate all the interfaces that you confirmed in step 2.
The applicable command depends on whether the target interface is a single NIC interface or the SLAVE
interface of a bonding device.
[For a single NIC interface]
# /sbin/ifdown ethX

TABLE 4.7 Hardware address description examples

Hardware address
00:0e:0c:70:c3:38
00:0e:0c:70:c3:39
...
121
Bus address Slot number
0000:0b:01.0 20
0000:0b:01.1 20
... ...
CA92344-0537-08