Sun Flash Accelerator F20 PCIe Card User’s Guide · 2 Sun Flash Accelerator F20 PCIe Card User’s Guide • April 2014 The system treats each FMod as a separate storage volume

Sun Flash Accelerator F20 PCIe Card

User’s Guide

Part No.: E21358-04April 2014

Copyright © 2010, 2014, Oracle and/or its affiliates. All rights reserved.This hardware, software and related documentation are provided under a license agreement containing restrictions on use and disclosure and areprotected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce,translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to usin writing.If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, thefollowing notice is applicable:U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are"commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in anyinherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon aretrademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks ofSPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd.This software or hardware and documentation may provide access to or information on content, products, and services from third parties. OracleCorporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-partycontent, products, or services.

Copyright © 2010, 2014, Oracle et/ou ses affiliés. Tous droits réservés.Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à desrestrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire,diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et parquelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté àdes fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’ellessoient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence dece logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique :U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pasconçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vousutilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, desauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliésdéclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom mentionné peut correspondre à des marquesappartenant à d’autres propriétaires qu’Oracle.AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. Intel et Intel Xeon sont desmarques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marquesdéposées de SPARC International, Inc. UNIX est une marque déposée concédée sous licence par X/Open Company, Ltd.Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits etdes services émanant de tiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ouservices émanant de tiers. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûtsoccasionnés ou des dommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation.

PleaseRecycle

Contents

Preface vii

Preparing for Installation 1

Understanding Card Features 1

Flash Module Architecture Overview 1

Energy Storage Module Overview 2

Required ESM Replacement 3

Ship Kit Contents 4

Required Tools 5

Observing Safety Precautions 5

General Safety Information 6

Safety Symbols 6

ESD Safety Measures 6

Antistatic Wrist Strap 7

Antistatic Mat 7

▼ Perform ESD Prevention Measures 7

▼ Update the Host System 8

Installing the Card 9

Installing the Hardware 9

▼ Verify Available PCIe Slot 10

▼ (Optional) Install Full-Height Bracket 10

▼ Install the Card Into a System 11

iii

Card LED Locations 12

FMod Alignment for Optimal Performance 13

(Optional) Using the SAS/SATA Controller as a Boot Device 14

SAS/SATA Controller as a Boot Device 15

▼ Configure the SAS/SATA Controller as a Boot Device (SPARCSystems) 15

▼ Configure the SAS/SATA Controller as a Boot Device (x86 Systems)15

▼ Remove the Card From a System 16

Servicing the Card 17

Servicing FMods 17

▼ Locate an FMod Using Software 17

FMod Physical Locations 18

▼ Remove an FMod 19

▼ Install an FMod 21

▼ Replacing FMod Retention Clips 22

Servicing the ESM 23

Monitoring ESP Lifespan 23

Monitoring ESM Lifespan Options 23

Sun Flash Accelerator F20 ESM Monitoring Utility 24

Oracle ILOM ESM Monitoring for SPARC T-Series Servers 25

Oracle ILOM ESM Monitoring for x86 X Series Servers 26

XSCF ESM Monitoring for SPARC M Series Servers 28

Removing the ESM 30

▼ Remove the ESM 30

▼ Remove the ESM (Alternate Configuration) 32

Installing the ESM 33

▼ Install the ESM 34

▼ Install the ESM (Alternate Configuration) 35

iv Sun Flash Accelerator F20 PCIe Card User’s Guide • April 2014

Updating the FMod Firmware 37

▼ Update the FMod Firmware (Oracle Solaris OS) 37

▼ Update the FMod Firmware (Windows and Linux OS) 39

Updating the SAS/SATA Controller Firmware 40

▼ Update the SAS/SATA Controller Firmware (Oracle Solaris OS) 40

▼ Update the SAS/SATA Controller Firmware (Linux OS) 43

▼ Update the SAS/SATA Controller Firmware (Windows) 43

▼ Replace the Card 44

Troubleshooting the Card 45

Troubleshooting Chart 45

Card LEDs 46

Understanding Specifications 49

Physical Dimensions 49

Environmental Specifications 49

Electrical Specifications 50

Connector Pinouts 50

Glossary 53

Contents v

vi Sun Flash Accelerator F20 PCIe Card User’s Guide • April 2014

Preface

This user’s guide provides detailed procedures that describe installing andconfiguring Oracle’s Sun Flash Accelerator F20 PCIe card. This guide also includesinformation about the installation and maintenance of the card. This document iswritten for technicians, system administrators, authorized service providers (ASPs),and users who have advanced experience troubleshooting and replacing hardware.

Note – For specific installation instructions, see your system installation guide. Forinformation about restrictions and use of the Sun Flash Accelerator F20 PCIe card onyour server, see the most recent version of the server product notes.

This preface contains the following topics:

■ “Product Notes” on page vii

■ “Related Documentation” on page viii

■ “Feedback” on page viii

■ “Access to Oracle Support” on page viii

Product NotesFor late-breaking information and known issues about this product, refer to theproduct notes at:

http://docs.oracle.com/cd/E19682-01/index.html

vii


Related Documentation

FeedbackProvide feedback about this documentation at:

http://www.oracle.com/goto/docfeedback

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. Forinformation visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.

Documentation Links

Sun FlashAccelerator F20PCIe Card


viii Sun Flash Accelerator F20 PCIe Card User’s Guide • April 2014

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs


http://www.oracle.com/goto/docfeedback

Preparing for Installation

The following topics describe information you need before installing or servicing theSun Flash Accelerator F20 PCIe card.

Note – For specific installation instructions, see your system installation guide. Forinformation about installation and use of the card on your server, see the most recentversion of the server product notes.

■ “Understanding Card Features” on page 1

■ “Ship Kit Contents” on page 4

■ “Required Tools” on page 5

■ “Observing Safety Precautions” on page 5

■ “Update the Host System” on page 8

Understanding Card FeaturesThe following topics provide an overview of the card features.

■ “Flash Module Architecture Overview” on page 1

■ “Energy Storage Module Overview” on page 2

■ “Required ESM Replacement” on page 3

Flash Module Architecture OverviewThe solid-state flash module (FMod) architecture enables much faster throughputcompared to conventional disk-based drive technology. Four FMods are installed onone Sun Flash Accelerator F20 PCIe card.

1

The system treats each FMod as a separate storage volume. FMods are managedusing the same tools as those for conventional (platter-based) hard drives. When youinstall the card, or add or replace FMods on the card, you must format each newFMod before you can read or write data to it. If you move the card or individualFMods to a different server using a different operating system or file system, youmust reformat the FMods to work with the new file system.

Additionally, solid state flash devices have block alignments typically aligned on4-Kbyte boundaries, not the 512-byte boundaries of conventional disks. In order tomaximize performance, partitions need to be aligned on 4-Kbyte boundaries. Formore information, see “FMod Alignment for Optimal Performance” on page 13.

Note – Like any other storage media, if you reformat the FMods on the card, anypreexisting data on the FMods is destroyed during the formatting process.

Related Information


■ “Servicing the Card” on page 17

Energy Storage Module OverviewThe Sun Flash Accelerator F20 PCIe card includes an energy storage module (ESM) toensure data integrity during a power interruption, functioning similar to a batterybackup.

Data indexing and data chache are periodically stored on volatile memory on eachFMod. The data cache is necessary to achive the performance expected of the FMods.In the event of a power interruption, existing data in volatile storage must be writtento flash memory before total power loss occurs. When properly charged and inservice, the ESM provides enough electrical power to enable data to be written tolocal flash memory during a sudden power loss. The ESM is essential for protectingthe FMods from damage and for ensuring data integrity.

Note – If the ESM is offline or charging, the FMods function in write-through mode(writing all data directly to flash memory), resulting in significantly reduced writeperformance. If you see a significant decrease in write performance, make sure theESM is functioning properly.

2 Sun Flash Accelerator F20 PCIe Card User’s Guide • April 2014

Caution – Long-term ESM durability is affected by excessive heat. As with all datacenter equipment, maintaining efficient system and component cooling is critical. Formore specific site planning guidelines and best practices, refer to your server siteplanning guide and product notes.

Related Information

■ “Required ESM Replacement” on page 3


■ “Monitoring ESP Lifespan” on page 23

■ “Servicing the ESM” on page 23

Required ESM ReplacementBased on the expected life of the ESM in supported hosts, and to maintain optimalcard performance, plan to replace the ESM according to the table below.

To help you monitor the age of the ESM, Sun provides two options for monitoringthe ESM, see “Monitoring ESP Lifespan” on page 23. To service the ESM (F371-4650),see “Servicing the ESM” on page 23.

If the charge capacity in the ESM falls below the minimum threshold, then Oraclewill replace the failed ESM module at no extra charge, if the system is covered eitherby the Oracle Premier Support for Systems or occurs during the warranty period.

Caution – If the ESM is not replaced at the recommended service interval, the levelof stored energy will continue to degrade over time. Any data stored on the card is atrisk of being lost if there is not enough stored energy to complete a write operationduring a power failure. To avoid this risk, replace the ESM at the recommendedservice interval.

Host System Expected ESM Life

Exadata V2 3 years

Exadata X2-2, X2-8 4 years

All other supported servers 3 years


Note – The long-term durability of the ESM is affected by excessive heat. Refer toyour server product notes to understand any slot or thermal restrictions that apply toyour server.

Product documentation is available at:

http://www.oracle.com/documentation

Related Information




Ship Kit ContentsThe ship kit contains the following components:

■ Sun Flash Accelerator F20 PCIe card

■ Full-height PCIe bracket

■ Antistatic wrist strap

■ Sun Flash Accelerator F20 PCIe Card Getting Started Guide (not pictured)




Required ToolsYou need the following tools to install or service the card:

■ Antistatic wrist strap

■ Antistatic mat

■ No. 1 Phillips screwdriver

Observing Safety PrecautionsThis section contains information about safeguarding the equipment and personnelfrom damage.


■ “General Safety Information” on page 6

■ “Safety Symbols” on page 6

■ “ESD Safety Measures” on page 6

■ “Perform ESD Prevention Measures” on page 7

General Safety InformationFor your protection, observe the following safety precautions when setting up yourequipment:

■ Follow all cautions and instructions marked on the equipment and described inthe your server’s safety information.

■ Follow the electrostatic discharge safety practices as described in this section.

Safety SymbolsNote the meanings of the following symbols that might appear in this document:

Caution – There is a risk of personal injury or equipment damage. To avoidpersonal injury and equipment damage, follow the instructions.

Caution – Hot surface. Avoid contact. Surfaces are hot and might cause personalinjury if touched.

Caution – Hazardous voltages are present. To reduce the risk of electric shock anddanger to personal health, follow the instructions.

ESD Safety MeasuresElectrostatic discharge sensitive devices, such as the motherboard, PCI cards, harddrives, and memory modules require special handling.


Caution – Circuit boards and hard drives contain electronic components that areextremely sensitive to static electricity. Ordinary amounts of static electricity fromclothing or the work environment can destroy the components located on theseboards. Do not touch the components along their connector edges.

Caution – You must disconnect all system power supplies before servicing any ofthe components documented in this chapter.

Antistatic Wrist StrapWear an antistatic wrist strap (provided) when handling ESD-sensitive components.

Antistatic MatPlace ESD-sensitive components such as motherboards, memory, and other PCBs onan antistatic mat (not provided).

Related Information

■ “Perform ESD Prevention Measures” on page 7

▼ Perform ESD Prevention Measures1. Prepare an antistatic surface to set parts on during the removal, installation, or

replacement process.

Place ESD-sensitive components such as the printed circuit boards on an antistaticmat. The following items can be used as an antistatic mat:

■ Antistatic bag used to wrap a replacement part

■ ESD mat

■ A disposable ESD mat (shipped with some replacement parts or optionalsystem components)

2. Attach an antistatic wrist strap.

When servicing or removing server components, attach an antistatic strap to yourwrist and then to a metal area on the chassis.


Related Information■ “ESD Safety Measures” on page 6

▼ Update the Host SystemCheck the Sun Flash Accelerator F20 PCIe Card Product Notes for the latest firmwarerequirements, available at: http://oracle.com/pls/topic/lookup?ctx=E19682-01&id=homepage.

● Download and install any firmware updates required to support the HBA, drivebackplane, system BIOS, or OBP/system firmware for your system from thislocation:

https://support.oracle.com/CSP/ui/flash.html

Note: You will be asked to update card firmware later.


http://oracle.com/pls/topic/lookup?ctx=E19682-01&id=homepage


http://sunsolve.sun.com




Installing the Card

The following section contains information about installing the card into a system.

■ “Installing the Hardware” on page 9

■ “(Optional) Using the SAS/SATA Controller as a Boot Device” on page 14

■ “Remove the Card From a System” on page 16

Installing the HardwareFollow these steps to install the card into a system.

Step Description Links

1. Verify that your system supports theSun Flash Accelerator F20 PCIe card,and has an appropriate PCIe slotavailable.

“Verify Available PCIe Slot” on page 10

2. (Optional) Install a full-height bracket(only for systems with full-height PCIeslots).

“(Optional) Install Full-Height Bracket”on page 10

3. Install the card into a server. “Install the Card Into a System” onpage 11

4. Format the FMods for optimalperformance.

“FMod Alignment for OptimalPerformance” on page 13

5. Remove the card for servicing orupgrading.

“Remove the Card From a System” onpage 16

9

▼ Verify Available PCIe Slot● Verify that your system supports the Sun Flash Accelerator F20 PCIe card, and

has an appropriate PCIe slot available.

See the Sun Flash Accelerator PCIe Card Product Notes and your system productnotes for support information and any restrictions that might apply to yoursystem. Install the card in a slot with maximum cooling.

Caution – Ensure the system and the Sun Flash Accelerator F20 PCIe card areproperly cooled. Do not mix the Sun Flash Accelerator F20 PCIe card and other PCIedevices before verifying that such configurations are supported by your system.

Related Information■ “(Optional) Install Full-Height Bracket” on page 10

■ “Install the Card Into a System” on page 11

▼ (Optional) Install Full-Height BracketSome systems accept only full-height PCIe cards. These instructions describe how toinstall the full-height PCIe bracket onto the card.

1. Perform ESD prevention measures.

See “Perform ESD Prevention Measures” on page 7.

2. Remove both FMods near the back panel bracket.

Note – Note the FMod locations. Each FMod must be installed in the same slot fromwhich it was removed.

See “Remove an FMod” on page 19.

3. Remove the half-height bracket from the card.

Remove the two Phillips No. 1 screws that secure the bracket to the card.

4. Attach the full-height bracket to the card.

Secure the bracket with two Phillips No. 1 screws.


5. Install the FMods you removed in Step 2.

Note – Note the FMod locations. Each FMod must be installed in the same slot fromwhich it was removed.

See “Install an FMod” on page 21.

Related Information■ “Install an FMod” on page 21

■ “Remove an FMod” on page 19

■ “Install the Card Into a System” on page 11

▼ Install the Card Into a System1. For system-specific PCIe card installation instructions, see your system service

manual and product notes.


Note – The ESM takes approximately five minutes to charge during system startup.For more information see “Energy Storage Module Overview” on page 2.

2. If applicable, perform any required commands for your system to recognize thenew card.

For the Oracle Solaris OS, use the reboot command with the reconfigurationoption.

3. Verify successful installation of the card through your systems’s OS and thecard LEDs.

Upon completed installation, the four FMods on the card will appear to yoursystem as four discrete SSDs.

Verify the card is properly installed by checking the card LED status; power LED= on, ESM ok = on, ESM fault = off.

4. Download and install the latest firmware for the card.

See the Sun Flash Accelerator PCIe Card Product Notes for minimum requiredfirmware versions.

5. Configure the system to maximize flash technology.

Solid state flash devices have block alignments typically aligned on 4-Kbyteboundaries, not the 512-byte boundaries of conventional disks. In order tomaximize performance, partitions need to be aligned on 4-Kbyte boundaries. Foran example of the alignment procedure, see, “FMod Alignment for OptimalPerformance” on page 13.

Related Information■ “FMod Alignment for Optimal Performance” on page 13

■ “(Optional) Install Full-Height Bracket” on page 10

Card LED Locations


Related Information

■ “Card LEDs” on page 46

FMod Alignment for Optimal PerformanceTo obtain optimal performance, all partitions must be aligned to start on 4K-alignedboundaries. Actions required to ensure proper alignment vary based on yourenvironment.

In SPARC environments with an SMI label, no verification is required. In SPARCenvironments with an EFI label, it is sufficient to verify that partition boundariesstart on 4K-aligned boundaries by using the format command. In x86 environmentsthere are multiple tools to create partitions, it is important to understand the toolused to ensure the partition starts at a 4K-aligned value.

The following Oracle Solaris x86 example uses the format command to inspect andalter partition tables.

Along with verifying partition boundaries, in x86 environments, you must alsoensure that the disk partition1 starts at a 4K-aligned value. If the entire disk isspecified for use by the Oracle Solaris OS, the disk partition starts at cylinder 1 bydefault. This can be determined by using the fdisk command as follows:

EXAMPLE: Determine Whether a Partition Starts at a 4K-Aligned Value

A cylinder is 16065 blocks:(16065 blocks/cylinder * 512 bytes/block)/4096 = 2008.125 bytesThis is not a 4K-aligned value.

The next 4K-aligned value in this case would be cylinder 8: (8 cylinder * (16065blocks/cylinder * 512 bytes/block) / 4096 = 16065

This value is a 4K-aligned value (evenly divisible by 8).

1. References to disk partitions in this context refer to the partitions on the Sun Flash Accelerator F20 PCIeFMods.

# fdisk /dev/rdsk/c0t13d0p0Total disk size is 2987 cylindersCylinder size is 16065 (512 byte) blocks

CylindersPartition Status Type Start End Length %====== ====== ====== ===== === ====== ===

1 Solaris2 1 2986 2986 100


Note – When a disk is added to the zpool, ZFS creates partitions that start oncylinder 0 by default, which results in 4K alignment. No tuning is needed if you useZFS.

Ensure that individual partitions are created on 4K-aligned boundaries. To do this,use the format command to inspect and alter partition boundaries. 4K-alignedboundaries must be setup in both format and in fdisk.

When you are finished, the partition should look similar to the following example.

EXAMPLE: Verify That a Partition Starts at a 4K-Aligned Value

Once the fdisk partition is aligned, no further adjustments are needed.

(Optional) Using the SAS/SATAController as a Boot DeviceThis section contains information about configuring the card’s onboard controller asa boot device.

■ “SAS/SATA Controller as a Boot Device” on page 15

■ “Configure the SAS/SATA Controller as a Boot Device (SPARC Systems)” onpage 15

■ “Configure the SAS/SATA Controller as a Boot Device (x86 Systems)” on page 15

Related Information

■ “Updating the SAS/SATA Controller Firmware” on page 40

# fdisk /dev/rdsk/c0t13d0p0Total disk size is 2987 cylindersCylinder size is 16065 (512 byte) blocks

CylindersPartition Status Type Start End Length %====== ====== ====== ===== === ====== ===

1 Active Solaris2 8 2986 2979 100


SAS/SATA Controller as a Boot DeviceBy default, the Sun Flash Accelerator F20 PCIe card is configured as a nonbootabledevice.

On SPARC-based systems, you can configure and manage devices attached to theSun Flash Accelerator F20 PCIe card—including

FMods—using conventional Oracle Solaris tools and utilities. In addition, you canuse conventional Oracle Solaris tools and utilities to configure an FMod as a bootdevice. No additional firmware configuration is necessary.

On x86-based systems, you must use the SAS configuration utility to configure theSun Flash Accelerator F20 PCIe card for use as a boot device. Some systems mightrequire additional configuration steps. Consult the product notes for your server forspecific configuration instructions.

▼ Configure the SAS/SATA Controller as a BootDevice (SPARC Systems)● On SPARC systems, you can use conventional Oracle Solaris-based tools to

configure the SAS/SATA controller as a boot device.

See your Oracle Solaris documentation for more information.

▼ Configure the SAS/SATA Controller as a BootDevice (x86 Systems)Use this procedure to configure the SAS/SATA controller as a boot device on x86systems.

Note – In some cases, it might be necessary to edit system BIOS settings to recognizethe Sun Flash Accelerator F20 PCIe SAS/SATA controller. Check your systemdocumentation for more information.

1. Power on the system using a system console or Oracle ILOM command.

2. Watch for the following console message during the boot process:

LSI Corporation MPT SAS BIOSMPTBIOS-6.26.00.00 (2008.10.14)Copyright 2000-2008 LSI Corporation


3. Press control+C to interrupt the boot process and start the SAS configurationutility.

4. Follow the onscreen instructions to do the following:

■ Alter boot order to 0

■ Change the boot support to Enabled BIOS & OS

5. Navigate to Advanced Device Properties, and set the Maximum INT Devices forthis Adapter to 4, to use one of the card FMods as a boot device.

The card FMods will now appear in the BIOS boot list.

6. Return to the BIOS boot list to configure the system boot order.

▼ Remove the Card From a System● For specific PCIe card removal instructions, see your system service manual and

product notes.

Please wait, invoking SAS Configuration Utility.


Servicing the Card

This section contains service information for the card.

■ “Servicing FMods” on page 17


■ “Updating the FMod Firmware” on page 37


■ “Replace the Card” on page 44


■ “Troubleshooting Chart” on page 45

Servicing FModsThese topics explain how to locate and service FMods.

■ “Locate an FMod Using Software” on page 17


■ “Install an FMod” on page 21

■ “Replacing FMod Retention Clips” on page 22

■ “FMod Physical Locations” on page 18

▼ Locate an FMod Using SoftwareThis procedure describes locating an FMod from your OS. To physically locate anFMod on the card, use the labels. See “FMod Physical Locations” on page 18.

● Locate an FMod as you would locate any hard disk drive (HDD) from your OS.

■ For Oracle Solaris use the format, firmwareflash, dmesg, raidctl, ora similar command to locate the FMod.

17

For example, type:

In this example, the FMods are located at controller 2, with target numbers 0 -3. FMods are always targets 0 - 3, which corresponds with the labeling on thecard.

■ For Linux, you must have root access, and depending on your Linuxdistribution you might need the sg3_utils package installed.

Use the fdisk, parted, dmesg, lsscsi, lspci or similar command tolocate the FMod.

■ For Windows, use the Device Manager or Disk Manager to locate FMods.

Related Information■ “Remove an FMod” on page 19

■ “Install an FMod” on page 21


FMod Physical LocationsLocate FMods using the label on the card.

# formatSearching for disks...done

AVAILABLE DISK SELECTIONS:0. c2t0d0 <DEFAULT cyl 2985 alt 2 hd 255 sec 63>

pci@7c,0/pci10de,378@b/pci1000,1000@0/sd@0,01. c2t1d0 <DEFAULT cyl 2985 alt 2 hd 255 sec 63>



pci@7c,0/pci10de,378@b/pci1000,1000@0/sd@3,0Specify disk (enter its number):


Related Information



▼ Remove an FMod1. Perform ESD prevention measures.


2. Remove the card from the system.

If you are servicing the lower FMod, you must first remove the upper FMod.

a. Note the location of each FMod on the card.

You must replace FMods in the same locations to retain consistent deviceaddresses after servicing the card.

b. Slightly loosen the retention clip screws before attempting to remove theFMod.

Loosen the clip screws 1-2 turns to prevent breaking the clips.


c. Gently disengage the retention levers from the FMod.

d. Pull the FMod straight up and off the card.

The FMod near the faceplate is held in place by a groove on the back of thefaceplace. Remove this FMod at an angle to free it from the metal groove.

3. Place the FMod on an antistatic mat.

Related Information■ “Flash Module Architecture Overview” on page 1




▼ Install an FMod

Note – You must replace each FMod in the same location on the card to retainconsistent device addresses.



2. Press the FMod connector into the corresponding connector on the card.

Note – If you replaced FMod 1, note that the ESM cable lays between FMod 1 andFMod 0.

3. Replace the upper FMod.


4. Tighten the FMod retention clip screws to secure the new FMod.

5. Install the card into the system.

For instructions, see the service manual and the product notes for your system.

6. Power up the system and verify successful installation of the card through yoursystem’s OS.

The successfully installed FMods will appear to your system as discrete SSDs.

For example, using the Oracle Solaris OS format command:

7. Update the FMod firmware.

See “Updating the FMod Firmware” on page 37.




▼ Replacing FMod Retention ClipsIn the event one or more FMod retention clips break, you can order replacement clips(Oracle Part Number 555-1970) from:https://shop.oracle.com/pls/ostore/f?p=dstore:home:0.

1. Remove any FMods required to replace the broken clip.


2. Completely remove the broken retention clip screw and clip from the board.

3. Install the new retention clip, but do not tighten the retention clip screw.

Leave the retention clip loose to ease installation of the FMod.

# formatAVAILABLE DISK SELECTIONS: 0. c2t0d0 <DEFAULT cyl 2985 alt 2 hd 255 sec 63>

/pci@7c,0/pci10de,378@b/pci1000,1000@0/sd@0,0 1. c2t1d0 <DEFAULT cyl 2985 alt 2 hd 255 sec 63>



/pci@7c,0/pci10de,378@b/pci1000,1000@0/sd@3,0


https://shop.oracle.com/pls/ostore/f?p=dstore:home:0

4. Install the FMod.


Related Information■ “Install an FMod” on page 21


Servicing the ESMThese topics explain how to service the ESM and configure ESM lifespan monitoringutility.


■ “Remove the ESM” on page 30

■ “Install the ESM” on page 34

Monitoring ESP Lifespan■ “Monitoring ESM Lifespan Options” on page 23

■ “Sun Flash Accelerator F20 ESM Monitoring Utility” on page 24

■ “Oracle ILOM ESM Monitoring for SPARC T-Series Servers” on page 25

■ “Oracle ILOM ESM Monitoring for x86 X Series Servers” on page 26

■ “XSCF ESM Monitoring for SPARC M Series Servers” on page 28

Monitoring ESM Lifespan OptionsBecause the onboard ESM has a limited lifespan, Oracle provides two differentmethods that monitor how long an ESM has been installed, and notifies you when toreplace the ESM.

One option is the Sun Flash Accelerator F20 ESM Monitoring Utility, a simple scriptthat you install on your host server to track the life of the ESM. You must use thismonitoring option for F20 cards with part numbers 511-1500-01 and 511-1275-03.


The second option uses Oracle ILOM (or XSCF for M-series servers) to monitor theF20 card. Oracle ILOM will track the ESM lifespan and notify you when to replacethe ESM. You must use this monitoring option for F20 cards with part numbers511-1500-05 or greater, and with Oracle ILOM system firmware version 7.2.7.d orgreater.

Note – M Series servers only support cards with part numbers 511-1500-xx.

Related Information

■ “Sun Flash Accelerator F20 ESM Monitoring Utility” on page 24

■ “Oracle ILOM ESM Monitoring for SPARC T-Series Servers” on page 25

■ “Oracle ILOM ESM Monitoring for x86 X Series Servers” on page 26

■ “XSCF ESM Monitoring for SPARC M Series Servers” on page 28

Sun Flash Accelerator F20 ESM Monitoring UtilityThe Sun Flash Accelerator F20 ESM Monitoring Utility is a simple tool that youinstall on your host server to track the life of the ESM. Once installed, the ESMMonitoring Utility runs weekly to track the age of your ESM. The utility sendsmessages to the console and the /var/adm/messages file as the ESM approaches orexceeds the replacement interval. Optionally, you can use an external monitoring toolto configure an SNMP trap that sends an email alert when these messages appear.

The utility can be run manually anytime to display the current ESM replacement dataon all installed cards.

Note – Installation of this utility is required on cards with part number 511-1500-01and 511-1275-03 or less to maintain optimal performance for the life of the card. Thisoption will not work on cards with part numbers 511-1500-02 and 511-1275-04 orhigher.

Download the ESM Monitoring Utility.

1. Go to http://cs.sun.com/download/index.jsp?cat=OperatingSystems&tab=3.

2. Locate the “Sun Flash Accelerator F20 ESM Monitoring Utility for Oracle Solaris1.0”.

3. Log in (if required) to download the file.

To install the utility, follow the directions in the README file.


http://cs.sun.com/download/index.jsp?cat=Operating Systems&tab=3

http://cs.sun.com/download/index.jsp?cat=Operating Systems&tab=3

If you have multiple Sun Flash Accelerator F20 PCIe cards of the same age installed,consider replacing the ESMs at the same time to minimize system downtime. Servicethe ESM (F371-4650) as described in the Sun Flash Accelerator F20 PCIe User’s Guide(820-7265).

Related Information

■ “Monitoring ESM Lifespan Options” on page 23

Oracle ILOM ESM Monitoring for SPARC T-Series ServersFor later-generation F20 cards (part number 511-1500-02 and 511-1275-04 or greater),ESM lifespan is automatically monitored by the Oracle ILOM system managementfirmware installed on your host. (ESM monitoring requires the minimum OracleILOM firmware version, see the supported firmware versions in the Sun FlashAccelerator F20 PCIe Product Notes.)

Oracle ILOM monitors ESMs by recording the Total_Time_On for each installed F20card, and then issues warning messages (to the event log and to the host OracleSolaris syslog) as an ESM approaches the end of its lifespan.

For example, one week before an ESM reaches its threshold, Oracle ILOM issues thiswarning message:

When an ESM reaches its threshold, Oracle ILOM issues this critical event message:

Note – You can configure Oracle ILOM to send these alerts by email or SNMP trap.See your Oracle ILOM documentation for more information.

Service the ESM (F371-4650) as described in the Sun Flash Accelerator F20 PCIe User’sGuide (820-7265).

"/SYS/MB/RISER1/PCI4/F20CARD ESM is approaching its lifespan. Pleaseschedule a replacement as soon as possible."

"/SYS/MB/RISER1/PCI4/F20CARD ESM has exceeded its lifespan. Pleaseschedule a replacement as soon as possible."


Once you have replaced your ESM, use the following commands to remove the faultwarnings; this also resets the F20 card Total_Time_On counter to 0.

Use the following commands to locate the path to your card. Find the path in a linestarting with “FRU”, similar to the example below.

Related Information


Oracle ILOM ESM Monitoring for x86 X Series ServersFor later-generation F20 cards (part number 511-1500-02 and 511-1275-04 or greater),ESM lifespan is automatically monitored by the Oracle ILOM system managementfirmware installed on your host. (ESM monitoring requires the minimum OracleILOM firmware version, see the supported firmware versions in the Sun FlashAccelerator F20 PCIe Product Notes.)

Oracle ILOM monitors ESMs by recording the system UPTIME for each installed F20card, and then issues warning messages (to the event log and to the host OracleSolaris syslog) as an ESM approaches the end of its year lifespan.

For example, one week before an ESM reaches its threshold, Oracle ILOM issues thiswarning message:

-> cd /SYS/MB/RISER0/PCIE3/F20CARD

-> set clear_fault_action=true

-> start /SP/faultmgmt/shellAre you sure you want to start /SP/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm faulty

...FRU : /SYS/MB/RISER0/PCIE3/F20CARD...

"/SYS/MB/RISER1/PCI4/F20CARD ESM is approaching its lifespan. Pleaseschedule a replacement as soon as possible."


When an ESM reaches its threshold, Oracle ILOM issues this critical event message:

Note – You can configure Oracle ILOM to send these alerts by email or SNMP trap.See your Oracle ILOM documentation for more information.

Service the ESM (F371-4650) as described in the Sun Flash Accelerator F20 PCIe User’sGuide (820-7265).

Once you have replaced your ESM, use the following Oracle ILOM commands toremove the fault warnings and reset the F20 card UPTIME value to 0. For example:

Note – The path for the F20 card will vary based on the host server.

"/SYS/MB/RISER1/PCI4/F20CARD ESM has exceeded its lifespan. Pleaseschedule a replacement as soon as possible."

-> show /SYS/MB/RISER/PCIE2/F20CARD/UPTIME

/SYS/MB/RISER/PCIE2/F20CARD/UPTIMETargets:

Properties:type = Power Unitipmi_name = PCIE2/F20/UPclass = Threshold Sensorvalue = 768.000 Hoursupper_nonrecov_threshold = 17500.000 Hoursupper_critical_threshold = 17200.000 Hoursupper_noncritical_threshold = 16800.000 Hourslower_noncritical_threshold = N/Alower_critical_threshold = N/Alower_nonrecov_threshold = N/Aalarm_status = cleared

Commands:cdshow

-> cd /SYS/MB/RISER0/PCIE3/F20CARD

-> set clear_fault_action=trueAre you sure you want to clear /SYS/MB/RISER/PCIE2/F20CARD (y/n)? ySet ’clear_fault_action’ to ’true’


Use the following commands to locate the path to your card. Find the path in a linestarting with “FRU”, similar to the example below.

Related Information


XSCF ESM Monitoring for SPARC M Series ServersFor later-generation F20 cards (part number 511-1500-02 or greater), ESM lifespan isautomatically monitored by the XSCF system management firmware installed onyour host.

Note – SPARC M Series servers do not support XSCF ESM monitoring on F20 cardswith part numbers 511-1275-xx.

XSCF monitors ESMs by recording the Total_Time_On for each installed F20 card,and then issues fault reports when an ESM appoaches the end of its lifespan.

To view the ESM lifespan at any time, type:

-> start /SP/faultmgmt/shellAre you sure you want to start /SP/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm faulty

...FRU : /SYS/MB/RISER0/PCIE3/F20CARD...

XSCF> ioxadm lifetimeNAC Total Time On (% of life)IOU#0-PCI#1 1685 0IOU#0-PCI#3 1685 0XSCF> ioxadm -v lifetimeNAC Total Time On (% of life) Warning Time Fault TimeIOU#0-PCI#1 1685 0 1008000 1051200IOU#0-PCI#3 1685 0 1008000 1051200


30-days before an ESM reaches its threshold, XSCF posts a message, similar to thefollowing message, to the console log:

Once you receive this message, type the following command for more detail:

When an ESM reaches its threshold, XSCF posts this message to the console log:

Once you receive this message, type the following command for more detail:

Mar 25 15:35:10 burl-m4000-0 fmd: SOURCE: sde, REV: 1.16, CSN:0000000000 EVENT-ID:144796b5-a7e2-4285-a3f1-30ce047767f3 Refer tohttp://www.sun.com/msg/SCF-8000-9X for detailed information.

XSCF> fmdump -mMSG-ID: SCF-8000-9X, TYPE: Fault, VER: 1, SEVERITY: MinorEVENT-TIME: Thu Mar 25 15:35:10 EDT 2010PLATFORM: SPARC Enterprise M4000 , CSN: 0000000000, HOSTNAME:burl-m4000-0SOURCE: sde, REV: 1.16EVENT-ID: 144796b5-a7e2-4285-a3f1-30ce047767f3DESC: An energy storage module is approaching its lifespan.Refer to http://www.sun.com/msg/SCF-8000-9X for more information.AUTO-RESPONSE: No immediate action is takenIMPACT: Backup power may not be available in event of power loss.REC-ACTION: Schedule a repair procedure as soon as possible toreplace the ESM.

Feb 17 12:49:24 burl-m4000-0 fmd: SOURCE: sde, REV: 1.16, CSN:0000000000 EVENT-ID:98198f1d-2e66-4635-90dd-5381b2bf2f1f Refer tohttp://www.sun.com/msg/SCF-8000-AE for detailed information.

XSCF> fmdump -mMSG-ID: SCF-8000-AE, TYPE: Fault, VER: 1, SEVERITY: MajorEVENT-TIME: Wed Feb 17 12:49:24 EST 2010PLATFORM: SPARC Enterprise M4000 , CSN: 0000000000, HOSTNAME:burl-m4000-0SOURCE: sde, REV: 1.16EVENT-ID: 98198f1d-2e66-4635-90dd-5381b2bf2f1fDESC: An energy storage module has exceeded its lifespan.Refer to http://www.sun.com/msg/SCF-8000-AE for more information.AUTO-RESPONSE: No immediate action is takenIMPACT: Backup power may not be available in event of power loss.REC-ACTION: Schedule a repair procedure as soon as possible toreplace the ESM.


Note – You can configure XSCF to send these alerts by email or SNMP trap. See yourXSCF documentation for more information.

Once you replace your ESM, use the following command to clear the fault warningsand reset the F20 card Total_Time_On counter to 0:

Use of ioxadm lifetime -z requires fieldeng privileges.

For more information, see the XSCF product documentation:

http://download.oracle.com/docs/cd/E19867-01/E21466-01/E21466-01.pdf

Related Information


Removing the ESMThe card comes with two possible ESM configurations. Use the ESM removalprocedure appropriate for your card.


■ “Remove the ESM (Alternate Configuration)” on page 32

▼ Remove the ESMBefore you begin, perform the following tasks:

■ “Perform ESD Prevention Measures” on page 7.

■ Remove the card from the system and place it on an antistatic mat. Forinstructions, see the service manual and the product notes for your system.

Caution – The card can be hot when removed. Wait 20 seconds after you remove thecard before you touch card components.

1. Remove FMod0 from the card.


XSCF> ioxadm lifetime -z IOU#x-PCI#y




Note – FMod0 must be removed to access the ESM cable.

2. Disconnect the ESM cable from connector J803 on the card.

3. Remove the two retaining pins on the back of the card.

a. First remove the center pin from each retaining pin.

b. Next, remove the outer section of each retaining pin.

4. Slide the ESM assembly (the ESM shroud and the ESM) off the card.

Carefully slide the ESM off the card without disturbing FMod3.

5. Remove the ESM shroud from the ESM.


Related Information■ “Energy Storage Module Overview” on page 2



▼ Remove the ESM (Alternate Configuration)Before you begin, perform the following tasks:


■ Remove the card from the system and place on an antistatic mat. For instructions,see the service manual and the product notes for your system.

1. Remove FMod0 from the card.


Note – FMod0 must be removed to access the ESM cable.

2. Remove the ESM cover.

3. Disconnect the ESM cable from the card.

4. Lift the ESM assembly up and out of the ESM shroud, while carefully threadingthe ESM cable through the opening in the side of the ESM shroud.





Installing the ESMThe card comes with two possible ESM configurations. Use the ESM installprocedure appropriate for your card.


■ “Install the ESM (Alternate Configuration)” on page 35


▼ Install the ESMBefore you begin, perform the following task:


1. Remove FMod0.


2. Cover the ESM with the shroud.

This forms the ESM assembly.

3. Place the ESM assembly next to the board, then slide it gently onto the card.

Line up the retaining pin holes in the shroud with the retaining pin holes in thecard for proper placement.

Note – Take care to slide the ESM assembly into place without disturbing FMod3.

4. Install the two retaining pins from the back of the card.

a. First install the outer section of each retaining pin.


b. Next, install the center sections of the each retaining pin.

5. Connect the ESM plug to J803 on the card.

Route the ESM cable around the retainer clip so that the cable will lay betweenFMod0 and FMod1.

6. Install FMod0.

See “Install an FMod” on page 21



8. Restart the system and verify the correct LED status for the card.

See “Card LEDs” on page 46.




▼ Install the ESM (Alternate Configuration)Before you begin, perform the following task:


1. Remove FMod0.


2. Lower the ESM into the ESM shroud, while carefully threading the ESM cablethrough the opening in the side of the ESM shroud.

3. Connect the ESM plug to J803 on the card.

Route the ESM cable around the retainer clip so that the cable will lay betweenFMod0 and FMod1.


4. Snap the ESM cover into place.

5. Install FMod0.

See “Install an FMod” on page 21



7. Restart the system and verify the correct LED status for the card.

See “Card LEDs” on page 46.





Updating the FMod FirmwareCheck the latest version of the Sun Flash Accelerator F20 PCIe Card Product Notes, aswell as the latest version of the system product notes, to determine if updating theFMod firmware is necessary.

This section contains procedures for updating FMod firmware.

■ “Update the FMod Firmware (Oracle Solaris OS)” on page 37

■ “Update the FMod Firmware (Windows and Linux OS)” on page 39

Related Information



▼ Update the FMod Firmware (Oracle Solaris OS)

Note – Use a console connection to view status information during firmwareupdates.

1. Download and install the Oracle Hardware Management Pack 2.2, or greater,which includes the fwupdate tool, to your server.

Follow instructions to download the firmware here:

http://www.oracle.com/technetwork/server-storage/servermgmt/downloads/index.html

The firmware is available at My Oracle Support:

https://support.oracle.com/

Follow the instructions for installing and configuring the Oracle HardwareManagement Pack in the Oracle Hardware Management Pack 2.2 Installation Guide(E25304), available at the link below. Install all patches required for your OS.

http://download.oracle.com/docs/cd/E20451_01/html/E25304/index.html

Once you have successfully installed the fwupdate component, go on to step 2 ofthis procedure.







2. Download and unpack the latest version of FMod firmware.

The firware is available at https://support.oracle.com/. Search for patch ID145426-01.

3. Stop all I/O functions on the card.

4. To locate an FMod, type:

Note – This procedure shows how to update one FMod. Make sure to update allinstalled FMods.

5. Follow the instructions in the firmware README file to update the firmware.

This example assumes the new firmware file (D20Y_metadata.xml) is in thesame directory from which you run the command.

Caution – Do not run the update disk_firmware command without the -xD20Y_metadata.xml option. Without this option, the device can becomeunresponsive.

# fwupdate list diskDISKS====================ID Brand Model Chassis Slot Type Media Size(GB) Firmware Revision------------------------------------------------------------------------------c2d0 MARVELL SD88SA02 0 14 sata SSD 24 D20Rc2d1 MARVELL SD88SA02 0 14 sata SSD 24 D20Rc2d2 MARVELL SD88SA02 0 14 sata SSD 24 D20Rc2d3 MARVELL SD88SA02 0 14 sata SSD 24 D20R

# fwupdate update disk-firmwate -x D20Y_metadata.xml -n c2d0The following components will be upgraded as shown:====================ID Priority Action Status Old Firmware Ver.Proposed Ver.New Firmware Ver. SystemReboot------------------------------------------------------------------------------c2d0 1 Check FW Success D20R D20Y N/A System Power

Do you wish to process all of the above component upgrades? [y/n] yUpdating c2d0: Success

Verifying all priority 1 updates

Execution Summary



Note – Update the firmware on all FMods on the card before automaticallyrebooting.

6. Repeat step 5 for each FMod on the card.

7. Verify the new FMod firmware was successfully installed. Type:

In this example the firmware was successfully updated from version D20R toD20Y.



▼ Update the FMod Firmware (Windows andLinux OS)● Check the Sun Flash Accelerator F20 PCIe Card Product Notes for information

about updating FMod firmware using a Windows or Linux system.

====================ID Priority Action Status Old Firmware Ver.Proposed Ver.New Firmware Ver. SystemRebootc2d0 1 Post Power Pending D20R D20Y N/A System PowerSystem Reboot required for some applied firmwareDo you wish to automatically reboot now? [y/n]

# fwupdate list diskDISKS====================ID Brand Model Chassis Slot Type Media Size(GB) Firmware Revision------------------------------------------------------------------------------c2d0 MARVELL SD88SA02 0 14 sata SSD 24 D20Y


Updating the SAS/SATA ControllerFirmwareCheck the latest version of the Sun Flash Accelerator F20 PCIe Card Product Notes, aswell as the latest version of the system product notes, to determine if updating thecontroller firmware is necessary.

■ “Update the SAS/SATA Controller Firmware (Oracle Solaris OS)” on page 40

■ “Update the SAS/SATA Controller Firmware (Linux OS)” on page 43

■ “Update the SAS/SATA Controller Firmware (Windows)” on page 43

Related Information


■ “Configure the SAS/SATA Controller as a Boot Device (x86 Systems)” on page 15

▼ Update the SAS/SATA Controller Firmware(Oracle Solaris OS)


1. Download and install the Oracle Hardware Management Pack 2.2, or greater,which includes the fwupdate tool, to your server.

Follow instructions to download the firmware here:


The firmware is available at My Oracle Support:


Follow the instructions for installing and configuring the Oracle HardwareManagement Pack in the Oracle Hardware Management Pack 2.2 Installation Guide(E25304), available at the link below. Install all patches required for your OS.


Once you have successfully installed the fwupdate component, go on to step 2 ofthis procedure.








3. To locate all controllers on the system, type:

4. To locate the F20 card controller, type:

F20 card controllers list MARVELL as the disk manufacturer. See controller c0 inthis example.

# fwupdate list controller==============================================================================Controller==============================================================================ID Manufacturer XML Model Product FW BIOSVersion Support Name Version------------------------------------------------------------------------------c0 LSI Logic N/A 0x0058 SAS1068E 01.27.03.00-IT 6.26.00.00c1 LSI Logic N/A 0x0058 SAS1068E 01.27.03.00-IT 6.26.00.00

# fwupdate list disk==============================================================================Controller==============================================================================ID Manufacturer XML Model Product FW BIOSVersion Support Name Version------------------------------------------------------------------------------c0 LSI Logic N/A 0x0058 SAS1068E 01.27.03.00-IT 6.26.00.00

DISKS========================ID Manufacturer XML Model Chassis Slot Type Media Size(GB) FWVersion Support------------------------------------------------------------------------------c0d0 MARVELL N/A SD88SA02 - 0 sata SSD 24 D20Rc0d1 MARVELL N/A SD88SA02 - 1 sata SSD 24 D20Rc0d2 MARVELL N/A SD88SA02 - 2 sata SSD 24 D20Rc0d3 MARVELL N/A SD88SA02 - 3 sata SSD 24 D20R

==============================================================================Controller==============================================================================ID Manufacturer XML Model Product FW BIOSVersion Support Name Version------------------------------------------------------------------------------c1 LSI Logic N/A 0x0058 -


5. To update the LSI1068E controller firmware, type the following command andthen type “y” to confirm the update when prompted.

6. After installing the firmware update, power off the system.

7. After at least two minutes, power on the system to activate the new firmware.

8. Verify the new controller firmware was successfully installed. Type:

DISKS========================ID Manufacturer XML Model Chassis Slot Type Media Size(GB) FWVersion Support------------------------------------------------------------------------------c1d0 SEAGATE N/A ST914602SSUN146G - - SSD 156 0603c1d1 SEAGATE N/A ST914602SSUN146G - - SSD 156 0603

# fwupdate update sas-controller-firmware -n controller-name -f firmware-update-file

The following components will be upgraded as shown:============================================================================ID Priority Action Status Old Firmware Proposed New System

Ver. Ver. Reboot------------------------------------------------------------------------------c1 1 Check FW Success 01.27.03.00-IT Not Provided N/A None

Do you wish to process all of the above component upgrades? [y/n]? yUpdating c1: Success

Verifying all priority 1 updatesNo metadata provided, so version verification can not be completed

Execution Summary============================================================================ID Priority Action Status Old Firmware Proposed New System

Ver. Ver. Reboot------------------------------------------------------------------------------c1 1 Validate Pending 01.27.03.00-IT Not 01.27.91.00-IT None

Provided

# fwupdate list controller==============================================================================Controller==============================================================================ID Manufacturer XML Model Product FW BIOSVersion Support Name Version------------------------------------------------------------------------------


▼ Update the SAS/SATA Controller Firmware(Linux OS)



2. Download the most up-to-date firmware from the LSI web sitehttp://www.lsi.com/support/sun/.

Check the Sun Flash Accelerator F20 PCIe Card Product Notes for the latest firmwareversions.

3. Download the sasflash utility from the LSI web site.

Find the generic sasflash utility under any controller, for example:

http://www.lsi.com/support/sun/

4. Use the sasflash utility to update the LSI1068E firmware.


6. Power on the system to activate the new firmware.

7. Verify that the new controller firmware was successfully installed.

▼ Update the SAS/SATA Controller Firmware(Windows)



c0 LSI Logic N/A 0x0058 SAS1068E 01.27.91.00-IT 6.26.00.00c1 LSI Logic N/A 0x0058 SAS1068E 01.27.03.00-IT 6.26.00.00






2. Download the most up-to-date firmware from the LSI web sitehttp://www.lsi.com/support/sun/.

Check the Sun Flash Accelerator F20 PCIe Card Product Notes for the latest firmwareversions.

3. Download the sasflash utility from the LSI web site.

Find the generic sasflash utility under any controller, for example:


4. Use sasflash to update the LSI1068E firmware.


6. Power on the system to activate the new firmware.

7. Verify that the new controller firmware was successfully installed.

▼ Replace the CardReplacement cards are shipped with new ESMs, and without FMods. When replacingthe card, you must also replace the ESM. If you are replacing a faulty card, you musttransfer the FMods to the new card.



2. Remove the card from the system and place the card on an antistatic mat.

For instructions, refer to the service manual and the product notes for yoursystem.

3. Remove all the FMods from the old card.


Note – Note the position of each FMod. You must replace each FMod in the samelocation on the new card to retain proper device mapping.

4. Remove the ESM from the old card.

See “Removing the ESM” on page 30.

5. Install the ESM onto the new card.

See “Installing the ESM” on page 33.





6. Install all the FMods onto the new card.


Replace each FMod in the same relative location as on the old card to retainproper system mapping.

7. Install the new card into the system.


Related Information■ “Updating the FMod Firmware” on page 37


Troubleshooting the Card■ “Troubleshooting Chart” on page 45


Troubleshooting Chart

Issue Probable Cause Action

A single FMod is no longer visibleby the OS.

Failed FMod. Find a failed FMod from your OS, just as you wouldlocate a failed HDD. FMod target numbers are always0-3, and those numbers correspond to the FModlabelling on the card.

Card no longer visible to the OS. Failed card. Find a failed card using your OS, just as you wouldlocate any failed PCIe card. See “Replace the Card”on page 44 for instructions about replacing the cardand transferring the ESM and FMods to the new card.


Related Information






Card LEDsUse the card LEDs to determine the status of the card.

I/O performance decreasesdrastically.

Failed ESM. Check card LEDs. If the amber ESM Service RequiredLED is lit, replace the ESM. See“Remove the ESM” onpage 30.

I/O performance slow. FMods notproperly aligned.

Set FMod partitions to start on 4K-alignedboundaries. See “FMod Alignment for OptimalPerformance” on page 13.

I/O performance slow. Connecting theonboardSAS/SATAexpander toexternal devices.

Connecting the onboard expander to external devicescan slow FMod performance as the expander nowmanages more traffic. This feature is not currentlysupported.

Issue Probable Cause Action


Related Information

■ “Troubleshooting Chart” on page 45

LED Icon Description

FMod 3, 2, 1, 0(green)

FMod • On – Normal operation• Blink – There is write activity in the corresponding FMod.• Off – System power is off.

Note: If an FMod is not present then the LED will remain ON.

ESM OK LED(green)

• Off – The system is not running in its normal state. System power might beoff, the ESM could be faulty, the host slot could be powered off, or the cardcould be faulty.

• Steady on – The ESM is adequately charged and capable of providing enoughemergency power to retain data integrity in the event of a power interruption.No service action is required.

• Fast blink – The ESM is charging (approximately five minutes). No serviceaction is required. The card is functioning is write-through (non-caching)mode at this time.

ESM ServiceRequired LED(amber)

• On – The ESM is not retaining enough reserve power to support write-backmode, or the ESM is not reaching the proper charge level in the alloted time.The card is functioning in write-through (non-caching) mode. Service isrequired. The ESM or the card might be faulty.

• Off – Normal operation

Power LED PWR • On – The system is powered on and power rails on the board are up.• Off – Host slot power is off, the system is off, or the card is faulty.



Understanding Specifications

The following topics contain information about card specifications:

■ “Physical Dimensions” on page 49

■ “Environmental Specifications” on page 49

■ “Electrical Specifications” on page 50

■ “Connector Pinouts” on page 50

Physical DimensionsThe Sun Flash Accelerator F20 PCIe card from Oracle meets the PCI low-profile MD2specification.

Environmental Specifications

Note – With the ESM installed, the ambient temperature must not exceed 104˚F(40˚C). For specific site planning guidelines and best practices, refer to the server siteplanning guide and product notes for your server.

Specification Dimention

Height 2.6 in. (67 mm)

Length 6.6 in. (167 mm)

49

Electrical Specifications

Connector PinoutsThere are two types of ports: A narrow port communicates over a narrow link andcontains only one transmit/receive pair, and a wide port communicates over a widelink and contains more than one transmit/receive pair. The ports reside in the PHYlayer, and the link resides in the physical layer.

Note – Direct connection to SAS or SATA drives is not supported.

Specification Measurement

Ambient temperature without forced airflow 32 to 104 ˚F (0 to 40˚C)

Ambient temperature with forced airflow(recommended)

32 to 131˚F (0 to 55˚C)

Relative humidity 10 to 90%, noncondensing

Altitude Up to 9840 ft. (3,000m)

Specification

DC power requirements PCI Express, DC Voltage 3.3V 5%, 12V 8%

AC power consumption 16.5 Watts (charging with de-rated ASIC load)17 Watts (charge complete, with 100% ASIC load)21 Watts (charging with 100% ASIC load)

Current requirements 2.0A @ 3.3 VDC; 1.0A @ 12.0 VDC

Signal Name 1 Physical Link 2 Physical Links 3 Physical Links 4 Physical Links

Rx 0+ S1 S1 S1 S1

Rx 0– S2 S2 S2 S2


Related Information

■ “Configure the SAS/SATA Controller as a Boot Device (SPARC Systems)” onpage 15

Rx 1+ N/A S3 S3 S3

Rx 1– N/A S4 S4 S4

Rx 2+ N/A N/A S5 S5

Rx 2– N/A N/A S6 S6

Rx 3+ N/A N/A N/A S7

Rx 3– N/A N/A N/A S8

Tx 3– N/A N/A N/A S9

Tx 3+ N/A N/A N/A S10

Tx2– N/A N/A S11 S11

Tx 2+ N/A N/A S12 S12

Tx 1– N/A S13 S13 S13

Tx 1+ N/A S14 S14 S14

Tx 0– S15 S15 S15 S15

Tx 0+ S16 S16 S16 S16

Signal ground G1-G9 G1-G9 G1-G9 G1-G9

Chassis ground Housing Housing Housing Housing

Signal Name 1 Physical Link 2 Physical Links 3 Physical Links 4 Physical Links

Understanding Specifications 51


Glossary

Eenergy storage module

(ESM)Device containing supercapaciters that provides enough backup power toenable data in volatile memory to be written to non-volatile flash.

A functional ESM is critical for maintaining FMod performance. In the eventof an ESM failure, the FMod reverts to a write-through(non-cache) mode toensure data integrity, at the expense of write performance.

Fflash memory One of two types of solid-state memory on an FMod.

Flash memory provides persistent data storage on the FMod.

flash module (FMod) A storage device containing solid-state memory.

The FMod consists of two logical components: volatile storage and flashmemory. While volatile storage provides read/write performance similar toRAM, data integrity is potentially at risk during an electrical powerinterruption. The energy storage module (ESM) is necessary to preserve dataintegrity and protect the hardware during a sudden power loss.

The system treats each FMod as a separate storage volume. FMods aremanaged using the same tools as those for conventional (platter-based) harddrives. An FMod can be configurated as a boot device.

The Sun Flash Accelerator F20 PCIe card contains four FMods.

53

Vvolatile storage One of two types of solid-state memory on an FMod.

Volatile storage provides read/write performance similar to DRAM. Data isregularly written to flash memory (as a background task in a first-in-first-outmanner) using a write-through mode.

Wwrite-back mode High-performance data access mode in which data is written to and read

from volatile storage.

Write-back mode is available only when the ESM is properly charged andonline.

write-through mode Persistant data access mode in which data is written directly to flashmemory by-passing the DRAM.

The Sun Flash Accelerator F20 PCIe card reverts to write-through mode if itdetects a failure with the ESM, or if the ESM is charging. This ensures dataintegrity, at the expense of write performance.


Documents

Sun Flash Accelerator F20 PCIe Card User’s Guide · 2 Sun Flash Accelerator F20 PCIe Card User’s Guide • April 2014 The system treats each FMod as a separate storage volume