Computer Drive User Manual
Table Of Contents
- Chapter 1. HPSS 7.1 Configuration Overview
- Chapter 2. Security and System Access
- Chapter 3. Using SSM
- 3.1. The SSM System Manager
- 3.2. Quick Startup of hpssgui
- 3.3. Configuration and Startup of hpssgui and hpssadm
- 3.4. Multiple SSM Sessions
- 3.5. SSM Window Conventions
- 3.6. Common Window Elements
- 3.7. Help Menu Overview
- 3.8. Monitor, Operations and Configure Menus Overview
- 3.9. SSM Specific Windows
- 3.10. SSM List Preferences
- Chapter 4. Global & Subsystem Configuration
- 4.1. Global Configuration Window
- 4.2. Storage Subsystems
- 4.2.1. Subsystems List Window
- 4.2.2. Creating a New Storage Subsystem
- 4.2.3. Storage Subsystem Configuration Window
- 4.2.3.1. Create Storage Subsystem Metadata
- 4.2.3.2. Create Storage Subsystem Configuration
- 4.2.3.3. Create Storage Subsystem Servers
- 4.2.3.4. Assign a Gatekeeper if Required
- 4.2.3.5. Assign Storage Resources to the Storage Subsystem
- 4.2.3.6. Create Storage Subsystem Fileset and Junction
- 4.2.3.7. Migration and Purge Policy Overrides
- 4.2.3.8. Storage Class Threshold Overrides
- 4.2.4. Modifying a Storage Subsystem
- 4.2.5. Deleting a Storage Subsystem
- Chapter 5. HPSS Servers
- 5.1. Server List
- 5.1. Server Configuration
- 5.1.1. Common Server Configuration
- 5.1.1. Core Server Specific Configuration
- 5.1.2. Gatekeeper Specific Configuration
- 5.1.3. Location Server Additional Configuration
- 5.1.4. Log Client Specific Configuration
- 5.1.1. Log Daemon Specific Configuration
- 5.1.2. Migration/Purge Server (MPS) Specific Configuration
- 5.1.3. Mover Specific Configuration
- 5.1.3.1. Mover Specific Configuration Window
- 5.1.3.1. Additional Mover Configuration
- 5.1.3.1.1. /etc/services, /etc/inetd.conf, and /etc/xinetd.d
- 5.1.3.1.2. The Mover Encryption Key Files
- 5.1.3.1.3. /var/hpss/etc Files Required for Remote Mover
- 5.1.3.1.1. System Configuration Parameters on IRIX, Solaris, and Linux
- 5.1.3.1.1. Setting Up Remote Movers with mkhpss
- 5.1.3.1.2. Mover Configuration to Support Local File Transfer
- 5.1.1. Physical Volume Repository (PVR) Specific Configuration
- 5.1.1. Deleting a Server Configuration
- 5.1. Monitoring Server Information
- 5.1.1. Basic Server Information
- 5.1.1. Specific Server Information
- 5.1.1.1. Core Server Information Window
- 5.1.1.1. Gatekeeper Information Window
- 5.1.1.1. Location Server Information Window
- 5.1.1.2. Migration/Purge Server Information Window
- 5.1.1.3. Mover Information Window
- 5.1.1.1. Physical Volume Library (PVL) Information Window
- 5.1.1.2. Physical Volume Repository (PVR) Information Windows
- 5.1. Real-Time Monitoring (RTM)
- 5.2. Starting HPSS
- 5.1. Stopping HPSS
- 5.2. Server Repair and Reinitialization
- 5.1. Forcing an SSM Connection
- Chapter 6. Storage Configuration
- 6.1. Storage Classes
- 6.2. Storage Hierarchies
- 6.3. Classes of Service
- 6.4. Migration Policies
- 6.5. Purge Policies
- 6.6. File Families
- Chapter 7. Device and Drive Management
- Chapter 8. Volume and Storage Management
- 8.1. Adding Storage Space
- 8.2. Removing Storage Space
- 8.3. Monitoring Storage Space
- 8.4. Dealing with a Space Shortage
- 8.5. Volume Management
- 8.6. Monitoring and Managing Volume Mounts
- 8.7. New Storage Technology Insertion
- Chapter 9. Logging and Status
- Chapter 10. Filesets and Junctions
- Chapter 11. Files, Directories and Objects by SOID
- Chapter 12. Tape Aggregation
- Chapter 13. User Accounts and Accounting
- Chapter 14. User Interfaces
- Chapter 15. Backup and Recovery
- Chapter 16. Management Tools
3.3.3. SSM Configuration File
The hpssgui and hpssadm scripts use the SSM configuration file, ssm.conf for configuration.
The mkhpss utility will create the SSM configuration file for the security mechanism supported by SSM.
The mkhpss utility will store the generated ssm.conf at $HPSS_PATH_SSM; the default location is /var/
hpss/ssm. The configuration file will contain host and site specific variables that the hpssgui and
hpssadm script will read. The variables contain information about:
• SSM hostname
• SSM RPC number
• SSM RPC protection level
• SSM security mechanism
• SSM UNIX Realm [only if using UNIX authentication]
If any of these configuration parameters are modified, the ssm.conf file must be updated and redistributed
from the server machine to all of the SSM client machines.
Users can also use their SSM configuration file to manage SSM client parameters instead of using the
command line options. The hpssgui and hpssadm scripts can be directed to use an alternate SSM
configuration file with the -m option. The default SSM configuration file contains comments describing
each of the available parameters that may be set along with any associated environment variable and
command line option. The following table documents these variables and the corresponding command
line options:
Table 1. SSM General Options
File Option Command Line
Option
Functionality
HPSS_SSM_ALARM_RATE -A Alarm refresh rate
LOGIN_CONFIG -C Full path to login.conf file
HPSS_SSM_DATE_FORMAT -D Date format pattern
HPSS_SSM_ALARMS_GET -G Number of alarms requested per poll
HPSS_SSM_LIST_RATE -L
How long hpssgui/hpssadm waits
between polling for lists
HPSS_SSM_ALARMS_DISPLAY -N Max number of alarms displayed by
hpssgui
HPSS_SSM_CLASSPATH -P Full path to hpss.jar file
LOG_FILE -S Full path for session log file
HPSS_SSM_WAIT_TIME -W How long SM waits before returning if
object is unchanged
HPSS_SSM_CNTRY_CODE -c Country code, internationalization
HPSS_SSM_DEBUG -d Debug flag
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 39