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

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)
What is the workaround? See JAGaf45963. All nodes that may be Session Server nodes, and all
nodes that may be discovered in a Serviceguard Session, must have each other's networks in
their /etc/hosts file. This includes private subnets.
JAGaf11256 Serviceguard Manager won't discover nodes if another cluster has the same name.
What is the problem? Once Serviceguard Manager discovers a cluster, it will ignore any others
that have the same name. For example, imagine that one subnet has a cluster clus1, whose
members are node1 and node2. Now imagine that another subnet has a cluster named clus1,
whose members are nodeX and nodeY. The situation is not common because Serviceguard insists
that the cluster name must be unique in its environment. Because the Session Server may have
different subnet access than either cluster does, it may be able to see clusters that cannot see each
other. If it does, it will display the first clus1 that it encounters during discovery, and ignore the
other.
What is the workaround? There is no workaround.
JAGaf09768 More than one config screen can be opened for one cluster.
What is the problem? Serviceguard Manager does not stop you from opening two configuration
screens at the same time. If you enter changes in both screens, thinking there is only one, you
may not apply the configuration that you expected.
What is the workaround? There is no workaround.
JAGaf08484 Null Pointer exception search string "ss" in help window (Javahelp bug).
What is the problem? If you enter a string of two or more s's (ss, sss, etc), in the Help Search window,
you get an error. This is a known defect in Javahelp. It causes a NullPointerException.
What is the workaround? There is no workaround.
Installing and Running Serviceguard Manager 45