HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 19: SAN Maintenance 255
cluster (for example, because the server has crashed) and you cannot
reboot the server. Run the command from a server that is communicating
with the cluster, not from the non-responsive server. If none of the servers
are responsive, try to execute the command from a client using the
Microsoft psexec utility.
mx server markdown <server>
The command informs HP Clustered File System that the server has been
verified to be down and does not need to be fenced, as it cannot threaten
filesystem integrity.
When HP Clustered File System cannot fence a server, an alert such as the
following will be displayed:
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.
The following example shows the operation of the command:
$ mx server markdown 99.10.20.4
This utility is used to verify that a server is down in the
event that it cannot be fenced and cannot be rebooted.
IMPORTANT: This utility must be run only after the server has
been physically verified to be down. If the server is not
down, running this utility could result in filesystem
corruption.
Do you wish to continue? y
SUCCESS 99.10.20.4 has been marked as down.
Cautions for Using mx server markdown
To avoid filesystem corruption when using the mx server markdown
command, it is important to follow these guidelines: