Brocade Fabric OS Encryption Administrator's Guide v7.1.0 (53-1002721-01, March 2013)

344 Fabric OS Encryption Administrator’s Guide (SKM/ESKM)
53-1002721-01
Reclaiming the WWN base of a failed Brocade Encryption Switch
6
29. If HA cluster membership for the old Brocade Encryption Switch was in place. Do the following
for moving container movement to the new Brocade Encryption Switch.
a. Replace the old EE with the new EE using the following command on the group leader.
Admin:switch> cryptocfg –replace <WWN of Old BES> <WWN of new BES>
b. Issue commit.
Admin:switch> cryptocfg --commit
c. Replace the HAC membership from the old EE to the new EE using the following command
on the group leader.
Admin:switch> cryptocfg –-replace –haclustermember <HA cluster name> <WWN
of Old BES> <WWN of New BES>
d. Issue commit.
Admin:switch> cryptocfg –-commit
e. If “manual” failback was set on the HA cluster, you must manually fail back the LUNs
owned by the newly replaced Brocade Encryption Switch.
30. If HA cluster membership for the old Brocade Encryption Switch was not in place. Do the
following for moving container to the New BES.
a. Replace the old EE with the new EE using following command on the group leader.
Admin:switch> cryptocfg –replace <WWN of Old BES> <WWN of new BES>
b. Issue commit.
Admin:switch> cryptocfg --commit
31. Check the EG state using the following command to ensure that the entire EG is in a converged
and In Sync state.
Admin:switch> cryptocfg –-show –groupcfg
Reclaiming the WWN base of a failed Brocade Encryption Switch
When a Brocade Encryption Switch fails, to reclaim the WWN base, follow these steps:
1. Locate the Brocade Encryption Switch that has failed and deregister from the encryption
group.
Admin:switch> cryptocfg –-dereg –membernode <switchWWN>
2. Reclaim the WWN base of the failed Brocade Encryption Switch.
Admin:switch> cryptocfg --reclaimWWN –membernode <switchWWN> [-list]
3. Synchronize the crypto configurations across all member nodes.
Admin:switch> cryptocfg –-commit