Swapping Engines In An Ha Cluster; Failback Option; Invoking Failback - Brocade Communications Systems StoreFabric SN6500B Administrator's Manual

2
High availability (HA) clusters

Swapping engines in an HA cluster

Swapping engines is useful when replacing hardware. Swapping engines is different from removing
an engine and adding another because when you swap engines, the configured targets on the
former HA cluster member are moved to the new HA cluster member.
1. Select Configure > Encryption from the menu task bar to display the Encryption Center
2. Select an encryption group from the Encryption Center Devices table, then select Group >
To swap engines, select one engine from the High Availability Clusters table and one unclustered
engine from encryption engine from the Non HA Encryption Engines table, then click the
double-arrow.
NOTE
The two engines being swapped must be in the same fabric.

Failback option

The Failback option determines the behavior when a failed encryption engine is restarted. When
the first encryption engine comes back online, the encryption group's failback setting (auto or
manual) determines how the encryption engine resumes encrypting and decrypting traffic to its
encryption targets.
•
•

Invoking failback

To invoke failback to the restarted encryption engine from the BNA client, complete the following
steps:
1. Select Configure > Encryption from the menu task bar to display the Encryption Center
2. Select an encryption group from the Encryption Center Devices table to which the encryption
3. Select the online encryption engine, then click Failback.
4. Click OK, then close the Encryption Center dialog box.
58
dialog box.
HA Cluster from the menu task bar
The Encryption Group Properties dialog box displays, with the HA Clusters tab selected (Refer
to Figure 33).
In auto mode, when the first encryption engine restarts, it automatically resumes encrypting
and decrypting traffic to its encryption targets.
In manual mode, the second encryption engine continues handling the traffic until you
manually invoke failback using the CLI or BNA, or until the second encryption engine fails.
When the encryption engine recovers, it can automatically fail back its CryptoTarget containers
if the second encryption engine is not hosting them.
dialog box (Refer to Figure 1
engine belongs, then click Group > HA Clusters.
The Encryption Group Properties dialog box displays, with the HA Clusters tab selected (Refer
to Figure 33).
on page 14).
Fabric OS Encryption Administrator's Guide (SKM/ESKM)
53-1002721-01