HP A7533A - Brocade 4Gb SAN Switch Base Release Note page 54

An encrypted LUN goes into the internal encryption engine (EE) LUN
state (Disabled (key not in sync)) as a result of rekeying and
High Availability Cluster (HAC)/Data Encryption Key (DEK) cluster
failover and failback. This results in the encrypted LUN not being
available for crypto operations.
An Encryption SAN Switch goes into the faulty state after alternately
rebooting the two encryption switches in the group with the physical
connectivity to the targets and initiators. This results in the faulty encryp-
tion switch not being available for crypto operations.
After rebooting an Encryption SAN Switch of an HAC that has con-
nectivity to the physical targets and initiators, all of the crypto targets
are lost in the HAC. LUNs that were part of the lost crypto target con-
tainers are not available for crypto operations.
An Encryption SAN Switch shows Encryption Engine busy when
continuously disabling/enabling I/O sync ports of the encryption
switch. This results in the encryption switch and EE not being available
for crypto operations.
During an overnight stress test of rekey and ISL disable/enable cycles,
one host experienced write failures to encrypted LUNs, while a second
host writing to the same targets did not experience any problems.
While rekey operations are in progress, disrupting the I/O sync link
causes rekey operations to hang.
A rekey operation hangs as a result of failing over to a path that no
longer has access to the physical target. The rekey operation is not
completed.
During I/O and crypto operations, three LUNs in an encryption con-
tainer show Key ID Unavailable, and one LUN shows inquiry
failed. However, all LUNs are fully functional with no issues in all
other encryption containers.
Mixing Fibre Channel FastWrite (FCFW) and non-FCFW flows can
cause dcam entries to be set incorrectly. The FCFW flow appears to
fail without any port-filter counters being incremented, indicating that
the FCFW frames were seen.
The rekey operation restarts, but hangs after all EEs in the encryption
group are rebooted.
Rekeyed LUNs remain in the Not Ready (Getting key from
archive) state when the SKM (key vault) goes down, and does not
recover even after the key vault is back online. LUNs cannot be re-
covered even after removing them from and adding them back to the
target container.
A persistently disabled GE port on an HP MP Router blade loses its
persistency after hafailover, such that the port is simply disabled,
rather than persistently disabled.
A passive path LUN gets stuck in the Not Ready (Getting key
from archive) state when running a test that periodically breaks
the Ethernet connection to the primary key vault.
54
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Workaround prior to update: Reboot
the Encryption engine (EE).
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g
Fixed in Fabric OS 6.2.0g