Serviceguard Manager Version A.05.02 Release Notes, Third Edition, July 2009

available for the user. Even if a snmp agent dies on the backend, the polling should be able to
refresh the data with a slight delay, depending on the polling interval setting which can be
customized by the user.
JAGaf45963 Cannot cmapplyconf from root from node in cluster
What is the problem? Creating or modifying a cluster or package within Serviceguard Manager
(equivalent to using the cmapplyconf command) may result in the inability for Serviceguard
to resolve the source IP address to a valid IP Address.
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/hostson all nodes within the cluster. All interfaces on all nodes that
may be used as a Session Server, and all nodes that may be included in their session, must share
all of each other's interface definitions. The name service switch policy for hosts must be set to
files followed by any other sources used such as DNS, NIS or LDAP. Below is an example hosts
file:
15.145.162.131 gryf.uksr.hp.com
gryf 10.8.0.131 gryf.uksr.hp.com gryf 10.8.1.131
gryf.uksr.hp.com gryf 10.8.2.131 gryf.uksr.hp.com
gryf 15.145.162.132 sly.uksr.hp.com sly 10.8.0.132
sly.uksr.hp.com sly 10.8.1.132 sly.uksr.hp.com
sly 10.8.2.132 sly.uksr.hp.com sly 15.145.162.67
bit.uksr.hp.com bit 10.30.8.8 bit.uksr.hp.com
bit 15.145.162.69 bot.uksr.hp.com bot 10.30.8.7
bot.uksr.hp.com bot
Following is an example host entry from /etc/nsswitch.conf:
hosts: files [NOTFOUND=continue] dns
JAGaf44886 In Asian locales in Windows, the uninstaller has illegible text (ZeroG bug)
What is the problem? The problem is that in Asian locales, the text size in the Uninstaller panel is
so small that it is hard to read. This affects usability of the installer.
What is the workaround? There is no workaround.
JAGaf44056 Traditional-Chinese font size too small on HP-UX client
What is the problem? On Serviceguard Manager A.04.02 on HP-UX, the Traditional Chinese font
is small and difficult to read.
What is the workaround? To increase the font size for Serviceguard Manager in Traditional Chinese
on HP-UX systems, please follow the instructions below. [Please note that when this work-around
has been completed, though the font size will be larger, you may have to increase the size of
windows to fully see all of the buttons on Serviceguard Manager's screens.
Installing and Running Serviceguard Manager 43