asc ha
Use this command to manage OS and application-level High Availability (HA) on CloudControl.
Syntax
asc ha [options]
|
Option |
Description |
|
-d, --disband |
Disconnect the CloudControl from the HA cluster. This can be run from the primary or secondary CloudControl nodes. |
|
--disable-password-sync |
Disables the synchronization of the 'ascadminuser' password. |
|
--dualSiteHaConf |
Used to add and modify VIP and PIP configuration for the secondary host to allow your primary and secondary PIP to be located in separate subnets. See |
|
--dualSiteHaConf --list |
Lists the contents of the VIP and PIP configuration file for the dual site HA configuration. |
|
--dualSiteHaConf --delete |
Deletes the existing VIP and PIP configuration file for the dual site HA configuration. |
|
-e, --peertest |
Test the health of the remote system and automatically failover if needed. |
|
--enable-password-sync |
Enables the synchronization of the 'ascadminuser' password. |
|
-f, --failover {auto|manual} |
Set the failover mode. Valid values are:
|
|
-h, --help |
Display usage text. |
|
--haclean |
Clean old HA sync data keeping only the three most recent data sets. Use |
|
-i, --interval <minutes> |
Sets the data synchronization period, in minutes, between CloudControl nodes. The default is 10 minutes, and the valid range is 2-1440 minutes. |
|
-j, --join |
Join two CloudControl nodes to create an HA cluster. This can be run from either the primary or secondary node. This requires the IP address and password for the node that you want to join, and the status (mode) of the node you are joining from. |
|
-o, --mode {primary|secondary} |
Sets the HA mode. Valid values are:
Changing the HA mode triggers a failover event. |
|
-n, --nosync |
Do not perform an initial synchronization of data between HA nodes during a join, or prior to initiating a failover. |
|
-p, --password <password> |
The password of the remote CloudControl. Required when joining an HA cluster. Optionally, the password can be supplied via the |
|
-s, --sync |
Forces an immediate synchronization of data between HA CloudControl nodes. |
|
--sshkeyrotate |
Rotates the SSH keys on the primary and secondary nodes of an existing cluster. After rotating, use the Note: If there is a failure during key rotation, disband the cluster on both nodes and reform using the |
|
--sshkeytest |
Tests the network connection between the two HA CloudControl nodes and verifies the SSH keys. |
|
-t, --status |
View the current configuration and operational state of the HA cluster. |
|
-u, --timeout <minutes> |
Sets the primary CloudControl monitoring minimum time threshold, in minutes, before an automatic failover event occurs. The minimum value is 10. |
|
-v, --pollinterval <minutes> |
Sets the health monitoring period, in minutes, before automatic failover mode is enabled. |
|
--virtual-ip |
Set the CloudControl Service IP address. |
Examples
Trigger a failover event from the secondary node:
asc ha --mode primary
Synchronize and trigger a failover event from the primary node:
asc ha --sync --mode secondary
View the HA configuration and status:
asc ha --status
Create an HA cluster from the primary CloudControl node:
asc ha --join <secondary-IP-address> --password SecondaryS3crEt --mode primary
Create an HA cluster from the secondary CloudControl node:
asc ha --join <primary-IP-address> --password PrimaryS3crEt --mode secondary
Leave the HA cluster from either the primary or secondary node:
asc ha --disband
Enable automatic failover:
asc ha --failover auto
Disable automatic failover:
asc ha --failover manual
Perform an automatic failover immediately:
asc ha --failover now
Set up HA with a remote secondary node and one PIP:
asc ha --dualSiteHaConf Do you want configure VIP for secondary?(yes/no) yes
Configuring : VIP
Primary FQDN [test.hytrust.com]:
Primary VIP [10.222.73.214]:
Primary Netmask [255.255.0.0]:
Secondary FQDN [test.hytrust.com]:
Secondary VIP [10.222.73.215]:
Secondary Netmask [255.255.255.0]:
Configuring : PIP
vCenter Published DNS on Primary [vcsa31-pip.test.hytrust.com]:
vCenter PIP on Primary [10.222.73.219]:
Primary Netmask [255.255.0.0]:
vCenter Published DNS on Secondary [vcsa31-pip.test.hytrust.com]:
vCenter PIP on Secondary [10.222.73.220]:
Secondary Netmask [255.255.255.0]:
Do you want to configure PIP for secondary node?(yes/no) no
Success: The High Availability system has been updated
Listing the dual HA setup configuration:
asc ha --dualSiteHaConf --listType : VIP
Primary FQDN : test.hytrust.com
Primary IP : 10.222.73.213
Primary Netmask : 255.255.0.0
Secondary FQDN : test.hytrust.com
Secondary IP : 10.222.73.212
Secondary Netmask : 255.255.255.0
Type : PIP
Primary FQDN : vcsa31-pip.test.hytrust.com
Primary IP : 10.222.73.219
Primary Netmask : 255.255.0.0
Secondary FQDN : vcsa31-pip.test.hytrust.com
Secondary IP : 10.222.73.218
Secondary Netmask : 255.255.255.0
Success: The High Availability system has been updated
Deleting a dual HA setup configuration:
asc ha --dualSiteHaConf --deleteDo you want to delete VIP configuration for test.hytrust.com - 10.222.73.214?(yes/no) no
Do you want to delete PIP configuration for vcsa31-pip.test.hytrust.com - 10.222.73.219?(yes/no) no
Do you want to delete PIP configuration for vc2.test.hytrust.com - 10.222.73.222?(yes/no) yes
Success: The High Availability system has been updated
|
Follow us: |
