Introduction
You can manage entire Oracle Database Appliance stack using oakcli command-line interface. There are several options available using oakcli, you can use the "oakcli -h" to list the options that you can use to manage ODA. Validating an ODA is an important task for ODA administrator.
[root@odanode1 ~]# oakcli -h
Usage: oakcli show - Shows disk, diskgroup, expander, controller, server, processor, memory, power, cooling, network, enclosure, storage, version, fs, raidsyncstatus, dbhomes, dbstorage, databases, db_config_params, core_config_key, env_hw, ASR
oakcli configure - Configures the Network or ASR or additional Net
oakcli apply - Applies the core_config_key
oakcli locate - Locates a disk
oakcli deploy - Deploys the Database Appliance
oakcli update - Updates the Database Appliance
oakcli validate - Validates the Database Appliance
oakcli manage - Manages the OAK repository, diagcollect etc.,
oakcli unpack - Unpack the given package to OAK repository
oakcli copy - Copies the deployment config file
oakcli upgrade - Upgrades database
oakcli stordiag - Run storage diagnostic tool on both Nodes
oakcli test - Test ASR
oakcli orachk - Performs configuration settings check on ODA
oakcli create - Creates Database, DB storage, snapshotdb, dbhome, db_config_params file
oakcli delete - Deletes Database, DB storage, dbhome, db_config_params file
oakcli modify - Performs modify opeartions on Database
oakcli resize - Resizes DB storage
In this article we will focus on validating ODA using "oakcli validate" command.
BM ODA X4-2
Public interface : COPPER
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
[root@odanode1 ~]# oakcli show dbhomes -detail
Oracle HomeName Oracle Home Version Oracle HomeLocation Database Name Database Type
---------------- --------------------- --------------------------------------- --------------- -----------
OraDb12102_home1 12.1.0.2.170117(24732082,24828633) /u01/app/oracle/product/12.1.0.2/dbhome_1 xyz12c RAC
Usage:
oakcli validate [-V | -l | -h]
oakcli validate [-v] [-f absolute output_file_name] [-a | -d | -c check1[,check2] [-ver <patch version>] <-prechecks|-postchecks>]
ARGUMENTS:
-v verbose output
-f output_file_name.The output is sent to the file instead of standard output
-a run all checks
-d run only default checks.
-c check1[,check2] run specific checks
-l list the checks and description
-V Print the Version
-h print help
EXAMPLES:
oakcli validate -l
oakcli validate -a
oakcli validate -c OSDiskStorage
oakcli validate -c SharedStorage
oakcli validate -c StorageTopology
oakcli validate -c DiskCalibration
oakcli validate -c SystemComponents,NetworkComponents,asr
oakcli validate -c ospatch -ver 12.1.2.0.0
oakcli validate -c ol6upgrade <-prechecks|postchecks>
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
RESULT: System Information:-
Manufacturer:Oracle Corporation
Product Name:SUN FIRE X4170 M3
Serial Number:xxxxxx
RESULT: BIOS Information:-
Vendor:American Megatrends Inc.
Version:17110500
Release Date:12/22/2014
BIOS Revision:11.5
Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.7.32.a r112581
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=212 Volts IN_POWER=120 Watts OUT_POWER=120 Watts
RESULT: Powersupply PS1 V_IN=214 Volts IN_POWER=120 Watts OUT_POWER=110 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=4400 RPM F1=4100 RPM
RESULT: Cooling Unit FM1 fan speed F0=4400 RPM F1=4100 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Current Speed:2900 MHz Core Enabled:8 Thread Count:16
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Current Speed:2900 MHz Core Enabled:8 Thread Count:16
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 264361708 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=19 degrees C
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Raid device /dev/md0 found clean
RESULT: Raid device /dev/md1 found clean
RESULT: Physical Volume /dev/md1 in VolGroupSys has 154920.81M out of total 599449.93M
RESULT: Volumegroup VolGroupSys consist of 1 physical volumes,contains 4 logical volumes, has 0 volume snaps with total size of 599449.93M and free space of 154920.81M
RESULT: Logical Volume LogVolOpt in VolGroupSys Volume group is of size 60.00g
RESULT: Logical Volume LogVolRoot in VolGroupSys Volume group is of size 30.00g
RESULT: Logical Volume LogVolSwap in VolGroupSys Volume group is of size 24.00g
RESULT: Logical Volume LogVolU01 in VolGroupSys Volume group is of size 300.00g
RESULT: Device /dev/mapper/VolGroupSys-LogVolRoot is mounted on / of type ext3 in (rw)
RESULT: Device /dev/md0 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolOpt is mounted on /opt of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 19978 MB free out of total 30238 MB
RESULT: /boot has 419 MB free out of total 485 MB
RESULT: /opt has 40179 MB free out of total 60476 MB
RESULT: /u01 has 252770 MB free out of total 302380 MB
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_373739864 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_373739864 has both the paths up and active
RESULT: Disk HDD_E0_S01_373740616 path1 status active device sdb with status active path2 status active device sdz with status active
SUCCESS: HDD_E0_S01_373740616 has both the paths up and active
RESULT: Disk HDD_E0_S02_373260876 path1 status active device sdc with status active path2 status active device sdaa with status active
SUCCESS: HDD_E0_S02_373260876 has both the paths up and active
RESULT: Disk HDD_E0_S03_373338164 path1 status active device sdd with status active path2 status active device sdab with status active
SUCCESS: HDD_E0_S03_373338164 has both the paths up and active
RESULT: Disk HDD_E0_S04_373746132 path1 status active device sde with status active path2 status active device sdac with status active
SUCCESS: HDD_E0_S04_373746132 has both the paths up and active
RESULT: Disk HDD_E0_S05_373581568 path1 status active device sdf with status active path2 status active device sdad with status active
SUCCESS: HDD_E0_S05_373581568 has both the paths up and active
RESULT: Disk HDD_E0_S06_373745880 path1 status active device sdg with status active path2 status active device sdae with status active
SUCCESS: HDD_E0_S06_373745880 has both the paths up and active
RESULT: Disk HDD_E0_S07_373740700 path1 status active device sdh with status active path2 status active device sdaf with status active
SUCCESS: HDD_E0_S07_373740700 has both the paths up and active
RESULT: Disk HDD_E0_S08_371918788 path1 status active device sdi with status active path2 status active device sdag with status active
SUCCESS: HDD_E0_S08_371918788 has both the paths up and active
RESULT: Disk HDD_E0_S09_371919956 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_371919956 has both the paths up and active
RESULT: Disk HDD_E0_S10_371907528 path1 status active device sdk with status active path2 status active device sdai with status active
SUCCESS: HDD_E0_S10_371907528 has both the paths up and active
RESULT: Disk HDD_E0_S11_371833792 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_371833792 has both the paths up and active
RESULT: Disk HDD_E0_S12_371908584 path1 status active device sdm with status active path2 status active device sdak with status active
SUCCESS: HDD_E0_S12_371908584 has both the paths up and active
RESULT: Disk HDD_E0_S13_371909804 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_371909804 has both the paths up and active
RESULT: Disk HDD_E0_S14_373517740 path1 status active device sdo with status active path2 status active device sdam with status active
SUCCESS: HDD_E0_S14_373517740 has both the paths up and active
RESULT: Disk HDD_E0_S15_371921536 path1 status active device sdp with status active path2 status active device sdan with status active
SUCCESS: HDD_E0_S15_371921536 has both the paths up and active
RESULT: Disk HDD_E0_S16_373740588 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: HDD_E0_S16_373740588 has both the paths up and active
RESULT: Disk HDD_E0_S17_371922120 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: HDD_E0_S17_371922120 has both the paths up and active
RESULT: Disk HDD_E0_S18_371834964 path1 status active device sds with status active path2 status active device sdaq with status active
SUCCESS: HDD_E0_S18_371834964 has both the paths up and active
RESULT: Disk HDD_E0_S19_371835288 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: HDD_E0_S19_371835288 has both the paths up and active
RESULT: Disk SSD_E0_S20_805833242 path1 status active device sdu with status active path2 status active device sdas with status active
SUCCESS: SSD_E0_S20_805833242 has both the paths up and active
RESULT: Disk SSD_E0_S21_805834016 path1 status active device sdv with status active path2 status active device sdat with status active
SUCCESS: SSD_E0_S21_805834016 has both the paths up and active
RESULT: Disk SSD_E0_S22_805833106 path1 status active device sdw with status active path2 status active device sdau with status active
SUCCESS: SSD_E0_S22_805833106 has both the paths up and active
RESULT: Disk SSD_E0_S23_805829508 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_805829508 has both the paths up and active
INFO: Doing oak network checks
RESULT: Detected active link for interface eth0 with link speed 10000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth1 with link speed 10000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth2 with link speed 1000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth3 with link speed 1000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth4 with link speed 1000Mb/s and cable type as Twisted Pair
WARNING: No Link detected for interface eth5 with cable type as Twisted Pair
INFO: Checking bonding interface status
RESULT: Bond interface bond0 is up configured in mode:fault-tolerance (active-backup) with current active interface as eth2
Slave1 interface is eth2 with status:up Link fail count=0 Maccaddr:00:10:e0:23:d9:86
Slave2 interface is eth3 with status:up Link fail count=0 Maccaddr:00:10:e0:23:d9:87
ERROR: Bond interface bond1 has 0 slave interfaces, expected 2 interface
SUCCESS: eth0 is running 192.168.16.24
SUCCESS: eth1 is running 192.168.17.24
It may take a while. Please wait...
INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance - E0
INFO : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/dstmo605001por/storagetopology/StorageTopology-2017-07-26-09:43:08_8061_20345.log
Checkname -- Description
========= ===========
*SystemComponents -- Validate system components based on ilom sensor data readings
*OSDiskStorage -- Validate OS disks and filesystem information
*SharedStorage -- Validate Shared storage and multipathing information
DiskCalibration -- Check disk performance with orion
*NetworkComponents -- Validate public and private network components
*StorageTopology -- Validate external JBOD connectivity
asr -- Validate asr components based on asr config file and ilom sensor data readings
ospatch -- Verifies whether OS patching could be successful or not
ol6upgrade -- Validates the ol6 upgrade
* -- These checks are also performed as part of default checks
It may take a while. Please wait...
INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance - E0
INFO : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/odanode1/storagetopology/StorageTopology-2017-06-28-14:17:35_10800_11311.log
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Raid device /dev/md0 found clean
RESULT: Raid device /dev/md1 found clean
RESULT: Physical Volume /dev/md1 in VolGroupSys has 369669.18M out of total 599449.93M
RESULT: Volumegroup VolGroupSys consist of 1 physical volumes,contains 4 logical volumes, has 0 volume snaps with total size of 599449.93M and free space of 369669.18M
RESULT: Logical Volume LogVolOpt in VolGroupSys Volume group is of size 60.00g
RESULT: Logical Volume LogVolRoot in VolGroupSys Volume group is of size 30.00g
RESULT: Logical Volume LogVolSwap in VolGroupSys Volume group is of size 24.00g
RESULT: Logical Volume LogVolU01 in VolGroupSys Volume group is of size 100.00g
RESULT: Device /dev/mapper/VolGroupSys-LogVolRoot is mounted on / of type ext3 in (rw)
RESULT: Device /dev/md0 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolOpt is mounted on /opt of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 13665 MB free out of total 30238 MB
RESULT: /boot has 419 MB free out of total 485 MB
RESULT: /opt has 46447 MB free out of total 60476 MB
RESULT: /u01 has 76169 MB free out of total 100794 MB
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_1464747464 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_1464747464 has both the paths up and active
RESULT: Disk HDD_E0_S01_1464755868 path1 status active device sdz with status active path2 status active device sdb with status active
SUCCESS: HDD_E0_S01_1464755868 has both the paths up and active
RESULT: Disk HDD_E0_S02_1464707864 path1 status active device sdc with status active path2 status active device sdaa with status active
SUCCESS: HDD_E0_S02_1464707864 has both the paths up and active
RESULT: Disk HDD_E0_S03_1464750264 path1 status active device sdab with status active path2 status active device sdd with status active
SUCCESS: HDD_E0_S03_1464750264 has both the paths up and active
RESULT: Disk HDD_E0_S04_1464735404 path1 status active device sdac with status active path2 status active device sde with status active
SUCCESS: HDD_E0_S04_1464735404 has both the paths up and active
RESULT: Disk HDD_E0_S05_1464754648 path1 status active device sdad with status active path2 status active device sdf with status active
SUCCESS: HDD_E0_S05_1464754648 has both the paths up and active
RESULT: Disk HDD_E0_S06_1464734536 path1 status active device sdae with status active path2 status active device sdg with status active
SUCCESS: HDD_E0_S06_1464734536 has both the paths up and active
RESULT: Disk HDD_E0_S07_1464777748 path1 status active device sdaf with status active path2 status active device sdh with status active
SUCCESS: HDD_E0_S07_1464777748 has both the paths up and active
RESULT: Disk HDD_E0_S08_1464777992 path1 status active device sdag with status active path2 status active device sdi with status active
SUCCESS: HDD_E0_S08_1464777992 has both the paths up and active
RESULT: Disk HDD_E0_S09_1464744228 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_1464744228 has both the paths up and active
RESULT: Disk HDD_E0_S10_1464734532 path1 status active device sdk with status active path2 status active device sdai with status active
SUCCESS: HDD_E0_S10_1464734532 has both the paths up and active
RESULT: Disk HDD_E0_S11_1464757412 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_1464757412 has both the paths up and active
RESULT: Disk HDD_E0_S12_1464430876 path1 status active device sdak with status active path2 status active device sdm with status active
SUCCESS: HDD_E0_S12_1464430876 has both the paths up and active
RESULT: Disk HDD_E0_S13_1464736940 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_1464736940 has both the paths up and active
RESULT: Disk HDD_E0_S14_1464781048 path1 status active device sdam with status active path2 status active device sdo with status active
SUCCESS: HDD_E0_S14_1464781048 has both the paths up and active
RESULT: Disk HDD_E0_S15_1464786920 path1 status active device sdan with status active path2 status active device sdp with status active
SUCCESS: HDD_E0_S15_1464786920 has both the paths up and active
RESULT: Disk HDD_E0_S16_1464781112 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: HDD_E0_S16_1464781112 has both the paths up and active
RESULT: Disk HDD_E0_S17_1464780984 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: HDD_E0_S17_1464780984 has both the paths up and active
RESULT: Disk HDD_E0_S18_1464786496 path1 status active device sdaq with status active path2 status active device sds with status active
SUCCESS: HDD_E0_S18_1464786496 has both the paths up and active
RESULT: Disk HDD_E0_S19_1464781148 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: HDD_E0_S19_1464781148 has both the paths up and active
RESULT: Disk SSD_E0_S20_805976279 path1 status active device sdas with status active path2 status active device sdu with status active
SUCCESS: SSD_E0_S20_805976279 has both the paths up and active
RESULT: Disk SSD_E0_S21_805976092 path1 status active device sdat with status active path2 status active device sdv with status active
SUCCESS: SSD_E0_S21_805976092 has both the paths up and active
RESULT: Disk SSD_E0_S22_805976245 path1 status active device sdau with status active path2 status active device sdw with status active
SUCCESS: SSD_E0_S22_805976245 has both the paths up and active
RESULT: Disk SSD_E0_S23_805976275 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_805976275 has both the paths up and active
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
RESULT: System Information:-
Manufacturer:Oracle Corporation
Product Name:SUN SERVER X4-2
Serial Number:1438NML03N
RESULT: BIOS Information:-
Vendor:American Megatrends Inc.
Version:25040100
Release Date:11/09/2016
BIOS Revision:4.1
Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.8.25 r114493
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=118 Volts IN_POWER=130 Watts OUT_POWER=120 Watts
RESULT: Powersupply PS1 V_IN=116 Volts IN_POWER=130 Watts OUT_POWER=110 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=5900 RPM F1=3100 RPM
RESULT: Cooling Unit FM1 fan speed F0=6300 RPM F1=3400 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Current Speed:2700 MHz Core Enabled:12 Thread Count:24
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Current Speed:2700 MHz Core Enabled:12 Thread Count:24
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 264360108 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=23 degrees C
[root@odanode1 ~]# oakcli validate -c DiskCalibration
INFO: Doing oak disk calibration checks
INFO: About to run random read IOPS throughput tests for SASDisk
RESULT: Random read throughput across all 20 SASDisk = 3195 IOPS
INFO: About to run random read IOPS throughput tests for SSDDisk
RESULT: Random read throughput across all 4 SSDDisk = 99947 IOPS
INFO: About to run random read MBPS throughput tests for SASDisk
RESULT: Random read throughput across all 20 SASDisk = 1689 MBPS
INFO: About to run random read MBPS throughput tests for SSDDisk
RESULT: Random read throughput across all 4 SSDDisk = 1506 MBPS
INFO: Completed IOPS tests for individual disks of type SASDisk
INFO: Completed MBPS tests for individual disks of type SASDisk
INFO: Completed IOPS tests for individual disks of type SSDDisk
INFO: Completed MBPS tests for individual disks of type SSDDisk
INFO: Completed all single disk tests
INFO: Calibration results for SASDisk
RESULT: Random read throughput of HDD_E0_S13_1464736940 is 236 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S05_1464754648 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S03_1464750264 is 239 IOPS 156 MBPS
RESULT: Random read throughput of HDD_E0_S00_1464747464 is 238 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S11_1464757412 is 238 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S15_1464786920 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S07_1464777748 is 238 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S16_1464781112 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S14_1464781048 is 238 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S09_1464744228 is 237 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S01_1464755868 is 237 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S02_1464707864 is 240 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S08_1464777992 is 238 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S06_1464734536 is 236 IOPS 147 MBPS
RESULT: Random read throughput of HDD_E0_S04_1464735404 is 236 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S17_1464780984 is 235 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S18_1464786496 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S10_1464734532 is 233 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S19_1464781148 is 202 IOPS 130 MBPS
RESULT: Random read throughput of HDD_E0_S12_1464430876 is 236 IOPS 148 MBPS
INFO: Calibration results for SSDDisk
RESULT: Random read throughput of SSD_E0_S23_805976275 is 39761 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S22_805976245 is 39463 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S21_805976092 is 39683 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S20_805976279 is 43784 IOPS 434 MBPS
INFO: oak Asr information and Validations
RESULT: /opt/oracle/oak/conf/asr.conf exist
RESULT: ASR Manager ip:192.168.1.11
RESULT: ASR Manager port:162
SUCCESS: ASR configuration file validation successfully completed
RESULT: ilom alertmgmt level is set to minor
RESULT: ilom alertmgmt type is set to snmptrap
RESULT: alertmgmt snmp_version is set to 2c
RESULT: alertmgmt community_or_username is set to public
RESULT: alertmgmt destination is set to 192.168.1.11
RESULT: alertmgmt destination_port is set to 162
SUCCESS: Ilom snmp confguration for asr set correctly
RESULT: /etc/hosts has entry 141.146.1.169 transport.oracle.com
RESULT: notification trap configured to ip:192.168.1.11
RESULT: notification trap configured to port:162
SUCCESS: Asr notification trap set correctly
.....
.....
.....
Conclusion
In this article we have learned several Oracle Database Applinace validation commands along with their outputs. Validating ODA is an important task for an administrator to ensure there are hardware or software issues. oakcli command line interface made it easy to manage the entire ODA stack. Thanks to oakcli.
You can manage entire Oracle Database Appliance stack using oakcli command-line interface. There are several options available using oakcli, you can use the "oakcli -h" to list the options that you can use to manage ODA. Validating an ODA is an important task for ODA administrator.
[root@odanode1 ~]# oakcli -h
Usage: oakcli show - Shows disk, diskgroup, expander, controller, server, processor, memory, power, cooling, network, enclosure, storage, version, fs, raidsyncstatus, dbhomes, dbstorage, databases, db_config_params, core_config_key, env_hw, ASR
oakcli configure - Configures the Network or ASR or additional Net
oakcli apply - Applies the core_config_key
oakcli locate - Locates a disk
oakcli deploy - Deploys the Database Appliance
oakcli update - Updates the Database Appliance
oakcli validate - Validates the Database Appliance
oakcli manage - Manages the OAK repository, diagcollect etc.,
oakcli unpack - Unpack the given package to OAK repository
oakcli copy - Copies the deployment config file
oakcli upgrade - Upgrades database
oakcli stordiag - Run storage diagnostic tool on both Nodes
oakcli test - Test ASR
oakcli orachk - Performs configuration settings check on ODA
oakcli create - Creates Database, DB storage, snapshotdb, dbhome, db_config_params file
oakcli delete - Deletes Database, DB storage, dbhome, db_config_params file
oakcli modify - Performs modify opeartions on Database
oakcli resize - Resizes DB storage
In this article we will focus on validating ODA using "oakcli validate" command.
- To check if the ODA is Bare Metal or Virtual Platform setup, execute the following command:
BM ODA X4-2
Public interface : COPPER
- To check the ODA software and its components versions, execute the following command:
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
- To check the Oracle Homes and their versions, execute the following command:
[root@odanode1 ~]# oakcli show dbhomes -detail
Oracle HomeName Oracle Home Version Oracle HomeLocation Database Name Database Type
---------------- --------------------- --------------------------------------- --------------- -----------
OraDb12102_home1 12.1.0.2.170117(24732082,24828633) /u01/app/oracle/product/12.1.0.2/dbhome_1 xyz12c RAC
Validate Oracle Databsae Appliance
- To list options available with "oakcli valiadate", execute the following command:
Usage:
oakcli validate [-V | -l | -h]
oakcli validate [-v] [-f absolute output_file_name] [-a | -d | -c check1[,check2] [-ver <patch version>] <-prechecks|-postchecks>]
ARGUMENTS:
-v verbose output
-f output_file_name.The output is sent to the file instead of standard output
-a run all checks
-d run only default checks.
-c check1[,check2] run specific checks
-l list the checks and description
-V Print the Version
-h print help
EXAMPLES:
oakcli validate -l
oakcli validate -a
oakcli validate -c OSDiskStorage
oakcli validate -c SharedStorage
oakcli validate -c StorageTopology
oakcli validate -c DiskCalibration
oakcli validate -c SystemComponents,NetworkComponents,asr
oakcli validate -c ospatch -ver 12.1.2.0.0
oakcli validate -c ol6upgrade <-prechecks|postchecks>
- To perform default ODA checks, execute the following command:
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
RESULT: System Information:-
Manufacturer:Oracle Corporation
Product Name:SUN FIRE X4170 M3
Serial Number:xxxxxx
RESULT: BIOS Information:-
Vendor:American Megatrends Inc.
Version:17110500
Release Date:12/22/2014
BIOS Revision:11.5
Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.7.32.a r112581
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=212 Volts IN_POWER=120 Watts OUT_POWER=120 Watts
RESULT: Powersupply PS1 V_IN=214 Volts IN_POWER=120 Watts OUT_POWER=110 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=4400 RPM F1=4100 RPM
RESULT: Cooling Unit FM1 fan speed F0=4400 RPM F1=4100 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Current Speed:2900 MHz Core Enabled:8 Thread Count:16
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Current Speed:2900 MHz Core Enabled:8 Thread Count:16
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 264361708 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=19 degrees C
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Raid device /dev/md0 found clean
RESULT: Raid device /dev/md1 found clean
RESULT: Physical Volume /dev/md1 in VolGroupSys has 154920.81M out of total 599449.93M
RESULT: Volumegroup VolGroupSys consist of 1 physical volumes,contains 4 logical volumes, has 0 volume snaps with total size of 599449.93M and free space of 154920.81M
RESULT: Logical Volume LogVolOpt in VolGroupSys Volume group is of size 60.00g
RESULT: Logical Volume LogVolRoot in VolGroupSys Volume group is of size 30.00g
RESULT: Logical Volume LogVolSwap in VolGroupSys Volume group is of size 24.00g
RESULT: Logical Volume LogVolU01 in VolGroupSys Volume group is of size 300.00g
RESULT: Device /dev/mapper/VolGroupSys-LogVolRoot is mounted on / of type ext3 in (rw)
RESULT: Device /dev/md0 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolOpt is mounted on /opt of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 19978 MB free out of total 30238 MB
RESULT: /boot has 419 MB free out of total 485 MB
RESULT: /opt has 40179 MB free out of total 60476 MB
RESULT: /u01 has 252770 MB free out of total 302380 MB
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_373739864 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_373739864 has both the paths up and active
RESULT: Disk HDD_E0_S01_373740616 path1 status active device sdb with status active path2 status active device sdz with status active
SUCCESS: HDD_E0_S01_373740616 has both the paths up and active
RESULT: Disk HDD_E0_S02_373260876 path1 status active device sdc with status active path2 status active device sdaa with status active
SUCCESS: HDD_E0_S02_373260876 has both the paths up and active
RESULT: Disk HDD_E0_S03_373338164 path1 status active device sdd with status active path2 status active device sdab with status active
SUCCESS: HDD_E0_S03_373338164 has both the paths up and active
RESULT: Disk HDD_E0_S04_373746132 path1 status active device sde with status active path2 status active device sdac with status active
SUCCESS: HDD_E0_S04_373746132 has both the paths up and active
RESULT: Disk HDD_E0_S05_373581568 path1 status active device sdf with status active path2 status active device sdad with status active
SUCCESS: HDD_E0_S05_373581568 has both the paths up and active
RESULT: Disk HDD_E0_S06_373745880 path1 status active device sdg with status active path2 status active device sdae with status active
SUCCESS: HDD_E0_S06_373745880 has both the paths up and active
RESULT: Disk HDD_E0_S07_373740700 path1 status active device sdh with status active path2 status active device sdaf with status active
SUCCESS: HDD_E0_S07_373740700 has both the paths up and active
RESULT: Disk HDD_E0_S08_371918788 path1 status active device sdi with status active path2 status active device sdag with status active
SUCCESS: HDD_E0_S08_371918788 has both the paths up and active
RESULT: Disk HDD_E0_S09_371919956 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_371919956 has both the paths up and active
RESULT: Disk HDD_E0_S10_371907528 path1 status active device sdk with status active path2 status active device sdai with status active
SUCCESS: HDD_E0_S10_371907528 has both the paths up and active
RESULT: Disk HDD_E0_S11_371833792 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_371833792 has both the paths up and active
RESULT: Disk HDD_E0_S12_371908584 path1 status active device sdm with status active path2 status active device sdak with status active
SUCCESS: HDD_E0_S12_371908584 has both the paths up and active
RESULT: Disk HDD_E0_S13_371909804 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_371909804 has both the paths up and active
RESULT: Disk HDD_E0_S14_373517740 path1 status active device sdo with status active path2 status active device sdam with status active
SUCCESS: HDD_E0_S14_373517740 has both the paths up and active
RESULT: Disk HDD_E0_S15_371921536 path1 status active device sdp with status active path2 status active device sdan with status active
SUCCESS: HDD_E0_S15_371921536 has both the paths up and active
RESULT: Disk HDD_E0_S16_373740588 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: HDD_E0_S16_373740588 has both the paths up and active
RESULT: Disk HDD_E0_S17_371922120 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: HDD_E0_S17_371922120 has both the paths up and active
RESULT: Disk HDD_E0_S18_371834964 path1 status active device sds with status active path2 status active device sdaq with status active
SUCCESS: HDD_E0_S18_371834964 has both the paths up and active
RESULT: Disk HDD_E0_S19_371835288 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: HDD_E0_S19_371835288 has both the paths up and active
RESULT: Disk SSD_E0_S20_805833242 path1 status active device sdu with status active path2 status active device sdas with status active
SUCCESS: SSD_E0_S20_805833242 has both the paths up and active
RESULT: Disk SSD_E0_S21_805834016 path1 status active device sdv with status active path2 status active device sdat with status active
SUCCESS: SSD_E0_S21_805834016 has both the paths up and active
RESULT: Disk SSD_E0_S22_805833106 path1 status active device sdw with status active path2 status active device sdau with status active
SUCCESS: SSD_E0_S22_805833106 has both the paths up and active
RESULT: Disk SSD_E0_S23_805829508 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_805829508 has both the paths up and active
INFO: Doing oak network checks
RESULT: Detected active link for interface eth0 with link speed 10000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth1 with link speed 10000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth2 with link speed 1000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth3 with link speed 1000Mb/s and cable type as Twisted Pair
RESULT: Detected active link for interface eth4 with link speed 1000Mb/s and cable type as Twisted Pair
WARNING: No Link detected for interface eth5 with cable type as Twisted Pair
INFO: Checking bonding interface status
RESULT: Bond interface bond0 is up configured in mode:fault-tolerance (active-backup) with current active interface as eth2
Slave1 interface is eth2 with status:up Link fail count=0 Maccaddr:00:10:e0:23:d9:86
Slave2 interface is eth3 with status:up Link fail count=0 Maccaddr:00:10:e0:23:d9:87
ERROR: Bond interface bond1 has 0 slave interfaces, expected 2 interface
SUCCESS: eth0 is running 192.168.16.24
SUCCESS: eth1 is running 192.168.17.24
It may take a while. Please wait...
INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance - E0
INFO : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/dstmo605001por/storagetopology/StorageTopology-2017-07-26-09:43:08_8061_20345.log
- To list the different validation checks and their description, execute the following command.
Checkname -- Description
========= ===========
*SystemComponents -- Validate system components based on ilom sensor data readings
*OSDiskStorage -- Validate OS disks and filesystem information
*SharedStorage -- Validate Shared storage and multipathing information
DiskCalibration -- Check disk performance with orion
*NetworkComponents -- Validate public and private network components
*StorageTopology -- Validate external JBOD connectivity
asr -- Validate asr components based on asr config file and ilom sensor data readings
ospatch -- Verifies whether OS patching could be successful or not
ol6upgrade -- Validates the ol6 upgrade
* -- These checks are also performed as part of default checks
- To validate JBOD (just a bunch of disks) connectivity, execute the following command:
It may take a while. Please wait...
INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X4-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO : Check number of Controllers
SUCCESS : Number of Internal LSI SAS controller found : 1
SUCCESS : Number of External LSI SAS controller found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller : 50:00.0
SUCCESS : External LSI SAS controller 0 : 30:00.0
SUCCESS : External LSI SAS controller 1 : 40:00.0
INFO : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance - E0
INFO : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/odanode1/storagetopology/StorageTopology-2017-06-28-14:17:35_10800_11311.log
- To Validate OS disks and filesystem information, execute the following command:
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Raid device /dev/md0 found clean
RESULT: Raid device /dev/md1 found clean
RESULT: Physical Volume /dev/md1 in VolGroupSys has 369669.18M out of total 599449.93M
RESULT: Volumegroup VolGroupSys consist of 1 physical volumes,contains 4 logical volumes, has 0 volume snaps with total size of 599449.93M and free space of 369669.18M
RESULT: Logical Volume LogVolOpt in VolGroupSys Volume group is of size 60.00g
RESULT: Logical Volume LogVolRoot in VolGroupSys Volume group is of size 30.00g
RESULT: Logical Volume LogVolSwap in VolGroupSys Volume group is of size 24.00g
RESULT: Logical Volume LogVolU01 in VolGroupSys Volume group is of size 100.00g
RESULT: Device /dev/mapper/VolGroupSys-LogVolRoot is mounted on / of type ext3 in (rw)
RESULT: Device /dev/md0 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolOpt is mounted on /opt of type ext3 in (rw)
RESULT: Device /dev/mapper/VolGroupSys-LogVolU01 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 13665 MB free out of total 30238 MB
RESULT: /boot has 419 MB free out of total 485 MB
RESULT: /opt has 46447 MB free out of total 60476 MB
RESULT: /u01 has 76169 MB free out of total 100794 MB
- To Validate Shared storage and multipathing information, execute the following command:
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_1464747464 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_1464747464 has both the paths up and active
RESULT: Disk HDD_E0_S01_1464755868 path1 status active device sdz with status active path2 status active device sdb with status active
SUCCESS: HDD_E0_S01_1464755868 has both the paths up and active
RESULT: Disk HDD_E0_S02_1464707864 path1 status active device sdc with status active path2 status active device sdaa with status active
SUCCESS: HDD_E0_S02_1464707864 has both the paths up and active
RESULT: Disk HDD_E0_S03_1464750264 path1 status active device sdab with status active path2 status active device sdd with status active
SUCCESS: HDD_E0_S03_1464750264 has both the paths up and active
RESULT: Disk HDD_E0_S04_1464735404 path1 status active device sdac with status active path2 status active device sde with status active
SUCCESS: HDD_E0_S04_1464735404 has both the paths up and active
RESULT: Disk HDD_E0_S05_1464754648 path1 status active device sdad with status active path2 status active device sdf with status active
SUCCESS: HDD_E0_S05_1464754648 has both the paths up and active
RESULT: Disk HDD_E0_S06_1464734536 path1 status active device sdae with status active path2 status active device sdg with status active
SUCCESS: HDD_E0_S06_1464734536 has both the paths up and active
RESULT: Disk HDD_E0_S07_1464777748 path1 status active device sdaf with status active path2 status active device sdh with status active
SUCCESS: HDD_E0_S07_1464777748 has both the paths up and active
RESULT: Disk HDD_E0_S08_1464777992 path1 status active device sdag with status active path2 status active device sdi with status active
SUCCESS: HDD_E0_S08_1464777992 has both the paths up and active
RESULT: Disk HDD_E0_S09_1464744228 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_1464744228 has both the paths up and active
RESULT: Disk HDD_E0_S10_1464734532 path1 status active device sdk with status active path2 status active device sdai with status active
SUCCESS: HDD_E0_S10_1464734532 has both the paths up and active
RESULT: Disk HDD_E0_S11_1464757412 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_1464757412 has both the paths up and active
RESULT: Disk HDD_E0_S12_1464430876 path1 status active device sdak with status active path2 status active device sdm with status active
SUCCESS: HDD_E0_S12_1464430876 has both the paths up and active
RESULT: Disk HDD_E0_S13_1464736940 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_1464736940 has both the paths up and active
RESULT: Disk HDD_E0_S14_1464781048 path1 status active device sdam with status active path2 status active device sdo with status active
SUCCESS: HDD_E0_S14_1464781048 has both the paths up and active
RESULT: Disk HDD_E0_S15_1464786920 path1 status active device sdan with status active path2 status active device sdp with status active
SUCCESS: HDD_E0_S15_1464786920 has both the paths up and active
RESULT: Disk HDD_E0_S16_1464781112 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: HDD_E0_S16_1464781112 has both the paths up and active
RESULT: Disk HDD_E0_S17_1464780984 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: HDD_E0_S17_1464780984 has both the paths up and active
RESULT: Disk HDD_E0_S18_1464786496 path1 status active device sdaq with status active path2 status active device sds with status active
SUCCESS: HDD_E0_S18_1464786496 has both the paths up and active
RESULT: Disk HDD_E0_S19_1464781148 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: HDD_E0_S19_1464781148 has both the paths up and active
RESULT: Disk SSD_E0_S20_805976279 path1 status active device sdas with status active path2 status active device sdu with status active
SUCCESS: SSD_E0_S20_805976279 has both the paths up and active
RESULT: Disk SSD_E0_S21_805976092 path1 status active device sdat with status active path2 status active device sdv with status active
SUCCESS: SSD_E0_S21_805976092 has both the paths up and active
RESULT: Disk SSD_E0_S22_805976245 path1 status active device sdau with status active path2 status active device sdw with status active
SUCCESS: SSD_E0_S22_805976245 has both the paths up and active
RESULT: Disk SSD_E0_S23_805976275 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_805976275 has both the paths up and active
- To Validate system components based on ilom sensor data readings, execute the following command:
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.10.0
Controller_INT 11.05.03.00 Up-to-date
Controller_EXT 11.05.03.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED 944A Up-to-date
HDD_LOCAL A72A Up-to-date
HDD_SHARED A72A Up-to-date
ILOM 3.2.8.25 r114493 Up-to-date
BIOS 25040100 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.5.2.8 Up-to-date
OAK 12.1.2.10.0 Up-to-date
OL 6.8 Up-to-date
GI_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
DB_HOME 12.1.0.2.170117(2473 Up-to-date
2082,24828633)
RESULT: System Information:-
Manufacturer:Oracle Corporation
Product Name:SUN SERVER X4-2
Serial Number:1438NML03N
RESULT: BIOS Information:-
Vendor:American Megatrends Inc.
Version:25040100
Release Date:11/09/2016
BIOS Revision:4.1
Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.8.25 r114493
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=118 Volts IN_POWER=130 Watts OUT_POWER=120 Watts
RESULT: Powersupply PS1 V_IN=116 Volts IN_POWER=130 Watts OUT_POWER=110 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=5900 RPM F1=3100 RPM
RESULT: Cooling Unit FM1 fan speed F0=6300 RPM F1=3400 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Current Speed:2700 MHz Core Enabled:12 Thread Count:24
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Current Speed:2700 MHz Core Enabled:12 Thread Count:24
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 264360108 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=23 degrees C
- To Check disk performance, execute the following command:
(Do not execute it on a business system. It may degrade the performance)
[root@odanode1 ~]# oakcli validate -c DiskCalibration
INFO: Doing oak disk calibration checks
INFO: About to run random read IOPS throughput tests for SASDisk
RESULT: Random read throughput across all 20 SASDisk = 3195 IOPS
INFO: About to run random read IOPS throughput tests for SSDDisk
RESULT: Random read throughput across all 4 SSDDisk = 99947 IOPS
INFO: About to run random read MBPS throughput tests for SASDisk
RESULT: Random read throughput across all 20 SASDisk = 1689 MBPS
INFO: About to run random read MBPS throughput tests for SSDDisk
RESULT: Random read throughput across all 4 SSDDisk = 1506 MBPS
INFO: Completed IOPS tests for individual disks of type SASDisk
INFO: Completed MBPS tests for individual disks of type SASDisk
INFO: Completed IOPS tests for individual disks of type SSDDisk
INFO: Completed MBPS tests for individual disks of type SSDDisk
INFO: Completed all single disk tests
INFO: Calibration results for SASDisk
RESULT: Random read throughput of HDD_E0_S13_1464736940 is 236 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S05_1464754648 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S03_1464750264 is 239 IOPS 156 MBPS
RESULT: Random read throughput of HDD_E0_S00_1464747464 is 238 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S11_1464757412 is 238 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S15_1464786920 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S07_1464777748 is 238 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S16_1464781112 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S14_1464781048 is 238 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S09_1464744228 is 237 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S01_1464755868 is 237 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S02_1464707864 is 240 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S08_1464777992 is 238 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S06_1464734536 is 236 IOPS 147 MBPS
RESULT: Random read throughput of HDD_E0_S04_1464735404 is 236 IOPS 150 MBPS
RESULT: Random read throughput of HDD_E0_S17_1464780984 is 235 IOPS 149 MBPS
RESULT: Random read throughput of HDD_E0_S18_1464786496 is 240 IOPS 148 MBPS
RESULT: Random read throughput of HDD_E0_S10_1464734532 is 233 IOPS 151 MBPS
RESULT: Random read throughput of HDD_E0_S19_1464781148 is 202 IOPS 130 MBPS
RESULT: Random read throughput of HDD_E0_S12_1464430876 is 236 IOPS 148 MBPS
INFO: Calibration results for SSDDisk
RESULT: Random read throughput of SSD_E0_S23_805976275 is 39761 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S22_805976245 is 39463 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S21_805976092 is 39683 IOPS 433 MBPS
RESULT: Random read throughput of SSD_E0_S20_805976279 is 43784 IOPS 434 MBPS
- To Validate asr components based on asr config file, execute the following command:
INFO: oak Asr information and Validations
RESULT: /opt/oracle/oak/conf/asr.conf exist
RESULT: ASR Manager ip:192.168.1.11
RESULT: ASR Manager port:162
SUCCESS: ASR configuration file validation successfully completed
RESULT: ilom alertmgmt level is set to minor
RESULT: ilom alertmgmt type is set to snmptrap
RESULT: alertmgmt snmp_version is set to 2c
RESULT: alertmgmt community_or_username is set to public
RESULT: alertmgmt destination is set to 192.168.1.11
RESULT: alertmgmt destination_port is set to 162
SUCCESS: Ilom snmp confguration for asr set correctly
RESULT: /etc/hosts has entry 141.146.1.169 transport.oracle.com
RESULT: notification trap configured to ip:192.168.1.11
RESULT: notification trap configured to port:162
SUCCESS: Asr notification trap set correctly
.....
.....
.....
Conclusion
In this article we have learned several Oracle Database Applinace validation commands along with their outputs. Validating ODA is an important task for an administrator to ensure there are hardware or software issues. oakcli command line interface made it easy to manage the entire ODA stack. Thanks to oakcli.
No comments:
Post a Comment