Changes since 5.1

Server

GUI

ADM

 

 

 

 

The SSM client script options for connecting to the System Manager

n

n

n

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

n

n

n

administrator as firewall exceptions has changed; 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.

 

 

 

The default setting is 0 (zero) which means that the port will be chosen by

 

 

 

the RPC portmapper. See Section 3.3.6:Using SSM Through a Firewall,

 

 

 

of the HPSS Management Guide.

 

 

 

Access to port 88 is needed for Kerberos authentication and access to port

n

n

n

111 is needed if the RPC portmapper is needed to find the System

 

 

 

Manager.

 

 

 

 

 

 

 

The ssmuser.config file provided in HPSS 5.1 is no longer available. In

n

n

n

6.2, all authorized SSM users and their privilege levels are defined in the

 

 

 

DB2 user acl AUTHZACL table. See Section 3.3.2.1: hpssuser Utility and

 

 

 

Section 3.3.2.2: SSM User Authorization in the HPSS Management Guide

 

 

 

for details.

 

 

 

 

 

 

 

SSM now represents the three basic Core Server volume structures, the

 

n

n

physical volume, virtual volume, and storage map, as a single combined

 

 

 

Core Server volume structure.

 

 

 

 

 

 

 

Access to the delog utility via the SSM GUI, deferred in 5.1, has now been

 

n

 

permanently retired.

 

 

 

 

 

 

 

The ability to broadcast messages to other SSM GUI users is not yet

 

n

 

available.

 

 

 

The SSM clients can specify the number of items to display for the Alarms

 

n

n

and Events list. See the -N option on the hpssadm/hpssgui man page and

 

 

 

Section 9.6: Managing SSM Alarms and Events in the HPSS Management

 

 

 

Guide.

 

 

 

The SSM clients keep an internal cached copy of the Alarms and Events

 

n

n

list which is maintained by regular polling requests to the System

 

 

 

Manager. Each polling request returns only “new” messages, those which

 

 

 

have not already been retrieved by the SSM client in a previous polling

 

 

 

request. If there are no new messages in the System Manager log cache,

 

 

 

no messages are returned. This will help performance of the display of

 

 

 

this window. See the -A, -G and -N options of the hpssadm/hpssgui man

 

 

 

pages and Section 9.6.5: Controlling SSM Log Message Handling in the

 

 

 

HPSS Management Guide.

 

 

 

The ability to see which users are logged into SSM, referred to in HPSS

 

n

n

4.5 as a list of SSM "consoles", was not yet available in 5.1. It is now

 

 

 

available in 6.2 as part of the System Manager Statistics window from both

 

 

 

the hpssgui and hpssadm.

 

 

 

 

 

 

 

HPSS Installation Guide

July 2008

Release 6.2 (Revision 2.0)

29

Page 29
Image 29
IBM HPSS manual SSM User Authorization in the Hpss Management Guide