3.7.0 HP StorageWorks HP Scalable NAS File Serving Software event notification guide HP Scalable NAS for Linux (AG513-96007, June 2009)

Message and Corrective ActionID
Server <server> was unfenced.
Action. None. Alert 13901 is resolved.
13902
<server> should be rebooted ASAP as it was excluded from the SAN to protect
filesystem integrity.
Action. The server was excluded from the cluster because it could no longer
communicate over the network. The server should be rebooted at the first
opportunity. Also check the network and make sure that the server is not
experiencing a resource shortage.
13903
Server <server> was unfenced.
Action. None. Alert 13903 is resolved.
13904
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 Scalable NAS 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 Scalable NAS File Serving Software administration guide for more
information about the mx server markdown command.
13905
Server <server> fencing failure resolved.
Action. None. Alert 13905 is resolved.
13906
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.
Action. HP Scalable NAS 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 Scalable NAS File Serving Software administration guide for more
information about the mx server markdown command.
13907
Event messages30