Table of Contents
Advertisement
44
Configuring for the Sun Environment
(Solaris 2.4, 2.5, 2.6, 7, and 8)
Use the following for attaching the Viper 200 to Sun Sparc
and Intel systems.
Finding current SCSI controllers and targets
In order to properly attach SCSI devices to hosts it is
necessary to ensure that each target device has a unique
SCSI address. The commands 'modinfo' and 'dmesg' can be
used to find the SCSI controllers in use and the SCSI target
devices installed.
For example, the command "dmesg | egrep "target" | sort |
uniq" can find all SCSI controllers and SCSI targets. The
output may look similar to:
sd32 at ithps0: target 2 lun 0
sd34 at ithps0: target 4 lun 0
st21 at ithps1: target 0 lun 0
st22 at ithps1: target 1 lun0
In this case the Viper 200 could be set for SCSI ID address 2
thru 6 and attached to controller ithps1 (this particular
controller also supports SCSI addresses 8 thru 15). See
figure 1 to view how to set the SCSI ID address jumpers for
the Viper 200.
Types of controllers
You may be able to view the main pages of three types of
SCSI controllers for Sun Sparc systems, esp, glm and isp.
We recommend that the Viper 200 not be attached to esp
controllers. This controller is not fast enough to work with the
Viper 200. The minimum recommended controller would be a
glm controller, which is an Ultra Wide controller.
We recommend Ultra2 SCSI capable controllers capable of
80MB/s data transfer. Ultra 3 controllers supporting 160MB/s
transfer rates can also be used.
Viper 200 Installation Manual
Advertisement
Table of Contents
