How to change InfiniBand bonding on Exadata X4-2 from active/active to active/passive

Asset ID:	1-71-1642955.1
Update Date:	2015-04-16
Keywords:

Solution Type Technical Instruction Sure

Solution 1642955.1 : How to change InfiniBand bonding on Exadata X4-2 from active/active to active/passive

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]
Oracle Exadata Storage Server Software - Version 11.2.3.3.0 to 12.1.2.1.1 [Release 11.2 to 12.1]
Exadata X4-2 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Platinum Services - Version N/A to N/A
Linux x86-64

Goal

In the default deployment of the Exadata X4-2 Database Machine, the InfiniBand bonding is set up in the active/active mode, on all database servers and all storage cells. Earlier models of the Exadata Database Machine (V2, X2-2, X3-2) have the InfiniBand set up in the active/passive mode. If there is a requirement to have a single cluster with a combination of X4-2 and V2/X2-2/X3-2, the InfiniBand bonding needs to be set up in active/passive mode on all X4-2 database servers. This is normally done by Oracle Advanced Customer Support team at the deployment time.

If the requirement to connect X4-2 to V2/X2-2/X3-2 was not known at the deployment time, the Exadata X4-2 Database Machine would have been deployed with the InfiniBand bonding in active/active mode. In that case the InfiniBand bonding needs to be changed to active/passive mode on X4-2 database servers. This document describes the procedure to accomplish this task. Note that there is no need to make any changes on the X4-2 storage cells.

The procedure applies to Exadata image version 11.2.3.3.0 and later, and Clusterware version 11.2.0.1 and later. Please refer to Exadata Database Machine and Exadata Storage Server Supported Versions [Doc ID 888828.1], for a minimum Exadata image and Clusterware versions, for specific product features.

The document shows an example of the procedure on a quarter rack Exadata X4-2 Database Machine, running Exadata image version 12.1.1.1.0.131219 and Clusterware version 12.1.0.1.2. The commands, server names, paths and IP addresses are provided for reference purposes only. Make sure to use the correct values for your system.

Note that there is no need to make any changes on the X4-2 storage cells.

Solution

SECTION I - The backup

1. Backup the root file system

Use the /opt/oracle.SupportTools/dbserver_backup.sh script to backup the root file system.

[root@exadb01 ]# /opt/oracle.SupportTools/dbserver_backup.sh
[INFO]
[INFO] Start to backup root /dev/VGExaDb/LVDbSys1 and boot partitions
[INFO] Check for Volume Group "VGExaDb"
...
[INFO] Root file system is mounted to /dev/VGExaDb/LVDbSys1
[INFO] The active root partition /dev/VGExaDb/LVDbSys1 has proper label DBSYS
[INFO] The backup partition /dev/VGExaDb/LVDbSys2 has no label
[INFO] LVM root partition size: 30.00G (62914560S)
[INFO] Spare root partition already exists
[INFO] LVM spare root partition size: 30.00G (62914560S)
[INFO] Compare versions between active and spare root partitions
[INFO] Image version on the root partition is 12.1.1.1.0.131219
[INFO] Image version on the spare root partition is 11.2.3.3.0.131014.1
[INFO] Create ext3 file system on spare root partition /dev/VGExaDb/LVDbSys2
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3932160 inodes, 7864320 blocks
393216 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
240 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
...
/boot/grub/fat_stage1_5
/boot/.vmlinuz-2.6.39-400.128.1.el5uek.hmac
/boot/lost+found/
/boot/I_am_hd_boot
/boot/vmlinuz-2.6.39-400.128.1.el5uek
~
[INFO] Unmount snapshot partition /mnt_snap
[INFO] Remove snapshot partition /dev/VGExaDb/LVDbSys1Snap
Logical volume "LVDbSys1Snap" successfully removed
[INFO] Save partition table of /dev/sda in /mnt_spare/part_table_backup.txt
[INFO] Save lvm info in /mnt_spare/lvm_info.txt
[INFO] Unmount spare root partition /mnt_spare
[INFO] Backup of root /dev/VGExaDb/LVDbSys1 and boot partitions is done successfully
[INFO] Backup partition is /dev/VGExaDb/LVDbSys2
[INFO] /boot area back up named boot_backup.tbz (tar.bz2 format) is on the /dev/VGExaDb/LVDbSys2 partition.
[INFO] No other partitions were backed up. You may manually prepare back up for other partitions.

Perform the same on all database servers in the X4-2 cluster.

2. Backup the Oracle Cluster Registry (OCR)

To perform the OCR backup, run the following command as privileged user (root):

[root@exadb01 ]# /u01/app/12.1.0.1.2/grid/bin/ocrconfig -manualbackup

exadb02 2014/04/01 04:59:29 /u01/app/12.1.0.1.2/grid/cdata/dmorl4-scan/backup_20140401_045929.ocr
exadb02 2014/03/25 21:23:15 /u01/app/12.1.0.1.2/grid/cdata/dmorl4-scan/backup_20140325_212315.ocr
...

Note that the backup command was run from database server 1, and that the backup was automatically created on database server 2.

3. Backup the databases

Make sure to have the current whole database backups for all databases running in the X-2 cluster.

4. Backup network interface information

Copy ifcfg-ib0 and ifcfg-ib1 to a backup directory on all database servers in the X4-2 cluster:

[root@exadb01 ]# cp /etc/sysconfig/network-scripts/ifcfg-ib? /u01/backup
[root@exadb02 ]# cp /etc/sysconfig/network-scripts/ifcfg-ib? /u01/backup

5. Backup the Exadata specific configuration files

Copy the Exadata specific configuration files to a backup directory on all database servers in the X4-2 cluster:

[root@exadb01 ]# cp /etc/oracle/cell/network-config/cellinit.ora /u01/backup
[root@exadb02 ]# cp /etc/oracle/cell/network-config/cellinit.ora /u01/backup
[root@exadb02 ]# cp /opt/oracle.cellos/ORACLE_CELL_OS_IS_SETUP /u01/backup

6. Backup ASM spfile

Use the asmcmd spbackup or CREATE PFILE FROM SPFILE to backup the ASM spfile, as the Grid Infrastructure owner:

[grid@exadb01 ]$ asmcmd find --type ASMPARAMETERFILE "*" "*"
+DBFS_DG/dmorl4-scan/ASMPARAMETERFILE/REGISTRY.253.838319431

[grid@exadb01 ]$ asmcmd spbackup +DBFS_DG/dmorl4-scan/ASMPARAMETERFILE/REGISTRY.253.838319431 /u01/backup/spfileASM.backup

SECTION II - The changes

1. Create the ifcfg-bondib0 network interface scripts

Create the /etc/sysconfig/network-scripts/ifcfg-bondib0 script on all database servers in the X4-2 cluster.

Given the following existing interface ib0 and ib1 configuration:

[root@exadb01 ]# ifconfig
...
ib0       Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          inet addr:192.168.10.20 Bcast:192.168.11.255 Mask:255.255.252.0
          inet6 addr: fe80::210:e000:143:ff01/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:7000 Metric:1
          RX packets:9556671 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9359690 errors:3 dropped:245 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:12239234362 (11.3 GiB) TX bytes:7907513652 (7.3 GiB)

ib0:1     Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          inet addr:169.254.101.135 Bcast:169.254.127.255 Mask:255.255.128.0
          UP BROADCAST RUNNING MULTICAST MTU:7000 Metric:1

ib1       Link encap:InfiniBand HWaddr 80:00:00:49:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          inet addr:192.168.10.21 Bcast:192.168.11.255 Mask:255.255.252.0
          inet6 addr: fe80::210:e000:143:ff02/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:7000 Metric:1
          RX packets:7569638 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7544286 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:4032498410 (3.7 GiB) TX bytes:5841237149 (5.4 GiB)

ib1:1     Link encap:InfiniBand HWaddr 80:00:00:49:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          inet addr:169.254.157.236 Bcast:169.254.255.255 Mask:255.255.128.0
          UP BROADCAST RUNNING MULTICAST MTU:7000 Metric:1
...

The script should look like this, on node 1:

[root@exadb01 ]# cat ifcfg-bondib0
DEVICE=bondib0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
BONDING_OPTS="mode=active-backup miimon=100 downdelay=5000 updelay=5000 num_grat_arp=100"
IPV6INIT=no
IPADDR=192.168.10.20
NETMASK=255.255.252.0
NETWORK=192.168.8.0
BROADCAST=192.168.11.255
MTU=7000
CONNECTED_MODE=yes

The script should look like this, on node 2:

[root@exadb02 ]# cat ifcfg-bondib0
DEVICE=bondib0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
BONDING_OPTS="mode=active-backup miimon=100 downdelay=5000 updelay=5000 num_grat_arp=100"
IPV6INIT=no
MTU=7000
IPADDR=192.168.10.22
NETMASK=255.255.252.0
NETWORK=192.168.8.0
BROADCAST=192.168.11.255

2. Modify the ifcfg-ib0 and ifcfg-ib1 scripts

Modify the ifcfg-ib0 and ifcfg-ib1 scripts on all database servers in the X4-2 cluster.

After the changes the scripts should look like this, on node 1:

[root@exadb01 ]# cat ifcfg-ib0
DEVICE=ib0
USERCTL=no
ONBOOT=yes
MASTER=bondib0
SLAVE=yes
BOOTPROTO=none
HOTPLUG=no
IPV6INIT=no
CONNECTED_MODE=yes
MTU=7000

[root@exadb01 ]# cat ifcfg-ib1
DEVICE=ib1
USERCTL=no
ONBOOT=yes
MASTER=bondib0
SLAVE=yes
BOOTPROTO=none
HOTPLUG=no
IPV6INIT=no
CONNECTED_MODE=yes
MTU=7000

After the changes the scripts should look like this, on node 2:

[root@exadb02 ]# cat ifcfg-ib0
DEVICE=ib0
USERCTL=no
ONBOOT=yes
MASTER=bondib0
SLAVE=yes
BOOTPROTO=none
HOTPLUG=no
IPV6INIT=no
CONNECTED_MODE=yes
MTU=7000

[root@exadb02 ]# cat ifcfg-ib1
DEVICE=ib1
USERCTL=no
ONBOOT=yes
MASTER=bondib0
SLAVE=yes
BOOTPROTO=none
HOTPLUG=no
IPV6INIT=no
CONNECTED_MODE=yes
MTU=7000

3. Move the network route and rule scripts

Move the network route and rule scripts from network-scripts directory, on all database servers in the X4-2 cluster.

Node 1

[root@exadb01 ]# mv /etc/sysconfig/network-scripts/route-ib? /u01/backup
[root@exadb01 ]# mv /etc/sysconfig/network-scripts/rule-ib? /u01/backup

Node 2

[root@exadb02 ]# mv /etc/sysconfig/network-scripts/route-ib? /u01/backup
[root@exadb02 ]# mv /etc/sysconfig/network-scripts/rule-ib? /u01/backup

4. Modify the CLUSTER_INTERCONNECTS initialization parameter

4.1. ASM

Modify the initialization parameter CLUSTER_INTERCONNECTS for all ASM instances in X4-2 cluster. The parameter should be changed from CLUSTER_INTERCONNECTS='<ib0 IP>:<ib1 IP>' to CLUSTER_INTERCONNECTS='<bondib0 IP>', with the correct values for each instance. Perform this as the Grid Infrastructure owner:

[grid@exadb01 ]$ sqlplus / as sysasm

SQL> show parameter CLUSTER_INTERCONNECTS

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cluster_interconnects string 192.168.10.20:192.168.10.21

SQL> alter system set CLUSTER_INTERCONNECTS='192.168.10.20' scope=spfile sid='+ASM1';

System altered.

SQL> alter system set CLUSTER_INTERCONNECTS='192.168.10.22' scope=spfile sid='+ASM2';

System altered.

SQL>

4.2. Databases

Modify the initialization parameter CLUSTER_INTERCONNECTS for all databases instances in X4-2 cluster. The parameter should be changed from CLUSTER_INTERCONNECTS='<ib0 IP>:<ib1 IP>' to CLUSTER_INTERCONNECTS='<bondib0 IP>', with the correct values for each instance. Perform this as the oracle software owner. The following example is for database dbm01 and its instances dbm011 and dbm012.

Repeat the above for all other databases in X-2 cluster.

5. Modify the cluster interconnect interface configuration

Make the change as the grid infrastructure software owner, from node 1 only.

Add the new bondib0 interface:

[grid@exadb01 ]$ oifcfg setif -global bondib0/192.168.8.0:cluster_interconnect

Delete the existing ib0 and ib1 interfaces:

[grid@exadb01 ]$ oifcfg delif -global ib0/192.168.8.0
[grid@exadb01 ]$ oifcfg delif -global ib1/192.168.8.0

Verify the current configuration:

[grid@exadb01 ]$ oifcfg getif
bondeth0 10.141.132.0 global public
bondib0 192.168.8.0 global cluster_interconnect

6. Modify the Exadata specific configuration files

Remove the ipaddress2 line from the cellinit.ora file, on all database servers in the X4-2 cluster.

The modified file, on node 1, should look like this:

[root@exadb01 ]# cat /etc/oracle/cell/network-config/cellinit.ora
ipaddress1=192.168.10.20/22

The modified file, on node 2, should look like this:

[root@exadb02 ]# cat /etc/oracle/cell/network-config/cellinit.ora
ipaddress1=192.168.10.22/22

Make the change in /opt/oracle.cellos/ORACLE_CELL_OS_IS_SETUP, on all database servers in the X4-2 cluster.

From

active-bond-ib=yes

active-bond-ib=no

7. Stop CRS

Stop the CRS on all database servers in the X4-2 cluster.

7.1. Node 1

[root@exadb01 ]# /u01/app/12.1.0.1.2/grid/bin/crsctl stop crs
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'exadb01'
CRS-2673: Attempting to stop 'ora.crsd' on 'exadb01'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'exadb01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'exadb01'
CRS-2673: Attempting to stop 'ora.testdb.db' on 'exadb01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on 'exadb01'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'exadb01'
CRS-2673: Attempting to stop 'ora.DBFS_DG.dg' on 'exadb01'
CRS-2673: Attempting to stop 'ora.RECO.dg' on 'exadb01'
CRS-2673: Attempting to stop 'ora.cvu' on 'exadb01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN3.lsnr' on 'exadb01'
CRS-2673: Attempting to stop 'ora.exadb01.vip' on 'exadb01'
CRS-2673: Attempting to stop 'ora.oc4j' on 'exadb01'
CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.scan1.vip' on 'exadb01'
CRS-2677: Stop of 'ora.LISTENER_SCAN2.lsnr' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.scan2.vip' on 'exadb01'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.LISTENER_SCAN3.lsnr' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.scan3.vip' on 'exadb01'
CRS-2677: Stop of 'ora.exadb01.vip' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.exadb02.vip' on 'exadb01'
CRS-2677: Stop of 'ora.RECO.dg' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.scan2.vip' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.scan3.vip' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.oc4j' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.scan1.vip' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.exadb02.vip' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.testdb.db' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.DATA.dg' on 'exadb01'
CRS-2677: Stop of 'ora.DATA.dg' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.DBFS_DG.dg' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'exadb01'
CRS-2677: Stop of 'ora.asm' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.cvu' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.ons' on 'exadb01'
CRS-2677: Stop of 'ora.ons' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.net1.network' on 'exadb01'
CRS-2677: Stop of 'ora.net1.network' on 'exadb01' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'exadb01' has completed
CRS-2677: Stop of 'ora.crsd' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.storage' on 'exadb01'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'exadb01'
CRS-2673: Attempting to stop 'ora.gpnpd' on 'exadb01'
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'exadb01'
CRS-2677: Stop of 'ora.storage' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.drivers.acfs' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.ctssd' on 'exadb01'
CRS-2673: Attempting to stop 'ora.evmd' on 'exadb01'
CRS-2673: Attempting to stop 'ora.asm' on 'exadb01'
CRS-2677: Stop of 'ora.mdnsd' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.evmd' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.asm' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'exadb01'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'exadb01'
CRS-2677: Stop of 'ora.cssd' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.crf' on 'exadb01'
CRS-2673: Attempting to stop 'ora.diskmon' on 'exadb01'
CRS-2677: Stop of 'ora.crf' on 'exadb01' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'exadb01'
CRS-2677: Stop of 'ora.diskmon' on 'exadb01' succeeded
CRS-2677: Stop of 'ora.gipcd' on 'exadb01' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'exadb01' has completed
CRS-4133: Oracle High Availability Services has been stopped.

7.2. Node 2

Stop the CRS on node 2, with the same 'crsctl stop crs' command.

8. Reboot all database servers in the X4-2 cluster.

8.1. Node 1

[root@exadb01 ]# reboot

Broadcast message from root (pts/0) (Tue Apr 1 06:36:44 2014):

The system is going down for reboot NOW!

8.2. Node 2

Reboot node 2

9. Verify the changes

After the reboot of all database servers in the X4-2 clusterr, check the network, clusterware and database status.

These examples show the checks on node 1. Make sure to verify the same on all nodes in the X4-2 cluster.

9.1. Network interfaces

[root@exadb01 ]# ifconfig bondib0
bondib0   Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          inet addr:192.168.10.20 Bcast:192.168.11.255 Mask:255.255.252.0
          inet6 addr: fe80::210:e000:143:ff01/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST MTU:7000 Metric:1
          RX packets:15524 errors:0 dropped:6568 overruns:0 frame:0
          TX packets:3760 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1547456 (1.4 MiB) TX bytes:1136281 (1.0 MiB)

[root@exadb01 ]# ifconfig ib0
ib0       Link encap:InfiniBand HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:7000 Metric:1
          RX packets:9059 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3760 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:1082808 (1.0 MiB) TX bytes:1136281 (1.0 MiB)

[root@exadb01 ]# ifconfig ib1
ib1       Link encap:InfiniBand HWaddr 80:00:00:49:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:7000 Metric:1
          RX packets:6701 errors:0 dropped:6701 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:477864 (466.6 KiB) TX bytes:0 (0.0 b)

9.2 Clusterware

[root@exadb01 ]# /u01/app/12.1.0.1.2/grid/bin/crsctl status resource -t
--------------------------------------------------------------------------------
Name           Target State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
               ONLINE ONLINE       exadb01                STABLE
               ONLINE ONLINE       exadb02                STABLE
ora.DBFS_DG.dg
               ONLINE ONLINE       exadb01                STABLE
               ONLINE ONLINE       exadb02                STABLE
ora.LISTENER.lsnr
               ONLINE ONLINE       exadb01                STABLE
               ONLINE ONLINE       exadb02                STABLE
ora.RECO.dg
               ONLINE ONLINE       exadb01                STABLE
               ONLINE ONLINE       exadb02                STABLE
ora.asm
               ONLINE ONLINE       exadb01                Started,STABLE
               ONLINE ONLINE       exadb02                Started,STABLE
ora.net1.network
               ONLINE ONLINE       exadb01                STABLE
               ONLINE ONLINE       exadb02                STABLE
ora.ons
               ONLINE ONLINE       exadb01                STABLE
               ONLINE ONLINE       exadb02                STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
      1        ONLINE ONLINE       exadb02                STABLE
ora.LISTENER_SCAN2.lsnr
      1        ONLINE ONLINE       exadb01                STABLE
ora.LISTENER_SCAN3.lsnr
      1        ONLINE ONLINE       exadb01                STABLE
ora.MGMTLSNR
      1        OFFLINE OFFLINE                             STABLE
ora.cvu
      1        ONLINE ONLINE       exadb01                STABLE
ora.dbm01.db
      1        ONLINE ONLINE       exadb01                Open,STABLE
      2        ONLINE ONLINE       exadb02                Open,STABLE
ora.exadb01.vip
      1        ONLINE ONLINE       exadb01                STABLE
ora.exadb02.vip
      1        ONLINE ONLINE       exadb02                STABLE
ora.mydb.db
      1        OFFLINE OFFLINE                             STABLE
      2        OFFLINE OFFLINE                             STABLE
ora.oc4j
      1        ONLINE ONLINE       exadb01                STABLE
ora.scan1.vip
      1        ONLINE ONLINE       exadb02                STABLE
ora.scan2.vip
      1        ONLINE ONLINE       exadb01                STABLE
ora.scan3.vip
      1        ONLINE ONLINE       exadb01                STABLE
ora.testdb.db
      1        ONLINE ONLINE       exadb01                Open,STABLE
--------------------------------------------------------------------------------

9.3. The ASM and database instances

[root@exadb01 ~]# ps -ef | grep pmon
root      11598      1 0 06:40 ?        00:00:00 /usr/bin/perl -w /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -server
oracle    22053      1 0 06:48 ?        00:00:00 asm_pmon_+ASM1
oracle    22964      1 0 06:48 ?        00:00:00 ora_pmon_dbm011
oracle    23019      1 0 06:48 ?        00:00:00 ora_pmon_testdb1
root      28106 13038 0 06:50 pts/0    00:00:00 grep pmon

Conclusion

If the requirement to connect an Exadata X4-2 Database Machine to V2/X2-2/X3-2 was not known at the deployment time, the Exadata X4-2 Database Machine would have been deployed with the InfiniBand bonding in active/active mode. In that case the InfiniBand bonding needs to be changed to active/passive mode on database servers only.

Tthere is no need to make any changes on the X4-2 storage cells.

References

Oracle® Exadata Database Machine Owner's Guide 11g Release 2 (11.2)
Oracle® Clusterware Administration and Deployment Guide 12c Release 1 (12.1)
<NOTE:888828.1> - Exadata Database Machine and Exadata Storage Server Supported Versions

Attachments

This solution has no attachment