HP StorageWorks 8/8 - SAN Switch Release Note page 53

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.
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
HP StorageWorks Fabric OS 6.2.0g release notes 53