Serviceguard Manager Version A.04.02 Release Notes, February 2005

Serviceguard Manager Version A.04.02 Release Notes
Patches and Fixes in this Version
Chapter 150
• What is the workaround? There is no workaround. Install and use
Serviceguard Manager on a Windows or HP-UX management
station.
JAGaf46330 HP-UX/Asian locales: non-default printers n/a in
JavaHelp print services
• What is the problem? The problem occurs in Asian locales on HP-UX
systems. The online help system contains a print command. When
you press the print command, the dialogue allows you to select
configured printer devices. In C Locale, these configured print
devices appear correctly in the print services window. In Asian
locales, the literal 'device' is shown instead.
• What is the workaround? Copy and paste the text into an editor
window, then print that text file.
JAGaf45963 Cannot cmapplyconf from root from node in cluster
• What is the problem? For redundancy, Serviceguard commands use
all networks available on a system to communicate with
Serviceguard daemons. This includes configured interfaces not listed
in the cluster ASCII file. To authorize these communications,
Serviceguard must be able to resolve the source IP address to a valid
hostname. Valid hostnames include every node in the cluster and
any node outside the cluster that needs to communicate with nodes
within a cluster, which would include a Session Server COM node in
Serviceguard Manager.
A permission problem will result when Serviceguard cannot verify
that the source address of a message is authorized and cannot
resolve the source IP address to a valid hostname. The actual
symptoms of a permission problem will vary depending on what
operation is being performed. The following is an example of a
message which could be seen in syslog.log:
Dec 1 13:13:45 sly cmclconfd[15227]: WARNING: User root
from ip address 10.8.1.131 does not have privileges to
access this node. Either they are coming from a node
without enhanced security or somebody may be attempting
un-authorized access to this system.
• What is the workaround? To avoid permission problems, all
interfaces for all authorized nodes must be defined in /etc/hosts on
all nodes within the cluster. All interfaces on all nodes that may be