Introduction

There can be situations when a Controller Cluster should be reverted converted to act as a Standalone Controller:

...

Converting a Controller Cluster to a Standalone Controller offers to re-instate the Cluster at any later point in time.

Revoking the Controller Cluster

Stopping the Controller Cluster

As a prerequisite both active and standby Controller instances have to be terminated.

Reverting the Controller Journal

Users decide which Controller instance should become the Standalone Controller to continue operations.

...

# reverting Controller journal for Unix with no running Controller instances
./controller_instance.sh revoke

# reverting Controller journal for Unix with a running Controller instance that is stopped and reverted (available starting from release 2.5.1)
./controller_instance.sh stop --revoke

@rem reverting Controller journal for Unix with no running Controller instances
./controller_instance.cmd revoke

@rem reverting Controller journal for Unix with a running Controller instance that is stopped and reverted
 (available starting from release 2.5.1) .\controller_instance.cmd stop --revoke

...

• Running the above script will remove any cluster related items from the Controller instance's journal.
• This allows the Controller instance to be started as a Standalone Controller.
• Standalone Controllers
  • do not connect to a Cluster Watch Agent,
  • do not connect nor can be connected to/from a second Controller instance acting in a standby role.

Configuring the Standalone Controller

The Controller's administrative menu is invoked from the JOC Cockpit user interface as follows:

...

At the point in time when submitting the changes the Controller will not be started. Therefore the Test Connection function cannot be used.

Starting the Standalone Controller

With the Controller type being reverted users can start the Standalone Controller from the command line like this:

...