HP DDS/DAT drives UNIX, Linux and OpenVMS configuration guide (DW049-90915, November 2009)

HP Evolution II DDS/DAT drives: UNIX, Linux and OpenVMS configuration guide 33

7 Sun (Solaris) servers and workstations

NOTE: Only SCSI drives are supported on Solaris.

Determining the SCSI ID

Before you configure your system to support a DDS-format drives, you need to determine which SCSI

ID to use. IDs must be unique for each device on attached to the SCSI bus.

1. Use the

modinfo command to identify SCSI controller drivers installed on the system.

For FAS or ESP devices:

% modinfo | grep "HBA Driver"

This will produce output similar to the following:

104 78032000 12660 33 1 glm (glm SCSI HBA Driver)

This indicates that there a GLM-based SCSI controller on the system. For the adapter to which the

new tape drive is attached, you will need to determine what SCSI IDs are already used.

2. Determine the SCSI IDs of the existing devices attached to the SCSI controller:

For all adapters:

% dmesg | egrep ".*xxx.*target" | sort | uniq

where xxx = the type of adapter (esp, glm, fas or isp), as appropriate.

For example, for an GLM-based adapter:

% dmesg | egrep ".*glm.*target" | sort | uniq

This produces a list similar to:

sd6 at glm0: target 6 lun 0

This indicates that SCSI ID 6 is used for an existing device. SCSI ID 7 is generally used for the

adapter itself. In this situation, you would use a SCSI ID from 1 to 5 for the new tape drive.

Driver configuration

NOTE: Drives should work well with Solaris without modifications to the kernel, and you are

recommended to try this.

Only if necessary, make the following file modifications to enhance performance:

1. In the file

/kernel/drv/st.conf, after these lines:

########

#ident "@(#)st.conf 1.6 93/05/03 SMI"

add the following, where X is the SCSI target address of the device you have attached (the

spaces are significant in the strings):