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-1570044.1
Update Date:2016-07-28
Keywords:
Solution Type  Technical Instruction Sure

Solution  1570044.1 :   Pillar Axiom: How to handle a Volume Status Changed (R5)  

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


 Purpose


 Scope


 Details




Applies to:  

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



Goal


How to recover from  Volume Status Changed events (CM_EVT_VOLUME_STATUS_CHANGED)


Solution


Purpose


There are many causes for Volume Status Changed events.  This document was written to explain some of those that are more common.


If you still have questions after reading this article,  go to the  My Oracle Support Community - Pillar Axiom Storage System


 


Scope


When these events are sent, a specific volume of volumes are identified as the cause.  Below is a list of common examples  that will cause these events.


 


Details


    

  1. Conservative Mode (the disabling of Write Cache) has changed because:
    

      

    1. Brick Critical message has caused the Volume to change ConservativeMode to TRUE (Write Cache disabled).
      2. 

    2. Brick Normal message has caused the Volume to return to ConsevativeMode to FALSE (Write Cache re-enabled).
      3. 

    3. The Block Services Slammer software component:
      4. 

        

      1. Has failed.
        2. 

      2. Has recovered.
        3. 

      3. Has lost battery backed memory.
        4. 

      4. Has regained battery backed memory.
        5. 

      5. The Block Services Buddy has gone critical or returned to normal.

        6. 

      

    

    2. 

  2. Online status has changed - the Volume is no longer online.

    3. 

  3. Redundancy status has change - the Volume has lost a drive and may no longer have enough redundancy to rebuild if another drive fails.

    4. 

  4. Write cache mirror is inconsistent - cache copies do not match between Control Units.

    5. 

  5. A SnapLUN is offline:
    

      

    1. It may have ran out of space.
      2. 

    2. It may be offline due to lost sync.
      3. 

    

    6. 



    There should be an Administrator Alert that allows the an account with administrator privileges to delete it.


Check the following:


    

  1. Is there a recent or current environmental issue that may have triggered this event?
    2. 

  2. Was there any power removed?
    3. 

  3. Were you performing maintenance which could have generated this event?
    4. 



If none of these conditions exist, or you still have questions about this event, please open a Service Request in My Oracle Support.



Attachments

This solution has no attachment


















       

Copyright © 2018 Oracle, Inc.  All rights reserved.

 Feedback