Phone Lines icon GFI Support Home

Articles in this section

See more

Exinda CLI: Clustering and HA

Author: Sughra Mehdi Updated

Overview

 

This article provides information regarding the Exinda CLI command cluster which is used to configure clustering.

 

Information

 

NOTE:  The following syntax convention is used:
  • {}: Options are enclosed in  braces and are separated by '|'
  • []: Optional keywords are enclosed in brackets
  • <>: User input is required where variables are enclosed in greater-than and less-than symbols

The following tables show commands used for performing common actions related to clustering and HA:

 

Configuring the Interface for the Cluster Service

Action Description Command 

Parameter Description 
To configure a cluster internal or external address cluster interface <inf>

Any interface not bound to a bridge or used in another role (e.g. Mirror or WCCP) may be used. This command will need to be run on each node in the cluster, and each with a unique cluster internal address.
cluster interface <inf> ip address <address> <netmask>

This command should also be executed on all cluster nodes, using the same cluster external address.
To configure the master cluster
  • cluster master interface <inf>

  • cluster master address vip <address> <netmask>

The role of the node (master or slave) is shown in the CLI prompt. Once the cluster is up, configuration changes should only be made on the cluster master. Configuration changes made on the master will be sent to slave nodes.
To control how data is synchronized between cluster members [no] cluster sync {all|acceleration|monitor|optimizer|compression}
  • sync all - Acceleration, monitor and optimizer data are synchronized. This is disabled by default.
  • sync acceleration- Synchronize acceleration data only
  • sync acceleration redirect-only - Do not accelerate any connections; only perform monitoring
  • sync monitor - Synchronize monitor data only
  • sync optimizer - Synchronize optimizer data only
  • sync compression - Configure cluster compressions settings
  • sync compression threshold - Set the size of the data block that will trigger compression
  • sync compression threshold <value> - Set the compression value (default is 2048)
  • sync compression zip - Enable zip compression between cluster nodes
  • sync compression zip level <value> - Set the zip compression level, where 1 is the fastest, largest compressed block and 9 is the slowest, smallest compressed block and best compression. When zip compression is enabled, the level value defaults to 9 until changed. Note that the larger compression block requires less bandwidth, but results in smaller blocks and requires more CPU power.

  

Viewing Cluster Configuration and Status

 Action Description

 Command  Parameter Description 

To show a brief overview of the current cluster configuration

show cluster global brief

  Not Applicable
To show cluster sync status information show cluster sync {acceleration|optimizer|monitor|compression}
  • sync acceleration - Show acceleration sync status
  • sync redirect-only - Synchronize redirect data only
  • sync monitor - Synchronize monitor data only
  • sync optimizer - Synchronize optimizer data only
  • sync compression - Show cluster compression information

To display all the appliances in the cluster

 show appliances  Not Applicable

 

Find more CLI commands.

Back to Top

Was this article helpful?
0 out of 0 found this helpful

Related articles