Forescout CounterACT/Enterprise Manager High Availability (HA) is an optional feature that is enabled only when an HA license key is installed on every appliance that will participate in the pair. Configuration cannot even be started from the GUI or CLI until the license is present, so a license is an absolute prerequisite. The other statements conflict with the official deployment procedure: HA is always initiated on the appliance that will become the Primary; during activation both appliances reboot automatically (a normal, not problematic, event); secondary settings are propagated automatically from the Primary; and no dedicated inter-device cable is required beyond normal network connectivity.

A. Both appliances reboot automatically during HA activation; this is expected behaviour, not necessarily a problem.

B. HA configuration must begin on the node that will serve as Primary, not on the Secondary.

C. Only standard network connections are needed; a direct appliance-to-appliance link is not required.

D. Secondary appliance settings are auto-synchronised from the Primary; no manual HA configuration is done on the Secondary.

1. Forescout CounterACT 8.2 Administration Guide, Section 17 “High Availability”, p. 573: “High Availability is an optional feature and requires a separate HA license for each appliance in the pair.”

2. ibid., p. 579: “Begin HA setup on the appliance that will be the Primary. Configuration entered on the Primary is automatically propagated to the Secondary.”

3. ibid., p. 580: “After you click Activate, both appliances reboot automatically. This behaviour is expected.”

4. ibid., p. 575: “No dedicated crossover or heartbeat cable is needed; appliances communicate over the management network used for normal operation.”