Control path failover (CPF) support is enabled automatically by default when the IBMtape device driver is installed on Solaris system. The Solaris IBMtape device driver provides a driver configuration parameter failover for you to enable or disable the library control path failover support. To enable the CPF support for all of the paths, no any action is required. To disable the CPF support for all of the paths or a particular path, use the following steps:
1. To disable CPF support for all the paths, add and set the failover parameter to off at the beginning of IBMtape.conf file in the directory of /usr/kernel/drv.
2. To disable a particular path, add and set the failover parameter to off in the path entry in IBMtape.conf file. For example, name=″IBMtape″class=″scsi″ target=3 lun=1 failover=0;
3. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel:
# /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape
4. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ’ 0666 bin bin’ IBMtape
# /opt/IBMtape/tmd
Primary and Alternate Paths
When the device driver configures a logical device with path failover support enabled, the first device configured always becomes the primary path. When a second or more logical device is configured with path failover support enabled for the same physical device, it configures as an alternate path. The device driver supports up to 16 physical paths for single a device.
The primary and alternate path information can be obtained in the field of″Path
example in Figure 13.
The labeling of a logical device as either a primary or alternate path is for information only; it is used to:
1. Identify the actual number of physical devices configured on the system and a specific logical device associated with them. There is only one logical device labeled the primary path for each physical device. However, there can be multiple logical devices labeled as an alternate path for the same devices.
2. Provide information about which logical devices configured on the system have path failover enabled.
Querying Primary and Alternate Path Configuration
You can display the primary and alternate path configuration for all devices with the tapelist utility.
Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions, refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 259 or “Solaris System - Tape Utility Program (tapeutil)” on page 397.
Disable and Enable Primary and Alternate Paths
Once you install the IBMtape device driver, by default, all the available paths for a physical device are enabled.
Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions, refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 259 or “Solaris System - Tape Utility Program (tapeutil)” on page 397.
Data Path Failover and Load Balancing Support for Tape Drives
Note: The tape drive failover feature code must be installed prior to enabling the DPF for IBM Ultrium tape drive in the Solaris IBMtape device driver. Refer to “Automatic Failover” on page 12 to determine which feature code is required for your machine type.
Configuring and Deconfiguring Path Failover Support
Path failover support for tape drives is not enabled automatically when the device driver is installed. It must be configured initially on each logical device after installation. When path failover support is enabled for a logical device, it remains #tapelist -1
Inst# Special File Device Serial No TGT/LUN Ucode WWNN WWPN
Device Physical Path Path Type
--- ---
686 /dev/rmt/12smc 03584L32 0000000T0039 1/1 402j N/A N/A
/devices/pci@If,2000/QLGC,qla@1/IBMtape@1,1 Primary
688 /dev/rmt/14smc 03584L32 0000000T0039 2/1 402j N/A N/A
/devices/pci@If,2000/QLGC,qla@1/IBMtape@2,1 Alt_path_1
694 /dev/rmt/26smc 03584L32 0000000T0039 5/1 402j N/A N/A
/devices/pci@If,2000/QLGC,qla@1/IBMtape@5,1 Alt_path_2
set until the device is deleted or the support is deconfigured. The path failover setting is retained even if the system is rebooted. Path failover support can be enabled on all configured devices at one time, or it can be enabled or disabled selectively by logical device. It may be desirable at times to configure some, but not all, logical paths to a device with the support enabled. Follow the above steps to enable the DPF support:
1. To enable the support globally on all currently configured devices, add an entry
ofdpf_support=1 at the beginning of theIBMtape.conf file, such as
dpf_support=1;
2. Or, to enable a particular path, add the parameter dpf_supportand turn it on in the path entry in theIBMtape.conffile. For example,
name="IBMtape" class="scsi" target=3 lun=0 dpf_support=1;
3. For the IBM Ultrium tape drive, you need to enter the DPF feature key(s) in the parameterdpf_keysat the beginning of theIBMtape.conffile in the directory /usr/kernel/drv. For example:
dpf_keys="A729E60F7B119411, C7A0B9ef2c1a4360, a729e60f7b118460"; Notes:
a. The parameter dpf_keys is in the format “key1,key2,key3, ... ”. Each key is 16 characters long with a comma "," and a space " ". The IBMtape driver supports up to 36 dpf keys.
b. DPF keys do not need to be added inIBMtape.confif you are running the latest drive code on Ultrium-3 and Ultrium-4 drives.
4. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel
# /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape
5. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape
# /opt/IBMtape/tmd
This deconfigures all devices to remove or comment out the parameter
dpf_support in theIBMtape.conffile, and reboot the system or deconfigure and
reconfigure all devices. For example,
1. To disable the support globally on all currently configured devices, remove or comment out the entrydpf_support=1at the beginning of theIBMtape.conffile. # dpf_support=1; * comment out the parameter
2. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel:
# /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape
3. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape
# /opt/IBMtape/tmd
To disable the support on a single logical device, following these steps:
1. To enable the support globally on all currently configured devices, add an entry
dpf_support=1at the beginning of theIBMtape.conffile, such as
dpf_support=1;
2. To disable a particular path, add the parameterdpf_support and turn it off in the path entry in theIBMtape.conffile. For example,
3. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel:
# /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape
4. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape
# /opt/IBMtape/tmd
Primary and Alternate Paths
When the device driver configures a logical device with path failover support enabled, the first device configured always becomes the primary path. When a second logical device is configured with path failover support enabled for the same physical device, it configures as an alternate path. A third logical device is
configured as the next alternate path, and so on. The device driver supports up to 16 physical paths for a single device.
For example, if 0st (port 0 of 3592) is configured first, then 5st (port 1), 18st (port 1) and 21st (port 0) to the two HBAs through a switch (here, WWPN
5005076302400127 from port 0 and 5005076302800127 from port 1), the
/opt/IBMtape/tapelist command output is similar to the example in Figure 14.
The labeling of a logical device as either a primary or alternate path is for information only, in order to:
1. Be able to identify the actual number of physical devices configured on the system and a specific logical device associated with them. There is only one logical device labeled the primary path for each physical device. However, there may be many (multiple) logical devices labeled as an alternate path for the same devices.
2. Provide information about which logical devices configured on the system have path failover support enabled.
Querying Primary and Alternate Path Configuration
You can display the primary and alternate path configuration for all devices with the tapelist utility.
Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions, refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 259 or “Solaris System - Tape Utility Program (tapeutil)” on page 397.
#tapelist -1
Inst# Special File Device Serial No TGT/LUN Ucode WWNN WWPN
Device Physical Path Path Type
--- ---
685 /dev/rmt/0st 03592J1A 000001300168 1/0 04CE 5005076302000127 5005076302400127
/devices/pci@1f,2000/QLGC,qla@1/IBMtape@1,0 Primary
697 /dev/rmt/5st 03592J1A 000001300168 7/0 04CE 5005076302000127 5005076302800127
/devices/pci@1f,2000/QLGC,qla@1/IBMtape@7,0 Alt_path_1
666 /dev/rmt/18st 03592J1A 000001300168 1/0 04CE 5005076302000127 5005076302800127 /devices/pci@1f,4000/JNI,FCR@2/IBMtape@1,0 Alt_path_2
670 /dev/rmt/21st 03592J1A 000001300168 3/0 04CE 5005076302000127 5005076302400127 /devices/pci@1f,4000/JNI,FCR@2/IBMtape@3,0 Alt_path_3
Disable and Enable Primary and Alternate Paths
Once you enter the parameterdpf_supportin theIBMtape.conffile and install the IBMtape device driver, all the available paths for a physical device are enabled. If it is necessary to disable a path and not perform path fail over (for example due to maintenance), run commands to disable and then later enable the primary and alternate paths.
Note: See Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 259 or “Solaris System - Tape Utility Program (tapeutil)” on page 397
System-Managed Encryption
Device Driver Configuration
System-Managed Encryption can be set on global or a specific tape drive in
IBMtape.conf in /usr/kernel/drv. There are 2 new configuration parameters added for encryption:
sys_encryption_proxy “ON/OFF” Use System Encryption FCP Proxy Manager sys_encryption_write “OFF/ON/CUSTOM” System Encryption for Write Commands at BOP
The sys_encryption_proxy parameter enables device driver system-managed encryption for a tape drive by setting the value to ON (default set).
The sys_encryption_write parameter controls if the device driver can set the tape drive to encryption enabled for write commands. When set toOFF, the tape drive uses encryption for read operations; write operations do not use encryption. When set to ON, the tape drive uses encryption for both read/write operations. When set toCUSTOM, the device driver does not modify current tape drive setting. The custom setting is intended for applications using system-managed encryption to control write encryption without device driver intervention. The parameter is set to “CUSTOM” by default.
Note: If sys_encryption_write is set toON, an application can not open a tape drive using the append mode.
To make a global setting to enable SME in IBMtape.conf:
sys_encryption_write=1; # System Encryption for Write Commands at BOP To enable SME for a particular target:
name=″IBMtape″ class=″scsi″ target=0 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0 sys_encryption_write=1;
To disable SME in a particular target: name=″IBMtape″ class=″scsi″ target=0 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0 sys_encryption_proxy=0;
Querying Tape Drive Configuration
There is atapeutilcommand available for encryption to query tape drive encryption settings.
The current tape drive encryption settings can be queried using the tapeutil menu with the option “Get Drive Encryption Settings” or the command line “tapeutil –f /dev/rmt/device_special_file encryption”.
Note: See “Solaris System - Tape Utility Program (tapeutil)” on page 397 for information on thetapeutilapplication.
Following is an example of a correct tape drive configuration with
sys_encryption_write set to “on”. If the sys_encryption_write parameter is set to “no”, then the tape drive “Encryption State” is Off.
# tapeutil -f /dev/rmt/38stn encryption
GET_ENCRYPTION_STATE command succeeded. Encryption settings:
Encryption Capable ... Yes Encryption Method .... System Encryption State... ON