IBM LTO4 Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: OEM Drive and Library
 

In this Document

Symptoms

Cause

Solution

Applies to:

Symptoms

Card is causing SCSI errors when attached to the Tape unit ( IBM   ULT3580-HH4      BBNF )
When tape unit disconnected errors stop.
Jul 12 16:37:27 Reg10svr1001 scsi: [ID 107833 kern.warning] WARNING: /pci@400/pci@2/pci@0/pci@8/LSI,sas@0 (mpt_sas2):
Jul 12 16:37:27 Reg10svr1001    unknown ioc_status = 0
Jul 12 16:37:27 Reg10svr1001 scsi: [ID 107833 kern.notice]      scsi_state = 0, transfer count = 0, scsi_status = 0
Jul 12 16:37:27 Reg10svr1001 genunix: [ID 892980 kern.warning] WARNING: Page83 data not standards compliant IBM      ULT3580-HH4      BBNF
Jul 12 16:37:27 Reg10svr1001 scsi: [ID 243001 kern.warning] WARNING: /pci@400/pci@2/pci@0/pci@8/LSI,sas@0 (mpt_sas2):
Jul 12 16:37:27 Reg10svr1001    Encode devid failed for path target:9, lun:0
Jul 12 16:37:27 Reg10svr1001 scsi: [ID 107833 kern.warning] WARNING: /pci@400/pci@2/pci@0/pci@8/LSI,sas@0 (mpt_sas2):
Jul 12 16:37:27 Reg10svr1001    unknown ioc_status = 0
Jul 12 16:37:27 Reg10svr1001 scsi: [ID 107833 kern.notice]      scsi_state = 0, transfer count = 0, scsi_status = 0

Questions are:
1. Is this a supported configuration?
2. What and where? Customer is asking for firmware level required.
3. Are there any special drivers required for this card with a tape unit attached?
4. Are there any know issue's with the Erie card?

Cause

 Card is causing SCSI errors when attached to the Tape unit ( IBM ULT3580-HH4 BBNF )

Solution

The SAS2 HBA's are not supported with tape devices on Solaris at this time.

If the customer wants to use a SAS tape device on a Solaris machine they will need to use the SAS1 Pandora card.

There are a couple of knowledge articles and bugs written up on the SAS2 issues.  One is a workaround to get Solaris to see and use the SAS tape device connected to a SAS2 HBA but even if that is done the backup application won't be able to use it and thus why this config isn't supported. 

There are 2 issues that have been encountered with the SAS2 drives that will end up going in the SL500 and the SL24/48 libraries.  They are listed below and are only issues with using Solaris and our SAS2 HBA code named “Erie”:

• CR 6991469: Unable to generate sgen entry on SAS2 tape products with SAS2 6Gb/s HBA
  Here is a current workaround.  The /etc/drivers_aliases file needs to have "sgen scsiclass,08" added.  This would be a customer edit.  The Oracle driver group is looking into this issue and how it can be resolved in the driver (mpt_sas).  sgen has been hardcoded in the HBA driver in the past, it was decided with mpt_sas not to hardcode sgen.
• CR 6989444: Backup software unable to detect library/tape devices attached to ERIE SAS2 HBA cards
  Changes in Solaris have made it so the ISV's are unable to see the robot or drives. Due to these issues and no fix being given in the near future for the second one Enginerring has decided to not support SAS2 tape drives on Solaris at this time.

Provided by Ryan Lucas.

This solution has no attachment