Creating An Ha Cluster - Brocade Communications Systems StoreFabric SN6500B Administrator's Manual

Brocade fabric os encryption administrator's guide v7.1.0 (53-1002721-01, march 2013)
Hide thumbs Also See for StoreFabric SN6500B:
Table of Contents

Advertisement

Creating an HA cluster

1. Log in to the group leader as Admin or FabricAdmin.
2. Enter the cryptocfg
3. Enter cryptocfg
4. Display the HA cluster configuration by entering the cryptocfg
NOTE
An HA cluster configuration must have two encryption engines before you can commit the
transaction with the cryptocfg
the option to force the commit operation by issuing cryptocfg
commit with caution, because the resulting configuration will not be functional and provide no
failover/failback capabilities.
Fabric OS Encryption Administrator's Guide (SKM/ESKM)
53-1002721-01
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 Backbone 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 Backbone chassis are specified.
create
--
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.
FabricAdmin: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
EE Node WWN
Number
10:00:00:05:1e:51:94:00
Slot
EE Node WWN
Number
10:00:00:05:1e:55:3a:f0
Operation succeeded.
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.
. In the following example, the encryption group brocade has one committed HAC1
command
with two encryption engines.
FabricAdmin:switch>cryptocfg --show -hacluster -all
Encryption Group Name: brocade
Number of HA Clusters: 1
HA cluster name: HAC1 - 1 EE entry
Status:
Committed
WWN
11:22:33:44:55:66:77:00
10:00:00:05:1e:53:74:87
High availability cluster configuration
hacluster command. Specify a name for the HA cluster and
-
Local/
Remote
2
Local
Local/
Remote
0
Remote
Slot Number
Status
0
Online
3
Online
commit command. To commit an incomplete HA cluster, you have
--
show
hacluster
--
-
commit
force. Use the forced
--
-
3
all
-
155

Advertisement

Table of Contents
loading

This manual is also suitable for:

Fabric os 7.1.0

Table of Contents