3.7.0 HP StorageWorks HP Scalable NAS File Serving Software administration guide - HP Scalable NAS 3.7 for Linux (AG513-96002, October 2009)

7. Verify the fencing configuration as described in the HP Scalable NAS File Serving
Software installation guide.
Server cannot be located
If the cluster reports that it cannot locate a server on the SAN but you know that the
server is connected, there may be an FC switch problem.
For example, on a Brocade FC switch, log into the switch and verify that all F-Port
and L-Port IDs specified in switchshow also appear in the local nameserver,
nsshow. If the lists of ports are different, reboot the switch. If the reboot does not
clear the problem, there may be a problem with the switch.
Also consult your FC switch documentation or the FC switch vendor. If the switch
appears to be operating properly, contact HP Technical Support.
Server cannot be fenced
The following command can be used in situations where HP Scalable NAS is unable
to fence a server that is not communicating with the cluster (for example, because
the server has crashed) and you cannot reboot the server.
mx server markdown <server>
The command informs HP Scalable NAS that the server has been verified to be down
and does not need to be fenced, as it cannot threaten filesystem integrity.
When HP Scalable NAS 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
SAN maintenance372