[Veritas-bu] sgscan missing shared drive
2002-04-12 09:24:55
Subject: |
[Veritas-bu] sgscan missing shared drive |
From: |
ccang AT ncs.com DOT sg (Ang Chip Chiang NCS) |
Date: |
Fri, 12 Apr 2002 21:24:55 +0800 |
Hi,
Here're the steps required to configure FC drives:
1) System level
/kernel/drv/st.conf (note that this file will be overwritten every time you
apply the Solaris Recommended patch. So make a backup to some other
location)
name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
(target depends on what you set in your HBA config file, see
/kernel/drv/lpfc.conf for Emulex and /kernel/drv/jnic.conf for JNI on the
persistant binding part)
2) /usr/openv/volmgr/bin/driver/sg.conf
name="sg" class="scsi" target=0 lun=0;
name="sg" class="scsi" target=0 lun=1;
3) /usr/openv/volmgr/bin/driver/sg.links
type=ddi_pseudo;name=sg;addr=0,0; sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1; sg/c\N0t0l1
(note that the spacing should be a tab)
4) #modinfo |grep sg
Ensure you have the 3.4 ver.
Else
#rem_drv sg
#mv /kernel/drv/sg.conf /kernel/drv/sg.conf.OLD
#/usr/openv/volmgr/bin/driver/sg.install
(Basically this will re-install the sg driver and also to copy the
/usr/openv/volmgr/bin/driver/sg.conf to /kernel/drv/sg.conf)
5) #sgscan
Hope that helps.
Regards,
ACC
-----Original Message-----
From: Brochart, Fabrice
To: 'larry.kingery AT veritas DOT com'; Markham, Richard
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Sent: 4/12/02 5:04 PM
Subject: RE: [Veritas-bu] sgscan missing shared drive
If you want to see this drive, you have to modify /kernel/drv/st.conf
name="st" class="scsi"
target=0 lun=0;
name="st" class="scsi"
target=0 lun=1;
Hth
F@brice
-----Original Message-----
From: Larry Kingery [ mailto:larry.kingery AT veritas DOT com
<mailto:larry.kingery AT veritas DOT com> ]
Sent: vendredi 12 avril 2002 03:36
To: Markham, Richard
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: Re: [Veritas-bu] sgscan missing shared drive
You need to consult the MM Device Configuration Guide. Looks like you
missed the section on adding SCSI/LUN support for devices greater
than...
Your second tape drive is on LUN 1, but Solaris out of the box only
looks at LUN 0.
Markham, Richard writes:
> A media server is showing the following:
>
> sgscan output:
> /dev/sg/c0t0l0: Disk (/dev/rdsk/c0t0d0): "SEAGATE ST336704LSUN36G"
> /dev/sg/c0t1l0: Disk (/dev/rdsk/c0t1d0): "SEAGATE ST336704LSUN36G"
> /dev/sg/c0t6l0: Cdrom: "TOSHIBA DVD-ROM SD-M1401"
> /dev/sg/c2t0l0: Tape (/dev/rmt/0): "QUANTUM DLT8000"
> /dev/sg/c3t0l0: Changer: "STK L40"
> /dev/sg/c3t0l1: Tape (???): "QUANTUM DLT8000"
>
> the second tape drive should reflect '/dev/rmt/1' where there is '???'
> i check and there is link lights on the brocades for the two fiber
> connections
> and my other media managers that are split across the same two
brocades
> are
> accessing both the shared tape drives correctly. I can say this is
> machine specific
> but to include the fiber cable as well.
>
> patchlevel NB_34_2 on Solaris 8
>
> i recently rm /dev/rmt/* and 'drvconfig' & 'tapes'. /dev/rmt/ shows
no
> 1*
>
> anyone have a suggest on what could be the issue?
>
[html removed]
--
Larry Kingery
Does fuzzy logic tickle?
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
|
|
|