Shell Commands › Server Management › set Command (Server Management)--Set Server's HA Role

set Command (Server Management)--Set Server's HA Role

Set server configuration parameter

Syntax

server set <name> <prop>=<val> [ --force ]  

Options

<name>

Name of server for which to set information.

<prop>=<val>

Server parameter to modify. The following parameters may be set:

role

Server's HA role. May be one of the following:

'primary'

Server that is currently running the CA 3Tera AppLogic grid controller

'secondary'

Server that may run the CA 3Tera AppLogic grid controller in case of a controller server failure

'none'

Server will never run the CA 3Tera AppLogic grid controller and does not participate in controller HA

ha_network

Enable/disable network HA for the server (both external and backbone)

ha_backbone

Enable/disable network HA on the backbone network

ha_external

Enable/disable network HA on the external network

backbone

specify which switch is active for the backbone network

external

Specify which switch is active for the external network

hypervisor_name

Name of the hypervisor

hypervisor_lic_key

Hypervisor license key

--force

Skip the user verification prompt when setting a new primary server for a grid

Examples

server set srv1 role=primary

Set server srv1's role to primary

server set srv2 role=secondary

Set server srv2's role to secondary

server set srv1 ha_network=1

Enable network HA for the server (external and backbone)

server set srv2 ha_backbone=0

Disable network HA on the backbone network for the server

server set srv2 ha_external=0

Disable network HA on the external network for the server

server set srv2 backbone="11:22:33:44:55:66"

Set backbone NIC connected to switch with an ID of 11:22:33:44:55:66 as active, all backbone network traffic on srv2 passes through the NIC connected to that switch

server set srv2 external="77:88:99:AA:BB:CC"

Set external NIC connected to switch with an ID of 77:88:99:AA:BB:CC as active, all external network traffic on srv2 passes through the NIC connected to that switch

Notes:

• You must be a grid maintainer to set any of the network HA or hypervisor-related parameters (that is, ha_network, ha_backbone, ha_external, backbone, external, hypervisor_name, and hypervisor_lic_key).
• If a server is assigned to be the new primary server for a grid, the grid controller is immediately migrated to the new primary server. The old primary server will be assigned the previous role of the new primary server (the roles are swapped).
• The only way to change the role of a primary server is to assign a different server in the grid as the new primary server (users are not allowed to explicitly change a server's role from primary to either none or secondary).
• A grid must have one and only one primary server; a grid may have from 0 to 7 secondary servers. By default upon grid installation/upgrade, a grid with 3 or more servers has 1 primary server and 2 secondary servers. Additional secondary servers may be assigned using this CLI command.
• For a grid to recover from a controller server failure, there must be at least 2 secondary servers up and running at the time of the server failure. If this requirement is not met (for example, there is only one secondary server at the time of the primary server failure), the grid controller remains down and requires grid maintainer intervention to restore the grid controller to an operational state. If this type of controller failure is encountered, contact your service provider for assistance.
• If there are not enough secondary servers in a grid to recover from a future primary server failure, CA 3Tera AppLogic notifies the user by posting a grid dashboard message.