Fabric OS Encryption Administrator's Guide

138 Fabric OS Encryption Administrator’s Guide
53-1002159-03
High availability cluster configuration
3
• It is recommended that the HA cluster configuration be completed before you configure
storage devices for encryption.
• It is mandatory that the two encryption engines in the HA cluster belong to two different nodes
for true redundancy. This is always the case for Brocade encryption switches, but is not true if
two FS8-18 blades in the same DCX or DCX-4S chassis are configured in the same HA cluster.
In Fabric OS v6.3.0 and later releases, HA cluster creation is blocked when encryption engines
belonging to FS8-18 blades in the same DCX or DCX-4S are specified.
Creating an HA cluster
1. Log in to the group leader as Admin or SecurityAdmin.
2. Enter the cryptocfg
--create -hacluster command. Specify a name for the HA cluster and
optionally add the node WWN of the encryption engine you wish to include in the HA cluster.
Provide a slot number if the encryption engine is a blade. The following example creates an HA
cluster named “HAC1” with two encryption engines.
SecurityAdmin:switch>cryptocfg --create -hacluster HAC 10:00:00:05:1
e:51:94:00 2 10:00:00:05:1e:55:3a:f0 0
Slot Local/
EE Node WWN Number Remote
10:00:00:05:1e:51:94:00 2 Local
Slot Local/
EE Node WWN Number Remote
10:00:00:05:1e:55:3a:f0 0 Remote
Operation succeeded.
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.