HP StorageWorks PolyServe Software command reference guide HP PolyServe Software 4.0.
Legal and notice information © Copyright 2004, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Functional cross reference ................................................... 7 Administrative commands ..................................................................................... 7 Diagnostic commands ........................................................................................ 11 2 Cluster commands ........................................................... 13 Overview ........................................................................................................
View membership partitions and their status ................................................... Active and inactive membership partitions ............................................... Sizes for membership partitions .............................................................. Export configuration changes ................................................................. mprepair options .................................................................................. msmtool.
registry.exe – dump registry contents .................................................................... sandiskinfo.exe – show SAN disk/LUN information ................................................ Disk information ......................................................................................... Show partition information .................................................................... Show local device information ...............................................................
mx mx mx mx mx mx mx mx mx disk – disk commands ................................................................................... 84 dynvolume – dynamic volume commands ........................................................ 85 eventnotifier – event notification commands ...................................................... 87 fs – filesystem commands ............................................................................... 92 matrix – cluster commands ............................................
1 Functional cross reference Administrative commands Function Command CIFS Manage Matrix File Shares mx mfs Manage Virtual CIFS Servers mx vfs Manage Virtual File Shares mx vfs_share Cluster Configuration, initial mx config Configuration, membership partitions mx config mp Configuration, snapshot method mx config snapshot Dump configuration information mx matrix dump Verify cluster requirements on server mxcheck Event notification services and event log Add a message to the event log mx m
Function Command Destroy a filesystem destroypsfs Label a filesystem psfslabel List volumes available for filesystem mx fs showcreateopt Manage drive letters/paths mx fs Recreate a filesystem mx fs recreate Report filesystem information psfsinfo Report volume information sandiskinfo Resume a suspended filesystem psfsresume Suspend a filesystem for backups psfssuspend Filesystem quotas Edit user and group quotas edquota Manage quotas psfsquota, mx quota setquota Report quotas for a fi
Function Command Save membership partition data mpdump Restore mxds datastore mpimport -X Save mxds datastore mpdump -X Monitors Device monitor, manage mx device Service monitor, manage mx service Quotas Manage quotas psfsquota, mx quota Restore quota data psfsrq Save quota data psfsdq Role-Based Security Manage operating system accounts that belong to management roles mx account Manage roles for cluster operations mx role SAN Disks, display information sandiskinfo Disks, import into
Function Command Naming database, display PSANinfo Servers Add, update, enable, or disable server mx server License file, read mx server read_license Cluster event file, add message mx matrix log Verify matrix requirements mxcheck Snapshots Create snapshot mx snapshot create Destroy snapshot mx snapshot destroy Snapshot options, display mx snapshot showcreateopt SQL Server Install SQL instances mx mni Manage Virtual MSDTCs mx vmsdtc Manage Virtual MSDTC services mx vmsdtc_service Man
Function Command Virtual hosts Manage virtual hosts mx vhost Volumes Back up a dynamic volume mx dynvolume export Manage dynamic volume mx dynvolume Recover a dynamic volume mx dynvolume import Diagnostic commands Function Command Configuration Check status of matrix components mx config list, mpconfig mp list Test fencing configuration mx config testfencing Fencing Mark server that cannot be fenced as “down” mx server markdown Unfence ports on FC switches PSANcfg Filesystem Check and re
Function Command Cluster requirements, verify on server mxcheck Restore configuration from dump file mx --file Membership partitions Create or repair membership partitions mprepair, mx config mp Restore membership partition data mpimport Restore mxds datastore mpimport -X Monitors Device monitor, clear event mx device clear Service monitor, clear event mx service clear SAN FC logins, display PSANinfo FC switch, unfence ports PSANcfg SAN disk information, display sandiskinfo
2 Cluster commands Overview HP PolyServe Matrix Server includes several commands that can be helpful for administrators managing a Matrix Server cluster. Other commands provide diagnostic information and should be used only under the direction of HP personnel. Certain other commands are used internally and should not be run directly. The commands are located in the following directories: • %SystemDrive%\Program Files\Polyserve\MatrixServer\bin • %SystemDrive%\Program Files\Polyserve\MatrixServer\tools .
administration. Other commands are used internally by Matrix Server or should be run only at the request of HP personnel when diagnosing issues on your system. NOTE: Commands not documented in this chapter are Matrix Server processes, commands used internally by Matrix Server, or commands for use by HP personnel. Permissions for Matrix Server binary files By default, the machine local Administrators group has full cluster rights and can run all Matrix Server binaries.
Description This command forces a system reboot when certain error conditions exist during Matrix Server startup. It is used internally by Matrix Server and should never be run directly. diskupdate.exe – reattempt to access a disk Synopsis bin\diskupdate Description This command should be run only at the request of HP personnel. dismount.exe – dismount a PSFS filesystem Synopsis bin\dismount Description This command should be run only at the request of HP personnel. dledit.
Description This utility should be run only at the request of HP personnel. eventlog.exe – dump the contents of the event log Synopsis tools\eventlog Description This command is used internally by the mxcollect utility and should not be run directly. fsprobe.exe – report filesystem information Synopsis tools\fsprobe Description This command should be run only at the request of HP personnel. gcstat.
hbaapidump.exe – display LUN information Synopsis tools\hbaapidump Description This tool displays information about the LUNs seen by the HBA drivers and can be used to verify that the HBA libraries are working correctly. hn2ip.exe – determine a server's IP address Synopsis bin\hn2ip Description This command determines a server’s IP address based on its hostname. The command is used internally during matrix configuration and should not be run directly. idfence.
makescldb.exe – create membership partitions Synopsis bin\makescldb Description This command is used internally by Matrix Server and should not be run directly. (To create membership partitions, use the “Configure Matrix” feature on the PolyServe Management Console.) mcs.exe – manipulate the cluster log This utility provides several commands that are used internally by Matrix Server; however the following commands may be useful when administering a matrix.
Description This command can be used to display events from the cluster event log on the local server. The options are: -b Display the output in XML format. -c Do not display column headings in the output. -h [] Display the specified number of events, starting at the beginning of the log. If is omitted, all matching events will be displayed. (If -t is also specified, it will not have any effect.) -h --count Display the number of matching events but not the events themselves.
message The text provided with the logged event. postedtime The time the event was stored on the local node. processid The process ID of the process logging the event. severity The severity level such as Alert or Critical. source The component that generated the message. subject The object to which the event relates. subjecttype The description of the subject. subjecttypeid The ID assigned to the subject. subjecttypename Used to identify the object to programs.
Event fields. The filter event fields are: postedtime The time the event was stored on the local node. The time must be specified as YYYY-MM-DDTHH:NN:SS. The year (YYYY) is the only required element. The month (MM), day (DD), hour (HH), minute (NN) and second (SS) must be two digits in length and can include a leading zero (for example, 200711-12T08:01:59.) If a time is specified, the month and day must also be specified. If a time or date element is not specified, it is assumed to be zero.
> Test if a filter event field is greater. Syntactical elements. Expressions can be enclosed in parentheses “( )” and can contain AND and OR operations, which use the syntax && and || respectively. AND and OR operations can be used only to connect filter event subtypes, filter event fields, and parenthesized statements. Logical negation is also allowed using the ! character.
Description The mpdump utility backs up the membership partition data to a file and/or the screen. When mpdump is run with no options, the data is output to the screen. The options are: -F Send the data to the default membership partition backup file, which is located by default at %SystemDrive%\Program Files\Polyserve\matrixserver\conf\MP.backup{.prev}. 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 MP.backup.
NOTE: Matrix Server must be stopped on all nodes when mpimport is used. Database corruption can occur if the utility is executed while Matrix Server is running on a node. mpimport fails if Matrix Server is running on the current node; however, it does not check the other nodes. mpimport does not check for the physical presence of the disks or subdevices that it is importing and, for example, allows the devices to be imported even if they are not physically visible on the server.
recreates the membership partitions from scratch based on the contents of the input file. mpimport -r | [| ...] Remove the specified disks or dynamic volumes from the existing database. mpimport --replace Replace all occurrences of olduid with newuid throughout the membership partition data. mpimport -X Restore the mxds datastore on the membership partitions using the default backup file (MPmxds.backup).
disk containing a membership partition also has its own list of the membership partitions. Under normal operations, these lists should all match. The output from --get_current_mps contains a record for each membership partition. Following is a sample record. 20:00:00:04:cf:13:33:12::0/1 OK 8001Kb active The first field contains the disk UUID followed by a slash and the partition number (partition 1 in the above example). The second field reports the status of the membership partition.
Active and inactive membership partitions A membership partition can be either active or inactive. (This attribute is reported in the last field of the record displayed by the mprepair --get_current_mps command.) The current membership partitions should all be active. If there are old membership partitions in the matrix, you may want to either remove them or mark them as inactive.
mprepair options Matrix Server can operate with either one membership partition or three membership partitions. To ensure that a membership partition is always available, we recommend that you use three membership partitions. Display Membership Partitions. To display information about membership partitions, type the following command: mprepair --display_mplists The output shows the local membership partition list on the server where you are running mprepair.
partitions. Resilvering takes place automatically when a change is made to the device naming database or when you add, remove, or replace a membership partition. However, in certain situations you may need to perform the resilver operation manually. For example, a membership partition might become corrupt or a local membership list might become out of date. The --resilver operation requires that you specify a good membership partition. The other membership partitions are then resilvered from that partition.
UID is the UID for the device and PART# is the partition number. This option is useful if the matrix includes old membership partitions that are marked active or if you want to import a disk that contains an active membership partition. Clear the Host Registry. The --clear_hr option removes all entries from the server registry. This command should be used only under the direction of HP Support. Reset the Cluster ID.
mxcheck.exe – verify cluster requirements Synopsis bin\mxcheck Description The mxcheck utility verifies that a server meets the configuration requirements for Matrix Server. It is run automatically each time Matrix Server is started. You can also run mxcheck manually. The utility performs the following checks on the server: • System check: hardware, operating system version, service pack version, available physical memory.
mxconsole.exe – start the PolyServe Management Console Synopsis bin\mxconsole Description The mxconsole command starts the PolyServe Management Console, which is used to configure and monitor the matrix. The Management Console can be run from either a matrix server or a local machine outside the matrix. (See the HP PolyServe Matrix Server administration guide for information about using the Management Console.) mxgenpass.
mxsanconf.exe – configure FC switches Synopsis bin\mxsanconf Description In general, this command should not be run directly. If a matrix is configured to use fabric fencing, the mxsanconf command must be successfully run on each node before Matrix Server is started. The command configures the list of FibreChannel switches that will be managed by Matrix Server and creates or updates the files psSAN.cfg and FCswitches in the directory %SystemDrive%Program Files\PolyServe\MatrixServer\conf.
# mxsanlk This host: 99.10.30.3 This host’s SDMP administrator: 99.10.30.1 Membership Partition -------------------psd1p1 psd2p1 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. held by SDMP administrator The SANlock was most recently held by the SDMP administrator of the cluster to which the host where mxsanlk was run belongs. trying to lock, last held by host X.X.X.
The host on which mxsanlk was run held the SANlock but the SDMP process responsible for the SANlock is now unresponsive. lock is corrupt, will repair This transitional state occurs after the SDMP has detected that the SANlock has been corrupted but before it has repaired the SANlock. trying to lock (lock is corrupt, will repair) The host on which mxsanlk was run is trying to acquire the SANlock. The SANlock was corrupted but will be repaired.
mxsetsecret.exe – set the network secret password Synopsis bin\mxsetsecret This command is used during matrix configuration and should be run manually only at the request of HP personnel. mxstart.exe – start Matrix Server processes Synopsis bin\mxstart Description This command is used internally by Matrix Server and should never be run directly. mxstop.exe – start Matrix Server processes Synopsis bin\mxstop Description This command is used internally by Matrix Server and should never be run directly.
pathfilter.exe – translate the install path Synopsis bin\partresize Description This command is used by the Matrix Server install process and should never be run directly. PSANcfg.exe – control port operations Synopsis /opt/hpcfs/sbin/PSANcfg [-hu] [-[lL] ] [switch ...] Description The PSANcfg command can be used to add or remove local HBA port information in the Matrix Server configuration and to unfence ports on FibreChannel switches.
The options are: -n Print the contents of the Naming Database. -c If the cluster uses a custom community string to access the FC switch, use this option to specify the string. The PSANinfo command will fail if this option is not specified for configurations using a custom community string. -s Wait seconds between probes of the FC switch. -u Wait microseconds between probes of the FC switch. If no options are specified, PSANinfo displays the status of the switch one time only.
psdctl – display device bindings Synopsis /opt/hpcfs/tools/psdctl Description This command should be run only at the request of HP personnel. psfscheck – check or repair a PSFS filesystem Synopsis bin\psfscheck [options] device Description The psfscheck utility looks for a PSFS filesystem on a device, replays transactions that are to be replayed, and either checks or repairs the filesystem.
NOTE: The psfscheck utility requires exclusive access to the device. If it cannot obtain exclusive access, it will forcibly dismount the volume The options for checking a filesystem are: --rebuild-tree Rebuild the filesystem tree using leaf nodes found on the device. Normally you should use this option only if psfscheck reports errors that can be fixed only by --rebuild-tree.
-y Cause psfscheck to answer “yes” to all questions. Enable or disable FZBMs The psfscheck utility also provides options to enable or disable Full Zone Bit Maps (FZBMs). This 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. For details about FZBM, see the article “Using the FZBM On-Disk Filesystem Format” on hp.com.
Disable the creation of 8.3 file names and name tunneling. -e query8dot3 Determine whether 8.3 support is enabled. When 8.3 support is enabled, applications requiring 8.3 short file names and name tunneling will work correctly. When 8.3 support is disabled, 8.3 file names will no longer be created and the name tunnel cache will be purged and removed. Filesystems enabled for 8.3 support cannot be mounted on Matrix Server versions earlier than 3.6.1, even if the 8.3 support is later disabled.
Disable quotas on the specified filesystem and free the associated blocks. --set-dq [T|G|M|K] Set the default hard quota for users on the specified filesystem. The optional modifiers specify that the size is in terabytes (T), gigabytes (G), megabytes (M), or kilobytes (K). If a modifier is not specified, the size will be calculated in bytes. (The default is rounded down to the nearest filesystem block.) --set-sdq [T|G|M|K] Set the default soft quota on the specified filesystem.
--sparse-realcost Quota accounting for sparse files reflects the actual allocation of filesystem space to the files. psfsdebug – get PSFS filesystem image Synopsis tools\psfsdebug Description This command should be used only under the direction of HP personnel. psfsdq – save quota data Synopsis bin\psfsdq [-f ] Description The psfsdq command prints a quota summary for all users and groups having quota information stored on the specified PSFS filesystem.
psfsformat.exe – create a PSFS filesystem Synopsis bin\psfsformat [-fq] [-l
when allocating a block. It is particularly useful for speeding up allocation times on large, relatively full filesystems. enable8dot3 Create the filesystem with support for 8.3 short file names (SFN) and name tunneling enabled. These features should be enabled only if you have a specific need for them, as the use of 8.3 files causes degradation in filesystem performance. The degradation is proportional to the number of 8.3 files created. If 8.3 SFN support is later disabled but 8.
nologhardlimit File operations that result in exceeding a user’s hard limit are not logged. logsoftlimit File operations that result in exceeding a user’s soft limit are logged in the system event log. nologsoftlimit File operations that result in exceeding a user’s soft limit are not logged. enforcehardlimit File operations that will result in exceeding a user’s hard limit are denied. noenforcehardlimit File operations that will result in exceeding a user’s hard limit are allowed.
QUOTA – the disk quota feature SPARSE_FILES – sparse files support EIGHT_THREE_PRIMED – 8.3 short file name (SFN) feature ADS – Alternate Data Streams SMALL_FILES – the small files performance enhancement feature If the feature is enabled, the name of the feature will be displayed. If the feature is not enabled, “=0 will be reported. (You can use the --help option to list the features that can be tested.
• By the drive letter, such as X: • By the mount point (junction), such as C:\san\vol2 • By the psd or psv name, such as psd2p2 or psv3 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. The psfsquota utility then examines the existing files and stores current allocations for each user and group owning a file on the filesystem.
File operations that result in exceeding a user’s hard limit are not logged. ––log-softlimit File operations that result in exceeding a user’s soft limit are logged in the system event log. ––nologsoftlimit File operations that result in exceeding a user’s soft limit are not logged. ––enforce-hardlimit File operations that will result in exceeding a user’s hard limit are denied. ––no-enforce-hardlimit File operations that will result in exceeding a user’s hard limit are allowed.
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 cluster. When you have completed your work with the suspended filesystem, use the psfsresume utility to resume the filesystem. Issue the psfsresume command from the server where you executed psfssuspend.
psfssuspend.exe – suspend a PSFS filesystem Synopsis bin\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 to ensure that all blocks copied are up-to-date.
psfsunpack.exe – unpack a PSFS filesystem image Synopsis tools\psfsunpack Description This command should be used only under the direction of HP personnel. psvctl.exe – manage dynamic volumes Synopsis tools\psvctl Description This command should be used only under the direction of HP personnel. registry.exe – dump registry contents Synopsis tools\registry Description This command is used internally by the mxcollect utility and should not be run directly. sandiskinfo.
Disk information With no options, sandiskinfo displays the UID, vendor, model, and capacity of each imported disk and specifies the FC switch used to access the disk. Disk: \\.\Global\psd2 Uid: 20:00:00:04:cf:13:38:3a::0 SAN info: fcswitch5:7 Vendor: SEAGATE Capacity: 34733M Following are commonly used options for imported and unimported disks: sandiskinfo [-i|-u|-v|-f] [-alr] [-U] [-q] The options are: -i Display information for imported disks (the default). -u Display information for unimported disks.
Show partition information The -a option also lists the partitions on each disk. When combined with -u, it displays partition information for unimported disks. sandiskinfo -a Disk: \\.
Vendor: SEAGATE Capacity: 34733M Local Device Paths: \\.\Global\PhysicalDrive4 partition 01: size 9M type (PSMP/Active) partition 02: size 4097M type (PSFS Filesystem) partition 03: size 4097M type (PSFS Filesystem) partition 04: size 9220M type (unknown) Show filesystem information The -f option displays existing PSFS filesystems on imported disks. Show available volumes The -v option lists available volumes on imported disks or LUNs.
# sandiskinfo --subdevices Subdevice: 20:00:00:04:cf:13:38:18::0/2 Subdevice: 20:00:00:04:cf:13:38:18::0/7 Subdevice: 20:00:00:04:cf:13:38:18::0/8 Subdevice: 20:00:00:04:cf:13:38:18::0/9 Subdevice: 20:00:00:04:cf:13:38:18::0/10 Subdevice: 20:00:00:04:cf:13:38:18::0/11 Subdevice: 20:00:00:04:cf:13:38:18::0/12 Subdevice: 20:00:00:04:cf:13:38:18::0/13 Subdevice: 20:00:00:04:cf:13:38:18::0/14 Size: Size: Size: Size: Size: Size: Size: Size: Size: 1950M 490M 490M 490M 490M 490M 490M 490M 490M psd1p2 psd1p7 psd
Lists unimported dynamic volumes that cannot be imported into the cluster. scsf.exe – shadow copies of shared folders Synopsis bin\scsf Description This command is used internally by Matrix Server and should not be run directly. sdmp.exe, sdmp_ctl.
snapctl.exe – manage snapshot operations Synopsis bin\snapctl Description This command is used internally and should not be run directly. snmpget, snmpset, snmpwalk – SNMP utilities These utilities are provided as a convenience. spctl.exe – dump the SanPulse trace buffer Synopsis tools\spctl Description This command should be run only at the request of HP personnel. spdebug.
sqlreg.exe – create a registry file Synopsis bin\sqlreg Description This command is used internally by HP PolyServe Software for Microsoft SQL Server and should never be run directly. wmtest.exe – test server-based fencing Synopsis tools\wmtest Description This command is used for testing purposes and should be run only at the request of HP personnel.
3 mx commands The mx utility provides a command-line interface for administering a cluster and monitoring its operation. The matrixrc file Matrix Server can use an optional, external configuration file named .matrixrc to provide authentication information for cluster connections. If the file is configured, it will be used when you connect to a cluster through either the Matrix Server Connect window or the mx command.
• The fourth field, default, specifies that this server will be connected to by default if a server name is not specified on the command line. Specifying a default server is optional. Blank lines and lines beginning with a # character are ignored. Notes regarding the .matrixrc file When working with the .matrixrc file, you should be aware of the following: • When editing the .matrixrc file by hand, you need to put quotation marks around user names or passwords that contain spaces.
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 .matrixrc file to match machine names: srv3 srv* admin admin secret1 secret1 default In the following command, --matrix srv8 matches the wildcard.
try the other servers in the list. If “default” is omitted, the mx command will attempt to connect to the servers in the order that they are specified in the list. # production cluster prod admin secret1 default { srv1 srv2 srv3 admin secret1 default srv4 admin secret2 } Encrypted passwords in the .matrixrc file Passwords are encrypted automatically when you use the Matrix Server Connect window to specify the password. You can also use the mxgenpass.
The mx_options affect an entire mx command session. The options are: --help Displays a command summary. --matrix Specifies the cluster that you want to connect with. hostname can be any node in the cluster. --config Specifies an alternate 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.
Class Cluster Object application A grouping of cluster resources such as virtual hosts, service monitors, and device monitors config Initial cluster configuration config mp Membership partition configuration config snapshot Snapshot method configuration device Device monitor disk SAN disk dynvolume Dynamic volume eventnotifier Event notification services fs PSFS filesystem matrix The entire cluster mfs Matrix File Share mni Multi-Node Installer for SQL instances netif Network
Class Cluster Object vsql Virtual SQL Server vsqlinstance Virtual SQL Server instance vssas Virtual SSAS vssasinstance Virtual SSAS instance To specify a command affecting a class, use this syntax: For example, the following command displays the status of servers that are currently up: mx server status --up mx account – account management commands Use the following mx account commands to manage user and group accounts that belong to management roles.
Whether the account is for a user or group, or is unknown. The default is GROUP. listroles—List the role memberships of an account mx account listroles [--form ] [--type ] [--effective] [--noHeaders] [--csv] [--showBorder] [] This command lists the roles to which the account belongs. To show information for the current user, omit the account parameter. The options are: --type Whether the account is for a user or group, or is unknown.
mx alert – cluster alert commands Use the following command to view Matrix Server alerts. alert—Display all outstanding alerts mx alert status [--severity ] [--noHeaders] [--csv] [--showborder] The options are: [--severity ] Filters the alerts according to the specified alert level. The levels are: INFO, WARNING, ERROR, CRITICAL. If you specify more than one alert level, use commas to separate the levels. [--noHeaders] Do not display column headers in the output.
rename—Rename an application mx application rename status—Show status for an application mx application status [--severity OK|WARNING|ERROR] [ ...] mx config – cluster configuration commands Use the following commands to configure the cluster. NOTE: If you are performing the initial configuration of a cluster, the mx config, mx config mp, and mx config snapshot commands must be entered in a specific order.
Command Description secret Set the cluster secret license key testfencing Test the fencing configuration webfencing Configure the web-based fencing module check—Check the cluster configuration mx config check This command specifies whether cluster components are configured or unconfigured. It does not verify that components are configured correctly. To see the state of each component, use commands such as mx config list and mx config mp list.
The default SNMP community string for Matrix Server is private. If you want to use a custom community string, use the --community option to enter the appropriate value. The SNMP community string must be set to the same value on Matrix Server and on the SAN switches. import—Import the cluster configuration mx config import This command can be used when the cluster is either online or offline.
The current administrative traffic protocol (either Multicast or Unicast). Multicast is the default. [--santype] The current storage type (either FibreChannel or iSCSI). [--servers] The servers currently in the cluster. [--snapshots] The snapshots currently in the cluster. [--status] The current status of the cluster (STARTING, RUNNING, STOPPING, or STOPPED). [--switches] The FibreChannel switches currently configured in the cluster.
santest—Test the switch configuration mx config santest --santype [fc|iscsi] ... This command can be used only when the cluster is offline. is either fc for FibreChannel or iscsi for iSCSI. santype—Set the SAN storage type mx config santype [fc|isci] This command can be used only when the cluster is offline. Specify the appropriate type, either fc for FibreChannel or iscsi for iSCSI. The default is fc.
server1 and server2 and their Remote Management Controllers are server1-iLO and server2-iLO, specify -iLO as the suffix. --ipdelta The delta to add to each server’s IP address to determine the IP addresses of the associated Remote Management Controllers. For example, if your servers are 1.255.200.12 and 1.255.200.15 and their Remote Management Controllers are 1.255.201.112 and 1.255.201.115, specify 0.0.1.100 as the delta.
Command Description dump Dump the membership partition configuration list List the current membership partitions in a running or stopped cluster list_avail_disks List disks that can be used for membership partitions list_avail_partitions List partitions that can be used for membership partitions repair Repair a membership partition set Add or replace membership partitions In general, these commands can be used when Matrix Server is online or offline.
partitions, but the physical size can vary and will always be the same or larger than the “used” size. list_avail_disks—List disks that can be used for membership partitions mx config mp list_avail_disks [--noHeaders] [--csv] [--showborder] The options are: [--noHeaders] Do not display column headers in the output. [--csv] Display the output in comma-separated value format. [--showborder] Display borders in the output.
is the second membership partition, and is the third membership partition. The options are: [--recreate] Allow existing membership partition information to be destroyed. [--force] Force membership partition replacements to occur even if the partitions to be replaced cannot be invalidated. [--reuse] Allow disks that contain existing volume information to be reused. (The existing data is destroyed.
--username The user name required to access the management appliance. --passwd The password required to access the management appliance. For engenio, specify the following: --controllerA The hostname or IP address for controllerA. --controllerB The hostname or IP address for controllerB. --passwd The password for the storage array controller.
showtype—show available snapshot methods mx config snapshot showtype test—test an existing snapshot method configuration mx config snapshot test --method --hostname | --controllerA The options are: --method The supported types are hpeva and engenio. --hostname |--controllerA For hpeva, use the --hostname option to specify the hostname for the management appliance.
--type specifies the type of device monitor to be created: CUSTOM, DISK, GATEWAY, SHARED_FILESYSTEM, or NTSERVICE. --servers specifies the server or servers that use the monitored device. The can include up to 32 characters. The optional arguments are: [--application ] The application associated with this device monitor. [--timeout ] The maximum amount of time to wait for a probe of the device to complete. For CUSTOM device monitors, the default is 60 seconds.
the mount path will be prepended to the filename to determine the complete filename path that should be probed. The second parameter is optional. • NTSERVICE device monitor. Whether services dependent on the monitored NT service should also be started when the NT service is started (specify either Yes or No). If you want the services to be started, you can also specify the number of attempts that should be made. Use a semicolon to separate the values (for example, Yes;3).
servers. Upon server failure, the monitor will fail over to an active server unless all associated service and device monitors are down. With always, the monitor is active on only one of the selected servers. Upon server failure, the monitor will fail over to an active server even if all associated service and device monitors are down. With multiple, the monitor is active simultaneously on all selected servers. [--vhosts ,,...] The virtual hosts associated with the device monitor.
The arguments are the same as the device add command; however, the --servers argument is not required and the monitor type cannot be changed. mx disk – disk commands Use the following commands to import SAN disks into a cluster, to remove them from a cluster, or to display status information.
mx dynvolume – dynamic volume commands Use the following commands to manage dynamic volumes.
A filesystem cannot be mounted on the volume that will be deleted. dump—Dump dynamic volume configuration to stdout mx dynvolume dump extend—Extend a dynamic volume mx dynvolume extend [--reuse] You can use either spaces or commas to separate the subdevice names. The --reuse option causes the operation to proceed even though a specified partition may be associated with an unimported dynamic volume.
properties—Display properties for a dynamic volume mx dynvolume properties showcreateopt—List subdevices available for use in a dynamic volume mx dynvolume showcreateopt mx eventnotifier – event notification commands Use the following commands to manage event notification services.
The options are: [--snmp] Add the specified event IDs to the SNMP notification service. [--email] Add the specified event IDs to the email notification service. [--script] Add the specified event IDs to the script notification service. If none of the options are specified, the event IDs will be added to all notification services.
[--smtpport ] The port to be used on the SMTP server. The default is port 25. [--smtpuser ] The username used to access the SMTP server. This option is needed only if the server requires credentials. [--smtppass ] The password used to access the SMTP server. This option is needed only if the server requires credentials.
Disable the script notification service. If none of the options are specified, all notification services will be disabled. enable—Enable an event notifier service mx eventnotifier enable [--snmp] [--email] [--script] The options are: [--snmp] Enable the SNMP notification service. [--email] Enable the email notification service. [--script] Enable the script notification service. If none of the options are specified, all notification services will be enabled.
removeevents—remove cluster event definitions from a notification service mx eventnotifier removeevents [--snmp] [--email] [--script] You can specify individual event IDs or a range of IDs to be removed. Use commas to separate the values, for example: 100, 300-400,555. The options are: [--snmp] Remove the specified event IDs to the SNMP notification service. [--email] Remove the specified event IDs to the email notification service.
test—Test an event notifier service mx eventnotifier test [--snmp] [--email] [--script] This command verifies that events can be sent to the specified notification service. An error will be reported if the service is disabled or is not configured. The options are: [--snmp] Test the SNMP notification service. [--email] Test the email notification service. [--script] Test the script notification service. If none of the options are specified, all notification services will be tested.
Command Description dump Dump filesystem configuration to stdout getdriveletters Display drive letters in use on a server queryassignments Display drive letter or path assignments for a filesystem recreate Reformat a filesystem showcreateopt Display information about storage devices status Display status information unassign Unassign a drive letter or path assign—Assign a drive letter or path to a filesystem mx fs assignpath --path [--createdir] ALL_SERVERS
Enable quotas on the filesystem. [--defaultUserHardLimit ] The default hard limit on the filesystem. unlimited specifies that there is no default. The optional size modifiers specify that the size is in kilobytes (K), megabytes (M), gigabytes (G), or terabytes (T). If a modifier is not specified, the size will be calculated in bytes. (The default is rounded down to the nearest filesystem block.
recreate—Reformat a PSFS filesystem mx fs recreate [options] showcreateopt—Display information about storage devices mx fs showcreateopt status—Display status information mx fs status [--verbose] [--standard|--snapshots] This command lists the status of each filesystem. The --verbose option displays the FS type (always PSFS), the size of the filesystem in KB, and the UUID of the parent disk.
dump—Dump cluster configuration information The following command dumps configuration information to stdout. The information includes the configuration of servers, network interfaces, virtual hosts, service and device monitors, notifiers, disks, and filesystems. The configuration also includes sleep setting and alerts.
Command Description enable Enable a Matrix File Share status Display the status of a Matrix File Share update Update an existing Matrix File Share add—Add a Matrix File Share mx mfs add --path --servers ALL_SERVERS|, ,... [arguments] --servers specifies the servers on which the Matrix File Share should be configured. is the name for the Matrix File Share. is the location of the Matrix File Share (such as y:\myshared).
Share all subdirectories under the specified path. [--caching ] Enables or disables offline caching. The arguments are: • manual. Only the files and programs that users specify will be available offline. This is the default. • documents. All files and programs that users open from the share will be automatically available offline. • programs. All files and programs that users open from the share will be automatically available offline.
mx mni – Multi-Node Installer for SQL Instances Use the following commands to install SQL instances with the Multi-Node Installer.
--product_id A unique identifier for the HP PolyServe Software product definition to be installed. | ALL_SERVERS The servers on which the SQL Server instance will be upgraded. install—Install or upgrade one or more SQL or SSAS instances on one or more servers Some of the options apply only to SQL instances or SSAS instances. Be careful to use the correct options when installing an instance.
--serverSSAS | ALL_SERVERS The servers on which the SSAS instance will be installed. listinstances—List the SQL Server or SSAS instances installed on the matrix mx mni listinstances [--product_type ] The --product_type option specifies the type of instances to display: SQL, SSAS, or both. The default is ALL.
--location For a SQL Server base product, is the path to the folder containing the files needed to install the product. For a Service Pack or Hotfix, points to the executable file. --force Overwrite the existing product definition. mx netif – network interface commands Use the following commands to manage network interfaces or to display their status.
admin—Make a network available for administrative traffic mx netif admin ... This command is deprecated in Matrix Server 4.0. Use the allowadmintraffic command instead. allowadmintraffic—Make a network available for Matrix Server administrative traffic mx netif allowadmintraffic ... delete—Remove a network interface mx netif delete disable—Disable a network interface for virtual hosting mx netif disable ...
--allowadmin traffic|--discourageadmintraffic|--excludeadmintraffic Select interfaces that allow, discourage, or exclude administrative traffic. --active|--inactive Select interfaces that are currently active (handling administrative traffic) or inactive. --noheaders Do not display column headers. --csv Use commas to separate the output.
Command Description unsetuser Remove filesystem quotas for one or more users Commands for groups: setgroup Set the filesystem quota for users in one or more groups showgroup Display quotas for users in groups matching the search criteria unsetgroup Remove quotas for users in one or more groups Commands for filesystems These commands allow you to enable or disable quotas on a filesystem and to set or display the quota options configured on the filesystem.
The default soft limit for users on the filesystem who have not been assigned an individual limit. unlimited specifies that the default is unlimited. The size modifiers are K (kilobytes), M (megabytes), G (gigabytes), or T (terabytes). If a modifier is not specified, the size is calculated in kilobytes. (The default is rounded down to the nearest filesystem block.) If this option is not used, the default will be unlimited. [--enforceHardLimit ] Whether hard limits are enforced.
The default soft limit for all users on the filesystem. unlimited means that the default is unlimited. The size modifiers are K (kilobytes), M (megabytes), G (gigabytes), or T (terabytes). If a modifier is not specified, the size is calculated in kilobytes. (The default is rounded down to the nearest filesystem block.) [--force] Continue with the command even if some specified filesystems do not have quotas enabled.
[--noHeaders] Do not display column headers in the output. [--csv] Display the output in comma-separated value format. showdefaults—Show the default quotas for one or more filesystems mx quota showoptions [opt-args] ALL_FILESYSTEMS| ... The optional arguments are: [--noHeaders] Do not display column headers in the output. [--csv] Display the output in comma-separated value format. Commands for users These commands allow you to set, display, or remove the filesystem quotas for individual users.
[--id ] A user ID or range of IDs. [--name ] One or more user names. You can also enter a regular expression. [--regex] The value specified for --name is a regular expression. [--hardLimitRange -] A range of hard limits. [--spaceUsedRange -] A range of disk space usage. [--percentUsedRange <#%>-<#%> A range of percentages of disk space used.
[--hardLimitRange -] A range of hard limits. [--spaceUsedRange -] A range of disk space usage. [--percentUsedRange <#%>-<#%> A range of percentages of disk space used. [--noHeaders] Do not display column headers in the output. [--csv] Display the output in comma-separated value format. [--showID] Show user IDs in the output.
A range of disk space usage. [--percentUsedRange <#%>-<#%> A range of percentages of disk space used. Commands for groups These commands allow you to set, remove, or display quotas for all of the users in a particular group. setgroup—Set the filesystem quota for one or more groups mx quota setgroup [optional-args] ALL_FILESYSTEMS | ... The optional arguments are the same as mx quota setuser except that --name is a list of group names and the --memberof argument is not used.
Command Description list List cluster roles listmembers List members of a cluster role delete—Delete a cluster role mx role delete This command deletes a role from the cluster. Accounts belonging to the role will automatically lose their membership. disable—Disable a cluster role mx role disable This command disables a role. Disabling a role can be a temporary way to remove all members from the role.
listmembers—List the members of a cluster role mx role listmembers This command lists the user or group accounts that are members of the specified role. mx server – server commands Use the following commands to configure servers or to display their status.
outage. The default is autorecover. This command can be used when the cluster is either running or offline. delete—Delete one or more servers from a cluster mx server delete ... This command can be used when the cluster is either running or offline. disable—Disable one or more servers mx server disable ... dump—Dump the server configuration to stdout mx server dump enable—Enable one or more previously disabled servers mx server enable ...
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.
[--timestamp ] Filter by a particular time range expressed as . [--noHeaders] Do not display column headers in the output. [--csv] Display the output in comma-separated value format. [--showborder] Display borders in the output. mx service – service monitor commands Use the following commands to configure service monitors or to display their status.
The maximum amount of time to wait for a probe of the device to complete. For NTSERVICE monitors, the default is 15 seconds. For CUSTOM service monitors, the default is 60 seconds. For all other service monitors, the default is five seconds. [--frequency ] The interval of time at which the monitor probes the service. For CUSTOM service monitors, the default is 60 seconds. For all other service monitors, the default is 30 seconds.
[--startTimeout ] The amount of time to wait for the Start script to complete. [--stopScript
