1. Manuals
  2. Brands
  3. Oracle Manuals
  4. Control Unit
  5. SAS-1
  6. Upgrade manual

Oracle SAS-1 Upgrade Manual

Compatibility upgrade for the sun blade 6000 modular system
Hide thumbs
Table of Contents

Advertisement

Quick Links

SAS-1/SAS-2 Compatibility Upgrade Guide
For the Sun Blade 6000 Modular System
Part No.: E21704-01
March 2011, Revision A

Advertisement

Table of Contents
loading

Related Manuals for Oracle SAS-1

Summary of Contents for Oracle SAS-1

  • Page 1 SAS-1/SAS-2 Compatibility Upgrade Guide For the Sun Blade 6000 Modular System Part No.: E21704-01 March 2011, Revision A...
  • Page 2 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. 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.

  • Page 3: Table Of Contents

    Overview 1 System Requirements for the SAS-1/SAS-2 Compatibility Upgrade 2 List of SAS-1 Server Modules That Are Compatible With SAS-2 Upgrade 3 Upgrading Disk Module and SAS-NEM Expander Firmware 4 Obtain the Latest Disk Module and SAS-NEM Expander Firmware for SAS-...
  • Page 4 ▼ Save a Snapshot of Your Host Bus Adapter Persistent Mappings 21 ▼ Restore a Snapshot of Your Host Bus Adapter Persistent Mappings 25 Index 29 Book Title without trademarks, or an abbreviated book title • March 2011...

  • Page 5: Using This Documentation

    Using This Documentation This document describes how to upgrade SAS-1 Network Express Modules (NEMs) and disk modules in Sun Blade 6000 Modular System from Oracle to allow SAS- 1/SAS-2 device coexistence. Related Documentation For the most up-to-date information about your server, refer to its documentation set located at (http://www.oracle.com/technetwork/documentation/index.html)
  • Page 6 Book Title without trademarks, or an abbreviated book title • March 2011...

  • Page 7: Sas-1/Sas-2 Compatibility Upgrade Instructions

    This document provides information on compatibility requirements for a server module with a SAS-2 RAID Expansion Module (REM) in a Sun Blade 6000 Modular System chassis that has SAS-1 Network Express Modules (NEMs), or SAS-1 NEMs and Sun Blade 6000 Disk Modules (which are SAS-1 devices).

  • Page 8: System Requirements For The Sas-1/Sas-2 Compatibility Upgrade

    To ensure optimal system performance and avoid the potential for a system hang, you need to upgrade the SAS expander firmware of all SAS-1 NEMs and Sun Blade 6000 Disk Modules in the chassis to the latest available firmware update that supports SAS-1/SAS-2 coexistence.

  • Page 9: List Of Sas-1 Server Modules That Are Compatible With Sas-2 Upgrade

    SAS-1 REM HBA that you can use to perform the SAS-1/SAS-2 compatibility upgrade. Since the upgrade to the affected SAS-1 devices (NEMs and disk modules) must be done through the SAS-1 bus, the server module(s) at which the upgrade will be performed must have one of the supported HBAs.

  • Page 10: Upgrading Disk Module And Sas-Nem Expander Firmware

    6000 Disk Modules before attempting to install your SAS-2 server module into the chassis. The upgrade can only be performed from server modules in the chassis and only from server modules with a supported SAS-1 REM or on-board LSI controller chip.

  • Page 11: Obtain The Latest Disk Module And Sas-Nem Expander Firmware For Sas-1/Sas-2 Coexistence

    Expander Firmware for SAS-1/SAS-2 Coexistence To support SAS-1/SAS-2 coexistence, SAS expanders for both the Sun Blade 6000 Disk Modules and SAS-1 NEMs must be at firmware version 5.04.03, at a minimum. You need to download the latest available firmware update for your platform.

  • Page 12: Obtain The Firmware Update Utility To Deploy The Required Expander Firmware

    SAS-1 NEM and disk module that TABLE 1-3 requires a firmware upgrade. SAS-1 NEM and Disk Module Download Image Names TABLE 1-3 SAS-1 NEM or Disk Module Download Image Names Sun Blade 6000 Disk Module Software 2.1 (B18-AA) •...

  • Page 13: Upgrade Disk Module And Sas-Nem Firmware Using The Fwupdate Utility

    ■ appropriate Sun Blade 6000 Disk Module software package from the Oracle download site to each server module equipped with a SAS-1 REM that is slot- paired with a Sun Blade 6000 Disk Module. See “Obtain the Latest Disk Module and SAS-NEM Expander Firmware for SAS-1/SAS-2 Coexistence”...
  • Page 14 Note – You must be logged in with root permission level to run fwupdate commands on Unix-based platforms, or Administrator permission level for Windows platforms. These instructions can be used on servers running Oracle Solaris, Linux, or Windows. 2. Change directories to where the fwupdate tool is located.
  • Page 15 The following expander components must be upgraded: Network Express Module (NEM) expanders: ■ The expander manufacturing image ■ The expander firmware ■ Disk module expanders (both Master and Slave): ■ The expander manufacturing image ■ The expander firmware ■ Chapter 1 SAS-1/SAS-2 Compatibility Upgrade Instructions...
  • Page 16 (disk module expanders first, then NEM expanders). 4. Upgrade the expander firmware of the SAS-1 disk module or NEM as follows: a. Rename the manufacturing image from /path/mfgImageCust03x.5.04.03.bin to mfgImageCust03x.bin.
  • Page 17 If you see an “Upgrade succeeded, but is not yet active” message, it can be safely ignored. d. If the chassis has two SAS-1 NEMs, repeat the upgrade process described in Step b Step c for the second NEM.
  • Page 18 b. Upgrade the manufacturing image by entering: fwupdate update expander-manufacturing-image -n c0x0 -f /path/mfgImageCust03x.bin Where c0x0 is the ID for the target NEM expander, and path is the directory path to where the image file is located, and x is determined by the name of the manufacturing image file for the specific disk module expander being upgraded (see TABLE 1-3...
  • Page 19 -> stop -f /CH -> start /CH 7. When done, check that all host viewable SAS expanders are at the supported version for SAS-1/SAS-2 coexistence (5.04.03) by entering the command: fwupdate list all Example output might look like this: CONTROLLER c0...
  • Page 20 SAS-1 disk modules in the chassis have had their expanders upgraded. 10. If your SAS-1 NEMs have an ILOM service processor, you might also need to upgrade its ILOM firmware to achieve a supported firmware level that is matched to the new expander firmware.

  • Page 21: Using The Lsiutil Software

    A P P E N D I X Using the lsiutil Software Some procedures in this manual require the use of a software program called lsiutil. This appendix provides information on where to obtain the software and how to use it. Caution –...

  • Page 22: Installing Lsiutil

    Installing lsiutil Download lsiutil and unzip it in a temporary directory. It will create operating system-specific subdirectories. If you are running lsiutil on a SPARC blade, use the Solaris subdirectory. Otherwise, use the Solaris x86 subdirectory. ▼ Using lsiutil From the Command Line Several of the procedures in this appendix use the lsiutil software at the command line.
  • Page 23 2. If you have not done so already, change the permissions (read and execute access) on the lsiutil file by entering the following command: # chmod 755 lsiutil 3. Start lsiutil by entering the command: # ./lsiutil The opening screen appears. 4.
  • Page 24 Tip – You do not have to see a command to enter it. If you know its number, just enter it. Alternatively, you can choose to see the entire menu if you want to, as shown in Step 4. 5. Enter p to enable paged mode, or e to enable expert mode. The complete menu appears in expert mode.
  • Page 25 Each time you press Enter you will see a new page of menu items until you reach the end. Appendix a Using the lsiutil Software...

  • Page 26: Why Save Lsi Host Bus Adapter Persistent Mappings

    Why Save LSI Host Bus Adapter Persistent Mappings? Replacing a failed LSI host bus adapter on a server blade running the Solaris OS can lead to significant downtime if your replacement adapter does not know how the old adapter was addressing the disks in its server blade and in the disk blade. Among other problems, your system will not know where your boot drive is located.

  • Page 27: Saving And Restoring A Persistence Map

    Saving and Restoring a Persistence Map You can use lsiutil to both save and restore a snapshot of your persistence mapping. ▼ Save a Snapshot of Your Host Bus Adapter Persistent Mappings 1. Run lsiutil in interactive mode. 2. Type 1 and press Enter. The basic (incomplete) interactive menu opens.
  • Page 28 Tip – You cannot see all the commands in the menu, but you can enter any command number if you know what it is. In this case you want to open the Persistence menu. This is done with command 15. 3.
  • Page 29 4. Type 7 and press Enter. You are prompted for the name of the file where you want to store the host bus adapter persistent mappings snapshot. Note – If you expect to boot from DOS when you restore the persistent mappings snapshot, you must restrict the file name to 8 characters.
  • Page 30 The file is saved to the current directory. lsiutil confirms this by displaying a statement of the number of persistent entries saved. 6. Type 0 (zero) and press Enter three times to exit lsiutil. Book Title without trademarks, or an abbreviated book title • March 2011...
  • Page 31 Caution – You must save the persistence table snapshot to external media as you will not be able to reinstall it from a local disk if your LSI host bus adapter fails. You must have a snapshot for every server blade in the chassis. Label them carefully. ▼...
  • Page 32 3. Type 1 and press Enter. The basic (incomplete) interactive menu opens. Tip – You cannot see all the commands in the menu, but you can enter any command number if you know what it is. In our case we want to open the Persistence menu.
  • Page 33 5. Type 10 and press Enter. This clears any persistence map that is present in the host bus adapter. 6. Type 8 and press Enter. You are prompted for the name of a persistent mappings snapshot file to load. Type the name of the snapshot file. For example, HBA33_persistence_file. 7.
  • Page 34 8. Type 0 (zero) and press Enter three times to exit lsiutil. Note – The adapter persistent mappings snapshot file you just loaded is still valid. Make sure that you save a copy of it on external media. Book Title without trademarks, or an abbreviated book title • March 2011...
  • Page 35 Index LSI host bus adapters restoring a snapshot of your persistent mappings, 25 saving a snapshot of your persistent mappings, 21 why save a snapshot of your persistent mappings, 20 lsiutil installing, 16 using from the command-line, 16 using the interactive menus, 16 where to obtain the software, 15 persistent mappings restoring a snapshot for your LSI host bus...
  • Page 36 Book Title without trademarks, or an abbreviated book title • March 2011...

This manual is also suitable for:

Sas-2

Table of Contents