Cannot Add A New Node Into Existing Cluster From New Node; Cluster Reference Fails When Using The Cluster Name To Access Cluster Administrator On The Local Node; Cluster Node Eviction Occasionally Fails - HP StorageWorks 4000s - NAS Release Note

Cannot add a new node into existing cluster from new
node
In a cluster already up and running, if an attempt is made to add
a new node from the server which is not a existing member, the
action will fail and a message will be displayed The cluster
service on new node can not be started. The
only way to add new node in a cluster is to add it from a node
that is already a member of the cluster.
Cluster reference fails when using the cluster name to
access cluster administrator on the local node
When using cluster administrator to administer the local cluster,
the use of the cluster name will fail to access the cluster. Use of
the "." is an acceptable workaround in the connect field of
cluster administrator. Alternatively, one may use any node
member's host name to connect to the cluster through cluster
administrator.

Cluster node eviction occasionally fails

When attempting the eviction of a cluster node, intermittent
failures can occur in the eviction process and the cluster will
report the node evicted. However, the node being evicted will
retain its cluster information and reformation of the node into the
cluster is blocked. This is especially true when the node being
evicted was turned off when the eviction process occurred. In
these circumstances, a forced cleanup of the node is required via
the following command line procedure prior to the reforming of
the cluster:
cluster node nodename /forcecleanup
On occasion this command will fail also and a registry entry is
required for the cluster cleanup. To create a place holder, type
the following line at the command line:
sc create clussvc
18 HP StorageWorks NAS 4000s and 9000s Release Notes