3.6.0 Matrix Server Installation Guide (5697-7079, February 2008)

Appendix A: Configure the Matrix from the Command Line 48
Copyright © 1999-2008 PolyServe, Inc. All rights reserved.
mx config webfencing --ruser <user name> --vendor <vendor> --mixedvendor
yes|no --hostname <name>|--hostsuffix <suffix> |--ipdelta <delta>
[--type reset|shutdown] [--bladeslot <slot>] [--sharedlogin yes|no]
[--rpassword <password>]
Configure web management-based fencing, in which Matrix Server
uses remote management hardware on the server to remove its access
to PSFS filesystems. iSCSI storage must use this fencing method.
When configuring web management-based fencing, you will need to
specify how Matrix Server should identify the Remote Management
Controller associated with each server. Use one of these methods:
--hostname <host name>
Specify the hostname for the Remote Management Controller
associated with this server. You will need to use this method if your
Remote Management Controllers are from different vendors. This
method must also be used for IBM BladeCenter servers.
--hostsuffix <host suffix>
Specify the common suffix to append to each server name to
determine the associated Remote Management Controller name. For
example, if your server names are server1 and server2 and their
Remote Management Controllers are server1-iLO and server2-iLO,
enter -iLO as the suffix.
--ipdelta <ip delta>
Specify 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,
enter 0.0.1.100 as the delta.
The other webfencing options are:
--vendor <vendor>
The vendor for your remote management controller (dell, hp, ibm, or
ipmi).
[--bladeslot <slot>]
For IBM Blade Center only, the blade slot.
--mixedvendor yes|no
Whether the vendor and type settings apply to all servers.