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

Chapter 19: SAN Maintenance 256
• 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 called for a server that is up and in
communication with the cluster, the following message will be displayed
when you run the command:
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.
Operator error may have caused filesystem corruption!
99.10.20.4 returned to the cluster without being rebooted,
even though the operator verified that 99.10.20.4 was down.
It is recommended that all filesystems that 99.10.20.4 had
mounted be checked for corruption. This alert will display
for 48 hours.
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.
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.