Description of terms used in resiliency and recovery

Failback

Occurs after a failed Appliance reconnects to the Enterprise Manager and regains control of the endpoints and network devices previously distributed to recipient Appliances.

Failback

Failed Appliance

An Appliance that has a malfunction. This occurs when the Enterprise Manager fails to connect to the Appliance at the operating system level for a defined period of time. Attempts by the Enterprise Manager to connect to it through port 13000 result in connection time outs. For example, if the Appliance is unplugged or in the event of a natural disaster.

About Failover and Failback

Failover Assignment

The range of endpoints and network devices transferred to a recipient Appliance after failover.

About Failover and Failback

Failover Cluster

A group of geographically/logically connected Appliances, such as those at a data center. Appliances within a failover cluster that fail, can fail over to other Appliances in the cluster.

Failover Clusters

Failover Clustering

A resiliency solution implemented with clusters of Appliances. Redundancy is achieved by defining clusters of Appliances that can automatically take over discovery, assessment, and control in case of single or multiple Appliance failure within the cluster/s.

About Forescout Resiliency and Recovery Solutions

Failover Excess

Number of endpoints that exceed Appliance capacity after a failover.

These endpoints are not fully handled by the Appliance, meaning that not all of their host properties are fully resolved, and they will not match policies that depend on such unresolved properties. As a result, relevant actions will not be applied to these endpoints.

Handling Endpoints that Exceed Capacity

Failover Scope

A group of one or more failover clusters. Allows failover across clusters.

Failover Scope

Original Assignment

The range of endpoints and network devices originally handled by the recipient Appliance, before failover.

About Failover and Failback

Recipient Appliance

A functioning Appliance managed by the same Enterprise Manager as the failed Appliance which takes over handling of the range of transferred endpoints and network devices after a failover.

About Failover and Failback

Active Node

The device in a high availability pair that is currently handling discovery, assessment, and control of endpoints.

High Availability Pairing

High Availability Pairing

A resiliency solution implemented in pairs of two devices. Redundancy is achieved by assigning an Active node and a Standby node. The Standby node automatically takes over discovery, assessment, and control in case the Active node fails.

About Forescout Platform Resiliency and Recovery Solutions

Primary Node

The node you use to set up high availability. It is initially the Active node.

High Availability Pairing

Secondary Node

The node that you set up to take over if the primary node fails. It is initially the Standby node.

High Availability Pairing

Standby Node

The backup device in a high availability pair that takes over if the Active Node fails.

High Availability Pairing

Pingable Host

IP address of a host that is tested to check if the management interface is Reachable or Not Reachable.

Out of Band Configuration

This feature defines an additional out of band management interface.

Disaster Recovery for Enterprise Manager

A recovery solution implemented in pairs of two Enterprise Managers. Redundancy is achieved by defining a Recovery Enterprise Manager that is manually triggered to take over from an Enterprise Manager that is no longer functioning as a result of a disaster.

About Forescout Platform Resiliency and Recovery Solutions

Recovery Enterprise Manager

A backup Enterprise Manager that is manually triggered to take over from an Enterprise Manager that is no longer functioning as a result of a disaster.

About Forescout Platform Resiliency and Recovery Solutions