Data Center Fabric Manager Enterprise User Manual v10.3.X (53-1001357-01, November 2009)

DCFM Enterprise User Manual 503

53-1001357-01

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.

To swap engines, select one engine from the right tree (see Figure 211) and one unclustered

engine from the list on the left, and click the double-arrow button.

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.

• 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 Management application, or until the second

encryption engine fails.

Invoking failback

To invoke failback to the restarted encryption engine from the Management application, complete

the following steps.

1. Select Configure > Encryption.

The Encryption Center dialog box displays.

2. Select the group to which the encryption engine belongs from the Encryption Devices table,

and click Properties.

The Encryption Group Properties dialog box displays.

3. Click the HA Clusters tab.

4. Select the online encryption engine and click Failback.

5. Click OK on the Encryption Group Properties dialog box.

6. Click Close on the Encryption Center dialog box.