Chancing All Passwords on Exadata

All the components of an Exadata system have default passwords. We will look at each component and how to change the default passwords for each.

Database Server
An Exadata X5-2 has eight database servers. Each server has the following ID with defaults passwords:
•    Root
•    Oracle
•    Grid

As a user, you can either go in individually, change the passwords on each server or use the utility DCLI that Oracle provides on an Exadata to change all the passwords in parallel on all servers. Oracle provides files that include various server configurations. For the database component, the dbs_group file is used to change the root, grid and Oracle passwords on all database servers.

#cd /opt/oracle.SupportTools/onecommand
[root@xex1dbadm01 onecommand]# cat dbs_group
xex1dbadm01
xex1dbadm02
xex1dbadm03
xex1dbadm04
xex1dbadm05
xex1dbadm06
xex1dbadm07
xex1dbadm08
ORAPASS=<oraclpassword>
ROOTPASS=<rootpassword>
GRIDPASS=<gridpassword>
dcli -l root -g dbs_group “echo ${ROOTPASS} | passwd –stdin root”
dcli -l root -g dbs_group “echo ${ORAPASS} | passwd –stdin oracle”
dcli -l root -g dbs_group “echo ${GRIDPASS} | passwd –stdin grid”

This will allow for parallel execution of change password for all the servers in the file dbs_group and the end result being new passwords on all your database servers.
Database Server Service Processor
Each Oracle Exadata Database server comes with an ILOM (integrated lights on management) interface, which is also known as a service processor. Each service processor comes with a default password that should be changed immediately.

$ cd /opt/oracle.SupportTools/onecommand
HOSTLIST=`cat /opt/oracle.SupportTools/onecommand/dbs_group`
for TSOH in $HOSTLIST
do
echo $TSOH
ipmitool -H $TSOH-ilom -U root -P <old password> set password 2 <New password>
done

Cell Server Password Change
A full Exadata X5-2 comes with 14 storage cells, and, as such, it is important to be able to use DCLI to change the password,
which allows for changing all the accounts on the cell server (i.e., root, celladmin and cellmonitor).

ROOTPASS=<rootpass>
CELLADMPASS=<celladminpassword>
CELLMONPASS=<cellmonpass>
dcli -l root -g ~/cell_group “echo ${CELLADMPASS} | passwd –stdin celladmin”
dcli -l root -g ~/cell_group “echo ${CELLMONPASS} | passwd –stdin cellmonitor”
dcli -l root -g ~/cell_group “echo ${ROOTPASS} | passwd –stdin root”

Storage Cell Service Processor
Each Exadata storage cell has a service processor similar to a database server, and a similar strategy can be used to the database server for changing ILOM passwords.

$ cd /opt/oracle.SupportTools/onecommand
HOSTLIST=`cat /opt/oracle.SupportTools/onecommand/cell_group`
for TSOH in $HOSTLIST
do
echo $TSOH
ipmitool -H $TSOH-ilom -U root -P <old password> set password 2 <New password>
done

InfiniBand Switches
A Full Rack Exadata has three InfiniBand switches, and, as with other components, it is important to change the passwords. Due to Oracle Bug 13494021,
you might have to perform some extra steps on each InfiniBand switch.

ssh root@<infiniband switch>
–only if you hit bug 13494021 you will do this
cd /conf
cp -p shadow shadow.backup
cd /etc
cp -p shadow /conf/shadow
ln -sf /etc/shadow.ilom shadow
ls -l shadow*
— End Bug Fix
#Passwd nm2user
#passwd ilom-admin
#passwd root
#passwd ilom-operator

Cisco Switch

An Exadata system also contains a Cisco brand switch. It is important to check what utility is available during install time.
It is preferable to have ssh enabled on the switch rather than telnet, which ships as default on the X5-2. Oracle My Oracle Support (MOS) Note 1415044.1 can be used to reconfigure the Cisco switch to ssh only. Once the configuration is complete, you can change the password from the default using the below commands.

ssh admin@<ciscoswitch>
Switch>enable
Password:
Switch#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#enable password <new password>
Switch(config)#enable secret <new password>
The enable secret you have chosen is the same as your enable password.
This is not recommended. Re-enter the enable secret.
Switch(config)#end
Switch#write memory
#exit

Advertisements

Upgrading/Downgrading Exadata iLOM firmware

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.

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

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

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

How to Simulate an Exalogic Machine for Training Purposes

In the new “Cloud Computing” era, Oracle is leading it’s private cloud offering with the new complete hardware and software platform for Enterprise applications, Oracle Exalogic. However, even within Oracle it can be quite difficult to gain access to an Exalogic machine, and getting to know the system just by reading the documentation is a daunting task. So this post will walk you through the steps of setting up a simulated Exalogic machine, in a virtual environment, that you can use for training purposes.

After completing these steps, you will have an environment where you will be able to make the same storage, network, operating system and software configurations as on the actual Exalogic machine. Of course, this will not be suitable for production, nor will any benchmarks have any relevance. It’s just something that you can use to get yourself familiarized with the machine. If you are new to the Exalogic machine, I suggest going over the Oracle Exalogic White Paper before continuing with the steps.

So, in order to build the system, you will need:

1. Oracle Virtual Box. Download it from here and install on your system if not already installed.

2. Sun Storage Simulator. This is a pre-built virtual machine simulating the actual Sun ZFS Storage Appliance that comes with the Exalogic Machine. It can be downloaded from here.

3. The Oracle Enterprise Linux image that is applied on every compute node in the Exalogic machine. You can get it from edelivery.oracle.com by searching for to “Oracle Fusion Middleware” – “Linux x86_64″, then click on “Oracle Exalogic Elastic Cloud Software 11g Media Pack” and download the two archives with “Base Image for Exalogic Linux x86-64″ in the title. Also, you can choose to download the Solaris images from the same location.

4. Specific network Configurator for Exalogic. From the same link as in step 3 download “Oracle Exalogic 2.0.0.0.0 Configuration Utility for Exalogic Linux x86-64 and Exalogic Solaris x86-64 (64-bit)”

5. You can also download the Weblogic Server software and Coherence software from the same link on eDelivery.

Once you have downloaded the above tools, you can start building the “machine”, block-by-block:

Step 1: Installing Virtual Box

Run VirtualBox installation program and follow the instructions in the installation wizard.

Step2: Import the Sun Storage VBox

From the Oracle VM VirtualBox Manager click “File -> Import Appliance…” and go through the Import Appliance wizard choosing “Sun ZFS Storage 7000.ovf” file from the downloaded Storage Simulator. After the import, the appliance should show up in your VBox Manager:

Select the newly imported VM and click “Start”. After booting, configure the basics:

Host Name: Any name you want.
DNS Domain: “localdomain”
Default Router: The same as the IP address, but put 1 as the final octet.
DNS Server: The same as the IP address, but put 1 as the final octet.
Password: Whatever you want.

You can now access the appliance interface with a browser, accessing https://:215 , usually https://192.168.56.101:215 and login with” root” and the password provided above. After accepting a few default settings, you will see an overview screen of the appliance, just as you would see on an actual Exalogic machine:

Step 3: Creating a virtual machine for the first Compute Node

Usually a quarter rack Exalogic machine has 8 compute nodes, but for demonstration purposes it is enough to build only 2 computes nodes which will be used to cluster the Middleware components. To build a simulated compute node, we will first create a virtual box and then apply the Base Image for Exalogic Linux x86_64 on it, just like installing any Oracle Enterprise Linux.

To create the Compute Node VBox, go to the Oracle VM VirtualBox Manager and click “New”. Follow the instructions in the wizard by choosing a Linux – Oracle (64 bit) operating system, whatever name you want for the virtual machine (for example CN01) and choosing the memory resources you would like to allocate to this machine. This will hardly match the 96Gb of RAM on a real Exalogic compute node, but it will serve demonstration purposes just fine.

Step 4: Applying the Exalogic Linux x86_64 image on the simulated Compute Node

Make sure that both downloaded archives are in the same folder and then execute the runMe.sh script to merge the archives in a single file. You should obtain a “el_x2-2_baseimage_linux_1.0.0.2.0_64.iso” image file.

If on Windows, you can merge the two files by running:

copy /B el_x2-2_baseimage_linux_2.0.0.0.0_6 4.iso.part0+el_x2-2_baseimage_linux_2.0.0.0.0_64.iso.part1 el_x2-2_baseimage_lin ux_2.0.0.0.0_64.iso

el_x2-2_baseimage_linux_2.0.0.0.0_64.iso.part0

el_x2-2_baseimage_linux_2.0.0.0.0_64.iso.part1

1 file(s) copied.

Go back to the Oracle VM VirtualBox Manager and select the newly created CN01 VBox, then click on Settings. Go to “Storage” and click on “Add CD/DVD Device”. In the popup, select “Choose Disk” and navigate to the base image iso file above. You should then see the image in the IDE Controller list:

Next, navigate to “System” in the left menu and make sure that the CD/DVD-ROM is selected in the Boot Order list and is the first bootable media in the list.

Next, start up the Virtual Machine and follow the Linux OS installation process. If instead of the below screen you get a “Your CPU does not support long mode. Use a 32bit distribution” message, then you need to enable VT-x support in BIOS, depending on your host machine.

Once you install the operating system on the first compute node, you use the Oracle VirtualBox manager clone facility to create a similar virtual machine (CN02).

Step 5: Use Exalogic_one-command to configure the network interfaces and IP addresses of the storage appliance and compute nodes

After unzipping the “Oracle Exalogic 2.0.0.0.0 Configuration Utility for Exalogic” archive, you will get a series of scripts, a spreadsheet called “el_configurator.ods” and, most importantly a readme.txt file. Follow the instructions in the readme to use the spreadsheet. If not sure how to fill the IP addresses in the spreadsheet, I suggest taking a look at the Exalogic Enterprise Deployment Guide at the default Network settings. Basically, you will have to assign IP addresses to your storage and compute nodes on three interfaces:

NET0 – Management interface /ILOM

BOND0 – simulating the Private Infiniband, for traffic between the compute nodes and the storage heads (ib0 and ib1)

BOND1 – Ethernet over InfiniBand (EoIB), for Ethernet traffic, on eth interfaces.

Once you have a correct filled spreadsheet run the scripts on a master compute node (usually the first, but can be any) to configure the network “within” your Exalogic simulated machine.

All done, all that is left to do now is to consult the Enterprise Deployment Guide on how to configure the storage project and shares, install the Weblogic server and configure a domain etc.Of course, the specific optimizations for Exalogic will not be applied in this training Weblogic domain.

A good idea is to use the Oracle VM VirtualBox Manager to export this setup to a backup by going to File -> Export Appliance.. and choosing the three VBoxes you’ve just created. You will then be able to port the entire Exalogic simulated machine or restore it easily.