When I configured a tape library on a san I remember having to assign the
extra LUN as you stated, but I also remember using the switch admin for the
SAN to assign the world wide address to the robot and drive(s).  Also on sun
I believe you have to do a reconfigure reboot, boot -r   Although you may
not be using the shared storage option, the shared storage option (SSO)
administration guide gives some tips on configuring a library within the
SAN.  It may be helpful.  You can find the guide on the veritas web site. 

Dan

-----Original Message-----
From: Ayaz Mudarris [mailto:ayaz AT colltech DOT com]
Sent: Wednesday, March 07, 2001 5:40 PM
To: mtole AT pwi DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] sgscan oddity


On Thu, Mar 01, 2001 at 11:11:54AM -0800, Matthew Tole wrote:
> I am having a problem getting solaris is assign a
> device file for a tape drive on a fabric SAN. When I
> do an sgscan I get:
> 
> /dev/sg/c0t6l0: Disk (/dev/rdsk/c0t0d0): "SEAGATE
> ST336704LSUN36G"
> /dev/sg/c2t0l0: Changer "STK   L180"
> /dev/sg/c4t2l0: Tape (???): "STK   9840"
> /dev/sg/c5t0l0: Tape (/dev/rmt/0): "STK   9840"
> 
> I have checked the st.conf to make sure that there are
> enough lun assignments but short of that I am stuck.
> Any ideas.
> 


Try persistant binding in sg.conf file

-- 
Ayaz Mudarris
eFax (253) 541-2141


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu