
Chapter 3: mx Commands 105
information, see “Server Cannot Be Fenced” in Chapter 17 of the HP
StorageWorks Clustered File System Administration Guide.
CAUTION: 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 is the
server is not actually down and can access shared storage. Note
that if the server is left up but is physically disconnected from the
shared storage, it is critical that the server be rebooted before
reconnecting it to shared storage, or filesystem corruption can
occur.
read_license—Read the license file on a server
mx server read_license <server>
start—Start HP Clustered File System on one or more servers
mx server start <server> ...
This command can be used when the cluster is either running or offline.
status—Display server status
mx server status
[
--enabled
|
--disabled
] [
--up
|
--down
] [<
server
> ...]
stop—Stop HP Clustered File System on one or more servers
mx server stop <server> ...
This command can be used when the cluster is either running or offline.
update—Update one or more servers in a cluster
mx server update [--serverSeverity autorecover| noautorecover]
<server> ...
viewevents—View the events that have occurred on the server
mx server viewevents [--filter <string>] [--maxevents <number>]
[--timestamp <startTime,endTime>] [--noHeaders] [--csv]
[--showborder] <server>
This command can be used when the cluster is either running or offline. The
options are:
[--filter <string>]
Comentarios a estos manuales