Portions of this work were produced by Lawrence Livermore National Security, LLC, Lawrence Livermore National
Laboratory (LLNL) under Contract No. DE-AC52-07NA27344 with the U.S. Department of Energy (DOE); by the
University of California, Lawrence Berkeley National Laboratory (LBNL) under Contract No. DE-AC0205CH11231 with DOE; by Los Alamos National Security, LLC, Los Alamos National Laboratory (LANL) under
Contract No. DE-AC52-06NA25396 with DOE; by Sandia Corporation, Sandia National Laboratories (SNL) under
Contract No. DE-AC04-94AL85000 with DOE; and by UT-Battelle, Oak Ridge National Laboratory (ORNL) under
Contract No. DE-AC05-00OR22725 with DOE. The U.S. Government has certain reserved rights under its prime
contracts with the Laboratories.
DISCLAIMER
Portions of this software were sponsored by an agency of the United States Government. Neither the United States,
DOE, The Regents of the University of California, Los Alamos National Security, LLC, Lawrence Livermore
National Security, LLC, Sandia Corporation, UT-Battelle, nor any of their employees, makes any warranty, express
or implied, or assumes any liability or responsibility for the accuracy, completeness, or usefulness of any
information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned
rights.
Printed in the United States of America.
HPSS Release 7.3
November 2009 (Revision 1.0)
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, RISC/6000, pSeries, and xSeries are trademarks or registered trademarks
of International Business Machines Corporation.
UNIX is a registered trademark of the Open Group.
Linux is a registered trademark of Linus Torvalds in the United States and other countries.
Kerberos is a trademark of the Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Incorporated in the United States and other countries.
ACSLS is a trademark of Sun Microsystems, Incorporated.
Microsoft Windows is a registered trademark of Microsoft Corporation.
NFS, Network File System, and ACSLS are trademarks of Sun Microsystems, Inc.
DST is a trademark of Ampex Systems Corporation.
Other brands and product names appearing herein may be trademarks or registered trademarks of third parties.
2.4.3. Deleting a Location Policy......................................................................................................................28
2.5. Restricting user access to HPSS. ..................................................................................................28
Chapter 3. Using SSM............................................................................................................................31
3.1. The SSM System Manager............................................................................................................31
3.1.1. Starting the SSM System Manager..........................................................................................................31
3.1.2. Tuning the System Manager RPC Thread Pool and Request Queue Sizes.............................................31
3.1.3. Labeling the System Manager RPC Program Number ...........................................................................32
3.2. Quick Startup of hpssgui...............................................................................................................33
3.3. Configuration and Startup of hpssgui and hpssadm.......................................................................34
3.3.1. Configuring the System Manager Authentication for SSM Clients.........................................................35
3.3.2. Creating the SSM User Accounts............................................................................................................35
3.3.2.1. The hpssuser Utility........................................................................................................................35
3.3.2.2. SSM User Authorization.................................................................................................................36
3.3.2.3. User Keytabs (For Use with hpssadm Only)...................................................................................37
3.3.2.3.1. Keytabs for Kerberos Authentication: hpss_krb5_keytab......................................................38
3.3.2.3.2. Keytabs for UNIX Authentication: hpss_unix_keytab...........................................................38
3.3.3.2. krb5.conf (For Use with Kerberos Authentication Only)................................................................41
3.3.4. SSM Help Files (Optional)......................................................................................................................42
3.9.2. About HPSS.............................................................................................................................................58
3.9.3. HPSS Health and Status...........................................................................................................................58
3.9.3.1. SM Server Connection Status Indicator .........................................................................................59
3.9.3.4. Menu Tree.......................................................................................................................................62
4.2.1. Subsystems List Window.........................................................................................................................74
4.2.2. Creating a New Storage Subsystem.........................................................................................................76
4.2.4. Modifying a Storage Subsystem..............................................................................................................81
4.2.5. Deleting a Storage Subsystem..................................................................................................................81
5.1. Server List.....................................................................................................................................83
5.1. Server Configuration.....................................................................................................................87
5.1.1. Common Server Configuration................................................................................................................89
5.1.1. Deleting a Server Configuration............................................................................................................123
5.1. Monitoring Server Information....................................................................................................125
5.1.1. Basic Server Information.......................................................................................................................125
5.1.1. Specific Server Information...................................................................................................................127
5.1.1.1. Core Server Information Window.................................................................................................127
5.1.1.1. Gatekeeper Information Window.................................................................................................130
5.1.1.1. Location Server Information Window..........................................................................................132
5.1.1. Shutting Down an HPSS Server............................................................................................................151
5.1.2. Shutting Down All HPSS Servers..........................................................................................................152
5.1.3. Halting an HPSS Server.........................................................................................................................152
5.1.4. Shutting Down the SSM Server.............................................................................................................152
5.1.5. Shutting Down the Startup Daemon......................................................................................................153
5.1.6. Stopping the Prerequisite Software........................................................................................................153
5.2. Server Repair and Reinitialization...............................................................................................153
5.2.1. Repairing an HPSS Server.....................................................................................................................153
5.2.2. Reinitializing a Server...........................................................................................................................154
5.1. Forcing an SSM Connection........................................................................................................156
6.5.3. Changing a Purge Policy........................................................................................................................192
6.5.4. Deleting a Purge Policy.........................................................................................................................193
6.6.1. File Family Configuration......................................................................................................................194
6.6.2. Changing a File Family..........................................................................................................................194
6.6.3. Deleting a File Family...........................................................................................................................194
Chapter 7. Device and Drive Management ........................................................................................196
7.1. Configure a New Device & Drive................................................................................................196
7.1.1. Devices and Drives Window.................................................................................................................202
7.1.2. Enable Variable Block Sizes for Tape Devices.....................................................................................207
7.1.3. Changing a Drive's Configuration..........................................................................................................207
7.1.4. Deleting a Drive's Configuration...........................................................................................................208
7.2. Monitoring Devices and Drives...................................................................................................209
7.2.1. Mover Device Information Window......................................................................................................209
7.2.2. PVL Drive Information Window...........................................................................................................214
7.3.3. Drive Pool Considerations.....................................................................................................................219
7.4. Changing Device and Drive State................................................................................................220
7.4.1. Unlocking a Drive..................................................................................................................................220
7.4.2. Locking a Drive.....................................................................................................................................220
7.4.3. Repairing the State of a Device or Drive...............................................................................................221
9.2.1. Creating a Log Policy............................................................................................................................295
9.2.3. Changing a Log Policy...........................................................................................................................298
9.2.4. Deleting a Log Policy............................................................................................................................299
9.3. Managing the Central Log...........................................................................................................299
9.3.1. Configuring Central Log Options..........................................................................................................299
9.3.2. Viewing the Central Log (Delogging)...................................................................................................300
9.5. Managing Local Logging.............................................................................................................301
9.5.1. Configuring Local Logging Options......................................................................................................302
9.5.2. Viewing the Local Log..........................................................................................................................302
9.6. Managing SSM Alarms and Events ............................................................................................302
9.6.1. Alarms and Events Window..................................................................................................................302
14.4.1. Mounting via the Command Line........................................................................................................351
14.4.2. Mounting via the ‘/etc/fstab’ File.........................................................................................................351
14.4.3. Mount Options.....................................................................................................................................352
14.4.4. Un-mounting an HPSS Filesystem.......................................................................................................354
14.4.5. Linux ‘proc’ Filesystem Statistics........................................................................................................354
16.1.3. System Info..........................................................................................................................................368
16.1.4. System Management............................................................................................................................369
16.1.5. User Interfaces.....................................................................................................................................370
The HPSS Management Guide is intended as a resource for HPSS administrators. For those performing the initial
configuration for a new HPSS system, Chapter 1 provides a configuration roadmap. For both new systems and those
upgraded from a previous release, Chapter 1 provides a configuration, operational, and performance checklist which
should be consulted before bringing the system into production. The remaining chapters contain the details for
configuring, reconfiguring, monitoring, and managing an HPSS system.
Conventions Used in This Book
Example commands that should be typed at a command line will be proceeded by a percent sign (‘%’) and be
presented in a boldface courier font:
% sample command
Any text preceded by a pound sign (‘#’) should be considered comment lines:
# This is a comment
Angle brackets (‘<>’) denote a required argument for a command:
% sample command <argument>
Square brackets (‘[]’) denote an optional argument for a command:
% sample command [optional argument]
Vertical bars (‘|’) denote different choices within an argument:
% sample command <argument1 | argument2>
A byte is an eight bit data octet. A kilobyte, KB, is 1024 bytes (2
10
bytes). A megabyte, MB, is 1048576
bytes (220 bytes). A gigabyte, GB, is 1073741824 bytes (230 bytes), a terabyte, TB, is 1099511627776
bytes (240 bytes), and a petabyte, PB, is 1125899906842624 bytes (250 bytes).
This chapter defines the high-level steps necessary to configure, start, and verify correct operation of a
new 7.1 HPSS system, whether that system is created from scratch or created by conversion from a 6.2
HPSS system.
To create or modify the HPSS configuration, we recommend that the administrator first be familiar with
the information described in the HPSS Installation Guide, Chapter 2: HPSS Basics and Chapter 3: HPSS Planning.
Before performing the procedures described in this chapter, be certain that the appropriate system
preparation steps have been performed. See the HPSS Installation Guide, Chapter 4: System Preparation
for more information. For a system created from scratch, be certain that the HPSS installation and
infrastructure configuration have been completed. See the HPSS Installation Guide, Chapter 5: HPSS Installationand Infrastructure Configuration for more information. To convert from a 6.2 system, see
the HPSS Conversion Guide for HPSS release 7.1.
1.2. Starting the SSM GUI for the First Time
The HPSS system is ready to be configured using SSM once the HPSS software is installed on the node
and the HPSS infrastructure components are configured. In order to start the SSM GUI you must first
start all infrastructure components and the SSM System Manager as follows:
% /opt/hpss/bin/rc.hpss -m start
Next you will need to add an SSM Admin user. To do this you will need to invoke the hpssuser utility as
follows:
Once the SSM Admin user has been created, you can invoke the SSM GUI as follows (for hpssgui.pl
options, see the hpssgui man page):
% /opt/hpss/bin/hpssgui.pl
Note: This command may be done as an HPSS user.
When the SSM GUI is running you can begin to configure the rest of HPSS (servers, devices, etc) as
described in the following sections. For more information on SSM, see Chapter 3: Using SSM on page
31.
1.3. HPSS Configuration Roadmap (New HPSS Sites)
The following steps summarize the configuration of an HPSS system when creating the 7.1system from
scratch (not upgrading from a previous release). It is important that the steps be performed in the order
listed. Each step is required unless otherwise indicated. Each step is discussed in more detail in the
referenced section.
1. Configure storage subsystems (Section 4.2.2:Creating a New Storage Subsystem on page 76)
Subsystems can be configured only partially at this time. The Gatekeeper, Default COS, and
Allowed COS fields will be updated in a later step.
2. Configure HPSS storage policies
·Accounting Policy (Section 13.2.1: on page 330)
·Log Policies (Section 9.2: Log Policies on page 295)
·Location Policy (Section 2.4: Location Policy on page 26)
·Migration Policies (Section 6.4: Migration Policies on page 180)
·Purge Policies (Section 6.5: Purge Policies on page 189)
3. Configure HPSS storage characteristics
·Storage Classes (Section 6.1.1: Configured Storage Classes on page 157)
·Storage Hierarchies (Section 6.2: Storage Hierarchies on page 170)
·Classes of Service (Section 6.3: Classes of Service on page 174)
4. Configure HPSS servers (Section 5.1: Server Configuration on page 87)
5. Create global configuration (Section 4.1: Global Configuration Window on page 72)
6. Configure MVR devices and PVL drives (Section 7.1: Configure a New Device & Drive on page
196)
7. Configure file families, if used (Section 6.6: File Families on page 193)
8. Update storage subsystem configurations with Gatekeeper and COS information (Section 4.2.4:
Modifying a Storage Subsystem on page 81 and Section 4.2.3:Storage Subsystem Configuration
Window on page 76)
9. Create the endpoint map (Section 5.1.3: Location Server Additional Configuration on page 99).
1.4. Initial HPSS Startup Roadmap (All Sites)
This section provides instructions for starting the HPSS servers and performing post-startup
configuration. For sites which are converting from 6.2, only step 1 may be necessary. For sites
configuring a new 7.1 system from scratch, all steps are necessary:
1. Start the HPSS servers (Section 5.2.2: Starting HPSS Servers on page 149)
2. Unlock the PVL drives (Section 7.4.2: Locking a Drive on page 220)
3. Create HPSS storage space:
A. Import volumes into HPSS (Section 8.1.1: Importing Volumes into HPSS on page 223)
5. Create Filesets and Junctions (Section 10.1: Filesets & Junctions List on page 308 and Section
10.5: Creating a Junction on page 315)
6. Create HPSS /log Directory
If log archiving is enabled, using an HPSS namespace tool such as scrub or ftp, create the /log
directory in HPSS. This directory must be owned by hpsslog and have permissions rwxr-xr-x.
The /log directory can be created by the root user using ftp as follows:
% ftp <node> <HPSS Port> # login as root user
ftp> mkdir /log
ftp> quote site chown hpsslog /log
ftp> quote site chmod 755 /log
1.5. Additional Configuration Roadmap (All Sites)
This section provides a high level roadmap for additional HPSS configuration.
1. Configure HPSS User Interfaces (Chapter 14: User Interfaces on page 339)
2. Set up Backup for DB2 and Other Infrastructure (Chapter 15: Backup and Recovery on page 356)
3. Set up High Availability, if desired (HPSS Installation Guide, Chapter 3: HPSS Planning)
4. Optionally configure support for both authentication mechanisms (HPSS Installation Guide,
Section 5.9: Supporting Both Unix and Kerberos Authentication for SSM)
1.6. Verification Checklists (All Sites)
This section provides a number of checklists regarding configuration, operational and performance
issues.
1.6.1. Configuration Checklists
After HPSS is running, the administrator should use the following checklists to verify that HPSS was
configured or converted correctly:
Global Configuration
•Verify that a Default Class of Service has been selected.
•Verify that a Root Core Server has been selected.
Storage Subsystem Configuration
•Verify that a Default Class of Service has been selected if desired.
•Verify that a Gatekeeper has been selected if gatekeeping or account validation is required.
•Verify that the COS Name list has been filled in correctly.
•Verify that a Core Server and Migration Purge Server have been configured for each storage
subsystem.
•Verify that each storage subsystem is accessible by using lsjunctions and ensuring that there is at
least one junction to the Root fileset of each subsystem. (The root fileset for a given subsystem
can be found in the specific configuration for the subsystem’s Core Server)
Servers
•Verify that all required HPSS servers are configured and running.
•Verify that all servers are configured with the intended level of logging, whether using their
server specific policies or the default policy. Also, verify that all Core Server and Mover log
policies have the DEBUG flag turned on to aid in the diagnostics of any future problems.
Devices and Drives
•Verify that all devices/drives are configured and each is assigned to an appropriate PVR/Mover.
•For tape devices, verify that the “Locate Support” option is enabled if supported.
•For tape devices, verify that the “NO-DELAY” option is enabled if supported by the device.
•For disk devices, verify that the “Bytes on Device” and “Starting Offset” values are correct.
•Verify that all configured drives are unlocked.
Storage Classes
•Verify that all storage classes are defined and each has sufficient free storage space.
•Verify that each storage class that will be migrated and purged is configured with the appropriate
migration and purge policy.
•Verify that no storage class at the lowest level in a hierarchy is configured with a migration or
purge policy.
•To support repack and recover of tape volumes, verify that the stripe width of each tape storage
class is less than half of the number of available drives of the appropriate drive type.
Storage Hierarchies
•Verify that all storage hierarchies are defined.
Classes of Service (COS)
•Verify that all classes of service are defined.
•Verify that each COS is associated with the appropriate storage hierarchy.
•Verify that the COS is configured to use the characteristics of the hierarchy and the underlying
storage classes. In addition, verify that the classes of service have the correct Minimum File Size
and Maximum File Size values. If these sizes overlap, the file placement may be indeterminate
when the user creates a file using the size hints. For classes of services which are not to be used as
part of standard file placement, set their Force Selection flag to ON so that they will only be
•Monitor free space from the top level storage class in each hierarchy to verify that the migration
and purge policy are maintaining adequate free space.
1.6.3. Performance Checklist
Measure data transfer rates in each COS for:
•Client writes to disk
•Migration from disk to tape
•Staging from tape to disk
•Client reads from disk
Transfer rates should be close to the speed of the underlying hardware. The actual hardware speeds can
be obtained from their specifications and by testing directly from the operating system (e.g., using dd to
read and write to each device). Keep in mind that transfer performance can be limited by factors external
to HPSS. For example, HPSS file read performance may be limited by the performance of the UNIX file
system writing the file rather than limits inside HPSS.
As of release 6.2, HPSS no longer uses DCE security services. The new approach to security divides
services into two APIs, known as mechanisms, each of which has multiple implementations.
Configuration files control which implementation of each mechanism is used in the security realm
(analogous to a DCE cell) for an HPSS system. Security mechanisms are implemented in shared object
libraries and are described to HPSS by a configuration file. HPSS programs that need to use the
mechanism dynamically link the library to the program when the program starts.
The first type of mechanism is the authentication mechanism. This API is used to acquire credentials
and to verify the credentials of clients. Authentication verifies that a client really is who he claims to be.
The second type of mechanism is the authorization mechanism. Once a client's identity has been
verified, this API is used to obtain the authorization details associated with the client such as uid, gid,
group membership, etc., that are used to determine the privileges accorded to the client and the resources
to which it has access.
2.1.1. Security Services Configuration
Ordinarily, the configuration files that control HPSS's access to security services are set up either by the
installation tool, mkhpss, or by the metadata conversion tools. This section is provided purely for
reference. Each of the files below is stored by default in /var/hpss/etc.
•auth.conf, authz.conf
These files define which shared libraries provide implementations of the authentication and
authorization mechanisms, respectively. They are plain text files that have the same format. Each
line is either a comment beginning with # or consists of two fields separated by whitespace: the
path to a shared library and the name of the function used to initialize the security interface.
•site.conf
This file defines security realm options. This is a plain text file in which each line is a comment
beginning with # or is made up of the following fields, separated by whitespace:
·<siteName> - the name of the local security site. This is usually just the realm name in
lowercase.
·<realmName> - the name of the local security realm. If using Kerberos authentication, this is
the name of the Kerberos realm. For UNIX authentication, it can be any non-empty string. By
convention, it is usually the fully qualified hostname.
·<realmID> - the numeric identifier of the local security realm. If using Kerberos
authentication and this is a preexisting site going through conversion, this value is the same as
the DCE cross cell ID which is a unique number assigned to each site. A new site setting up a
new HPSS system will need to contact an HPSS support representative to obtain a unique
value.
·<authzMech> - the name of the authorization mechanism to be used by this HPSS system.
·<authzURL> - a string used by the authorization mechanism to locate the security data for
this realm. This should be "unix" for UNIX authorization, and for LDAP it should be an
LDAP URL used to locate the entry for the security realm in an LDAP directory.
2.1.2. Security Mechanisms
HPSS 7.1 supports UNIX and Kerberos mechanisms for authentication. It supports LDAP and UNIX
mechanisms for authorization.
2.1.2.1. UNIX
UNIX-based mechanisms are provided both for authentication and authorization. These can draw either
from the actual UNIX user and group information on the current host or from a separately maintained set
of files used only by HPSS. This behavior is controlled by the setting of the variable
HPSS_UNIX_USE_SYSTEM_COMMANDS in /var/hpss/etc/env.conf. If this variable is set to any nonempty value other than FALSE, the actual UNIX user and group data will be used. Otherwise, local files
created and maintained by the following HPSS utilities will be used. Consult the man pages for each
utility for details of its use.
•hpss_unix_keytab - used to define "keytab" files that can be used to acquire credentials
recognized by the UNIX authentication mechanism.
•hpss_unix_user - used to manage users in the HPSS password file (/var/hpss/etc/passwd).
•hpss_unix_group - used to manage users in the HPSS groups file (/var/hpss/etc/group).
•hpss_unix_passwd - used to change passwords of users in the HPSS password file.
•hpss_unix_keygen - used to create a key file containing a hexadecimal key. The key is used
during UNIX authentication to encrypt keytab passwords. The encryption provides an extra layer
of protection against forged passwords.
Keep in mind that the user and group databases must be kept synchronized across all nodes in an HPSS
system. If using the actual UNIX information, this can be accomplished using a service such as NIS. If
using the HPSS local files, these must manually be kept in synchronization across HPSS nodes.
2.1.2.2. Kerberos 5
The capability to use MIT Kerberos authentication is provided in HPSS 7.1, however, IBM
Service Agreements for HPSS do not provide support for problem isolation nor fixing defects
(Level 2 and Level 3 support) in MIT Kerberos. Kerberos maintenance/support must be siteprovided.
Kerberos 5 is an option for the authentication mechanism. When this option is used, the local realm
name is taken to be the name of a Kerberos realm. The Kerberos security services are used to obtain and
verify credentials.
LDAP authorization is not supported by IBM Service Agreements. The following information
is provided for sites planning to use LDAP authorization with HPSS 7.1 as a site supported
feature.
An option for the authorization mechanism is to store HPSS security information in an LDAP directory.
LDAP (Lightweight Directory Access Protocol) is a standard for providing directory services over a
TCP/IP network. A server supporting the LDAP protocol provides a hierarchical view of a centralized
repository of data and provides clients with sophisticated search options. The LDAP software supported
by the HPSS LDAP authorization mechanism is IBM Tivoli Directory Server (Kerberos plug-in available
for AIX only) and OpenLDAP (Kerberos plug-in available for AIX and Linux). One advantage of using
the LDAP mechanism over the UNIX mechanism is that LDAP provides a central repository of
information that is used by all HPSS nodes; it doesn't have to be manually kept in sync.
The rest of this section deals with how to accomplish various administrative tasks if the LDAP
authorization mechanism is used.
2.1.2.3.1. LDAP Administrative Tasks
Working with Principals
•Creating a principal
A principal is an entity with credentials, like a user or a server. The most straightforward way to
create a new principal is to use the -add and -ldap options of the hpssuser utility. The utility will
prompt for any needed information and will drive the hpss_ldap_admin utility to create a new
principal entry in the LDAP server. To create a new principal directly with the
hpss_ldap_admin utility, use the following command at the prompt:
princ create -uid <uid> -name <name> -gid <gid> -home <home>
-shell <shell> [-uuid <uuid>]
If no UUID is supplied, one will be generated.
•Deleting a principal
Likewise, use the -del and -ldap options of the hpssuser utility to delete the named principal from
the LDAP server. To delete a named principal directly with the hpss_ldap_admin utility, use the
following command at the prompt:
princ delete [-uid <uid>] [-name <name>] [-gid <gid>]
[-uuid <uuid>]
You may supply any of the arguments listed. This command will delete any principal entries in
the LDAP information that have the indicated attributes.
·-mech - a string identifying the authorization mechanism in use at the foreign realm, such as
"unix" or "ldap"
·-name - the name of the foreign realm, e.g. "SOMEREALM.SOMEDOMAIN.COM"
·-url - the URL of the security mechanism of the foreign realm. This only matters if the
foreign realm is using LDAP as its authorization mechanism. If so, this must be the LDAP
URL of the main entry for the security realm in the foreign LDAP server. This should be
obtained from the foreign site's administrator. An example would be:
"ldap://theirldapserver.foreign.com/cn=FOREIGNREALM.FOREIGN.COM"
•Deleting a trusted foreign realm
To delete an entry for a trusted foreign realm, use the following hpss_ldap_admin command:
trealm delete [-id <realmID>] [-name <realmName>]
Any of the arguments listed can be supplied to select the trusted realm entry that will be deleted.
2.2. HPSS Server Security ACLs
Beginning with release 6.2, HPSS uses a table of access control information stored in the DB2
configuration database to control access to HPSS servers. This is the AUTHZACL table. HPSS
software uses the configured authentication mechanism (e.g. Kerberos) to determine a caller's identity via
credentials provided by the caller, then uses the configured authorization mechanism to retrieve the
details of the caller that determine the access granted. Once the identity and authorization information
have been obtained, each HPSS server grants or denies the caller's request based on the access control list
information stored in the database.
The default ACLs for each type of server are as follows:
Core Server:
r—-c--- user ${HPSS_PRINCIPAL_FTPD}
rw—c--- user ${HPSS_PRINCIPAL_DMG}
rw-c-dt user ${HPSS_PRINCIPAL_MPS}
r--c--- user ${HPSS_PRINCIPAL_NFSD}
rw-c-d- user ${HPSS_PRINCIPAL_SSM}
r--c--- user ${HPSS_PRINCIPAL_FS}
------t any_other
Gatekeeper:
rw----- user ${HPSS_PRINCIPAL_CORE}
rw-c--- user ${HPSS_PRINCIPAL_SSM}
r-----t any_other
Location Server:
r--c--t user ${HPSS_PRINCIPAL_SSM}
r-----t any_other
Mover:
rw-c--t user ${HPSS_PRINCIPAL_SSM}
r-----t any_other
rw---dt user ${HPSS_PRINCIPAL_PVR}
rw-c-dt user ${HPSS_PRINCIPAL_SSM}
------t any_other
PVR:
rw---dt user ${HPSS_PRINCIPAL_PVL}
rw-c--t user ${HPSS_PRINCIPAL_SSM}
------t any_other
SSM:
rwxcidt user ${HPSS_PRINCIPAL_ADM_USER}
------t any_other
All other types:
rw-c-dt user ${HPSS_PRINCIPAL_SSM}
------t any_other
In most cases, the ACLs created by default for new servers should be adequate. In normal operation, the
only ACL that has to be altered is the one for the SSM client interface. This is handled automatically by
the -ssm option of the hpssuser utility. If, for some reason, an ACL should need to be modified in some
other way, the hpss_server_acl utility can be used. See the hpss_server_acl man page for more
information.
2.3. SSM User Security
SSM supports two types of users, administrators and operators:
•admin. This security level is normally assigned to an HPSS administrator. Administrators may
open all SSM windows and perform all control functions provided by SSM.
•operator. This security level is normally assigned to an HPSS operator. Operators may open
most SSM windows and can perform all SSM control functions except for HPSS configuration.
Security is applied both at the window level and the field level. A user must have permission to open a
window to do anything with it at all. If the user does succeed in opening a window, all items on that
window may be viewed. Field level security then determines whether the user can modify fields, push
buttons, or otherwise modify the window.
The security level of an SSM user is determined by his entry in the access control information table in
the HPSS configuration database. The initial security level for a user is assigned when the SSM user is
created by hpssuser. Security levels may be viewed and modified with the hpss_server_acl utility.
See also Section 3.3.2.2: SSM User Authorization on page 36.
2.4. Location Policy
All Location servers in an HPSS installation share a Location Policy. The Location Policy is used by the
Location Servers to determine how and how often information should be updated. In general, most of the
default values for the policy can be used without change.
The Location Policy can be created and updated using the Location Policy window. If the Location
Policy does not exist, the fields will be displayed with default values for a new policy. Otherwise, the
configured policy will be displayed.
Once a Location Policy is created or updated, it will not be in effect until all local Location Servers are
restarted or reinitialized. The Reinitialize button on the Servers window can be used to reinitialize a
running Location Server.
2.4.2. Location Policy Configuration Window
This window allows you to manage the location policy, which is used by HPSS Location Servers. Only
one location policy is permitted per HPSS installation.
Once a location policy is created or updated, it will not take effect until all local Location Servers are
started or reinitialized. The Reinitialize button on the Servers list window (Section 5.1: Server List on
page 83) can be used to reinitialize a running Location Server.
Field Descriptions
Location Map Update Interval. Interval in seconds that the Location Server rereads the location map.
Advice - If this value is set too low, a load will be put on the database while reading configuration
metadata. If set too high, new servers will not be registered in a timely manner. Set this value higher if
timeouts are occurring during Location Server communications.
If you have multiple Location Servers, you should consider increasing the update interval since each
Location Server obtains information independently and will increase the overall system load.
Maximum Request Threads. The maximum number of concurrent client requests allowed.
Advice - If the Location Server is reporting heavy loads, increase this number. If this number is above
300, consider replicating the Location Server on a different machine. Note if this value is changed, the
general configuration thread value (Thread Pool Size) should be adjusted so that its value is always
larger than the Maximum Request Threads. See Section 5.1.1.2: Interface Controls on page 92.
Maximum Request Threads should not normally exceed (Maximum Location Map Threads + 400).
This is not enforced. If you need more threads than this to handle the load, consider configuring an
additional Location Server.
Maximum Location Map Threads. The maximum number of threads allocated to contact other
Location Servers concurrently.
Advice - The actual number of Location Map threads used is Maximum Location Map Threads or the
number of other HPSS installations to contact, whichever is smaller. This value does not need to be
changed unless the system is experiencing timeout problems contacting other Location Servers.
Location Map Timeout. The maximum amount of time in seconds to wait for a Location Server to
return a location map.
Advice - This value should be changed only if the system is experiencing very long delays while
contacting another Location Server.
Local HPSS Site Identification:
HPSS ID. The UUID for this HPSS installation.
Local Site Name. The descriptive name of the HPSS installation.
Advice - Pick a name to uniquely describe the HPSS system.
Local Realm Name. The name where the realm containing Location Server path information should be
stored.
Advice - All clients will need to know this group name since it is used by them when initializing to
contact the Location Server. If the default is not used, ensure that the associated environment variable
for this field is changed accordingly for all HPSS interfaces.
2.4.3. Deleting a Location Policy
The Location Policy can be deleted using the Location Policy window. Since only one Location Policy
may be defined in a system, and it must exist for the system to run, it is better to simply update the policy
rather than delete and recreate it. See Section 2.4.2: Location Policy Configuration Window on page 27
for more details.
2.5. Restricting user access to HPSS.
System administrators may deny access to HPSS to specific users by including that user in a
configuration file that is read by the HPSS Core Server. This file is read by the Core Server at start up
time and also read again when the SSM Administrator presses the Reload List button on the Restricted Users window or whenever the Core Server receives a REINIT request. Any user in this file is denied
the usage of the HPSS system completely. To set up this file, you must do the following:
1. Add the HPSS_RESTRICTED_USER_FILE environment variable to /var/hpss/etc/env.conf. Set
the value of this variable to the name of the file that will contain the list of restricted users.
2. Edit the file and add the name of the user to the file. The name should be in the form:
name@realm
The realm is not required if the user is local to the HPSS realm. For example:
dsmith@lanl.gov
3. You may put comment lines in the file by beginning the line with a “#”.
4. In order for the file to become effective, restart the Core Server, press the Reload List button on
the Restricted Users SSM window or REINIT the Core Server.
NOTE: The file should be configured on the system where the root Core Server is running; this
is the Core Server associated with the Root Name Server. Additionally, if running with multiple
storage subsystems on different machines, be sure to configure the
HPSS_RESTRICTED_USER_FILE on each machine where a Core Server runs.
2.5.1. Restricted Users Window
This window lists all the root Core Server users restricted from HPSS access. To open the window, from
the HPSS Health and Status window select the Configure menu, and from there select the Restricted
Users menu item.