Using Advanced Tape Services
B3936-90032 January 1999 © Copyright 1999 Hewlett-Packard Company
Legal Notices The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Copyright © 1999 Hewlett-Packard Company. This document contains information which is protected by copyright. All rights are reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Corporate Offices: Hewlett-Packard Co. 3000 Hanover St. Palo Alto, CA 94304
Use, duplication or disclosure by the U.S. Government Department of Defense is subject to restrictions as set forth in paragraph (b)(3)(ii) of the Rights in Technical Data and Software clause in FAR 52.227-7013. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2). Use of this manual and flexible disc(s), compact disc(s), or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited. A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office.
2
Contents
1. Overview of Advanced Tape Services ATS and Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 ATS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 ATS Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 ATS Configuration Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 ATS Command Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 2. Planning Your ATS Configuration Planning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Advanced Tape Services Configuration Worksheet . . . . . . . . . . . . . . . . .24 MC/ServiceGuard Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Advanced Tape Services ASCII Configuration File Content . . . . . . . . . .27 Global Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Tape Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 No Hardware Match Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 3. Configuring ATS Devices Creating the Advanced Tape Services ASCII Configuration File . . . . . .36 Editing the Advanced Tape Services ASCII Configuration File . . . . . . .40 Verifying the Advanced Tape Services ASCII Configuration File. . . . . .43 Applying the Advanced Tape Services ASCII Configuration File. . . . . .46 4. Maintaining Advanced Tape Services Devices Viewing the Advanced Tape Services Configuration . . . . . . . . . . . . . . . .50 Viewing Shared Tape Device Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Updating the Cluster Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
3
Contents
Replacing or Updating Advanced Tape Services Configured Devices . . 58 Reclaiming Advanced Tape Services Devices . . . . . . . . . . . . . . . . . . . . . 63 Removing ATS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 A. Advanced Tape Services Man Pages ats Man Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 atsconf Man Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 stapplyconf Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 stcheckconf Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 stdeleteconf Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 stgetconf Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 stquerycl Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 streclaim Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 stviewcl Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 B. Troubleshooting Advanced Tape Services Reviewing the System Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Sample System Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Reviewing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Using the stgetconf Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 C. Advanced Tape Services Messages cmtaped Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 stapplyconf Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 stcheckconf Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4
Contents
stdeleteconf Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 stgetconf Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 stquerycl Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 streclaim Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 stviewcl Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 D. Blank Advanced Tape Services Planning Worksheets Advanced Tape Services Configuration Worksheet . . . . . . . . . . . . . . . . .96
5
Contents
6
Printing History Table 1 Printing Date January 1999
Part Number B3936-90032
Edition Edition 1
This edition documents installing and configuring Advanced Tape Services. This printing date and part number indicate the current edition. The printing date changes when a new edition is printed. (Minor corrections and updates which are incorporated at reprint do not cause the date to change.) The part number changes when extensive technical changes are incorporated. New editions of this manual will incorporate all material updated since the previous edition. HP Printing Division: High Performance Systems Division Hewlett-Packard Co. 19111 Pruneridge Ave. Cupertino, CA 95014
7
8
Preface This guide describes how to plan for and configure the Advanced Tape Services (ATS) to share tape devices and tape library robotic devices between nodes on an MC/ServiceGuard cluster. The chapters are as follows: • “Overview of Advanced Tape Services,” which describes the functions of ATS. • “Planning Your ATS Configuration,” which describes general configuration and MC/ServiceGuard configuration requirements for using ATS. • “Configuring ATS Devices,” which describes how to configure ATS on your MC/ServiceGuard cluster. • “Maintaining Advanced Tape Services Devices,” which describes how to view, modify, and understand your ATS configuration. Related Publications
The following documents contain additional related information: • Peter Weygant, Clusters for High Availability: A Primer of HP-UX Solutions (ISBN 0-13-494758-4). HP Press: Prentice Hall, Inc., 1996. • Managing MC/ServiceGuard (HP Part Number B3936-90024). • Hewlett-Packard Fibre Channel SCSI Multiplexer: Service and User Manual (HP A3308-90005) • HP OpenView IT/Operations Administrators Task Guide (P/N B4249-90003) • Configuring OPS Clusters with MC/LockManager (HP Part Number B5158-90019). • Managing Highly Available NFS (HP Part Number B5125-90001) • Managing Systems and Workgroups (HP Part Number B2355-90157) • http://docs.hp.com/hpux/ha external web site for information about Hewlett-Packard’s high-availability technologies where you can find documents such as this document and Writing Monitors for the Event Monitoring Service (EMS)
9
Problem Reporting
If you have any problems with the software or documentation, please contact your local Hewlett-Packard Sales Office or Customer Service Center.
10
Overview of Advanced Tape Services
1
Overview of Advanced Tape Services This manual explains how to configure and use shared tape devices in an MC/ServiceGuard cluster. The Advanced Tape Services (ATS) facility allows a minimum two-node, up to a maximum four-node cluster to share stand-alone magnetic tape devices and/or tape library robotic devices. This chapter provides an overview of ATS facility features and configuration. Topics include: • ATS and Cluster Configuration • ATS Features • ATS Supported Devices • ATS Configuration Samples • ATS Command Usage
Chapter 1
11
Overview of Advanced Tape Services ATS and Cluster Configuration
ATS and Cluster Configuration MC/ServiceGuard’s ATS extends the High Availability (HA) capability of the cluster to include shared tape devices and tape library robotic devices that can be connected to more than one node in the cluster. Shared tape devices can be used for backups of files activated on more than one cluster node. This means that even after a package fails over to another node, a backup of the package data continues or restarts on the alternate node. You can configure shared tape devices only between any two nodes in a cluster. The maximum cluster size in a shared tape configuration is currently four nodes. While any tape device can be configured for shared use in the cluster, the greatest benefit is obtained with high end devices such as the HP DLT 4/48 tape library, which has four separate tape drives and a robotic device (arm) that loads and unloads up to 48 8-GB cartridges. Device files corresponding to each tape or library robotic mechanism are created and written to an ATS ASCII configuration file. As is done in MC/ServiceGuard, ATS uses this file to keep track of the devices configured in the cluster. The content of this file is described in detail in the chapter “Planning Your ATS Configuration.”
12
Chapter 1
Overview of Advanced Tape Services ATS Features
ATS Features ATS generates new device files with the same cluster-wide unique name on all nodes that are connected to any shared tape device. This includes tape library robotic devices and individual tape devices. With unique cluster-wide device names for each shared device, applications can use the same device file name for a particular device. This way the device name is the same no matter what node the application is on. ATS provides automatic reclaiming. That is, shared devices are made available to applications on other cluster nodes automatically after a system failure of the node that owns an ATS shared device. ATS provides exclusive allocation and access between devices. Only one process on any one host has access to a particular device file at any particular time.
Chapter 1
13
Overview of Advanced Tape Services ATS Supported Devices
ATS Supported Devices ATS supports the following devices: • Magnetic tape devices that are supported with the Fibre Channel SCSI MUX. • Tape library robotic devices that are supported with the Fibre Channel SCSI MUX. Refer to the /etc/cmcluster/shared tape/ats_tapelibs file for a complete list of supported devices. NOTE
You can modify the ats_tapelibs file to add newly supported devices, however this file is overwritten and automatically updated upon each update of MC/ServiceGuard or ATS. Any changes you have made to the file are lost.
14
Chapter 1
Overview of Advanced Tape Services ATS Configuration Samples
ATS Configuration Samples ATS configurations have a range of possibilities. These include: • One magnetic tape device shared between the nodes of a two-node cluster. • One tape library with four tape devices shared between the nodes of a two-node cluster. • One magnetic tape device and one tape library with four tape devices shared among the nodes of a four-node cluster. • Four tape libraries with four tape devices each shared among the nodes of a four-node cluster.
Chapter 1
15
Overview of Advanced Tape Services ATS Configuration Samples Figure 1-1 illustrates an HP DLT 4/48 tape library being shared among a two-node cluster. Figure 1-1
Two Node Cluster with ATS Configuration node 1
node 2 Pkg A disks
Pkg B
Pkg A Pkg A mirrors
Pkg B disks Pkg B mirrors
fibre channel connections
FC MUX
SCSI bus connections Shared Tape Library HP 4/48
Robotic Arm Tape Drives
HUB
16
Chapter 1
Overview of Advanced Tape Services ATS Configuration Samples Figure 1-2 shows a four-node cluster with a number of HP DLT 4/48 libraries. Four Node Cluster with ATS Configuration
SCSI bus connections
FC MUX
fibre channel connections
node 2
node 1
Pkg B
Pkg C
Pkg D
FC MUX
Pkg A
FC MUX
Figure 1-2
node 3
Shared Tape Libraries HP 4/48
node 4
FC MUX
HUB
Chapter 1
17
Overview of Advanced Tape Services ATS Command Usage
ATS Command Usage The following is a list of ATS functions and their associated ATS commands. To create or update the ATS configuration file, use the stquerycl command. • This command scans all the nodes in the cluster for shared tape devices and shared library robotic devices. • It then generates an ATS configuration file, assigning cluster-wide identifiers to each shared device. • If stquerycl is executed on a cluster with an existing ATS configuration, the existing ATS configuration is merged, device by device, with any newly detected hardware. • An established MC/ServiceGuard configuration is required for this command to function. • Refer to “Creating the Advanced Tape Services ASCII Configuration File” on page 36 or “Updating the Cluster Configuration” on page 54. To verify the ATS configuration information, use the stcheckconf command. • This command reads the ATS configuration file and verifies it against the MC/ServiceGuard configuration file. • Refer to “Verifying the Advanced Tape Services ASCII Configuration File” on page 43 or “Viewing the Advanced Tape Services Configuration” on page 50. To verify and apply your ATS configuration, use the stapplyconf command. • This command reads the ATS configuration file and verifies it against the MC/ServiceGuard configuration file. • If the verification is successful, the MC/ServiceGuard configuration is updated with the ATS configuration information. • This updated configuration is distributed to all nodes in the cluster. • Refer to “Applying the Advanced Tape Services ASCII Configuration File” on page 46. 18
Chapter 1
Overview of Advanced Tape Services ATS Command Usage To view the ATS configuration portion of the MC/ServiceGuard configuration file, use the stgetconf command. • This command retrieves the ATS configuration information from the MC/ServiceGuard configuration file. • Refer to “Viewing the Advanced Tape Services Configuration” on page 50. To view the current status of the shared devices configured on the cluster, use the stviewcl command. • This command uses the ATS configuration configured on the cluster and displays the status of the configured shared tape devices and shared library robotic devices. • Refer to “Viewing Shared Tape Device Status” on page 52. To reclaim a shared tape device for use by the cluster, use the streclaim command. • This command reclaims the specified device for use by the cluster. • Refer to “Reclaiming Advanced Tape Services Devices” on page 63. To remove ATS configuration from your MC/ServiceGuard configuration, use the stdeleteconf command. • This command deletes the ATS portion from the MC/ServiceGuard configuration file. • This command does not remove ATS device special files or associated alias files. • Refer to “Removing ATS Configuration” on page 65.
Chapter 1
19
Overview of Advanced Tape Services ATS Command Usage
20
Chapter 1
Planning Your ATS Configuration
2
Planning Your ATS Configuration This chapter describes planning considerations and requirements for using Advanced Tape Services in an MC/ServiceGuard cluster. The sections in the chapter are as follows: • Planning Overview • Advanced Tape Services Configuration Worksheet • MC/ServiceGuard Configuration • Advanced Tape Services ASCII Configuration File Content
Chapter 2
21
Planning Your ATS Configuration Planning Overview
Planning Overview Planning for sharing tape devices consists of: • Determining your purpose for sharing tape devices: • Are cost savings a critical need? Then by using ATS and sharing tape devices you can reduce the number of tape devices required to provide backup services for nodes in a cluster. Refer to Figure 1-1 on page 16 for an illustration of a two-node cluster sharing one tape device. • Is High Availability coverage your critical need? Then by using ATS and assigning two nodes to share each tape device and each tape library robotic device to each node you can ensure that your backup processes are always operational and previous backup data is always accessible. Refer to Figure 1-2 for an illustration of four tape libraries shared in a High Availability pattern among a four-node cluster. • Verifying prerequisites: • Cluster requirements—the nodes that will be sharing the tape devices are in the same cluster • Software requirements—MC/ServiceGuard is installed and configured on all nodes of the cluster • Hardware requirements—the nodes and the tape device support Fibre Channel MUX connections. Figure 2-1 shows one way to represent your shared tape configuration. This represents an ATS configuration set up for High Availability coverage for your shared tape devices. The diagram includes user assigned alias names (library_1) and the ATS assigned cluster-wide unique device names (sac10). The standard ATS naming convention assigns numbers as follows: • Tape libraries, or more specifically their library robotic arm devices are assigned a device name, /dev/rac/sac# • Tape devices, whether stand-alone or contained within a tape library are assigned device names, /dev/rmt/st#m
22
Chapter 2
Planning Your ATS Configuration Planning Overview • The number value (#) increments for each device, tape or library, it encounters ATS Configuration and Naming Conventions library robotic: sac0: library_1 tape drive 1: st1m: lib1_dev1 tape drive 2: st2m: lib1_dev2 tape drive 3: st3m: lib1_dev3 tape drive 4: st4m: lib1_dev4
Cluster Name: my_cluster Individual Tape Devices Library autochanger robotic arm FC MUX
Component
heckle
node 2 jeckle
node 3 hansel
node 4 gretel
node 1
FC MUX library robotic: sac15: library_4 tape drive 1: st16m: lib4_dev1 tape drive 2: st17m: lib4_dev2 tape drive 3: st18m: lib4_dev3 tape drive 4: st19m: lib4_dev4
FC MUX
ATS Supplied Unique Name
User Assigned Alias
FC MUX
Figure 2-1
library robotic: sac5: library_2 tape drive 1: st6m: lib2_dev1 tape drive 2: st7m: lib2_dev2 tape drive 3: st8m: lib2_dev3 tape drive 4: st9m: lib2_dev4
library robotic: sac10: library_3 tape drive 1: st11m: lib3_dev1 tape drive 2: st12m: lib3_dev2 tape drive 3: st13m: lib3_dev3 tape drive 4: st14m: lib3_dev4
HUB
Chapter 2
23
Planning Your ATS Configuration Advanced Tape Services Configuration Worksheet
Advanced Tape Services Configuration Worksheet The first part of the following worksheet applies to the entire cluster, use one per cluster. The following page is for listing all the ATS configured devices, make copies and use as many as needed.
Cluster Name/ID: my_cluster Maximum number of reclaim processes allowed (2-100): 2 Maximum number of display processes allowed (2-100): 2 Minimum time between status updates (1-3600): n/a Node 1 Name/ID: heckle Node 2 Name/ID: jeckle Node 3 Name/ID: hansel Node 4 Name/ID: gretel Device Name/ID: /dev/rac/sac5 Alias: library_2
Hide: Yes/No NO
Description: Tape library second floor Type:
Autochanger X
Node: gretel
Tape
Other:
Node: jeckle
Device Name/ID: /dev/rmt/st6m Alias: lib2_dev1
Hide: Yes/No NO
Description: First tape device library 2 Type:
Autochanger
Node: gretel
24
Tape X
Other:
Node: jeckle
Chapter 2
Planning Your ATS Configuration Advanced Tape Services Configuration Worksheet
Device Name/ID: /dev/rmt/st7m Alias: lib2_dev2
Hide: Yes/No NO
Description: Second tape device library 2 Type:
Autochanger
Node: gretel
Tape X
Other:
Node: jeckle
Device Name/ID: /dev/rmt/st8m Alias: lib2_dev3
Hide: Yes/No NO
Description: Third tape device library 2 Type:
Autochanger
Node: gretel
Tape X
Other:
Node: jeckle
Device Name/ID: /dev/rmt/st9m Alias: lib2_dev4
Hide: Yes/No NO
Description: Fourth tape device library 2 Type:
Autochanger
Node: gretel
Tape X
Other:
Node: jeckle
Device Name/ID: /dev/rac/sac10 Alias: library_3
Hide: Yes/No NO
Description: Tape library systems group Type:
Autochanger X
Node: hansel
Tape
Other:
Node: jeckle
Device Name/ID: /dev/rmt/st11m Alias: lib2_dev1
Hide: Yes/No NO
Description: First tape device library 3 Type:
Autochanger
Node: hansel
Chapter 2
Tape X
Other:
Node: jeckle
25
Planning Your ATS Configuration MC/ServiceGuard Configuration
MC/ServiceGuard Configuration You can set up for shared tape devices as part of your MC/ServiceGuard configuration process. The minimum MC/ServiceGuard configuration steps that need to be completed prior to configuring the Advanced Tape Services tool are described in detail in the Managing MC/ServiceGuard manual: • Preparing Your System • Installing MC/ServiceGuard • Creating the Logical Volume Infrastructure • Configuring the Cluster—executing the cmquerycl command • Verifying the Cluster Configuration—executing the cmcheckconf command • Distributing the Binary Configuration File—executing the cmapplyconf command
26
Chapter 2
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content
Advanced Tape Services ASCII Configuration File Content The ATS configuration file is divided into sections as follows. • Global Information • Tape Device Information • No Hardware Match Information Refer to the atsconf man page for additional information about the ATS ATS configuration file.
Global Information Global information is at the top of the file. It lists information that applies to the entire cluster. Most of these fields are editable. The global information section fields are: • CLUSTER_NAME The MC/ServiceGuard cluster where the configuration is generated. This is a non-editable field. • Timestamp Date and time when configuration file is written. There is no other significance for this information. This is a non-editable field. • MAX_NUM_RECLAIM_PROCS The number of reclamation assistant processes which will be created on each cluster node for automatic shared tape device reclamation. The parameter can be changed to optimize performance. Recommended value: The largest number of shared tape devices and library robotics on any cluster node divided by 2. • MAX_NUM_DISPLAY_PROCS The number of assistant processes which will be created on each cluster node for display of shared tape device information.The parameter can be changed to optimize performance.
Chapter 2
27
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content Recommended value: The largest number of shared tape devices and library robotics on any cluster node divided by 2. • MAX_TIME_FOR_STATUS_UPDATE Reserved. Accepts values from 1 to 3600, but performs no function at this time. Figure 2-2 shows a sample portion of the global information portion of the ATS configuration file. Figure 2-2
Sample Advanced Tape Services ASCII Configuration File, Global Information # # # # #
******************************************************************** ************ TAPE SHARING CLUSTER CONFIGURATION FILE *************** ***** For complete details about cluster parameters and how to ***** ***** set them, consult the stquerycl(1m) and atsconf(4) man pages * ********************************************************************
CLUSTER_NAME
my_cluster
# Generated
Tue Nov 10 13:09:01 1998
# The following parameters can be changed to optimize performance of # automatic reclamation and stviewcl. These are the number of assistant # processes which will be created on each node in the cluster. MAX_NUM_RECLAIM_PROCS MAX_NUM_DISPLAY_PROCS
2 2
(range is 2-100) (range is 2-100)
# The following parameter specifies the minimum time (in seconds) between # status queries for stviewcl. MIN_TIME_FOR_STATUS_UPDATE 1
(range is 1-3600)
Tape Device Information Tape device information is shownfor each tape device found. This includes stand-alone tape drive, tape library robotic devices, and the individual tape drives in a tape library device. The term autochanger refers to the robotic arm device of the tape library. Selected information can be edited.
28
Chapter 2
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content
Editable Device Entry Information The device entry information that can be edited is: • DEVICE_NAME The cluster-wide identifier (numeric embedded in DEVICE_NAME) may be modified but must remain unique across the cluster. This name is autogenerated by stquerycl. The format is: • /dev/rmt/st#m for tape devices • /dev/rac/sac# for library devices Use this ability to modify the cluster wide identifier automatically generated when you have replaced a tape device. An stquerycl will find the new device and assign it a new cluster-wide identifier number. It will place the old device under the No Hardware Match listing. If you want to use the cluster-wide device name you have already set up for the previous device, change the new device name (st#m) to the old device name and delete the No Hardware Match in the ATS configuration file. • HIDE_DEVICE The HIDE_DEVICE flag can be modified. If no is changed to yes the device will not be automatically reclaimed and its status will not be reported. A possible use for this option is when a device is temporarily being used by a system that is not an active cluster member. This can be advantageous for system data recovery when the system cannot or should not be an active node in the cluster. When the HIDE_DEVICE option is yes, the device will not display when the stviewcl is executed, unless the -a option is specified. The HIDE_DEVICE flag is ignored by the streclaim command. The HIDE_DEVICE flag is set to YES if a device is shareable but not configured to be automatically reclaimed at this time. If at a later date, the device should again be automatically reclaimed, the HIDE_DEVICE flag must be set to NO. • ALIAS_NAME An alias name can be added at the ALIAS_NAME field of this file for each specific device. Remove the # and add an alias name. Multiple aliases for each specific device is allowed.
Chapter 2
29
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content ATS creates device files for each alias in the following format: /dev/rmt/alias_name for tape devices /dev/rac/alias_name for library devices Specify alias_name to name the device something that might be more meaningful to you. For example: HP_DLT_7. Alias names display in the stviewcl, stquerycl, stcheckconf, and stgetconf output. • DESCRIPTION The DESCRIPTION can be added to this file for each specific device. Remove the # and add any description desired. Multiple lines are allowed so you can add as much information as you need. Each line requires the DESCRIPTION token. Suggested descriptions might include location or users of the device. Description information displays in the stviewcl, stquerycl, stcheckconf, and stgetconf output. Figure 2-3 continues with the previous sample ATS configuration file to show the editable portion of one tape device entry. Figure 2-3
Sample Advanced Tape Services ASCII Configuration File, Editable Tape Device Information # The following device information was returned by stquerycl(1m). # The cluster-wide identifier (numeric embedded in DEVICE_NAME) # may be modified but must remain unique across the cluster. DEVICE_NAME
/dev/rmt/st6m
# The following flag can be modified. If "no" is changed to "yes" the device # will not be reclaimed and its status will not be reported. HIDE_DEVICE
no
# The following information can be added to this file for the above device. # Remove the "#" and add alias name. Multiple aliases are allowed. # ALIAS_NAME # ALIAS_NAME
/dev/rmt/meaningful_name /dev/rmt/meaningful_name
# The following information can be added to this file for the above device. # Remove the "#" and add any description desired. Multiple lines are allowed. # DESCRIPTION # DESCRIPTION
30
This is a commented line of device description. This is another commented line of device description.
Chapter 2
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content
Non-Editable Device Entry Information The device entry information that cannot be edited is obtained by the command by various searches of the current active cluster. It includes various physical and logical addresses and identification numbers: • DEVICE_TYPE This is either tape or autochanger. Autochanger indicates a tape library robotic device. • FCMUX_ID Identifier for the Fibre Channel SCSI Multiplexer (MUX) to which the shared devices is attached. • BUS Shared device hardware path element. • TARGET Shared device hardware path element. • LUN Shared device hardware path element. • DEVICE_ID Shared device identification. • VENDOR Shared device vendor/manufacturer. • PRODUCT_ID Shared device vendor assigned identification. • NODE_NAME For each tape device there will be up to two entries for node name, one for each node the tape device is connected to and shared between. • MAJOR_NUMBER For each tape device there will be up to two entries for major number, one for each node the tape device is connected to and shared between. • MINOR_NUMBER
Chapter 2
31
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content For each tape device there will be up to two entries for minor number, one for each node the tape device is connected to and shared between. Figure 2-4 continues with the previous sample ATS configuration file to show the non-editable portion of one tape device entry. Figure 2-4
Sample Advanced Tape Services ASCII Configuration File, Non-Editable Tape Device Information # DO NOT ALTER any of the remaining data for this device entry! DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 137 28 240 27 0 5 0 1 128 2 2 0 0 0 0 137 86 36 85 243 163 32 100 QUANTUM DLT7000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x175000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
heckle 205 0x145000
No Hardware Match Information Tape device information is included in the file for each tape device previously known but currently not found. If a device is unavailable to the current active cluster, it will display as No Hardware Match for the current active cluster. All the standard tape device information is included, a note is added, and it is placed at the end of the file. This entry can be completely removed or retained for reference as you choose. In some cases, the device is only temporarily unavailable, for example if it is powered off or if the device has been replaced. If a device is listed under No Hardware Match and later it returns to the current cluster, another execution of stquerycl will return it to its active state. Figure 2-5 shows an example of the No Hardware Match header text. The balance of the information in the entry is the same as a typical tape device entry.
32
Chapter 2
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content Figure 2-5
Sample Advanced Tape Services ASCII Configuration File, No Hardware Match Information # **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE **** # The following device entry does not match the hardware scan. # This entry will be ignored (you may delete this ENTIRE entry). # The following device information was returned by stquerycl(1m). # The cluster-wide identifier (numeric embedded in DEVICE_NAME) # may be modified but must remain unique across the cluster. DEVICE_NAME
/dev/rmt/st16m
# The following flag can be modified. If "no" is changed to "yes" the device # will not be reclaimed and its status will not be reported. HIDE_DEVICE
no
# The following information can be added to this file for the above device. # Remove the "#" and add alias name. Multiple aliases are allowed. # ALIAS_NAME # ALIAS_NAME
/dev/rmt/meaningful_name /dev/rmt/meaningful_name
# The following information can be added to this file for the above device. # Remove the "#" and add any description desired. Multiple lines are allowed. # DESCRIPTION # DESCRIPTION
This is a commented line of device description. This is another commented line of device description.
# DO NOT ALTER any of the remaining data for this device entry! DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 17 145 6 45 0 2 0 1 128 2 2 0 0 0 0 208 217 190 20 5 12 229 249 Quantum DLT4000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
gretel 205 0x002000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x002000
# **** NOTE
Chapter 2
End of entry with no hardware match
NOTE ****
33
Planning Your ATS Configuration Advanced Tape Services ASCII Configuration File Content
34
Chapter 2
Configuring ATS Devices
3
Configuring ATS Devices This chapter explains how to configure and use Advanced Tape Services. The basic steps are described in detail in the following sections: • Creating the Advanced Tape Services ASCII Configuration File • Editing the Advanced Tape Services ASCII Configuration File • Verifying the Advanced Tape Services ASCII Configuration File • Applying the Advanced Tape Services ASCII Configuration File To view the configuration, see “Viewing the Advanced Tape Services Configuration” on page 50.
Chapter 3
35
Configuring ATS Devices Creating the Advanced Tape Services ASCII Configuration File
Creating the Advanced Tape Services ASCII Configuration File Use the stquerycl command to: • Identify shared tape devices and shared tape library robotic devices in the cluster. • Generate an ATS configuration file for the cluster. This includes automatically assigning cluster-wide unique identifiers to each shared device. The cluster-wide identifiers for each shared device may change with each execution of the stquerycl command until the configuration is applied to the cluster with a stapplyconf command, described in “Applying the Advanced Tape Services ASCII Configuration File” on page 46. To create the ATS configuration file: 1. Create the cluster, by executing the MC/ServiceGuard commands: • cmquerycl • cmcheckconf • cmapplyconf Refer to the Managing MC/ServiceGuard manual for information on using these commands and setting up your cluster. The cluster does not need to be started, but it does need to be configured. 2. Create the ATS configuration file, by typing: stquerycl -C filename
For example: stquerycl -C /etc/cmcluster/my_cluster_ats.ascii
-C filename is a required option if you want to save the output for editing and/or applying to your MC/ServiceGuard cluster. It specifies the location and name of the ATS configuration file to be created, in this example: /etc/cmcluster/my_cluster_ats.ascii
36
Chapter 3
Configuring ATS Devices Creating the Advanced Tape Services ASCII Configuration File This example creates an ATS configuration file in the default cluster configuration directory, /etc/cmcluster. The file name can be any valid filename, but this example references the cluster name, my_cluster, and indicates that the file is an ATS configuration file. When you create the ATS configuration file cluster information is filled in, including ATS assigned device names. Aliases and Description fields are not filled in. Edit the cluster characteristics as needed to define the desired device sharing parameters. CAUTION
Each device contains node and device specific identification information. Do not edit this information. The information is marked in the file with the header: DO NOT ALTER any of the remaining data for this device entry!
Other stquerycl command options include: -v displays the configuration file information on screen in addition to writing the configuration file. -k tells ATS to get the I/O data from the kernel data structures rather than by performing a physical scan of the hardware. Using this option saves command execution time, but could overlook any newly attached devices since the ATS configuration file was created. Therefore, remember the following: • Do not use the -k option if the hardware has been changed since the last time you ran stquerycl. • Do not use it with the first stquerycl or stcheckconf command. ATS must check the current cluster hardware to be accurate. But subsequently, in the same session, it is not necessary to check the cluster hardware with each command. 3. Review the content of the ATS configuration file. Figure 3-1 shows the global information and part of the first device entry.
Chapter 3
37
Configuring ATS Devices Creating the Advanced Tape Services ASCII Configuration File
Global Information Section
Figure 3-1
Sample ATS ASCII Configuration File # # # # #
******************************************************************** ************ TAPE SHARING CLUSTER CONFIGURATION FILE *************** ***** For complete details about cluster parameters and how to ***** ***** set them, consult the stquerycl(1m) and atsconf(4) man pages * ********************************************************************
CLUSTER_NAME
my_cluster
# Generated
Tue Nov 10 13:09:01 1998
# The following parameters can be changed to optimize performance of # automatic reclamation and stviewcl. These are the number of assistant # processes which will be created on each node in the cluster.
Editable Entries
MAX_NUM_RECLAIM_PROCS MAX_NUM_DISPLAY_PROCS
(range is 2-100) (range is 2-100)
# The following parameter specifies the minimum time (in seconds) between # status queries for stviewcl. MIN_TIME_FOR_STATUS_UPDATE
Editable Information Section
1
(range is 1-3600)
# The following device information was returned by stquerycl(1m). # The cluster-wide identifier (numeric embedded in DEVICE_NAME) # may be modified but must remain unique across the cluster. DEVICE_NAME
Typical entry for each tape device
2 2
/dev/rmt/st16m
# The following flag can be modified. If "no" is changed to "yes" the device # will not be reclaimed and its status will not be reported. HIDE_DEVICE
no
# The following information can be added to this file for the above device. # Remove the "#" and add alias name. Multiple aliases are allowed. # ALIAS_NAME # ALIAS_NAME
/dev/rmt/meaningful_name /dev/rmt/meaningful_name
# The following information can be added to this file for the above device. # Remove the "#" and add any description desired. Multiple lines are allowed. # DESCRIPTION # DESCRIPTION
Non-Editable Information Section
This is a commented line of device description. This is another commented line of device description.
# DO NOT ALTER any of the remaining data for this device entry! DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 137 28 240 27 0 5 0 1 128 2 2 0 0 0 0 137 86 36 85 243 163 32 100 QUANTUM DLT7000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x175000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
heckle 205 0x145000
38
Chapter 3
Configuring ATS Devices Creating the Advanced Tape Services ASCII Configuration File When you execute the stquerycl command with the -C option, the ATS configuration file is created. You have the option to modify selected information in this file. This file contains the following information: • Global Information Global information is reference information about the cluster. Selected fields in this section can be edited. • Entry for each tape device found Tape device entries include information that can be edited, such as alias names and hide options and information that cannot be edited, such as physical and logical identification numbers and associated node connect information. • Entry for each tape library robotic device (autochanger) found Tape library robotic device entries include information that can be edited, such as alias names and hide options and information that cannot be edited, such as physical and logical identification numbers, associated library robotic connect information, and associated node connect information. • Entry for all devices where no hardware match was found At the time that stquerycl is executed, previously defined shareable device entries may not be available. If this occurs the device information is identified as No Hardware Match and noted in the ATS configuration file. The specific file entry is: # The following device entry does not match the hardware scan.
No Hardware Match entries can be removed in their entirety as desired. Refer to the atsconf man page for lists of the definitions of all the parameters that appear in this file. Many are also described in this manual. Modify your my_cluster_ats.ascii file to fit your requirements, using the data on the Advanced Tape Services configuration worksheet.
Chapter 3
39
Configuring ATS Devices Editing the Advanced Tape Services ASCII Configuration File
Editing the Advanced Tape Services ASCII Configuration File Editing the ATS configuration file is not required. To proceed directly with the ATS configuration, continue to the section, “Verifying the Advanced Tape Services ASCII Configuration File” on page 43. To edit the ATS configuration file: 1. Open the file in any text editor to modify the text. In the configuration file, keywords are separated from definitions by white space. Comments are permitted, and must be preceded by a pound sign (#) in the far left column. 2. Modify global information block fields as desired. The editable fields include: • MAX_NUM_RECLAIM_PROCS • MAX_NUM_DISPLAY_PROCS • MIN_TIME_FOR_STATUS_UPDATE time.)
(Reserved. Not used at this
To edit these fields, replace the specified value. Refer to “Advanced Tape Services ASCII Configuration File Content” on page 27 for information about these fields. 3. Add alias names, as desired, for each device. a. Find the device entry and its alias name location. For example: # ALIAS_NAME
/dev/rmt/meaningful_name
b. Remove the pound sign (#) comment indicator. c. Replace the meaningful_name text with the alias name. An alias name has to be a normal file name. It has to be unique. It has to reside in the same directory as the normal device file. The normal device file locations are: • /dev/rmt if the device is a magnetic tape • /dev/rac if the device is an autochanger
40
Chapter 3
Configuring ATS Devices Editing the Advanced Tape Services ASCII Configuration File An example of an alias name is: /dev/rmt/HP_DLT_7 4. Add description information, as desired, for each device. a. Find the device entry and its description field location. For example: # DESCRIPTION This is a commented line of device description.
The contents of the DESCRIPTION field display in the ATS configuration file, and the verbose outputs for the stviewcl and stgetconf commands. b. Remove the pound sign (#) comment indicator. c. Replace the text following the DESCRIPTION field name with your informative text. An example of a description is: This is the tape device in the second floor, right corner. 5. Specify hidden devices, as desired. Hidden devices are not displayed in the stviewcl command output unless the -a option is included in the command string. When a node using hidden devices halts without first releasing the devices, the hidden devices need to be manually reclaimed. a. Find the device entry and its hidden flag field. For example: HIDE_DEVICE
no
b. Change the HIDE_DEVICE setting to yes. 6. Change ATS generated device names. When stquerycl creates an ATS configuration file, it assigns unique, system-wide device names to all devices in the cluster. When a device is replaced you might want to rename the new device to the old device name. a. Find the device entry and its device name field. For example: DEVICE_NAME
/dev/rmt/st21m
b. Change the numeric portion of the name only. For example, if the old device’s name was /dev/rmt/st0m and the new device is named st21m, change the st21m to st0m. 7. Remove No Hardware Match found entries, as desired. Chapter 3
41
Configuring ATS Devices Editing the Advanced Tape Services ASCII Configuration File Any device that was previously known to the cluster but was unavailable to the cluster at the time the stquerycl scan was performed, is listed in the ‘no hardware match’ section of the ATS configuration file. An unavailable device is one which is not connected or is powered down and it is still contained in kernel tables on any node in the cluster. a. Before removing a No Hardware Match found entry, ensure that the referenced device is not just temporarily unavailable to the cluster. b. Delete the lines from the # **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE ****
all the way through to the # **** NOTE End of entry with no hardware match NOTE ****
8. Save the file. 9. Proceed to the next section, “Verifying the Advanced Tape Services ASCII Configuration File”.
42
Chapter 3
Configuring ATS Devices Verifying the Advanced Tape Services ASCII Configuration File
Verifying the Advanced Tape Services ASCII Configuration File Anytime you have edited the ATS configuration file, it is good practice to verify the changes. Use the stcheckconf command to verify the content of the file. This command reads the configuration file specified and verifies the contents against the MC/ServiceGuard cluster. It checks the following: • Each device and its associated identification numbers and addresses are valid and active in the cluster • Each tape device or tape library robotic device is shared between no more than two active nodes in the cluster Verify a newly created or modified ATS configuration file by typing: stcheckconf -C /etc/cmcluster/stape.ascii
-C is required. It specifies the location and name of the ATS configuration file to be verified, in this example, /etc/cmcluster/stape.ascii. Other command options include: -v indicates the verbose option. This displays detailed information on modifications to the configuration for each device on the screen as it is verified. If no modifications were made to the ATS configuration file no detailed information displays. -k tells ATS to get the I/O data from the kernel data structures rather than by performing a physical scan of the hardware. Using this option saves command execution time, but could overlook any newly attached devices since the ATS configuration file was created, therefore: • Do not use the -k option if the hardware has been changed since the last time you ran stquerycl. • Do not use it with the first stquerycl or stcheckconf command. ATS must check the current cluster hardware to be accurate. But subsequently, in the same session, it is not necessary to check the cluster hardware with each command. The following is a sample of stcheckconf output with no changes made.
Chapter 3
43
Configuring ATS Devices Verifying the Advanced Tape Services ASCII Configuration File Beginning verification of ATS configuration. stcheckconf completed with no errors.
The verbose option applies, but only displays information for devices that have been modified. The following is a partial sample of stcheckconf output with changes made.
44
Chapter 3
Configuring ATS Devices Verifying the Advanced Tape Services ASCII Configuration File
Beginning verification of ATS configuration.
Change Comments
Standard Device Entry Data
Change Comments
Standard Device Entry Data
# ============================================================= # DEVICE_NAME /dev/rmt/st6m NO STATUS HIDE_DEVICE ALIAS_NAME
NO /dev/rmt/HP_DLT_6
DESCRIPTION
This is a tape for everybody else.
DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 38 91 125 165 0 1 0 1 128 2 2 0 0 0 0 208 217 190 20 61 83 108 76 Quantum DLT4000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
gretel 205 0x031000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
jeckle 205 0x1e1000
# ----------------------------------------------------------- # An alias was added. (ATS 4.30) The description was modified. (ATS 4.31) # =========================================================== # DEVICE_NAME /dev/rmt/st7m NO STATUS HIDE_DEVICE ALIAS_NAME
YES /dev/rmt/HP_DLT_7
DESCRIPTION
This is my special tape device.
DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 38 91 125 165 0 2 0 1 128 2 2 0 0 0 0 208 217 190 20 113 16 249 120 Quantum DLT4000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
gretel 205 0x032000
NODE_NAME jeckle MAJOR_NUMBER 205 MINOR_NUMBER 0x1e2000 # ------------------------------------------------------------ # This device will now be reclaimed. (ATS 4.27) An alias was added. (ATS 4.30) The description was modified. (ATS 4.31) ASCII file was verified with modifications. (ATS 4.19)
Chapter 3
45
Configuring ATS Devices Applying the Advanced Tape Services ASCII Configuration File
Applying the Advanced Tape Services ASCII Configuration File After specifying and verifying all ATS parameters, use the stapplyconf command to apply the configuration. This action distributes configuration file information to all the nodes in the cluster. Before distributing the configuration, ensure that your security files permit copying among the cluster nodes. See the Managing MC/ServiceGuard manual. CAUTION
Apply the ATS configuration to the cluster when ATS is first configured, every time the ATS configuration file is edited. Anytime cmapplyconf has been executed a new stquerycl and stapplyconf sequence should be performed. This ensures that all shared tape devices and shared library robotic devices are correctly configured for use. To update the configuration and distribute the configuration to all nodes in the cluster: 1. Prior to applying the ATS configuration, the MC/ServiceGuard configuration must be in place, that is a cmapplyconf must have been executed successfully at least once. See Managing MC/ServiceGuard and “Creating the Advanced Tape Services ASCII Configuration File” on page 36 for more information. The cluster does not need to be started, but it does need to be configured. 2. Apply the ATS configuration to the cluster, whether the MC/ServiceGuard cluster is running or halted, by typing: stapplyconf -C filename
For example: stapplyconf -v -C /etc/cmcluster/stape.ascii
-C is required. It specifies the ATS configuration file name. -v displays detailed information only on modifications to the configuration and lists the device files that are created. Other stapplyconf options include:
46
Chapter 3
Configuring ATS Devices Applying the Advanced Tape Services ASCII Configuration File -k tells ATS to get the I/O data from the kernel data structures rather than by performing a physical scan of the hardware. Using this option saves command execution time, but could overlook any newly attached devices since the ATS configuration file was created, therefore: • Do not use the -k option if the hardware has been changed since the last time you ran stquerycl. • Do not use it with the first stquerycl or stcheckconf command. ATS must check the current cluster hardware to be accurate. But subsequently, in the same session, it is not necessary to check the cluster hardware with each command. -f distributes the ATS configuration to the cluster without a verification prompt. The following is a partial sample output. Beginning verification of ATS configuration. Distribute ATS configuration to all nodes in cluster my_cluster ([y]/n):y Configuration database updated successfully. jeckle:Successfully created device file "/dev/rac/sac5" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6m" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6mb" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6mn" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6mnb" on Node jeckle. . . . hansel:Successfully created device file "/dev/rmt/st12mn" on Node hansel. hansel:Successfully created device file "/dev/rmt/st12mnb" on Node hansel. hansel:Successfully created device file "/dev/rmt/st13m" on Node hansel. hansel:Successfully created device file "/dev/rmt/st13mb" on Node hansel. hansel:Successfully created device file "/dev/rmt/st13mn" on Node hansel. hansel:Successfully created device file "/dev/rmt/st13mnb" on Node hansel. Completed ATS configuration.
Each entry for a device has the UNIX standard four-way options: • st#m opens the tape device with default settings. • st#mb opens the tape device using Berkeley settings. • st#mn tells the system to not rewind the tape device upon a close using the System 5 settings. • st#mnb tells the system to not rewind the tape device upon a close using the Berkeley settings.
Chapter 3
47
Configuring ATS Devices Applying the Advanced Tape Services ASCII Configuration File 3. You have completed all the ATS configuration steps, if you have not already done so, proceed and complete the MC/ServiceGuard configuration.
48
Chapter 3
Maintaining Advanced Tape Services Devices
4
Maintaining Advanced Tape Services Devices This chapter explains how to maintain Advanced Tape Services devices. The topics discussed include: • Viewing the Advanced Tape Services Configuration • Viewing Shared Tape Device Status • Updating the Cluster Configuration. • Replacing or Updating Advanced Tape Services Configured Devices • Reclaiming Advanced Tape Services Devices • Removing ATS Configuration
Chapter 4
49
Maintaining Advanced Tape Services Devices Viewing the Advanced Tape Services Configuration
Viewing the Advanced Tape Services Configuration You can view the ATS configuration that was applied to the MC/ServiceGuard cluster configuration. This would be useful if your original ATS configuration file is lost or damaged or if you want to compare the current applied configuration to the original ATS configuration file. Use the stgetconf command. stgetconf extracts all the ATS configuration information from the MC/ServiceGuard configuration file and outputs the content to the screen. To view the current ATS configuration, at the cluster command line type: stgetconf -C filename
-C filename saves the output to a file. It specifies the location and name of the retrieved ATS configuration. NOTE
Use a different filename than the one you specified to create the ATS configuration or it will overwrite the original ATS configuration file. Figure 4-1 shows the global information and part of the first device entry of the stgetconf output. The stgetconf output file is in the same format as the stquerycl ATS configuration file. Refer to “Advanced Tape Services ASCII Configuration File Content” on page 27.
50
Chapter 4
Maintaining Advanced Tape Services Devices Viewing the Advanced Tape Services Configuration Figure 4-1
stgetconf Output # # # # #
******************************************************************** ************ TAPE SHARING CLUSTER CONFIGURATION FILE *************** ***** For complete details about cluster parameters and how to ***** ***** set them, consult the stquerycl(1m) and atsconf(4) man pages * ********************************************************************
CLUSTER_NAME
my_cluster
# Generated
Tue Nov 10 13:09:01 1998
# The following parameters can be changed to optimize performance of # automatic reclamation and stviewcl. These are the number of assistant # processes which will be created on each node in the cluster. MAX_NUM_RECLAIM_PROCS MAX_NUM_DISPLAY_PROCS
2 2
(range is 2-100) (range is 2-100)
# The following parameter specifies the minimum time (in seconds) between # status queries for stviewcl. MIN_TIME_FOR_STATUS_UPDATE
1
(range is 1-3600)
# The following device information was returned by stquerycl(1m). # The cluster-wide identifier (numeric embedded in DEVICE_NAME) # may be modified but must remain unique across the cluster. DEVICE_NAME
/dev/rmt/st19m
# The following flag can be modified. If "no" is changed to "yes" the device # will not be reclaimed and its status will not be reported. HIDE_DEVICE
no
# The following information can be added to this file for the above device. # Remove the "#" and add alias name. Multiple aliases are allowed. # ALIAS_NAME # ALIAS_NAME
/dev/rmt/meaningful_name /dev/rmt/meaningful_name
# The following information can be added to this file for the above device. # Remove the "#" and add any description desired. Multiple lines are allowed. # DESCRIPTION # DESCRIPTION
This is a commented line of device description. This is another commented line of device description.
# DO NOT ALTER any of the remaining data for this device entry! DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 137 28 240 27 0 5 0 1 128 2 2 0 0 0 0 137 86 36 85 243 163 32 100 QUANTUM DLT7000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x175000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
heckle 205 0x145000
Chapter 4
51
Maintaining Advanced Tape Services Devices Viewing Shared Tape Device Status
Viewing Shared Tape Device Status When the cluster is started, check the ATS configuration and shared tape device status of the cluster by typing at the command line: stviewcl -v st_name
-v indicates the verbose option. This displays status of shared devices and the ATS configuration file information on screen. Hidden devices are not displayed for stviewcl or stviewcl -v. -a specifies show all ATS configured sharable devices. This displays the status of all shared devices, including hidden devices. st_name indicates the path name of one or more specific device files. For example to view the status of device st17m by typing: stviewcl -v st17m
stviewcl checks the /dev/rmt and /dev/rac paths for the st17m device and displays the status. DEVICE_NAME /dev/rmt/st17m
STATUS AVAILABLE
Possible status values include: AVAILABLE NO HARDWARE DETECTED
NO STATUS OWNED BY node_name
The device is up and available for use by any customer application. The device is a library or tape device and is configured for use, but a search of the cluster indicates the device is currently not available for use. The device is a tape and is configured for use, but the cluster is not currently active on this node. The device is currently being used by a cluster node of name node_name.
RESERVED BY UNKNOWN HOST The device is currently being used by a host outside the currently formed cluster, possibly by a cluster node which has been removed from the cluster temporarily.
52
Chapter 4
Maintaining Advanced Tape Services Devices Viewing Shared Tape Device Status Figure 4-2 is a partial sample of the stviewcl output for device st17m with the verbose option. Figure 4-2
stviewcl Output for device st17m with Verbose Option # ===================================================================== # DEVICE_NAME
/dev/rmt/st17m
AVAILABLE
HIDE_DEVICE DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
NO tape 1 0 0 0 0 0 0 0 117 23 56 15 17 145 6 45 1 2 0 1 128 2 2 0 0 0 0 208 217 190 20 113 130 227 199 Quantum DLT4000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
heckle 205 0x121000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x011000
Figure 4-3 is a partial sample of the stviewcl output without the verbose option. Figure 4-3
stviewcl Output without Verbose Option DEVICE_NAME /dev/rac/sac15
STATUS AVAILABLE
/dev/rmt/st16m
AVAILABLE
/dev/rmt/st17m
AVAILABLE
/dev/rmt/st18m
AVAILABLE
/dev/rmt/st19m
AVAILABLE
/dev/rmt/st20m
AVAILABLE
Chapter 4
53
Maintaining Advanced Tape Services Devices Updating the Cluster Configuration
Updating the Cluster Configuration Every time the cmapplyconf command is executed you should update the ATS configuration by performing an stquerycl and stapplyconf sequence to also update the ATS configuration file with the new cluster configuration. To update the ATS configuration: 1. Verify the current status of the ATS configuration in the MC/ServiceGuard cluster configuration by typing: stgetconf -v -C filename
-C filename saves the output to a file. It specifies the location and name of the retrieved ATS configuration. -v displays detailed information of the configuration and lists the device files that are created. The following shows the global information and part of the first device entry of the output from an stgetconf. This return from stgetconf displays the latest ATS information from the MC/ServiceGuard configuration file.
54
Chapter 4
Maintaining Advanced Tape Services Devices Updating the Cluster Configuration
# # # # #
******************************************************************** ************ TAPE SHARING CLUSTER CONFIGURATION FILE *************** ***** For complete details about cluster parameters and how to ***** ***** set them, consult the stquerycl(1m) and atsconf(4) man pages * ********************************************************************
CLUSTER_NAME
my_cluster
# Generated
Tue Nov 10 13:09:01 1998
# The following parameters can be changed to optimize performance of # automatic reclamation and stviewcl. These are the number of assistant # processes which will be created on each node in the cluster. MAX_NUM_RECLAIM_PROCS MAX_NUM_DISPLAY_PROCS
2 2
(range is 2-100) (range is 2-100)
# The following parameter specifies the minimum time (in seconds) between # status queries for stviewcl. MIN_TIME_FOR_STATUS_UPDATE 1
(range is 1-3600)
# The following device information was returned by stquerycl(1m). # The cluster-wide identifier (numeric embedded in DEVICE_NAME) # may be modified but must remain unique across the cluster. DEVICE_NAME
/dev/rmt/st16m
# The following flag can be modified. If "no" is changed to "yes" the device # will not be reclaimed and its status will not be reported. HIDE_DEVICE
no
# The following information can be added to this file for the above device. # Remove the "#" and add alias name. Multiple aliases are allowed. # ALIAS_NAME # ALIAS_NAME
/dev/rmt/meaningful_name /dev/rmt/meaningful_name
# The following information can be added to this file for the above device. # Remove the "#" and add any description desired. Multiple lines are allowed. # DESCRIPTION # DESCRIPTION
This is a commented line of device description. This is another commented line of device description.
# DO NOT ALTER any of the remaining data for this device entry! DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 137 28 240 27 0 5 0 1 128 2 2 0 0 0 0 137 86 36 85 243 163 32 100 QUANTUM DLT7000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x175000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
heckle 205 0x145000
Chapter 4
55
Maintaining Advanced Tape Services Devices Updating the Cluster Configuration 2. Update the ATS configuration file by typing: stquerycl -C filename
-C filename saves the output for editing and/or applying to your MC/ServiceGuard cluster. It specifies the location and name of the ATS configuration file to be created. 3. Edit the ATS configuration file if necessary. 4. Verify the modified ATS configuration file by typing: stcheckconf -k -C filename
-C filename is a required option. It specifies the location and name of the ATS configuration file to be checked or validated. stcheckconf should be executed every time you modify the ATS configuration file to validate the modifications before attempting to apply the configuration file. 5. Apply the ATS configuration to the cluster by typing: stapplyconf -k -v -C filename
-C filename is required. It specifies the ATS configuration file name to be applied to the cluster. -v displays detailed information on modifications to the configuration and lists the device files that are created. The following is a partial sample output which lists the modifications made. This step can be performed regardless of whether the cluster is up or down.
56
Chapter 4
Maintaining Advanced Tape Services Devices Updating the Cluster Configuration
Beginning verification of ATS configuration. Distribute ATS configuration to all nodes in cluster my_cluster([y]/n):y Configuration database updated successfully. # ===================================================================== # DEVICE_NAME
/dev/rmt/st6m
NO STATUS
HIDE_DEVICE DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
NO tape 1 0 0 0 0 0 0 0 117 23 56 15 137 28 240 27 0 5 0 1 128 2 2 0 0 0 0 137 86 36 85 243 163 32 100 QUANTUM DLT7000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
gretel 205 0x175000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
jeckle 205 0x145000
# --------------------------------------------------------------------- # The cluster wide name was changed. (ATS 4.25) FROM: "/dev/rmt/st15m" TO: "/dev/rmt/st6m" ASCII file was verified with modifications. (ATS 4.19) Distribute ATS configuration to all nodes in cluster my_cluster([y]/n):y Configuration database updated successfully. . . . jeckle:Successfully created device file "/dev/rac/sac5" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6m" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6mb" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6mn" on Node jeckle. jeckle:Successfully created device file "/dev/rmt/st6mnb" on Node jeckle. . . . gretel:Successfully created device file "/dev/rac/sac5" on Node gretel. gretel:Successfully created device file "/dev/rmt/st6m" on Node gretel. gretel:Successfully created device file "/dev/rmt/st6mb" on Node gretel. gretel:Successfully created device file "/dev/rmt/st6mn" on Node gretel. gretel:Successfully created device file "/dev/rmt/st6mnb" on Node gretel. Completed ATS configuration.
Chapter 4
57
Maintaining Advanced Tape Services Devices Replacing or Updating Advanced Tape Services Configured Devices
Replacing or Updating Advanced Tape Services Configured Devices There are times when you will need to update your ATS configuration so that it is consistent with the hardware configuration, both the physical configuration and the logical configuration kept in the kernel data structures. You should update your ATS configuration by performing a stquerycl and stapplyconf sequence whenever any of the following occur: • a new ATS sharable tape or tape library robotic device is connected to a cluster node • the SCSI target id of an ATS configured tape device or tape library robotic device is modified • an ATS configured tape device, tape library robotic device, or a Fibre Channel SCSI Mux to which ATS sharable devices are attached is replaced • the firmware for an ATS configured tape device, tape library robotic device, or Fibre Channel SCSI Mux to which ATS sharable devices are attached is updated NOTE
You do not need to update the ATS configuration if you are applying patches for the tape device driver, the Fibre Channel host bus adaptor driver, or the Fibre Channel SCSI Mux driver. Whenever you replace a hardware device you need to update and reapply your ATS configuration. If you need to update the ATS configuration for one of the above reasons: 1. Perform the device addition, modification, replacement, or firmware download as needed and according to the guidelines specified for each particular device. 2. Update the ATS configuration file by typing stquerycl -C filename
-C filename is a required option if you want to save the output for editing and/or applying to your MC/ServiceGuard cluster. It specifies the location and name of the ATS configuration file to be created.
58
Chapter 4
Maintaining Advanced Tape Services Devices Replacing or Updating Advanced Tape Services Configured Devices 3. Edit the ATS configuration file as needed. • Review the file and locate any new No Hardware Match entries. If these entries are for devices which you have configured for use with other utilities, such as your backup utility, then determine whether you should modify any newly created ATS device entries to use the obsolete ATS unique device name (st#m or rac#) in the No Hardware Match entries. • Remove any unneeded No Hardware Match device entries found at the end of the ATS configuration file if they are no longer needed. Refer to “No Hardware Match Information” on page 32. Delete the text for each obsolete device, between and including the: # **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE **** # **** NOTE
Chapter 4
End of entry with no hardware match
NOTE ****
59
Maintaining Advanced Tape Services Devices Replacing or Updating Advanced Tape Services Configured Devices The following is a sample of a No Hardware Match entry. # **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE **** NOTE **** # The following device entry does not match the hardware scan. # This entry will be ignored (you may delete this ENTIRE entry). # The following device information was returned by stquerycl(1m). # The cluster-wide identifier (numeric embedded in DEVICE_NAME) # may be modified but must remain unique across the cluster. DEVICE_NAME
/dev/rmt/st13m
ATS supplied name of replaced hardware
# The following flag can be modified. If "no" is changed to "yes" the device # will not be reclaimed and its status will not be reported. HIDE_DEVICE
no
# The following information can be added to this file for the above device. # Remove the "#" and add alias name. Multiple aliases are allowed. # ALIAS_NAME # ALIAS_NAME
/dev/rmt/meaningful_name /dev/rmt/meaningful_name
# The following information can be added to this file for the above device. # Remove the "#" and add any description desired. Multiple lines are allowed. # DESCRIPTION # DESCRIPTION
This is a commented line of device description. This is another commented line of device description.
# DO NOT ALTER any of the remaining data for this device entry! DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
tape 1 0 0 0 0 0 0 0 117 23 56 15 17 145 6 45 0 2 0 1 128 2 2 0 0 0 0 208 217 190 20 5 12 229 249 Quantum DLT4000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
gretel 205 0x002000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x002000
# **** NOTE
End of entry with no hardware match
NOTE ****
• Make any modifications to the ATS configuration file to meet your needs. This might include: • updating new ATS sharable device entries to use obsoleted ATS unique device names for backward compatability with your environment. For example, preserving consistent naming for use by associated applications. 60
Chapter 4
Maintaining Advanced Tape Services Devices Replacing or Updating Advanced Tape Services Configured Devices • adding any desired alias names. • Save the ATS configuration file. 4. Validate the modified ATS configuration file with the stcheckconf command to check for any configuration errors and inconsistencies which may have been made. If any errors are found in the ATS configuration file, correct them and re-validate it using stcheckconf until there are no errors found. Perform this validation using the stcheckconf command as follows: stcheckconf -C filename
-C filename specifies the location and name of the ATS configuration file to be checked or validated. 5. Apply the updated ATS configuration file to make the active ATS configuration consistent with the new physical cluster configuration using the stapplyconf command as follows: stapplyconf -C filename
-C filename is required. It specifies the ATS configuration filename to be applied to the cluster. The MC/ServiceGuard cluster can be running or halted when the stapplyconf command is executed. The following is a partial sample output which lists the modifications made.
Chapter 4
61
Maintaining Advanced Tape Services Devices Replacing or Updating Advanced Tape Services Configured Devices
Beginning verification of ATS configuration. Distribute ATS configuration to all nodes in cluster my_cluster([y]/n):y Configuration database updated successfully. # ===================================================================== # DEVICE_NAME
/dev/rmt/st16m
NO STATUS
HIDE_DEVICE DEVICE_TYPE FCMUX_ID BUS TARGET LUN DEVICE_ID VENDOR PRODUCT_ID
NO tape 1 0 0 0 0 0 0 0 117 23 56 15 137 28 240 27 0 5 0 1 128 2 2 0 0 0 0 137 86 36 85 243 163 32 100 QUANTUM DLT7000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
hansel 205 0x175000
NODE_NAME MAJOR_NUMBER MINOR_NUMBER
heckle 205 0x145000
# --------------------------------------------------------------------- # The cluster wide name was changed. (ATS 4.25) FROM: "/dev/rmt/st15m" TO: "/dev/rmt/st16m" ASCII file was verified with modifications. (ATS 4.19) Distribute ATS configuration to all nodes in cluster my_cluster([y]/n):y Configuration database updated successfully. . . . jeckle:Successfully created device file "/dev/rac/sac15" on Node heckle. jeckle:Successfully created device file "/dev/rmt/st16m" on Node heckle. jeckle:Successfully created device file "/dev/rmt/st16mb" on Node heckle. jeckle:Successfully created device file "/dev/rmt/st16mn" on Node heckle. jeckle:Successfully created device file "/dev/rmt/st16mnb" on Node heckle. . . . gretel:uccessfully created device file "/dev/rac/sac15" on Node hansel. gretel:Successfully created device file "/dev/rmt/st16m" on Node hansel. gretel:Successfully created device file "/dev/rmt/st16mb" on Node hansel. gretel:Successfully created device file "/dev/rmt/st16mn" on Node hansel. gretel:Successfully created device file "/dev/rmt/st16mnb" on Node hansel. Completed ATS configuration.
62
Chapter 4
Maintaining Advanced Tape Services Devices Reclaiming Advanced Tape Services Devices
Reclaiming Advanced Tape Services Devices Devices are allocated to an application running on a particular system. When a system fails while having a shared tape device allocated to it, the shared device needs to be made available again for use by applications on other cluster nodes. This process of making shared devices available again is called reclaiming. In most cases devices are reclaimed automatically. Here are three cases: • Explicit close of application using a device. For example, when an application is finished using a device the device is made available. • Orderly shutdown. For example, if a termination of a process was running a package and the process terminated, the package would have an orderly shutdown and the device is now available. • Non-orderly shutdown. For example if there is a system panic, or a transfer of control (TOC) from MC/ServiceGuard, ATS would automatically reclaim devices for use on the remaining node. Hidden devices are not automatically reclaimed. See “Editing the Advanced Tape Services ASCII Configuration File” on page 40 for information on hidden devices. To manually reclaim a device perform the following: 1. View the status of the devices by typing: stviewcl -a The following is a sample output where device st7m needs to be reclaimed. DEVICE_NAME
STATUS
/dev/rac/sac5
AVAILABLE
/dev/rmt/st6m
AVAILABLE
/dev/rmt/st7m
AVAILABLE
/dev/rmt/st8m
AVAILABLE
2. Reclaim the device from a node that is physically connected to the device st_name, by typing: Chapter 4
63
Maintaining Advanced Tape Services Devices Reclaiming Advanced Tape Services Devices streclaim st_name
st_name is required. It is the path name of the device file -f forces a device reclaim without a verification prompt. For example streclaim st7m
streclaim checks the /dev/rmt and /dev/rac paths for the st7m device and displays the status. The following is a sample output. DEVICE_NAME /dev/rmt/st7m
STATUS RESERVED BY UNKNOWN HOST
Reclaim device st7 ? ([n]/y) : y Successfully reclaimed device "st7m".
In this example, the force option was not used and ATS prompted to verify the reclaim. 3. Verify the device is now available by typing: stviewcl -a The following is a sample output where device st7m has been reclaimed. DEVICE_NAME /dev/rac/sac5
AVAILABLE
/dev/rmt/st6m
AVAILABLE
Alias
/dev/rmt/HP_DLT_6
/dev/rmt/st7m Alias
AVAILABLE
/dev/rmt/HP_DLT_7
/dev/rmt/st8m
64
STATUS
AVAILABLE
Chapter 4
Maintaining Advanced Tape Services Devices Removing ATS Configuration
Removing ATS Configuration You can remove the ATS portion of the MC/ServiceGuard cluster configuration. You might want to do this to clear the way to start a fresh ATS configuration. To remove the ATS configuration: 1. From the command line, type: stdeleteconf
stdeleteconf removes the ATS information from the MC/ServiceGuard cluster configuration file on all the distributed nodes. 2. Optionally, remove device special files and associated alias files. stdeleteconf does not remove device special files or associated alias files created by stapplyconf. If you wish to remove these files, choose from either of the following procedures. • Inspect, then remove selected files from the /dev/rmt and /dev/rac directories. a. On each node of the cluster, list the contents of the /dev/rmt and /dev/rac directories by using the ls -l or ll command. b. Remove only the shared tape device special files and associated alias files using the rmsf command. • Remove all the files in the /dev/rmt and /dev/rac directories. a. On each node of the cluster, from the command line, type: rmsf /dev/rmt/* rmsf /dev/rac/*
b. Rebuild those special files known to the kernel. Type: insf -e
NOTE
This method may result in devices having changed system level device special filenames. For example, a device previously known as 0m may now be known to the system as 4m.
Chapter 4
65
Maintaining Advanced Tape Services Devices Removing ATS Configuration
66
Chapter 4
Advanced Tape Services Man Pages
A
Advanced Tape Services Man Pages The following is a list of man pages used for Advanced Tape Services configuration and maintenance. Man pages for these commands are available on your system after installation of ATS. The ATS man pages are: • ats Man Page • atsconf Man Page • stapplyconf Command • stcheckconf Command • stdeleteconf Command • stgetconf Command • stquerycl Command • streclaim Command • stviewcl Command
Appendix A
67
Advanced Tape Services Man Pages ats Man Page
ats Man Page The ats man page describes the Advanced Tape Services for high availability clusters. The Advanced Tape Services facility of MC/ServiceGuard provides for the sharing of tape and associated library robotic (autochanger) devices among the multiple nodes (hosts) of a high availability cluster. ats enables the following: • Automated shared tape device detection, cluster-wide naming, and configuration. • Recognition of device aliases provided by the system administrator. • Tape device status determination across cluster, showing “who owns what.” • Automatic deallocation of tape devices when the ‘owning’ cluster node fails - devices are immediately available to alternate systems. • Command to allow manual deallocation of owned sharable tape devices and tape library robotic devices.
68
Appendix A
Advanced Tape Services Man Pages atsconf Man Page
atsconf Man Page The atsconf man page describes the Advanced Tape Services configuration file. The atsconf file specifies a shared tape configuration for a high availability cluster. The stquerycl(1m) command queries the cluster and generates the ATS configuration file. Portions of the shared tape configuration information may be edited by the system administrator. The ATS configuration file is verified against the cluster with stcheckconf(1m) and applied to the cluster with stapplyconf(1m). stgetconf(1m) retrieves the current shared tape configuration for the cluster. stdeleteconf(1m) removes the shared tape configuration from the cluster. NOTE
The ATS configuration file is created by ATS and it is not a free format medium. The system administrator is allowed limited freedom to edit the file content. However, the overall arrangement of the content may not be altered. The atsconf file contents are described in “Advanced Tape Services ASCII Configuration File Content” on page 27.
Appendix A
69
Advanced Tape Services Man Pages stapplyconf Command
stapplyconf Command The stapplyconf command verifies and applies the ATS configuration. stapplyconf reads the shared_tape_configuration_file specified and verifies the contents against the MC/ServiceGuard cluster. (See atsconf(4) for configuration file specification.) If the verification is successful, the cluster configuration is updated with the shared tape information and the updated configuration is distributed to each node in the cluster. If the -f option is not specified, the user will be prompted for confirmation before the updated configuration is distributed to the nodes in the cluster. A MC/ServiceGuard cluster configuration must be successfully completed before stapplyconf is done. The stapplyconf options are: • -C shared_tape_configuration_file Specifies the name of the ATS configuration file. • -f Forces the ATS configuration onto each node in the cluster without a prompt. • -k Retrieve the I/O data from the kernel data structures rather than by scanning the hardware. Using this potion saves command execution time, but could overlook newly attached devices since the ATS configuration file was created. • -v Display the details of modifications during the verification process and lists device files created.
70
Appendix A
Advanced Tape Services Man Pages stcheckconf Command
stcheckconf Command The stcheckconf command verifies the ATS configuration without applying it to the cluster. Depending up on the options specified. stcheckconf returns an error if there is no shared tape ASCII configuration file or the MC/ServiceGuard cluster configuration file /etc/cmcluster/cmclconfig does not exist. The stcheckconf options are: • -C shared_tape_configuration_file Specifies the name of the ATS configuration file. • -k Retrieve the I/O data from the kernel data structures rather than by scanning the hardware. Using this potion saves command execution time, but could overlook newly attached devices since the ATS configuration file was created. • -v Display the details of modifications during the verification process. This displays detailed information on modifications to the configuration for each device on the screen as it is verified. If no modifications were made to the ATS configuration file no detailed information displays.
Appendix A
71
Advanced Tape Services Man Pages stdeleteconf Command
stdeleteconf Command The stdeleteconf command deletes the ATS portion of a MC/ServiceGuard cluster configuration. The stdeleteconf command does not remove shared tape device special files or any associated alias files created by stapplyconf. The stdeleteconf command returns an error if there is no shared tape configuration or the MC/ServiceGuard cluster configuration file /etc/cmcluster/cmclconfig does not exist. The stdeleteconf option is: • -f Forces the removal of the ATS configuration from each node in the cluster without a prompt.
72
Appendix A
Advanced Tape Services Man Pages stgetconf Command
stgetconf Command The stgetconf command retrieves the shared tape portion of a MC/ServiceGuard cluster configuration. The retrieved shared tape configuration information is output to screen unless -C shared_tape_configuration_file is specified. See atsconf(4) for details of the share tape configuration. The stgetconf command returns an error if there is no shared tape configuration or the MC/ServiceGuard cluster configuration file /etc/cmcluster/cmclconfig does not exist. The stgetconf options are: • -C shared_tape_configuration_file Specifies the name of the ATS configuration file. • -v Reserved for future use.
Appendix A
73
Advanced Tape Services Man Pages stquerycl Command
stquerycl Command The stquerycl command queries the cluster for ATS configuration information. stquerycl scans all nodes in the cluster for sharable tape and tape library robotic devices. It generates a shared tape configuration (see atsconf(4) man page), assigning cluster-wide unique identifiers to each shared device. If stquerycl is executed on a cluster with an existing shared tape configuration, the existing configuration information is merged, device by device, with the newly detected hardware configuration. A MC/ServiceGuard cluster configuration must be successfully completed before stquerycl is done. The stquerycl options are: • -C shared_tape_configuration_file Specifies the filename of the ATS configuration file to be created. If this is not specified the output displays to the screen only. • -k Retrieve the I/O data from the kernel data structures rather than by scanning the hardware. • -v When the -C option is also specified -v displays the details of the configuration in addition to writing it to the -C specified file.
74
Appendix A
Advanced Tape Services Man Pages streclaim Command
streclaim Command The streclaim command reclaims the specified shared tape device. Device reclamation is automatic when a node owning a shared tape device in a high available cluster fails. The streclaim command provides manual backup for this automation. If the -f option is not specified, the user will be prompted for confirmation for the device. NOTE
This command does not check to see if the device being reclaimed is in use. If the device is in use, the owning node (application) will lose the current access to the device. The streclaim options are: • st_name Specifies the path name of the device file. For example, /dev/rmt/st2m. • -f Reclaims the device without a prompt.
Appendix A
75
Advanced Tape Services Man Pages stviewcl Command
stviewcl Command The stviewcl command displays information about shared tape devices. For each st_name specified, stviewcl displays information for that shared tape device only. If no st_name is specified, stviewcl displays names and corresponding information for all configured shared tape devices. The stviewcl options are: • st_name Specifies the path name of the device file. For example, /dev/rmt/st2m. • -a Display all devices, even those with the HIDE_DEVICE option set to YES. • -v Display the detailed device information.
76
Appendix A
Troubleshooting Advanced Tape Services
B
Troubleshooting Advanced Tape Services The following sections offer a few suggestions for troubleshooting by reviewing the state of the running system and by examining cluster status data, log files, and configuration files. Topics include: • Reviewing the System Log File • Reviewing Configuration Files • Using the stgetconf Command
Appendix B
77
Troubleshooting Advanced Tape Services Reviewing the System Log File
Reviewing the System Log File Messages from Advanced Tape Services are written to the system log file. The default location of the log file is /var/adm/syslog/syslog.log. You can use a text editor, such as vi, or the more command to view the log file for historical information on your cluster. This log provides information on the following: • Commands executed and their outcome. • Major cluster and ATS events which may, or may not, be errors. • Cluster and ATS status information. • References to the ATS daemon, cmtaped. NOTE
Many other products running on HP-UX in addition to MC/ServiceGuard use the syslog.log file to save messages. The HP-UX Managing Systems and Workgroups manual provides additional information on using the system log.
Sample System Log Entries The following entries from the file /var/adm/syslog/syslog.log show a sampling of ATS error messages. Dec 02 17:26:42:0:ATS:ff: Action - cmtaped terminating. (ATS1.14) Dec 02 17:33:59:0:ATS:01: External error - Could not get temporary device file name. (ATS 1.26) Dec 02 17:59:33:0:ATS:01: External error - Multiple "SCTL incomplete" failures on 0x1e1000 : Error 0. (ATS 1.104) Dec 02 17:59:33:0:ATS:02: External error - Multiple "SCTL incomplete" failures on 0x141000 : Error 0. (ATS 1.104) Dec 02 18:03:56:0:ATS:ff: Action - cmtaped terminating. (ATS1.14) Dec 02 18:04:44:0:ATS:01: External error - The ioctl for 'test unit ready' failed on 0x1e2000 : Not a typewriter. (ATS 1.100) Dec 02 18:41:57:0:ATS:01: External error - Could not read from pipe, Device busy. (ATS 1.17) Dec 02 18:41:57:0:ATS:01: External error - Could not read message. (ATS 1.24) Dec 02 18:43:36:0:ATS:ff: Action - cmtaped terminating. (ATS1.14)
78
Appendix B
Troubleshooting Advanced Tape Services Reviewing the System Log File
Dec 02 18:43:36:0:ATS:02: Action - cmtaped assistant # 2 terminating. (ATS 1.15) Dec 02 18:47:28:0:ATS:02: External error - Only 60 bytes of 60 byte message header was received. (ATS 1.18) Dec 02 18:47:28:0:ATS:01: External error - Could not read message. (ATS 1.24) Dec 02 18:47:28:0:ATS:02: External error - Could not understand message type Dec 02 18:47:54:0:ATS:ff: Action - cmtaped terminating. (ATS 1.14) Dec 02 18:48:52:0:ATS:ff: Action - cmtaped terminating. (ATS1.14) Dec 02 18:48:52:0:ATS:02: Action - cmtaped assistant # 2 terminating. (ATS 1.15) Dec 02 18:48:52:0:ATS:01: Action - cmtaped assistant # 1 terminating. (ATS 1.15) Dec 02 18:54:56:0:ATS:ff: Action - cmtaped received signal "SIGPIPE." Dec 02 18:54:57:0:ATS:01: External error - Read 99 bytes instead of 120 bytes as defined in header. (ATS 1.19) Dec 02 18:54:57:0:ATS:01: External error - Could not read message. (ATS 1.24) Dec 02 18:54:57:0:ATS:02: External error - Read 99 bytes instead of 120 bytes as defined in header. (ATS 1.19) Dec 02 18:59:16:0:ATS:01: External error - Could not allocate memory for reply buffer. (ATS 1.20) Dec 02 19:03:48:0:ATS:ff: Action - cmtaped terminating. (ATS1.14) Dec 02 19:04:34:0:ATS:00: External error - No memory for merge status buffer. (ATS 1.21) Dec 02 19:04:34:0:ATS:ff: Action - cmtaped received signal "SIGPIPE." Dec 02 19:25:56:0:ATS:ff: Action - cmtaped - no requestor to reply. (ATS 1.32) Dec 02 19:26:03:0:ATS:ff: Action - cmtaped terminating. (ATS1.14) Dec 02 19:26:03:0:ATS:02: Action - cmtaped assistant # 2 terminating. (ATS 1.15) Dec 02 19:31:16:0:ATS:01: External error - Could not get memory for device table. (ATS 1.27) Dec 02 19:36:13:0:ATS:ff: External error - No memory available for internal table for shared devices: Bad address. (ATS 1.34) Dec 02 19:36:13:0:ATS:ff: External error - cmtaped - failed to initilize internal data structures. (ATS 1.12) Dec 02 19:42:15:0:ATS:ff: External error - Could not create pipe for assistant #1: Bad file number. (ATS 1.36) Dec 02 19:47:48:0:ATS:ff: External error - Could not create assistant #1: Bad file number. (ATS 1.37)
Appendix B
79
Troubleshooting Advanced Tape Services Reviewing Configuration Files
Reviewing Configuration Files Review the ATS configuration file, use the stgetconf command. Ensure that the file is complete and correct according to your configuration planning worksheets. Refer to Chapter 2, “Planning Your ATS Configuration,” on page 21 for a sample and description of the ATS configuration file.
80
Appendix B
Troubleshooting Advanced Tape Services Using the stgetconf Command
Using the stgetconf Command stgetconf allows you to examine the binary ATS configuration file, even when the cluster is not running. The command displays the content of this file on the node where you run the command. If you try to view an ATS configuration prior to configuring your cluster, an error message displays.
Appendix B
81
Troubleshooting Advanced Tape Services Using the stgetconf Command
82
Appendix B
Advanced Tape Services Messages
C
Advanced Tape Services Messages This appendix lists the Advanced Tape Services messages. The messages are divided into the following sections: • cmtaped Messages • stapplyconf Messages • stcheckconf Messages • stdeleteconf Messages • stgetconf Messages • stquerycl Messages • streclaim Messages • stviewcl Messages
Appendix C
83
Advanced Tape Services Messages cmtaped Messages
cmtaped Messages Unable to open the message catalog,continuing: variable_object (ATS 1.1) cmtaped - failed to setup signal handler. (ATS 1.2) cmtaped - failed to initialize(incorrect usage). (ATS 1.3) cmtaped - failed to register as generic client. (ATS 1.4) cmtaped - failed to get node handle. (ATS 1.5) cmtaped - failed to open target. (ATS 1.6) cmtaped - failed to setup status API environment. (ATS 1.7) cmtaped - failed to set up sdb callback. (ATS 1.8) cmtaped - failed to establish end point for communication. (ATS 1.9) cmtaped - failed to bind to the Endpoint. (ATS 1.10) cmtaped - cl_config_create_callback failed(variable_object) (ATS 1.11) cmtaped - failed to initilize internal data structures. (ATS 1.12) cmtaped - received unknown event type. variable_value
(ATS 1.13)
cmtaped terminating. (ATS 1.14) cmtaped assistant # variable_value terminating. (ATS 1.15) cmtaped - invalid CDB callback type. (ATS 1.16) Assistant could not read from pipe, message from cmtaped, variable_object.(ATS 1.17) Only variable_value bytes of variable_value byte message header was received. (ATS 1.18) Read variable_value bytes instead of variable_value bytes as defined in header. (ATS 1.19) Could not allocate memory for reply buffer. (ATS 1.20) Could not allocate memory for the merged status buffer. (ATS 1.21) Either /dev/rmt/stvariable_valuem or /dev/rac/sacvariable_value is not open. (ATS 1.22) Device /dev/rmt/stvariable_valuem or /dev/rac/sacvariable_value could not be reset. (ATS 1.23) Assistant could not read message from cmtaped. (ATS 1.24) Could not understand message type variable_value. (ATS 1.25) Could not get temporary device file name. (ATS 1.26) Could not get memory for device table. (ATS 1.27)
84
Appendix C
Advanced Tape Services Messages cmtaped Messages cmtaped received unknown req message type: variable_value. (ATS 1.28) cmtaped received reply to unknown message type variable_value. (ATS 1.29) Bad Message version. Message type: variable_object, version: variable_value mincast version: variable_value. (ATS 1.30) cmtaped received bad reply status(variable_value) (ATS 1.31) cmtaped - no requestor to reply. (ATS 1.32) cmtaped - deleting msg variable_object from incoming msg queue. (ATS 1.33) No memory available for internal table for shared devices: variable_object. (ATS 1.34) cdb_lookup_ats failed.(variable_object) (ATS 1.35) Could not create pipe for assistant # variable_value: variable_object. (ATS 1.36) Could not create assistant # variable_value: variable_object. (ATS 1.37) Could not write to pipe for assistant #variable_value: variable_object. (ATS 1.38) ATS message received has incorrect original type: variable_value. (ATS 1.39) No memory available for device status request queue variable_object. (ATS 1.40) Merge assistant had a fatal error. (ATS 1.41) Failed to lookup ATS info in the configuration database. (ATS 1.42) cmtaped - Lost connection with cluster daemon. (ATS 1.43) cmtaped - select failed. Error: variable_object. (ATS 1.44) Error: variable_object. (ATS 1.45) The ioctl for test unit ready failed on 0x%6.6x : variable_object. (ATS 1.100)\ Multiple Unit Attentions on 0x%6.6x : variable_object. (ATS 1.101) Device inquiry failed for device 0x%6.6x. (ATS 1.102) Could not get memory for status check. (ATS 1.103) Multiple SCSI control incomplete failures on 0x%6.6x : variable_object. (ATS 1.104) This is text for CMTAPED_ERR_485 (ATS 1.485)
Appendix C
85
Advanced Tape Services Messages stapplyconf Messages
stapplyconf Messages Failed to verify the ATS ascii configuration file. (ATS 3.1) Failed to update configuration database. (ATS 3.2) Failed to create device files for some ATS devices. (ATS 3.3) Failed creating device files. (ATS 3.4) Creating variable_object failed with status: variable_object.(ATS 3.5) Failed to create device files for ATS device(s). (ATS 3.6) Failed while looking up ATS information to create device files on cluster variable_object. (ATS 3.7) Unable to obtain local node information. Error: variable_object. (ATS 3.8)
86
Appendix C
Advanced Tape Services Messages stcheckconf Messages
stcheckconf Messages Cluster wide name is same as previous cluster wide name or alias name. (ATS 4.1) Device type was modified in shared device ASCII configuration file. (ATS 4.2) SCSI bus on Fibre channel multiplexer was modified in shared device ASCII configuration file. (ATS 4.3) SCSI target ID was modified in shared device ASCII configuration file. (ATS 4.4) The SCSI target LUN was modified in shared device ASCII configuration file. (ATS 4.5) The FCMUX_ID bytes were modified in shared device ASCII configuration file. (ATS 4.6) The DIVICE_ID bytes were modified in shared device ASCII configuration file. (ATS 4.7) Vendor ID was modified in shared device ASCII configuration file. (ATS 4.8) Product ID was modified in shared device ASCII configuration file. (ATS 4.9) Serial was modified in shared device ASCII configuration file. (ATS 4.10) The number of media transports was modified in shared device ASCII configuration file. (ATS 4.11) The number of storage slots was modified in shared device ASCII configuration file. (ATS 4.12 ) The number of mail slots was modified in shared device ASCII configuration file. (ATS 4.13) The number of tape drives was modified in shared device ASCII configuration file. (ATS 4.14) Device entry is missing from shared device ASCII configuration file. (ATS 4.15) There is no hardware for this device entry in shared device ASCII configuration file. (ATS 4.16) The connected nodes, major numbers or minor numbers were modified in shared device ASCII configuration file. (ATS 4.17) Internal error, No valid device entry passed to print error. (ATS 4.18) ASCII file was verified with modifications. (ATS 4.19) ASCII file was verified. (ATS 4.20) Library drive information was modified in shared device ASCII configuration file. (ATS 4.21)
Appendix C
87
Advanced Tape Services Messages stcheckconf Messages Alias name is same as cluster wide name. (ATS 4.22) Alias name is same as previous cluster wide name or alias name. (ATS 4.23) This device entry will be removed from the shared device configuration. (ATS 4.24) The cluster wide name was changed. (ATS 4.25) FROM: variable_object TO: variable_object This device will no longer be reclaimed. (ATS 4.26) This device will now be reclaimed. (ATS 4.27) The alias was modified. (ATS 4.28) An alias was removed. (ATS 4.29) An alias was added. (ATS 4.30) The description was modified. (ATS 4.31) Internal error, invalid error number. (ATS 4.32) MAX_NUM_RECLAIM_PROCS value (variable_value) is out of range or missing. (range is 2 - 100) (ATS 4.33) MAX_NUM_DISPLAY_PROCS value (variable_value) is out of range or missing. (range is 2 - 100) (ATS 4.34) MIN_TIME-FOR-STATUS-UPDATE value (variable_value) is out of range or missing. (range is 1 -3600) (ATS 4.35) MAX_NUM_RECLAIM_PROCS was modified. (ATS 4.36) MAX_NUM_DISPLAY_PROCS was modified. (ATS 4.37) MIN_TIME-FOR-STATUS-UPDATE was modified. (ATS 4.38) Global data in shared device ASCII configuration file was modified. (ATS 4.39) Completed with errors. (ATS 4.200) Failed while gathering ATS information. (ATS 4.201) Failed reading ATS Ascii configuration file. (ATS 4.202) Failed verifying ATS cluster wide global configuration data. (ATS 4.203) Failed verifying ATS cluster wide device configuration data. (ATS 4.204)
88
Appendix C
Advanced Tape Services Messages stdeleteconf Messages
stdeleteconf Messages Failed to delete ATS configuration for cluster variable_object. (ATS 5.1) ATS configuration does not exist or is empty for cluster variable_object. (ATS 5.2)
Appendix C
89
Advanced Tape Services Messages stgetconf Messages
stgetconf Messages Error looking up ATS configuration information for cluster variable_object. (ATS 6.1) Failed to write ATS configuration to variable_object. (ATS 6.2) Unable to write ATS configuration to stdout. (ATS 6.3)
90
Appendix C
Advanced Tape Services Messages stquerycl Messages
stquerycl Messages Unable to complete cluster-wide remote command execution. failed? (ATS 7.1) All nodes in cluster not at same ServiceGuard revision. shared tape configuration. (ATS 7.2)
Node
May not do
stquerycl failed while writing ATS ASCII configuration file.(ATS 7.3) stquerycl failed writing ATS ASCII configuration information to stdout.(ATS 7.4) Command failed while executing ats_ioscan.(ATS 7.5) Command failed while executing ats_xtrctid.(ATS 7.6) Command failed while executing ats_mrgid.(ATS 7.7) Lookup of ATS information from the configuration database failed.(ATS 7.8) Command failed while executing ats_mrgcdb.(ATS 7.9) One or more blanks on line variable_value in tape library specification file variable_object.(ATS 7.10) One or more tabs on line variable_value in tape library specification file variable_object.(ATS 7.11) Vendor id field not terminated with colon character on line variable_value in tape library specification file variable_object.(ATS 7.12) Empty vendor id field on line variable_value in tape library specification file variable_object.(ATS 7.13) Product id field not terminated with colon character on line variable_value in tape library specification file variable_object.(ATS 7.14) Empty product id field on line variable_value in tape library specification file variable_object.(ATS 7.15)
Appendix C
91
Advanced Tape Services Messages streclaim Messages
streclaim Messages Device variable_object does not exist. (ATS 8.1) Device variable_object is not an ATS shared device. (ATS 8.2) Device variable_object not found in ATS configuration file.(ATS 8.3) Failed to allocate memory for message. (ATS 8.4) Failed to lookup configuration database.(ATS 8.5) Unable to determine status of device. (ATS 8.6) Failed to reclaim device variable_object. (ATS 8.7) Ioctl for variable_value 0x%6.6x failed. (ATS 8.8) The version of cmtaped running on this node does not recognize this ATS command. (ATS 8.9) The version of ATS commands installed is not compatible with the version of cmtaped running on this node. (ATS 8.10)
92
Appendix C
Advanced Tape Services Messages stviewcl Messages
stviewcl Messages Failed looking up the ATS configuration database for cluster variable_object.(ATS 9.1) variable_object not in ATS configuration file. (ATS 9.2) Unable to construct message to send to cmtaped. (ATS 9.4) Unable to obtain status of ATS device(s). (ATS 9.5) An stapplyconf may be in progress or the cluster may be reforming.Retry the command.(ATS 9.6) No ATS devices are currently configured in cluster variable_object.(ATS 9.7) The version of cmtaped running on this node does not recognize this ATS command. (ATS 9.8) No ATS device found in argument(s) specified in command.(ATS 9.9) Internal error, illegal status value of variable_value. (ATS 9.10) Internal error, illegal device type of variable_object. (ATS 9.11) The version of ATS commands installed is not compatible with the version of cmtaped running on this node. (ATS 9.12) ATS command failed to obtain node handle.(ATS 9.13) ATS command failed to get local node id. (ATS 9.14) Command failed in create communication end point.(ATS 9.15) Command failed to send request to cmtaped.(ATS 9.16)
Appendix C
93
Advanced Tape Services Messages stviewcl Messages
94
Appendix C
Blank Advanced Tape Services Planning Worksheets
D
Blank Advanced Tape Services Planning Worksheets This appendix reprints blank versions of the planning worksheets described in the “Planning Your ATS Configuration” chapter. You can duplicate the worksheet if you find it useful and fill it in as a part of the planning process.
Appendix D
95
Blank Advanced Tape Services Planning Worksheets Advanced Tape Services Configuration Worksheet
Advanced Tape Services Configuration Worksheet The first portion of the following worksheet applies to the entire cluster, use one per cluster. The next page is for listing all the ATS configured devices, make copies and use as many as needed.
Cluster Name/ID: Maximum number of reclaim processes allowed (2-100): Maximum number of display processes allowed (2-100): Minimum time between status updates (1-3600): Node 1 Name/ID: Node 2 Name/ID: Node 3 Name/ID: Node 4 Name/ID: Device Name/ID: Alias:
Hide: Yes/No
Description: Type:
Autochanger
Node:
Tape
Other:
Node:
Device Name/ID: Alias:
Hide: Yes/No
Description: Type: Node:
96
Autochanger
Tape
Other:
Node:
Appendix D
Blank Advanced Tape Services Planning Worksheets Advanced Tape Services Configuration Worksheet
Device Name/ID: Alias:
Hide: Yes/No
Description: Type:
Autochanger
Node:
Tape
Other:
Node:
Device Name/ID: Alias:
Hide: Yes/No
Description: Type:
Autochanger
Node:
Tape
Other:
Node:
Device Name/ID: Alias:
Hide: Yes/No
Description: Type:
Autochanger
Node:
Tape
Other:
Node:
Device Name/ID: Alias:
Hide: Yes/No
Description: Type:
Autochanger
Node:
Tape
Other:
Node:
Device Name/ID: Alias:
Hide: Yes/No
Description: Type:
Autochanger
Node:
Appendix D
Tape
Other:
Node:
97
Blank Advanced Tape Services Planning Worksheets Advanced Tape Services Configuration Worksheet
98
Appendix D
Index
A -a stviewcl, 52, 76 administration reviewing configuration files, 80 troubleshooting, 77 Advanced Tape Services, 11 ALIAS_NAME editing, 40 ALIAS_NAME field, 30 applying configuration, 46, 61 ATS, 11 cluster requirements, 22 commands, 18 configuration file, 27, 30, 36 global data, 27 configuring, 35 cost savings, 22 hardware requirements, 22 High Availability, 22 maintenance procedures, 49 man pages, 67 removing configuration, 65 sample configuration file, 37 software requirements, 22 system log file, 78 ats man page, 68 ats_tapelibs file, 14 atsconf man page, 69 autochanger, 28 automatic reclaiming, 63 B BUS field, 31 C -C stapplyconf, 46, 56, 70
Index
stcheckconf, 56, 71 stcheckconf option, 43 stgetconf, 50, 54, 73 stquerycl, 56, 74 changing name, 41 cluster device names, 13 device naming, 36 nodes, 11 cluster requirements ATS, 22 CLUSTER_NAME field, 27 cmapplyconf ATS configuration, 46 cmapplyconf command, 54 cofiguration updating, 58 command stapplyconf, 36 stquerycl, 36, 58 commands ATS, 18 deleteconf, 19 indf, 65 MC/ServiceGuard, 36 reclaim, 19 rmsf, 65 stapplyconf, 18, 61 stcheckconf, 18 stdeleteconf, 65 stgetconf, 19, 50, 80 stquerycl, 18 streclaim, 63 stviewcl, 52, 63 viewcl, 19 configuration, 58 applying, 46 ATS file, 27 changing device names, 41 create, 18 delete, 19 editing file, 59 four-node cluster, 17
global data, 28 MC/ServiceGuard, 26 planning, 21 sample ATS file, 37 samples, 15 tape device, 28 two-node cluster, 16 update, 18 verify, 18 verify and apply, 18 view, 19 viewing, 50, 80 worksheet, 24 worksheets, 95 configuration file ATS, 30 atsconf man page, 69 CLUSTER_NAME field, 27 create, 36 DEVICE_NAME, 29 editing, 40, 59 editing global data, 40 global data, 27 MAX_NUM_DISPLAY_PROC S field, 27 MAX_NUM_RECLAIM_PROC S field, 27 MAX_TIME_FOR_STATUS_U PDATE field, 28 No Hardware Match, 32 No Hardware Match entry, 39 non-editable fields, 32 tape device entry, 39 tape library device entry, 39 Timestamp field, 27 troubleshooting, 80 verify, 43 viewing, 81 configuring ATS, 35 ATS configuration file, 36 shared devices, 36 cost savings
99
Index
ATS, 22 create configuration, 18 configuration file, 36 D delete configuration, 19 DESCRIPTION editing, 41 DESCRIPTION field, 30 device, 41 hide, 29 name settings, 47 naming, 29 reclaim, 19 replacing, 58 status, 19 verify, 43 viewing status, 52 device special files removing, 65 DEVICE_ID field, 31 DEVICE_NAME, 29 DEVICE_NAME field, 29 DEVICE_TYPE field, 31 devices reclaiming, 63 supported, 14 E editing alias names, 40 configuration file, 40 description data, 41 global configuration data, 40 error messages, 83 F -f
stapplyconf, 46, 70
100
stdeleteconf, 72 streclaim, 63, 75 FCMUX_ID field, 31 fibre channel SCSI MUX, 14 updating configuration, 58 field ALIAS_NAME, 30 DESCRIPTION, 30 DEVICE_NAME, 29 HIDE_DEVICE, 29 fields BUS, 31 CLUSTER_NAME, 27 DEVICE_ID, 31 DEVICE_TYPE, 31 FCMUX_ID, 31 LUN, 31 MAJOR_NUMBER, 31 MAX_NUM_DISPLAY_PROC S, 27 MAX_NUM_RECLAIM_PROC S, 27 MAX_TIME_FOR_STATUS_U PDATE, 28 MINOR_NUMBER, 32 NODE_NAME, 31 PRODUCT_ID, 31 TARGET, 31 Timestamp, 27 VENDOR, 31 firmware updating configuration, 58 H hardware requirements ATS, 22 hidden devices reclaiming, 63 hide device, 29 HIDE_DEVICE setting, 41
HIDE_DEVICE field, 29 High Availability ATS, 22 HP DLT 4/48 Library, 12 I insf command, 65 K -k stapplyconf, 46, 56, 70 stcheckconf, 71 stcheckconf option, 43 stquerycl, 74 L library device configuring, 36 naming, 13 library devices shared, 12 LUN field, 31 M MAJOR_NUMBER field, 31 man pages, 67 ats, 68 atsconf, 69 stapplyconf, 70 stcheckconf, 71 stdeleteconf, 72 stgetconf, 73 stquerycl, 74 streclaim, 75 stviewcl, 76 MAX_NUM_DISPLAY_PROCS field, 27 MAX_NUM_RECLAIM_PROCS field, 27 MAX_TIME_FOR_STATUS_UP DATE field, 28
Index
Index
MC/ServiceGuard commands, 36 configuration, 26 messages error, 83 MINOR_NUMBER field, 32 N naming /dev/rac/sac#, 40 /dev/rmt/st#m, 40 changing device names, 41 device, 29 replacing names, 60 setting options, 47 shared devices, 22 No Hardward Match configuration file entry, 39 No Hardware Match, 32 removing, 42 removing entry, 59 sample entry, 60 NODE_NAME field, 31 O options, 46 -C stgetconf, 50 stapplyconf, 46, 70 stcheckconf, 43, 71 stdeleteconf, 72 stgetconf, 54, 73 stquerycl, 36, 37, 74 stquerycl -C, 36 stquerycl -k, 37 stquerycl -v, 37 streclaim, 75 streclaim -f, 63 stviewcl, 52, 76 P planning configuration, 21
Index
PRODUCT_ID field, 31 R rac directory, 40 reapplying, 58 rebuilding special files, 65 reclaim devices, 19 reclaiming devices, 63 hidden devices, 63 removing ATS configuration, 65 device special files, 65 No Hardware Match, 42 replacing devices, 58 rmsf command, 65 rmt directory, 40 robotic arm, 28 S SCSI target id updating configuation, 58 shared devices, 12 naming, 22 shared tape devices replacing, 58 software requirements ATS, 22 stapplyconf command, 18 man page, 70 options, 70 stapplyconf command, 36, 46, 56, 61 commands stapplyconf, 46 output sample, 47 sample output, 56, 61 status
devices, 19 system log file, 78 stcheckconf command, 18 man page, 71 options, 43, 71 output sample, 43 stcheckconf command, 43, 56 commands stcheckconf, 61 stdeleteconf command, 19 man page, 72 options, 72 stdeleteconf command, 65 stgetconf command, 19 man page, 73 options, 73 sample output, 50 stgetconf command, 50, 54, 80 options, 54 sample output, 54 stquerycl -C option, 36 command, 18 man page, 74 options, 36, 37, 74 stquerycl command, 36, 56, 58 streclaim command, 19 man page, 75 options, 75 streclaim command, 63 options, 63 sample output, 63 stviewcl command, 19 man page, 76 options, 76 stviewcl command, 52, 63 options, 52 system log file
101
Index
sample entries, 78 troubleshooting, 78 viewing, 78 T tape device configuration file entry, 39 configuring, 36 naming, 13, 22 tape devices replacing, 58 shared, 12 tape library, 12, 28 naming, 22 replacing, 58 tape library device configuration file entry, 39 TARGET field, 31 Timestamp field, 27 troubleshooting, 77 approaches, 77 reviewing system log file, 78
stquerycl, 37 validating configuration, 61 VENDOR field, 31 verify configuration, 18 configuration file, 43 verify and apply configuration, 18 view configuration, 19 viewing ATS configuration file, 81 configuration, 50, 80 device status, 52 system log file, 78 W worksheet configuration, 24 worksheets configuration, 95
U update configuration, 18 updating ATS configuration, 54 configuration, 58 MC/ServiceGuard configuration, 54 V -v stapplyconf, 46, 56, 70 stcheckconf, 71 stcheckconf option, 43 stgetconf, 54, 73 stquerycl, 74 stviewcl, 52, 76 -v option stquerycl, -k option
102
Index
