Oracle SGX-SAS6-INT-Z, SG-SAS6-INT-Z Installation Manual

Download

Page 1

Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6INT-Z

Part No: E22494-08

May 2017

Page 2

Page 3

Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

Part No: E22494-08

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected 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. Reverse engineering, 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 us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

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 any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation 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.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. 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-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?

ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Page 4

Référence: E22494-08

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 à des restrictions d'utilisation et de divulgation. Sauf stipulation expresse de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, accorder de licence, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et par quelque 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'elles soient 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 livré sous licence au Gouvernement des Etats-Unis, ou à quiconque qui aurait souscrit la licence de ce logiciel pour le compte du Gouvernement des Etats-Unis, la notice suivante s'applique :

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 pas conçu ni n'est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer un risque de dommages corporels. Si vous utilisez ce logiciel ou ce matériel dans le cadre d'applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent toute responsabilité quant aux dommages causés par l'utilisation de ce logiciel ou matériel pour des applications dangereuses.

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 marques appartenant à d'autres propriétaires qu'Oracle.

Intel et Intel Xeon sont des marques ou des marques déposées d'Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marques déposées de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d'Advanced Micro Devices. UNIX est une marque déposée de The Open Group.

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 et des services émanant de tiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services émanant de tiers, sauf mention contraire stipulée dans un contrat entre vous et Oracle. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûts occasionnés ou des dommages causés par l'accès à des contenus, produits ou services tiers, ou à leur utilisation, sauf mention contraire stipulée dans un contrat entre vous et Oracle.

Accès aux services de support Oracle

Les clients Oracle qui ont souscrit un contrat de support ont accès au support électronique via My Oracle Support. Pour plus d'informations, visitez le site http://www.oracle.com/

pls/topic/lookup?ctx=acc&id=info ou le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs si vous êtes malentendant.

Page 5

Using This Documentation ................................................................................. 9

1 HBA Overview ............................................................................................... 11

Kit Contents ................................................................................................. 11

HBA Features ............................................................................................... 11

SAS/SATA Features ............................................................................... 12

Valid Drive Mix Configurations With HDDs and SSDs ........................................ 13

Operating System and Technology Requirements ................................................ 13

System Interoperability ................................................................................... 14

Host Platform Support ............................................................................ 14

Storage System Support .......................................................................... 15

Software Support ................................................................................... 15

Boot Support ................................................................................................ 15

2 Hardware Installation and Removal .............................................................. 17

Observing ESD and Handling Precautions ......................................................... 17

Installing the HBA ........................................................................................ 18

▼ To Prepare for Hardware Installation ................................................... 18

▼ To Install the HBA ........................................................................... 19

▼ To Connect the HBA to Internal Storage Devices ................................... 20

▼ To Complete the Installation .............................................................. 20

Next Steps ................................................................................................... 22

Removing the HBA ....................................................................................... 23

▼ To Remove the HBA: ....................................................................... 23

3 Creating a Bootable Drive in a Preboot Environment ................................... 25

Overview of Creating a Bootable Drive in a Preboot Environment .......................... 25

Utilities Overview ................................................................................. 26

Page 6

Contents

Methods For Creating a Bootable Drive .................................................... 27

Creating a Bootable Drive (SPARC) ................................................................. 27

▼ To Create a Bootable Drive (SPARC) .................................................. 27

Using the FCode Utility to Create a Bootable Drive (SPARC) ......................... 27

Creating an Alias for a Bootable Drive (SPARC) ........................................ 30

Creating a Bootable Drive (x86) ...................................................................... 32

Using the UEFI Menu to Create a Bootable RAID Volume (x86) .................... 32

Using the BIOS Configuration Utility (Legacy BIOS Booting) to Create a

Bootable Drive (x86) ............................................................................. 44

Validating the Label of the HBA Drive ............................................................. 49

▼ To Verify That the Label of a RAID Volume Is Valid .............................. 49

Next Steps ........................................................................................... 51

Installing the Oracle Solaris OS ....................................................................... 51

▼ To Prepare to Install the Oracle Solaris OS ........................................... 52

▼ To Install the Oracle Solaris OS: ......................................................... 52

Next Steps ................................................................................................... 52

4 HBA Software Installation ............................................................................. 53

Installing the Oracle Solaris Driver and Firmware ............................................... 53

Firmware Updates ................................................................................. 54

Installing the Linux Driver and Firmware .......................................................... 54

▼ To Install the Linux Driver ................................................................ 54

Firmware Updates ................................................................................. 54

Installing the Windows Server Driver and Firmware ............................................ 55

▼ To Install the Windows Driver ............................................................ 55

Firmware Updates ................................................................................. 55

Installing the VMware Driver and Firmware ...................................................... 55

Installing the RAID Configuration Utility .......................................................... 56

5 Activating Volumes ....................................................................................... 57

Overview of Volume Activation ....................................................................... 57

Activating a Volume (SPARC) ......................................................................... 58

▼ To Activate a Volume (SPARC) .......................................................... 58

Activating a Volume (x86) .............................................................................. 58

▼ To Activate a Volume (x86) ............................................................... 58

Activating a Volume (From an OS) .................................................................. 59

▼ To Activate a Volume (From an OS) .................................................... 59

6 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 7

Contents

6 Known Issues ................................................................................................ 61

MegaRAID Storage Manager GUI-Related Issues ............................................... 61

Cannot Hotplug the HBA Card Through the MSM GUI ............................... 61

Cannot Assign a Global Hot Spare Through the MSM GUI ........................... 62

Cannot Upgrade Firmware on the HBA Therough the MSM GUI ................... 62

Utility-Related Issues ..................................................................................... 62

Sun Storage 6 Gb SAS PCIe HBA, Internal is Not Displayed in the BIOS Setup

Utility .................................................................................................. 63

A Hard Drive is Not Displayed in the BIOS Setup Utility ............................. 63

Non-Alphabetical Characters Are Displayed in RAID Volume Names ............. 63

Cannot Delete a RAID Volume Using the SAS2IRCU Utility ........................... 64

There Is No FCode Utility Command for Creating a RAID 10 Volume ............. 64

Storage-Related Issues .................................................................................... 64

The Oracle Solaris Operating System Installation Hangs ............................... 65

The System Hangs After Deleting a RAID Volume ...................................... 65

Pressing Ctrl+N Might Bypass Network Boot and HBA Option ROM Load ...... 65

Blue Ready-to-Remove LED Does Not Illuminate After Issuing the cfgadm -c

unconfigure Command .......................................................................... 66

Only 24 Devices Are Displayed In The System BIOS Boot List ..................... 68

A HBA Specifications ....................................................................................... 69

Physical Dimensions ...................................................................................... 69

PCI Performance ........................................................................................... 69

SAS Port Bandwidths .................................................................................... 70

HBA Card Layout ......................................................................................... 71

Connectors ................................................................................................... 71

Environmental Specifications ........................................................................... 72

Glossary ............................................................................................................ 75

Page 8

8 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 9

Using This Documentation

■

Overview – Describes how to troubleshoot and maintain the universal host bus adapter

■

Audience – Technicians, system administrators, and authorized service providers

■

Required knowledge – Advanced experience troubleshooting and replacing hardware

Product Documentation Library

Documentation and resources for this product and related products are available at http://

docs.oracle.com/cd/E19337-01/index.html.

Feedback

Provide feedback about this documentation at http://www.oracle.com/goto/docfeedback.

Using This Documentation 9

Page 10

10 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 11

♦ ♦ ♦ C H A P T E R 1

HBA Overview

This chapter provides a basic overview of Oracle's internal Sun Storage 6 Gigabit per second (Gb) Serial Attached SCSI/SATA (SAS) PCI Express (PCIe) host bus adapter (HBA), which uses LSI technology. The chapter also describes the various operating systems, host platforms, software, and infrastructure configurations that support the HBA.

This chapter contains the following topics:

■

“Kit Contents” on page 11

■

“HBA Features” on page 11

■

“Valid Drive Mix Configurations With HDDs and SSDs” on page 13

■

“Operating System and Technology Requirements” on page 13

■

“System Interoperability” on page 14

■

“Boot Support” on page 15

Kit Contents

■

Sun Storage 6 Gb SAS PCIe HBA, Internal

■

Accessing Documentation document

HBA Features

The internal Sun Storage 6 Gb SAS PCIe HBA (SGX-SAS6-INT-Z, SG-SAS6-INT-Z) provides a low-cost, PCI Express SAS solution for computer manufacturers. The HBA uses either a standard or low-profile PCI bracket type and has the following features:

■

Support for over 800 single-pathed, or 400 dual-pathed, internal physical disks that can be accessible by the HBA (for supported configurations, see the storage device documentation)

■

Support for RAID levels 0, 1, and 10

■

Support for a maximum of two logical RAID volumes that can be provided by the HBA

Chapter 1 • HBA Overview 11

Page 12

HBA Features

■

Support for a maximum of 10 physical devices within any single RAID volume and a maximum of fourteen physical devices within all RAID volumes combined

■

PCI Express interface that is compatible with the PCI Express Specification, revision 2.0 and backward compatible with the PCI Express Specification, revision 1.1

■

Implementation of the PCI Express interface as an x4 or x8 interface

■

Compatibility with the PCIe Low Profile standards

■

PCI Express transmission and reception data rate that is 5.0 Gb/s in each direction, yielding a total bandwidth of 10 Gb/s for each full-duplex lane

■

Simplified cabling with a point-to-point, serial architecture

■

Smaller and thinner cables that promote unrestricted airflow

■

Serial, point-to-point, enterprise-level storage interface

SAS/SATA Features

The following are the SAS/SATA features supported by the HBA:

■

Serial SCSI protocol (SSP), serial ATA tunneling protocol (STP), and serial management protocol (SMP), as defined in the Serial Attached SCSI (SAS) Specification, version 2.0

■

SAS interface that is compatible with the ANSI Serial Attached SCSI Specification, revision

2.0 and the Serial ATA Specification, revision 2.6

■

Capability of running with either four or eight serial ports for connection to SAS/SATA (Serial ATA) devices

■

Each serial port is capable of 6.0 Gb/s SAS and SATA link rates and 1.5 Gb/s or 3.0 Gb/s SATA link rates

Note - While each serial port is capable of 6 Gb/s SAS and SATA link rates, only four of

the eight serial ports can operate at 6 Gb/s link rates at one time. This is to accommodate platforms that are not designed for 6 Gb/s operation.

■

Support for the easy addition of SAS interfaces to any computer, workstation, or server with a PCI Express bus

■

Four or eight PCIe PHYs, which provide possible host-side maximum transmission and reception rates of up to 4 Gb/s

■

Narrow and wide ports

■

SATA target devices, as defined in the Serial ATA Specification, version 2.6

■

Transfer of data using SCSI information units

Figure 1, “Oracle's Sun Storage 6 Gb SAS PCIe HBA, Internal,” on page 13 shows the

physical features of the HBA.

12 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 13

Valid Drive Mix Configurations With HDDs and SSDs

FIGURE 1

Oracle's Sun Storage 6 Gb SAS PCIe HBA, Internal

Valid Drive Mix Configurations With HDDs and SSDs

This HBA supports connectivity using SATA II drives, SAS drives, or both. The following are some basic rules about the types of drives you can use:

■

Within a logical volume:

■

You cannot mix SAS and SATA drives.

■

You cannot mix HDDs and SSDs of any type.

■

Within an enclosure (SAS expander or direct-connect SAS cable), you can mix any drive types, subject to any restrictions imposed by the enclosure.

Operating System and Technology Requirements

The HBA requires the operating system (OS) and technology levels, at minimum, listed in

Table 1, “Supported Operating System/Technology Versions ,” on page 13.

TABLE 1

Operating System/Technology Recommended Versions (minimum)

Oracle Solaris OS for the x86 (32bit and 64-bit) platform

Supported Operating System/Technology Versions

†

■ Oracle Solaris 11.1 with SRU7

■ Oracle Solaris 10 01/13 with patches 149176-02 and 145649-04, at minimum

Chapter 1 • HBA Overview 13

Page 14

System Interoperability

Operating System/Technology Recommended Versions (minimum)

Oracle Solaris OS for the SPARC (32-bit and 64-bit) platform

Linux OS (64-bit) ■ Red Hat Enterprise Linux (RHEL) 5.9 and 6.4

Virtual Machine OS Oracle VM 3.2.1

Microsoft Windows OS (64-bit) ■ Window Server 2008 R2 including SP1

VMware Technology ■ VMware ESX/ESXi 5.0

†

Oracle supports the Oracle Solaris 10 10/09 OS with patches 142676-02 (x86) and 143523-02 (SPARC) as the minimum Oracle Solaris OS level. However, if issues occur with the HBA, Oracle Support requires that you update to the recommended OS levels listed in Table

1, “Supported Operating System/Technology Versions ,” on page 13.

System Interoperability

This section provides host platform and software support information. The section contains the following topics:

†

To obtain the latest patches and SRUs, go to http://support.oracle.com

■ Oracle Solaris 11.1 with SRU7

■ Oracle Solaris 10 01/13 with patches 149175-02 and 145648-04, at minimum

To obtain the latest patches and SRUs, go to http://support.oracle.com

■ SUSE Linux Enterprise Server (SLES) 11 SP2

■ Oracle Enterprise Linux 5.9 and 6.4 (Red Hat Compatible Kernel (RHCK) and Unbreakable Enterprise Kernel (UEK) 2, at minimum)

■ Windows Server 2012

■ VMware ESX/ESXi 5.1

■

“Host Platform Support” on page 14

■

“Storage System Support” on page 15

■

“Software Support” on page 15

Host Platform Support

Table 2, “Host Platform Support,” on page 14 lists the supported host platforms for the

HBA. For up-to-date information, see your Oracle system Product Notes and web pages.

For supported operating system and technology versions, see Table 1, “Supported Operating

System/Technology Versions ,” on page 13.

TABLE 2

Platform Supported OS/Technology

Oracle SPARC Servers

14 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Host Platform Support

Page 15

Platform Supported OS/Technology

SPARC T3-2 Oracle Solaris

SPARC T4-2 Oracle Solaris

Oracle x86 Servers

Sun Fire X4170 M2 Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Sun Fire X4270 M2 Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Sun Fire X4470 Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Sun Server X2-4 Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Sun Server X3-2 Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Sun Server X3-2L Oracle Solaris, Linus, VMware, Virtual Machine, and Windows

Sun Server X4-2 Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Sun Server X4-2L Oracle Solaris, Linux, VMware, Virtual Machine, and Windows

Storage System Support

Internal disk drives are the only storage supported by the HBA.

Boot Support

Software Support

Install, Flash, and BIOS configuration utilities are provided. The HBA uses the FusionMPT architecture for all major operating systems, which allows for thinner drivers for better performance. To obtain the most up-to-date device drivers, firmware, and boot code that support your operating system, go to: http://www.lsi.com/sep/Pages/oracle/index.aspx

Boot Support

Booting through the HBA is supported in the following operating system and technology environments:

■

Oracle Solaris 10 01/13 OS for the SPARC and x86 platforms

■

Oracle Solaris 10 11.1 OS for the SPARC and x86 platforms

■

RHEL 5.9 and 6.4 OSes

■

SLES 11 SP2 OS

■

Oracle Linux 5.9 and 6.4 OSes

■

Oracle VM 3.2.1 OS

■

Windows Server 2008 R2 including SP1 OS

Chapter 1 • HBA Overview 15

Page 16

Boot Support

■

Windows Server 2012 OS

■

ESX and ESXi Server, version 5.0 and 5.1 technology

16 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 17

♦ ♦ ♦ C H A P T E R 2

Hardware Installation and Removal

This chapter explains how to install and remove the HBA. For detailed instructions, see your system installation or service manual and the installation manual for the storage devices to be connected to the HBA.

This chapter contains the following topics:

■

“Observing ESD and Handling Precautions” on page 17

■

“Installing the HBA” on page 18

■

“Next Steps” on page 22

■

“Removing the HBA” on page 23

Observing ESD and Handling Precautions

Caution - Damage to the HBA can occur as the result of careless handling or electrostatic

discharge (ESD). Always handle the HBA with care to avoid damage to electrostatic-sensitive components.

To minimize the possibility of ESD-related damage, use both a workstation antistatic mat and an ESD wrist strap. You can get an ESD wrist strap from any reputable electronics store or from Oracle as part number #250-1007.

Observe the following precautions to avoid ESD-related problems:

■

Leave the HBA in its antistatic bag until you are ready to install it in the system.

■

Always use a properly fitted and grounded wrist strap or other suitable ESD protection when handling the HBA and observe proper ESD grounding techniques.

■

Always hold the HBA by the metal enclosure.

■

Place the HBA on a properly grounded antistatic work surface pad when it is out of its protective antistatic bag.

Chapter 2 • Hardware Installation and Removal 17

Page 18

Installing the HBA

Before you start, read the instructions in this section as well as the installation instructions for the storage devices to be connected to the HBA. This section contains the following topics:

■

“To Prepare for Hardware Installation” on page 18

■

“To Install the HBA” on page 19

■

“To Connect the HBA to Internal Storage Devices” on page 20

■

“To Complete the Installation” on page 20

To Prepare for Hardware Installation

Read and observe the safety information for this product.

See the Safety and Compliance documentation for this HBA.

Make a backup of your data.

Familiarize yourself with the physical features of the HBA (see Figure 17, “HBA

Board Layout,” on page 71).

Ensure that you have the proper cables for the HBA.

The HBA has two internal x4 mini-SAS connectors, each connecting to four 6 Gb/s SAS ports. You will need to use the appropriate cable to connect the HBA to SAS versus SATA storage devices.

For connection to internal drives or backplanes, you must use an internal cable with a standard mini-SAS connector (SFF-8087) on the controller side of the cable. The other end of the cable can fan out into four SAS-style cables for direct connection to SAS or SATA disk drives. Figure

2, “Installing the HBA,” on page 19 illustrates the connector locations on the internal HBA

and the use of a controller-based, fan-out cable to connect to drives that require a SAS-style signal connector.

Use only Oracle-provided SAS cables. For more information or to purchase cables for your Oracle system, visit http://www.oracle.com. Cable connectors are keyed so that you cannot insert them incorrectly.

Unpack the box containing the HBA in a static-free environment and inspect it for damage.

Note - Leave the HBA in its protective bag until you are ready to install it. If there is damage,

contact Oracle customer support.

18 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 19

To Install the HBA

Attach an antistatic wrist strap and remove the HBA from its protective bag.

See “Observing ESD and Handling Precautions” on page 17.

Refer to the service or installation manual for your particular system for instructions on how to locate an available PCI Express slot in the system.

Align the HBA to the PCI Express slot and press down gently and firmly to seat the HBA into the slot (see Figure 2, “Installing the HBA,” on page 19).

FIGURE 2

Figure Legend

Bracket screw

Press here

Mini-SAS x4 (SFF-8087) internal connector with shell

Press here

Mini-SAS x4 (SFF-8087) to SAS x1 internal fan-out cable

32-bit slots (3.3 V only)

PCI Express x8 slot

64-bit slot (3.3 V only)

Installing the HBA

Chapter 2 • Hardware Installation and Removal 19

Page 20

To Connect the HBA to Internal Storage Devices

Edge of host board

Note - The host adapter shape, size, and locations of components may vary from this

illustration.

When the HBA is fully inserted in the slot, secure the HBA to the chassis of the system by installing the bracket screw, if applicable, or by engaging the system retention mechanism.

To Connect the HBA to Internal Storage Devices

Configure and install the SAS devices, SATA devices, or both in the system.

For more information, see the documentation for the storage devices.

Connect the serial SAS cables to the two internal x4 mini-SAS connectors and attach the other end of the cables to the serial disk drives or other SAS/SATA devices, per your requirements (Figure 2, “Installing the HBA,” on page 19).

Use only Oracle-provided SAS cables (provided with your system at time of purchase). You can also purchase Oracle cables at http://www.oracle.com.

Observe the light-emitting diodes (LEDs) during data transfer on the connected drives to ensure normal operation of the HBA.

To Complete the Installation

Replace the system cover and reconnect the AC power cords, as described in the system documentation.

If you needed to turn the system power off as part of the installation, turn power on to the system.

Note - Ensure that the power is turned on to the SAS devices, SATA II devices, or both before

or at the same time that the power is turned on to the host system. If the system is powered up before these devices, the devices might not be recognized.

20 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 21

If you need to install an OS on your system, complete the procedures in

Chapter 3, “Creating a Bootable Drive in a Preboot Environment ” and then go to

the next step.

If you already have an OS installed on an x86 system, review the BIOS bootup messages to ensure that you see the LSI BIOS initialization banner and that you are prompted for the BIOS utility (by pressing Ctrl+C).

If you see the banner and are prompted for the utility, it means the BIOS has detected the HBA card.

If you already have an OS installed on a SPARC system, during the powerup process of the system, use the probe-scsi-all command at the Open Boot Prompt (OBP) ok prompt to verify that the system recognizes the HBA.

The probe-scsi-all command displays the SCSI devices that are connected to the host, as shown in the following example.

{0} ok probe-scsi-all /pci@0/pci@0/pci@8/pci@0/pci@a/LSI,sas@0 MPT Version 2.00, Firmware Version 4.00.00.00 Target 9 Unit 0 Disk SEAGATE ST914602SSUN146G0603 286739329 Blocks, 146 GB SASAddress 5000c5000b305b4d PhyNum 0 Target a Unit 0 Disk SEAGATE ST914602SSUN146G0603 286739329 Blocks, 146 GB SASAddress 5000c5000b304cad PhyNum 1 Target b Unit 0 Disk HITACHI H101414SCSUN146GSA23 286739329 Blocks, 146 GB SASAddress 5000cca000310015 PhyNum 2 Target c Unit 0 Disk HITACHI H101414SCSUN146GSA23 286739329 Blocks, 146 GB SASAddress 5000cca0002cf035 PhyNum 3 {0} ok

To Complete the Installation

This example shows a SAS 2 controller (LSI,sas@0) connected to four physical drives.

(Optional) If you would like to create additional RAID volumes on the system (maximum of two RAID 0, 1, and 10 volumes per system), follow either Step 6a or

Step 6b, then continue with Step 6c:

(SPARC only) During the power-up process of the system, access the OBP and create RAID volumes for the HBA by issuing the appropriate FCode commands.

Chapter 2 • Hardware Installation and Removal 21

Page 22

Next Steps

For more information about the different FCode commands that you can use to create RAID volumes, see Chapter 3, “Creating a Bootable Drive in a Preboot Environment ”.

(x86 only) During the power-up process of the system, review the BIOS bootup messages, access the BIOS Configuration utility by pressing Ctrl+C, when prompted, and create volumes for the HBA through the BIOS utility.

For more information about creating volumes through the BIOS utility, see Chapter 3,

“Creating a Bootable Drive in a Preboot Environment ”.

Go to the Oracle support area of the LSI web site (http://www.lsi.com/sep/

Pages/oracle/index.aspx), download the SAS2IRCU utility, and issue the sas2ircu

command, with no options, at the command-line or at a terminal window.

Issuing the sas2ircu command, with no options, produces a list of SAS2IRCU utility commands that you can use to create RAID volumes for the HBA. Upon reviewing the list of commands, use the appropriate commands to create the RAID volumes.

Note - With version 04.250.04.02 of the SAS2IRCU utility, be careful when using the DELETE

command. The DELETE command can take no arguments or a single argument. Issuing the DELETE command with no arguments deletes all RAID volumes. Issuing the command with a

single argument deletes only the RAID volume that you specify in the argument. With version

6.250.02.00 of the SAS2IRCU utility or later, use the DELETEVOLUME command to delete a single RAID volume.

For more information about the RAID configuration utilities, see “Installing the RAID

Configuration Utility” on page 56.

After you initiate the creation of a RAID 1 or RAID 10 volume, the HBA performs a background initialization task that synchronizes untouched blocks of each side of the mirror for the entire volume. This background task operates transparently, and does not prevent normal communication with the volume or immediate mirroring of new data written to the volume. However, applications might experience performance degradation until the background initialization task is complete.

Next Steps

Install any software required by the HBA, specific to your operating system, as described in

Chapter 4, “HBA Software Installation”.

22 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 23

Removing the HBA

If you need to remove the HBA from the system, for any reason, follow the procedure in this section.

To Remove the HBA:

Prepare your operating system for HBA removal.

Attach an antistatic wrist strap.

See “Observing ESD and Handling Precautions” on page 17.

Turn off the power to the system, all drives, enclosures, and system components.

Refer to the service manual for your specific system to locate the HBA in the chassis of the system.

Removing the HBA

Unscrew the bracket screw securing the HBA to the system, if applicable, or disengage the system retention mechanism that is securing the HBA to the system.

Pull up on the HBA to unseat it from the PCI Express slot.

Refer to the service manual for your specific system to reattach the cover to the system.

Chapter 2 • Hardware Installation and Removal 23

Page 24

24 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 25

♦ ♦ ♦ C H A P T E R 3

Creating a Bootable Drive in a Preboot Environment

This chapter describes how to use the HBA for your boot device prior to installing an operating system (OS) on the system.

Note - If you are installing the HBA into a system that already has an OS installed, do not

perform any procedures in this chapter. Instead, complete the HBA installation, as described in

“To Complete the Installation” on page 20.

This chapter contains the following topics:

■

“Overview of Creating a Bootable Drive in a Preboot Environment” on page 25

■

“Creating a Bootable Drive (SPARC)” on page 27

■

“Creating a Bootable Drive (x86)” on page 32

■

“Validating the Label of the HBA Drive” on page 49

■

“Installing the Oracle Solaris OS” on page 51

■

“Next Steps” on page 52

Overview of Creating a Bootable Drive in a Preboot Environment

As an installation option, you can choose to install the HBA into a system that does not yet have an OS installed. With this installation option, if you plan to use the HBA as your boot device, you can optionally create a RAID volume for the HBA. You can then install the OS onto a physical drive or onto that RAID volume to enable you to boot from the HBA. On a SPARC system, you would perform these actions through the FCode utility. On an x86 system, you would do so either through the Unified Extensible Firmware Interface (UEFI) Drive Control menu of the BIOS Setup utility (UEFI booting) or through the BIOS Configuration utility (Legacy BIOS booting).

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 25

Page 26

Overview of Creating a Bootable Drive in a Preboot Environment

This section contains the following topics:

■

“Utilities Overview” on page 26

■

“Methods For Creating a Bootable Drive” on page 27

Utilities Overview

You can specify the HBA to be your boot device by using one of these utilities:

■

FCode utility - A utility that you can run on a SPARC system and that is accessible through the Open Boot PROM (OBP) environment. This utility consists of a set of special commands to display targets and manage RAID volumes.

■

UEFI menu of the BIOS Setup utility - A utility that you can run on an x86 system only if you have set your system BIOS to boot in UEFI BIOS mode (which you can specify through the Boot menu of the BIOS Setup utility). You can access this utility by pressing F2, when prompted, during bootup, and then using the right arrow key to navigate to the UEFI Driver Control menu at the top of the screen. The UEFI Driver Control menu provides a standard environment for booting an operating system, managing physical disks and RAID volumes, and running pre-boot applications.

Note - Some operating system versions do not support UEFI BIOS mode. For information

about whether your operating system supports UEFI BIOS mode, see your system and operating system documentation.

■

BIOS Configuration utility - A legacy booting utility that you can run on an x86 system only if you have set your system BIOS to boot in legacy mode (which you can specify through the Boot menu of the BIOS Setup utility). You access this utility by typing Ctrl

+C, when prompted, during bootup. This utility consists of a text-based user interface that

enables you to manage physical disks and RAID volumes.

Note - Entering the BIOS Configuration utility (even if you make no changes in the utility)

might cause the system boot order list, provided by the system BIOS, to reset. To ensure that the boot order is accurate after exiting the utility, access the server mainboard BIOS during the next reboot of the system. Review the boot order list to verify that the order is correct, and make any changes, if necessary. This will occur each time you enter the utility.

26 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 27

Methods For Creating a Bootable Drive

Based on the type of system in which you are installing the HBA (SPARC or x86), follow the procedures in one of these sections:

■

If you are installing the HBA into a SPARC system, go to “Creating a Bootable Drive

(SPARC)” on page 27.

■

If you are installing the HBA into an x86 system, go to “Creating a Bootable Drive

(x86)” on page 32.

Creating a Bootable Drive (SPARC)

Follow the steps in this section to create a bootable drive in a preboot environment on a SPARC system:

■

“To Create a Bootable Drive (SPARC)” on page 27

Creating a Bootable Drive (SPARC)

To Create a Bootable Drive (SPARC)

You do not need to perform both steps in this procedure if you plan to install the Oracle Solaris OS onto a physical drive. If you plan to use a physical drive to install the OS, go directly to Step

Optionally create a RAID volume from which to boot (see “Using the FCode Utility

to Create a Bootable Drive (SPARC)” on page 27).

Create an alias for the bootable drive (see “Creating an Alias for a Bootable

Drive (SPARC)” on page 30).

Using the FCode Utility to Create a Bootable Drive (SPARC)

This section describes how to use the FCode utility to set up a RAID volume on a SPARC system prior to installing the Oracle Solaris operating system (OS). You can then use the RAID volume as your boot drive upon which to install the Oracle Solaris OS. This section contains the following topics:

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 27

Page 28

To Prepare to Use the FCode Utility (SPARC)

■

“To Prepare to Use the FCode Utility (SPARC)” on page 28

■

“To Create a RAID Volume With the FCode Utility (SPARC)” on page 29

To Prepare to Use the FCode Utility (SPARC)

Before using the FCode utility to set up a RAID volume on a SPARC system, prepare to use the FCode utility by doing the following:

Note - Do not perform the steps in this section if you want to install the OS on a

non-RAID volume. Instead, go directly to “To Create an Alias for a Bootable Drive

(SPARC)” on page 30.

Open an xterm or a gnome terminal window.

FCode commands can produce large amounts of detailed output. The xterm and gnome terminal windows provide scroll bar functionality, which helps with viewing such output.

Enter the OBP environment by performing one of the following tasks:

■ Press STOP+A on a Sun keyboard from Oracle.

■ Issue a break from a remote console.

Use the show-devs command to list the device paths on the system and select the device path for the HBA.

The mpt_sas-based controllers will end with LSI,sas@number.

{0} ok show-devs <...> /pci@1e,600000/pci@0/pci@3/LSI,sas@0 /pci@1e,600000/pci@0/pci@3/LSI,sas@0/disk /pci@1e,600000/pci@0/pci@3/LSI,sas@1 <...>

Use the select command to select the HBA on which the FCode commands that you issue will operate.

{0} ok select /pci@1e,600000/pci@0/pci@3/LSI,sas@0

If you were able to determine and select the card that you wanted in the previous step, skip to Step 6. Otherwise, if more than one of the mpt_sas-based cards is

28 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 29

To Create a RAID Volume With the FCode Utility (SPARC)

displayed in the show-devs output, use the select and .properties commands to determine which card you want and then select that card.

{0} ok select /pci@1e,600000/pci@0/pci@3/LSI,sas@0 {0} ok .properties … subsystem-id 00003050

The internal facing cards contain a subsystem-ID of 00003050. To further specify the card, you can also display the SAS addresses of any connected drives by using the show-children command.

Review the following table for useful Fcode commands.

FCode Command Description

show-children

show-volumes

create-raid0-volume

create-raid1-volume

create-raid10-volume

delete-volume

Lists all connected physical drives and RAID volumes.

Lists all connected RAID volumes in detail.

Creates a RAID 0 volume (minimum two targets).

Creates a RAID 1 volume (exactly two targets).

Creates a RAID 10 volume (minimum four targets).

Deletes a RAID volume.

You are now ready to use the FCode commands to optionally create a RAID volume on the HBA. For more information, see “To Create a RAID Volume With the FCode Utility

(SPARC)” on page 29. If you plan to install the OS onto a physical drive, go to “Creating an Alias for a Bootable Drive (SPARC)” on page 30.

To Create a RAID Volume With the FCode Utility (SPARC)

Perform the steps in this section if you want to optionally configure a RAID volume on a SPARC system. You can then install the Oracle Solaris operating system (OS) on that RAID volume.

Note - Do not perform the steps in this section if you want to install the OS on a

non-RAID volume. Instead, go directly to “To Create an Alias for a Bootable Drive

(SPARC)” on page 30.

Use the show-children command to list all the physical drives attached to the HBA.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 29

Page 30

To Create an Alias for a Bootable Drive (SPARC)

{0} ok show-children MPT Version 2.00, Firmware Version 4.00.00.00 Target 9 <...>Unit 0 Disk SEAGATE ST914602SSUN146G0603 286739329 Blocks, 146 GB SASAddress 5000c5000b305b4d PhyNum 0 Target a Unit 0 Disk SEAGATE ST914602SSUN146G0603 286739329 Blocks, 146 GB SASAddress 5000c5000b304cad PhyNum 1 Target b Unit 0 Disk HITACHI H101414SCSUN146GSA23 286739329 Blocks, 146 GB SASAddress 5000cca000310015 PhyNum 2 Target c Unit 0 Disk HITACHI H101414SCSUN146GSA23 286739329 Blocks, 146 GB SASAddress 5000cca0002cf035 PhyNum 3  

Use the create-raid0-volume, create-raid1-volume, or create-raid10-volume command to create a RAID volume from the physical disks.

Note - The only volumes supported by the HBA are volumes created with size MAX (the volumes

use the maximum drive space possible). Volumes using less than the maximum space of the smallest physical drive in the volume are not supported.

{0} ok 9 a create-raid0-volume -- for RAID 0, with targets 9 and a -{0} ok 9 a b c create-raid10-volume -- for RAID 10 with targets 9, a, b, and c --

Go to “Creating an Alias for a Bootable Drive (SPARC)” on page 30.

Creating an Alias for a Bootable Drive (SPARC)

This section describes how to create an alias for a bootable drive in order to help simplify the process of booting the drive. This section contains the following topic:

■

“To Create an Alias for a Bootable Drive (SPARC)” on page 30

To Create an Alias for a Bootable Drive (SPARC)

Perform the steps in this section to help simplify the process of booting a drive on a SPARC system.

30 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 31

To Create an Alias for a Bootable Drive (SPARC)

Issue the show-disks command to list the disks on the system.

Note that, as shown in the following example, you can determine the HBA drives by looking for the LSI,sas@number label, where number is 0 for the first HBA detected, and increments for each additional HBA detected.

{0} ok show-disks <...> a) /pci@1e,600000/pci@0/pci@3/LSI,sas@0/disk b) /pci@1e,600000/pci@0/pci@3/LSI,sas@1/disk c) /pci@1e,600000/pci@0/pci@3/LSI,sas@2/disk <...> q) NO SELECTION Enter Selection, q to quit:

Select the bootable drive for which you want to create an alias.

a) /pci@1e,600000/pci@0/pci@3/LSI,sas@0/disk b) /pci@1e,600000/pci@0/pci@3/LSI,sas@1/disk c) /pci@1e,600000/pci@0/pci@3/LSI,sas@2/disk <...> q) NO SELECTION Enter Selection, q to quit: c /pci@1e,600000/pci@0/pci@3/LSI,sas@2/disk has been selected.

Use the nvalias alias-name HBA-drive-path command to create an alias for the bootable drive that you selected in Step 2 (you can press Ctrl+Y to paste the device path).

In the following example, the alias name is mydev.

{0} ok nvalias mydev /pci@1e,600000/pci@0/pci@3/LSI,sas@2/disk

You can now boot from the bootable drive by using the boot alias-name command.

{0} ok boot mydev

To optionally add the bootable drive to the boot-device list and then automatically boot from the drive by controlling the boot device order, issue the following commands, as shown.

{0} ok printenv boot-device boot-device = disk0 disk1 {0} ok setenv boot-device mydev disk0

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 31

Page 32

Creating a Bootable Drive (x86)

boot-device = mydev disk0

In this example, the mydev alias is set as disk0, the first disk in the boot device list. This results in the automatic booting of the bootable drive, /pci@1e,600000/pci@0/pci@3/LSI,sas@2/ disk.

Validate the label of the bootable drive by following the steps in “Validating the

Label of the HBA Drive” on page 49.

Creating a Bootable Drive (x86)

You have the following methods for creating a bootable drive on an x86 system:

■

If you have set your system BIOS to boot in UEFI BIOS mode (which you can specify through the Boot menu of the BIOS Setup utility), do one of the following:

- Install the OS on a non-RAID volume by using the Oracle System Assistant utility. For more information, see the Oracle System Assistant documentation.

- Install the OS on a RAID volume by setting up a RAID volume with the UEFI menu of the Setup utility, as described in “Using the UEFI Menu to Create a

Bootable RAID Volume (x86)” on page 32.

■

If you have set your system BIOS to boot in legacy mode (which you can specify through the Boot menu of the BIOS Setup utility), follow the steps in “Using

the BIOS Configuration Utility (Legacy BIOS Booting) to Create a Bootable Drive (x86)” on page 44.

Using the UEFI Menu to Create a Bootable RAID Volume (x86)

This section describes how to use the UEFI Driver Control menu in the BIOS Setup utility to optionally set up a RAID volume on an x86 system. You can then install the operating system onto that RAID volume.

Note - If you want to install the OS on a non-RAID volume, you do not need to perform the

steps in this section. Instead, during bootup, launch Oracle System Assistant and specify a bootable drive on which to install an OS. For more information, see the Oracle System Assistant documentation.

32 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 33

To Verify the Drives and Their Slots (x86)

In order to configure a RAID volume, the HBA must have firmware version 11.05.02.00, at minimum, installed. Before performing the steps in this section, verify the firmware level on the HBA and perform any firmware updates, as necessary. For information about updating firmware, see Chapter 4, “HBA Software Installation”.

Perform the following procedures, in the order listed below, to configure a RAID volume on an x86 system:

■

“To Verify the Drives and Their Slots (x86)” on page 33

■

“To Create a RAID Volume (x86)” on page 37

■

“To Confirm the RAID Volume Creation (x86)” on page 41

To Verify the Drives and Their Slots (x86)

This procedure helps you identify drives to be used in a RAID volume configuration.

From the Integrated Lights Out Manager (ILOM) software or Video Graphics Array (VGA) video port, access the system console.

Initiate a system boot.

During the boot process, the BIOS initialization banner lists information about the discovered SAS adapters and devices that are attached to the discovered HBAs in the system.

Press F2 during the boot process, when prompted, to launch the BIOS Setup utility, and then use the right arrow key to navigate to UEFI Driver Control menu.

From the list of controllers that are displayed, use the up and down arrow keys to navigate to the LSI SAS2 MPT Controller menu option and press Enter.

In the following example, the LSI SAS2 MPT Controller HII Configuration Application field is then displayed in the left tab of the utility.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 33

Page 34

To Verify the Drives and Their Slots (x86)

FIGURE 3

LSI SAS2 MPT Controller HII Configuration Application Field

Press Enter to display the Controller Management, Virtual Disk Management, and Physical Disk Management menu options.

Use the arrow keys to navigate to the Physical Disk Managment menu option and press Enter.

34 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 35

To Verify the Drives and Their Slots (x86)

FIGURE 4

Selecting the Physical Disk Management Menu Option

From the menu options that are displayed, navigate to the View Physical Disk Properties menu option and press Enter.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 35

Page 36

To Verify the Drives and Their Slots (x86)

FIGURE 5

Selecting the View Physical Properties Menu Option

On the properties page that is displayed, navigate to the View Physical Disk Properties field and press Enter.

The Select Physical Disk pop-up window is displayed. In the following example, there are 4 drives in Slots 0, 1, 2, and 3.

36 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 37

To Create a RAID Volume (x86)

FIGURE 6

Select Physical Disk Pop-up Window

Before You Begin

Review the physical disks and note their respective slots for future reference.

You can use these disks to be part of your RAID volume configuration. See “To Create a RAID

Volume (x86)” on page 37.

To Create a RAID Volume (x86)

After you have verified which drives are available for RAID volume configuration, as described in “To Verify the Drives and Their Slots (x86)” on page 33, you can use those drives to create a RAID volume. In the following procedure, drives 2 and 3 from Step 8 (0:1:2, 0:1:3) are being used to create a RAID 1 volume.

Note - Do not perform the steps in this procedure if you want to install the operating system on

a non-RAID volume. Instead, use Oracle System Assistant.

The HBA must have firmware level 11.05.02.00, at minimum, installed.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 37

Page 38

To Create a RAID Volume (x86)

From the Select Physical Disk pop-up window (Figure 6, “Select Physical Disk

Pop-up Window,” on page 37), use the Esc key to return to the Controller

Management menu option, and press Enter.

FIGURE 7

Selecting the Controller Management Menu Option

From the menu options that are displayed, use the arrow keys to navigate to the Create Configuration menu option and press Enter.

38 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 39

To Create a RAID Volume (x86)

FIGURE 8

Selecting the Create Configuration Menu Option

From the menu options that are displayed, use the arrow keys to navigate to the Select Physical Disks menu option and press Enter.

In the following example, note that the RAID 1 level is selected. You might want to create a different level of RAID volume, based on your requirements.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 39

Page 40

To Create a RAID Volume (x86)

FIGURE 9

Selecting the Select Physical Disks Menu Option

For each drive that you want in the RAID volume configuration, do the following:

Use the arrow keys to navigate to the drive.

Press Enter to launch the Enabled/Disabled pop-up window for that drive.

In the pop-up window, navigate to the Enabled field and press Enter.

The pop-up window closes and the drive is now listed as Enabled.

40 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 41

To Confirm the RAID Volume Creation (x86)

FIGURE 10

Enabling the Drives for RAID Volume Configuration

Before You Begin

After you have enabled all the drives that you want to be part of the RAID volume, use the arrow keys to navigate to the Apply Changes field on the same page, and press Enter.

The RAID volume is now created with the drives that you enabled.

Complete the steps in “To Confirm the RAID Volume Creation

(x86)” on page 41.

To Confirm the RAID Volume Creation (x86)

Before performing this procedure, verify the drives and their slots (“To Verify the Drives and

Their Slots (x86)” on page 33) and create a RAID volume (“To Create a RAID Volume (x86)” on page 37).

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 41

Page 42

To Confirm the RAID Volume Creation (x86)

Use the Esc key to return to the Create Configuration menu option (Figure 9,

“Selecting the Select Physical Disks Menu Option,” on page 40) and press

Enter.

A page is displayed that asks if you would like to continue with the volume creation.

Confirm the volume creation by doing the following:

Use the arrow keys to navigate to the Confirm field.

Change the value of the Confirm field to Enabled and press Enter.

Yes and No fields are displayed.

Use the arrow key to navigate to the Yes field and press Enter.

This completes the RAID volume creation process.

FIGURE 11

Confirming the RAID Volume Creation

42 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 43

To Confirm the RAID Volume Creation (x86)

To verify that the RAID volume (logical volume) was created, use the arrow keys to navigate to the Virtual Disk Management menu option (Figure 4, “Selecting

the Physical Disk Management Menu Option,” on page 35), press Enter, and

review the RAID volume information on the page that is displayed.

In the following example, a RAID 1 volume is created with a target ID of 891.

FIGURE 12

Viewing the Newly Created RAID Volume

Exit the Setup utility and reboot into the Oracle System Assistant utility to install an OS on that RAID volume or manipulate the boot drive.

You can now nstall the OS on the volume, as described in “Installing the Oracle

Solaris OS” on page 51.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 43

Page 44

To Prepare to Use the BIOS Configuration Utility

Using the BIOS Configuration Utility (Legacy BIOS Booting) to Create a Bootable Drive (x86)

This section describes how to use the BIOS Configuration utility to set up a drive on an x86 system prior to installing an OS. You can then use the drive as your boot drive upon which to install the OS. This section contains the following topics:

■

“To Prepare to Use the BIOS Configuration Utility” on page 44

■

“To Create a RAID Volume With the BIOS Configuration Utility (x86)” on page 47

To Prepare to Use the BIOS Configuration Utility

From the Integrated Lights Out Manager (ILOM) software or Video Graphics Array (VGA) video port, access the system console.

Initiate a system boot.

During the boot process, the BIOS initialization banner lists information about the discovered SAS adapters and devices that are attached to the discovered HBAs in the system.

Upon seeing the prompt, Press Ctrl-C to start LSI Corp Configuration Utility..., immediately press Ctrl+C to access the LSI Corp Config Utility utility.

The LSI Corp Config Utility menu is displayed (see Figure 13, “LSI Corp Config Utility

Menu,” on page 45).

44 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 45

To Prepare to Use the BIOS Configuration Utility

FIGURE 13

LSI Corp Config Utility Menu

To change the boot options, use the arrow keys to navigate to the Boot Order field, and use the keys on your keyboard to change the values (see the following table).

Key Function

Insert Enables booting

Del Disables booting

Plus (+) Increases the numeric value in order to change the boot order

Minus (-) Decreases the numeric value in order to change the boot order

To change other options, use the arrow keys to navigate to the HBA that you want, and press Enter.

The Adapter Properties screen is displayed for the selected HBA (see Figure 14, “Adapter

Properties Screen,” on page 46).

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 45

Page 46

To Prepare to Use the BIOS Configuration Utility

FIGURE 14

Adapter Properties Screen

To view the devices and RAID volumes attached to the HBA, use the arrow keys to navigate to the SAS Topology field, and press Enter.

The SAS Topology screen is displayed (see Figure 15, “SAS Topology Screen,” on page

47).

46 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 47

To Create a RAID Volume With the BIOS Configuration Utility (x86)

FIGURE 15

SAS Topology Screen

You can now use the BIOS Configuration utility to create a RAID volume on the HBA.

To Create a RAID Volume With the BIOS Configuration Utility (x86)

Note - Do not perform the steps in this section if you want to install the OS on a non-RAID

volume. Instead, go directly to “To Select a Bootable Drive (x86)” on page 49.

From the Adapter Properties screen of the LSI Corp Config Utility utility, use the arrow keys to navigate to the RAID Properties field, and press Enter.

The Select New Volume Type screen is displayed (see Figure 16, “Select New Volume Type

Screen,” on page 48).

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 47

Page 48

To Create a RAID Volume With the BIOS Configuration Utility (x86)

FIGURE 16

Select New Volume Type Screen

Navigate to the type of volume that you want to create and press Enter.

Type C to create the volume, choose to Save the changes, and then exit the menu.

You are returned to the Adapter Properties screen, and have successfully created a RAID volume on which to install an OS.

Perform the steps in “Selecting a Bootable Drive (x86)” on page 48.

Selecting a Bootable Drive (x86)

This section describes how to select the bootable drive on which you want to install the OS on an x86 system. This section contains the following topic:

■

“To Select a Bootable Drive (x86)” on page 49

48 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 49

To Select a Bootable Drive (x86)

From the Adapter Properties screen of the LSI Corp Config Utility utility, navigate to the SAS Topology field, and press Enter.

The SAS Topology screen is displayed.

Navigate to the device that you want, and press Alt+B to select the device as the primary boot device.

If you want an alternate boot device, navigate to the device that you want, and press Alt+A.

Confirm the changes you have made, save the configuration, and then press Esc to exit the utility.

Note - Additional boot devices for the HBA might be present in the system BIOS as possible

disk selections. However, these devices are not guaranteed to be consistent through storage configuration changes.

Validate the label of the bootable drive that you created, by following the steps in

“Validating the Label of the HBA Drive” on page 49.

Validating the Label of the HBA Drive

This section describes how to verify that the physical drive or RAID volume you created for the HBA has a valid Oracle Solaris label, and therefore can be recognized by the OS. Sometimes, drives and RAID volumes need to be relabeled using the format command (in the case of SPARC systems) or the fdisk command (in the case of x86 systems) in order to be recognized.

To Verify That the Label of a RAID Volume Is Valid

Note - For your reference, this section provides an example procedure for a SPARC system

that runs the Oracle Solaris OS. For an x86 system that runs a supported OS, you would use the fdisk command for that OS to verify the label of a disk. For more information about labeling disks using the fdisk command, see the documentation for your OS.

Become the root user on the system, and issue the format command.

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 49

Page 50

To Verify That the Label of a RAID Volume Is Valid

# format Searching for disks...done c5t5000C5000B304CAFd0: configured with capacity of 136.71GB c5t5000C5000B305B4Fd0: configured with capacity of 136.71GB c5t5000CCA0002CF034d0: configured with capacity of 136.71GB c5t5000CCA000310014d0: configured with capacity of 136.71GB AVAILABLE DISK SELECTIONS:

0. c5t5000C5000B304CAFd0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000c5000b304caf

1. c5t5000C5000B305B4Fd0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000c5000b305b4f

2. c5t5000CCA0002CF034d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000cca0002cf034

3. c5t5000CCA000310014d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000cca000310014 Specify disk (enter its number):

When prompted, type the number of a disk drive that is attached to the newly installed HBA card, and press Enter.

0. c5t5000C5000B304CAFd0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000c5000b304caf

1. c5t5000C5000B305B4Fd0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000c5000b305b4f

2. c5t5000CCA0002CF034d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000cca0002cf034

3. c5t5000CCA000310014d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /scsi_vhci/disk@g5000cca000310014 AVAILABLE DISK SELECTIONS: Specify disk (enter its number): 2 selecting c5t5000CCA0002CF034d0 [disk formatted]

The Format menu is displayed.

If you see a Disk not labeled. Label it now? message, type y to label the selected disk.

50 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 51

Type q to exit the utility.

FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk fdisk - run the fdisk program repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision scsi - independent SCSI mode selects cache - enable, disable or query SCSI disk cache volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit format> q #

Installing the Oracle Solaris OS

Next Steps

If you are installing the HBA in a SPARC system, install the Oracle Solaris OS, as described in

“Installing the Oracle Solaris OS” on page 51.

If you are installing the HBA in an x86 system, install a supported OS (for a list of supported OSes, see “Operating System and Technology Requirements” on page 13. If you plan to install the Oracle Solaris OS on an x86 system, follow the instructions in “Installing the Oracle Solaris

OS” on page 51.

Installing the Oracle Solaris OS

You can install the Oracle Solaris 10 01/13 OS, at minimum, on the bootable drive that you created, as described in this chapter. Starting with the Oracle Solaris 10 01/13 OS, the driver required by the HBA is provided with the Oracle Solaris OS. This section contains the following topics:

Chapter 3 • Creating a Bootable Drive in a Preboot Environment 51

Page 52

To Prepare to Install the Oracle Solaris OS

■

“To Prepare to Install the Oracle Solaris OS” on page 52

■

“To Install the Oracle Solaris OS:” on page 52

To Prepare to Install the Oracle Solaris OS

Ensure that you have a bootable drive upon which to install the Oracle Solaris OS, as described in this chapter.

To Install the Oracle Solaris OS:

Obtain the Oracle Solaris 10 01/13 OS, at minimum, from the download site:

http://www.oracle.com/technetwork/server-storage/solaris10/overview/index.html

Perform a normal installation, as described in the Oracle Solaris 10 installation documentation.

Apply any patches that are specifically required for the system.

You can obtain these Oracle Solaris patches at:

http://support.oracle.com

Reboot the system.

# reboot

The system can now see, and boot from, the RAID volume on which you installed the Oracle Solaris OS.

Next Steps

Continue with the HBA installation, as described in “To Complete the Installation” on page 20.

52 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 53

♦ ♦ ♦ C H A P T E R 4

HBA Software Installation

After you have completed the hardware installation and powered on the system, follow the instructions presented in this chapter for your operating system to install the HBA driver and any other utilities required for the installation.

This chapter contains the following topics:

■

“Installing the Oracle Solaris Driver and Firmware” on page 53

■

“Installing the Linux Driver and Firmware” on page 54

■

“Installing the Windows Server Driver and Firmware” on page 55

■

“Installing the VMware Driver and Firmware” on page 55

■

“Installing the RAID Configuration Utility” on page 56

Installing the Oracle Solaris Driver and Firmware

The latest driver (mpt_sas) for this HBA is included as part of the Oracle Solaris 10 01/13 OS and the Oracle Solaris 11.1 OS. You can obtain the latest version of the Oracle Solaris OS at:

http://www.oracle.com/technetwork/server-storage/solaris10/overview/index.html

The HBA requires the the following patches and SRUs, at minimum, for the driver to work:

■

Oracle Solaris 10 01/13 (for the SPARC environment): patches 149175-02 and 14564804

■

Oracle Solaris 10 01/13 (for the x86 environment): patches 149176-02 and 45649-04

■

Oracle Solaris 11.1: SRU 7

You can obtain these Solaris patches at:

http://support.oracle.com

Chapter 4 • HBA Software Installation 53

Page 54

Installing the Linux Driver and Firmware

Firmware Updates

The Solaris firmware and boot code update for the HBA, along with any accompanying documentation, are available for download at:

http://www.lsi.com/sep/Pages/oracle/index.aspx

Installing the Linux Driver and Firmware

Consult the Oracle hardware platform document to determine which Linux releases are supported on your specific host platform.

The Linux driver required to run the HBA with the Linux OS is available for download at:

http://www.lsi.com/sep/Pages/oracle/index.aspx

To Install the Linux Driver

In a browser, go to http://www.lsi.com/sep/Pages/oracle/index.aspx.

Select the type and then model of the HBA that you want (SG(X)-SAS6-INT-Z).

Select and download the Linux driver that is supported by the Linux release (Red Hat Enterprise Linux, SuSE Linux Enterprise Server, or Oracle Enterprise Linux) on your hardware platform.

Select and download the corresponding Readme file for the Linux driver, and follow the instructions in the Readme file to complete the driver installation.

Firmware Updates

The Linux firmware and boot code update for the HBA, along with any accompanying documentation, are available for download at:

54 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 55

Installing the Windows Server Driver and Firmware

http://www.lsi.com/sep/Pages/oracle/index.aspx

Installing the Windows Server Driver and Firmware

Consult the Oracle hardware platform document to determine which Windows releases are supported on your specific host platform.

The Windows Server driver required to run the HBA is available for download at:

http://www.lsi.com/sep/Pages/oracle/index.aspx

To Install the Windows Driver

In a browser, go to http://www.lsi.com/sep/Pages/oracle/index.aspx.

Select the type and then model of the HBA that you want (SG(X)-SAS6-INT-Z).

Select and download the specific Windows driver that is supported by the Windows release on your hardware platform.

Select and download the corresponding Readme file for the Windows driver, and follow the instructions in the Readme file to complete the driver installation.

Firmware Updates

The Windows firmware and boot code update for the HBA, along with any accompanying documentation, are available for download at

http://www.lsi.com/sep/Pages/oracle/index.aspx

Installing the VMware Driver and Firmware

The HBA driver is included as part of the VMware ESX Server installation. The VMware ESX Server installation requires nothing from the user.

Chapter 4 • HBA Software Installation 55

Page 56

Installing the RAID Configuration Utility

The HBA can be configured for RAID 0, 1, and 10. Use the SAS2IRCU utility, a command-line interface utility, to create RAID volumes for the HBA.

This utility, and its associated documentation, is available for download at:

http://www.lsi.com/sep/Pages/oracle/index.aspx

56 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 57

♦ ♦ ♦ C H A P T E R 5

Activating Volumes

This chapter describes how to make the HBA recognize a newly connected RAID volume that was created prior to its connection with the HBA or that was previously connected to a different HBA.

This chapter contains the following sections:

■

“Overview of Volume Activation” on page 57

■

“Activating a Volume (SPARC)” on page 58

■

“Activating a Volume (x86)” on page 58

■

“Activating a Volume (From an OS)” on page 59

Overview of Volume Activation

When you connect a RAID volume to the HBA, and that volume was created outside of the HBA or was previously connected to a different HBA, the HBA considers this volume to be a foreign RAID volume. To protect data, the foreign RAID volume is unusable by the operating system or system boot loader until you manually activate it. You must manually activate a volume in the following situations:

■

You plan to move the physical disks that make up a hardware RAID volume from one system to another system with the HBA.

■

You are replacing an existing HBA that is managing hardware RAID volumes with a new HBA.

Based on your configuration, use the appropriate utility to manually activate a RAID volume:

■

If the HBA is installed in a SPARC System - Use the FCode utility. See “Activating a

Volume (SPARC)” on page 58.

■

If the HBA is installed in an x86 System - Use the BIOS Configuration utility. See

“Activating a Volume (x86)” on page 58.

Chapter 5 • Activating Volumes 57

Page 58

Activating a Volume (SPARC)

■

From an operating system (OS) - Use the SAS2IRCU utility. See “Activating a Volume

(From an OS)” on page 59.

Activating a Volume (SPARC)

Follow the procedure in this section to activate a SPARC volume.

To Activate a Volume (SPARC)

Select the HBA to which the foreign volume is connected, as described in “To

Prepare to Use the FCode Utility (SPARC)” on page 28.

List the active and foreign volumes by issuing the show-volumes command.

Issue the volume-number-of-foreign-volume activate-volume command.

The volume is now activated, and can be used by the HBA.

Activating a Volume (x86)

Follow the procedure in this section to activate an x86 volume.

To Activate a Volume (x86)

Enter the BIOS Configuration utility, as described in “To Prepare to Use the BIOS

Configuration Utility” on page 44.

Navigate to the HBA to which the foreign volume is connected and press Enter.

Navigate to the RAID Properties field and press Enter.

Navigate to View Existing Volume and press Enter.

Ensure that the appropriate foreign volume is displayed on the screen.

You can toggle between the two volumes by pressing Alt+N.

58 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 59

Navigate to Manage Volume and press Enter.

Navigate to Activate Volume and press Enter.

The volume is now activated, and can be used by the HBA.

Activating a Volume (From an OS)

Follow the procedure in this section to activate a volume.

To Activate a Volume (From an OS)

Go to the Oracle support area of the LSI web site (http://www.lsi.com/sep/

Pages/oracle/index.aspx), download the SAS2IRCU utility, and issue the sas2ircu

command, with no options, at the command-line or at a terminal window.

To display a synopsis of the SAS2IRCU utility command-line arguments, issue the sas2ircu 0 activate command.

Activating a Volume (From an OS)

To obtain the controller ID, issue the sas2ircu list command.

To obtain the volume ID, issue the sas2ircu controller-ID display command.

The volume is now activated, and can be used by the HBA.

Chapter 5 • Activating Volumes 59

Page 60

60 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 61

♦ ♦ ♦ C H A P T E R 6

Known Issues

This chapter provides supplementary and workaround information about the HBA. Specific bug identification numbers are provided for service personnel.

This chapter contains the following sections:

■

“MegaRAID Storage Manager GUI-Related Issues” on page 61

■

“Utility-Related Issues” on page 62

■

“Storage-Related Issues” on page 64

MegaRAID Storage Manager GUI-Related Issues

The section contains the following information:

■

“Cannot Hotplug the HBA Card Through the MSM GUI” on page 61

■

“Cannot Assign a Global Hot Spare Through the MSM GUI” on page 62

■

“Cannot Upgrade Firmware on the HBA Therough the MSM GUI” on page 62

Cannot Hotplug the HBA Card Through the MSM GUI

Bug 15700904

Issue: If the MegaRAID Storage Manager (MSM) software is installed on the system, and the

MSM software services are running, you cannot perform hotplug remove and insert operations on the HBA. When attempting to perform such an operation, a popup window is displayed stating that the HBA card is busy and that you must close the program that is accessing the card.

Workaround: Use the Task Manager application to stop the following MSM software services:

■

MSMFramework

Chapter 6 • Known Issues 61

Page 62

Utility-Related Issues

■

MegaMontiorSrv

After you have stopped these services, you can perform HBA card hotplug operations. You can restart the MSM software services after the hotplug operations are complete.

Cannot Assign a Global Hot Spare Through the MSM GUI

Bug 15762780

Issue: From the MegaRAID Storage Manager (MSM) graphical user interface (GUI), after

creating a drive using 2 hard disks, the option to create a global host spare from a third hard drive becomes inactive.

Workaround: Assigning global hot spares is not supported through the MSM GUI. Instead, use the SAS2IRCU utility to assign global hot spares.

Cannot Upgrade Firmware on the HBA Therough the MSM GUI

Bug 15664024

Issue: The firmware level on the HBA remains the same after using the MegaRAID Storage

Manager software to upgrade the firmware.

Workaround: Upgrading firmware through the MegaRAID Storage Manager software is not supported for this HBA. To upgrade firmware on the HBA, use the SAS2IRCU utility. You can obtain the SAS2IRCU utility from the Oracle support area of the LSI web site:

http://www.lsi.com/sep/Pages/oracle/index.aspx

Utility-Related Issues

This section contains the following information:

■

“Sun Storage 6 Gb SAS PCIe HBA, Internal is Not Displayed in the BIOS Setup Utility” on page 63

■

“A Hard Drive is Not Displayed in the BIOS Setup Utility” on page 63

■

“Non-Alphabetical Characters Are Displayed in RAID Volume Names” on page 63

62 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 63

Utility-Related Issues

■

“Cannot Delete a RAID Volume Using the SAS2IRCU Utility” on page 64

■

“There Is No FCode Utility Command for Creating a RAID 10 Volume” on page 64

Sun Storage 6 Gb SAS PCIe HBA, Internal is Not Displayed in the BIOS Setup Utility

Bug 15803027

Issue: If you have a Sun Storage 6 Gb SAS PCIe HBA, Internal and a Sun Storage 6 Gb SAS

PCIe HBA, External installed in a Sun Server X2-4 system, the Sun Storage 6 Gb SAS PCIe HBA, Internal might not be displayed in the BIOS Setup utility.

Workaround: The Sun Storage 6 Gb SAS PCIe HBA, Internal and Sun Storage 6 Gb SAS PCIe HBA, External must have the same level of firmware installed. If you encounter this issue, upgrade the firmware on the HBAs to be the latest firmware version. You can now see both HBAs in the BIOS Setup utility.

A Hard Drive is Not Displayed in the BIOS Setup Utility

Bug 15769403

Issue: After removing and reinserting a hard drive that is part of a RAID-1 virtual drive

configuration on the HBA, the hard drive is no longer displayed in the BIOS Setup utility.

Workaround: None. This is expected behaviour. To view the hard drive after reinsertion, reboot the system and enter the BIOS Setup utility. You can now view the hard drive.

Non-Alphabetical Characters Are Displayed in RAID Volume Names

Bug 15597943

Issue: In the LSI BIOS Configuration utility, non-alphabetical characters are occasionally

displayed in the volume names of RAID volumes. This occurs intermittently; subsequent reboots might cause the characters to go away, resulting in the correct volume names being displayed, or might cause the garbled characters to continue to be displayed. This is a cosmetic issue only. The volumes are fully functional and usable.

Chapter 6 • Known Issues 63

Page 64

Storage-Related Issues

Workaround: You can identify each volume in the LSI BIOS Configuration utility by reviewing the volume number or the constituent disks of the volume.

Cannot Delete a RAID Volume Using the SAS2IRCU Utility

Bug 15625274

Issue: There are no SAS2IRCU utility Help instructions on how to delete a RAID volume through

the SAS2IRCU utility.

Workaround: For information about how to delete a specific RAID volume using the SAS2IRCU utility, see the note in Step 6c of “To Complete the Installation” on page 20.

There Is No FCode Utility Command for Creating a RAID 10 Volume

Bug 15635981

Issue: The supported RAID types for this HBA are 0, 1, and 10. However, there is no FCode

command (in the SPARC Open Boot Prom (OBP) environment) that enables you to create a RAID 10 volume. Instead, there is a command that lets you create a RAID 1E volume (create- raid1e-volume command). When you use this command to create a volume, the SAS2IRCU utility displays this volume as a RAID 10 volume.

Workaround: To create a RAID 10 volume through the FCode utility, use the create-raid1e- volume command.

Storage-Related Issues

This section contains the following information:

■

“The Oracle Solaris Operating System Installation Hangs” on page 65

■

“The System Hangs After Deleting a RAID Volume” on page 65

■

“Pressing Ctrl+N Might Bypass Network Boot and HBA Option ROM Load” on page 65

64 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 65

Storage-Related Issues

■

“Blue Ready-to-Remove LED Does Not Illuminate After Issuing the cfgadm -c unconfigure Command” on page 66

■

“Only 24 Devices Are Displayed In The System BIOS Boot List” on page 68

The Oracle Solaris Operating System Installation Hangs

Bug 15761911

Issue: If you use the graphical user interface (GUI) mode to install the Oracle Solaris operating

system (OS), and you install the OS onto a volume configured on the HBA, the OS installation might hang during the “detecting locale” portion of the installation.

Workaround: Verify that the volume on which you plan to install the OS is not a resyncing RAID 1 or RAID 10 volume. To prevent hangs, ensure that the volume is in optimal mode, rather than resync mode, prior to installing the OS.

The System Hangs After Deleting a RAID Volume

Bug 15764098

Issue: If you delete a RAID volume configured on this HBA, and that volume is in resync

mode, the system in which the HBA is installed might hang.

Workaround: When you need to delete a RAID volume that is configured on the HBA, verfity that the volume is in optimal mode, not in resync mode. If the volume is resyncing, wait to delete the volume until after the resync process is complete

Pressing Ctrl+N Might Bypass Network Boot and HBA Option ROM Load

Bug 15601623

Issue: If you install the HBA in a Sun Fire X4170 M2 or Sun Fire X4270 M2 system, and you

press Ctrl+N on the serial console to initiate a network boot, the network boot might not be initiated, and the Option ROM for the HBA might not be loaded.

Workaround: Do one of the following:

Chapter 6 • Known Issues 65

Page 66

Determine the Physical Location, and Then Hot Plug, a Disk

■

Use the ILOM Remote Console and press F12 to initiate a network boot.

■

If using the serial console, press Ctrl+E to get to the BIOS boot device priority menu, and then move the desired PXE adapter (network boot device) to the top of the boot device priority list. The PXE adapter will then be used as the boot device.

■

Press Ctrl+N during, or after, the time the HBA Option ROM code is running. The Option ROM code is running when the following banner is displayed:

LSI Corporation MPT SAS2 BIOS.

Blue Ready-to-Remove LED Does Not Illuminate After Issuing the cfgadm -c unconfigure Command

Bug 15622936

Issue: If you need to replace a drive connected to the HBA on a system running the

Oracle Solaris OS, it is difficult to physically locate that drive after issuing the cfgadm -c unconfigure command. This is because the blue Ready-to-Remove LED is not illuminating on

the drive, as it is expected to do.

Workaround: To determine the physical location of the disk, and then to hot plug the disk, perform the procedure in this section.

Determine the Physical Location, and Then Hot Plug, a Disk

Run the format command on the disk that you want to physically locate in the chassis of the system.

In the following example, the disk that needs to be replaced is /dev/dsk/ c14t50010B90004BEF66d0.

# format c14t50010B90004BEF66d0 selecting c14t50010B90004BEF66d0 [disk formatted] FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk

66 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 67

Determine the Physical Location, and Then Hot Plug, a Disk

fdisk - run the fdisk program repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit format>

Issue the analyze format command.

format> analyze ANALYZE MENU: read - read only test (doesn't harm SunOS) refresh - read then write (doesn't harm data) test - pattern testing (doesn't harm data) write - write then read (corrupts data) compare - write, read, compare (corrupts data) purge - write, read, write (corrupts data) verify - write entire disk, then verify (corrupts data) print - display data buffer setup - set analysis parameters config - show analysis parameters !<cmd> - execute <cmd> , then return quit quit

Issue the read analyze command and type y at the prompt.

analyze> read Ready to analyze (won't harm SunOS). This takes a long time, but is interruptable with CTRL-C. Continue? ypass 0 

To find the physical drive slot in the chassis of the system, check the activity blinking LEDs on the drives.

The activity LED blink rate will be consistent on the drive that you want to replace.

If you are unable to determine the drive slot due to other drive activity blink rates, do the following:

Chapter 6 • Known Issues 67

Page 68

Determine the Physical Location, and Then Hot Plug, a Disk

Press Ctrl+Z at the command-line to suspend the analyze function.

Look at the drive slots and verify that the drive that you want has a solid activity LED on the drive (the LED is no longer blinking, but remains illuminated).

After you have found the drive slot that you want, run the fg command to resume the analyze function.

Type Ctrl+C at the command-line to interrupt the read test.

If you are unable to identify the drive, as described Step 4 and Step 5 in this procedure, do the following:

Take the system to single-user mode in order to quiesce all other system activity

Repeat Step 1 through Step 6.

Now that you have physically located the drive, issue the cfgadm -c unconfigure command to unconfigure the drive, and then remove the drive from the chassis.

Only 24 Devices Are Displayed In The System BIOS Boot List

Bug 15648283

Issue: If you install multiple HBA cards in an x86 system, the total number of devices

populated across all cards can be no more than 24. Additional devices will not be displayed in the system BIOS boot list.

Workaround: Use the BIOS Configuration utility to select which adapters are candidates for booting and which drives connected to those adapters you want designated as boot drives. This enables you to gaurantee which drives are consistently listed in the system BIOS boot list.

68 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 69

♦ ♦ ♦ A P P E N D I X A

HBA Specifications

The appendix contains the specifications for the HBA. This appendix contains the following topics:

■

“Physical Dimensions” on page 69

■

“PCI Performance” on page 69

■

“SAS Port Bandwidths” on page 70

■

“HBA Card Layout” on page 71

■

“Environmental Specifications” on page 72

Physical Dimensions

The HBA board is a 6.6-in. x 2.713-in., low-profile board. The component height on the top and bottom of the board follows the PCI Express specifications.

PCI Performance

The PCI Express features of the HBA include the following:

■

Provides 4 or 8 PCI Express PHYs

■

Supports a single-PHY (one lane) link transfer rate up to 6.0 Gb/s in each direction

■

Supports link widths of x8, x4, and x1

■

Automatically downshifts to a x4-link width if plugged into a x8 connector that is wired as a x4 connector

■

Provides a scalable interface:

■

Single-lane aggregate bandwidth of up to 0.5 GB/s (500 MB/s)

■

Quad-lane aggregate bandwidth of up to 2.0 GB/s (2000 MB/s)

■

Eight-lane aggregate bandwidth of up to 4.0 GB/s (4000 MB/s)

Appendix A • HBA Specifications 69

Page 70

SAS Port Bandwidths

■

Supports serial, point-to-point interconnections between devices:

■

Reduces the electrical load of the connection

■

Enables higher transmission and reception frequencies

■

Supports lane reversal and polarity inversion

■

Supports PCI Express hot plugging

■

Supports power management

■

Supports PCI Power Management 1.2:

■

Supports active-state power management (ASPM), including the L0, L0s, L1 states, by placing links in a power-savings mode when there is no link activity

■

Contains a replay buffer that preserves a copy of the data for retransmission in case a cyclic redundancy check (CRC) error occurs

■

Supports the PCI Express advanced error-reporting capabilities

■

Uses a packetized and layered architecture

■

Achieves high bandwidth per pin with low overhead and low latency

■

Provides software compatibility with PCI and PCI-X software:

■

Leverages existing PCI device drivers

■

Supports the memory, I/O, and configuration address spaces

■

Supports memory read/write transactions, I/O read/write transactions, and configuration read/write transactions

■

Provides 4 KB of PCI configuration address space per device

■

Supports posted and nonposted transactions

■

Provides quality-of-service (QOS) link configuration and arbitration policies

■

Supports Traffic Class 0 and one virtual channel

■

Supports message-signaled interrupts (both MSI and MSI-X) as well as INTx interrupt signaling for legacy PCI support

■

Supports end-to-end CRC (ECRC) and advanced error reporting

SAS Port Bandwidths

The HBA supports narrow and wide ports, as described in the following table.

TABLE 3

Half Duplex Full Duplex

Narrow Port (1 Lane), 600 MB/s Narrow Port (1 Lane), 1200 MB/s

Wide Port (2 Lanes), 1200 MB/s Wide Port (2 Lanes), 2400 MB/s

Wide Port (4 Lanes), 2400 MB/s Wide Port (4 Lanes), 4800 MB/s

70 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

6-Gb/s SAS Bandwidths

Page 71

HBA Card Layout

Figure 17, “HBA Board Layout,” on page 71 shows the card layout of the HBA.

HBA Card Layout

FIGURE 17

HBA Board Layout

■

Connectors

The different HBA connectors are listed in the following table (see Figure 17, “HBA Board

Layout,” on page 71 for connector locations).

J1: PCI Express x8-lane board edge connector

J3: UART connection

J7, J8: SFF-8087 mini-SAS, internal, right-angle connector

J6: 4-pin, right angle, 0.1-in. pitch, pin header for driving external activity LED

Appendix A • HBA Specifications 71

Page 72

Environmental Specifications

TABLE 4

Connector Description

PCI Express Connector (J1) The HBA supports an x8 interface. The PCI Express connection is through the edge

UART Connector (J3) Debug port requiring a special cable and support to gather detailed IOC status.

SAS/SATA Connectors (J7 and J8) The HBA supports SAS connections through connectors J7 and J8. These connectors are

Activity LED Header (J6) 4-pin, right-angle, 0.1-in. pitch, pin header for driving external activity LEDs

HBA Connectors

connector, J1, which provides connections on both the top (J1B) and bottom (J1A) of the board. The signal definitions and pin numbers conform to the PCI Express specifications.

SFF-8087 mini-SAS, internal, right-angle connectors.

Table 5, “UART Connections,” on page 72 lists the UART connections and their functions.

TABLE 5

UART Connections

Pin Function

1 UART0_TX

2 Gnd

3 UART0_RX

4 3.3 V

Table 6, “LED Header,” on page 72 details the LED headers and their functions.

TABLE 6

LED Header

Pin Function

1 3.3 V

2 Port 0

3 Port 1

4 3.3 V

Environmental Specifications

The HBA environmental requirements are listed in Table 7, “HBA Environmental

Specifications,” on page 72.

TABLE 7

Specification Operating Non-Operating

Temperature ■ +10˚C to +60˚C without battery backup unit ■ -30˚C to +80˚C without battery backup unit

72 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

HBA Environmental Specifications

• May 2017

Page 73

Environmental Specifications

Specification Operating Non-Operating

■ +10˚C to +44.8˚C with iBBU battery backup ■ 0˚C to +45˚C with iBBU battery backup

Humidity 5% to 90% RH, non-condensing, 40˚C max, 27˚C max

93% RH, non-condensing, 40˚C max, 120 hours

wet bulb, 16 hour dwells at extreme

Altitude 3200m at 40˚C, 4 hour dwell 12,200m at 0˚C, 4 hour dwell

Vibration 0.25G in all axes swept for 5-500-5 Hz, 5 sweeps in all

at 1 octave/min

1.2G in all axes swept for 5-500-5 Hz, 5 sweeps in all at 1 octave/min

Shock 5.5G, 11 ms half-sine, 10 shocks in x-, y-, and z-axes 33G, 11 ms half-sine, 3 shocks in x-, y-, and z-axes

Airflow At least 200 linear feet per minute (LFPM) At least 200 linear feet per minute (LFPM)

Appendix A • HBA Specifications 73

Page 74

74 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 75

Glossary

A, B

BIOS Acronym for Basic Input/Output System. Software that provides basic read/write capability.

Usually kept as firmware (ROM-based). The system BIOS on the motherboard of a computer boots and controls the system. The BIOS on your host adapter acts as an extension of the system BIOS.

configuration Refers to the way a computer is set up, the combined hardware components (computer,

monitor, keyboard, and peripheral devices) that comprise a computer system, or the software settings that enable the hardware components to communicate with each other.

device driver A program that enables a microprocessor (through the operating system) to direct the operation

of a peripheral device.

domain validation

drive group A group of physical drives that combines the storage space on the drives into a single segment

A software procedure in which a host queries a device to determine its ability to communicate at the negotiated data rate.

of storage space. A hot-spare drive does not actively participate in a drive group.

EEPROM Acronym for electronically erasable programmable read-only memory. It is a memory chip that

typically stores configuration information, as it provides stable storage for long periods without electricity and can be reprogrammed. Refer to NVRAM.

Glossary 75

Page 76

external SAS device

A SAS device installed outside the computer cabinet. These devices are connected using specific types of shielded cables.

Fusion-MPT architecture

An acronym for Fusion-Message Passing Technology architecture. Fusion-MPT consists of several main elements: Fusion-MPT firmware, the Fibre Channel and SCSI hardware, and the operating system level drivers that support these architectures. Fusion-MPT architecture offers a single binary, operating system driver that supports both Fibre Channel and SCSI devices.

G, H

host The computer system in which a RAID adapter is installed. It uses the RAID adapter to transfer

information to and from devices attached to the SCSI bus.

host adapter board

host bus adapter

hot spare An idle, powered-on, standby drive that is ready for immediate use in case of drive failure. A

A circuit board or integrated circuit that provides a device connection to the computer system.

A piece of hardware that connects a host to network and storage devices.

hot spare does not contain any user data. A hot spare can be dedicated to a single redundant array or it can be part of the global hot‐spare pool for all arrays managed by the adapter.

When a drive fails, the adapter firmware automatically replaces and rebuilds the data from the failed drive to the hot spare. Data can be rebuilt only from virtual drives with redundancy (RAID levels 1, 5, 6, 10, 50, and 60; not RAID level 0), and the hot spare must have sufficient capacity.

internal SAS device

A SAS device installed inside the computer cabinet. These devices are connected using a shielded cable.

J, K, L, M

main memory The part of computer memory that is directly accessible by the CPU (usually synonymous with

RAM).

76 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 77

NVRAM Acronym for nonvolatile random access memory. An EEPROM (electronically erasable read-

only memory) chip that stores configuration information. Refer to EEPROM.

O, P

PCI Acronym for peripheral component interconnect. A high-performance, local bus specification

that enables the connection of devices directly to computer memory. The PCI Local Bus enables transparent upgrades from 32-bit data path at 33 MHz to 64-bit data path at 33 MHz, and from 32‐bit data path at 66 MHz to 64-bit data path at 66 MHz.

PCI Express Acronym for Peripheral Component Interconnect Express. A high‐ performance, local bus

specification that enables the connection of devices directly to computer memory. PCI Express is a two-way, serial connection that transfers data on two pairs of point-to-point data lines. PCI Express goes beyond the PCI specification in that it is intended as a unifying I/O architecture for various systems: desktops, workstations, mobile, server, communications, and embedded devices.

SAS

peripheral devices

PHY The interface required to transmit and receive data packets transferred across the serial bus.

A piece of hardware (such as a video monitor, drive, printer, or CD‐ROM) used with a computer and under the control of the computer. SCSI peripherals are controlled through a MegaRAID SAS RAID controller (host adapter).

Each PHY can form one side of the physical link in a connection with a PHY on a different SATA device. The physical link contains four wires that form two differential signal pairs. One differential pair transmits signals, while the other differential pair receives signals. Both differential pairs operate simultaneously and enable concurrent data transmission in both the receive and the transmit directions.

Q, R, S

SAS Acronym for Serial Attached SCSI. A serial, point-to-point, enterprise‐level device

interface that leverages the proven SCSI protocol set. The SAS interface provides improved performance, simplified cabling, smaller connections, lower pin count, and lower power requirements when compared to parallel SCSI. SAS adapters leverage a common electrical and physical connection interface that is compatible with Serial ATA. The SAS adapters support the ANSI Serial Attached SCSI Standard, Version 2.0. In addition, the adapter supports the Serial ATA II (SATA II) protocol defined by the Serial ATA Specification, Version 1.0a. Supporting both the SAS interface and the SATA II interface, the SAS adapter is a versatile

Glossary 77

Page 78

SAS device

adapter that provides the backbone of both server and high-end workstation environments. Each port on the SAS RAID adapter supports SAS devices, SATA II devices, or both.

SAS device Any device that conforms to the SAS standard and is attached to the SAS bus by a SAS cable.

This includes SAS RAID adapters (host adapters) and SAS peripherals.

SATA Acronym for Serial Advanced Technology Attachment. A physical storage interface standard,

SATA is a serial link that provides point-to-point connections between devices. The thinner serial cables enable better airflow within the system and permit smaller chassis designs.

SMP Acronym for Serial Management Protocol. SMP communicates topology management

information directly with an attached SAS expander device. Each PHY on the adapter can function as an SMP initiator.

spanning A method for combining multiple drives into a single logical drive. If you want to have all of

the drive capacity in one drive group, you can span (merge) the drives so that the operating system sees just one large drive. For more information, refer to the MegaRAID SAS Software User's Guide, located at: http://www.lsi.com/sep/Pages/oracle/index.aspx.

SSP Acronym for Serial SCSI Protocol. SSP enables communication with other SAS devices. Each

PHY on the SAS adapter can function as an SSP initiator or SSP target.

STP Acronym for Serial Tunneling Protocol. STP enables communication with a SATA II device

through an attached expander. Each PHY on the SAS adapter can function as an STP initiator.

stripe size The total drive space consumed by a stripe not including a parity drive. For example, consider

a stripe that contains 64 Kbytes of drive space and has 16 Kbytes of data residing on each drive in the stripe. In this case, the stripe size is 64 Kbytes and the stripe element size is 16 Kbytes. The stripe depth is four (four drives in the stripe). You can specify stripe sizes of 8 Kbytes, 16 Kbytes, 32 Kbytes, 64 Kbytes, 128 Kbytes, 256 Kbytes, 512 Kbytes, or 1 Mbyte for each logical drive.

A larger stripe size produces improved read performance, especially if most of the reads are sequential. For mostly random reads, select a smaller stripe size.

striping Drive striping writes data across two or more drives. Each stripe spans two or more drives but

consumes only a portion of each drive. Each drive, therefore, may have several stripes. The amount of space consumed by a stripe is the same on each drive that is included in the stripe. The portion of a stripe that resides on a single drive is a stripe element. Striping by itself does not provide data redundancy; striping in combination with parity provides data redundancy.

T, U, V, W, X, Y, Z

virtual drive A storage unit created by a RAID controller from one or more drives. Although a virtual

drive may be created from several drives, it is seen by the operating system as a single drive.

78 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017

Page 79

virtual drive

Depending on the RAID level used, the virtual drive can retain redundant data in case of a drive failure.

Glossary 79

Page 80

80 Sun Storage 6 Gb SAS PCIe HBA, Internal Installation Guide For HBA Models SGX-SAS6-INT-Z and SG-SAS6-INT-Z

• May 2017