Changes since 4.5 | Server | GUI | ADM |
|
|
|
|
The SSM client scripts can use ports exempted by the network | n | n | n |
administrator as firewall exceptions. See 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. Access to port | n | n | n |
111 is needed if the RPC portmapper is needed to find the System |
|
|
|
Manager. |
|
|
|
The user_authorization.dat and hpssadm.config files provided in HPSS 4.5 | n | n | n |
are no longer available. |
|
|
|
In 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. |
|
|
|
The hpssgui and hpssadm programs will now optionally record every error |
| n | n |
and informational message in an ASCII log file. The |
|
|
|
programs is used to specify whether to create the session log and what to |
|
|
|
name it. |
|
|
|
The basic and specific server config structures, along with the server's log |
| n | n |
policy, have been combined in 5.1 into a single structure. |
|
|
|
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. |
|
|
|
|
|
|
|
The delog utility is no longer available via the SSM GUI. This feature has |
| n |
|
been retired. |
|
|
|
The ability to broadcast messages to other SSM GUI users is not yet |
| n |
|
available. |
|
|
|
Alarms and events are no longer acknowledged from the SSM GUI. |
| n |
|
|
|
|
|
The SSM clients can specify the number of items to display for the Alarms |
| n | n |
and Events list. See the |
|
|
|
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 |
|
|
|
pages and Section 9.6.5: Controlling SSM Log Message handling in the |
|
|
|
HPSS Management Guide. |
|
|
|
HPSS Installation Guide | July 2008 |
Release 6.2 (Revision 2.0) | 23 |