HP StorageWorks Clustered File System 3.6.1 Windows Storage Server Edition event notification guide (AG515 - 96011, August 2008)

Chapter 3: Event Messages 30

13905 Reboot <server> ASAP as it stopped cluster network communication at

date/time but attempts to exclude it from the SAN were unsuccessful!

Rebooting it will allow normal cluster operation to continue. Alternatively, if

the server cannot be rebooted, but can be confirmed to have no access to the

SAN, run ‘mx server markdown <server>' to restore normal cluster

operation.

Action. HP Clustered File System cannot fence a server that is no longer

communicating with the cluster. Either reboot the server or run the mx

server markdown command to restore normal operations. Before using mx

server markdown, be sure that the server is physically down. If the

command is run on a server that is not down, filesystem corruption can

occur. See “Server Cannot Be Fenced” in the HP StorageWorks Clustered File

System Administration Guide for more information about the mx server

markdown command.

13906 Server <server> fencing failure resolved.

Action. None. Alert 13905 is resolved.

13907 Reboot <server> ASAP! It is no longer in communication with the cluster,

and may be dirty, but attempts to exclude it from the SAN were

unsuccessful. Rebooting it will allow normal cluster operation to continue.

Alternatively, if the server cannot be rebooted, but can be confirmed to have

no access to the SAN, run ‘mx server markdown <server>' to restore normal

cluster operation.