Page 1: Installation Guide
HPSS Installation Guide High Performance Storage System Release 6.2 July 2008 (Revision 2.0) HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 2 High Performance Storage System is a trademark of International Business Machines Corporation. IBM is a registered trademark of International Business Machines Corporation. IBM, DB2, DB2 Universal Database, AIX, pSeries, and xSeries are trademarks or registered trademarks of International Business Machines Corporation.
Page 3: Table Of Contents
Chapter 1. Release 6.2...15 1.1.New Features...15 1.1.1.DCE Replacement ...15 1.1.2.Linux Support ...15 1.1.3.Security...15 1.1.4.SCSI PVR ...15 1.1.5.HPSS VFS Interface...15 1.1.6.GridFTP Interface...15 1.1.7.SAN3P/PIO Support ...15 1.1.8.Additional hpssadm Configuration Options...15 1.1.9.Additional hpssadm operations...16 1.1.10.Additional Library and Device Support...16 1.1.11.SAN Virtual Volume ID Mapping...16 1.1.12.Drive Pools...17 1.1.13.FTP Enhancement...17 1.1.14.mkhpss Enhancement...17...
Page 4 3.3.2.3.2.Client API Requirements...61 3.3.2.3.3.FTP/PFTP Client Requirements...61 3.3.2.4.HPSS HDM Nodes (Linux only)...61 3.4.Hardware Considerations ...62 3.4.1.Network Considerations...62 3.4.2.Robotically Mounted Tape...62 3.4.2.1.IBM 3494...63 3.4.2.2.Drive-Controlled LTO Libraries (IBM 3582, IBM 3583, IBM 3584, Spectralogic T120)...63 HPSS Installation Guide Release 6.2 (Revision 2.0) July 2008...
Page 5 3.4.2.3.STK L40, STK SL500, STK SL8500...63 3.4.2.4.STK...63 3.4.2.5.ADIC AML ...63 3.4.3.Manually Mounted Tape...63 3.4.4.Tape Devices...63 3.4.4.1.Multiple Media Support...64 3.4.5.Disk Devices...67 3.4.6.Special Bid Considerations...68 3.5.HPSS Sizing Considerations...68 3.5.1.HPSS User Storage Space...69 3.5.2.HPSS Infrastructure Storage Space...69 3.5.3.HPSS Filesystems...71 3.5.3.1./opt/hpss...71 3.5.3.2./var/hpss...71 3.5.3.3./var/hpss/adm/core...72 3.5.3.4./var/hpss/hpssdb...72 3.5.3.5./var/hpss/hpssdb/subsys1 &...
Page 6 3.7.6.6.SCSI PVR...88 3.7.7.Mover ...89 3.7.7.1.AIX Asynchronous I/O...89 3.7.7.2.Tape Devices...89 3.7.7.2.1.AIX...89 3.7.7.2.2.Solaris...89 3.7.7.2.3.IRIX...90 3.7.7.2.4.Linux...90 3.7.7.3.Disk Devices...90 3.7.7.4.Performance...91 3.7.8.Logging Service...91 3.7.9.Startup Daemon...92 3.7.10.Storage System Management...92 3.8.Storage Subsystem Considerations...94 3.9.Storage Policy Considerations ...94 3.9.1.Migration Policy ...94 3.9.1.1.Migration Policy for Disk...94 3.9.1.2.Migration Policy for Tape...95 3.9.2.Purge Policy ...95 3.9.3.Accounting Policy and Validation ...96 3.9.4.Security Policy...98...
Page 7 3.12.HPSS Metadata Backup Considerations ...117 3.13.HPSS Security Considerations...117 Chapter 4. System Preparation...119 4.1.General Setup...119 4.2.Setup Filesystems...120 4.2.1.DB2 Filesystem...120 4.2.2.HPSS Filesystem...121 4.3.Setup Tape Libraries...121 4.3.1.Special LTO Considerations...121 4.3.2.IBM 3584...121 4.3.3.3494...122 4.3.4.STK...123 4.3.5.AML...123 4.4.Verify Tape Drives...124 4.4.1.AIX...124 4.4.2.Solaris...125 4.4.3.IRIX...126 4.4.4.Linux...126 4.5.Setup Disk Drives...126 4.5.1.AIX...127...
Page 8 5.1.4.Installation Target Directory Preparation...136 5.2.Install Prerequisite Software...137 5.2.1.Install Java...137 5.2.2.Install MIT Kerberos (If Using Kerberos Authentication)...137 5.2.3.Install LDAP (If Using LDAP Authorization)...137 5.2.4.Install Prerequisite Software for XFS HDM...138 5.3.Install HPSS/DB2 and Configure HPSS Infrastructure...139 5.3.1.Install and Configure HPSS - Root Subsystem Machine...139 5.3.1.1.Pre-Installation Configuration...139 5.3.1.2.Install HPSS Documentation and DB2 Software...141 5.3.1.3.Set Up DB2 Permanent License...142...
Page 9 Chapter 6. Upgrading to HPSS Release 6.2 ...179 6.1.Special Instructions for Upgrading to HPSS 6.2.2...179 6.2.Planning for the HPSS 6.2 Upgrade...180 6.2.1.Metadata changes in HPSS 6.2...180 6.2.2.Upgrade Requirements and Limitations...182 6.2.3.New Authentication and Authorization Mechanisms...182 6.2.3.1.Authentication Mechanisms...183 6.2.3.2.Authorization Mechanisms...183 6.2.4.New HPSS 6.2 System Files...184 6.2.5.Testing the Metadata Conversion...184 6.2.6.Estimating the Metadata Conversion Time (for 4.5 upgrades only)...184 6.2.6.1.Running Time for the Long Running Metadata Conversion Utilities (for 4.5 upgrades only)...
Page 10 6.3.16.Enable DB2 Backup...215 6.3.17.Perform the DCE Export: hpss_dce_export...215 6.3.18.Perform the Unix, LDAP or Kerberos Import...215 6.3.19.Prepare the 6.2 System...217 6.3.19.1.Tune DB2 for normal operations...218 6.3.19.2.Modify Accounting, if applicable...218 6.3.19.3.Update FTP Configuration Files...218 6.3.19.4.Populate the HPSS.conf files...218 6.3.19.5.Copy the rc.hpss Script to /etc...218 6.3.19.6.Run the bind Script ...218 6.3.19.7.Create Default Server Security ACLs...218 6.3.19.8.Create SSM User Ids...219...
Page 11 D.6. Transfer Agent Stanza...287 D.7. Stanzas Reserved for Future Use...291 Appendix E. hpss_env_defs.h...293 Appendix F. /var/hpss files...309 HPSS Installation Guide Release 6.2 (Revision 2.0) July 2008...
Page 12 List of Figures Figure 1. File Migration and Stage Operations...37 Figure 2. Class of Service / Hierarchy / Storage Class...38 Figure 3. HPSS Components...40 Figure 4. HPSS Generic Configuration...52 Figure 5. Basic HPSS Metadata & Filesystem Allocation...70 Figure 6. The Relationship of Various Server Data Structures...82 Figure 7.
Page 13 List of Tables Table 1. HPSS Client Interface and Mover Platforms...49 Table 2. Supported Platform/Driver/Tape Drive Combinations...64 Table 3. Cartridge/Drive Affinity Table...66 Table 4. Paging Space Info...79 Table 5. Gatekeeping Call Parameters...100 Table 6. Suggested Block Sizes for Disk...107 Table 7. Suggested Block Sizes for Tape...108 Table 8.
Page 14 About this book The HPSS Installation Guide is for use both at system installation time as well as throughout the lifetime of the system. It will guide system administrators through the planning and installation of a new HPSS system. It also guides system administrators through the conversion process to upgrade existing HPSS systems to Release 6.2.
Page 15: Chapter 1. Release 6.2
Chapter 1. Release 6.2 This chapter summarizes HPSS changes for Release 6.2 into four categories: new features, retired features, deferred features, and changed features. Changes since release 4.5 and 5.1 are described. 1.1. New Features This section describes the new HPSS features added to Release 6.2. 1.1.1.
Page 16: Additional Hpssadm Operations
1.1.10. Additional Library and Device Support Spectra Logic library • ADIC Scalar i500 library • IBM and HP LTO Generation 3 and 4 drives. Tape encryption has not been certified with • HPSS. SAIT-1 drives • IBM TS1120 (3592 Generation 2 and 3) drives. Tape encryption has not been certified with •...
Page 17: Drive Pools
1.1.12. Drive Pools HPSS provides HPSS end clients the ability to direct tape read I/O requests to a predefined group of tape drives referred to as a Drive Pool. This ability helps HPSS administrators manage tape drive scheduling and thus availability. For more information, please refer to Section 7.3: Drive Pools of the HPSS Management Guide.
Page 18: Mover Enhancement
1.1.18. Mover Enhancement Multiple Movers for one or more HPSS instances can now be configured to run on the same machine. The -c <alternate var path> flag is added to the Mover entry in the inetd configuration file to specify an alternate "/var/hpss"...
Page 19: Dmap Gateway Changes
Core Server's memory image Modified the DMG table. In support of the new HPSS RPC library, the TCP port was • eliminated and the Program and Version numbers were added to DMG specific configuration. Modified the DMGFILESET table. The TCP port was eliminated and the TCP hostname and •...
Page 20: 2.Viewing Dmap Gateway Xdsm Fileset Information
filesystems do not support mirrored namespaces, fields which were specific to managing mirrored filesets are also no longer available. This includes the following configuration options: Global Mount Point · Local Mount Point · Fileset Owner · Fileset Permissions · Communication between the HDM and the DMAP Gateway now uses the HPSS RPC library. •...
Page 21: Ssm Changes
1.4.4. SSM Changes Significant changes were made in SSM between Releases 4.5 and 5.1 and again between 5.1 and 6.2. For the reader's convenience, all changes between 4.5 and 6.2 are summarized in Section 3.3.4.1: Changes Affecting Sites Upgrading Directly from 4.5. Changes between 5.1 and 6.2 are summarized in Section 3.3.4.2: Changes Affecting Sites Upgrading from 5.1.
Page 22 Changes since 4.5 The SSM client scripts now use an internal polling mechanism for getting window updates (as opposed to being notified of the update by the server). This means that: The SSM client application no longer requires a second •...
Page 23 Changes since 4.5 The SSM client scripts can use ports exempted by the network administrator as firewall exceptions. See the -n option on the hpssadm/hpssgui man pages. The port on which the System Manager will listen may be controlled by setting the $HPSS_SSM_SERVER_LISTEN_PORT environment variable.
Page 24 Changes since 4.5 The ability to see which users are logged into SSM, referred to in HPSS 4.5 as a list of SSM "consoles", is available in 6.2 as part of the System Manager Statistics window from both the hpssgui and hpssadm. The menu bar has been reorganized extensively.
Page 25 Changes since 4.5 Column ordering is now controlled by dragging columns to the desired location. The modified order is preserved automatically in the user preferences across hpssgui restarts. When messages have been written to the status bar, the most recent messages can be viewed in the status bar's tooltip.
Page 26 Changes since 4.5 The HPSS 4.5 hpssadm commands pvr_cartridge • pvl_volume • ss_pv • ss_map • ss_vv • have been replaced by a single command "volume". The volume command has a required option "-type" for which these types may be specified: PVL Volume Information •...
Page 27: 2.Changes Affecting Sites Upgrading From 5.1
Changes since 4.5 The hpssadm config command now supports the additional structures: Class of Service Config • Storage Class (but not subsystem-specific storage class options) • Global Config • Accounting Policy • Location Policy • All server configurations; servers which were not supported before are •...
Page 28 Changes since 5.1 Options to the hpssgui and hpssadm startup scripts have changed significantly. See the man pages for details. Following are some highlights: The scripts are dependent upon an ssm configuration file (ssm.conf), created by mkhpss, which contains some site-specific configuration values.
Page 29 Changes since 5.1 The SSM client script options for connecting to the System Manager across a Virtual Private Network connection (VPN) have changed. See the -p and -h options on the hpssgui and hpssadm man pages. The SSM client script option for using ports exempted by the network administrator as firewall exceptions has changed;...
Page 30 Changes since 5.1 The menu bar has been reorganized slightly. The "Data Server Statistics" menu item has been replaced by the "System Manager Statistics" menu item, available from the Monitor->SSM Information menu path. "Column View" was added to the menu bar for SSM windows that display an SSM table.
Page 31 Changes since 5.1 The mechanism for selecting columns to be displayed in each list window has moved from the list's Preferences window to the "Column View" menu of the list window itself. See the description of the "Column View" menu item in Section 3.6: Common Window Elements of the HPSS Management Guide for details.
Page 32 Changes since 5.1 Since SSM now represents the three Core Server volume structures as a single structure, the types specified to the hpssadm volume command have changed. The 5.1 types: Disk Storage Map Information • Disk Physical Volume Information • Disk Virtual Volume Information •...
Page 33 Changes since 5.1 A new subcommand “update” has been added to the hpssadm device command for updating the mover device and pvl drive objects. HPSS Installation Guide Release 6.2 (Revision 2.0) Server July 2008...
Page 34 HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 35: Chapter 2. Hpss Basics
HPSS. HPSS is the result of a collaborative effort by leading US Government supercomputer laboratories and industry to address very real, urgent high-end storage requirements. HPSS is offered commercially by IBM. HPSS provides scalable parallel storage systems for highly parallel computers as well as traditional supercomputers and workstation clusters.
Page 36: Based On Standard Components
These components are offered on many vendors’ platforms. The full HPSS system has been implemented on IBM AIX and LINUX platforms, and some components of HPSS have been ported to other platforms. Refer to Section 2.4: HPSS Hardware Platforms on page 48 and Section 3.3: Prerequisite Software Considerations on page 58 for specific...
Page 37: Hpss Components
2.3. HPSS Components The components of HPSS include files, filesets, junctions, virtual volumes, physical volumes, storage segments, metadata, servers, infrastructure, user interfaces, a management interface, and policies. Media and file metadata are represented by data structures that describe the attributes and characteristics of storage system components such as files, filesets, junctions, storage segments, and volumes.
Page 38: Hpss Files, Filesets, Volumes, Storage Segments And Related Metadata
Figure 2. Class of Service / Hierarchy / Storage Class 2.3.1. HPSS Files, Filesets, Volumes, Storage Segments and Related Metadata The various metadata constructs used to describe the HPSS namespace and HPSS storage are described below: Files (Bitfiles) Files in HPSS, called bitfiles in deference to IEEE Mass Storage Reference •...
Page 39 recorded on these tapes. HPSS supports grouping files on tape volumes only. Families can only be specified by associating the family with a fileset. All files created in the fileset belong to the family. When one of these files is migrated from disk to tape, it is recorded on a tape with other files in the same family.
Page 40: Hpss Servers
Class of Service (COS). Each bitfile has an attribute called Class Of Service. The COS • defines a set of parameters associated with operational and performance characteristics of a bitfile. The COS results in the bitfile being stored in a storage hierarchy suitable for its anticipated and actual size and usage characteristics.
Page 41 consisting of directories, files, and links. These name space objects may exist within filesets that are connected via junctions. Second, the Core Server provides the abstraction of logical bitfiles to its clients. A bitfile is identified by a Core Server generated name called a bitfile ID. Clients may reference portions of a bitfile by specifying the bitfile ID and a starting address and length.
Page 42 The purpose of tape file migration is to make an additional copy (or multiple additional copies) of a file, in a tape storage class, to a lower level in the hierarchy. It is also possible to move files downwards instead of copying them. In this case there is no duplicate copy maintained.
Page 43 Physical Volume Repository (PVR) • system may contain multiple PVRs, each cartridge is managed by only one. PVRs provide APIs for clients to request cartridge mounts and dismounts and query the status of cartridges. For convenience, PVRs are often configured in one-to-one correspondence to tape libraries. For information on the types of tape libraries supported by HPSS PVRs, see Section 3.4.2: Robotically Mounted Tape on page 62.
Page 44: Hpss Storage Subsystems
2.3.3. HPSS Storage Subsystems The goal of storage subsystems (or just “subsystems”) is to increase the scalability of HPSS by allowing multiple Core Servers to be used within a single HPSS system. Every HPSS system is partitioned into one or more subsystems. Each subsystem contains a single Core Server. If migration and purge are needed, then the subsystem should contain a single Migration/Purge Server.
Page 45 HPSS Core Server performs most of the HPSS metadata changes using the transaction management tools provided by DB2. For the most part, these metadata transactions are managed entirely within the Core Server. Other servers such as MPS and PVL modify their metadata transactionally, and those transactions are entirely contained within those servers.
Page 46: Hpss User Interfaces
HPSS. A delog function is provided to extract and format log records from a central or archived log file. Delog options support filtering by time interval, record type, server, and user. Accounting. The HPSS accounting system provides the means to collect usage information in •...
Page 47: Hpss Policy Modules
GUI. The hpssgui simplifies the management of HPSS by organizing a broad range of technical data into a series of easy-to-read graphic displays. The hpssgui allows monitoring and control of virtually all HPSS processes and resources from windows that can easily be added, deleted, moved, or overlapped as desired.
Page 48: Hpss Hardware Platforms
HPSS distribution image. Maintenance of the PFTP and Client API software on platforms other than AIX and Linux is the responsibility of the customer, unless a support agreement is negotiated with IBM. Contact your HPSS Support Representative for information on how to obtain the needed software.
Page 49: Mover Platforms
The following matrix illustrates which platforms support HPSS interfaces. Table 1. HPSS Client Interface and Mover Platforms Platform PFTP Client Client API IBM AIX Sun Solaris (Big Endian ONLY) Digital UNIX Not Tested Hewlett-Packard HPUX Not Tested Silicon Graphics IRIX...
Page 50: Hpss Installation Guide July
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 51: Chapter 3. Hpss Planning
3.1. Overview This chapter provides HPSS planning guidelines and considerations to help the administrator effectively plan, and make key decisions about, an HPSS system. The planning process for HPSS must be done carefully to ensure that the resulting system satisfies the site’s requirements and operates in an efficient manner. We recommend that the administrator read this entire chapter before planning the system.
Page 52: Hpss Configuration Planning
Figure 4. HPSS Generic Configuration 3.1.2. HPSS Configuration Planning Before beginning the planning process, there is an important issue to consider. HPSS was designed to optimize the transfer of large files at the expense of some small file transfer performance. If at all possible, try to reduce the number of small files that are introduced into your HPSS system.
Page 53 aggregate the individual files into large individual files before moving them into the HPSS name space. The following planning steps must be carefully considered for the HPSS infrastructure configuration and the HPSS configuration phases: 1. Identify the site’s storage requirements and policies, such as the initial storage system size, anticipated growth, usage trends, average file size, expected throughput, backup policy, and availability.
Page 54: Purchasing Hardware And Software
more information about configuring families. Plan for filesets and junctions, if any. Refer to Chapter 10: Filesets and Junctions in • the HPSS Management Guide for more information. Plan for HPSS storage classes. Refer to Section 3.10.1: Storage Class on page 102 for •...
Page 55: Hpss Operational Planning
3.1.4. HPSS Operational Planning The following planning steps must be carefully considered for the HPSS operational phase: 1. Define the site guidelines for the HPSS users and SSM users. Each HPSS user who uses the storage services provided by HPSS should be assigned •...
Page 56: Requirements And Intended Uses For Hpss
guide that the HPSS support/deployment team uses to monitor and check the progress of an installation. 3.2. Requirements and Intended Uses for HPSS This section provides some guidance for the administrator to identify the site’s requirements and expectations of HPSS. Issues such as the amount of storage needed, access speed and data transfer speed, typical usage, security, expected growth, data backup, and conversion from an old system must be factored into the planning of a new HPSS system.
Page 57: Duplicate File Policy
3.2.5. Duplicate File Policy The policy on duplicating user data files impacts the amount of data stored and the amount of data moved. If all user files are duplicated, the system will require twice as much tape storage. If users perform their own duplication of files, the system may consume a smaller amount of storage space.
Page 58: High Availability Option
3.3.1.1. DB2 HPSS uses the DB2 Universal Database Enterprise Server Edition by IBM Corporation to manage all HPSS metadata. DB2 software is included in the HPSS distribution. Refer to Section 5.3.1.2: Install HPSS Documentation and DB2 Software on page 141 for more information. The required DB2 FixPak must be downloaded and installed after the DB2 base is installed.
Page 59: 3.Ldap And Ibm Kerberos
- 306.ibm.com/software/tivoli/resource - center/security/code-directory - server.jsp webpage . Installing the IBM Kerberos client is only required if LDAP is being used for authorization and the LDAP daemon will be used for Kerberos authentication. This option is supported only on AIX. The fileset for the IBM Kerberos client is located on the AIX Expansion Pack CD.
Page 60: 1.2.Linux Requirements
• C compiler for Linux: gcc-3.4.5 (if planning to recompile HPSS code on this node) • IBM ATL: ibmatl-5.3.9.0-0 (if planning to use IBM tape library and drives from this node) • 3.3.2.2. HPSS Mover Nodes A Mover consists of two processes: the mover administrative process that runs on the server node, and the remote mover process that handles the HPSS devices and data transfers.
Page 61: 2.3.Solaris Requirements
1 GB RAM • 3.3.2.2.3. Solaris Requirements Each Solaris Mover node must have the following prerequisites: Solaris UltraSPARC based processor • Solaris 8+ (32-bit or 64-bit) • C compiler: Forte Developer 7 C 5.4 2002/03/09 (if planning to recompile Mover code) •...
Page 62: Hardware Considerations
PVR. The tape libraries supported by HPSS are: IBM 3494 • IBM 3582, 3583, 3584 (LTO). These libraries are now being called the IBM TS3500. • Spectralogic T120 (LTO, SAIT) • STK L40 (LTO) •...
Page 63: 1.Ibm 3494
3.4.2.2. Drive-Controlled LTO Libraries (IBM 3582, IBM 3583, IBM 3584, Spectralogic T120) The IBM 3582, IBM 3583, IBM 3584, and Spectralogic T120 Tape Libraries and Robots must be attached to Linux or AIX workstation through a SCSI interface. In each case, the library shares a SCSI channel with one of the drives, so at least one of the drives in the library must be connected to the workstation.
Page 64: 1.Multiple Media Support
3590E drive if and only if there are no single-length 3590E drives configured in the system. IBM 3592 and 3580 tape technologies support multi-generation reads and writes. The HPSS PVL which is responsible for creating the mount list, does not know the difference between a read and a write request.
Page 65: Hpss Installation Guide July
(LTO) Gen4 drive can read 3580 (LTO) Gen4, 3580 (LTO) Gen3, and 3580 (LTO) Gen2 cartridges, but can only write 3580 (LTO) Gen4 and 3580 (LTO) Gen3 cartridges), HPSS will mount a 3580 (LTO) Gen2 cartridge into a 3580 (LTO) Gen4 drive only if 3580 (LTO) Gen2 drives are not defined in HPSS and 3580 (LTO) Gen3 drives are either busy or not defined.
Page 66: Table 3. Cartridge/Drive Affinity Table
Table 3. Cartridge/Drive Affinity Table Cartridge Type AMPEX DST-312 AMPEX DST-314 Single-Length 3590 Double-Length 3590 Single-Length 3590E Double-Length 3590E Single-Length 3590H Double-Length 3590H 3580 (LTO) Gen 1 3580 (LTO) Gen 2 3580 (LTO) Gen 3 HPSS Installation Guide Release 6.2 (Revision 2.0) Drive Preference List AMPEX DST-312 AMPEX DST-314...
Page 67: Disk Devices
3580 (LTO) Gen 4 3592 J1A Short Tape 3592 J1A Standard Tape 3592 EO5 JJ Short Tape 3592 EO5 JA Standard Tape 3592 EO5 JB XL Tape 3592 EO6 JJ Short Tape 3592 EO6 JA Standard Tape 3592 EO6 JB XL Tape STK 9840A STK 9840B STK 9840C...
Page 68: Special Bid Considerations
Fibre Channel. For these devices, operating system disk partitions of the desired size must be created (e.g., AIX logical volume or Linux/Solaris/IRIX disk partition), and the raw device name must be used when creating the Mover Device configuration (see Section 7.1: Configure a New Device & Drive of the HPSS Management Guide for details on configuring storage devices).
Page 69: Hpss User Storage Space
Starting with HPSS 6.2 there are many enhancements to the storage system to take advantage of Storage Area Networks. Though separated in Figure 4, in reality there is usually only one SAN at an installation and all the resources are attached to it. Besides the HPSS Movers being connected to SAN, the end-user clients are often SAN attached as well.
Page 70: Figure 5. Basic Hpss Metadata & Filesystem Allocation
Figure 5. Basic HPSS Metadata & Filesystem Allocation On the left hand side of the diagram, the raw physical volumes are shown attached to the disk array controller. The configuration of the disks by the controller and its software should be divided into three separate LUNs: 1) HPSS Filesystems and DB2 Backups, 2) DB2 Logs, 3) and the DB2 Tables.
Page 71: Hpss Filesystems
mirrored log components will need to be determined by HPSS and the customer based on transaction performance requirements. Potentially, disk resources primarily allocated for HPSS disk cache can be used or the site may want to dedicate a second disk array for this purpose to prevent any possible interference.
Page 72: 3./Var/Hpss/Adm/Core
to create a site policy configuration file, usually named /var/hpss/gk/gksitepolicy. The size of this file depends on the site-implemented gatekeeping policy. If the Gatekeeper Service is not used, there is a minimal amount of disk space used in this directory. If an Accounting report is requested, a report file and a checkpoint file are created in the •...
Page 73: 7./Db2/Backups/Subsys1 & Subsysx
3.5.3.7. /db2/backups/subsys1 & subsysX Similar to /db2/backups/cfg, the /db2/backups/subsys1 filesystem temporarily stores backup images of the subsystem archived logs and database as they are generated. The backup files are then transferred to long-term media, such as tape, using a backup file manager such as TSM. Details are described in the Section 3.5.4.4: DB2 Disk Space on page 77.
Page 74: Hpss Metadata Space
Section 5.3.1.2: Install HPSS Documentation and DB2 Software on page 141. The tables and indexes are separated into separate logical volumes/partitions to ease future expansion of the database and to maximize performance of database operations. For Linux, access to a /dev/hdxy partition is through the Linux buffered I/O system. While this is an appropriate access method for a filesystem that supports journaled logging, for DB2 and Mover accesses, non-buffered IO is required.
Page 75 disk devices. The “6.2 Sizing Spreadsheet” input tab is shown below. Based on the input, the resulting output is show below: HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 76 Definitions for the DB2 tables are as follows: Bitfile Disk Allocation Maps. (BFDISKALLOCREC) For each bitfile stored on disk, one or more rows will be created in the Disk Allocation Maps table. The number of rows is determined by the storage segment size in the Storage Class in which the files are stored and the average file size stored in that Storage Class.
Page 77: 4.Db2 Disk Space
bytes. Disk Storage Segments. (STORAGESEGDISK) Expect the size of the disk storage segment metadata table to be quite volatile. As files are added to HPSS, disk storage segments will be created, and as files are migrated to tape and purged from disk, they will be deleted. A rough estimate of the number of disk storage segments can be obtained by estimating the number of files that will be resident on disk in the subsystem for each Storage Class, then multiplying by the Average Number of Segments parameter of the Storage Class.
Page 78: System Memory And Disk Space
created will require approximately 10MB of disk space in a filesystem that should be used only for database home directories and other DB2 home directories (such as the DB2 Administration Server and Fenced User). This filesystem should be protected by RAID since DB2 may require information in the database home directory to properly recover a database.
Page 79: Hpss Interface Considerations
The amount of memory for nodes running HPSS Movers, and no DB2 servers, is dependent on the number and types of devices configured on the Mover node, the expected usages of those devices, and the configuration of the Movers memory than Movers supporting tape devices because disk devices are likely to have more outstanding requests.
Page 80: Parallel Ftp
Class of Service and Accounting Code information. In addition, the chgrp, chmod, and chown commands are supported as quote site options. The FTP daemon is built on top of the Client API and must be run on a node that supports Kerberos clients.
Page 81: Core Server
3.7.1. Core Server The Core Server is responsible for managing the HPSS name space (files, directories, links, etc.), bitfiles, and storage (physical volumes, virtual volumes, etc.) for a single subsystem. Each of these areas of responsibility are outlined in greater detail below. Core Server at large The Core Server uses POSIX threads to service concurrent requests.
Page 82: Figure 6. The Relationship Of Various Server Data Structures
Figure 6. The Relationship of Various Server Data Structures Disk Storage Allocation Each Core Server manages disk storage units for HPSS. It maps each disk storage unit onto an HPSS disk Physical Volume (PV) and records configuration data for the PV. Groups of one or more PVs (disk stripe groups) are managed by the server as disk Virtual Volumes (VVs).
Page 83: Migration/Purge Server
The Core Server is designed to scale up its ability to manage tapes as the number of tapes increases. As long as sufficient memory and CPU capacity exist, threads can be added to the server to increase its throughput. Additional subsystems can also be added to a system, increasing concurrency even further.
Page 84: Gatekeeper
metadata updates and can impose extra overhead on DB2. Also, unpredictable purge behavior may be observed if the purge record ordering is changed with existing purge records in the system until these existing records are cleared. A purge run ends when either the supply of purge records is exhausted or the purge target is reached.
Page 85 Sites can choose to configure zero (0) or more Gatekeepers per HPSS system. Gatekeepers are associated with storage subsystems. Each storage subsystem can have zero or one Gatekeeper associated with it and each Gatekeeper can support one or more storage subsystems. Gatekeepers are associated with storage subsystems using the Storage Subsystem Configuration screen (see Section 4.2: Storage Subsystems of the HPSS Management Guide).
Page 86: Location Server
requests from a particular host or user. The Site Interfaces will be located in a shared library that is linked into the Gatekeeper. It is important that the Site Interfaces return a status in a timely fashion. Create, open, and stage requests from MPS are timing sensitive, thus the Site Interfaces won't be permitted to delay or deny these requests, however the Site Interfaces may choose to be involved in keeping statistics on these requests by monitoring requests from Authorized Callers.
Page 87: 1.Stk Pvr
PVR can issue them to the 3584. HPSS is designed to work with the AIX tape driver (Atape) software to talk to the IBM 3584 LTO Library over a SCSI channel. Currently HPSS is only supported for the AIX version of the Atape driver.
Page 88: 3.3494 Pvr
3.7.6.3. 3494 PVR The 3494 PVR can manage an IBM 3494 tape robot attached via Ethernet or SCSI. The PVR will create a process to receive asynchronous notifications from the robot. At least one PVR should be created for every robot managed by HPSS. If multiple 3494 robots are managed, care must be taken to ensure that the PVRs are configured to communicate with the correct /dev/lmcp devices.
Page 89: Mover
For Solaris, the method used to enable variable block sizes for a tape device is dependent on the type of driver used. Supported devices include Solaris SCSI Tape Driver and IBM SCSI Tape Driver. For the IBM SCSI Tape Driver, set the block_size parameter in the /opt/IBMtape/IBMtape.conf configuration file to 0 and perform a reboot with the reconfiguration option.
Page 90: 2.3.Irix
Driver has a built-in configuration table for all HPSS supported tape drives. This configuration provides variable block size for most HPSS supported drives. In order to override the built-in configuration, device information can be supplied in the /dev/kernel/st.conf as global properties that apply to each node.
Page 91: 4.Performance
A number of conditions can influence the number of Movers configured and the specific configuration of those Movers: Each Mover process is built to handle a specific device interface, e.g., IBM SCSI-attached • 3590/3590H/3580 drives. If multiple types of devices are to be supported, multiple Movers must be configured.
Page 92: Startup Daemon
3.7.9. Startup Daemon The Startup Daemon is responsible for starting, monitoring, and stopping the HPSS servers. The Daemon responds only to requests from the SSM System Manager. It shares responsibility with each HPSS server for ensuring that only one copy of the server runs at a given time. It helps the SSM determine whether servers are still running, and it allows the SSM to send signals to servers.
Page 93 values may need to be overridden in env.conf. Key SM Environment Variables Variable HPSS_SM_SRV_CONNECT_FAIL_COUNT HPSS_SM_SRV_CONNECT_INTERVAL_MI HPSS_SM_SRV_CONNECT_INTERVAL_MA HPSS_SM_SRV_MONITOR_THREADS HPSS_SM_SRV_QUEUE_SIZE HPSS_SM_SRV_TPOOL_SIZE HPSS Installation Guide Release 6.2 (Revision 2.0) Default Functionality Value Connection Fail Count: number of connection failures to a server before the Max Connection Interval takes affect (*) Interval between attempting server connections when Connection Fail...
Page 94: Storage Subsystem Considerations
Variable HPSS_SM_SRV_MAX_CONNECTIONS * The SM attempts to throttle the connection attempts to other servers. It will attempt to reconnect to each server every HPSS_SM_SRV_CONNECT_INTERVAL_MIN seconds until the number of failures for that server has reached HPSS_SM_SRV_CONNECT_FAIL_COUNT. After the failure count has been reached the SM will only try to reconnect to the server every HPSS_SM_SRV_CONNECT_INTERVAL_MAX seconds until a successful connection is made at which time the connection interval for the server will be set back to HPSS_SM_SRV_CONNECT_INTERVAL_MIN.
Page 95: 2.Migration Policy For Tape
Disk migration is controlled by several parameters. By default, these parameters are the same across all subsystems. However, subsystem-specific policies may be created which override all of these values. For a list of these parameters, refer to Section 6.4.2.2: Disk Migration Policy Configuration in the HPSS Management Guide.
Page 96: Accounting Policy And Validation
storage class by periodically extracting this information from the HPSS Core Server. Based upon parameters in the purge policy, a purge run will be started when appropriate. The administrator can also force the start of a purge run via SSM. The disk purge is controlled by several parameters: The Do not purge files accessed within <nnn>...
Page 97 out of the hpssGECOS field, it does not exist in UNIX. It only exists in LDAP. The metadata for each file and directory in an HPSS system contains an Account field, which determines how the storage will be charged. Each user has at least one default account index, which is put into the Account field of all new files and directories .
Page 98: Security Policy
the principal's LDAP hpssGECOS attribute, then Site-style accounting will be used. Otherwise UNIX-style accounting will be used. To keep the accounting information consistent, it is important to set up all users in the HPSS Authorization services with the same style of accounting (i.e. they should all have the AA= string in their hpssGECOS attribute or none should have this string.) The hpss_ldap_admin tool can be used to set attributes for a user including the hpssGECOS field.
Page 99: 5.Security Audit
3.9.4.5. Security Audit HPSS provides the ability to record information about authentication, file creation, deletion, access, and authorization events. The security audit policy in each HPSS server determines what audit records a server will generate. In general, all servers can create authentication events, but only the Core Server will generate file events.
Page 100: Table 5. Gatekeeping Call Parameters
Gatekeeper configured in its storage subsystem. If one is found, the Core Server asks the Gatekeeper for its monitor types by calling the gk_GetMonitorTypes function which calls the locally implemented gk_site_GetMonitorTypes function which determines which types of requests to monitor. This query by the Core Server occurs each time the Core Server connects to the Gatekeeper, which occurs whenever the Core Server or Gatekeeper is restarted.
Page 101: Storage Characteristics Considerations
DOWN or when the user application is aborted. NOTES: 1. All open requests to the Core Server will call the Gatekeeping Service open API (gk_Open). This includes opens that end up invoking a stage. 2. Any stage call that is invoked on behalf of open will NOT call the Gatekeeping Service stage API (gk_Stage).
Page 102: Storage Class
(VVs). Each VV contains one or more PVs. The VV characteristics described by a Storage Class include the VV Block Size and VV Stripe Width. If PVs are grouped one at a time, so that their Stripe Width is one, they are still defined as VVs. A number of additional parameters are defined in Storage Classes.
Page 103: 1.Media Block Size Selection
SSM provides the capability to define storage classes and to add and delete virtual volumes to and from the defined storage classes. A storage class is identified by a storage class ID and its associated attributes. For detailed descriptions of each attribute associated with a storage class, see Section 6.1.1: Configuring a Storage Class of the HPSS Management Guide.
Page 104: 5.Blocks Between Tape Marks Selection (Tape Only)
utility programs copy data from one tape VV to another, so the number of available tape drives of the appropriate type must be at least twice the tape Stripe Width, for these programs to function. Migration of files between tape storage classes in a hierarchy, that are of the same media type, requires at least twice as many available tape drives as the Stripe Width of the Storage Class.
Page 105: 6.Minimum Storage Segment Size Selection (Disk Only)
streaming to maximize performance. For recommended values for various media types, see Section 3.10.1.12: Some Recommended Parameter Values for Supported Storage Media on page 106. 3.10.1.6. Minimum Storage Segment Size Selection (disk only) The Core Server maps disk files onto a series of disk storage segments. The size of the storage segments is controlled by the Min Storage Segment Size parameter, the Max Storage Segment Size parameter, and the Average Number of Segments parameter.
Page 106: 8.Maximum Vvs To Write (Tape Only)
3.10.1.8. Maximum VVs to Write (tape only) This parameter restricts the number of tape VVs, per Storage Class, that can be concurrently written by the Core Server. Its purpose is to minimize the number of tape mounts and to limit the number of tape VVs being written, to prevent files from being scattered over a number of tapes.
Page 107: 12.1.Disk Media Parameters
3.10.1.12.1. Disk Media Parameters Table 7 contains attributes settings for the supported disk storage media types. Table 6. Suggested Block Sizes for Disk Disk Type SCSI Attached SSA Attached Fibre Channel Attached In Table 7: Media Block Size is the block size to use in the Storage Class definition. For disk, this value •...
Page 108: Table 7. Suggested Block Sizes For Tape
Media Block Size Ampex DST-312 1 MB Ampex DST-314 1 MB IBM 3580 (LTO) 256 KB IBM 3580 (LTO Gen 2) 256 KB IBM 3580 (LTO Gen 3) 256 KB IBM 3580 (LTO Gen 4) 256 KB IBM 3590 256 KB...
Page 109: Storage Hierarchy
StorageTek T10000A 256 KB StorageTek T10000B 256 KB In the above table: Media Block Size is the block size to use in the Storage Class definition. This is the size of the • data blocks written to tape. Note that for tape devices, the Mover configuration does not contain the Media Block Size.
Page 110: Class Of Service
3.10.3. Class of Service Each HPSS file belongs to a single Class of Service (COS) which is selected when the file is created. It is selected via Class of Service Hints information passed to the Core Server when the bitfile is created.
Page 111: 4.Selecting Optimum Access Size
guaranteed that the file is completely and successfully staged before it is read. If the stage operation fails, the open will return with an error. Guideline 3: Select the Stage on Open Async option if you wish to stage the entire file to the top level in the hierarchy and do not want the Client API open to block.
Page 112: 6.Selecting Transfer Rate
Section 5.7: Tune DB2 on page 171. For a detailed discussion on tuning DB2, refer to the DB2 Performance Tuning Guide, an IBM redbook. The following is a list of areas to consider when optimizing DB2 performance for HPSS: Database usage •...
Page 113: Bypassing Potential Bottlenecks
Maximum users and applications connected to DB2 · Nature of usage: read or update · Database logging • Hardware or software mirroring · Disk speed and reliability: select the fastest, most reliable disk · Location of physical disks and database data: it is recommended that they be separate ·...
Page 114: Ftp/Pftp
directly to tape, the buffer size used by the FTP server and the virtual volume block size defined for the Storage Class being written to will have a significant impact. If the buffer size used by the FTP server is not a multiple of the virtual volume block size, each buffer written will result in a distinct storage segment on the tape.
Page 115: Client Api
3.11.5. Client API The Client API provides the capability to perform data transfer of any size (the size being parameters supplied by the client to the read and write interfaces). The size of the data transfers can have a significant impact on the performance of HPSS. In general, larger transfers will generate less overhead than a series of smaller transfers for the same total amount of data.
Page 116: Xfs
stage requests. The site policy could limit the maximum number of non-Authorized Caller requests allowed at once by either delaying or denying particular requests. To delay the request, the site policy may return a special retry status along with the number of seconds to wait before the Client API retries the request.
Page 117: Hpss Metadata Backup Considerations
3.12. HPSS Metadata Backup Considerations This section contains guidelines for proper maintenance of the HPSS metadata stored in DB2. The policies described should be fully understood and implemented to protect the HPSS metadata. Failure to follow these policies can lead to unrecoverable data loss. The remainder of this section is a set of rules associated with backing up HPSS metadata.
Page 118 HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 119: Chapter 4. System Preparation
“mysteriously” degrade for a variety of reasons. This is especially true for client access to the HPSS system. 4.1. General Setup Each HPSS administrator should request a login id and password for the IBM HPSS web site • at http://www.hpss-collaboration.org/hpss/IDRequired.jsp.
Page 120: Setup Filesystems
% mkdir -p /var/hpss/stats % cd /opt/hpss/tools/deploy/bin % lsnode > /var/hpss/stats/lsnode.out Obtain your HPSS Realm Id from IBM. This information will be needed when mkhpss is • used to configure HPSS. For an existing installation, this is the ID which was previously referred to as the DCE Cell ID.
Page 121: Hpss Filesystem
PVR is re-reading the library map. The problem is self correcting and should not require outside intervention, beyond issuing a “Mark Repaired” on the affected servers. 4.3.2. IBM 3584 If using an IBM 3584 tape library, install the Atape driver, configure the SCSI Medium Changer HPSS Installation Guide Release 6.2 (Revision 2.0)
Page 122 Perform these tests before starting HPSS as the SMC device may be opened by only one process at a time. For drives in an IBM 3584 robot, identify the robot-specific device id (LTO drive locations) for each Mover tape device. This will be required when configuring the tape drives within HPSS.
Page 123: Stk
To start the lmcp daemon: root% /etc/methods/startatl To test whether lmcp daemon is configured and working correctly: % mtlib -l<lmcpDevice> -qL where lmcpDevice is usually /dev/lmcp0. To test ability to use lmcp daemon to mount a tape: % mtlib -l/dev/lmcp0 -m -V<tapeLabel> -x<deviceNumber> Test ability to dismount the tape: % mtlib -l/dev/lmcp0 -d -V<tapeLabel>...
Page 124: Verify Tape Drives
If using STK drives, verify that the drive type is not incorrectly set to Generic tape drive or • IBM Emulation mode. On each Tape Mover node, verify that the raw read and write I/O performance of all HPSS •...
Page 125: Solaris
To measure read performance on drive rmt1 using the previously-written uncompressed and compressed files: % iocheck -r -t 20 -b 1mb /dev/rmt1.1 % iocheck -r -t 20 -b 1mb /dev/rmt1.1 To unload a tape: % tctl -f <device> rewoffl Repeat the above steps for each tape drive. 4.4.2.
Page 126: Irix
4.4.3. IRIX On each Tape Mover node, verify that each tape drive has the variable-length block size option enabled. To determine if the variable block size option is enabled, the following should complete successfully: % dd if=/dev/null of=/dev/rmt/tps2d6nr bs=80 count=1 % dd if=/dev/null of=/dev/rmt/tps2d6nr bs=1024 count=1 If the variable-length block size option is not enabled, consult your driver documentation for procedures to enable it.
Page 127: Aix
4.5.1. AIX Verify that the correct number and type of disk devices are available on each DB2 and Disk • Mover node. The disk devices section of the lsnode report displays all available disk devices. To determine the type and number of available disk devices: % lsdev -C -S a -c disk If using SSA disks spread the SSA disks equally across the two loops on each SSA adapter.
Page 128: Linux
Use the iocheck.ksh script from the deployment tools package to show the performance of one or more individual disk devices and the peak aggregate performance of concurrent I/O across multiple disks (e.g., to show the peak performance of adapters). WARNING: The contents of this logical volume will be overwritten by iocheck so be sure to use the correct logical volume name.
Page 129: Setup Network Parameters
Install and configure all network interfaces and corresponding network connections. • Refer to IBM's internal network technologies home page for resources on configuring and tuning networks and TCP/IP. The network interfaces section of the lsnode report from each node shows the network interfaces that are configured.
Page 130 will be used. For Linux, a similar change should be made to /etc/nsswitch.conf: hosts: nis dns files For each AIX ethernet network interface, verify that the en0 and et0 interfaces are not both • configured at the same time (we recommend only using en0 unless the other nodes in the network are all using the 802.3 et* interface).
Page 131: Table 8. Network Options
ccs0 ccs0 You are looking for the best values possible for each network connection. These values will be used by HPSS to optimize its data transfers. This example is, by no means, a complete picture of what controls network performance. In fact, it is assumed that you have already optimized the networks.
Page 132: Hpss.conf Configuration File
There are also attributes that are specific to the individual network interface that may affect network performance. For example, the network interface for the IBM SP TB3 switch provides settings for the size of the send and receive pool buffer size, which have had an effect on throughput. It is recommended that the available interface specific documentation be referenced for more detailed information.
Page 133: Sp/X Switch Device Buffer Driver Buffer Pools
4.6.2. SP/x Switch Device Buffer Driver Buffer Pools IBM SP/x systems provide the capability to tune the buffer pool allocation in the switch device driver. Two variables can be changed: rpoolsize, which is the size of the buffer pool for incoming data, and spoolsize which is the buffer pool size for outgoing data.
Page 134 HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 135: Chapter 5. Hpss Installation And Infrastructure Configuration
The following sections discuss the steps that need to be taken in order to prepare the system for HPSS installation. 5.1.1. Distribution Media Obtain the HPSS software from your IBM HPSS customer support representative. The software is available on one of the following distribution media: CD-ROM (available 6.2.1 or later) •...
Page 136: Create Owner Account For Hpss Files
Table 9. Installation Package Sizes and Disk Requirements Platfor HPSS Package Name HPSSServer-6.2.0.0.lpp HPSSClientMover-6.2.0.0.lp HPSSSource-6.2.0.0.lpp Linux HPSSServer-6.2.0.0.rpm HPSSClientMover-6.2.0.0.rp HPSSSource-6.2.0.0.rpm IRIX HPSSClientMover-6.2.0.0.ta HPSSClientMover-6.2.0.0.pk (ALL) SSMHelp.tar 5.1.3. Create Owner Account for HPSS Files The HPSS software must be installed by a root user. In addition, a UNIX User ID of hpss and Group ID of hpss is required for the HPSS installation process to assign the appropriate ownership for the HPSS files.
Page 137: Install Prerequisite Software
5.2.2. Install MIT Kerberos (If Using Kerberos Authentication) The capability to use MIT Kerberos authentication is provided in HPSS 6.2, however, IBM Service Agreements for HPSS do not provide support for defects in MIT Kerberos. Kerberos maintenance/support must be site-provided.
Page 138: Install Prerequisite Software For Xfs Hdm
LDAP will use the version of DB2 that is installed from the HPSS installation CD. Installing the IBM Kerberos client is required only if LDAP is being used for authorization and you will be using Kerberos authentication with the LDAP daemon. The fileset for the IBM Kerberos client is located on the AIX 5.2 Expansion Pack CD #2.
Page 139: Install Hpss/Db2 And Configure Hpss Infrastructure
XFS uses the Linux udev daemon to dynamically configure the DMAPI device node. Use the chkconfig command to make sure that boot.udev is "on". Note that if a change is required, then the machine needs to be rebooted in order for it to take effect. 5.3.
Page 140 5. From the "Root Subsystem Machine" submenu, click on the 'Pre-Install Config' icon in the left panel. mkhpss will display the following screen: 6. Verify that the default values are correct for the given installation and modify if necessary. Click the 'Configure' button to perform the pre-installation setup. This will run a set of HPSS Installation Guide Release 6.2 (Revision 2.0) July 2008...
Page 141: 2.Install Hpss Documentation And Db2 Software
scripts to verify/create the 'hpss' account and group, setup the /var/hpss (default location) directory with the required subdirectories and initialize the HPSS environment file, env.conf in /var/hpss/etc. 7. If the pre-installation configuration succeeds, you will see the following message in the command output window: ## run command exited with status 0 Click the 'Done' button on the Command Output window to close the window.
Page 142: 3.Set Up Db2 Permanent License
DB2 software will be installed in the /usr/opt/db2_08_01 (AIX) or /opt/IBM/db2/v8.1 (Linux) directory. 2. For 6.2.0, the HPSS software and documentation should already be installed according to the installation step in section 5.3.1.1. Installing from CD will be an option starting in 6.2.1.
Page 143: 4.Configure Hpss Security Services
% su - % cd /usr/opt/db2_08_01/adm % ./db2licm -a <path name to the DB2 generic license file> The generic DB2 license file (*/db2/license/db2ese.lic) can be found on the DB2 Installation CD or image. It can also be obtained by contacting your HPSS Support Representative. To update the license with the appropriate number of of processors, issue the following command: % ./db2licm -n db2ese <number of processors>...
Page 144: Hpss Installation Guide July
3. Using the scrollbar, move the right-panel display until the "Authorization Service" information is seen. It should look like the following: HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 145 4. Select the "Configure Authorization Service" checkbox. Set the "Authorization Service" to "Unix and config files". 5. Review and modify (if necessary) the active fields: Local Site Name. The value is usually set to the full machine name of the local host •...
Page 146: 4.2.Configure Kerberos Authentication And Unix Authorization
configuration step. Other HPSS utilities are available to administer these HPSS configuration files. See section 2.2.2: Security Mechanisms in the HPSS Management Guide for more information. To use the HPSS configuration files, select the "Enable local Unix Passwd Files" checkbox. The default names for the files should be used as displayed. 7.
Page 147 KDC Directory. The pathname of the KDC directory. This directory should be set • to /var/hpss/krb5kdc. Master Password. The Kerberos administration password. • Be sure to remember this password to be able to administer the Kerberos environment later. Verify Password. Re-enter the Kerberos administration password. •...
Page 148 5. Select the "Configure Authorization Service" checkbox. Set the "Authorization Service" to "Unix and config files". 6. Review and modify (if necessary) the following authorization fields: Local Site Name. The value is usually set to the full host name of the local host. •...
Page 149: 4.3.Configure Kerberos Authentication And Ldap Authorization
8. Select the "Configure Server accounts" checkbox to create UNIX accounts for HPSS servers. 9. Click on the "Configure Security Services" button at the bottom of the screen to perform the specified security configuration. 10. If the configuration was a success, you should see the following message in the command output window: ## run command exited with status 0 Click the 'Done' button on the Command Output window to close the window.
Page 150 4. Select the "Configure Authorization Service" checkbox. Set the "Authorization Service" to "LDAP". 5. Review and modify (if necessary) the following authentication fields: Kerberos Install Path. The pathname where Kerberos is installed. The default • directory is /usr/kerberos. KDC Directory. The pathname of the KDC directory. This directory should be set •...
Page 151 Authentication Type. There are two supported options: Keytab File or Password. • The Keytab File option allows HPSS servers or utilities to read a keytab file to authenticate. The Password option requires a password to be supplied each time an HPSS server or utility is invoked.
Page 152: 5.Configure Db2 Services
Unix Passwd Files" checkbox as shown in the example above. The default names for the files should be used as displayed. 8. Select the "Configure Server accounts" checkbox to create accounts for HPSS servers. 9. Click on the "Configure Security Services" button at the bottom of the screen to perform the specified security configuration.
Page 153 3. Review and modify (if necessary) the following fields: Instance Owner. The name of the DB2 instance owner, normally 'hpssdb'. • Schema Name. The name of the DB2 schema containing the HPSS metadata table, • normally 'hpss'. Create DB2 Instance. Select this checkbox to create the DB2 instance. •...
Page 154 Create Subsys Database. Select this checkbox to create the "subsys1" database. • Subsystem Database Alias. The "real" database is configured as 'hsubsys1', while • the database alias is the name used by HPSS servers and utilities to reference the database. The default value of 'subsys1' should normally be used. Log File Directory.
Page 155 B. On the “Tablespace Config” window, set the Tablespace Type from the drop down menu. For the USERSPACE1 tablespace, select “SMS” System Managed Space. For the remaining tablespace entries, select Tablespace Type to "DMS" Database Managed Space. C. For USERSPACE1, which uses System Managed space, from the "Tablespace Config"...
Page 156 HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 157: 5.1.Remote Db2 Client Access & Fileset Creation/Deletion
F. Select the "Add" button to add "raw devices" to Container Path list. The "raw devices" must already exist. For AIX, the logical volumes must have already been created and the "raw" form be specified (i.e. LV "dbs1.tables", specify / dev/rdbs1.tables") For Linux, not only must the partition exist, but the "raw"...
Page 158: 6.Configure Other Services
a variable named DB2_USE_LOCAL_RESYNC set to the value of 'true' when starting DB2 in order for the aforementioned fileset operations to complete successfully: csh & tcsh: setenv DB2_USE_LOCAL_RESYNC true sh & bash: export DB2_USE_LOCAL_RESYNC=true 5.3.1.6. Configure Other Services This menu configures various services such as Parallel FTP, Java security for SSM, and SSM start scripts.
Page 159: 7.Create Configuration Bundle
4. After exiting mkhpss, verify permissions on the generated files. In particular, note the permissions on the keytab files. The hpss.keytab is used by HPSS servers to establish credentials. The mm.keytab is used by hpss utility programs. The kadm5.keytab is used to establish credentials as the Kerberos admin.
Page 160: Install And Configure Hpss - Secondary Subsystem Machine
5.3.2. Install and Configure HPSS – Secondary Subsystem Machine For the secondary subsystem machine, the following configuration steps must be performed: Pre-installation Configuration • Install HPSS documentation and DB2 • Set up DB2 permanent license • Install configuration bundle • Configure Security Services •...
Page 161: 2.Install Hpss Documentation And Db2 Software On A Subsystem
3. Verify that the default values are as desired. Modify them, if necessary. Click the 'Configure' button to perform the pre-installation setup. 4. If the pre-installation configuration was a success, you will see the following message in the command output window: ## run command exited with status 0 Click the 'Done' button on the Command Output window to close the window.
Page 162: 3.Set Up Db2 Permanent License
DB2 filesets you wish to install. DB2 software will be installed in the /usr/opt/db2_08_01 (AIX) or /opt/IBM/db2/v8.1 (Linux) directory. 2. For 6.2.0, the HPSS software and documentation should already be installed according to the installation step in section 5.3.2.1.
Page 163: 4.Install Configuration Bundle
% su - % cd /usr/opt/db2_08_01/adm % ./db2licm -a <path name to the DB2 generic license file> The generic DB2 license file (*/db2/license/db2ese.lic) can be found on the DB2 Installation CD or image. It can also be obtained by contacting your HPSS Support Representative. To update the license with the appropriate number of of processors, issue the following command: % ./db2licm -n db2ese <number of processors>...
Page 164: 5.Configure Hpss Security Services
5.3.2.5. Configure HPSS Security Services This section describes the procedure to configure a Kerberos or UNIX Security Client on the secondary subsystem machine. The security client must match the security mechanism on the root machine. To configure the security client for the secondary subsystem machine, perform the following steps: 1.
Page 165: 6.Configure Db2 Services
Configure server accounts. This checkbox is flagged when the server accounts • should be created on the local machine. This is usually not required when the Kerberos server has already been configured with the HPSS server accounts. 3. To configure the UNIX client, un-check the "Configure Kerberos Client" checkbox and select the "Configure server accounts"...
Page 166 2. Using the scrollbar, move the right-hand panel until you see the following screen: 3. Review and modify (if necessary) the following fields: Instance Owner. The name of the instance owner HPSS will use. Should use the • default value of 'hpssdb' in most cases. Schema Name.
Page 167: 7.Configure Other Services
Authentication Type. Currently there is only one authentication type allowed. • User Name. The UNIX userid to be used for DB2 authentication. This userid must • have a valid UNIX account before running this configuration option. Password and Verify Password. Enter and verify the UNIX password for the •...
Page 168: Install And Configure Hpss - Mover/Client Machine
"Configuration" icon and then the "Other Services" icon. The following window will be shown: 2. Click on the "Configure Other Services" button to complete the configuration of the Secondary Subsystem Machine. If the configuration was a success, you should see the following message in the command output window: ## run command exited with status 0 Click the 'Done' button on the Command Output window to close the window.
Page 169: 2.Install Configuration Bundle
Source Tree to obtain the source code from the root machine and install on the Mover/Client machine. 5.3.3.2. Install Configuration Bundle The configuration bundle is created on the root subsystem and contains configuration files used by the root, Mover/Client and subsystem machines. See page 159, section 5.3.1.7 Create Configuration Bundle for instructions on creating the Configuration Bundle on the root machine.
Page 170: Hpss Documentation & Manual
/opt/hpss/config/<HPSS configuration scripts> /opt/hpss/stk/<STK files> /opt/hpss/src/<HPSS source files> Included only if the hpss-src package is installed. /var/hpss/<HPSS configuration files> 2. Verify that the HPSS file ownerships and file permissions are set as follows: Executable files: • Include files: • Library files: •...
Page 171: Manual
bundle the HTML files for delivery to the hpssgui host machine. The recommended installation location for the HTML files on each hpssgui host is /var/hpss/doc for AIX and Linux platforms and c:\hpss\doc for Windows platforms. 5.5.2. Manual Page Setup Perform the following steps to set up HPSS manual pages: 1.
Page 172: Install And Build Hpss Source Code
DB2 tuning are referred to the HPSS DB2 Tuning Guide, available from your support representative, the DB2 Administrative Guide: Performance, available on-line from the IBM DB2 website, the IBM DB2 Tuning Redbook, and the many IBM and after-market books available on this subject.
Page 173: 3.Generate And Bind The Db2 Helper Program
DB_INSTALL_PATH = /usr/opt/db2_08_01 LDAP_INSTALL_PATH KRB5PATH GSIPATH Makefile.macros.LINUX: PVR_LIST LINUX_JAVA_ROOT = /usr/java/j2sdk1.4.2_05 DB_INSTALL_PATH = /opt/IBM/db2/V8.1 LDAP_INSTALL_PATH KRB5PATH GSIPATH 4. Log on as hpss. 5. Issue the "make clobber" command. 6. Issue the "make" command. 5.8.1.3. Generate and Bind the DB2 Helper Program When filesets are created or updated, it is sometimes necessary to make entries in both the global and the subsystem database.
Page 174: Construct And Build The Hpss Mover/Client Source Tree
1. Log on as hpss. 2. Change directory to /opt/hpss/bin. 3. Run the following command: % hpss_db2_bindall.ksh 5.8.2. Construct and Build the HPSS Mover/Client Source Tree This section describes the procedures to extract the Mover/Client code from the HPSS base source tree and to build the Mover/Client binaries.
Page 175: Construct And Build The Hpss Hdm Source Tree
5.8.3. Construct and Build the HPSS HDM Source Tree XFS is not supported in HPSS 6.2. XFS references have been left in the HPSS documentation to support the option of re-enabling XFS in future releases. This section describes the procedures to extract the HDM source code from the HPSS base source tree and to build the HDM binaries.
Page 176 You'll need to be logged in to Unix as user 'hpss' to have the needed permissions on the database. $ db2 (c) Copyright IBM Corporation 1993,2002 Command Line Processor for DB2 SDK 8.2.5 For more detailed help, refer to the Online Reference Manual.
Page 177 serverinterfaces where server_id = (select server_id from server where desc_name = 'SSM System Manager') and descriptive_name = 'Administrative Client Interface' AUTHN_MECH_SET_NUM_MECHS AUTHN_MECH_SET_MECHS1 ------------------------ --------------------- 1 record(s) selected. db2 => update server set (num_auth_mechs, authn_mechs1_mechanism, authn_mechs1_auth_type_key) = (2, 2, 1) where desc_name = 'SSM System Manager' DB20000I The SQL command completed successfully.
Page 178: Hpss Installation Guide July
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 179: Chapter 6. Upgrading To Hpss Release 6.2
PVLDRIVE and PVLACTIVITY tables by adding the new DRIVE_POOL_ID column to enable the new feature and setting the initial value to 0 since it will not be enabled by default. Contact IBM Support if an error occurs or if reversion to HPSS 6.2 is needed.
Page 180: Planning For The Hpss 6.2 Upgrade
6.2. Planning for the HPSS 6.2 Upgrade This section provides information necessary to plan the upgrade of an HPSS 4.5 or HPSS 5.1 system to HPSS 6.2. It is important that all planning information be reviewed carefully before performing the upgrade. 6.2.1.
Page 181 Modification of NFS metadata. In support of new authentication mechanisms, elimination of • credential object Id. Change privileged caller principal length from 15 to 255 characters. NFS is no longer supported. The NFS table contains converted metadata, but will be renamed to PRE62_NFS to prevent use.
Page 182: Upgrade Requirements And Limitations
information. New index definition for table. The metadata conversion is performed by the hpss_51_62_server conversion program. New SERVERINTERFACES table. This table is populated by the hpss_51_62_server • conversion with default server interface information. Modification of SITE table. In support of new authorization mechanism, elimination of •...
Page 183: 1.Authentication Mechanisms
hpss_ldap_import to convert DCE authorization information into LDAP. Kerberos authentication and Unix authorization. In this case, the site determines on its own • how to convert DCE authentication information into Kerberos. The site will then use hpss_unix_import to convert DCE authorization information into Unix. Depending on environment variables, the hpss_unix_import program may import authentication information (i.e.
Page 184: New Hpss 6.2 System Files
The hpss_dce_export and hpss_unix_import utilities are provided to convert DCE • authorization information. LDAP: Configuring LDAP is more complex than Unix. • Managing LDAP is fairly simple and does not require regular maintenance. • The hpss_dce_export and hpss_ldap_import utilities areprovided to convert DCE •...
Page 185: Running Time For The Long Running Metadata Conversion Utilities (For 4.5 Upgrades Only
three minutes, and the subsystem conversion took approximately 40 minutes. 6.2.6.1. Running Time for the Long Running Metadata Conversion Utilities (for 4.5 upgrades only) A system with more than 3 million HPSS files will see a significant performance gain from choosing to run the long running metadata conversion programs in parallel.
Page 186: Db2 Configuration And Tuning (For 4.5 Upgrades Only)
Services on page 165 and Section 5.7: Tune DB2 on page 171. For additional concerns about configuring DB2 that are not addressed, see the latest version of the DB2 UDB Performance Tuning Guide, an IBM redbook. Checking Database Configuration Settings To check database configuration setting, login as the database administrator or instance owner (e.g.
Page 187: Overview Of The Upgrade Utilities
% DB2 UPDATE DB CFG FOR <Database Name> USING <Setting> <Value> To reset to default settings, execute: % DB2 RESET DB CFG FOR <Database Name> Review and update the following: Associated with the database log are the log file size (LOGFILSIZ), the number of primary •...
Page 188: 2.Hpss 4.5 Upgrade Utilities
attributes pertinent to authorization are retained in HPSS 6.2. The program also optionally supports Unix authentication in HPSS 6.2 by obtaining each HPSS users’ password from DCE and preserving it in the Unix system or optionally into a local HPSS password file hpss_ldap_import –...
Page 189: 3.Hpss 5.1 Upgrade Utilities
load into the new table. db_convert_nsobject - This program converts the name server object metadata from the HPSS • 4.5 nsobjects SFS file to the HPSS 6.2 DB2 NSOBJECT and NSACL tables by reading records from SFS and performing DB2 loads into the new tables. db_convert_nstext - This program converts the name server text metadata from the HPSS 4.5 •...
Page 190: Hpss 6.2 Upgrade Procedures
hpss_md_convert_51. This program will rename the HPSS 5.1 tables by prepending the original table name with PRE62_ so that the original metadata in HPSS 5.1 is preserved. The hpss_md_convert_51 utility calls the following programs to perform the conversion: hpss_51_62_dmg – Reads the 5.1 metadata from the PRE62_DMG table, modifies the •...
Page 191: Install Authentication And Authorization Mechanisms
The steps in this section can be performed while the HPSS 4.5 or 5.1 system is running. LDAP requires 400MB free space in /opt/IBM/ldap/V6.0. To install LDAP, untar the LDAP release file (e.g. itds60-aix-ppc-native.tar). After the LDAP code is extracted, use smitty or the software installation tool of choice to install the code/packages.
Page 192 (e.g. . /home/hpssldap/sqllib/db2profile) 7. Setup DB2 instance for LDAP: % /opt/IBM/ldap/V6.0/sbin/idsicrt –n -e <random string> -I <ldap instance name> -t <user name> -l <dir for ldap instance> e.g. % /opt/IBM/ldap/V6.0/sbin/idsicrt -n -e [asUf4As].f -I idsldap -t idsldap -l /home/idsldap 8.
Page 193: Install Or Upgrade Db2
% /opt/IBM/ldap/V6.0/bin/idsldapmodify –c –i /opt/hpss/config/ HPSS_ldap_schema.ldif Note: where passwd is the password for the DN. In the example above, it would be the hpssldap user’s password since hpssldap is the DN used above and configured with LDAP on this system.
Page 194: Upgrade Aix
6.3.5. Upgrade AIX This step cannot be performed while the HPSS 4.5 or 5.1 system is running. This section applies to site that are upgrading to HPSS 6.2 from both HPSS 4.5 and HPSS 5.1. See Section 3.3.2: Prerequisite Summary By HPSS Node Type on page 59 for the the appropriate version of AIX required for HPSS 6.2.
Page 195: 1.Install Hpss 6.2 Distribution Image
6.3.8.1. Install HPSS 6.2 Distribution Image This step can be performed while the HPSS 4.5 or 5.1 system is running. Prior to installing the HPSS 6.2 code, sites should not disturb the current HPSS release code. It is possible for a site to revert to the previous release of HPSS at any point prior to the last step of starting the HPSS 6.2 servers.
Page 196: 3.Disable Binaries, Temporarily
code. Check $HPSS_ROOT/bin/convert62 to ensure the conversion programs compiled properly. The conversion utilities must include several Encina SFS files to compile and link using /usr/lpp/encina as the default pathname. If this problem is encounted during building the source code, create a link from /usr/lpp/encina to where the root Encina SFS directory resides.
Page 197 Next, use mkhpss and select the Configuration option and then Other Services option to configure the IEEE address for HPSS. This will create the /var/hpss/etc/ieee_802_addr file. This is only used by HPSS and will not affect other services on this system. Without performing this option the HPSS RPC mechanisms will fail.
Page 198 Environment variables are no longer kept in the $HPSS_ROOT/config subdirectory. Many are now kept in /var/hpss/etc/env.conf. The mkhpss utility will assist in creating the env.conf file and HPSS specific environment variables can be added to it. Before running the conversion utilities, ensure the following environment variables are properly defined.
Page 199: Setup Authentication And Authorization
MKHPSS_ROOT – set to the path of HPSS 6.2 code (e.g. "/opt/hpss") • HPSS_DB_INSTANCE_OWNER – the Unix User ID of the DB2 HPSS instance (e.g. • "hpssdb") HPSS_LDAP_BIND_TYPE – should correspond with the type of bindings allowed for LDAP • (e.g.
Page 200 HPSS_PRIMARY_AUTHN_MECH=krb5 HPSS_PRIMARY_AUTHENTICATOR=/krb5/hpss.keytabs Valid settings for unix authentication are: HPSS_PRIMARY_AUTHN_MECH=unix HPSS_PRIMARY_AUTHENTICATOR=/etc/passwd The new authorization is performed based on the contents of /var/hpss/etc/site.conf. This file will tell HPSS to use unix authorization, or to use LDAP and how to contact the LDAP server based on the URL entered.
Page 201 Using the scrollbar, move the right-panel scrollbar until the "Authorization Service" information is seen. It should look like the following: HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 202: Pre-Conversion System Check
6.3.11. Pre-Conversion System Check t is strongly recommended that a test conversion be performed prior to running the • conversion on a production system. See Section 184: Testing the Metadata Conversion on page 184 Ensure that the DB2 database has been configured prior to the conversion •...
Page 203: Take A Full Backup Of Sfs Or Db2
6.3.12. Take a full backup of SFS or DB2 This step should not be performed while the HPSS 4.5 or 5.1 system is running. The SFS or DB2 backup should be performed on the root and each non-root subsytem. Refer to the HPSS 4.5 or 5.1 Management Guide or contact your HPSS customer support representative for instructions on how to complete a SFS or DB2 backup.
Page 204: 3.Convert Configuration Metadata
The first program used in the 4.5 conversion is the information collection utility, db_convert_collect_info. This utility will gather configuration related information based on input provided about the 4.5 HPSS system. The program will save the information to several text files located in the /var/hpss/convert/6.2 directory.
Page 205: 5.Run The Long Running Utilities
subsystem Id of the subystem being converted as the command line arguments. For example, % su – root % db_subsys_convert This program provides an option to change all partially written HPSS 4.5 tapes to be read-only. When invoked, the option will force the storage map tape conversion to look at the current state (administrative and map states associated with storage map tape and tape virtual volume metadata) of each tape volume in HPSS 4.5 and, if the cartridge is determine to have data on it and be writable, it will set the state of the virtual volume to be non-writable.
Page 206 -db /var/hpss/convert/6.2/Convert.DB.Names \ -ss /var/hpss/convert/6.2/Convert.SS.Server.Ids \ -sub 1 % db_convert_bitfile –g /.:/encina/sfs/hpss/globalconfig \ -db /var/hpss/convert/6.2/Convert.DB.Names \ -sub 1 % db_convert_nsobject –g /.:/encina/sfs/hpss/globalconfig \ -db /var/hpss/convert/6.2/Convert.DB.Names \ -ns /var/hpss/convert/6.2/Convert.NS.Server.Ids \ -sub 1 % db_convert_nstext –g /.:/encina/sfs/hpss/globalconfig \ -db /var/hpss/convert/6.2/Convert.DB.Names \ -sub 1 % db_convert_storagesegdisk –g /.:/encina/sfs/hpss/globalconfig \ -db /var/hpss/convert/6.2/Convert.DB.Names \ -ss /var/hpss/convert/6.2/Convert.SS.Server.Ids \...
Page 207 root 1456 2034 0 16:04:08 pts/13 root 1567 1456 0 16:04:08 pts/13 Next, issue a 'kill -15 1381', sending a SIGTERM (kill -l, will list all signals and their appropriate number on your system) to the only the conversion C program, and not to any of the other bitfile conversion processes.
Page 208 -db /var/hpss/convert/6.2/Convert.DB.Names \ -sub 1 -restart When given the ‘-restart’ flag, the program will first attempt to determine that no other conversions or DB2 loads are currently running on the specific table. If a load or conversion is still running (due to failure to cleanup from an abnormal termination), the conversion should output a message and quit.
Page 209: 6.Create Core Server Acls
error occurs while reading metadata. A restart from a user termination (CTRL-C) works well 90% of the time. Sometimes a user termination can cause DB2 to output many system log errors (usually means the db2as, administrative server died). If the program is unable to perform a restart (i.e. an attempt to perform the restart and the program hangs or exits with an error again), there are steps to take to discover the problem.
Page 210: 7.Terminate The Scripting Session
environment variables to HPSS 4.5 values. Examples follow: HPSS_PRINCIPAL_SSM=hpss_ssm • HPSS_PRINCIPAL_FTPD=hpss_ftp • HPSS_PRINCIPAL_MPS=hpss_mps • HPSS_PRINCIPAL_NDCG=hpss_ndcg • HPSS_PRINCIPAL_NFSD=hpss_nfs • HPSS_PRINCIPAL_DMG=hpss_dmg • This allows the db_convert_dce_cds program to add proper DCE principals from HPSS 4.5 to a newly created core server ACL. Upon completion of the db_convert_dce_cds program, ensure the values are returned to valid HPSS 6.2 values.
Page 211: Verify Hpss 4.5 Conversion Results
machine to enable the HPSS 6.2 system to work properly. On several test machines, we had to open world access to the devices used by the HPSS Core Server and PVL in order for them to initialize properly. 6.3.14. Verify HPSS 4.5 Conversion Results Prior to running the verification utilities, we recommend that running the DB2 utility •...
Page 212: 3.Run Db_Convert_Ns_Check
ensure that the site has SFS and DB2 configured as expected. This program is not able to check the Name Server Objects (NSOBJECT) or ACLs (NSACL) table. The object count between two systems does not match because objects associated with deleted bitfiles are not converted. To invoke this utility, see the usage below: db_convert_size_check -g <SFS Global Config File>...
Page 213: 5.Terminate Scripting Session
check every bitfile descriptor in the 6.2 system. The -f and -l options check only the first and last number of bitfile descriptors provided with these options. To invoke this utility, see the usage below: db_convert_address_check -g <SFS Global Config File> -db <DB Names Text File>...
Page 214 Option 1 – Rename old tables [ renaming LSPOLICY table to PRE62_LSPOLICY ] [ renaming SERVER table to PRE62_SERVER ] [ renaming DMG table to PRE62_DMG ] [ renaming GATEKEEPER table to PRE62_GATEKEEPER ] [ renaming MOVERDEVICE table to PRE62_MOVERDEVICE ] [ renaming SITE table to PRE62_SITE ] Option 2 –...
Page 215: Enable Db2 Backup
6.3.16. Enable DB2 Backup Set up the DB2 backup process for HPSS metadata. Ensure that an initial backup of all HPSS databases are available at this point. Perform this step on each root and non-root subsystem. 6.3.17. Perform the DCE Export: hpss_dce_export This step applies to upgrades for both HPSS 4.5 and 5.1.
Page 216 5.1, set the non-default server principal values using the appropriate environment variable names: HPSS_PRE62_PRINCIPAL_CORE • HPSS_PRE62_PRINCIPAL_DMG • HPSS_PRE62_PRINCIPAL_FTPD • HPSS_PRE62_PRINCIPAL_GK • HPSS_PRE62_PRINCIPAL_HPSSD • HPSS_PRE62_PRINCIPAL_LOG • HPSS_PRE62_PRINCIPAL_LS • HPSS_PRE62_PRINCIPAL_MOUNTD • HPSS_PRE62_PRINCIPAL_MPS • HPSS_PRE62_PRINCIPAL_MVR • HPSS_PRE62_PRINCIPAL_PVL • HPSS_PRE62_PRINCIPAL_PVR • HPSS_PRE62_PRINCIPAL_SSM • HPSS_PRE62_PRINCIPAL_NFSD •...
Page 217: Prepare The 6.2 System
The conversion program that imports DCE authorization information into LDAP is called hpss_ldap_import. Usage: hpss_ldap_import <input dir> -realmname <realm> % hpss_ldap_import /var/hpss/convert/6.2 -realmname "cn=hpss.acme.com" Where the realmname option should use the name of the realm desired in LDAP. The program requires a path to the directory where expected input files reside (the same path used when running hpss_dce_export).
Page 218: 1.Tune Db2 For Normal Operations
6.3.19.1. Tune DB2 for normal operations Refer to Section 5.7: Tune DB2 on page 171. Perform this step on each root and non-root subsystem. 6.3.19.2. Modify Accounting, if applicable If the HPSS system consists of multiple subsystems and accounting by subsystems is desired, accounting metadata should be modified to support accounting by subsystem.
Page 219: 8.Create Ssm User Ids
that each caller of the interface is given. Run the hpss_init_server_acls program as follows: % /opt/hpss/bin/convert62/hpss_init_server_acls Error in stat of Keytab File, /var/hpss/etc/mm.keytab, 2 Note: The error is expected and does not indicate that the hpss_init_server_acls program did not complete successfully. In the above example, the error is displayed because the system did not have a mm lib or DB2 username and password setup for this system.
Page 220: 9.Create Location Server Endpoints
hpssgui.pl hpssgui.vbs hpss.jar login.conf The -ssmclientpkg option creates a tar file and places it in the specified directory (e.g. /tmp/ssmclientpkg.tar) which will contain the following files: hpss.jar – Java executables for running the SSM GUI • hpssgui.pl – Perl version of the SSM GUI start up script •...
Page 221: 1.Invoke The Ssm System Manager, Startup Daemon And Prerequisite Software
6.3.20.1. Invoke the SSM System Manager, Startup Daemon and prerequisite software Perform this step on the root subsystem only. Use the rc.hpss script to invoke the Startup Daemon, SSM System Manager and the prerequisite software. % /opt/hpss/bin/rc.hpss $ /etc/rc.hpss If problems are encountered, try starting the software independantly using the rc.hpss script. The default operation is "start".
Page 222: 2.Update Hpss Configurations
The default name of the SSM configuration file is ssm.conf. Its default location is the current directory or, if not there, in $HPSS_PATH_SSM (/var/hpss/ssm by default). The name and location may be overridden by the -m option to the hpssgui.pl script or by setting the value in the user's environment.
Page 223: 3.Dump Accounting Metadata, If Applicable
Mover Startup Daemon SSM System Manager 4. Review and update the Core Server(s) other configuration parameters, if necessary 5. For 4.5 upgrades only: Review all migration policies to ensure that they were converted correctly In pre-5.1 HPSS systems, migration policies could apply to both a disk and tape storage class. In HPSS 5.1, the migration policies were modified to apply only to disk or to tape, but not both.
Page 224: 4.Start Hpss 6.2 Servers
fields will display the current value. Change the accounting bits such that if the initial value is 1 then the new value will be 2 and conversely if the initial value is 2 then the new value will be 1. At this point, the HPSS system has no accounting metadata for existing files.
Page 225: Clean Up After A 4.5 To 6.2 Upgrade
Using the GUI, mark the MPS configuration executable and start it • Verify that Migration and Purge are working correctly • Repack and reclaim tape volumes • 6.3.22. Clean Up After a 4.5 to 6.2 Upgrade After the 6.2 system has been operational for an extended period, clean up the following: If it is still running, shutdown the SFS server •...
Page 226: 2.Revert The Hpss 6.2 System To Version 5.1
in tape mount errors for read operations Once it is determined that it’s safe to revert back to Release 6.2, perform the steps as follows. Note that this procedure assumes that the upgrade stopped after the 6.2 servers are up but before changes were made that may affect the 4.5 user data or invalidate the 4.5 metadata.
Page 227: Metadata Conversion Troubleshooting Procedures
the "PRE62_". Next, beginning with step 4, follow the procedures in Section 6.3.24.1: Revert the HPSS 6.2 System to Version 4.5 on page 225. The site will also have to revert the operating system software and any other upgraded software back to the HPSS 4.5 prerequisite versions so that the HPSS 4.5 code is not running on unsupported software.
Page 228: 2.Db_Config_Convert, Db_Subsys_Convert, And Db_Lr_Convert Errors And Warnings
6.4.1.2. db_config_convert, db_subsys_convert, and db_lr_convert Errors and Warnings 1SQL3304N The table does not exist. => The program is attempting to insert data into a table that has not been created under the database name and schema it is running under. Determine the database name entered for the subsystem during the db_convert_collect_info program (i.e.
Page 229 Resolution: Check that the table exists in the schema and that the db_convert_collect_info utility has been run recently. The empty table scripts pull their information about which schema to use from the text file /var/hpss/convert/6.2/Convert.DB.Names, created by running db_convert_collect_info. Enter the appropriate schema name for the global database (which will be used for all databases) when rerunning db_convert_collect_info.
Page 230 Resolution: Either the wrong filename or the wrong subsystem Id for that filename was entered. Rerun the conversion program with the correct subsystem Id and filename. SQL0968C The file system is full. SQLSTATE=57011 => This error message usually follows 10 or so other SQL messages, and means that the load operation for the long running conversion program failed because, most likely, the system temporary tablespace (which defaults to TEMPSPACE1) has run out of room.
Page 231: Hpss 5.1 To 6.2 Conversion Utility Errors
Error: write_bitfile_to_ASC failed to write to pipe, fd is -1, errno = 9 => This error results when running a long running conversion program that cannot write to /var/hpss/convert/6.2 and create a file called asc_fifo_bitfile (the named pipe for the C program to communicate with the DB2 load). Resolution: Ensure that the user running the conversion has write permissions on /var/hpss/convert/6.2.
Page 232: 2.Hpss_Init_Server_Acls Errors
trying to insert the converted metadata. If this resulted from previously running the metadata conversion, and the metadata should be re-converted, then identify the table name (e.g. “HPSS.SERVERINTERFACES”) and empty the table by executing a % db2 delete from <table name> statement where <table name>...
Page 233 through several syslogd error messages output to the monitor or a failed attempt at restarting the failed conversion program. Should DB2 be placed in an inconsistent state, the tablespace will likely have to be dropped and recreated along with the table being converted. Then the database will need to be recycled (using db2stop and db2start).
Page 234: Examples Of Hpss 4.5 Conversion Utility Output
The output displays “Re-running” which indicates that the utility is performing a restart. performing a restart and there are already rows in the DB2 table, rows committed should still equal rows submitted to the load. The conversion program will determine the number of records already loaded into the table, find the next consecutive SFS record to load, and continue counting until all SFS records are converted properly and inserted into the DB2 table(s).
Page 235 $ db_config_convert /.:/encina/sfs/hpss/globalconfig Logged into DCE as hpss_ssm. Emptying all configuration tables in global database... All config tables emptied in global database, under schema hpss. Running db_convert_global utility... Converting SFS file /.:/encina/sfs/hpss/globalconfig Converted 1 record successfully from /.:/encina/sfs/hpss/globalconfig db_convert_global complete, inserted 1 record into DB2 global table Running db_convert_storsubsys utility...
Page 236 Running db_convert_gatekeeper utility... Converting SFS file /.:/encina/sfs/hpss/gkconfig Converted 1 records successfully from /.:/encina/sfs/hpss/gkconfig db_convert_gatekeeper complete, inserted 1 records into DB2 gatekeeper table Running db_convert_logclient utility... Converting SFS file /.:/encina/sfs/hpss/logclient Converted 1 records successfully from /.:/encina/sfs/hpss/logclient db_convert_logclient complete, inserted 1 records into DB2 logclient table Running db_convert_logdaemon utility...
Page 237 /.:/encina/sfs/hpss/cartridge_stk Converting SFS file /.:/encina/sfs/hpss/cartridge_stk_rait Converted 4 records successfully from /.:/encina/sfs/hpss/cartridge_stk_rait db_convert_cartridge complete, inserted 32 records into DB2 cartridge table Running db_convert_cos utility... Converting SFS file /.:/encina/sfs/hpss/cos Converted 21 records successfully from /.:/encina/sfs/hpss/cos db_convert_cos complete, inserted 21 records into DB2 cos table Running db_convert_dmgfileset utility...
Page 238: 3.Db_Subsys_Convert Output
Running db_convert_purgepol utility... Converting SFS file /.:/encina/sfs/hpss/purgepolicy Converted 1 records successfully from /.:/encina/sfs/hpss/purgepolicy db_convert_purgepol complete, inserted 1 records into DB2 purgepol table Running db_convert_pvldrive utility... Converting SFS file /.:/encina/sfs/hpss/pvldrive Converted 17 records successfully from /.:/encina/sfs/hpss/pvldrive db_convert_pvldrive complete, inserted 17 records into DB2 pvldrive table Running db_convert_pvlpv utility...
Page 239 $ db_subsys_convert /.:/encina/sfs/hpss/globalconfig 1 Logged into DCE as hpss_ssm. Emptying all subsystem tables in subsys1 database... All subsystem tables emptied in subsys1 database, under schema hpss. Running db_convert_acctlog utility... Converting SFS file /.:/encina/sfs/hpss/acctlog.1 Converted 0 records successfully from /.:/encina/sfs/hpss/acctlog.1 db_convert_acctlog complete, inserted 0 records into DB2 acctlog table for subsystem 1 Running db_convert_acctsnap utility...
Page 240 Converted 600 records successfully from /.:/encina/sfs/hpss/bfmigrrec.1 db_convert_bfmigrec complete, inserted 600 records into DB2 bfmigrec table for subsystem 1 Running db_convert_bfpurgerec utility... Converting SFS file /.:/encina/sfs/hpss/bfpurgerec.1 Converted 0 records successfully from /.:/encina/sfs/hpss/bfpurgerec.1 db_convert_bfpurgerec complete, inserted 0 records into DB2 bfpurgerec table for subsystem 1 Running db_convert_bfssegchkpt utility...
Page 241: 4.Long Running Conversion Utilities Output
table for subsystem 1 Running db_convert_storagemapdisk utility... Converting SFS file /.:/encina/sfs/hpss/storagemapdisk.1 Converted 3 records successfully from /.:/encina/sfs/hpss/storagemapdisk.1 db_convert_storagemapdisk complete, inserted 3 records into DB2 storagemapdisk table for subsystem 1 db_convert_storagemapdisk complete, inserted 1 records into DB2 diskspace table for subsystem 1 Running db_convert_storagemaptape utility...
Page 242 Converting SFS file /.:/encina/sfs/hpss/bftapesegment.1 Converted 1159 records successfully from /.:/encina/sfs/hpss/bftapesegment.1 lr_db_convert_bftapeseg complete, submitted 1159 records to DB2 bftapeseg load for subsystem 1, 1596 operations per sec, 0.725914 total time Number of rows read Number of rows skipped Number of rows loaded Number of rows rejected Number of rows deleted Number of rows committed...
Page 243 Converting SFS file /.:/encina/sfs/hpss/nstext.1 Converted 408 records successfully from /.:/encina/sfs/hpss/nstext.1 lr_db_convert_nstext complete, submitted 408 records to DB2 nstext load for subsystem 1, 1233 operations per sec, 1.001456 total time Number of rows read Number of rows skipped Number of rows loaded Number of rows rejected Number of rows deleted Number of rows committed...
Page 244 HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 245: Appendix A. Glossary Of Terms And Acronyms
HPSS Accounting process. This message type is not currently used. Advanced Interactive Executive. An operating system provided on many IBM machines. A log record message type used to log high-level error conditions. Automated Media Library. A tape robot.
Page 246 Core Server. A UNIX program that runs continuously in the background. A relational database system, a product of IBM Corporation, used by HPSS to store and manage HPSS system metadata. A log record message type used to log lower-level error conditions.
Page 247 device directory dismount drive ESCON event export FDDI file file family fileset fileset ID fileset name file system ID Gatekeeper HPSS Installation Guide Release 6.2 (Revision 2.0) A physical piece of hardware, usually associated with a drive, that is capable of reading or writing data.
Page 248 Gatekeeping Service Gatekeeping Site Interface Gatekeeping Site Policy GECOS HACMP halt hierarchy HIMF HiPPI HPSS HPSS-only fileset IEEE IETF Imex import HPSS Installation Guide Release 6.2 (Revision 2.0) A registered interface in the Gatekeeper that provides a site the mechanism to create local policy on how to throttle or deny create, open and stage requests and which of these request types to monitor.
Page 249 IOD/IOR IRIX junction LANL LARC latency LDAP LLNL LMCP local log Location Server Log Client Log Daemon log record log record type logging service HPSS Installation Guide Release 6.2 (Revision 2.0) Input/Output Input/Output Descriptor / Input/Output Reply. Structures used to send control information about data movement requests in HPSS and about the success or failure of the requests.
Page 250 NERSC HPSS Installation Guide Release 6.2 (Revision 2.0) Location Server Linear Tape-Open. A half-inch open tape technology developed by IBM, HP and Seagate. Mandatory Access Control A programming data structure that represents an HPSS system resource. The resource can be monitored and controlled by operations on the managed object.
Page 251 notification object ORNL OS/2 PFTP physical volume Physical Volume Library Physical Volume Repository PIOFS POSIX purge purge lock RAID RAIT HPSS Installation Guide Release 6.2 (Revision 2.0) A notice from one server to another about a noteworthy occurrence. HPSS notifications include notices sent from other servers to SSM of changes in managed object attributes, changes in tape mount information, and log messages that are alarm, event, and status log record message types.
Page 252 reclaim registration reinitialization repack request RISC SCSI security shelf tape shutdown sink SMIT SOID source HPSS Installation Guide Release 6.2 (Revision 2.0) Random Access Memory The act of making empty tape virtual volumes available for reuse. Reclaimed tape virtual volumes are assigned a new Virtual Volume ID, but retain the rest of their previous characteristics.
Page 253 SSM session stage start-up status storage class storage hierarchy storage level storage map storage segment Storage Service storage subsystem Storage System Management stripe length HPSS Installation Guide Release 6.2 (Revision 2.0) HPSS Storage Service Serial Storage Architecture Storage System Management The environment in which an SSM user interacts with the SSM System Manager to monitor and control HPSS.
Page 254 stripe length stripe width System Manager TCP/IP trace transaction UUID virtual volume virtual volume block size XDSM HPSS Installation Guide Release 6.2 (Revision 2.0) The number of bytes that must be written to span all the physical storage media (physical volumes) that are grouped together to form the logical storage media (virtual volume).
Page 255 HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 256: Appendix B. References
22. IBM Ultrium Device Drivers Programming Reference WB1304-01 Interfacing Guide DAS, Order no. DOC F00 011 24. Installing, Managing, and Using the IBM AIX Parallel I/O File System, SH34-6065-02 25. Parallel and ESCON Channel Tape Attachment/6000 Installation and User's Guide, GA32-0311-02 26.
Page 257 Storage System (HPSS),” from the 1995 IEEE MSS Symposium, courtesy of the IEEE Computer Society Press. 33. T.W. Tyler and D.S. Fisher, “Using Distributed OLTP Technology in a High-Performance Storage System,” from the 1995 IEEE MSS Symposium, courtesy of the IEEE Computer Society Press.
Page 258: Appendix C. Developer Acknowledgments
HPSS development was performed jointly by IBM Worldwide Government Industry, Lawrence Berkeley National Laboratory, Lawrence Livermore National Laboratory, Los Alamos National Laboratory, NASA Langley Research Center, Oak Ridge National Laboratory, and Sandia National Laboratories.
Page 259: Appendix D. Hpss.conf Configuration File
Appendix D. The HPSS.conf configuration file contains tuning options to be used by HPSS clients and servers. For additional information, please see the HPSS.conf manual page. General HPSS.conf Rules/Suggestions: Keywords MUST be specified precisely as shown (no extra spaces) • Lines are comprised of comments, blank lines, simple specifiers, specifiers and values - “abc = •...
Page 260 Stanza (CMPD) PFTP Client = { E.g. PFTP Client = { Optional Reserved Stanza specifier. Must be terminated with a matching “}” SubStanza SYSLOG Facility = <value> Values: DAEMON, LOCAL0 ... LOCAL7 E.g. SYSLOG Facility = LOCAL2 Optional SubStanza specifying the Syslog Facility for the MultiNode Daemon SubStanza Debug Value = <value>...
Page 261 SubStanza Auto Parallel Size = <value> Value: Size - May be specified as a decimal number or “xMB” style notation. E.g. Auto Parallel Size = 4MB Optional SubStanza specifying the minimum file size to start using the “auto-parallel” features of the PFTP Client. SubStanza PortRange = <value>...
Page 262 SubStanza No SAN3P E.g. No SAN3P Optional SubStanza specifying not to use SAN3P even if it is available. Default is to use SAN3P if available. SubStanza No Transfer Agent Support E.g. No Transfer Agent Support Optional Substanza specifying to NOT use the Transfer Agent. Default is to use the Transfer Agent.
Page 263 The pftp_client automatically performs conversion of get and put commands to their parallel equivalents, pget and pput. Some sites have reported degraded performance as a result of this substitution occurring with small file transfers. To accommodate this problem, the Auto Parallel Size = value substanza may be specified in the HPSS.conf file where the “automatic”...
Page 264: Pftp Client Interfaces Stanza
; Transfer Buffer Size = 1MB ; Socket Buffer Size = 16MB # PFTP sets an Artificial (Compiled in) Maximum of 250GB MAX Ptran Size = 10GB # Disable SAN3P ; No SAN3P # Disable Transfer Agent ; No Transfer Agent Supported # Disable 64-bit Protocol - Default is on ;...
Page 265 SubSection The PFTP Client Interfaces = { … } stanza contains several configuration options for the pftp_client executables. SubStanzas refer to the hostname(s) associated with the local system where the pftp_client is being invoked. Sections refer to the Parallel FTP Daemon hostname(s) where the PFTP Daemon is being invoked. SubSections refer to the Network Interface to be utilized (by the host where the PFTP client is invoked) to transfer data to the HPSS Mover systems.
Page 266: Multinode Table Stanza
PFTP Client Interfaces Stanza Example: ; PFTP Client Interfaces = { # PFTP Client Host Name(s) ; water.clearlake.ibm.com water = { # Next Specification is the PFTP Daemon Host # water has 3 specific interfaces that can talk # to the HPSS Movers associated with the PFTP # Daemon Host "water", as well as various...
Page 267 Configuration Type Stanza (CMPD) SubStanza SubStanza (CMPD) Section (CMPD) Sub-Section The Multinode Table = { … } stanza contains one or more substanzas specifying the names of the host initiating the PFTP session. Each section contains one or more names/IP addresses of remote hosts executing a Multinode Daemon (multinoded).
Page 268: Network Option Stanza
# Hostname of the Client water water.clearlake.ibm.com = # Name of the system running the PFTP Server pftp_server pftp_server.clearlake.ibm.com = { # Specification of the Multinode Host # If the Data Node is a different interface than the interface # specified by the Control Node; then enter the Data Node # Interface after the "="...
Page 269: Table 15. Network Options Stanza Fields
Destination IP address “masked” by the NetMask value. The calling application (PFTP Client, Client API, or Mover) will apply the value of the NetMask specification in the configuration file entry to the specified destination address. A “Default” destination may be specified for all sources/destinations not explicitly specified in the HPSS.conf file.
Page 270 Section (CMPD) <Destination IP Address> = { E.g. 100.101.102.0 = { Optional SubStanza specifying a dotted decimal address of the destination interface. Only one address is allowed; however, networks and sub-networks may be chosen by appropriate specification of the NetMask. May contain: “Default = {“...
Page 271 SubSection TcpNoDelay = <value> Values: 0, 1 E.g. TcpNoDelay = 1 Optional parameter Indicates whether the TCP Delay option should be disabled (0) or enabled (any other value) SendSpace & RecvSpace Controls the size of the receive and send buffers for TCP/IP sockets. Internally, HPSS servers and clients attempt to set these buffers sizes explicitly, but other utilities may not.
Page 272 Multiple Sections may be included in any SubStanza. A “Default” Destination Interface • Name Section may be specified. NOTE: Do not include the quotes when specifying Default. The NetMask must be specified in Decimal Dot IP Address Notation • All SubSections must be specified in every Section. •...
Page 273: Pftp Daemon Stanza
Default = { NetMask = 255.255.255.0 RFC1323 = 1 SendSpace = 256KB RecvSpace = WriteSize = 512KB TCPNoDelay = 0 D.5. PFTP Daemon Stanza A large number of options are available for configuring the PFTP daemon and tuning its performance. These options were previously specified in the ftpaccess file or via command line switches.
Page 274 SubStanza SYSLOG Facility = <value> Value: DAEMON, LOCAL0 ... LOCAL7 E.g. SYSLOG Facility = LOCAL0 Replaces -s<string> option. Optional SubStanza specifying the syslog facility for the HPSS PFTPD. The default syslog facility is LOG_DAEMON (reference:/usr/include/sys/syslog.h). Alternatives are LOCAL0 - LOCAL7. Incorrect specification will default back to LOG_DAEMON. To make use of the alternates, modify /etc/syslog.conf to use the alternate facility.
Page 275 SubStanza FTP Access File = <value> Value: filename E.g. FTP Access File = myftpaccess Replaces -F<string> option. Optional SubStanza setting the {FTP_FtpAccessFile}. Default: ftpaccess. Located in the directory {FTPBaseDir}/etc. SubStanza Disable Slash Home Directory E.g. Disable Slash Home Directory Replaces -Z option. Optional SubStanza disabling use of / as the user’s home directory.
Page 276 SubStanza FTP Principal Keytab File = <value> Value: Pathname/Filename E.g. FTP Principal Keytab File = /var/hpss/etc/hpss.keytabs Optional SubStanza specifying the keytab containing the FTP principal. SubStanza Allow Passive Connections E.g. Allow Passive Connections Replaces -A option. Optional SubStanza enabling passive connections. Note: Not supported in the HPSS parallel FTP daemon for parallel operations.
Page 277 SubStanza PFTP IO Buffer Size = <value> E.g. PFTP IO Buffer Size = 4MB Replaces -b<string> option. Optional SubStanza setting the preferred IO Buffer Size for the PFTP Server SubStanza Debug Value = <value> E.g. Debug Value = 3 Replaces -d option(s). Optional SubStanza specifying the level of debugging desired (1-3).
Page 278 Kerberized PFTP Servers. Default: /etc/v5srvtab. (HPSS only.) SubStanza HPSS Realm Name = <value> E.g. HPSS Realm Name = FIRE.CLEARLAKE.IBM.COM Optional SubStanza setting the Realm name for the PFTP Daemon. SubStanza Use Port Range E.g.
Page 279 SubStanza Maximum Time Out = <value> Value: Time in seconds E.g. Maximum Time Out = 86400 Replaces -T option and hpss_option MTO time in ftpaccess. Optional SubStanza specifying the maximum timeout in seconds. SubStanza Use UDP ONLY E.g. UDP ONLY Replaces -U option.
Page 280 SubStanza PortRange = <value> E.g. PortRange = ncadg_ip_udp[10100-12100]:ncacn_ip_tcp[10100-12100] Optional SubStanza specifying the port range to be used for the non-HPSS parallel FTP daemon which is necessary for parallel transfers. NOTE: This is ignored for passive listings, etc. SubStanza Socket Buffer Size = <value> Vlaues: Viable Socket Sizes E.g.
Page 281 SubSection COS = <value> E.g. COS = 2 Optional SubSection specifying the Class of Service to be used based on file size. 0 means allow the Core Server to determine the optimal COS. (Has no meaning for the Non-HPSS PFTD daemon.) SubStanza <nodename>...
Page 282 SubStanza PFTP Group File = <value> Value: E.g. PFTP Group File = /var/hpss/etc/pftp_groups Optional Substanza used to specify the file containing the group information for PFTP clients. Default is /var/hpss/etc/group. SubStanza Primary Authentication Mechanism = <value> Values: KRB5, IBM_HPSS_PKEY, GSI, UNIX E.g.
Page 283 UserName/Password Mechanism will NOT use a standard Password. SubStanza {Hostname} Service Name = {servicename} E.g. mymachine Service Name = fire.clearlake.ibm.com Optional Substanza used to specify alternate service names for the Kerberos service principals. The value after the equal sign is appended to either “host”...
Page 284 sizes in the range [1MB, 2MB). PFTP Daemon Stanza Example: PFTP Daemon = { # Allow the Daemon to take Core Dumps ; Allow Core Files # Directory to put core files in (Default = .) ; Core File Directory = /var/hpss/adm/core Specify the SYSLOG facility to use for all syslog messages except Authentication Messages.
Page 285 ; Default Time Out = 1500 Specify (in octal) the Default umask ; Default Umask = 077 Specification of the Level of HPSS Client API logging to use ( 0 - 3 ; Client API Verbose Value = 0 Do NOT allow the user to specify Classes of Service (HPSS Only) ;...
Page 286 ; 100MB = { ; BlockSize = 4MB ; StripeWidth= 0 ; COS = 0 ; 1GB = { ; BlockSize = 8MB ; StripeWidth= 0 ; COS = 0 # Use the System Password file routines (TRUE or FALSE) # The Default for PFTP is FALSE (Case Sensitive!) Use System Password Files = FALSE Path and Name for the PFTP Password File...
Page 287: Transfer Agent Stanza
; GSI = { ; Mapfile Specifier = LDAP:/var/hpss/etc/KRB2UnixMapfile ; Use Site Auth Method = CryptoCard ; Default Authorization Mechanism = LDAP ; IDENT = { ; Mapfile Specifier = FILE:/var/hpss/etc/IDENT2UnixMapfile ; Use Site Auth Method = SecurId ; Default Authorization Mechanism = DBAS USER_PASS = { ;...
Page 288 SubStanza Nodeset File = <value> Value: Pathname/filename E.g. Nodeset File = /var/hpss/etc/PMTA_NodeSets Optional Substanzaused to specify the location of the Transfer Agent file containing Nodesets. SubStanza Node Affinity File = <value> Value: Pathname/filename E.g. Node Affinity File = /var/hpss/etc/PMTA_NodeAffinity Optional Substanzaused to specify the location of the Transfer Agent file containing Node Affinities.
Page 289 SubStanza Debug Logfile = <value> Value: Pathname/filename E.g. Debug Logfile = /var/hpss/log/PMTA_Debugfile Optional Substanzaused to specify the location of the Transfer Agent Debugging File. Substanza SYSLOG Facility = <value> Values: DAEMON, LOCAL0 ... LOCAL7, NONE E.g. SYSLOG Facility = LOCAL0 Optional SubStanza specifying the syslog facility for the HPSS PFTPD.
Page 290 # Parallel Multinode Transfer Agent (PMTA) Section Transfer Agent = { # The (optional) NodeSet File contains named sets of # Nodes that can be referred to via the "SET:setname" # notation. Nodeset File = /var/hpss/etc/ta/nodeset.conf # The (optional) Node Affinity file is used to specify groups of nodes are able to communicate in a network whose topology does not support full interconnection Node Affinity File = /var/hpss/etc/ta/node_affinity.conf...
Page 291: Stanzas Reserved For Future Use
D.7. Stanzas Reserved for Future Use The following stanza names (specifiers) are reserved for future implementation in HPSS and should not be used by application developers. Transfer Agent (Partially Implemented) • Pipe File • Local File Path • • HPSS Installation Guide Release 6.2 (Revision 2.0) July 2008...
Page 292: Hpss Installation Guide July
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)
Page 293: Appendix E. Hpss_Env_Defs.h
The HPSS environment variables are defined in /opt/hpss/include/hpss_env_defs.h. These environment variables can be overridden in /var/hpss/etc/env.conf or in the local environment. static env_t hpss_env_defs[] = { ************************************************************************** HPSS_ROOT HPSS_HOST HPSS_NODE_TYPE HPSS_PATH_INSTALL HPSS_PATH_BIN HPSS_PATH_MSG HPSS_PATH_SLASH_BIN HPSS_PATH_SLASH_ETC HPSS_PATH_USR_BIN HPSS_PATH_USR_SBIN HPSS_PATH_VAR HPSS_USER HPSS_USERROOT HPSS_PATH_DB_INSTALL ************************************************************************** { "HPSS_ROOT",...
Page 294 { "HPSS_GRP_NAME_CLIENT", NULL}, ************************************************************************** * HPSS Server Principal names HPSS_PRINCIPAL HPSS_PRINCIPAL_CORE HPSS_PRINCIPAL_DMG HPSS_PRINCIPAL_FTPD HPSS_PRINCIPAL_GK HPSS_PRINCIPAL_HDM HPSS_PRINCIPAL_HPSSD HPSS_PRINCIPAL_LOG Daemon HPSS_PRINCIPAL_LS HPSS_PRINCIPAL_MOUNTD HPSS_PRINCIPAL_MPS Server HPSS_PRINCIPAL_MVR HPSS_PRINCIPAL_NFSD HPSS_PRINCIPAL_PVL HPSS_PRINCIPAL_PVR HPSS_PRINCIPAL_SSM HPSS_PRINCIPAL_ADM_USER ************************************************************************** { "HPSS_PRINCIPAL", { "HPSS_PRINCIPAL_CORE", { "HPSS_PRINCIPAL_DMG", { "HPSS_PRINCIPAL_FTPD", { "HPSS_PRINCIPAL_GK", { "HPSS_PRINCIPAL_HDM", { "HPSS_PRINCIPAL_HPSSD", { "HPSS_PRINCIPAL_LOG", { "HPSS_PRINCIPAL_LS",...
Page 295 HPSS_PRINCIPAL_MPS_UID Server HPSS_PRINCIPAL_MVR_UID HPSS_PRINCIPAL_NFSD_UID HPSS_PRINCIPAL_NS_UID HPSS_PRINCIPAL_PFSD_UID HPSS_PRINCIPAL_PVL_UID HPSS_PRINCIPAL_PVR_UID HPSS_PRINCIPAL_SS_UID HPSS_PRINCIPAL_SSM_UID * NOTE: Principal UID must be in the format of "-uid <number of uid>" For example: { "HPSS_PRINCIPAL_BFS_UID" ************************************************************************** { "HPSS_PRINCIPAL_CORE_UID", { "HPSS_PRINCIPAL_DMG_UID", { "HPSS_PRINCIPAL_FTPD_UID", { "HPSS_PRINCIPAL_GK_UID", { "HPSS_PRINCIPAL_HDM_UID", { "HPSS_PRINCIPAL_HPSSD_UID", { "HPSS_PRINCIPAL_LOG_UID", { "HPSS_PRINCIPAL_LS_UID", { "HPSS_PRINCIPAL_MOUNTD_UID",...
Page 296 HPSS_EXEC_PVR_SCSI HPSS_EXEC_SSMSM ************************************************************************** { "HPSS_EXEC_ACCT", NULL}, { "HPSS_EXEC_CORE", NULL}, { "HPSS_EXEC_DMG", NULL}, { "HPSS_EXEC_FTPD", NULL}, { "HPSS_EXEC_GK", NULL}, { "HPSS_EXEC_HPSSD", NULL}, { "HPSS_EXEC_LOGC", NULL}, { "HPSS_EXEC_LOGD", NULL}, { "HPSS_EXEC_LS", NULL}, { "HPSS_EXEC_MOUNTD", NULL}, { "HPSS_EXEC_MPS", NULL}, { "HPSS_EXEC_MVR", NULL}, { "HPSS_EXEC_MVR_TCP", NULL}, { "HPSS_EXEC_NFSD", NULL},...
Page 297 HPSS_EXEC_DELOG HPSS_EXEC_RECLAIM HPSS_EXEC_REPACK ************************************************************************** { "HPSS_EXEC_ACL_EDIT", NULL}, { "HPSS_EXEC_CDSCP", NULL}, { "HPSS_EXEC_DELOG", NULL}, { "HPSS_EXEC_RECLAIM", NULL}, { "HPSS_EXEC_REPACK", NULL}, ************************************************************************** * Logging Unix files HPSS_PATH_LOG HPSS_UNIX_LOCAL_LOG ************************************************************************** { "HPSS_PATH_LOG", { "HPSS_UNIX_LOCAL_LOG", NULL}, ************************************************************************** * Accounting Unix files HPSS_PATH_ACCT files HPSS_UNIX_ACCT_CHECKPOINT HPSS_UNIX_ACCT_REPORT HPSS_UNIX_ACCT_COMMENTARY **************************************************************************...
Page 298 HPSS_UNIX_NFS_CHECKPOINT HPSS_NFS_DISABLE_JUNCTIONS HPSS_MNT_DISABLE_JUNCTIONS ************************************************************************** { "HPSS_PATH_NFS", { "HPSS_UNIX_NFS_EXPORTS", NULL}, { "HPSS_UNIX_NFS_CREDMAP", NULL}, { "HPSS_UNIX_NFS_CACHEFILE", NULL}, { "HPSS_UNIX_NFS_CHECKPOINT", NULL}, { "HPSS_NFS_DISABLE_JUNCTIONS", "TRUE", { "HPSS_MNT_DISABLE_JUNCTIONS", "TRUE", ************************************************************************** * MPS Unix files HPSS_PATH_MPS HPSS_UNIX_MPS_REPORT ************************************************************************** { "HPSS_PATH_MPS", { "HPSS_UNIX_MPS_REPORT", ************************************************************************** * Gatekeeper Unix files HPSS_PATH_GK files HPSS_UNIX_GK_SITE_POLICY...
Page 299 { "HPSS_SUBSYS_DB_NAME", { "HPSS_MM_SCHEMA_NAME", { "HPSS_MM_LOW_WATER_MARK", { "HPSS_MM_HIGH_WATER_MARK", { "HPSS_MM_CACHE", { "HPSS_SERVER_DB_GROUP", { "HPSS_SERVER_DB_KEYTAB", NULL}, ************************************************************************** * Descriptive Names We use HPSS_HOST_TMP instead of HPSS_HOST because HPSS_HOST is being set in hpss_env using 'hostname', and so it always gets the long name.
Page 300 { "HPSS_HOST_TMP", { "HPSS_DESC_CORE", { "HPSS_DESC_DMG", { "HPSS_DESC_FTPD", { "HPSS_DESC_GK", { "HPSS_DESC_HPSSD", {HPSS_HOST_TMP})", { "HPSS_DESC_HPSSD_SHORT", { "HPSS_DESC_LOGC", NULL}, { "HPSS_DESC_LOGC_SHORT", { "HPSS_DESC_LOGD", { "HPSS_DESC_LS", { "HPSS_DESC_MM", { "HPSS_DESC_MOUNTD", { "HPSS_DESC_MPS", NULL}, { "HPSS_DESC_MVR", NULL}, { "HPSS_DESC_MVR_SHORT", { "HPSS_DESC_NFSD", { "HPSS_DESC_PVL", { "HPSS_DESC_PVR_AMPEX", { "HPSS_DESC_PVR_OPER", { "HPSS_DESC_PVR_STK",...
Page 301 updates HPSSSSM_UI_MO_RATE tries HPSSSSM_UI_LIST_RATE update tries HPSSSSM_UI_ALARM_RATE update tries HPSSGUI_SEC_MECH communication HPSSADM_SEC_MECH communication HPSSGUI_USER_CFG_PATH HPSSADM_USER_CFG_PATH HPSS_SSMUSER_JAVA_POLICY- Java policy file for SSM GUI and hpssadm JAVA_ROOT JAVA_BIN interpreter JAVA_CLS1 HPSS_SSM_CLASSPATH The JAVA_HOME variable is used by several HPSS scripts to set the command execution PATH and other variables.
Page 302 ************************************************************************** { "HPSS_PATH_SSM", { "HPSS_SSM_ALARMS", { "HPSS_SSM_ALARMS_DISPLAY", { "HPSS_SSM_ALARMS_GET", { "HPSS_SSM_COUNTRY", { "HPSS_SSM_LANGUAGE", { "HPSS_SSM_SERVER_LISTEN_PORT","0", { "HPSS_HELP_FILES_PATH", { "HPSS_HELP_URL_TYPE", { "HPSSGUI_SM_HOST_NAME", { "HPSSADM_SM_HOST_NAME", { "HPSSGUI_SM_PORT_NUM", { "HPSSADM_SM_PORT_NUM", { "HPSSGUI_RPC_PROT_LEVEL", NULL}, { "HPSSADM_RPC_PROT_LEVEL", NULL}, { "HPSSSSM_UI_WAIT_TIME", { "HPSSSSM_UI_MO_RATE", { "HPSSSSM_UI_LIST_RATE", { "HPSSSSM_UI_ALARM_RATE", { "HPSSGUI_SEC_MECH", { "HPSSADM_SEC_MECH", { "HPSSGUI_USER_CFG_PATH",...
Page 303 HPSS_API_MAX_CONN that within HPSS_API_DEBUG HPSS_API_RETRIES "retryable" HPSS_API_BUSY_DELAY HPSS_API_BUSY_RETRIES HPSS_API_TOTAL_DELAY HPSS_API_LIMITED_RETRIES HPSS_API_DMAP_WRITE_UPDATES - Used to control the frequency of the HPSS_API_REUSE_CONNECTIONS HPSS_API_USE_PORT_RANGE client HPSS_API_RETRY_STAGE_INP files HPSS_API_DISABLE_CROSS_REALM- Used to control cross-realm traversal HPSS_API_DISABLE_JUNCTIONS HPSS_API_SITE_NAME HPSS_API_AUTHN_MECH HPSS_API_RPC_PROT_LEVEL ************************************************************************** { "AIXTHREAD_COND_DEBUG", { "HPSS_API_HOSTNAME", { "HPSS_API_DESC_NAME", { "HPSS_API_DEBUG_PATH", { "HPSS_API_MAX_CONN", { "HPSS_API_DEBUG",...
Page 304 { "HPSS_API_TOTAL_DELAY", { "HPSS_API_LIMITED_RETRIES", { "HPSS_API_DMAP_WRITE_UPDATES","20", { "HPSS_API_REUSE_CONNECTIONS", "0", { "HPSS_API_USE_PORT_RANGE", { "HPSS_API_RETRY_STAGE_INP", { "HPSS_API_DISABLE_CROSS_REALM","0", { "HPSS_API_DISABLE_JUNCTIONS", "0", { "HPSS_API_SITE_NAME", { "HPSS_API_AUTHN_MECH", NULL}, { "HPSS_API_RPC_PROT_LEVEL", NULL}, { "HPSS_API_SAN3P", ************************************************************************** * HDM Specific HPSS_HDM_CAT_NAME - HPSS_HDM_SHMEM_KEY - The HDM's shared memory key (default 3789) HPSS_HDM_SERVER_ID - The HDM's Server ID (default 1) ************************************************************************** { "HPSS_HDM_CAT_NAME",...
Page 305 HPSS_CONFIG_CAT_NAME - HPSS config message catalog full pathname HPSS_INFRA_LOG_TYPES - Default types of infrastructure messages HPSS_INFRA_LOG_CONF file HPSS_MASTER_CAT_NAME - HPSS master message catalog full pathname ************************************************************************** { "HPSSLOG_SHMKEY", { "HPSSLOG_SHMID", { "HPSSLOG_HOSTNAME", { "HPSSLOGGER", { "HPSSLOG", { "HPSS_CONFIG_CAT_NAME", NULL}, { "HPSS_INFRA_LOG_TYPES", { "HPSS_INFRA_LOG_CONF", NULL}, { "HPSS_MASTER_CAT_NAME",...
Page 306 HPSS_AUTHZ_TYPES HPSS_SITE_LOCATION KRB5_INSTALL_PATH KRB5_KDC_DIR config KRB5_KDC_HOST mkhpss) HPSS_LDAP_URL If set and non-empty, specifies the URL of the LDAP server that the hpss ldap admin tool should connect to by default. HPSS_LDAP_SSL_KEYDB If set and non-empty, specifies the path to the SSL key db to use for SSL and indicates that SSL should be used to communicate with LDAP servers.
Page 307 NULL}, { "HPSS_PRIMARY_AUTHENTICATOR", "${HPSS_KRB5_KEYTAB_FILE}", NULL}, { "HPSS_CLIENT_AUTHN_MECH", NULL}, { "IEEE_802_FILE", NULL}, { "HPSS_AUTH_SERVICE_CONF", NULL}, { "HPSS_AUTHZ_SERVICE_CONF", NULL}, { "HPSS_SEC_EP_CONF", NULL}, { "HPSS_SEC_SITE_CONF", NULL}, { "KRB5_CONF", NULL}, { "HPSS_AUTHN_TYPES", { "HPSS_AUTHZ_TYPES", { "HPSS_SITE_LOCATION", { "KRB5_INSTALL_PATH", { "KRB5_KDC_DIR", NULL}, { "KRB5_KDC_HOST", { "HPSS_LDAP_URL", { "HPSS_LDAP_SSL_KEYDB", { "HPSS_LDAP_BIND_TYPE", { "HPSS_LDAP_BIND_ARG",...
Page 308 HPSS_PATH_CORE placed HPSS_PATH_TMP HPSS_PATH_ETC placed HPSS_ENV_CONF file HPSS_PTHREAD_STACK ************************************************************************** { "HPSS_PATH_ADM", { "HPSS_PATH_CORE", { "HPSS_PATH_TMP", { "HPSS_PATH_ETC", { "HPSS_PATH_CRED", { "HPSS_ENV_CONF", NULL}, { "HPSS_PTHREAD_STACK", { NULL, HPSS Installation Guide Release 6.2 (Revision 2.0) - Path where subsystem core files are - Path where temporary files are placed - Path where runtime config files are - The path to the environment override...
Page 309: Appendix F. /Var/Hpss Files
The /var/hpss directory tree is the default location of a number of HPSS configuration files, log files, and other files needed by the servers. The directories and configuration files can be created with the mkhpss utility or hand created. Be very careful when using mkhpss utility as selecting the wrong option can damage the already partially configured HPSS 6.2 system.
Page 310 authorization mechanism and authorization URL to utilize. rc.db2. Created by mkhpss. Script for starting DB2. • rc.krb. Created by mkhpss. Script for starting the Kerberos servers. • passwd. Created by mkhpss. A local HPSS-only password file for use with Unix •...
Page 311: Hpss Installation Guide July 2008 Release 6.2 (Revision 2.0)
of the HPSS servers it brought up in the node. HPSS may also write diagnostic log files and disk allocation maps in this directory, when configured to do so. The lock files are very small, but the log files and maps can be very large. HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0)

This manual is also suitable for:

Hpss 6.2

IBM High Performance Storage System HPSS Installation Manual

Chapter 1. Release 6.2

Chapter 2. HPSS Basics

Chapter 3. HPSS Planning

Chapter 4. System Preparation

Chapter 5. HPSS Installation and Infrastructure Configuration

Quick Links

Installation Guide

Related Manuals for IBM High Performance Storage System HPSS

Summary of Contents for IBM High Performance Storage System HPSS