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-1569641.1
Update Date:2018-04-20
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1569641.1 :   Controllers in a Sun Storage 6000/2500/2500-M2/Flexline Array Have an 820 Day Uptime Limit  


Related Items
  • Sun Storage Flexline 280 Array
  •  
  • Sun Storage 2510 Array
  •  
  • Sun Storage 2540-M2 Array
  •  
  • Sun Storage 2540 Array
  •  
  • Sun Storage 6780 Array
  •  
  • Sun Storage 6180 Array
  •  
  • Sun Storage 6130 Array
  •  
  • Sun Storage Flexline 380 Array
  •  
  • Sun Storage 2530 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
  • Sun Storage Flexline 240 Array
  •  
  • Sun Storage 6140 Array
  •  
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6580 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
  •  




Applies to:

Sun Storage Flexline 380 Array - Version Not Applicable and later
Sun Storage 6780 Array - Version All Versions and later
Sun Storage 2510 Array - Version Not Applicable and later
Sun Storage 2530 Array - Version Not Applicable and later
Sun Storage 2540-M2 Array - Version Not Applicable and later
Information in this document applies to any platform.

Purpose

This document describes the 820 day uptime limit which affects the controllers within a Sun Storage 6000, 2500, 2500-M2 and Flexline Array.

Details

After 820 days of continuous operation a controller in a Sun Storage 6000, 2500, 2500-M2, Flexline Array will automatically reboot due to an uptime limitation within the controller firmware. This reboot cannot be avoided and affects all firmware versions of the arrays, including both 06.xx and 07.xx firmware releases. This behaviour cannot be changed, so there will never be a fix for this issue. It is a known limitation of the array.

The exact behaviour in relation to the reboots after 820 days differs between 06.xx firmware releases and 07.xx firmware releases :

  • In 6.xx firmware both controllers are scheduled to automatically reboot after approximately 825 days of uptime. If both controllers were previously rebooted at the same time, this will cause an unscheduled simultaneous reboot of both controllers which can impact host i/o. This problem is discussed in the Alert <Document 1128605.1> Firmware for RAID Controllers Causes Unscheduled Simultaneous Reboot of Controllers After 828.5 Days of Continuous Operation.
  • In 7.xx firmware each controller is scheduled to reboot at different times - Controller A will reboot after approximately 820 days of uptime, Controller B will reboot after approximately 825 days of uptime. If both controllers were previously rebooted at the same time then this avoids an unscheduled simultaneous reboot. Provided all the attached data hosts have multipathing configured and in an optimal status then these sequential reboots will not impact host i/o.

To check the uptime of a controller refer to <Document 1455525.1> How to Determine Uptime of Sun Storage[TM] 2500, 2500-M2 and 6000 Disk Arrays.

Note : If a controller is manually rebooted before it's uptime limit is reached then this will reset the uptime counter back to zero and defer the automatic reboot for another 820 days

References

<NOTE:1128605.1> - Firmware for RAID Controllers Causes Unscheduled Simultaneous Reboot of Controllers After 828.5 Days of Continuous Operation
<NOTE:1455525.1> - How to Determine Uptime of Sun Storage[TM] 2500, 2500-M2 and 6000 Disk Arrays

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