Serviceguard Manager Version A.05.00 Release Notes, October 2005

Serviceguard Manager Version A.05.00 Release Notes
Patches and Fixes in this Version
Chapter 152
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.
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.