SL500 - SAS Support for SL500 Library With 14.32 Microcode

Asset ID:	1-71-1335840.1
Update Date:	2011-07-26
Keywords:

Solution Type Technical Instruction Sure

Solution 1335840.1 : SL500 - SAS Support for SL500 Library With 14.32 Microcode

Applies to:

Sun StorageTek SL500 Modular Library System - Version: Not Applicable and later [Release: N/A and later ]
HP LTO5 Tape Drive - Version: Not Applicable and later [Release: N/A and later]
Information in this document applies to any platform.

Goal

SAS (Serial Attached SCSI) Support and ADI Bridging for SL500 Library.

Solution

Following is information on SAS in the SL500 library:

-New SL500 firmware to support SAS.
     Library code at 14.32
     SLConsole code at 5.25
     HP LTO5 full height SAS drive with X3AS or later code.
     No Fibre Channel or SCSI interface card installed in the SL500

-SAS Support requires a new SL500 (bridged base) Base Module/Unit.
DEMs and CEMs will work with either the old or new Base Module/Unit without any changes required.

-New Base Module/Unit uses ADI (Automated Drive Interface).
Instead of being controlled by a library interface card, the library is managed through an HP LTO-5 FC or SAS tape drive.

Overview of ADI Bridging
- Automation Drive Interface (ADI) is the communication path that the library uses to talk to the drive. Typically the library uses this path to get drive status, configure the drive, and do rewind/unload commands to the drive.
- ADI bridging is the use of this communication path for the drive to receive the SCSI commands that are intended for the library over the data path of the drive and then the drive will present those commands to the library over the ADI communication path.
- The library commands are sent to LUN1 of the drive’s SAS WWN and LUN0 is where the drive will receive it’s commands. This is how the drive is able to distinguish the commands that are meant for the library and the commands that are meant for the drive.
- ADI bridging takes away the need for a separate control path interface
card for the library.

Overview of ADI Bridging
-Automation Drive Interface (ADI) is the communication path that the library uses to talk to the drive. Typically the library uses this path to get drive status, configure the drive, and do rewind/unload commands to the drive.
-ADI bridging is the use of this communication path for the drive to receive the SCSI commands that are intended for the library over the data path of the drive and then the drive will present those commands to the library over the ADI communication path.
-The library commands are sent to LUN1 of the drive’s SAS WWN and LUN0 is where the drive will receive it’s commands. This is how the drive is able to distinguish the commands that are meant for the library and the commands that are meant for the drive.
-ADI bridging takes away the need for a separate control path interface card for the library.

To Configure the new SL500 with Bridged Library Control
Start with Interface for Base Module/Unit:
-Choose FC or SAS
-For SAS: SAS (Bridge Base) Module/Unit
     (Part number: 7100273)
-For Drives, HP LTO-5 is the only SAS drive supported.

Part Numbers:
-HP LTO-5 SAS: 7100278
-HP LTO-5 FC: LTO5-HPFC-D-SL500Z
-PTO SAS Drive PN: 7100968

SAS Cabling
A SAS cable will need to be ordered for each drive.
-Oracle offers 2 choices: 1x1 cable (supports 1 drive) and a 2x1 (cable that supports 2 drives with 1 cable.)
-Part Numbers:
      1x1 cable: 7100276
      2x1 cable: 7100274

Note: Due to Solaris Technical Issues:
1x1 cable is recommended for use in Solaris Environments.
2x1 cable is recommended for use in Windows and Linox Environments.

Attachments

This solution has no attachment