Chapter 1
About This Release


Introduction

These release notes support ptx®/SPDRIVERS (Storage Products Drivers) V4.1.0 for systems running DYNIX/ptx® V4.6.1 or later maintenance releases. ptx/SPDRIVERS enables NUMA systems to communicate with various storage devices. Read this document before you install or run this release of ptx/SPDRIVERS.


Changes in ptx/SPDRIVERS V4.1.0

ptx/SPDRIVERS V4.1.0 contains the following changes since ptx/SPDRIVERS V4.0.0:


Changes in ptx/SPDRIVERS V4.0.0

ptx/SPDRIVERS V4.0.0 contains the following changes since ptx/SPDRIVERS V3.1.0:


System Requirements


Software Requirements

ptx/SPDRIVERS V4.1.0 runs on DYNIX/ptx V4.6.1 and later maintenance releases.


Disk Space Requirements

Installing ptx/SPDRIVERS requires approximately 3.5 MB in the root filesystem. No run-time disk space is required for ptx/SPDRIVERS.


Software Compatibility


Custom Miniroot Support

ptx/SPDRIVERS V4.x.x designates that the /etc/mctab file, the mc command, the mcbuild command, and the rc2 script that executes mcbuild at boot time be placed on the custom miniroot on a DYNIX/ptx V4.6.x system. (The device drivers are part of the kernel and do not have to be explicitly placed on the custom miniroot.) Additionally, for SAMS:Alexandria® and Backup Toolkit users, the Backup Toolkit systeminfo script, which is run during daily SAMS:Alexandria housekeeping, copies the /etc/mctab file under the name mctab in the /usr/alexbkup/disaster_recovery directory.


Software Compatibility with Backup Applications

Hosts running DYNIX/ptx V4.6.x and a backup application, like SAMS:Alexandria server, must install ptx/SPDRIVERS. ptx/SPDRIVERS includes all the tape and library device drivers required for the devices supported by DYNIX/ptx for use with backup applications like SAMS:Alexandria. No changes are required in the SAMS:Alexandria hardware configuration as the device names will remain the same after the upgrade to DYNIX/ptx V4.6.x and ptx/SPDRIVERS V4.x.x.

If the host is running DYNIX/ptx V4.6.x, ensure that ptx/SPDRIVERS is already installed before you install SAMS:Alexandria.


ATTENTION

Backup Toolkit V4.4.4, SAMS:Alexandria V4.50.70 and earlier versions, and NetBackup V3.4 and earlier versions do not support the FC-ported IBM Magstar 3590 Tape Subsystem.



Install ptx/SPDRIVERS

Before you install the ptx/SPDRIVERS software, you should familiarize yourself with the hardware installation requirements for the tape drives and libraries you plan to use. For more information, refer to the applicable hardware documentation. You should also determine the hardware connections you plan to use for each library before software installation.

Use ptx/INSTALL to install ptx/SPDRIVERS V4.1.0 from the DYNIX/ptx V4.6.1 and Layered Products Software, Volume 1 CD. The DYNIX/ptx V4.6.1 and Layered Products Software Installation Release Notes tell how to use this process to install all DYNIX/ptx software. This document also describes how to use the mcbuild utility to associate tape drives with media changers and how to verify hardware detection of configured devices.


ATTENTION

If you are upgrading from a host running DYNIX/ptx V4.4.7, V4.4.8, or V4.5.1, a change in the way DYNIX/ptx generates UUIDs for tape drives causes device name slippage for tc and tl devices that are attached at the time of the upgrade. This slippage can enable backup applications to execute operations on the wrong tape device, which could result in the loss of previously backed up data.

This scenario occurs because DYNIX/ptx V4.5.1 and V4.4.x do not use device serial numbers to generate the UUID for a tape device, but DYNIX/ptx V4.6.1 does. These modifications in DYNIX/ptx V4.6.1 result in a change in the unit number which causes the device number to be recalculated by the device naming database.

Before upgrading to DYNIX/ptx V4.6.1 and ptx/SPDRIVERS V4.1.x, note the names of all tc and tl devices that are attached to the system. Then, after the upgrade, delete the previous device names from the device naming database (devctl -D) and rename the newly named devices to the previous names (devctl -n).


Since ptx/SPDRIVERS contains kernel components, you must compile the kernel and reboot with that new kernel before you can use ptx/SPDRIVERS. If you try to compile the kernel and ptx/SPDRIVERS is not installed, DYNIX/ptx will output a warning message during the compile. Note, however, that the kernel can be built without ptx/SPDRIVERS.

The default system configuration file for ptx/SPDRIVERS is called /etc/conf/uts/symmetry/spd.std.


Deinstall ptx/SPDRIVERS

You can deinstall ptx/SPDRIVERS by using the Software Management option on the System Administration menu in the ptx/ADMIN menu system. If you are not familiar with the steps to deinstall a product, refer to the ptx/INSTALL Software Installation Guide. The deinstallation of ptx/SPDRIVERS does not delete the /etc/mctab file since this file was not created by the installation of ptx/SPDRIVERS.


ATTENTION

ptx/SPDRIVERS is tightly coupled with DYNIX/ptx and must not be deinstalled unless you no longer need to use the devices supported by ptx/SPDRIVERS. Once you deinstall ptx/SPDRIVERS, those devices are no longer accessible. Refer to "Media and Driver Support for ptx/SPDRIVERS Devices" later in this release note for the supported devices.


Once ptx/SPDRIVERS is deinstalled, you must rebuild the kernel and reboot the operating system.


Tape Drive and Media Type Support in ptx/SPDRIVERS

Table 1-1 summarizes the tape drives, media types, capacities, and device files that are supported by ptx/SPDRIVERS V4.1.0.

Table 1-1. Tape Drives and Media Types Supported by ptx/SPDRIVERS

Native Mode

Compressed Mode

Tape Drive

Media Type

Capacity

Device Filea

Capacity

Device Filea

DDS-2TM tape drive

4-mm DAT

4 GB

/dev/rmt/td0

8 GBb

/dev/rmt/td0c

DDS-3 tape drive

4-mm DAT

12 GB

/dev/rmt/td0

24 GBb

/dev/rmt/td0c

DLT4000 tape drive

DLTtape IIIxt

15 GB

/dev/rmt/tl0d15

30 GBb

/dev/rmt/tl0d15c

DLTtape IV

20 GB

/dev/rmt/tl0d20

40 GBb

/dev/rmt/tl0d20c

DLTtape IIIxt or IV

variablec

/dev/rmt/tl0

variablec

/dev/rmt/tl0c

DLT7000 tape drive

DLTtape IIIxt

15 GB

/dev/rmt/tl0d15

30 GBb

/dev/rmt/tl0d15c

DLTtape IV

20 GB

/dev/rmt/tl0d20

40 GB

/dev/rmt/tl0d20c

DLTtape IV

35 GB

/dev/rmt/tl0d35

70 GBb

/dev/rmt/tl0d35c

DLTtape IIIxt or IV

variablec

/dev/rmt/tl0

variablec

/dev/rmt/tl0c

IBM Magstar 3590 Tape Subsystem (E11 and E1A)d

IBM 3590 High Performace Tape Cartridge

20 GBe

40 GBf

/dev/rmt/tc0

60 GBeg

120 GBfg

/dev/rmt/tc0c


a. The device file names shown in this table are for devices assigned a unit number of zero, for example, /dev/rmt/tl0d15. Devices assigned a unit number of one are named /dev/rmt/tl1d15, and so on.

b. The compression amounts listed are based on a 2:1 compression rate. The actual capacity of a tape when used with hardware compression format varies with the type of data being backed up.

c. See the notes following this table for information about the capacity.

d. ptx/SPDRIVERS V4.1.0 supports only an FC-ported IBM Magstar 3590 Tape Subsystem. SCSI-attachment of this tape drive to a NUMA system requires a special support contract. Contact your IBM Sales Representative for more information.

e. Capacity of a Standard 3590 Cartridge.

f. Capacity of an Extended Length 3590 Cartridge.

g. The E11 and E1A models of the 3590 tape drive use a new compaction algorithm, which typically uses a 3:1 compression rate.


Additional Notes for DLT4000 and DLT7000 Tape Drives

Note the following additional information:


Additional Notes for the IBM Magstar 3590 Tape Subsystem

Note the following additional information specific to NUMA systems and ptx/SPDRIVERS V4.1.0:

For details on other limitations and caveats specific to NUMA systems, refer to the online document Supplement for IBM Tape Devices on NUMA Systems that is available at this URL:

http://webdocs.numaq.ibm.com/

To locate this document from the NUMA Customer Documentation web page, use the left pane to select the topic "Hardware" and then the subtopic "Tape Operation."

For further information about the IBM Magstar 3590 Tape Subsystem, refer to the publications at the following URL:

http://www.storage.ibm.com/hardsoft/tape/pubs/pubs3590.html


Library Support in ptx/SPDRIVERS

Table 1-2 describes the libraries that are supported by the drivers in this release of ptx/SPDRIVERS.

Table 1-2. Libraries Supported by ptx/SPDRIVERS

Library

Internal Tape Drive

Number of Tape Drives

Number of Tape Slots

Device Filea

EXB®-10h Autoloader/ Stacker

EXB-8505XL tape driveb

1

10-cartridge magazine

/dev/mch/mx0

DDS-2 Library

DDS-2 tape drive

2

4

22 or 60

20 or 58

/dev/mch/ms0

DDS-3 Library

DDS-3 tape drive

2

4

20

60

/dev/mch/ms0

HP® DLT4000 Library

DLT4000 tape drive

2

4

48

48

/dev/mch/ml0

STK L700 Library Storage Module (directly- or ACSLS-connected)c

DLT7000 tape drive

1 to 20

154-678

/dev/mch/mw0d

STK 9710 Library Storage Module (directly- or ACSLS-connected)

DLT4000 tape drive

DLT7000 tape drive

1 to 10

252 or 420 or 588

/dev/mch/mw0d

STK 9730 Library Storage Module (directly-connected)

DLT4000 tape drive

DLT7000 tape drive

1 to 4

18 or 30

/dev/mch/mw0

STK 9740 Library Storage Module (ACSLS-connected)

DLT7000 tape drive

1 to 10

318-486 per LSM

not applicabled


a. The device file names shown in this table are for devices assigned a unit number of zero, for example, /dev/rmt/mx0. Devices assigned a unit number of one are named /dev/rmt/mx0, and so on.

b. The EXB-8505XL tape drive uses 8-mm tapes and uses the tx device driver, which is provided by DYNIX/ptx, not ptx/SPDRIVERS.

c. This library is supported as a directly-connected library on xSeries 430 hosts and NUMA-Q 2000 hosts running DYNIX/ptx V4.5.x or V4.6.x. It is supported as an ACSLS-connected library on Symmetry hosts running DYNIX/ptx V4.5.x and all hosts running DYNIX/ptx V4.4.4 or later maintenance releases.

d. The library robotics of an ACSLS-connected library are controlled by STK's Automated Cartridge System Library Software (ACSLS) and not a device driver.


Additional Notes for STK Libraries

Note the following additional information:


ptx/SPDRIVERS Commands and Utilities

ptx/SPDRIVERS includes the following commands and utilities:


Associate Tape Drives with Media Changers By Using the mcbuild Utility

When using directly-connected libraries, you should use the mcbuild utility to associate tape drives with each media changer or library device. You can create or update these associations at any time-a system reboot is not required. This task is not applicable to ACSLS-connected libraries.

When mcbuild is not used, a media changer driver tries to determine the names of its connected tape drives the first time the media changer device is opened. The media changer driver then keeps those tape drive names until the system is rebooted. This method works most of the time, especially when there is only one media changer on the host and all the tape drives connected to the host are in the media changer. However, because the media changer device cannot return unique identifiers for the tape drives connected to it, the media changer driver has no way of positively associating a tape drive with that media changer device. Also, if you rename a tape device with the devctl command, the output from the mc command does not reflect the current device configuration until the system is rebooted.

To prevent these problems, you should use the mcbuild utility to explicitly associate tape drives with every media changer on the host. Even if you only have one media changer on the host, it is a good system administration practice to use the mcbuild utility.

Complete the following steps to use the mcbuild utility to associate tape drives to directly-connected media changer devices:

  1. Create or edit the /etc/mctab file to contain one line for each media changer device and its associated tape drives.


    ATTENTION

    Any time you add, remove, or rename a tape device that is associated with a media changer or a library device, you must first delete the library configuration from the host (devctl -d), next reprobe the host (devctl -c), then update the /etc/mctab file appropriately, and lastly run the mcbuild command. These actions remove the reference pointers established in the kernel by the previous mcbuild command. A system reboot is not required.


    Each line in the /etc/mctab file should be of the following format:

    mc_device_name drive1 drive2 drive3 ...

    The order given for the tape drives must correspond to their order as storage elements in the library. This is important because the naming order of tape drives may not correspond directly to their order in a library. For example, a library may have four tape drives with SCSI ID's 0, 1, 2, and 3. Because of the way they are cabled to the system, the system may probe them in a different order (such as 2, 3, 0, 1). The system will assign drive names in probe order, but mc(1) will erroneously assume that the drive name sequence follows its own ordering. mcbuild must be used to rectify this situation by listing the drive names in the correct order with respect to the library.

    For example, to associate the tape drives tl0 through tl3 with the HP DLT4000 library /dev/mch/ml0 and to associate the tape drives tl4 through tl8 with the STK 9710 library /dev/mch/mw0, you would add the following lines to the /etc/mctab file:

    /dev/mch/ml0 tl0 tl1 tl2 tl3 tl4
    /dev/mch/mw0 tl5 tl6 tl7 tl8 tl9

    If you do not know which tape drives belong to which library, you can determine this information as follows:

  2. Run the mcbuild utility to associate the tape drives and media changers that are defined in the /etc/mctab file.

    # mcbuild

ptx/SPDRIVERS Man Pages

ptx/SPDRIVERS includes online man pages that describe various components of this product. To view the ml(7) man page, for example, enter the following command:

# man 7 ml

The following man pages are included with ptx/SPDRIVERS:

cfwdl(1)
Downloads firmware to FC Host Adapters, FC Bridges, FC-ported IBM 3590 Tape Subsystems, and SCSI disk storage devices, tape drives, and tape libraries, and performs other administrative tasks. For more information, refer to the DYNIX/ptx V4.6.1 and Layered Products Software Installation Release Notes and go to Chapter 9, "Download Firmware with cfwdl."
fcinfo(1)
Uses a combination of mode and log sense commands to obtain and display statistical information obtained from Fibre Channel Bridge(s) installed in a NUMA system. fcinfo is a utility intended for use only by customer support personnel.
mc(1)
Manipulates media changer devices and displays their status.
mcbuild(1)
Associates tape drives with media changer devices.
scsilog(1)
Displays statistical information for a SCSI device by using the SCSI log sense command.
ml(7)
Device driver that supports the SCSI media changer for HP DLT4000 libraries.
ms(7)
Device driver that supports the SCSI media changer for DDS-2 libraries, DDS-3 libraries, and DDS-2 Autoloaders.
mw(7)
Device driver that supports the SCSI media changer for direct-connect STK L700, 9710, and 9730 libraries.
mx(7)
Device driver that supports the SCSI media changer for the EXB-10h Autoloader/Stacker.
spdrivers(7)
Overview of the device drivers and commands provided by ptx/SPDRIVERS.
tc(7)
Device driver that supports IBM Magstar 3590 Tape Subsystems.
td(7)
Device driver that supports DDS-2 tape drives and DDS-3 tape drives.
tl(7)
Device driver that supports DLT4000 tape drives and DLT7000 tape drives.

Problem Report Summary

This section describes the following subjects:

Note that no open problems have been explicitly fixed in ptx/SPDRIVERS V4.1.0. The numbers in parentheses identify the problems in the problem-tracking system.


Fixed Problems in ptx/SPDRIVERS V4.0.0

The following problem was fixed in ptx/SPDRIVERS V4.0.0:


Open Problem Summary


Request Sense Data Handling in scsimc Does Not Print Raw Sense Data (236516)

The media changer drivers all invoke the same code (scsimc) to handle request sense data; this code tries to interpret the sense data and return in text what the problem is. However, when an error occurs, scsimc does not return the raw sense data, so none of the media changer drivers can output this information to /usr/adm/ktlog. The raw sense data should be output because it frequently contains diagnostic information that can help isolate the source of the error.

Workaround. None.


mcbuild(1) Man Page Needs Additional Information (238064)

The mcbuild(1) man page should explain that the order given for the drives corresponds to their order as storage elements in the library.

This is important, because the naming order of tape drives may not correspond directly to their order in a library. For example, a library may have four tape drives with SCSI ID's 0, 1, 2, and 3. Because of the way they are cabled to the system, the system may probe them in a different order (such as 2, 3, 0, 1). The system will assign drive names in probe order, but mc(1) will erroneously assume that the drive name sequence follows its own ordering. mcbuild must be used to rectify this situation by listing the drive names in the correct order with respect to the library.

Also, the man page does not describe the output of the mcbuild command.

Workaround. None.


fcinfo Default Behavior Does Not Match Man Page Description (246748)

Due to changes in the dumpconf command in DYNIX/ptx V4.5, fcinfo no longer provides interactive searching through the configuration tree as its default behavior when no FC bridge devices are specified.

Workaround. Create a script called fcinfo_all with the following contents:

#!/bin/ksh
#set -x   

br_list=
IFS=:
/etc/dumpconf -d -m 2>&1 | while read devname dt dn cp cu pp pu fl if bus
do               if print "$devname" 2>&1 | grep "fcbr" > /dev/null
         then                       br_list="$br_list $devname"
         fi
done

IFS=" "   

/usr/service/bin/fcinfo  $@ $br_list


cfwdl Returns "Unable to create a download object" Error For a Variety of Reasons (251155)

When the cfwdl utility cannot download a firmware file to a device or cannot access a device, a vague error message is displayed about the situation:

cfwdl: Unable to create a download object for tl1

Workaround. If you receive this error message, take the following actions as appropriate:


Firmware Downloads to DLT Tape Drives and STK Libraries Cause Influx Conditions (251162)

In an STK library, each tape drive has an individual door that is generally left open between tape drive operations. When the tape drive door is open during a reset operation, the tape drive cannot determine whether it contains a tape, which then causes an influx condition to occur for that tape drive. This scenario occurs when the following events happen:

The influx condition prevents cfwdl from successfully downloading or auditing the firmware versions of the DLT tape drives. For example, if a tape drive is in the influx condition, the cfwdl -a command will fail with messages similar to the following:

# /usr/service/bin/cfwdl -a -d tl3
cfwdl: scsibus18 (target 2, lun 0): command 0x12: adapter unable to 
initiate command
cfwdl: Could not open the passthru device for tl3 to get the revision
cfwdl: Unable to create a download object for tl3

Workaround. To prevent influx conditions from occurring during firmware downloads, closely follow the recommended steps for downloading tape drive and library firmware that are provided in the DYNIX/ptx V4.6.1 and Layered Products Software Installation Release Notes. Specifically, refer to need to update hotlink rid Chapter 9, "Download Firmware with cfwdl," and review the section "DLT Tape Drive and STK Library Firmware Download Procedures."

This section also describes how to clear an influx condition that has occurred. Note that the recovery from this condition is different based on whether the library is directly-connected or ACSLS-connected.


cfwdl Firmware Message Text Runs Together (251960)

When you use cfwdl -u to determine which devices require firmware upgrades, messages similar to the following are returned for devices that require updates:

Device tl0 needs to be updated: Old Firmware XXXX New firmware 245FFirmware file
/usr/ssw/fw/DLT7K_STK_V95.sqfw

The problem is that the message is missing a blank space between the phrase about the new firmware version that is required (in this example, New firmware 245F) and the text about the firmware file required (Firmware File...). The result is that the firmware version looks like it is 245FFirmware.

Workaround. None.


cfwdl Requires sci0 to Exist in the Configuration Graph (253168)

If sci0 does not exist in the configuration graph and no device or subtree is specified to restrict the device search, cfwdl does not work. The problem occurs because cfwdl assumes that the device search should start at sci0 unless -d or -s are specified to start the search elsewhere in the configuration graph. cfwdl then fails when it cannot locate sci0.

Workaround. If a host does not have sci0, you can include the syntax -s sci_name in the cfwdl command to direct the start of the search. The variable sci_name is the name to which sci0 has been renamed. For example:

# /usr/service/bin/cfwdl -s sci1

Alternatively, you can rename the sci device back to sci0:

# devctl -n sci1 sci0
devctl: Assigned sci1 --> sci0