Upgrading/Downgrading Exadata iLOM firmware

January 9, 2015 Leave a comment

This post is not really Exadata specific, really it applies to any use of the Sun X4170 series of hardwre. And it definitely seems a long way from being a traditional DBA task. As I’ve had to perform this task a number of times recently I thought I’d document it here.

There are actually a number of ways of doing it, but finding and navigating the documentation can be challenging. The way I have performed and iLOM upgrade (or downgrade) has been to use the web interface. It can be done via the command line, but the web interface has worked well for me.

The software for the iLOM can be found in the software distribution, but you have to do some digging as it is contained within the dbw.tbz tar ball, which itself is found in the image_version.tbz file which is under the db_patch_version directory. What you need is something of the form:

1
2
3
[root@db01] tar xvf 11.2.2.4.2.111221.tbz opt/oracle.cellos/iso/cellbits/dbfw.tbz
 
[root@db01] tar xvf dbfw.tbz ActualFirmwareFiles/ILOM-3_0_9_19_e_r66106-Sun_Fire_X4170_X4270_X4275.pkg

This extracts just your iLOM pkg file.

So with your .pkg to hand, fire your web browser at the iLOM you want to upgrade and then choose Maintenance:

Obviously you click the upgrade Firmware Upgrade tab and then the Enter Upgrade Mode:

You now choose your iLOM pkg file and press the Upload button. This takes you to the following type of screen:

Where you can see you current version and what version you are going to upgrade/downgrade to. Once you hit the Start Upgrade button You are taken to a screen that shows the progress of the loading of the new firmware.

All very straightforward.

However, Oracle advise to follow MOS: 1327022.1 which has the following command line steps:

Check the pkg file is the version you want:

1
2
# cd /opt/oracle.cellos/iso/cellbits
# tar -tf dbfw.tbz

Now Check your current Firmware version:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
# /opt/oracle.cellos/CheckHWnFWProfile -d
[SystemModel]
 SUN FIRE X4170 SERVER
[BIOSVendor]
 American Megatrends Inc.
[BIOSVersion]
 07060232
[BIOSDate]
 07/25/2011
[ProcessorInformation]
 Cores:16
 Intel(R) Xeon(R) E5540 2.53GHz
[ILOMVersion]
 3.0.9.19.e r66106
[PhysicalMemoryGB]
 72
[DiskControllerPCIeSlotNumber]
 PCI-E Slot 0
[DiskControllerModel]
 LSI MegaRAID SAS 9261-8i
[DiskControllerFirmwareRevision]
 12.12.0-0048
[InfinibandHCAPCIeSlotNumber]
 PCI-E Slot 2
[InfinibandHCAPCIeSlotWidth]
 x8
[InfinibandHCADeviceID]
 26428
[InfinibandHCAChipRevision]
 A0
[InfinibandHCAImageType]
 ConnectX
[InfinibandHCAFirmwareVersion]
 2.7.0
[SASBackplaneFirmwareVersion]
 NotApplicable
[DiskControllerPCIeSlotWidth]
 x8
[InfinibandHCAHardwareRev]
 50
[LightsOutFirmwareVersion]
 Firmware Revision : 3.0
[Powersupplies]
 PS0 and PS1 ok
[Enclosure:Slot:DiskType:DiskMake:DiskModel:MinFwVersion]
 ALL:ALL SAS HITACHI H103014SCSUN146G A2A8

The above output is from a V2 running 11.2.2.4.2.

Finally you can upgrade the firmware with the following:

1
# /opt/oracle.cellos/CheckHWnFWProfile -U /opt/oracle.cellos/iso/cellbits

After this is complete, check your version again.

Oracle 12.1.0.2 Bundle Patching

January 3, 2015 Leave a comment

I’ve spent a few days playing with patching 12.1.0.2 with the so called “Database Patch for Engineered Systems and Database In-Memory”. Lets skip over why these not necessarily related feature sets should be bundled together into effectively a Bundle Patch.

First I was testing going from 12.1.0.2.1 to BP2 or 12.1.0.2.2. Then as soon as I’d done that of course BP3 was released.

So this is our starting position with BP1:

GI HOME:

1
2
3
4
[oracle@rac2 ~]$ /u01/app/12.1.0/grid_1/OPatch/opatch lspatches
19392604;OCW PATCH SET UPDATE : 12.1.0.2.1 (19392604)
19392590;ACFS Patch Set Update : 12.1.0.2.1 (19392590)
19189240;DATABASE BUNDLE PATCH : 12.1.0.2.1 (19189240)

DB Home:

1
2
3
[oracle@rac2 ~]$ /u01/app/oracle/product/12.1.0.2/db_1/OPatch/opatch lspatches
19392604;OCW PATCH SET UPDATE : 12.1.0.2.1 (19392604)
19189240;DATABASE BUNDLE PATCH : 12.1.0.2.1 (19189240)

Simple enough, right? BP1 and the individual patch components within BP1 give you 12.1.0.2.1. Even I can follow this.

Lets try and apply BP2 to the above. We will use opatchauto for this, and to begin with we will run an analyze:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
[root@rac2 ~]# /u01/app/12.1.0/grid_1/OPatch/opatchauto apply -analyze /tmp/BP2/19774304 -ocmrf /tmp/ocm.rsp
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation.  All rights reserved.
OPatchauto version : 12.1.0.1.5
OUI version        : 12.1.0.2.0
Running from       : /u01/app/12.1.0/grid_1
opatchauto log file: /u01/app/12.1.0/grid_1/cfgtoollogs/opatchauto/19774304/opatch_gi_2014-12-18_13-35-17_analyze.log
NOTE: opatchauto is running in ANALYZE mode. There will be no change to your system.
Parameter Validation: Successful
Grid Infrastructure home:
/u01/app/12.1.0/grid_1
RAC home(s):
/u01/app/oracle/product/12.1.0.2/db_1
Configuration Validation: Successful
Patch Location: /tmp/BP2/19774304
Grid Infrastructure Patch(es): 19392590 19392604 19649591
RAC Patch(es): 19392604 19649591
Patch Validation: Successful
Analyzing patch(es) on "/u01/app/oracle/product/12.1.0.2/db_1" ...
Patch "/tmp/BP2/19774304/19392604" analyzed on "/u01/app/oracle/product/12.1.0.2/db_1" with warning for apply.
Patch "/tmp/BP2/19774304/19649591" analyzed on "/u01/app/oracle/product/12.1.0.2/db_1" with warning for apply.
Analyzing patch(es) on "/u01/app/12.1.0/grid_1" ...
Patch "/tmp/BP2/19774304/19392590" analyzed on "/u01/app/12.1.0/grid_1" with warning for apply.
Patch "/tmp/BP2/19774304/19392604" analyzed on "/u01/app/12.1.0/grid_1" with warning for apply.
Patch "/tmp/BP2/19774304/19649591" analyzed on "/u01/app/12.1.0/grid_1" with warning for apply.
SQL changes, if any, are analyzed successfully on the following database(s): TESTRAC
Apply Summary:
opatchauto ran into some warnings during analyze (Please see log file for details):
GI Home: /u01/app/12.1.0/grid_1: 19392590, 19392604, 19649591
RAC Home: /u01/app/oracle/product/12.1.0.2/db_1: 19392604, 19649591
opatchauto completed with warnings.

Well, that does not look promising. I have no “one-off” patches in this home to cause a conflict, it should be a simple BP1->BP2 patching without any issues.

Digging into the logs we find the following:

1
2
3
4
5
6
7
8
9
10
.
.
.
[18-Dec-2014 13:37:08]       Verifying environment and performing prerequisite checks...
[18-Dec-2014 13:37:09]       Patches to apply -> [ 19392590 19392604 19649591  ]
[18-Dec-2014 13:37:09]       Identical patches to filter -> [ 19392590 19392604  ]
[18-Dec-2014 13:37:09]       The following patches are identical and are skipped:
[18-Dec-2014 13:37:09]       [ 19392590 19392604  ]
.
.

Essentially out of the 3 patches in the home at BP1 only the Database Bundle Patch 19189240 is superseded by BP2. Maybe this annoys me more than it should. I like my patches applied by BP2 to end in 2. I also don’t like the fact the analyze throws a warning about this.

Lets patch:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
[root@rac2 ~]# /u01/app/12.1.0/grid_1/OPatch/opatchauto apply /tmp/BP2/19774304 -ocmrf /tmp/ocm.rsp
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation.  All rights reserved.
OPatchauto version : 12.1.0.1.5
OUI version        : 12.1.0.2.0
Running from       : /u01/app/12.1.0/grid_1
opatchauto log file: /u01/app/12.1.0/grid_1/cfgtoollogs/opatchauto/19774304/opatch_gi_2014-12-18_13-54-03_deploy.log
Parameter Validation: Successful
Grid Infrastructure home:
/u01/app/12.1.0/grid_1
RAC home(s):
/u01/app/oracle/product/12.1.0.2/db_1
Configuration Validation: Successful
Patch Location: /tmp/BP2/19774304
Grid Infrastructure Patch(es): 19392590 19392604 19649591
RAC Patch(es): 19392604 19649591
Patch Validation: Successful
Stopping RAC (/u01/app/oracle/product/12.1.0.2/db_1) ... Successful
Following database(s) and/or service(s)  were stopped and will be restarted later during the session: testrac
Applying patch(es) to "/u01/app/oracle/product/12.1.0.2/db_1" ...
Patch "/tmp/BP2/19774304/19392604" applied to "/u01/app/oracle/product/12.1.0.2/db_1" with warning.
Patch "/tmp/BP2/19774304/19649591" applied to "/u01/app/oracle/product/12.1.0.2/db_1" with warning.
Stopping CRS ... Successful
Applying patch(es) to "/u01/app/12.1.0/grid_1" ...
Patch "/tmp/BP2/19774304/19392590" applied to "/u01/app/12.1.0/grid_1" with warning.
Patch "/tmp/BP2/19774304/19392604" applied to "/u01/app/12.1.0/grid_1" with warning.
Patch "/tmp/BP2/19774304/19649591" applied to "/u01/app/12.1.0/grid_1" with warning.
Starting CRS ... Successful
Starting RAC (/u01/app/oracle/product/12.1.0.2/db_1) ... Successful
SQL changes, if any, are applied successfully on the following database(s): TESTRAC
Apply Summary:
opatchauto ran into some warnings during patch installation (Please see log file for details):
GI Home: /u01/app/12.1.0/grid_1: 19392590, 19392604, 19649591
RAC Home: /u01/app/oracle/product/12.1.0.2/db_1: 19392604, 19649591
opatchauto completed with warnings.

I do not like to see warnings when I’m patching. The log file for the apply is similar to the analyze, identical patches skipped.

Checking where we are with GI and DB patches now:

1
2
3
4
5
6
7
8
[oracle@rac2 ~]$ /u01/app/12.1.0/grid_1/OPatch/opatch lspatches
19649591;DATABASE BUNDLE PATCH : 12.1.0.2.2 (19649591)
19392604;OCW PATCH SET UPDATE : 12.1.0.2.1 (19392604)
19392590;ACFS Patch Set Update : 12.1.0.2.1 (19392590)
[oracle@rac2 ~]$ /u01/app/oracle/product/12.1.0.2/db_1/OPatch/opatch lspatches
19649591;DATABASE BUNDLE PATCH : 12.1.0.2.2 (19649591)
19392604;OCW PATCH SET UPDATE : 12.1.0.2.1 (19392604)

The only one changed is the DATABASE BUNDLE PATCH.

The one MOS document I effectively have on “speed dial” is 888828.1 and that showed up BP3 as being available 17th December. It also had the following warning:

Before install on top of 12.1.0.2.1DBBP or 12.1.0.2.2DBBP, first rollback patch 19392604 OCW PATCH SET UPDATE : 12.1.0.2.1

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
[root@rac2 ~]# /u01/app/12.1.0/grid_1/OPatch/opatchauto apply -analyze /tmp/BP3/20026159 -ocmrf /tmp/ocm.rsp
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation.  All rights reserved.
OPatchauto version : 12.1.0.1.5
OUI version        : 12.1.0.2.0
Running from       : /u01/app/12.1.0/grid_1
opatchauto log file: /u01/app/12.1.0/grid_1/cfgtoollogs/opatchauto/20026159/opatch_gi_2014-12-18_14-13-58_analyze.log
NOTE: opatchauto is running in ANALYZE mode. There will be no change to your system.
Parameter Validation: Successful
Grid Infrastructure home:
/u01/app/12.1.0/grid_1
RAC home(s):
/u01/app/oracle/product/12.1.0.2/db_1
Configuration Validation: Successful
Patch Location: /tmp/BP3/20026159
Grid Infrastructure Patch(es): 19392590 19878106 20157569
RAC Patch(es): 19878106 20157569
Patch Validation: Successful
Command "/u01/app/12.1.0/grid_1/OPatch/opatch prereq CheckConflictAgainstOH -ph /tmp/BP3/20026159/19878106 -invPtrLoc /u01/app/12.1.0/grid_1/oraInst.loc -oh /u01/app/12.1.0/grid_1" execution failed
Log file Location for the failed command: /u01/app/12.1.0/grid_1/cfgtoollogs/opatch/opatch2014-12-18_14-14-50PM_1.log
Analyzing patch(es) on "/u01/app/oracle/product/12.1.0.2/db_1" ...
Patch "/tmp/BP3/20026159/19878106" analyzed on "/u01/app/oracle/product/12.1.0.2/db_1" with warning for apply.
Patch "/tmp/BP3/20026159/20157569" analyzed on "/u01/app/oracle/product/12.1.0.2/db_1" with warning for apply.
Analyzing patch(es) on "/u01/app/12.1.0/grid_1" ...
Command "/u01/app/12.1.0/grid_1/OPatch/opatch napply -phBaseFile /tmp/OraGI12Home2_patchList -local  -invPtrLoc /u01/app/12.1.0/grid_1/oraInst.loc -oh /u01/app/12.1.0/grid_1 -silent -report -ocmrf /tmp/ocm.rsp" execution failed:
UtilSession failed: After skipping conflicting patches, there is no patch to apply.
Log file Location for the failed command: /u01/app/12.1.0/grid_1/cfgtoollogs/opatch/opatch2014-12-18_14-15-30PM_1.log
Following step(s) failed during analysis:
/u01/app/12.1.0/grid_1/OPatch/opatch prereq CheckConflictAgainstOH -ph /tmp/BP3/20026159/19878106 -invPtrLoc /u01/app/12.1.0/grid_1/oraInst.loc -oh /u01/app/12.1.0/grid_1
/u01/app/12.1.0/grid_1/OPatch/opatch napply -phBaseFile /tmp/OraGI12Home2_patchList -local  -invPtrLoc /u01/app/12.1.0/grid_1/oraInst.loc -oh /u01/app/12.1.0/grid_1 -silent -report -ocmrf /tmp/ocm.rsp
SQL changes, if any, are analyzed successfully on the following database(s): TESTRAC
Apply Summary:
opatchauto ran into some warnings during analyze (Please see log file for details):
RAC Home: /u01/app/oracle/product/12.1.0.2/db_1: 19878106, 20157569
Following patch(es) failed to be analyzed:
GI Home: /u01/app/12.1.0/grid_1: 19392590, 19878106, 20157569
opatchauto analysis reports error(s).

Looking at the log file we see patch 19392604 already in the home conflicts with patch 19878106 from BP3. 19392604 is the OCW PATCH SET UPDATE in BP1 (and BP2) while 19878106 is the Database Bundle Patch in BP3. We see the following in the log file:

1
2
Patch 19878106 has Generic Conflict with 19392604. Conflicting files are :
                             /u01/app/12.1.0/grid_1/bin/diskmon

That seems messy. It definitely annoys me that to apply BP3 I have to take additional steps of rolling back a pervious BP. I don’t recall having to do this with previous Bundle Patches, and I’ve applied a fair few of them.

I rolled the lot back with opatchauto rollback. Then applied BP3 ontop of the unpatched homes I was left with. But lets look at what BP3 on top of 12.1.0.2 gives you:

GI Home:

1
2
3
4
[oracle@rac1 ~]$ /u01/app/12.1.0/grid_1/OPatch/opatch lspatches
20157569;OCW Patch Set Update : 12.1.0.2.1 (20157569)
19878106;DATABASE BUNDLE PATCH: 12.1.0.2.3 (19878106)
19392590;ACFS Patch Set Update : 12.1.0.2.1 (19392590)

DB Home:

1
2
3
[oracle@rac1 ~]$ /u01/app/12.1.0/grid_1/OPatch/opatch lspatches
20157569;OCW Patch Set Update : 12.1.0.2.1 (20157569)
19878106;DATABASE BUNDLE PATCH: 12.1.0.2.3 (19878106)

So for BP2 we had patch 19392604 OCW PATCH SET UPDATE : 12.1.0.2.1 Now we still have a 12.1.0.2.1 OCW Patch Set Update with BP3 but it has a new patch number!

Categories: 12c, bundle patch, Oracle Tags: , ,

CPU, PSU, SPU – Oracle Critical Patch Update Terminology Update

January 3, 2015 Leave a comment

It all started in January 2005 with Critical Patch Updates (CPU). Then Patch Set Updates (PSU) were added as cumulative patches that included priority fixes as well as security fixes. As of the October 2012 Critical Patch Update, Oracle has changed the terminology to better differentiate between patch types. This terminology will be used for the Oracle Database, Enterprise Manager, Fusion Middleware, and WebLogic.

Critical Patch Update (CPU) now refers to the overall release of security fixes each quarter rather than the cumulative database security patch for the quarter. Think of the CPU as the overarching quarterly release and not as a single patch.

Patch Set Updates (PSU) are the same cumulative patches that include both the security fixes and priority fixes. The key with PSUs is they are minor version upgrades (e.g., 11.2.0.1.1 to 11.2.0.1.2). Once a PSU is applied, only PSUs can be applied in future quarters until the database is upgraded to a new base version.

Security Patch Update (SPU) terminology is introduced in the October 2012 Critical Patch Update as the term for the quarterly security patch. SPU patches are the same as previous CPU patches, just a new name. For the database, SPUs can not be applied once PSUs have been applied until the database is upgraded to a new base version.

Bundle Patches are the quarterly patches for Windows and Exadata which include both the quarterly security patches as well as recommended fixes.

References: New Patch Nomenclature for Oracle Products [ID 1430923.1]

Categories: CPU, Oracle, PSU, SPU, upgrade Tags: , , ,

How to change IP and subnet mask of Exadata database nodes and Storage cells

December 25, 2014 Leave a comment
1. Check backup of  OCR
ocrconfig -showbackup
crsctl query css votedisk
Location to check  – /cdata/cluster_name
2.Take a backup of the gpnp profile on all nodes before starting.
cd /gpnp/dbnode1/profiles/peer
cp -p profile.xml profile.xml.bk
3.Determine if the CLUSTER_INTERCONNECT parameter is used in the Oracle Database and Oracle  ASM instances using the following command
set linesize 300
col NAME form a50
col VALUE form a50
SELECT inst_id, name,value FROM gv$parameter WHERE name =’cluster_interconnects';
   INST_ID NAME                                               VALUE
———- ————————————————– ————————————————–
         1 cluster_interconnects                              192.168.10.31
         2 cluster_interconnects                              192.168.10.32
ASM
ALTER SYSTEM SET CLUSTER_INTERCONNECTS=’192.168.20.31′ SCOPE=SPFILE SID=’+ASM1′;
ALTER SYSTEM SET CLUSTER_INTERCONNECTS=’192.168.20.32′ SCOPE=SPFILE SID=’+ASM2′;
DATABASE
ALTER SYSTEM SET CLUSTER_INTERCONNECTS=’192.168.20.31′ SCOPE=SPFILE SID=’DATABASE1′;
ALTER SYSTEM SET CLUSTER_INTERCONNECTS=’192.168.20.32′ SCOPE=SPFILE SID=’DATABASE2′;
4.Shut down all cluster-managed services on each database server as the oracle user using the  following command:
srvctl stop home -o -s /tmp/dbnode1_dbhome -n dbnode1
srvctl stop home -o -s /tmp/dbnode2_dbhome -n dbnode2
5. Modify the cluster interconnect interface to use the BONDIB0 interface on the first database server as follows - NEEDS TO BE DONE ON  FIRST NODE ONLY
a. Log in as the oracle user.
b. Set ORACLE_HOME to the Grid Infrastructure home.
c. Set the base for the ORACLE_SID environment variable using the following command. The
ORACLE_HOME environment variable must be set to the Grid Infrastructure home.
5.1  oifcfg iflist
eth0  10.240.64.0
bondeth0  10.240.48.0
bondib0  192.168.8.0
bondib0  169.254.0.0
5.2  oifcfg getif
bondeth0  10.240.48.0  global  public
bondib0  192.168.8.0  global  cluster_interconnect
Assign BONDIB0 as the global cluster interconnect interface using the following command:
5.3 oifcfg setif -global bond0/192.168.20.0:cluster_interconnect
5.4 Check Ips again
oifcfg getif
Output
bondeth0 10.240.48.0 global public
Bondib0 192.168.8.0 global cluster_interconnect
Bondib0 192.168.20.0 global cluster_interconnect
6.Shut down Oracle Clusterware and Oracle Clusterware CRS on each database server as follows
a./bin/crsctl stop crs -f
b./bin/crsctl disable crs
7.Change the InfiniBand IP addresses on each Exadata Storage Server as follows:
7.1 login as root
7.2 service celld stop
7.3 service ocrvottargetd stop
7.4 ipconf
[root@cellnode1 ~]# service celld stop
Stopping the RS, CELLSRV, and MS services…
The SHUTDOWN of services was successful.
[root@cellnode1 ~]# service ocrvottargetd stop
[root@cellnode1 ~]# service ocrvottargetd status
[root@cellnode1 ~]# ipconf
Logging started to /var/log/cellos/ipconf.log
Interface ib0 is Linked.  hca: mlx4_0
Interface ib1 is Linked.  hca: mlx4_0
Interface eth0 is Linked.  driver/mac: igb/00:21:28:d7:cf:82
Interface eth1 is … Unlinked.  driver/mac: igb/00:21:28:d7:cf:83
Interface eth2 is … Unlinked.  driver/mac: igb/00:21:28:d7:cf:84
Interface eth3 is … Unlinked.  driver/mac: igb/00:21:28:d7:cf:85
Network interfaces
Name     State      IP address      Netmask         Gateway         Net type     Hostname
ib0      Linked
ib1      Linked
eth0     Linked
eth1     Unlinked
eth2     Unlinked
eth3     Unlinked
Warning. Some network interface(s) are disconnected. Check cables and swicthes and retry
Do you want to retry (y/n) [y]: n
The current nameserver(s): 10.239.32.5 10.38.9.31 10.239.96.36 10.8.130.191
Do you want to change it (y/n) [n]:
The current timezone: Asia/Kolkata
Do you want to change it (y/n) [n]:
The current NTP server(s): 10.46.192.98
Do you want to change it (y/n) [n]:
Network interfaces
Name     State      IP address      Netmask         Gateway         Net type     Hostname
eth0     Linked     10.240.64.237   255.255.255.0   10.240.64.1     Management   cellnode1.enterprisenet.org
eth1     Unlinked
eth2     Unlinked
eth3     Unlinked
bondib0  ib0,ib1    192.168.10.33   255.255.252.0                   Private      cellnode1-priv.enterprisenet.org
Select interface name to configure or press Enter to continue: bondib0
Selected interface. bondib0
IP address or none [192.168.10.33]: 192.168.20.33
Netmask [255.255.252.0]:
Fully qualified hostname or none [cellnode1-priv.enterprisenet.org]:
Continue configuring or re-configuring interfaces? (y/n) [y]: n
Select canonical hostname from the list below
1: cellnode1.enterprisenet.org
2: cellnode1-priv.enterprisenet.org
Canonical fully qualified domain name [1]:
Select default gateway interface from the list below
1: eth0
Default gateway interface [1]:
Canonical hostname: cellnode1.enterprisenet.org
Nameservers: 10.239.32.5 10.38.9.31 10.239.96.36 10.8.130.191
Timezone: Asia/Kolkata
NTP servers: 10.46.192.98
Default gateway device: eth0
Network interfaces
Name     State      IP address      Netmask         Gateway         Net type     Hostname
eth0     Linked     10.240.64.237   255.255.255.0   10.240.64.1     Management   cellnode1.enterprisenet.org
eth1     Unlinked
eth2     Unlinked
eth3     Unlinked
bondib0  ib0,ib1    192.168.20.33   255.255.252.0                   Private      cellnode1-priv.enterprisenet.org
Is this correct (y/n) [y]:
Do you want to configure basic ILOM settings (y/n) [y]: n
Info. IP address of bondib0 changed to “192.168.20.33”
Info. Run /opt/oracle.cellos/validations/init.d/saveconfig
Info. Custom changes have been detected in /etc/sysconfig/network-scripts/ifcfg-bondib0
Warning. Config /etc/sysconfig/network-scripts/ifcfg-bondib0. Existing line “IPADDR=192.168.10.33″ will be overwritten with “IPADDR=192.168.20.33″
Info. Config /etc/sysconfig/network-scripts/ifcfg-bondib0. Original line “IPADDR=192.168.10.33″ will be commented
Warning. Config /etc/sysconfig/network-scripts/ifcfg-bondib0. Existing line “NETWORK=192.168.8.0″ will be overwritten with “NETWORK=192.168.20.0″
Info. Config /etc/sysconfig/network-scripts/ifcfg-bondib0. Original line “NETWORK=192.168.8.0″ will be commented
Warning. Config /etc/sysconfig/network-scripts/ifcfg-bondib0. Existing line “BROADCAST=192.168.11.255″ will be overwritten with “BROADCAST=192.168.23.255″
Info. Config /etc/sysconfig/network-scripts/ifcfg-bondib0. Original line “BROADCAST=192.168.11.255″ will be commented
Info. Original file will be saved in /opt/oracle.cellos/conf/network-scripts/backup_by_Exadata_ipconf
Info. Original file will be saved in /etc/ssh/sshd_config.backupbyExadata
Info. Generate /etc/ssh/sshd_config with ListenAddress(es) 10.240.64.237, 192.168.20.33
Stopping sshd:                                             [  OK  ]
Starting sshd:                                             [  OK  ]
bash /opt/oracle.cellos/ib_set_node_desc.sh
Re-login using new IP address 10.240.64.237 if you were disconnected after following commands
echo -n
ifdown bondib0
sleep 1
/opt/oracle.cellos/reset_rule_table.sh 200
sleep 1
ifup bondib0
sleep 3
cellcli -e “alter cell startup services rs”
cellcli -e “alter cell startup services ms”
cellcli -e “alter cell interconnect1=bondib0″
cellcli -e “alter cell shutdown services all force”
service ocrvottargetd restart
sleep 1
tgtadm: can’t find the target
Starting the RS services…
Getting the state of RS services…  running
Starting MS services…
The STARTUP of MS services was successful.
A restart of all services is required to put new network configuration into effect. MS-CELLSRV communication may be hampered until restart.
Cell cellnode1 successfully altered
Stopping the RS, CELLSRV, and MS services…
The SHUTDOWN of services was successful.
ipaddress1=192.168.20.33/22
[root@cellnode1 ~]#
7.5  as root user   – reboot
7.6 Verify the newly-assigned InfiniBand address on Exadata Storage Server using the following command
cellcli -e list cell detail | grep ipaddress1
Current output :
[root@cellnode1 ~]# cellcli -e list cell detail | grep ipaddress1
         ipaddress1:             192.168.10.33/22
Output after change
[root@cellnode1 ~]# cellcli -e list cell detail | grep ipaddress1
         ipaddress1:             192.168.20.33/22
7.7. If there is an error indicating that one or more cell services are not running, then restart the cell  services using the following command:
cellcli -e alter cell restart services all
8.Change the InfiniBand IP addresses on each database server as follows  - NEEDS TO BE PERFORMED ON ALL NODES ONE BY ONE
8.1 login as root
8.2 cd /etc/sysconfig/network-scripts
8.3 cp ifcfg-bondib0 orig_ifcfg-bondib0  
8.4 Edit the ifcfg-bond0 file to update the IPADDR, NETMASK, NETWORK and BROADCAST
fields.
[root@dbnode1 network-scripts]# cat ifcfg-bondib0
#### DO NOT REMOVE THESE LINES ####
#### %GENERATED BY CELL% ####
DEVICE=bondib0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.10.31
NETMASK=255.255.252.0
NETWORK=192.168.8.0
BROADCAST=192.168.11.255
BONDING_OPTS=”mode=active-backup miimon=100 downdelay=5000 updelay=5000 num_grat_arp=100″
IPV6INIT=no
MTU=65520
[root@dbnode2 network-scripts]# cat ifcfg-bondib0
#### DO NOT REMOVE THESE LINES ####
#### %GENERATED BY CELL% ####
DEVICE=bondib0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.10.32
NETMASK=255.255.252.0
NETWORK=192.168.8.0
BROADCAST=192.168.11.255
BONDING_OPTS=”mode=active-backup miimon=100 downdelay=5000 updelay=5000 num_grat_arp=100″
IPV6INIT=no
MTU=65520
UPDATED VALUE for DBNODE1 and DBNODE2
FOR DBNODE1?
IPADDR=192.168.20.31
NETMASK=255.255.252.0
NETWORK=192.168.20.0
BROADCAST=192.168.23.255
FOR DBNODE2?
IPADDR=192.168.20.32
NETMASK=255.255.252.0
NETWORK=192.168.20.0
BROADCAST=192.168.23.255
8.5 reboot
8.6 Verify the InfiniBand IP address information using the following command
Current value – dbnode1
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.32  Bcast:192.168.11.255  Mask:255.255.252.0
          inet6 addr: fe80::221:2800:1cf:2b97/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:65520  Metric:1
          RX packets:62232895 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67053494 errors:3 dropped:14 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:41159776048 (38.3 GiB)  TX bytes:34502152558 (32.1 GiB)
Current value – dbnode2
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.31  Bcast:192.168.11.255  Mask:255.255.252.0
          inet6 addr: fe80::221:2800:1cf:1e67/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:65520  Metric:1
          RX packets:67191396 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63617557 errors:0 dropped:11 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:34394734207 (32.0 GiB)  TX bytes:41626158309 (38.7 GiB)
ifconfig -a
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.20.32  Bcast:192.168.23.255  Mask:255.255.252.0
          inet6 addr: fe80::221:2800:1cf:2b97/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:65520  Metric:1
          RX packets:62232895 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67053494 errors:3 dropped:14 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:41159776048 (38.3 GiB)  TX bytes:34502152558 (32.1 GiB)
Current value – dbnode2
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.20.31  Bcast:192.168.23.255  Mask:255.255.252.0
          inet6 addr: fe80::221:2800:1cf:1e67/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:65520  Metric:1
          RX packets:67191396 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63617557 errors:0 dropped:11 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:34394734207 (32.0 GiB)  TX bytes:41626158309 (38.7 GiB)
9.Modify Cellinit.ora  (Do not edit the cellinit.ora or cellip.ora files when the database or Oracle ASM instance are running)
9.1 cd /etc/oracle/cell/network-config/
Current value on dbnode1
[root@dbnode1 network-config]# cat cellinit.ora
ipaddress1=192.168.10.31/22
[root@dbnode2 network-config]# cat cellinit.ora
ipaddress1=192.168.10.32/22
9.1 cp cellinit.ora cellinit.new
9.2 Modify cellinit.new to
ipaddress1=192.168.20.31/22
ipaddress1=192.168.20.32/22
9.3 rename the file back
mv cellinit.new cellinit.ora
10.Modify cellip.ora
10.1 cd /etc/oracle/cell/network-config/
Current Values :
[root@dbnode1 network-config]# cat cellip.ora
cell=”192.168.10.33″
cell=”192.168.10.34″
cell=”192.168.10.35″
[root@dbnode2 network-config]# cat cellip.ora
cell=”192.168.10.33″
cell=”192.168.10.34″
cell=”192.168.10.35″
10.2 cp cellip.ora orig_cellip.ora
10.3 modify cellip.ora to following on both nodes
cell=”192.168.20.33″
cell=”192.168.20.34″
cell=”192.168.20.35″
11.Update the /etc/hosts file on each database server and Exadata Storage Servers
11.1 login as root
11.2 Current value on both dbnode1 and dbnode2
### Compute Node Private Interface details
#####192.168.10.1       dbnode1-priv.enterprisenet.org dbnode1-priv
#####192.168.10.2       dbnode2-priv.enterprisenet.org dbnode2-priv
192.168.10.31   dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.10.32   dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
#####192.168.10.3       cellnode1-priv.enterprisenet.org cellnode1-priv
#####192.168.10.4       cellnode2-priv.enterprisenet.org cellnode2-priv
#####192.168.10.5       cellnode3-priv.enterprisenet.org cellnode3-priv
192.168.10.33   cellnode1-priv.enterprisenet.org cellnode1-priv
192.168.10.34   cellnode2-priv.enterprisenet.org cellnode2-priv
192.168.10.35   cellnode3-priv.enterprisenet.org cellnode3-priv
On CELLNODE1
#### END Generated by Exadata ####
### Compute Node Private Interface details
192.168.10.1    dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.10.2    dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
# 192.168.10.3  cellnode1-priv.enterprisenet.org cellnode1-priv
192.168.10.4    cellnode2-priv.enterprisenet.org cellnode2-priv
192.168.10.5    cellnode3-priv.enterprisenet.org cellnode3-priv
On CELLNODE2
#### END Generated by Exadata ####
### Compute Node Private Interface details
192.168.10.1    dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.10.2    dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
192.168.10.3    cellnode1-priv.enterprisenet.org cellnode1-priv
# 192.168.10.4  cellnode2-priv.enterprisenet.org cellnode2-priv
192.168.10.5    cellnode3-priv.enterprisenet.org cellnode3-priv
Updated value
On CELLNODE3
#### END Generated by Exadata ####
### Compute Node Private Interface details
192.168.10.1    dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.10.2    dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
192.168.10.3    cellnode1-priv.enterprisenet.org cellnode1-priv
192.168.10.4    cellnode2-priv.enterprisenet.org cellnode2-priv
# 192.168.10.5  cellnode3-priv.enterprisenet.org cellnode3-priv
11.3 cp /etc/hosts /etc/orig_hosts
11.4 update to
On both dbnode1 and dbnode2
#####192.168.10.1       dbnode1-priv.enterprisenet.org dbnode1-priv
#####192.168.10.2       dbnode2-priv.enterprisenet.org dbnode2-priv
#####192.168.10.31   dbnode1-priv.enterprisenet.org dbnode1-priv
#####192.168.10.32   dbnode2-priv.enterprisenet.org dbnode2-priv
192.168.20.31   dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.20.32   dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
#####192.168.10.3       cellnode1-priv.enterprisenet.org cellnode1-priv
#####192.168.10.4       cellnode2-priv.enterprisenet.org cellnode2-priv
#####192.168.10.5       cellnode3-priv.enterprisenet.org cellnode3-priv
#####192.168.10.33   cellnode1-priv.enterprisenet.org cellnode1-priv
#####192.168.10.34   cellnode2-priv.enterprisenet.org cellnode2-priv
#####192.168.10.35   cellnode3-priv.enterprisenet.org cellnode3-priv
192.168.20.33   cellnode1-priv.enterprisenet.org cellnode1-priv
192.168.20.34   cellnode2-priv.enterprisenet.org cellnode2-priv
192.168.20.35   cellnode3-priv.enterprisenet.org cellnode3-priv
On CELLNODE1
#### END Generated by Exadata ####
### Compute Node Private Interface details
###192.168.10.1    dbnode1-priv.enterprisenet.org dbnode1-priv
###192.168.10.2    dbnode2-priv.enterprisenet.org dbnode2-priv
192.168.20.31    dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.20.32    dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
### 192.168.10.3  cellnode1-priv.enterprisenet.org cellnode1-priv
##192.168.10.4    cellnode2-priv.enterprisenet.org cellnode2-priv
##192.168.10.5    cellnode3-priv.enterprisenet.org cellnode3-priv
# 192.168.20.33  cellnode1-priv.enterprisenet.org cellnode1-priv
192.168.20.34    cellnode2-priv.enterprisenet.org cellnode2-priv
192.168.20.35    cellnode3-priv.enterprisenet.org cellnode3-priv
On CELLNODE2
#### END Generated by Exadata ####
### Compute Node Private Interface details
###192.168.10.1    dbnode1-priv.enterprisenet.org dbnode1-priv
###192.168.10.2    dbnode2-priv.enterprisenet.org dbnode2-priv
192.168.20.31    dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.20.32    dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
##192.168.10.3    cellnode1-priv.enterprisenet.org cellnode1-priv
### 192.168.10.4  cellnode2-priv.enterprisenet.org cellnode2-priv
##192.168.10.5    cellnode3-priv.enterprisenet.org cellnode3-priv
192.168.20.33    cellnode1-priv.enterprisenet.org cellnode1-priv
# 192.168.20.34  cellnode2-priv.enterprisenet.org cellnode2-priv
192.168.20.35    cellnode3-priv.enterprisenet.org cellnode3-priv
On CELLNODE3
#### END Generated by Exadata ####
### Compute Node Private Interface details
###192.168.10.1    dbnode1-priv.enterprisenet.org dbnode1-priv
###192.168.10.2    dbnode2-priv.enterprisenet.org dbnode2-priv
192.168.20.31    dbnode1-priv.enterprisenet.org dbnode1-priv
192.168.20.32    dbnode2-priv.enterprisenet.org dbnode2-priv
### CELL Node Private Interface details
##192.168.10.3    cellnode1-priv.enterprisenet.org cellnode1-priv
## 192.168.10.4  cellnode2-priv.enterprisenet.org cellnode2-priv
###192.168.10.5    cellnode3-priv.enterprisenet.org cellnode3-priv
192.168.20.33      cellnode1-priv.enterprisenet.org cellnode1-priv
192.168.20.34       cellnode2-priv.enterprisenet.org cellnode2-priv
#192.168.20.35    cellnode3-priv.enterprisenet.org cellnode3-priv
12. Start Oracle Clusterware on each server using the following  command
/bin/crsctl start crs
13. Verify the cluster interconnect is using the RDS protocol on each database server by  examining the Oracle ASM alert.log
cd /u01/app/oracle/diag/asm/+asm/+ASM1/trace  for dbnode2
cd /u01/app/oracle/diag/asm/+asm/+ASM2/trace  for dbnode2
view alert_+ASM1.log
view alert_+ASM2.log
Search for “CELL interconnect IPC version: Oracle RDS/IP (generic)”
13.1 Check using skgxpinfo 
Current ouput
oracle >skgxpinfo
rds
13.2 If the instance is not using the RDS protocol over InfiniBand, then relink the Oracle binary as follows(if it is using RDS already, it does not change while chaging IP):
13.2.1 :As the oracle user, shut down any processes using the Oracle binary
crscrtl stop crs -f
13.2.2 As the root user
/crs/install/rootcrs.pl -unlock
13.2.3 as oracle user
cd /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/lib
make -f ins_rdbms.mk ipc_rds ioracle
13.2.4 run the following command if relinking the grid infrastructure home. Do not perform this step if you are not relinking the grid infrastructure home.
GRID_HOME/crs/install/rootcrs.pl -patch
14.Start all cluster-managed services using the SRVCTL utility as follows
14.1 Login as oracle
14.2 srvctl start home -o /u01/app/oracle/product/11.2.0/dbhome_1 -s /tmp/dbnode1_dbhome -n dbnode1
14.3 srvctl status database -d DATABASE
15. Verifiy using on both ASM and DB instance
set linesize 300
col NAME form a50
col VALUE form a50
SELECT inst_id, name,value FROM gv$parameter WHERE name =’cluster_interconnects';
16. Delete the Old Private Network
oifcfg delif -global bondib0/192.168.8.0
16.1 Verify Old Interface is no longer present
oifcfg getif
==> oifcfg getif
bondeth0  10.240.48.0  global  public
bondib0  192.168.30.0  global  cluster_interconnect
17.1 Enable Oracle Clusterware CRS automatic restart on each database server as follows
u01/app/11.2.0/grid/bin/crsctl enable crs on both nodes
18. Restart the cluster one by one and verify

Changing Admin/Management IP on Exadata

December 25, 2014 Leave a comment

The administration or management network is called the NET0 network and is used to provide shell access via SSH to the Exadata DMA. The NET0 network is enabled on interface eth0. To display the configuration, log in to a compute node and run the following ifconfig command:

[root@cm01dbm01 ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:21:28:B2:17:02
inet addr:172.16.1.10 Bcast:172.16.1.255 Mask:255.255.255.0
… Output omitted for brevity
[root@cm01dbm01 ~]#

This NET0/admin network is comprised of a single network interface and is not typically deployed with channel bonding, although in some rare cases clients choose to bond the eth0 interface with the NET3/eth3 interface to provide additional network interface redundancy. When configuring DNS for your Exadata Database Machine, the host name of each compute node is registered with the IP address of the NET0/admin interface. Validate this by using nslookup from any host on your network and compare the IP address returned from the DNS query with that of the previous ifconfig output:

Macintosh-8:~ jclarke$ nslookup cm01dbm01
Server: 11.11.1.250

Address: 11.11.1.250#53
Name: cm01dbm01.centroid.com
Address: 172.16.1.10
Macintosh-8:~ jclarke$

To change the IP address of your NET0/admin network, edit /etc/sysconfig/network-scripts/ifcfg-eth0. A sample of this configuration file based on the previous ifconfig output is provided:

root@cm01dbm01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
#### DO NOT REMOVE THESE LINES ####
#### %GENERATED BY CELL% ####
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
IPADDR=10.16.1.10
NETMASK=255.255.255.0
NETWORK=10.16.1.0
BROADCAST=10.16.1.255
GATEWAY=10.16.1.1
HOTPLUG=no
IPV6INIT=no
HWADDR=00:21:28:b2:17:02

[root@cm01dbm01 ~]#

After changing ifcfg-eth0, determine if other network interfaces require changes as well as the ILOM interface, NET1-2 interfaces, and any other configuration files. Specifically, when changing the management network’s IP address, you will need to locate the entry in /etc/hosts and make the necessary modification:

[root@cm01dbm01 ~]# grep cm01dbm01 /etc/hosts
192.168.10.1 cm01dbm01-priv.centroid.com cm01dbm01-priv
10.16.1.10 cm01dbm01.centroid.com cm01dbm01
192.168.10.1 cm01dbm01-priv.centroid.com cm01dbm01-priv

[root@cm01dbm01 ~]#

Next, change the ListenAddress to match your new eth0 IP address in /etc/ssh/sshd_config. This will enable remote users to obtain shell access via SSH to the administrative network:

[root@cm01dbm01 ~]# grep Listen /etc/ssh/sshd_config
#ListenAddress 0.0.0.0
#ListenAddress ::
ListenAddress 10.16.1.10

ListenAddress 192.168.10.1

After these changes are made, you must modify your routing rules for your management network in /etc/sysconfig/network-scripts/route-eth0. For example:

[root@cm01dbm01] # cd /etc/sysconfig/network-scripts
[root@cm01dbm01] # network-scripts]# ls route-eth0
route-eth0
[root@cm01dbm01 network-scripts]# cat route-eth0
172.16.1.0/24 dev eth0 table 220

default via 172.16.1.1 dev eth0 table 220
[root@cm01dbm01] #

After the changes are complete, restart your network services by running one of the following commands:

root@cm01dbm01 ~]# service network restart
… or
root@cm01dbm01 ~]# ifdown eth0

root@cm01dbm01 ~]# ifup eth0

Follow

Get every new post delivered to your Inbox.

Join 532 other followers