How to shut down Exalogic Elastic Cloud Storage Head prior to FRU replacement

Asset ID:	1-71-1605561.1
Update Date:	2018-04-16
Keywords:

Solution Type Technical Instruction Sure

Solution 1605561.1 : How to shut down Exalogic Elastic Cloud Storage Head prior to FRU replacement

Applies to:

Exalogic Elastic Cloud X5-2 Full Rack - Version X5 and later
Exalogic Elastic Cloud X5-2 Half Rack - Version X5 and later
Exalogic Elastic Cloud X5-2 Quarter Rack - Version X5 and later
Exalogic Elastic Cloud X5-2 Eighth Rack - Version X5 and later
Exalogic Elastic Cloud X3-2 Eighth Rack - Version X3 and later
Information in this document applies to any platform.

Goal

This note is to document what condition the Exalogic compute node servers should be in prior to FRU replacement by a field engineer.

Solution

WHAT STATE SHOULD THE EXALOGIC ELASTIC CLOUD STORAGE HEAD BE IN PRIOR TO FRU REPLACEMENT:

If the storage head to be serviced is the active node, customer should work with field engineer to fail over the storage head as to put it in standby. Then the field engineer will power off the storage head and remove the AC power cords.

NOTE - This is an Engineered system. The system administrator should prepare the system for service by performing any application related functions required to shutdown the node. This might include but is not limited to performing a system backup, failover of application or services, and finally a system shutdown.

NOTE - This is not a normal situation for a ZFS-SA the usual status is Clustered/Clustered. This is _only_ a requirement for the Exalogic to have a clustered ZFS-SA in cluster status Owner/Striped, which represents a take-over situation.

Note - Takeover will work but the ZFSSA recommended path is power off which causes a faster/saner “takeover”.

Procedure to check which storage head is Active or Ready (standby):

We will need to verify the storage cluster status and determine if the target storage node currently hosting the cluster resources and if so perform a failover.

- Login to target storage node.
- Verify cluster status, one node should report AKCS_OWNER and the other AKCS_STRIPPED. If this is not the case, DO NOT CONTINUE with this process until you resolve any cluster issues as failure to do so could result in a service outage.

Example of Active Storage Node (state = AKCS_OWNER):

sn01:> configuration cluster show
Properties:
                         state = AKCS_OWNER
                   description = Active (takeover completed)
                      peer_asn = d6df4e45-3677-4ac0-9aaa-90746df9d6a5
                 peer_hostname = sn02
                    peer_state = AKCS_STRIPPED
              peer_description = Ready (waiting for failback)

Children:
                        resources => Configure resources

Example of Passive Storage Node (state = AKCS_STRIPPED):

sn02:> configuration cluster show
Properties:
                         state = AKCS_STRIPPED
                   description = Ready (waiting for failback)
                      peer_asn = eeac79d6-5822-6ca6-e4dd-c68b25265f21
                 peer_hostname = sn01
                    peer_state = AKCS_OWNER
              peer_description = Active (takeover completed)

Children:
                        resources => Configure resources

- Determine if the target node is currently hosting the clustered resources (see previous step). If this is the case we have two options, shutdown the target node (will force resource failover to the alternate node) or perform a 'takeover' operation from the alternate (AKCS_STRIPPED) node.

Example of Node shutdown:

sn01:> maintenance system poweroff <CR>
This will turn off power to the appliance. Are you sure? (Y/N)

Example of Storage Node takeover:

sn02:> configuration cluster 
sn02:configuration cluster> takeover
Continuing will immediately take over the resources assigned to the cluster
peer. This may result in clients experiencing a slight delay in service.

Are you sure? (Y/N)

Note: The 'takeover' operation will result in failover of the clustered resources and will initiate a reboot of the original owner. You will either need to wait for the reboot to complete and shutdown the node or intercept the reboot operation and force a poweroff via ILOM (stop /SYS).

- If resource failover was required, check the alternate node to ensure the cluster resources migrated successfully (state should transition from AKCS_STRIPPED to AKCS_OWNER).

To Power off the Storage Head for service:

Method 1 using the Storage BUI/CLI

Method 2 using the ILOM interface

Documents available in MOS to assist the System Adminstrator to shut down the system in an orderly manner prior to FRU replacement by field engineer:

Steps To Shut Down/Power Off Exalogic Machine (Doc ID 1533391.1)

Full Stop/Start Sequence For Exalogic Virtualized Environment (Doc ID 1564397.1)

Master Note for Oracle Exalogic (Doc ID 1301247.1)

Exalogic Owners Guide

Attachments

This solution has no attachment