SUMMARY: DDS-4 on E3500

Thanks to Tony Walsh

Below is the solution given by Tony


> The simple thing to do would be to edit /kernel/drv/st.conf and change the
following lines to be
> uncommented.
> #
> #       In case there are wide tape drives, one can use these targets
> #
> #name="st" class="scsi"
> #       target=8 lun=0;
>
> #name="st" class="scsi"
> #       target=9 lun=0;
>
> #name="st" class="scsi"
> #       target=10 lun=0;
>
> #name="st" class="scsi"
> #       target=11 lun=0;
>
> #name="st" class="scsi"
> #       target=12 lun=0; # <--- This is the one you are looking to use
>
> #name="st" class="scsi"
> #       target=13 lun=0;
>
> #name="st" class="scsi"
> #       target=14 lun=0;
>
> #name="st" class="scsi"
> #       target=15 lun=0;
>
> The more hardware oriented change would be to change the jumpers on the
DDS4. These drives support
> Ultra SCSI controllers and so can have an id from 0 to 15 (not including 7
or 8). This means there
> are 4 jumpers instead of the 3 there used to be.
>
> Regards Tony Walsh
>
> > Suhairi Mansor wrote:
> >
> > Dear Managers
> >
> > I'm trying to configure a DDS-4 drive on an E3500 running Solaris 8.
I've run
> > drvconfig;tapes;devlinks as well as devfsadm but that didn't work. I
brought the system down to ok
> > prompt and did a probe-scsi-all. That revealed the DDS drive being
attached to target c. What does
> > target c means?
> >
> > Any idea how to bring this DDS drive up without resetting the SCSI
target?
> >
> >
> > TIA
> >
>
> --
>   \_         Views expressed in this posting are my opinions. They are in
no
>   </'      way related to opinions held by my employer, Sun Microsystems.
>  /)          Statements on Sun products included here are not gospel and
may
> (/         be closer to fiction rather than truth.
> `
>