Veritas-bu

[Veritas-bu] Solaris 8 not making devices for IBM LTO 2

2003-10-09 07:28:52
Subject: [Veritas-bu] Solaris 8 not making devices for IBM LTO 2
From: gmackinn AT ford DOT com (MacKinnon, G. R. (Gregory))
Date: Thu, 09 Oct 2003 07:28:52 -0400
> Steve Mickeler wrote:
> 
> Box = e450, Solaris 8
> HBA's = 2 x JNI 6460 , Driver 5.3 connected to a brocade fabric.
> ATL = STK L700 w/ 8 IBM LTO Gen 2 Drives connected to a brocade
> fabric.
> 
> Right now I'm just trying to see the physical tape drives.
> 
> my logs show that I'm, seeing the devices, 2 drives on each HBA
> 
> jnic146x0: Port 020055 (WWN 5005076300213C6B:5005076300613C6B)
> online
> jnic146x0: Port 020155 (WWN 5005076300213A72:5005076300613A72)
> online
> Network Port FFFC01 (WWN 1000006069102F0A:20FD006069102F0A)
> available
> 
> jnic146x1: Port 020255 (WWN 5005076300213B4C:5005076300613B4C)
> online
> jnic146x1: Port 020355 (WWN 5005076300213800:5005076300613800)
> online
> Network Port FFFC02 (WWN 1000006069102F6A:20FD006069102F6A)
> available
> 
> I'm using the latest st driver.
> 
> # strings /kernel/drv/st | grep IBM
> IBM     ULTRIUM-TD2
> IBM     ULT3580-TD2
> IBM     ULTRIUM-TD1
> IBM     ULT3580-TD1
> IBM Ultrium Gen 2 LTO
> IBM Ultrium Gen 2 LTO
> IBM Ultrium LTO
> IBM Ultrium LTO
> 
> However, no new devices are being created in /dev/rmt via boot -r
> or
> devfsadm
> 
> Any ideas ?
> _______________________________________________
Steve,

What does your /kernel/drv/fcaXX.conf look like? Are you
trying to port bind the tape drives? The Solaris box will
'see' anything in it's zone, but that doesn't make it 
available. I port bind the tape drives and force them
to certain targets/luns. Here's an example, YMMV.


fcaw.conf (relevant lines only)

#    and fabric operation is enabled
fca_nport = 1;

Then further down.

# *See technote for details on hba bindings
def_hba_binding  = "nonjni";

And a few lines later

def_port_binding = "$xxxxxx";

Now the HBA is looking for the Brocade ports. So I added
the following to the st.conf:


name="st" class="scsi" target=11 lun=0 hba="fcaw0" port="0d1600";
#Tape 9940-1 at SRL
name="st" class="scsi" target=12 lun=0 hba="fcaw0" port="0e1600";
#Tape 9940b-0-ecc 
name="st" class="scsi" target=13 lun=0 hba="fcaw0" port="101700";
#Tape 9940B-0-srl 

(I add the identical lines to sg.conf, changing the "st" to "sg".)


Then at your next reconfiguration boot you should see something
similar to this in /var/adm/messages:

Sep 29 10:52:49 manticora fcaw: [ID 451854 kern.notice] fcaw0:
Target 11: Port 0D1600 (500104F0004
6DA6C:500104F00046DA6D) online.
Sep 29 10:52:49 manticora fcaw: [ID 451854 kern.notice] fcaw0:
Target 11 Lun 0: Port 0D1600 (50010
4F00046DA6C:500104F00046DA6D) present.
Sep 29 10:52:49 manticora scsi: [ID 365881 kern.info]
/sbus@1f,0/fcaw@1,0/st@b,0 (st28):
Sep 29 10:52:49 manticora       <STK 9940 Tape Drive>
Sep 29 10:52:49 manticora scsi: [ID 193665 kern.info] st28 at fcaw0:
target b lun 0
Sep 29 10:52:49 manticora genunix: [ID 936769 kern.info] st28 is
/sbus@1f,0/fcaw@1,0/st@b,0
Sep 29 10:52:49 manticora fcaw: [ID 451854 kern.notice] fcaw0:
Target 12: Port 0E1600 (500104F0007
011D8:500104F0007011D9) online.
Sep 29 10:52:49 manticora fcaw: [ID 451854 kern.notice] fcaw0:
Target 12 Lun 0: Port 0E1600 (50010
4F0007011D8:500104F0007011D9) present.
Sep 29 10:52:49 manticora scsi: [ID 365881 kern.info]
/sbus@1f,0/fcaw@1,0/st@c,0 (st30):
Sep 29 10:52:49 manticora       <StorageTek 9940B>
Sep 29 10:52:49 manticora scsi: [ID 193665 kern.info] st30 at fcaw0:
target c lun 0
Sep 29 10:52:49 manticora genunix: [ID 936769 kern.info] st30 is
/sbus@1f,0/fcaw@1,0/st@c,0
Sep 29 10:52:49 manticora fcaw: [ID 451854 kern.notice] fcaw0:
Target 13: Port 101700 (500104F0007
011BA:500104F0007011BB) online.
Sep 29 10:52:49 manticora fcaw: [ID 451854 kern.notice] fcaw0:
Target 13 Lun 0: Port 101700 (50010
4F0007011BA:500104F0007011BB) present.
Sep 29 10:52:49 manticora scsi: [ID 365881 kern.info]
/sbus@1f,0/fcaw@1,0/st@d,0 (st32):
Sep 29 10:52:49 manticora       <StorageTek 9940B>
Sep 29 10:52:49 manticora scsi: [ID 193665 kern.info] st32 at fcaw0:
target d lun 0
Sep 29 10:52:49 manticora genunix: [ID 936769 kern.info] st32 is
/sbus@1f,0/fcaw@1,0/st@d,0


Then after that works semi-flawlessly, you can do a sanity check to
be sure you're looking at the drive you think you're looking at.

Say target 11 lun 0 (0d1600); you can see that the st.conf gave it
a pseudo device of st@b, so you do a ls -l /dev/rmt/? |grep st@b
and get

lrwxrwxrwx   1 root     root          40 Jul 21 11:16 /dev/rmt/9 ->
../../devices/sbus@1f,0/fcaw@1,0/st@b,0:

It's magic.


HTH,

Gregg


=================================================================
Gregg MacKinnon                         Ford Motor Co.
gmackinn AT ford DOT com                        2101 Village Rd. 
Technical Computing Section             Rm 1116, MD 1076        
(313) 594-3716   pager 7958343          Dearborn Michigan, 48124
==================================================================

<Prev in Thread] Current Thread [Next in Thread>