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-71-1464409.1
Update Date:2018-03-17
Keywords:

Solution Type  Technical Instruction Sure

Solution  1464409.1 :   Pillar Axiom: How To Shutdown an Axiom  


Related Items
  • Pillar Axiom 500 Storage System
  •  
  • Pillar Axiom 600 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
  •  




In this Document
Goal
Solution
 Before initiating a Shutdown of the Axiom please verify the following:
 Shutdown the Axiom:
 Power Off the Axiom:
 Power On the Axiom:
 Restart the Axiom (only if the Axiom was NOT powered Off/On):
 Check the Status of the Axiom:
 Check the status of the LUNs/FileSystems:
 Check for System Alerts or Administrator Actions:


Created from <SR 3-5753530181>

Applies to:

Pillar Axiom 500 Storage System - Version All Versions to All Versions [Release All Releases]
Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

 To Shutdown the Axiom in preparation for a maintenance activity.

Solution

When you Shutdown an Axiom it will shut down all of the software running on the system, it does NOT power off the system.

Before initiating a Shutdown of the Axiom please verify the following:

  • The Axiom is in a Normal state, if not please contact Oracle Support.
  • Ensure there are no Background Tasks running.
    • Axiom running on release R5, log into the GUI and click the "Tasks" button to see if there are any background processes running.
    • Axiom running on release R4 (or below), log into the UI in the bottom right corner click the Running man icon to see if any background processes are running.
  • Quiesce all I/O streams to the Axiom. Verify I/O is not being processed on the Axiom.
    • Axiom running on release R5, log into the GUI click "Monitor" tab, from the left menu under "Statistics and Trending" click "LUNs", in the main page verify the "Average IOPS" column for all LUNs shows 0.
    • Axiom running on release R4 (or below), log into the UI click "Health" tab, from the left menu under "Performance" click "LUNs" and make sure IOPs is 0 for every LUN, if filesystems exist then click "FileSystems" and verify IOPs is 0 for every filesystem.

Shutdown the Axiom:

  • Axiom running on release R5, from the top menu click "Axiom" and select "Shut Down", in the next window click "OK" to confirm you want to Shut Down the Axiom. Wait a couple of minutes for the system to complete Shut Down. To verify Shut Down succeeded, in the GUI click "Monitor" tab then click "Event Log", in the main page verify you see a "System shutdown succeeded" event. In the GUI click "Configure" tab, from the left menu click "System" and verify in the main page the "Status:" shows "Shutdown".
  • Axiom running on release R4 (or below), from the top menu click "System" tab, from the left menu click "Shutdown/Restart". In the main page under "<Actions>" click "Shutdown Now". In the next window click "OK" to confirm shutdown. Wait a couple of minutes for the system to complete Shut Down. To verify Shut Down succeeded, in the UI click "Health" tab then click "Event Log", in the main page verify you see a "Shutdown System by <username> succeeded" event. In the bottom left corner you will see an inverted yellow triangle and if you move your mouse over it, it will show the "System Status: Shutdown". If you click on the administrator alert (blinking yellow triangle) will report "System State is Read Only".

    This is the proper indication that the Shut Down was successful.

Power Off the Axiom:

  • We recommend powering off the Axiom using the Rack PDU breakers.
  • If you choose not to use the Rack PDU breakers, you may power off each individual hardware component of the Axiom in the following order:
    1. Power OFF FC Raid Bricks, from the back of each brick switch both power supplies to the OFF position.
    2. Power OFF FC Expansion Bricks, from the back of each brick switch both power supplies to the OFF position.
    3. Power OFF SATA Bricks, from the back of each brick switch both power supplies to the OFF position.
    4. Power OFF the NAS Slammer, by disconnecting the power cables from the back of the slammer
    5. Power OFF the SAN Slammer, by disconnecting the power cables from the back of the slammer
    6. Power OFF both Pilots, by disconnecting the power cable from the back of each Pilot
  • IMPORTANT! If the Slammers are going to be powered OFF for longer than 24 hours please remove the batteries so they don't discharge

Power On the Axiom:

  • Insert the batteries back into the Slammers if they were removed.
  • If you used the Rack PDU breakers to power OFF the Axiom, then use the Rack PDU breakers to power ON the Axiom.
  • If you powered off each individual hardware component of the Axiom, then you will need to power on each individual component in the following order:
    1. Power ON FC Expansion Bricks, from the back of each brick switch both power supplies to the ON position.
    2. Power ON FC Raid Bricks, from the back of each brick switch both power supplies to the ON position.
    3. Power ON SATA Bricks, from the back of each brick switch both power supplies to the ON position.
    4. Power ON both Pilots, connect the power cable from the back of each Pilot.
    5. Power ON the SAN Slammer, connect the power cables from the back of the Slammer
    6. Power ON the NAS Slammer, connect the power cables from the back of the Slammer

Restart the Axiom (only if the Axiom was NOT powered Off/On):

  • Axiom running on release R5, from the top menu click "Axiom" and select "Restart", in the next window click "OK" to confirm that you want to restart the system now.
  • Axiom running on release R4 (or below), from the top menu click "Axiom" and select "Shutdown/Restart", in the main page under "<Actions>" click "Restart Now". In the next window click "OK" to confirm restart.

The Axiom will cold start after you power ON the system or Restart the system in the GUI/UI. Once the pilots are available log into the GUI/UI and wait for the system to complete boot up, this may take 15-20 minutes to complete.

Check the Status of the Axiom:

  • Axiom running on release R5, in the GUI navigate to "Configure" tab -> click "System". In the main page view the "Status:", it should be Normal. In the bottom left corner you should see a green circle.
  • Axiom running on release R4 (or below), in the UI click "System" tab -> from the left menu click "Summary". In the main page it should show "System Status:" Normal. In the bottom left corner should see a green circle.

Check the status of the LUNs/FileSystems:

  • Axiom running on release R5, in the GUI navigate to "Configure" tab -> click "LUNs", in the main page make sure the Status of all LUNs are Online.
  • Axiom running on release R4 (or below), in the UI navigate to "Storage" tab -> click "LUNs", in the main page make sure the Status of all LUNs are Online. If filesystems exist, in the UI click "Storage" tab -> click "FileSystems", in the main page make sure the Status of all filesystems are Online.

Check for System Alerts or Administrator Actions:

  • Axiom running on release R5, in the GUI navigate to "Monitor" tab -> click "System Alerts". In the main page check if any system alerts exist that may need to be resolved.
  • Axiom running on release R4 (or below), in the UI bottom left check if there is a blinking yellow triangle, if not then there are no Administrator Actions. If you do see a blinking yellow triangle click on it to view the Administrator Actions that may need to be resolved.

At this point the system should be ready to be put back into production.


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