High availability clusters, Ha cluster configuration rules, Figure 36 – Brocade Fabric OS Encryption Administrator’s Guide Supporting RSA Data Protection Manager (DPM) Environments (Supporting Fabric OS v7.2.0) User Manual

Page 71

Advertising
background image

Fabric OS Encryption Administrator’s Guide (DPM)

51

53-1002922-01

High availability clusters

2

FIGURE 36

Engine Operations tab

3. Select the engine to replace from the Engine list.

4. Select the engine to use as the replacement from the Replacement list, then click Replace.

All containers hosted by the current engine (Engine list) are replaced by the new engine
(Replacement list).

High availability clusters

A high availability (HA) cluster is a group of exactly two encryption engines (EEs). One encryption
engine can take over encryption and decryption tasks for the other encryption engine, if that
member fails or becomes unreachable.

When creating a new HA cluster, add one engine to create the cluster, then add the second engine.
You can make multiple changes to the HA clusters list; the changes are not applied to the switch
until you click OK.

HA cluster configuration rules

The following rules apply when configuring an HA cluster:

The encryption engines that are part of an HA cluster must belong to the same encryption
group and be part of the same fabric.

An HA cluster cannot span fabrics and it cannot provide failover/failback capability within a
fabric transparent to host MPIO software.

HA cluster configuration and related operations must be performed on the group leader.

HA clusters of FS8-18 blades should not include blades in the same DCX Backbone chassis.

Advertising