Serviceguard Manager Version A.04.00 Release Notes, June 2004

Serviceguard Manager Version A.04.00 Release Notes
Patches and Fixes in this Version
Chapter 1 51
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 named 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. However, the
Session Server 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.
JAGaf03220 User preferences saved in A.03.00 or A.03.01 are
ignored by A.04.00.
• What is the problem? Because of extensive changes to Serviceguard
Manager version A.04.00, preferences are not carried over from
version A.03.00.
• What is the workaround? There is no workaround.