Filter
Top Products
To start the Startup Daemon, use the “-d” option to rc.hpss:
% su -
% /opt/hpss/bin/rc.hpss -d [start]
5.2.2.2. Starting SSM
The SSM System Manager configuration metadata should have already been created by mkhpss as part
of the the infrastructure configuration. After SSM is started, this configuration metadata may be modified
if necessary. Refer to the HPSS Installation Guide, Section 2.3.4: HPSS Infrastructure for more
information.
The SSM server startup script, rc.hpss, can be used to invoke the HPSS System Manager. The server
requires a number of environment variable values to be used as its command line arguments and to be
used to configure and manage the HPSS servers. These variables are defined by the system. The system
defined values can be overridden in the env.conf file. They should have been edited to reflect the site’s
configuration during the HPSS infrastructure configuration phase.
Before starting up the System Manager, ensure that DB2 and other prerequisite software are up and
running.
The rc.hpss script will not start the System Manager if it is already running on the same node. Ensure that
only one instance of the SSM System Manager is running at any one time.
To start the SSM System Manager, use the “-m” option to rc.hpss:
% su -
% /opt/hpss/bin/rc.hpss -m [start]
To start an SSM graphical user interface or command line interface session, see Section 3.3:
Configuration and Startup of hpssgui and hpssadm on page 34, or the hpssgui or hpssadm man page. For
best performance, it is recommended that the SSM graphical user interface (GUI) be installed on the
SSM user's desktop machine. However, authorized SSM users can invoke the hpssgui script directly from
the HPSS server machine if desired. However, most users of the SSM command line interface (hpssadm)
will most likely invoke the script on the server machine.
5.2.2.3. Starting Other HPSS Servers
Other servers are started using SSM or can be automatically started upon startup of the System Manager
by using the Core Server Auto Startup feature. This feature can be set using the Core Server
Configuration window. Refer to Section 5.1.1.1: Execution Controls on page 90.
When starting a server from SSM using the Servers window, one or more HPSS servers can be started by
the same request. SSM forwards the server’s configuration data to the appropriate HPSS Startup
Daemon. The Startup Daemon invokes the server with the appropriate input arguments. After the server
is started, SSM attempts to establish a connection with the server. The server status is reported in the
Status field on the Servers window. Refer to Section 5.1: Server List on page 83 for more information.
Before starting a server, ensure that DB2 and other prerequisite software are running, Kerberos is
running (if using Kerberos authentication), that the Startup Daemon on the server’s node is running and
has a connection with SSM, and that the server is configured and its Executable flag is set. Ensure that
any required PVR controllers are up and running before bringing up the PVRs.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 150