PolyServe Command Reference PolyServe Matrix Server 3.5 File Serving Utility™ 3.5 Database Utility™ 3.5 for Red Hat Enterprise Linux AS/ES 4.
Copyright © 2004-2007 PolyServe, Inc. Use, reproduction and distribution of this document and the software it describes are subject to the terms of the software license agreement distributed with the product (“License Agreement”). Any use, reproduction, or distribution of this document or the described software not explicitly permitted pursuant to the License Agreement is strictly prohibited unless prior written permission from PolyServe has been received.
Contents Functional Cross Reference Administrative Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix 1 Matrix Server Commands destroypsfs – destroy a PSFS filesystem . . . . . . . . . . . . . . . . . . . . . . . . 1 diskupdate – reattempt to access a disk . . . . . . . . . . . . . . . . . . . . . . . . 2 dlmdebug – debug DLM problems . . . . . . . . . . . . . . . . . . . . . . .
Contents iv Setup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Repair Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Membership partition status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Repair Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 mxmpio – monitor or manage MPIO devices. . . . . . . . . . . . . . . . . . .
Contents v resizepsfs – resize a PSFS filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . 47 sandiskinfo – show SAN disk/LUN information . . . . . . . . . . . . . . . . 49 Disk information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Options for dynamic volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 setquota – set quotas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functional Cross Reference Administrative Commands Function Command Page Fencing Configure fencing mxsetfence 34 Configure the fence agent mxfencecfg 14 Verify the fencing configuration mxfence 13 Create a filesystem mkpsfs mx fs create 4 70 Destroy a filesystem destroypsfs 1 File locks, matrix-wide psfssema 45 Label a filesystem psfslabel 42 List volumes available for filesystem fs showcreateopt 71 Mount a filesystem mx fs mount 71 Recreate a filesystem mx fs recreate 71 Re
Functional Cross Reference Function vii Command Page Manage quotas psfsquota mx quota setquota 42 78 52 Report quotas for a filesystem repquota 47 Report quotas for users quota 47 Restore quota data psfsrq 44 Save quota data psfsdq 40 Warn users of quota limits warnquota 53 mxlogger 17 Applications, manage mx application 61 Assign or change passwords mxpasswd 29 Configure matrix mxconfig 10 Dump configuration information mx matrix dump 74 Start Performance Dashboard mx
Functional Cross Reference Function viii Command Page Save MxFS-Linux configuration mx exportgroup dump 69 Virtual NFS Service, manage mx vnfs 89 mx notifier 77 Start dashboard mx matrix dashboard 73 View dashboard for Export Group mx exportgroup dashboard 68 Disks, display information sandiskinfo 49 Disks, import into matrix mx disk import 65 Disks, remove from matrix mx disk deport 66 Disks, show status mx disk status 65 Dynamic volumes, display information sandiskinfo 49
Functional Cross Reference Function ix Command Page Users Passwords, assign or change mxpasswd 29 Quotas, manage edquota mx quota 2 78 Quotas, report for users quota 47 mx vhost 87 Virtual hosts Manage virtual hosts Diagnostic Commands Function Command Page Fencing Mark server that cannot be fenced as “down” mx server markdown 84 Test server-based fencing wmtest 53 Unfence ports on FC switches PSANcfg 35 Verify fencing configuration mxfence 13 Check and repair a filesystem p
Functional Cross Reference Function x Command Page Monitors Device monitor, clear event mx device clear 64 Service monitor, clear event mx service clear 86 mxnlmconfig 28 PSANinfo 36 FC switch, unfence ports PSANcfg 35 SAN disk information, display sandiskinfo 49 SAN ownership locks, display mxsanlk 31 Server access to SAN, check mxsancheck 30 Mark server as down mx server markdown 84 Matrix logs, collect for Technical Support mxcollect 10 Matrix Server processes, manage mx
1 Matrix Server Commands Matrix Server includes several commands that can be helpful for administrators managing a Matrix Server cluster. Other Matrix Server commands provide diagnostic information and should be used only under the direction of PolyServe personnel. Matrix Server also includes commands that are used internally and should not be run directly. The Matrix Server commands are located in the following directories: • /opt/polyserve/bin • /opt/polyserve/sbin • /opt/polyserve/tools • /etc/init.
Chapter 1: Matrix Server Commands 2 diskupdate – reattempt to access a disk Synopsis /opt/polyserve/tools/diskupdate Description This command should be run only at the request of PolyServe personnel. dlmdebug – debug DLM problems Synopsis /opt/polyserve/tools/dlmdebug Description This utility should be run only at the request of PolyServe personnel.
Chapter 1: Matrix Server Commands 3 fsprobe – report filesystem information Synopsis /opt/polyserve/tools/fsprobe Description This command should be run only at the request of PolyServe personnel. gcstat – print grpcommd statistics Synopsis /opt/polyserve/tools/gcstat Description This command should be run only at the request of PolyServe personnel.
Chapter 1: Matrix Server Commands 4 lcl-dump – show information about LCL locks Synopsis /opt/polyserve/tools/lcl-dump Description This command should be run only at the request of PolyServe personnel. log_collect – obtain log files Synopsis /opt/polyserve/tools/log_collect Description This command is used internally by the mxcollect utility and should not be run directly. mkpsfs – create a PSFS filesystem Synopsis /opt/polyserve/sbin/mkpsfs [-q] [-y] [-n ] [-l
Chapter 1: Matrix Server Commands 5 You do not need to specify the full path name. A name such as psd6p4 or psv1 will work. mkpsfs requires exclusive access to the device. If it cannot obtain exclusive access, it will exit with an “ebusy” message. The arguments are as follows: blockcount The number of blocks on the device. If this value is omitted, mkpsfs will determine it automatically. -q Quiet. -y Cause mkpsfs to answer yes to all questions.
Chapter 1: Matrix Server Commands 6 disable-fzbm Create the filesystem without Full Zone Bit Maps (FZBMs). The FZBM on-disk filesystem format reduces the amount of data that the filesystem needs to read when allocating a block. It is particularly useful for speeding up allocation times on large, relatively full filesystems. enable-quotas Enables quotas on the filesystem. userdefault= groupdefault= Set the default quota limit for users or groups, respectively, to size bytes.
Chapter 1: Matrix Server Commands 7 The options are: -F Send the data to the default membership partition backup file, /var/opt/polyserve/run/MP.backup. This file can subsequently be used as input to the mpimport utility if needed. If there is an existing backup file, that file will be saved as /var/opt/polyserve/run/MP.backup.prev. -f Send the data to the specified output file. -v Output the data to both the screen and the file.
Chapter 1: Matrix Server Commands 8 mpimport --local [ ...] Import the set of disks corresponding to the specified local disknames. mpimport -p Import the disk indicated by the UID and assign the specified psdname to it. mpimport -p --local Import the disk indicated by the specified local diskname and assign psdname to it. mpimport [-s] [-M] -F [|...] Import the specified psd or psv devices.
Chapter 1: Matrix Server Commands 9 mx – Matrix Server command-line interface The mx utility provides a command-line interface for administering a matrix and monitoring its operation. See Chapter 2 for more information about the commands provided with this utility.
Chapter 1: Matrix Server Commands 10 -i Regenerate index.html in /var/opt/polyserve/mxcheck. (Suppresses default sequence execution and report.) -r Remove all but the last 40 logged reports. (Does indexing, suppresses default text report. Without -l, suppresses default sequence.) -p Prompt for user input when necessary. Also disables timeouts for individual tests. -q Suppress progress messages. The available sequences are as follows: • install.
Chapter 1: Matrix Server Commands 11 Description The mxconfig utility performs the initial configuration of Matrix Server.
Chapter 1: Matrix Server Commands 12 --config Specifies the configuration file to be consulted for server, user, and password information. The file must have the same format as matrixrc. --user Specifies the user to be logged in. mxdb – perform MxDB-Oracle-HiAv operations Synopsis /opt/polyserve/mxdb_oracle_ha/bin/mxdb Description This command is used to invoke the MxDB-Oracle-HiAv GUI.
Chapter 1: Matrix Server Commands 13 -a ʺIP:IP:IPʺ Add servers to a Virtual Oracle Service. The option is a list of quoted, colon-delimited IP addresses. -m ʺIP:IP:IP:IPʺ Modify Virtual Oracle Service. The option is a quoted list of IP addresses that represent the Primary, 1st Backup, 2nd Backup, and so on. -C Clear events raised on a Virtual Oracle Service. Should a node crash, Matrix Server will raise events so that the DBA can take action before returning the Virtual Oracle Service to the failed node.
Chapter 1: Matrix Server Commands 14 mxfencecfg – configure the fence agent Synopsis /opt/polyserve/bin/mxfencecfg mxfencecfg -r|-s -v [-b ] -i -u -p Description The mxfencecfg command is used in conjunction with mxsetfence to configure flexible fencing without running mxconfig. The mxsetfence command is run first, as described under “mxsetfence – configure fencing” on page 34.
Chapter 1: Matrix Server Commands 15 -p Specify the password needed to access the remote controller.
Chapter 1: Matrix Server Commands 16 values. The file describes the available options and the required format. We recommend that you change this file only at the request of PolyServe personnel. The mxinit options are: -s, --start Start the Matrix Server processes. -x, --stop Gently stop the Matrix Server processes. mxinit first attempts to unmount PSFS filesystems. If the unmount fails, the gentle stop operation will also fail.
Chapter 1: Matrix Server Commands 17 -M, --no-monitor Explicitly tell mxinit not to monitor processes. --hba-status Display the state of the FibreChannel host bus adapter drivers. --status Display the status of Matrix Server processes and modules. Following is an example.
Chapter 1: Matrix Server Commands 18 Description You can use the mxlogger command to add your own messages to the matrix.log file. For example, you may want to add messages about the state of your applications. The arguments are: -h Print a help message. -e entity The type of message that you are adding. entity can be USER1, USER2, USER3, USER4, USER5, USER6, USER7, or USER8. You will need to determine how you want to use these entities. -l level The severity of the message.
Chapter 1: Matrix Server Commands 19 Description The mxmpconf utility starts an ASCII interface that can be used to create a new set of membership partitions or to repair the existing partitions Membership partitions control access to the SAN and store the device naming database, which includes the global device names for SAN disks imported into the matrix. Each server in the matrix has a membership partition file, which is called the “local MP list.
Chapter 1: Matrix Server Commands 20 INACCESSIBLE. The mxmpconf utility cannot access the device containing the membership partition. CORRUPT. The partition is not valid. MISMATCH. The membership partition is valid but its MP list does not match the server’s local MP list. If the status is NOT FOUND or INACCESSIBLE, there may be a problem with the disk or with another SAN component. When the problem is repaired, the status should return to OK. If the status is CORRUPT, you should resilver the partition.
Chapter 1: Matrix Server Commands 21 only if there are fewer than three membership partitions. All membership partitions must have a status of OK. Remove Remove an existing membership partition. This operation removes the membership data and formatting from the partition. It also deletes the partition from the local MP list and from the membership partition lists on the remaining membership partitions. Replace Remove an existing membership partition and then select a partition to replace it.
Chapter 1: Matrix Server Commands 22 mxmpio – monitor or manage MPIO devices Synopsis /opt/polyserve/sbin/mxmpio command [options...] [parameters ...] [PSD-devices ...] Description Matrix Server uses multipath I/O (MPIO) to eliminate single points of failure. A matrix can include multiple FibreChannel switches, multiple FC ports per server, and multiported SAN disks. This configuration provides multiple paths for I/O between servers and SAN disks.
Chapter 1: Matrix Server Commands 23 active [ ...] Set the active target on the specified device. mpiostat [-l] [ ...] List the number of transient errors for each target and show the number of failovers and fatal errors for each device. mpioload [-l] [interval [count]] [ ...] Shows the load for each target (SCSI command I/Os) and total for the PSD device (block layer I/Os), number of failovers, and fatal errors for each device. iostat [-u] [interval [count]] [ ...
Chapter 1: Matrix Server Commands 24 paths on a per-server basis across the cluster. This is possible because mxmpioʹs controls are server specific. You can use the following command to specify either a particular HBA or a PSD device. Matrix Server will then fail over the I/O to the path that includes the specified device. In the command, PSD-device is specified by the base name of the device path, such as psd2p1 (not /dev/psd/psd2p1).
Chapter 1: Matrix Server Commands psd2p1 enabled 10000 psd2p2 enabled 30000 25 1. (08:50) scsi1/0/1/20 0. (41:11) scsi2/0/1/20 1. (08:51) scsi1/0/1/20 (active) 0. (41:12) scsi2/0/1/20 (active) 1. (08:52) scsi1/0/1/20 Now use the mxmpio command to change the path for psd2p1 to target 0: # /opt/polyserve/sbin/mxmpio active 0 psd2p1 To verify the change, run the mxmpio status -l command again. In the following output, device psd2p1 is now active on target 0.
Chapter 1: Matrix Server Commands 26 Set the timeout value The default timeout period for PSD devices is 30 seconds. If you need to modify this value for a particular PSD device, use the following command. value is in milliseconds; however, the smallest unit is 10 milliseconds. A value of zero disables timeouts.
Chapter 1: Matrix Server Commands 27 interval is the number of seconds between samplings. The default is one second. count is the number of samples to make; the default is to sample indefinitely. The information displayed for each interval includes the number of I/Os queued (total block and raw), minimum and maximum latency, count of I/Os, and average latency. The statistics are organized by I/O, with only actively used sizes shown. Latencies are in milliseconds.
Chapter 1: Matrix Server Commands 28 7. First I/O size (power of 2) 8. Number of I/Os queued (includes raw) 9. Number of raw I/Os queued 10. Number of MP failovers 11. Number of MP fatal errors 12... Per-target I/O statistics in tuples, or groups of two numbers. (The number of targets is indicated in field 4.) Each tuple consists of the following fields for each target: • SCSI I/Os queued • Transient failures Note that the “SCSI I/Os queued” numbers are for the underlying disk, not the partition.
Chapter 1: Matrix Server Commands 29 Description This command is provided with MxFS-Linux. NLM is the locking protocol used by NFS. By default, it is disabled in MxFS-Linux. If necessary, NLM can be enabled; however, you should be aware of the following caveat: • File locks granted by the NFS server are cluster-coherent. When a failover occurs, the locks are released by the original server and the client automatically reclaims them on the new server (the backup node).
Chapter 1: Matrix Server Commands 30 Description To add a new Matrix Server user and password, use the following syntax, where user and password are enclosed in curly braces. You must be user root. # mxpasswd mxpasswd> {user}{password} To change an existing password, use the following syntax. Users can change their own passwords. If you are root, you can change any user password without specifying the old password.
Chapter 1: Matrix Server Commands 31 switches that will be managed by Matrix Server. The command creates or updates the files /etc/opt/polyserve/psSAN.cfg and /var/opt/polyserve/FCswitches. is either the name or IP address of a switch to be managed. All switches to be configured must be specified in the same command. The node must be unfenced when the command is run.
Chapter 1: Matrix Server Commands 32 # mxsanlk This host: 99.10.30.3 This host’s SDMP administrator: 99.10.30.1 Membership Partition -------------------/dev/rpsd/psd1p1 /dev/rpsd/psd2p1 /dev/rpsd/psd3p3 SANlock State ------------held by SDMP administrator held by SDMP administrator held by SDMP administrator Any of these messages can appear in the “SANlock State” column.
Chapter 1: Matrix Server Commands 33 sdmp process hung The SDMP process responsible for the SANlock is unresponsive. trying to lock, sdmp process hung The host on which mxsanlk was run is trying to acquire the SANlock but the SDMP process responsible for the SANlock is unresponsive. locked, sdmp process hung The host on which mxsanlk was run held the SANlock but the SDMP process responsible for the SANlock is now unresponsive.
Chapter 1: Matrix Server Commands 34 mxsetfence – configure fencing Synopsis /opt/polyserve/bin/mxsetfence Description The mxsetfence command is used in conjunction with the mxfencecfg command to configure flexible fencing without running mxconfig. The mxsetfence command is run first, and initializes the fence configuration file /etc/opt/polyserve/fence.conf.
Chapter 1: Matrix Server Commands 35 Description Matrix Server runs on each server in the matrix. When a server is booted to run-levels 3 or 5, Matrix Server is started automatically by the script /etc/init.d/pmxs. If you need to start, stop, or restart Matrix Server on a particular server, invoke the pmxs script with the appropriate argument. The pmxs script calls the mxinit utility. For a start operation, mxinit starts the Matrix Server processes in the correct order and loads the kernel modules.
Chapter 1: Matrix Server Commands 36 PSANinfo – show FC logins, Naming Database Synopsis /opt/polyserve/sbin/PSANinfo [-n] [-c ] [[-s]|[-u]] Description The PSANinfo command can be used to print the Naming Database or to get a snapshot of logins for a particular FibreChannel switch. The options are: -n Print the contents of the Naming Database. -c If the matrix uses a custom community string to access the FC switch, use this option to specify the string.
Chapter 1: Matrix Server Commands 37 psdctl – manage device bindings Synopsis /opt/polyserve/tools/psdctl Description This command should be run only at the request of PolyServe personnel.
Chapter 1: Matrix Server Commands 38 When psfsck is running in check mode (the default action), it will attempt to fix any corruptions that can be repaired without --rebuild-tree. The types of corruption that can be fixed include: bad pointers to data blocks, incorrect st_size and st_blocks in a directory, directory entries pointing to nowhere, incorrect file sizes and modes, and objectid sharing. NOTE: The psfsck utility requires exclusive access to the device.
Chapter 1: Matrix Server Commands 39 recommended that you run psfsck again in check mode, without the --no-modify option, before running with the --rebuild-tree option. The -no-modify option cannot be specified in addition to --rebuild-tree or --rebuild-sb. -a Cause psfsck to assume that it was called by psfsck -A and to return, even if the filesystem does not seem to be unmounted cleanly. -y Cause psfsck to answer “yes” to all questions.
Chapter 1: Matrix Server Commands 40 --set-gdq [T|G|M|K] Set the default quota for groups on the specified filesystem. The modifiers are the same as the set-udq option. (The default is rounded down to the nearest filesystem block.) psfsdebug – get PSFS filesystem image Synopsis /opt/polyserve/tools/psfsdebug Description This command should be used only under the direction of PolyServe personnel.
Chapter 1: Matrix Server Commands 41 psfsinfo – report filesystem information Synopsis /opt/polyserve/tools/psfsinfo [--feature ] [--version] [--blocksize] [--verbose] ... Description The psfsinfo command reports information about the filesystem. With no options, the information includes the size of the filesystem, the block size, the version of the filesystem, and whether the disk quota or Full Zone Bit Map features are enabled.
Chapter 1: Matrix Server Commands 42 This option also reports the exit value: 0 – enabled 1 – not enabled 2 – could not open or read disk 3 – a bad argument was specified --version Display the version of the on-disk filesystem format. --blocksize Display only the block size used by the filesystem. --verbose, -v Enable verbose messages. psfslabel – label a PSFS filesystem Synopsis /opt/polyserve/bin/psfslabel “
Chapter 1: Matrix Server Commands 43 • For a non-partitioned psd device, the device is specified as /dev/psd/psdXXX, where XXX is the drive number. For example, /dev/psd/psd5. • For a psv device, the device is specified as /dev/psv/psvXXX, where XXX is the volume number. For example, /dev/psv/psv1. You do not need to specify the full path name. A name such as psd6p4 or psv1 will work. The options are: --enable-quotas Build the necessary quota infrastructure on the specified filesystem.
Chapter 1: Matrix Server Commands 44 psfsresume – resume a suspended PSFS filesystem Synopsis /opt/polyserve/tools/psfsresume Description The psfssuspend and psfsresume utilities affect the specified filesystem on all servers where it is mounted; however, the utilities should be executed on only one server in the matrix. When you have completed your work with the suspended filesystem, use the psfsresume utility to resume the filesystem.
Chapter 1: Matrix Server Commands 45 psfssema – manage matrix-wide file locks Synopsis /opt/polyserve/bin/psfssema /opt/polyserve/bin/psfssema /opt/polyserve/bin/psfssema /opt/polyserve/bin/psfssema -i -g -r -d Description The psfssema semaphore utility provides a simple synchronization mechanism for managing matrix-wide file locks.
Chapter 1: Matrix Server Commands 46 psfssuspend – suspend a PSFS filesystem Synopsis /opt/polyserve/tools/psfssuspend Description The psfssuspend utility suspends a PSFS filesystem in a stable, coherent, and unchanging state. While the filesystem is in this state, you can copy it for backup and/or archival purposes. When copying directly from a suspended device, be sure to use the raw device (/dev/rpsd/...) to ensure that all blocks copied are up-to-date.
Chapter 1: Matrix Server Commands 47 Description This command should be used only under the direction of PolyServe personnel. quota – report quota information for a user Synopsis /opt/polyserve/bin/quota Description This command is based on the Linux quota command but has been modified to work with PSFS filesystems as well as the standard Linux filesystem types. The command is provided on the Matrix Server quota tools RPM. There are no changes to the syntax or operation of the command.
Chapter 1: Matrix Server Commands 48 is invoked. Otherwise, the filesystem must be unmounted on all servers before it is resized. The utility can be used with either psd or psv devices. Use this syntax to specify the device: • For a psd device partition, the device is specified as /dev/psd/psdXXXpYY, where XXX is the drive number and YY is the partition number. For example, /dev/psd/psd6p4 specifies partition 4 on disk psd6.
Chapter 1: Matrix Server Commands 49 -s [+]size[K|M|G|T] The following example increases the size of the filesystem by 1 GB. resizepsfs -s +1G /dev/psd/psd6p4 sandiskinfo – show SAN disk/LUN information Synopsis /opt/polyserve/bin/sandiskinfo [-i|-u|-v|-f] [-alr] [-U] [-q] [--subdevices] [--dynvolumes] [--dynvol_properties [volname]] Description The sandiskinfo command can display information for both imported and unimported SAN disks (or LUNs) and also for dynamic volumes.
Chapter 1: Matrix Server Commands 50 -U Display output in the format used by the Management Console. This option is used internally by Matrix Server and does not produce human-readable output. -q Suppress output of all log messages. Following are some examples of these options. Show partition information The -a option also lists the partitions on each disk. When combined with -u, it displays partition information for unimported disks.
Chapter 1: Matrix Server Commands 51 Show available volumes The -v option lists available volumes on imported disks. These volumes are not currently in use for a PSFS filesystem or a membership partition. # sandiskinfo -v Volume: /dev/psd/psd5p1 Size: 3905M Disk=20:00:00:04:cf:13:32:d1::0 partition=01 type=Linux (83) Volume: /dev/psd/psd5p2 Size: 7386M Disk=20:00:00:04:cf:13:32:d1::0 partition=01 type=Linux (83) Options for dynamic volumes The following sandiskinfo options apply only to dynamic volumes.
Chapter 1: Matrix Server Commands 52 Subdevice: 20:00:00:04:cf:13:38:18::0/5 Size: 490M psd1p5 Subdevice: 20:00:00:04:cf:13:38:18::0/2 Size: 1950M psd1p2 Dynamic Volume: psv2 Size: 490M Stripe=32K/optimal Subdevice: 20:00:00:04:cf:13:38:18::0/7 Size: 490M psd1p7 Dynamic Volume: psv3 Size: 490M Stripe=8K/optimal Subdevice: 20:00:00:04:cf:13:38:18::0/10 Size: 490M psd1p10 setquota – set quotas Synopsis /opt/polyserve/sbin/setquota Description This command is based on the Linux setquota command but has bee
Chapter 1: Matrix Server Commands 53 spdebug – obtain SanPulse debug information Synopsis /opt/polyserve/tools/spdebug Description This command should be run only at the request of PolyServe personnel. spstat – show matrix state information Synopsis /opt/polyserve/tools/spstat Description This command should be run only at the request of PolyServe personnel.
Chapter 1: Matrix Server Commands 54 Valid brands: demo, dell, hp, ibm, ipmi Valid blades: 1-14; 0 for non-BladeCenter Valid commands: status, on, off NOTE: Do not run this command from the server that you are trying to power on, power off, or reset. Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
2 mx Commands The mx utility provides a command-line interface for administering a matrix and monitoring its operation. The matrixrc file Matrix Server can use an optional, external configuration file named .matrixrc to provide authentication information for matrix connections. If the file is configured, it will be used when you connect to a matrix through either the Matrix Server Connect window or the mx command.
Chapter 2: mx Commands 56 The entries in the matrixrc file have this format: machine user password default • The first field, machine, is either the name or IP address of the server. • The second field, user, is optional. It is the name of a user on that server, either admin for the administrator or another name for a read-only user. • The third field is also optional and contains the Matrix Server password for that user.
Chapter 2: mx Commands 57 When you issue a mx command without specifying a server name, as in the following example, it connects to the machine specified as the default in the .matrixrc file. mx server status To connect to a different server, include the --matrix option and specify the server name on the command line. For example, the following command connects to server acme1 as user admin using the password secret1. mx --matrix srv1 server status Use wildcards You can use wildcards in the .
Chapter 2: mx Commands 58 To connect to the matrix, include the option --matrix prod in the mx command. mx first attempts to access srv3, the default. If that server is not available, the command tries the other servers in the group. If your servers mostly use the same username and password, to simplify configuring the .matrixrc file, you can specify those values following the cluster name. You then only need to specify the values if they are different for a particular server.
Chapter 2: mx Commands 59 --matrix Specifies the matrix that you want to connect with. matrix can be any node in the matrix. --config Specifies the configuration file to be consulted for server, user, and password information. The file must have the same format as matrixrc. --file Executes the commands from the specified file. If you specify – instead of a file, the commands will be read from standard input.
Chapter 2: mx Commands 60 Class syntax The mx utility can manipulate the following classes of matrix objects.
Chapter 2: mx Commands 61 mx application – manage applications Use the following commands to manage Matrix Server applications: Rename an application: mx application rename Enable an application: mx application enable Disable an application: mx application disable Show status for an application: mx application status [--severity OK|WARNING|ERROR] [ ...
Chapter 2: mx Commands 62 [--frequency ] The interval at which the monitor probes the device. For DISK and SHARED_FILESYSTEM device monitors, the default is 30 seconds. For CUSTOM device monitors, the default is 60 seconds. [--probeSeverity nofailover|autorecover|noautorecover] The failover behavior for the monitor: With NOFAILOVER, when the monitor probe fails, the virtual host does not fail over. With AUTORECOVER, the virtual host fails over when a monitor probe fails.
Chapter 2: mx Commands 63 [--recoveryScript
