Serviceguard Manager Version A.05.02 Release Notes, 2nd Edition, May 2009

JAGaf43912 Cluster Properties: wrong lock info in older version of COM
What was the problem? Versions of COM older than B.03.01 may display wrong information about
the HP-UX cluster lock, because it may not support discovery of a Lock LUN. The COM (Cluster
Object Manager) is a component of Serviceguard.
What is the workaround? If you are using Lock LUN in a Linux cluster, upgrade COM to version
B.03.01 or later. The COM (Cluster Object Manager) is a component of Serviceguard. For more
information, see the documentation at http://docs.hp.com/hpux/ha -> Serviceguard.
JAGaf64743 Help: Problem entering Locale ko chars in index of online help viewer
What is the problem? Entering ko (Korean) characters into the index of online help can cause the
help window to hang.
What is the workaround? There is no workaround.
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.
Installing and Running Serviceguard Manager 41