Brocade Fabric OS Encryption Administrator’s Guide Supporting NetApp Lifetime Key Manager (LKM) and KeySecure Storage Secure Key Manager (SSKM) Environments (Supporting Fabric OS v7.2.0) - Manual (Page 175)

Fabric OS Encryption Administrator’s Guide (LKM/SSKM) 157
53-1002925-01
Decommissioning LUNs
3
Make sure the LUNs in previously committed LUN configurations and LUN modifications have a
LUN state of Encryption Enabled before creating and committing another batch of LUN
configurations or modifications.
NOTE
A maximum of 25 disk LUNs can be added or modified in a single commit operation. The
maximum commit for tape LUNs is eight. Attempts to commit configurations or modifications
that exceed the maximum commit allowed will fail with a warning. There is a five-second delay
before the commit operation takes effect.
Decommissioning LUNs
A disk device needs to be decommissioned when any of the following occur:
• The storage lease expires for an array, and devices must be returned or exchanged.
• Storage is reprovisioned for movement between departments.
• An array or device is removed from service.
In all cases, all data on the disk media must be rendered inaccessible. Device decommissioning
deletes all information that could be used to recover the data.
After device decommissioning is performed, the following actions occur:
• Metadata on the LUN is erased and the reference is removed from cache on the Brocade
Encryption Switch.
• The LUN state is shown as decommissioned in the key vault.
• The LUN is removed from the container.
NOTE
The key IDs that were used for encrypting the data are returned
When a device decommission operation fails on the encryption group leader for any reason, the
crypto configuration remains uncommitted until a user-initiated commit or a subsequent device
decommission operation issued on the encryption group leader completes successfully. Device
decommission operations should always be issued from a committed configuration. If not, the
operation will fail with the error message An outstanding transaction is pending in Switch/EG. IF
this happens, you can resolve the problems by committing the configuration from the encryption
group leader.
Provided that the crypto configuration is not left uncommitted because of any crypto configuration
changes or a failed device decommission operation issued on a encryption group leader node, this
error message will not be seen for any device decommission operation issued serially on an
encryption group member node. If more than one device decommission operation is tried in an
encryption group from member nodes simultaneously, then this error message is transient and will
go away after device decommission operation is complete. If the device decommissioning
operation fails, retry the operation after some time has passed.
If a LUN is removed when undergoing decommission or is in a decommission failed state, or if a
container hosting the LUN is deleted, you must use the
-
force option on the commit operation
(cryptocfg
--
commit
-
force). Failure to do so causes the commit operation to fail and a
decommission in progress error displays.