Supercluster Command-line Reference
The Illumio PCE control interface for Supercluster commands often have restrictions on the type of node they can be run on. For example, setting a cluster's runlevel can be run from any core or data node. Other database specific commands must only be run on specific data nodes. The following tables list the different command line operations you can perform and the specific node (or nodes) the commands must be run on.
Supercluster Commands to Node Reference
This section lists commands you can use to control behavior of PCEs and PCE databases in a Supercluster.
Supercluster PCE Control Commands
The commands have the following general syntax. The --retry-count
is optional and defaults to 5.
sudo -u ilo-pce illumio-pce-ctl sub-command--option [--retry-count]
The following table shows commands you can use to control PCE behavior:
Command | Description | Run on Node |
---|---|---|
| Revert a PCE to standalone state. | The affected node being repaired to join the Supercluster |
| Designate an existing member PCE cluster to be a Supercluster leader. | Any node |
| Temporarily drops the failed PCE from the Supercluster, so it is no longer replicated. | Any node |
| Assign a PCE cluster as the leader of your Supercluster. | Any node |
| Joins a PCE cluster to a Supercluster. Running this command can take up to 30 minutes depending on the number of PCEs in your Supercluster and size of the PCE database. | On any core node |
| Displays all current active Supercluster PCEs, members and leader. | On any core node or the data0 node |
| Restores a formerly failed leader or member to be restored to the Supercluster. This command can be run for a leader or a member. Executing this command can take up to 1 hour depending on the number of PCEs in the Supercluster and size of the PCE database. | On any core node |
Supercluster PCE Database Commands
The commands have the following general syntax. The --retry-count
is optional and defaults to 5.
sudo -u ilo-pce illumio-pce-db-management sub-command --option [--retry-count]
The following table shows commands you can use to control PCE database behavior:
Command | Description | Run on Node |
---|---|---|
| Restores a failed PCE's data, using a backup taken from that PCE before the failure. | On one of the data nodes only |
| Pauses all the pending database replication; for example, during a software upgrade. | Any node |
Re-runnable illumio-pce-ctl Arguments
All arguments to illumio-pce-ctl
are re-runnable in case of a command failure.
Argument on illumio-pce-ctl | Description |
---|---|
| Configures this PCE as the Supercluster leader. |
| Joins this PCE into the Supercluster specified by the FQDN of the Supercluster leader. While this command is running, it temporarily sets the runlevel to 1. When the command is interrupted, you might see runlevel 1 unexpectedly. |
| Assigns a new Supercluster leader. |
| Restores a failed PCE and rejoins it to the Supercluster. Replace While this command is running, it temporarily sets the runlevel to 1. When the command is interrupted, you might see runlevel 1 unexpectedly. |
| Temporarily drops the failed PCE from the Supercluster, so it is no longer replicated. |
| Shows the members in the Supercluster. |
| Shows the Supercluster configuration. |
| Displays the state of replication. The |
Re-runnable illumio-pce-db-management Arguments
All arguments to illumio-pce-db-management
are re-runnable in case of a command failure.
Argument on illumio-pce-db-managment | Description |
---|---|
| Writes the database persistent state in Supercluster to a file. |
| Restores data and persistent state of a Supercluster database. |
| Display Supercluster node replication information. |
| Quiesces all pending replication. |
| Show replication-related information for debugging. |