HP StorageWorks Clustered File System 3.2.1 Windows Storage Server Edition Administration Guide (February 2006)

Appendix B: Error and Event Log Messages 191
Fencing operation failed, reboot NN.NN.NN.NN ASAP.
NN.NN.NN.NN stopped cluster communication DATE HH:MM but
cannot be excluded from the cluster because of a networking
or fencing hardware failure or misconfiguration. To protect
filesystem integrity, some or all filesystem operations may
be paused until NN.NN.NN.NN is rebooted or until fencing
operations can be performed.
The server is unresponsive but HP Clustered File System is unable to
exclude it from the cluster because the fencing device is not responding to
the fencing request. Possibly the Ethernet connection to the FibreChannel
switch has failed. The server should be rebooted as soon as possible.
Internal error: unable to initialize security
Internal error: unable to initialize security. Java program
problem. Contact service.
If you receive one of these messages, report it to HP Technical Support at
your earliest opportunity.
Majority of membership partitions are unwritable, possibly
due to a SAN or storage hardware failure. As a result, disk
imports and deports cannot be done, and some servers may be
unable to mount filesystems.
In addition, HP Clustered File System’s ability to recover
from a future server failure is compromised. Such a failure
would leave HP Clustered File System no option but to pause
some or all filesystems throughout the cluster to preserve
filesystem integrity.
The servers in the cluster cannot write to the majority of the membership
partitions. Ensure that the servers can access the membership partitions
and have write access to them. If the disks containing the membership
partitions have failed, you will need to recreate the partitions. (See
“Manage Membership Partitions with mprepair” on page 160 for more
information.)