Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864-01, June 2010)

114 Fabric OS Encryption Administrator’s Guide
53-1001864-01
High Availability (HA) cluster configuration
3
3. Enter cryptocfg --commit to commit the transaction. Any transaction remains in the defined
state until it is committed. The commit operation fails if the HA cluster has less than two
members.
4. Display the HA cluster configuration by entering the cryptocfg
--show -hacluster -all command.
In the following example, the encryption group brocade has one committed HAC1 with two
encryption engines.
SecurityAdmin:switch>cryptocfg --show -hacluster -all
Encryption Group Name: brocade
Number of HA Clusters: 1
HA cluster name: HAC1 - 1 EE entry
Status: Committed
WWN Slot Number Status
11:22:33:44:55:66:77:00 0 Online
10:00:00:05:1e:53:74:87 3 Online
NOTE
An HA cluster configuration must have two encryption engines before you can commit the
transaction with the cryptocfg
--commit command. To commit an incomplete HA cluster, you have
the option to force the commit operation by issuing cryptocfg
--commit -force. Use the forced
commit with caution, because the resulting configuration will not be functional and provide no
failover/failback capabilities.
Adding an encryption engine to an HA cluster
1. Log into the group leader as Admin or SecurityAdmin.
2. Enter the cryptocfg --add -haclustemember command. Specify the HA cluster name and the
encryption engine node WWN. Provide a slot number if the encryption engine is a blade. The
following example adds a Brocade FS8-18 in slot 5 to the HA cluster HAC2.
SecurityAdmin:switch>cryptocfg --add -haclustermember HAC2 \
10:00:00:60:5b:03:1c:90 5
EE Node WWN: 10:00:00:60:5b:03:1c:90 5 Slot number: 5Detected
Add HA cluster member status: Operation succeeded.
3. Add another encryption engine before committing the transaction.