HP Brocade 8/12c Fabric OS Encryption Administrator's Guide - Page 233

Encryption group merge and split use cases 6 SecurityAdmin:switch>cryptocfg --show -hacluster -all Encryption Group Name: brocade_1 Number of HA Clusters: 1 HA cluster name: HAC3 - 2 EE entries Status: Committed WWN Slot Number EE1 => 10:00:00:05:1e:53:89:dd 0 EE2 => 10:00:00:05:1e:53:fc:8a 0 Status Online Online Encryption group merge and split use cases This section describes the following recovery scenarios and related operations: • "A member node failed and is replaced" on page 213 • "A member node reboots and comes back up" on page 214 • "A member node lost connection to the group leader" on page 215 • "A member node lost connection to all other nodes in the encryption group" on page 215 • "Several member nodes split off from an encryption group" on page 216 • "Adjusting heartbeat signaling values" on page 217 • "EG split possibilities requiring manual recovery" on page 217 A member node failed and is replaced Assume N1, N2 and N3 form an encryption group and N2 is the group leader node. N3 and N1 are part of an HA cluster. Assume that N3 failed and you want to replace the failed N3 node with an alternate node N4. Impact When N3 failed, all devices hosted on the encryption engines of this node failed over to the peer encryption engines in N1, and N1 now performs all of the failed node's encryption services. Re-key sessions owned by the failed encryption engine are failed over to N1. Recovery 1. Deregister the node N3 from the group leader node. cryptocfg --dereg -membernode 2. Reclaim the WWN base of the failed Brocade Encryption Switch. cryptocfg --reclaim WWN -membernode 3. Synchronize the crypto configurations across all member nodes. cryptocfg --commit NOTE When attempting to reclaim a failed Brocade Encryption Switch, do not execute cryptocfg --transabort. Doing so will cause subsequent reclaim attempts to fail. Fabric OS Encryption Administrator's Guide 213 53-1002159-03