Serviceguard Manager Version A.04.02 Release Notes, February 2005

Serviceguard Manager Version A.04.02 Release Notes
Patches and Fixes in this Version
Chapter 156
• 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.
JAGaf14625 Problems creating and modifying packages that
contain non-alphanumeric characters (,*,$,#, ...).
• What is the problem? All alphanumeric characters are accepted as
package names. However, you cannot use most of the other
characters on a keyboard. (For the exact list, see the Help topic for
Configuring Packages.)
The packages appear to be added. However, if you select one in the
tree or map, you will get a connection error. You will also get an error
if you try to open the properties for the package or its cluster.
• What is the workaround? In package names, do not use any of the
special characters listed. If you have an existing package with these
special characters, you will not be able to configure it through
Serviceguard Manager unless you change its name.
JAGaf14600 Package and property sheets show non-configured
cluster monitored subnets. (fixed in Serviceguard Manager
A.04.02)
• What is the problem? This happens if a node in the cluster has a lan
card that has more than one IP address, and the addresses are for
different subnets. If the subnet of one of the IP addresses is specified
as monitored, both subnets may show up in the list of monitored
subnets. This is especially likely with IPv6 addresses.
• What is the workaround? There is no workaround.
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 client Java Web Start uses the old jar files.
• What is the workaround? There are two workarounds: