Serviceguard Manager Version A.05.01 Release Notes, February 2007

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