beautypg.com

Brocade Fabric OS Encryption Administrator’s Guide Supporting Key Management Interoperability Protocol (KMIP) Key-Compliant Environments (Supporting Fabric OS v7.1.0) User Manual

Page 304

background image

286

Fabric OS Encryption Administrator’s Guide (KMIP)

53-1002747-02

Reclaiming the WWN base of a failed Brocade Encryption Switch

6

27. Verify that defzone is set as no access.

28. If HA cluster membership for the old Brocade Encryption Switch was in place move container

movement to the new Brocade Encryption Switch using the following procedure.

a. Replace the old EE with the new EE using the following command on the group leader.

Admin:switch> cryptocfg -–replace

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 of Old 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.

29. If HA cluster membership for the old Brocade Encryption Switch was not in place, move

container movement to the new Brocade Encryption Switch using the following procedure.

a. Replace the old EE with the new EE using following command on the group leader.

Admin:switch> cryptocfg -–replace

b. Issue commit.

Admin:switch> cryptocfg --commit

30. 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

2. Reclaim the WWN base of the failed Brocade Encryption Switch.

Admin:switch> cryptocfg --reclaimWWN –membernode [-list]

3. Synchronize the crypto configurations across all member nodes.

Admin:switch> cryptocfg –-commit