Oracle Database Appliance X4-2
 
Oracle Database Appliance X3-2
 
Oracle Database Appliance X5-2
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
 

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU replacement part, not CRU

Applies to:

Goal

 Describe the procedure needed to replace a DE2-24P chassis, including the possible need to re-program the serial-number of the chassis.

Solution

DISPATCH INSTRUCTIONS

- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?

                Training and experience with Oracle Database Appliance systems

   TIME ESTIMATE:  120 minutes

   TASK COMPLEXITY:  3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

   PROBLEM OVERVIEW: The disk centerplane in the DE2-24P/DE2-24C tray has been determined faulty and needs to be replaced. This require the whole tray chassis to be replaced as the centerplance is not considered to be field-replaceable.

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?:

   The system needs to be in such a state that the affected drive JBOD can be powered off, usually this means completely shut down of both ODA nodes.

WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE?:

Note* the commands below are run in oda_base if the ODA is running a Virtualized OS

1. Determine the serial number of the jbod chassis before shutting down the server nodes.
   
   1. From one of the nodes, type "oakcli show expander 0" and look for "sun-chassis-serial-number", make sure you have this serial number handy when it is time to re-program in the serial number

   Note* if "oakcli show expander 0" comes back with nothing, that means that 0 is not one of the expander numbers.  Use "oakcli show storage" to find the expander numbers, and use one of those.  For example:

               # oakcli show storage
==== BEGIN STORAGE DUMP ========
.......
Total number of expanders: 2
        Id         = 1    <<<<<<<<<<<<<<<<<<<<< you can use expander 1 or expander 2
        Serial Num = 50800200014751e4
        Vendor     = ORACLE
        Model      = DE2-24P
        FwVers     = 0018
        strId      = Primary
        WWN        = 50800200014c303e

        Id         = 2
        Serial Num = 50800200014751e4
        Vendor     = ORACLE
        Model      = DE2-24P
        FwVers     = 0018
        strId      = Secondary
        WWN        = 50800200014c307e

1. Shutdown GI/RDBMS stacks on the 2 nodes of this machine and bring down OS on both nodes  ** this step is typically done by the customer/admin **
2. Power off both nodes
   
   1. Power off the servers using power-button on the front, or "stop /SYS" in the ILOM cli
   2. Once the servers nodes are powered off, turn off JBOD using the power switches on the back of the array.
3. Swap JBOD chassis and re-cable, taking care to check all wiring and making sure all components go in to the same positions in the new chassis.
   
   1. Label cables and disks before removal --- location of hardware and cables is important when powered back on
4. Sequence to Power on JBOD and server nodes
   
   1. Power up JBOD first.
   2. Power on server nodes by pressing the small power-button on the front or by using "start /SYS" from the SP.
5. Verify disks are visible, and that the new JBOD is visible.  It is recommended to run these commands on both nodes to assure that each node is connected correctly.
   
   1. Use the "fwupdate list disk" command to make sure that the disks in the jbod are listed.  Each disk should be listed twice, one for each controller.
   2. Use the "oakcli show enclosure" command to make sure the jbod components are listed and in OK health. ** this command is only available in OAK version 2.8 and above
   3. Use the "oakcli validate -c storagetopology" command to verify that the cabling is correct.
6. Check the serial-number on the JBOD and if it differs from the original serial number seen in step#1, use the following procedure to re-program the serial number:
   1. If the server nodes are running oak version 12.1.2.0.0 or above, you can use the built-in utility (/opt/oracle/oak/bin/stordiag/jbod_gem_cli.sh).  If not, use the script attached to this doc.
   2. You will need to determine the device name used by this tool.  In this example, there is only 1 jbod, use the following command:

   # lsscsi -g |grep -i oracle
   [2:0:24:0]   enclosu ORACLE   DE2-24P          0018  -         /dev/sg24
   [3:0:24:0]   enclosu ORACLE   DE2-24P          0018  -         /dev/sg49
   
   we can either use /dev/sg24 or /dev/sg49 , for the sake of this document, I will use /dev/sg24

7. Run the following command to re-program in the original serial number, below is just an example, be sure to use the correct serial number, and the correct path to the jbod_gem_cli.sh tool:

7a.  If you are running version 12.1.2.0 and below:

# cd /opt/oracle/oak/bin/stordiag
# ./jbod_gem_cli.sh /dev/sg24 'set_fruid mid system_identityr serialnum "1310FM400J"'

7b.  If you are running version 12.1.2.1.0 and above:

# cd /opt/oracle/oak/bin/stordiag
#./jbod_gem_cli.sh -d /dev/sg24 -c 'set_fruid mid system_identityr serialnum "1310FM400J"'

    8.  Power off both nodes again

    9. Power off the JBOD again

    10. Start up the JBOD first , then power on the 2 nodes

    11. When they come up login to any node and lets verify the setting by running the following, the output should look like this:

# sg_ses -p 0x01 -H /dev/sg24
  ORACLE    DE2-24P           0018
    enclosure services device
Response in hex from diagnostic page: Configuration (SES)
 00     01 00 01 1b 00 00 00 00  22 00 0f 70 50 80 02 00    ........"..pP...
 10     01 68 9c 32 4f 52 41 43  4c 45 20 20 44 45 32 2d    .h.2ORACLE  DE2-
 20     32 34 50 20 20 20 20 20  20 20 20 20 30 30 31 38    24P         0018
 30     53 50 4d 53 01 00 00 78  60 0f 08 00 20 00 00 00    SPMS...x`... ...
 40     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 50     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 60     00 00 00 00 00 00 00 00  00 00 00 00 31 33 34 35    ............1310
 70     4e 4d 34 30 35 54 00 00  00 00 00 00 17 18 00 00    FM400J..........
 80     02 02 00 00 03 04 00 00  04 08 00 00 06 01 00 00    ................
 90     07 02 00 00 0e 01 00 00  12 04 00 00 13 04 00 00    ................
 a0     18 02 00 00 19 1e 00 00  86 02 00 19 89 02 00 1b    ................
 b0     8a 01 00 12 8b 02 00 21  53 42 42 20 4d 69 64 70    .......!SBB Midp
 c0     6c 61 6e 65 20 49 6e 74  65 72 63 6f 6e 6e 65 63    lane Interconnec
 d0     74 45 6e 63 6c 6f 73 75  72 65 20 45 6c 65 63 74    tEnclosure Elect
 e0     72 6f 6e 69 63 73 20 50  6f 77 65 72 45 6e 63 6c    ronics PowerEncl
 f0     6f 73 75 72 65 20 53 65  74 74 69 6e 67 73 45 6e    osure SettingsEn
 100    63 6c 6f 73 75 72 65 20  45 6c 65 63 74 72 6f 6e    closure Electron
 110    69 63 73 20 44 69 61 67  6e 6f 73 74 69 63 73       ics Diagnostics

================== End of steps ============================

OBTAIN CUSTOMER ACCEPTANCE
   WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?:

  Steps 1 through 7 above brings system back to an operational state including verification of status.

PARTS NOTE:

DE2-24P chassis part-number: 7043630

DE2-24P NEBS compliant chassis part-number: 7078863

REFERENCE INFORMATION:

Total number of expanders: 2
        Id         = 1
        Serial Num = 50800200014751e4
        Vendor     = ORACLE
        Model      = DE2-24P
        FwVers     = 0018
        strId      = Primary
        WWN        = 50800200014c303e

        Id         = 0
        Serial Num = 50800200014751e4
        Vendor     = ORACLE
        Model      = DE2-24P
        FwVers     = 0018
        strId      = Secondary
        WWN        = 50800200014c307e

References

This solution has no attachment