Replacing An Ha Cluster Member - 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

Replacing an HA cluster member

1. Log in to the group leader as Admin or SecurityAdmin.
2. Enter the cryptocfg
3. Enter cryptocfg
Case 1: Replacing a failed encryption engine in an HA cluster
Assume a working HA cluster with two operational encryption engines, EE1 and EE2. The target T1
is hosted on EE1 and target T2 is hosted on EE2. Refer to
EE2 fails and generates an offline notification. The target hosted on EE2 (T2 in this case)
automatically fails over to EE1. Even though the target T2 is now hosted on EE1 because of the
failover process, the target association is still EE2, and the container status is displayed on the
hosting node as failover. Use the cryptocfg
stat command to display the container status.
-
1. Invoke the cryptocfg
2. Commit the transaction. If failback mode is set to auto, the target (T2) which failed over earlier
3. Invoke the cryptocfg
4. Invoke the cryptocfg
5. After the transaction is committed, remove the failed encryption engine from the encryption
Fabric OS Encryption Administrator's Guide (SKM/ESKM)
53-1002721-01
replace
--
node WWN of the encryption engine to be replaced, and the node WWN of the replacement
encryption engine. Provide a slot number if the encryption engine is a blade. The replacement
encryption engine must be part of the same encryption group as the encryption engine that is
replaced.
SecurityAdmin:switch>cryptocfg --replace -haclustermember HAC2 \
10:00:00:05:1e:53:4c:91 10:00:00:05:1e:39:53:67
Replace HA cluster member status: Operation Succeeded.
commit to commit the transaction.
--
replace
--
the failed encryption engine (EE2) with another encryption engine (EE3). This operation
effectively removes the failed encryption engine (EE2) from the HA cluster and adds the
replacement encryption engine (EE3) to the HA cluster. The target associations (T2) from the
failed encryption engine (EE2) are transferred to the replacement encryption engine (EE3).
to EE1 automatically fails back to the replaced encryption engine (EE3).
reclaimWWN
--
the DCX Backbone chassis and the slot number of the encryption engine to be removed.
commit command to sync the configuration in the encryption group.
--
group.
Encryption group and HA cluster maintenance
haClusterMember command. Specify the HA cluster name, the
-
Figure
show
container <crypto target container name>
--
-
haclustermember command on the group leader to replace
-
EE command on the group leader followed by WWN of
-
104.
6
307

Advertisement

Table of Contents
loading

This manual is also suitable for:

Fabric os 7.1.0

Table of Contents