beautypg.com

Brocade Fabric OS Encryption Administrator’s Guide Supporting RSA Data Protection Manager (DPM) Environments (Supporting Fabric OS v7.2.0) User Manual

Page 307

background image

Fabric OS Encryption Administrator’s Guide (DPM)

287

53-1002922-01

Brocade Encryption Switch removal and replacement

6

20. Export the KAC CSR from the new node and sign the CSR from the CA that signed the failed

node CSR.

21. Import the signed CSR/Cert onto the new node.

22. Register back the signed KAC CSR/Cert onto the new node using the following command.

Admin:switch> cryptocfg --reg –KACcert

23. Remove the existing identity of the failed node from the DPM appliance.

24. Create an identity for the new node, and upload the new node KAC certificate to the DPM

appliance.

25. Check the EE state using the following command to ensure that the EE is online.

Admin:switch> cryptocfg -–show –localEE

26. From the new Brocade Encryption Switch, invoke the following command to set the default

zone as allAccess so the configuration from the existing Fabric is pushed to the new Brocade
Encryption Switch.

Admin:switch> defzone –allaccess

27. Invoke the following command on the new Brocade Encryption Switch.

Admin:switch> cfgsave

28. Replace the FC Cables to the new Brocade Encryption Switch.

29. Invoke the cfgsave command on any switch in that fabric. The fabric configuration from the

existing fabric will be merged into the new Brocade Encryption Switch.

30. Verify that defzone is set as no access.

31. 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 HA cluster membership from the old EE to the new EE using the following

command on the group leader.

Admin:switch> cryptocfg -–replace –haclustermember

of old Brocade Encryption Switch>

d. Issue commit.

Admin:switch> cryptocfg --commit

e. If “manual” failback was set on the HA cluster, user intervention will be required to

manually fail back the LUNs owned by the newly replaced Brocade Encryption Switch.