Login  Register

X5-2 ODA issues

Posted by Colby Merchlewitz on Mar 06, 2018; 3:27pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/X5-2-ODA-issues-tp5322.html

Hello Erman,

We are encountering a couple issues with our VM-ODA_BASE ODA X5-2 ODA, We are running OVM.

We initially were patching from DOM0, and the patch ended up trashing our second ODA_BASE node. We were able to get some of it restored but are still encountering some issues with OAKCLI commands.

I have replaced the IPS in the third comment to something generic.

1. oakcli commands don't seem to work on the oda_base node we restored:

[root@wdcoda01cn01 ~]# oakcli show repo
OAKERR:6000 Exception encountered in the module getMasterNode
OAKERR:6002 Master node was not found

2. Our storage topology seems to be off, this may be because of Firmware versions?:

[root@wdcoda01cn01 ~]# oakcli validate -c StorageTopology
 It may take a while. Please wait...
 INFO    : ODA Topology Verification
 INFO    : Running on Node1
 INFO    : Check hardware type
 SUCCESS : Type of hardware found : X5-2
 INFO    : Check for Environment(Bare Metal or Virtual Machine)
 SUCCESS : Type of environment found : Virtual Machine(ODA BASE)
 SUCCESS : Number of External SCSI controllers found : 2
 INFO    : Check for Controllers correct PCIe slot address
 SUCCESS : External LSI SAS controller 0 : 00:04.0
 SUCCESS : External LSI SAS controller 1 : 00:05.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
 FAILURE : Controller connected to correct EBOD number
 FAILURE : Controller port connected to correct EBOD port
 FAILURE : Overall Cable check for controller 0
 INFO    : Check for External Controller 1
 FAILURE : Controller connected to correct EBOD number
 FAILURE : Controller port connected to correct EBOD port
 FAILURE : Overall Cable check for Controller 1
 INFO    : Check for overall status of cable validation on Node1
 FAILURE : Overall Cable Validation on Node1
 INFO    : Check Node Identification status
 FAILURE : Node Identification
 ERROR   : Display wrong connection found on the Node
                CTRL0, PORT0 <==> JBOD0, EBOD0, PORT1
                CTRL1, PORT1 <==> JBOD0, EBOD1, PORT1
 INFO    : Correct cable connections with 1 JBOD
           NODE 0:
                CTRL0, PORT0 <==> JBOD0, EBOD1, PORT0 : [DARK BLUE CABLE]
                CTRL0, PORT1 <==> FREE
                CTRL1, PORT0 <==> FREE
                CTRL1, PORT1 <==> JBOD0, EBOD0, PORT0 : [LIGHT BLUE CABLE]
           NODE 1:
                CTRL0, PORT0 <==> FREE
                CTRL0, PORT1 <==> JBOD0, EBOD1, PORT1 : [DARK RED CABLE]
                CTRL1, PORT0 <==> JBOD0, EBOD0, PORT1 : [LIGHT RED CABLE]
                CTRL1, PORT1 <==> FREE
 INFO    : Convention Used
             CTRL0 : Controller 0
             CTRL1 : Controller 1
             <==>  : Physical cable connection between controller port and EBOD port
 INFO    : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/wdcoda01cn01/storagetopology/StorageTopology-2018-03-06-09:20:21_32048_14930.log

3. Here are the versioning details.

[root@wdcoda01cn01 ~]# oakcli show version -detail
Reading the metadata. It takes a while...
ERROR: 2018-03-06 09:16:11: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:16:11: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
ERROR: 2018-03-06 09:16:11: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:16:11: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
ERROR: 2018-03-06 09:16:11: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:16:11: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
ERROR: 2018-03-06 09:16:11: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:16:11: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
ERROR: 2018-03-06 09:16:11: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:16:11: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
ERROR: 2018-03-06 09:17:04: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:17:04: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
System Version  Component Name            Installed Version         Supported Version
--------------  ---------------           ------------------        -----------------
12.1.2.10.0
ERROR: 2018-03-06 09:17:04: Failed to connect to oakVmAgent
INFO: 2018-03-06 09:17:04: RPC::XML::Client::send_request: HTTP server error: Can't connect to 123.456.72.32:2523 (connect: Connection refused)
                Controller_EXT            13.00.00.00               10.00.00.00
                Expander                  0018                      Up-to-date
                SSD_SHARED {
                [ c1d20,c1d21,c1d22,      A29A                      Up-to-date
                c1d23 ]
                [ c1d16,c1d17,c1d18,      A29A                      Up-to-date
                c1d19 ]
                             }
                HDD_SHARED                PAG1                      Up-to-date
                ILOM                      unknown                   No-update
                BIOS                      unknown                   No-update
                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
                OVM                                                 3.2.11
                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)