![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 2357960.1 : FS System: Compatibility Matrix for Alternate Drive Replacements in Flash Storage Systems
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:Oracle FS1-2 Flash Storage SystemInformation in this document applies to any platform. PurposeTo provide proper guidance to support people for the replacement of drives based on their availability in the FS1-2 system. ScopeDrive availability can depend on many factors. Is the drive still being manufactured? Is there a known problem with the drive? Are there any local restrictions on what drive can be used? This document details the strategies used to provide the best chance for Oracle to have a valid replacement drive where ever it is needed. At this time, this document only covers 1.6TB SSDs and 8TB HDDs in the FS1-2 system. Additional information about drive firmware levels, drive model types and FS1-2 software versions can be found in KM Document 2095090.1 FS System: Drive Firmware Matrix for the FS1-2. Details1.6TB SSDs:For the FS1-2 system, Oracle currently stocks 1.6TB SSDs from two different vendors, SanDisk and Hitachi. Early on in the FS1-2 product's life a problem was discovered with the SanDisk versions that caused latency issues in Clustered environments (see Bug 20275961 for additional details). This necessitated using the Hitachi version as a replacement until a firmware fix from SanDisk was qualified. Now Hitachi has stopped manufacturing the 1.6TB SSD used in the FS1-2. Both of these decisions have resulted in a surplus of the SanDisk 1.6TB SSDs in stock as well as quantities of the Hitachi 1.6TB SSDs being depleted much faster than expected. The SanDisk issue was resolved with firmware version S318 which is found in R6.2.9 and above. This means that the SanDisk 1.6TB SSDs are once again a viable replacement for systems running R6.2.9 and above. In addition, Hitachi's replacement for its 1.6TB SSD is a 3.2TB SSD which is supported in R6.2.14 and above. In order to provide maximum utilization of the available parts, care must be taken when ordering 1.6TB SSDs so that we use the SanDisks we currently have in abundance and manage the depletion of the Hitachi 1.6TB drives. Since these actions are tied to the version of software running on the FS1-2 system, please consult the table below when ordering a replacement for a failed 1.6TB SSD 8TB HDDs:As is the case with some of the Hitachi 1.6TB SSDs above, they no longer manufacture the 8TB models used in the FS1-2. This makes the current stock limited and in need of proper management so as to maximize their availability. As such, for any FS1-2 running R6.2.14 and above, 8TB failures will be sent a 10TB HDD drive as a replacement. Customers running below R6.2.14 should be sent an 8TB HDD and asked to upgrade to the latest version as soon as possible in order to ensure timely replacements in the future.
1 Common Kit that includes both Evo 2.5 and Marlin brackets. Logistics may choose the Common Kit to replace the same drive model in different assembly. 2 If necessary, logistics may use FIPS (Federal Information Processing Standard) 1.6TB to replace non-FIPS 1.6TB. 3 EurAsian Economic Union (EAEU) rated drives should only be used in EAEU countries. For details on restrictions for EAEU countries, see KM Documents 2309387.1 Special Part for EAEU Countries (Armenia, Belarus, Kazakhstan, Kyrgyzstan and Russia) and 2334880.1 FS System: Firmware Update for Systems Installed in EAEU Countries. 4 For encryption purposes, the alternate part for a FIPS drive is a TCG (Trusted Computing Group) drive. It is understood that there may be rare instances that are outside of these parameters. These will depend on what spares are immediately available and/or the version of software running on the FS1-2. If these are encountered, please engage your GEO Technical Leads for assistance.
Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|