Serviceguard Manager Version A.05.02 Release Notes, March 2009

JAGaf48460 Event browser displays wrong status of snmp subagent
What is the problem? The event browser may incorrectly say that the SNMP subagent is down, and the trap
is not set, even when they are active and reporting new events.
What is the workaround? Follow these steps:
1. Bring up Set Trap dialog for the managed node.
2. Type in something in the textfield to force trap setting.
The status should now be Trap Set.
The back-end logic is:
Step 1: Use the community name supplied to set trap (Success or Failure)
Step 2: Query the status of the trap destination. Since the trap destination is already set in the backend,
Step 1 will not unset the trap, even if the community name is not correct. Step 2 will then display the updated
status.
Note: If the status is already Trap Set, unsetting the trap destination in the backend will not be visible in the
front-end GUI. In this case, please disconnect and then reconnect. Serviceguard Manager uses both snmp
event notification and polling to ensure the most up-to-date data is 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.
38 Serviceguard Manager Version A.05.02 Release Notes