3.5.1 Matrix Server Command Reference
Chapter 2: mx Commands 88
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
--policy
autofailback|nofailback
The failback action that the virtual host will take following failover to a
backup node. autofailback will fail back when a higher-ranked node
provides equal or greater services than the backup node; nofailback fails
back only if a higher-ranked node provides greater services than the backup
node. autofailback is the default.
--activitytype single|always
Whether, upon server failure, the virtual host will move to an active server if
all associated service and device monitors are inactive or down. If always is
specified, the failover will occur. If single is specified, the failover will not
occur and the virtual host will not be made active anywhere. single is the
default.
<vhost> can be either the hostname or the IP address for the virtual host. If
you specify the hostname, it can include up to 32 characters.
The order in which you specify the network interfaces determines the
ordering for failover. The first network interface is the primary interface;
network traffic for the virtual host goes to the server providing this
interface. The remaining network interfaces are backups. Each network
interface must be located on a different server.
Modify (update) an existing virtual host:
mx vhost update [--application <application>]
[--policy
autofailback|nofailback]
[--activitytype single|always] <vhost>
([<network_interface> ...][ALL_SERVERS <network_interface>])
Use this option to change the arguments or the ordering of the network
interfaces for failover.
Move a virtual host to another server:
mx vhost move [--policy autofailback|nofailback]
[--application <application_name>] [--activitytype
single|always] <vhost> ([<network_interface> ...][ALL_SERVERS
<network_interface>])
Delete a virtual host:
mx vhost delete <vhost>