HP LTO-3 - Tape Drives in SL500 Tape Library Having Configuration Issues With Solaris 10

Asset ID:	1-72-1009584.1
Update Date:	2011-05-06
Keywords:

Solution Type Problem Resolution Sure

Solution 1009584.1 : HP LTO-3 - Tape Drives in SL500 Tape Library Having Configuration Issues With Solaris 10

Applies to:

HP LTO3 Tape Drive - Version: Not Applicable and later [Release: N/A and later]
Sun StorageTek SL500 Modular Library System - Version: Not Applicable and later [Release: N/A and later]
All Platforms
Checked for relevance on 6-May-2011.

Symptoms

Symptoms
(HP) LTO3 Tape Drives in Sun StorEdge [TM] L500 Tape Library do not configure properly with Solaris[TM] 10.
The following error messages comes up on every boot:

Feb 7 20:03:56 ctidb2 genunix: [ID 540533 kern.notice] SunOS Release 5.10 Version Generic_118822-26 64-bit
:
:
Feb 7 20:07:04 ctidb2 ssfcp_online_child: mdi_pi_online: failed for st: target=11b00 lun=0 ffffffff
Feb 7 20:07:04 ctidb2 ssfcp_online_child: mdi_pi_online: failed for st: target=11d00 lun=0 ffffffff
Feb 7 20:07:04 ctidb2 ssfcp_online_child: mdi_pi_online: failed for st: target=11e00 lun=0 ffffffff
Feb 7 20:07:04 ctidb2 ssfcp_online_child: mdi_pi_online: failed for st: target=11c00 lun=0 ffffffff

Changes

{CHANGE}

Cause

{CAUSE}

Solution

Resolution
The following minimum version of firmwares should be installed into the SE L500 Tape Library:
STK L500 robotic controller = 1.02.2

HP LTO-3 Tape Drive = L29S

Go to the RMQUAL website for the latest information about Tape Library & Tape Drive firmware revision levels.

Details of the set-up which did not work:

The SE L500 attached to a SAN switch (Storage Area Network), and zoned with a Solaris 10 host.

SE L500 firmware revision levels:
STK L500 robotic controller = 1.02.6
HP LTO-3 Tape Drive = L25S/008.527

The /dev/rmt devices which are automatically generated under Solaris 10, are invalid device names. We can see /dev/rmt/ populated with wrong devices i.e., /devices/pci@dc,600000/ and not /devices/pci@fd,700000 which is the actual controller to which the SE L500 is attached via SAN.

# ls -l /dev/rmt :
lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root lrwxrwxrwx 1 root root 48 Jan 26 11:29 0 -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:
root 49 Jan 26 11:29 0b -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:b
root 50 Jan 26 11:29 0bn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:bn
root 49 Jan 26 11:29 0c -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:c
root 50 Jan 26 11:29 0cb -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:cb
root 51 Jan 26 11:29 0cbn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:cbn
root 50 Jan 26 11:29 0cn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:cn
root 49 Jan 26 11:29 0h -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:h
root 50 Jan 26 11:29 0hb -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:hb
root 51 Jan 26 11:29 0hbn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:hbn
root 50 Jan 26 11:29 0hn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:hn
root 49 Jan 26 11:29 0l -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:l
root 50 Jan 26 11:29 0lb -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:lb
root 51 Jan 26 11:29 0lbn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:lbn
root 50 Jan 26 11:29 0ln -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:ln
root 49 Jan 26 11:29 0m -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:m
root 50 Jan 26 11:29 0mb -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:mb
root 51 Jan 26 11:29 0mbn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:mbn
root 50 Jan 26 11:29 0mn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:mn
root 49 Jan 26 11:29 0n -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:n
root 49 Jan 26 11:29 0u -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:u
root 50 Jan 26 11:29 0ub -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:ub
root 51 Jan 26 11:29 0ubn -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:ubn
root 50 Jan 26 11:29 0un -> ../../devices/pci@dc,600000/pci@1/scsi@2/st@4,0:un

st.conf is configured with FC tapes support (entry in st.conf as follows):
name="st" parent="fp" target=0;

cfgadm tells us that the controller is configured but there are no tape drives nor media changer:

Ap_Id Receptacle   Occupant     Condition  Information When         Type         Busy     Phys_Id
================   ========     =========  =========== ===========  ==========   ====     =======
c10               connected    configured   unknown    unavailable  fc-fabric    n        /devices/pci@fd,700000/SUNW,qlc@1/fp@0,0:fc

luxadm can see tape devices as follows:
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 11b00 0 500104f00082aa90 500104f00082aa8f 0x1 (Tape device)
1 11c00 0 500104f00082aa93 500104f00082aa92 0x1 (Tape device)
2 11d00 0 500104f00082aa96 500104f00082aa95 0x1 (Tape device)
3 11e00 0 500104f00082aa9c 500104f00082aa9b 0x1 (Tape device)
4 11f00 0 500104f00082aa86 500104f00082aa85 0x8 (Medium changer device)
5 11900 0 210000e08b867e7d 200000e08b867e7d 0x1f (Unknown Type,Host Bus Adapter)

Service Request ID: 10810944

Escalation ID: 1-14929855
Solution ID: 1-15068343
Owner GEO: APAC
Customer GEO: APAC

HP LTO-3, Tape Drive, L500, firmware, Solaris 10
Previously Published As 83944

Attachments

This solution has no attachment