4.0.0 HP Polyserve Matrix Server Administration Guide (T5392-96052, March 2010)

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:
• Be sure to verify that the server is physically down or physically disconnected
from the shared storage before running the mx server markdown command.
Filesystem corruption can occur if the server is not actually down and can access
the shared storage.
• If the server is up but is physically disconnected from the shared storage when
the mx server markdown command is run, the server must be rebooted before
it is reconnected to shared storage. Failing to reboot the server before connecting
it to the storage can cause filesystem corruption.
If mx server markdown is run for a server that is up and in communication with
the cluster, the following message will be displayed:
Do you wish to continue? y
ERROR 99.10.20.3 is not down!
If the command is run for a server that is up but out of communication with the cluster
(for example, the server has lost network connectivity but has not been rebooted),
the mx server markdown command will succeed. However, if the server later
regains network connectivity to the cluster, an alert such as the following will be
displayed:
SAN maintenance258