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

What is the workaround? The assertion error will create a log dialog window. You can click the
continue button, and resume if this problem is encountered
JAGaf32042 Standby LANs config does not work properly (See also JAGae87650)
What is the problem? In the Serviceguard Manager A.04.00 and A.04.02 Cluster Configuration
screens, once you deselect a standby interface, it will not allow you to reselect that standby
interface.
What is the workaround? There is no workaround.
JAGaf17035 Some accessibility short-cut keys do not work in non-English locale.
What is the problem? Some accessibility short-cut keys do not work in traditional Chinese, simplified
Chinese, Korean, or Japanese.
What is the workaround? There is no workaround. If you require short-cut keys, install the English
version.
JAGaf16670 - Startup issues with Java Webstart
What is the problem? There are two problems:
First: With non-Windows systems running Mozilla, you have to manually register Webstart
as a helper application.
Second: When updating Serviceguard Manager on the client side, the SIM (Systems Insight
Manager) client Java Web Start uses the old .jar files.
What is the workaround? There are two workarounds:
First: With non-Windows systems running Mozilla, go to the browser menu and select
Preferences -> Navigator -> Helper App. For the settingField Value, put the following:
extension jnlp mime type application/x-java-jnlp-file handled by
application <patch-to-javaws>/javaws.exefont=symbol charset=fontspecific
code=183 descr='[bull]'
Second: When updating, you need to manually clear the Java Web Start cache on the SIM
client side. It contains the .jar files downloaded from the server. Before installing the new
Serviceguard Manager, clear the cache and the server will automatically download the new
.jar files.
JAGaf15152 Package with all nodes (*) causes problem when adding node to cluster.
What is the problem? If a configuration uses a wild card (*) to set node membership to all nodes,
you will have trouble adding a new node to the cluster.
What is the workaround? On the package configuration screen, remove the "all nodes" star wildcard.
Select all the nodes in the list, adding them one at a time. Then add the new node. Be sure the
configuration and control script are added to the new node before you do any more changes.
JAGaf14041 Connection error if IP Address of node can not be found
What is the problem? You will get an error if you try to view a cluster that does not have an entry
in your COM's /etc/hosts file. The following is an example of an error:
7836: Failed
to get storage information: Warning: Unable to determine an IP address
for epic15: 1. Error: Node chooyu is refusing Serviceguard communication.
Please make sure that the proper security access is configured on
node chooyu through either file-based access (pre-A.11.16 version)
or role-based access (version A.11.16 or higher) and/or that the host
name lookup on node chooyu resolves the IP address correctly. Failed
to gather configuration information. 7836: Syntax error in SQL query
"select containeeId as id from SGClusterVolumeGroupContainment where
containerId = "SGCluster:1078858874"" (result clause)
Installing and Running Serviceguard Manager 43