3.1.2 Matrix Server Administration Guide

Chapter 18: SAN Maintenance 240

Server Cannot Be Located

If the matrix 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.

Also consult your FC switch documentation or the FC switch vendor. If

the switch appears to be operating properly, contact PolyServe Technical

Support.

Server Cannot Be Fenced

The following command can be used in situations where Matrix Server is

unable to fence a server that is not communicating with the matrix (for

example, because the server has crashed) and you cannot reboot the

server.

mx server markdown <server>

The command informs Matrix Server that the server has been verified to

be down and does not need to be fenced, as it cannot threaten filesystem

integrity.

When Matrix Server cannot fence a server, an alert such as the following

will be displayed:

Reboot <server> ASAP as it stopped matrix network

communication at date/time but attempts to exclude it

from the SAN were unsuccessful!

Rebooting it will allow normal matrix 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 matrix operation.