Fujitsu PRIMEQUEST 2000 Series Administration Manual page 125

CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6
4.3 Hot replacement of IOU
# /sbin/vconfig add ethX Y
# /sbin/ifup ethX.Y
(enter command to set VLAN option as needed)
For SLAVE under bonding
Execute the following command to incorporate the SLAVE interface into the existing bonding
configuration. Incorporate all the necessary interfaces.
# /sbin/ifenslave bondY ethX
The VLAN-related operation is normally not required because a VLAN is created on the bonding device.
7. Mount all cables connected to the particular PCIC.
This step is performed by the field engineer in charge of your system.
Note
In GLS configuration with NIC switching way, you do not need to perform this step.
8. Remove the directory to which the interface configuration file was saved.
After all the interfaces to be replaced have been replaced, remove the save directory created in step 5 in
4.3.1 Preparation for IOU hot replacement
# rmdir /etc/sysconfig/network-scripts/temp
9. Execute the higher-level application processing required after NIC replacement.
Perform the necessary post processing (such as starting applications or restoring changed settings) for
the operations performed for the higher-level applications in step 3 in
replacement.
iSCSI (NIC) on the IOU
If replace iSCSI (NIC) on the IOU, you have to take not only the same steps of 'NIC on the IOU (including
Onboard NIC)' but also takes steps below in step 8 of that.
1. To restore access to the iSCSI connection interface, perform the following.
a. Confirm the state of multiple path by DM-MP (*1) or EMPD (*2).
b. Use the iscsiadm command to log in to the path (iqn) through which the replacement iSCSI card is
routed, and reconnect the session.
Example which confirms the state of session before connecting:
# /sbin/iscsiadm -m session
tcp: [1] 192.168.1.64:3260,1 iqn.2000-
09.com.fujitsu:storage-system.eternus-
dx400:00001049.cm0ca0p0
Example which login path going through a NIC to be replaced:
# /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage-
system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260
–-login
c. Use the iscsiadm command to confirm that the target session has been activated.
Example which confirms the state of session after connecting
# /sbin/iscsiadm -m session
tcp: [1] 192.168.1.64:3260,1 iqn.2000-
09.com.fujitsu:storage-system.eternus-
dx400:00001049.cm0ca0p0
tcp: [3] 192.168.2.66:3260,3 iqn.2000-
09.com.fujitsu:storage-system.eternus-
dx400:00001049.cm1ca0p0
d. You can confirm the activation of sessions on multipath products using DM-MP or ETERNUS
multidriver.
*1: Write down the DM-MP display contents at the session activation.
Example of DM-MP display before connecting path
# /sbin/multipath -ll
mpath1 (36000b5d0006a0000006a104900000000) dm-0
FUJITSU,ETERNUS_DX400
[size=50G][features=0][hwhandler=0][rw]
¥_ round-robin 0 [prio=1][active]
by executing the following command.
99
4.3.1 Preparation for IOU hot
CA92344-0537-08