Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-2158378.1
Update Date:2017-06-05
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  2158378.1 :   Exalogic : Procedure to stop and start all vServers during Compute Node maintenance  


Related Items
  • Oracle Exalogic Elastic Cloud Software
  •  
  • Exalogic Elastic Cloud X5-2 Hardware
  •  
  • Exalogic Elastic Cloud X4-2 Hardware
  •  
  • Oracle Exalogic Elastic Cloud X2-2 Hardware
  •  
  • Exalogic Elastic Cloud X3-2 Hardware
  •  
  • Exalogic Elastic Cloud X6-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>Exalogic/OVCA>Oracle Exalogic>MW: Exalogic Core
  •  




In this Document
Purpose
Scope
Details
 Preparation
 1.1 Download required script.
 1.2 Enable script executive mode.
 1.3 Save all vServers list.
 Problematic Computer Node is CN01 or CN02
 2.1 Stop control stack vServers.
 2.2 Stop all vServers.
 2.3. Power off computer node and perform maintenance tasks.
 2.4 Start control stack vServers.
 2.5 Start all vServers.
 Problematic Computer Node is neither CN01 nor CN02
 3.1 Stop all vServers.
 3.2 Power off computer node and perform maintenance tasks.
 3.3 Start all vServers.
References


Created from <SR 3-12978011036>

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.4.0.0 and later
Exalogic Elastic Cloud X5-2 Hardware - Version X5 to X5 [Release X5]
Exalogic Elastic Cloud X4-2 Hardware - Version X4 to X4 [Release X4]
Exalogic Elastic Cloud X3-2 Hardware - Version X3 to X3 [Release X3]
Oracle Exalogic Elastic Cloud X2-2 Hardware - Version X2 to X2 [Release X2]
Linux x86-64
Oracle Virtual Server(x86-64)

Purpose

This document provides detailed steps to stop and start all vServers in a Computer Node during a scheduled maintenance window for actions such as failed memory replacement.

Scope

 This document should be referred by hardware engineers before creating a task if problematic box needs to power off.

Details

Preparation

1.1 Download required script.

Here : cnode-vserver-control.py

1.2 Enable script executive mode.

chmod u+x cnode-vserver-control.py

1.3 Save all vServers list.

./cnode-vserver-control.py -a save

The script will list the currently running vServer, inspect its vm.cfg searching for the HA flag value, inspect the 'System.img' disk searching for the IPoIB-virt-admin IP address and save these information under '/root/.cnode-vserver-control/vservers-$HOSTNAME.lst'.

If '/root/.cnode-vserver-control/vservers-$HOSTNAME.lst' exists, please backup and delete.

Problematic Computer Node is CN01 or CN02

2.1 Stop control stack vServers.

    Method 1 : Refer part "Stopping the whole Exalogic Control stack" in doc 1594223.1.

    Method 2 : Use ExaBR.

    e.g.

/exalogic-lctools/bin/exabr stop control-stack

2.2 Stop all vServers.

Please refer "3.1 Start all vServers" in this document.

2.3. Power off computer node and perform maintenance tasks.

2.4 Start control stack vServers.

    Method 1 : Refer part "Starting the whole Exalogic Control stack" in doc 1594223.1.

    Method 2 : Use ExaBR.

    e.g.

/exalogic-lctools/bin/exabr start control-stack

2.5 Start all vServers.

Please refer "3.3 Start all vServers" in this document.

Problematic Computer Node is neither CN01 nor CN02

3.1 Stop all vServers.

Stop all Guest vServers by executing:

./cnode-vserver-control.py --force -a stop

Using the '--force' action will stop all vServes including those which enable HA flag.

The default timeout is 180 seconds to begin stopping vServers, you can change timeout by using flag "--stop-timeout"

e.g.

./cnode-vserver-control.py --force -a stop --stop-timeout 90

3.2 Power off computer node and perform maintenance tasks.

3.3 Start all vServers.

Start all Guest vServers by running:

# ./cnode-vserver-control.py -a start

 

Note: There are some other usages per script cnode-vserver-control.py, please refer the following note for details:

Utility for Stopping & Starting Exalogic Guest vServers (cnode-vserver-control.py) (Doc ID 1945615.1)

 

References

<NOTE:1594223.1> - How To Stop and Start the Entire Exalogic Control Stack In An Exalogic EECS v2.0.6.0.0 and later Virtual releases
<NOTE:1945615.1> - Utility for Stopping & Starting Exalogic Guest vServers (cnode-vserver-control.py)

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback