Command Line Interface modes

The mode of an Integration Appliance determines the type of Command Line Interface (CLI) commands that you can use.

An Integration Appliance can be in one of the following modes:
Active
An Integration Appliance in an high availability (HA) pair that is actively processing data is in the Active mode. You can run all CLI commands in this mode. The active Integration Appliance can be in one of the following states:
  • Active 1 - The active Integration Appliance is not communicating with its HA peer. If the peer Integration Appliance is rebooting or the R1 and R2 cables are disconnected, this status can occur.
  • Active 2 - The active Integration Appliance is communicating with its HA peer.
Idle
An Integration Appliance enters the Idle mode when an error that requires user action occurs. This state indicates that the non-active Integration Appliance is unable to be in either the Active or Standby mode. Only Integration Appliances that are part of an HA pair enter the Idle mode. You can run diagnet, ha, netspect, and system commands in this mode.
Standalone
A single Integration Appliance that processes all messages. A standalone Integration Appliance cannot be part of an HA pair. In this mode, you can run all commands except the commands associated with an HA pair.
Standby
An Integration Appliance in an HA pair that monitors the processing of the Active Integration Appliance runs in Standby mode. The Integration Appliance running in Standby mode stays in sync with the Integration Appliance running in the Active mode, ready to take over processing if the Active Integration Appliance goes down. You can run ha and system commands in this mode.
Unknown
In an HA pair, when an active Integration Appliance does not know the status of the standby Integration Appliance.

Typical HA pair mode combinations

When working with an HA pair, the following mode combinations are typical:
  • ACTIVE_2 and STANDBY - The active machine is communicating with its peer and vice versa. The pair is only highly available after the standby peer has synchronized all the data from the active peer.
  • ACTIVE_2 and IDLE - The active machine has been disconnected from the peer machine most likely as the result of a user issuing the ha disconnect command. Issue the ha connect command to restore the HA pair.
  • ACTIVE_1 and UNKNOWN - The active machine is not communicating with its peer most likely because the peer is rebooting, powered down, or the cables are disconnected.



Feedback | Notices


Timestamp icon Last updated: Wednesday, February 17, 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.cli.doc/CLI_modes.html