HP Brocade 8/12c Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864 - Page 206
Deleting an HA cluster member, Performing a manual failback of an encryption engine
View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 206 highlights
6 Encryption group and HA cluster maintenance Deleting an HA cluster member This command dissolves the HA cluster and removes failover capability from the participating encryption engines. 1. Log into the group leader as Admin or SecurityAdmin. 2. Enter the cryptocfg --delete -hacluster command. Specify the name of the HA cluster you wish to delete. SecurityAdmin:switch>cryptocfg --delete -hacluster HAC1 Delete HA cluster status: Operation succeeded. 3. Enter the cryptocfg --commit command to commit the transaction. Performing a manual failback of an encryption engine By default, failback occurs automatically if an encryption engine that failed was replaced or comes back online. When manual failback policy is set in the encryption group, you must invoke a manual failback of the encryption engine after the failing encryption engine was restored or replaced. Failback includes all of the encryption engine's target associations. Failback returns all encryption operations to the original encryption engine after it has been restored, or it transfers operations to a replacement encryption engine if the original encryption engine was replaced. The failback operation can only be performed within an HA cluster. 1. Log into the group leader as Admin or SecurityAdmin. 2. Enter the cryptocfg --failback -EE command. Specify the node WWN of the encryption engine to which failover occurred earlier and which is now performing all encryption tasks (current encryption engine), followed by the node WWN of the encryption engine to which failback should occur ("new" encryption engine). Specify a slot number if the encryption engine is a blade. SecurityAdmin:switch>cryptocfg --failback -EE 10:00:00:05:1e:53:4c:91 \ 10:00:00:05:1e:39:53:67 Operation Succeeded Failover/failback example The following example illustrates the states associated with the encryption engines during an active failover and failback process. • EE2 fails over to EE1. SecurityAdmin:switch>cryptocfg --show -hacluster -all Encryption Group Name: brocade 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 - Failover active Offline 188 Fabric OS Encryption Administrator's Guide 53-1001864-01