Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1373028.1
Update Date:2012-06-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  1373028.1 :   SL500/SL24/SL48 - SAS ADI Bridge Issue in Solaris with NetBackup  


Related Items
  • HP LTO5 Tape Drive
  •  
  • Sun StorageTek SL500 Modular Library System
  •  
  • Sun StorageTek SL48 Tape Library
  •  
  • Sun StorageTek SL24 Tape Autoloader
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL500 Library
  •  




In this Document
Symptoms
Cause
Solution


Applies to:

Sun StorageTek SL500 Modular Library System - Version Not Applicable and later
Sun StorageTek SL24 Tape Autoloader - Version Not Applicable and later
Sun StorageTek SL48 Tape Library - Version Not Applicable and later
HP LTO5 Tape Drive - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

In an Oracle Solaris environment running NetBackup and SL24/SL48/SL500 ADI Bridging with multiple SAS drives, 1 drive is not configured. NetBackup’s sg driver fails to build any device assigned target ID 7.

Issue :
If a configuration has multiple tape drives with a drive on target ID 7

let63:/> cfgadm –al

c14::rmt/0 tape connected configured unknown
c14::rmt/1 tape connected configured unknown
c14::rmt/2 tape connected configured unknown
c14::rmt/3 tape connected configured unknown
c14::rmt/4 tape connected configured unknown
c14::rmt/5 tape connected configured unknown
c14::rmt/6 tape connected configured unknown
c14::rmt/7 tape connected configured unknown
c14::scsi/changer/c14t500104F med-changer connected configured unknown

Netbackup will fail to build device on ID7 as seen in sgscan below:

let63:/usr/openv/volmgr/bin> ./sgscan

/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0): "SEAGATE ST914602SSUN146G"
/dev/sg/c0t0l1: Changer: "STK SL500"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c1t1d0): "SEAGATE ST914602SSUN146G"
/dev/sg/c0t2l0: Tape (/dev/rmt/2): "HP Ultrium 5-SCSI"
/dev/sg/c0t3l0: Tape (/dev/rmt/3): "HP Ultrium 5-SCSI"
/dev/sg/c0t4l0: Tape (/dev/rmt/4): "HP Ultrium 5-SCSI"
/dev/sg/c0t5l0: Tape (/dev/rmt/5): "HP Ultrium 5-SCSI"
/dev/sg/c0t6l0: Tape (/dev/rmt/6): "HP Ultrium 5-SCSI"
/dev/sg/c1t0l0: Tape (/dev/rmt/0): "HP Ultrium 5-SCSI"
/dev/sg/c1t1l0: Tape (/dev/rmt/1): "HP Ultrium 5-SCSI"

Cause

Drive not configured correctly.

Solution

General information on device configuration can be found in the Symantec NetBackup Device Configurations Guide. Here is a link to the document.
http://www.symantec.com/business/support/index?page=content&id=DOC3656

Steps to Follow:
1. After invoking sg.build script: /usr/openv/volmgr/bin/sg.build all –mt target –ml lun

2. Edit the sg.conf file under /usr/openv/volmgr/bin/driver/ and add the following lines:

name="sg" class="scsi" target=7 lun=0;
name="sg" class="scsi" target=7 lun=1;

3. Edit the sg.links file under /usr/openv/volmgr/bin/driver/ and add the following lines:

type=ddi_pseudo;name=sg;addr=7,0; sg/c\N0t7l0
type=ddi_pseudo;name=sg;addr=7,1; sg/c\N0t7l1

4. Install the new sg driver configuration by invoking the following two commands:

/usr/bin/rm –f /kernel/drv/sg.conf
/usr/openv/volmgr/bin/driver/sg.install

5. Invoking sgscan now shows the device on target ID 7, /dev/rmt/7:

let63:/usr/openv/volmgr/bin> ./sgscan

/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0): "SEAGATE ST914602SSUN146G"
/dev/sg/c0t0l1: Changer: "STK SL500"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c1t1d0): "SEAGATE ST914602SSUN146G"
/dev/sg/c0t2l0: Tape (/dev/rmt/2): "HP Ultrium 5-SCSI"
/dev/sg/c0t3l0: Tape (/dev/rmt/3): "HP Ultrium 5-SCSI"
/dev/sg/c0t4l0: Tape (/dev/rmt/4): "HP Ultrium 5-SCSI"
/dev/sg/c0t5l0: Tape (/dev/rmt/5): "HP Ultrium 5-SCSI"
/dev/sg/c0t6l0: Tape (/dev/rmt/6): "HP Ultrium 5-SCSI"
/dev/sg/c0t7l0: Tape (/dev/rmt/7): "HP Ultrium 5-SCSI"
/dev/sg/c1t0l0: Tape (/dev/rmt/0): "HP Ultrium 5-SCSI"
/dev/sg/c1t1l0: Tape (/dev/rmt/1): "HP Ultrium 5-SCSI"

Note:

This issue only applies to SAS-1.  SAS-2 on Solaris does not work with NBU: Document 1020986.1

The issue is a Netbackup problem.


Provided by Hung Lieu


Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback