How to adjust GI configuration after renaming a private Nic in Oracle 11gR2 RAC Environment

How to adjust GI configuration after renaming a private Nic in Oracle 11gR2 RAC Environment

Environment Description: AIX + 11gR2 RAC dual-node
Cause: the two NICs used for private network communication use a gigabit Nic. Now, they need to be replaced with a 10-Gigabit Nic. Because a 10-Gigabit Nic is a card and a port, the original Gigabit Nic is a card with two ports, and the slot on the host is limited, you must unplug the original Gigabit Nic to free up the location for the 10-Gigabit Nic, therefore, it is inevitable that the name of the 10g Nic recognized by ipvmgr in AIX will be different from the original one.

On the OS level, it seems to be a relatively simple action: Unplug the old network adapter-> press the new network adapter-> the OS recognizes the new network adapter and attaches it with an IP address, but the changes to GI are not small. After GI is installed and configured, the NIC name and subnet ID are recorded in OCR and GPnP profile. If the NIC name or subnet ID is changed, you must modify the content in OCR synchronously, otherwise the CRSD process will not start properly. In my case, the NIC name will change, so I will follow the steps below:

1. Back up the GPnP profile at two nodes.
Su-grid
Cp $ Oracle_HOME/gpnp/jqp750303/profiles/peer/profile. xml $ ORACLE_HOME/gpnp/jqp750303/profiles/peer/profile. xml.0310

2. Back up the NIC configuration in the current GI, as long as you run it on a node once.
Su-grid
Oifcfg getif <--- Note that this command must be executed only when GI is running
En15 10.11.176.0 global public
En16 2.2.144.0 global cluster_interconnect <--- this NIC will be replaced next

3. Stop GI-> stop-> unplug the Gigabit NIC-> press the 10-Gigabit NIC-> Start the host-> recognize the 10-Gigabit Nic
Remember the name of the 10g Nic on the OS: en17

4. Stop the service. Unplug the 10-Gigabit Nic and install it back into the Gigabit Nic. Then, start the host and recognize the Gigabit Nic again.
This step is to restore to the initial state to enable GI

5. Start GI
Crsctl start crs

6. Add the information of the 10g Nic to OCR
Su-grid
Oifcfg iflist <--- list NICs in the current OS environment
En15 10.11.176.0
En16 2.2.144.0 <--- en16 is the name of the Gigabit card

Oifcfg getif <--- list information of the network adapter saved in the current OCR
En15 10.11.176.0 global public
En16 2.2.144.0 global cluster_interconnect

Oifcfg setif-global en17/2.2.144.0: cluster_interconnect <--- write the name of the 10-gb Card Obtained in step 1, even if the en17 command does not exist.

Oifcfg getif <--- view the Modification result. The intranet Nic In OCR is changed to two, although en17 has not been installed yet.
En15 10.11.176.0 global public
En16 2.2.144.0 global cluster_interconnect
En17 2.2.144.0 global cluster_interconnect

7. Stop GI-> stop-> remove Gigabit NIC-> press 10g NIC-> Start host

8. Check whether the NIC name is correct after the host is started.
Oifcfg iflist
En15 10.11.176.0
En17 2.2.144.0 <--- en17 is a 10-gb card, and en16 disappears. this is OS-level information.

9. Start GI
Crsctl start crs

Oifcfg getif <--- there are two private network adapters in OCR
En15 10.11.176.0 global public
En16 2.2.144.0 global cluster_interconnect
En17 2.2.144.0 global cluster_interconnect

10. Delete the original Gigabit Nic
Oifcfg delif-global en16/2.2.144.0
Oifcfg getif
En15 10.11.176.0 global public
En17 2.2.144.0 global cluster_interconnect

11. If you are not at ease, restart GI again. If it succeeds, it will be OK.
Crsctl stop crs
Crsctl start crs

In this example, we need to describe one point,
Step 1 restart the host to see which name the 10 Gigabit NIC will be recognized after the OS is started;
Step 1 restart the host to restore the GI environment and start CRSD properly so that the 10g card information can be added to OCR in advance;
The 7th-step restart is the official installation of the 10-gb Nic;

Because the slot in my environment is not enough, it is caused by three reboots. If it is enough, the previous two reboots can be completely saved.