HP StorageWorks 1606 - Extension SAN Switch Release Note page 64

After user configured key ID without commit, CAL doesn't return key
ID value.
Auditcfg does not generate RBAC permission denied messages.
4Gb SAN Switch for c-Class BladeSystem puts out frequent warning
messsages (HIL-1505) that the temperature is above the threshold.
IROUNDUP failure when channel running local to DC04 SAN Director
CUP.
Need to add two more values for SNMP port state that includes "val-
idating (10)" module is being validated and "invalidModule (11)"
module is invalid.
WWN mapping for certain storage systems is incorrect.
RTWR max retries exhausted on DC04 SAN Director after stress test
with POST enabled.
If rekey process are started when a physical target of the backup EE
is offline, failover to that backup EE might not be possible even that
physical target is brought back online later on.
Passive path LUN gets stuck in not ready (Get key from archive) state.
Group leader node create a different key id for the dual path lun after
a configdownload.
Unable to de-register primary key vault when both primary and sec-
ondary key valuts are registered.
Re-keying of LUNs for a VMware host are not completing successfully.
In a 4-node Cluster rekey doesn't resume after slot poweron.
When running active/passive arrays with powerpath, if a subset of
the LUNs are trespassed, I/O does not properly fail over.
Encryption blade went in to a faulty (79) state while running rekey
operation in four node encryption group with 200+ LUNs.
During long running CP hafailover and slotpower cycle test, one En-
cryption blade came up faulty indicating BM-BC Heartbeat dead.
Observed CRITICAL while switch was coming up after hareboot on
Viking.
64
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Workaround prior to code change:
De-register the secondary KV first.
Fixed in FOS 6.3.0
Workaround prior to code change:
Delete container that aborts rekey and
re-start rekey on the container that
doesn't have any kind of reservation
conflict.
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0
Workaround prior to code change:
Avoid trespassing LUNs using
powerpath.
Fixed in FOS 6.3.0
Workaround prior to code change:
Slotpoweroff and slotpower on the
blade to recover.
Fixed in FOS 6.3.0
Fixed in FOS 6.3.0