HP StorageWorks 1606 HP StorageWorks FOS 6.3.0b Release Notes (5697-0360, Apri - Page 64

Fixed in FOS 6.3.0, doesn't have any kind of reservation

Page 64 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74

Fixed in FOS 6.3.0
After user configured key ID without commit, CAL doesn't return key
ID value.
Fixed in FOS 6.3.0
Auditcfg does not generate RBAC permission denied messages.
Fixed in FOS 6.3.0
4Gb SAN Switch for c-Class BladeSystem puts out frequent warning
messsages (HIL-1505) that the temperature is above the threshold.
Fixed in FOS 6.3.0
IROUNDUP failure when channel running local to DC04 SAN Director
CUP.
Fixed in FOS 6.3.0
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.
Fixed in FOS 6.3.0
WWN mapping for certain storage systems is incorrect.
Fixed in FOS 6.3.0
RTWR max retries exhausted on DC04 SAN Director after stress test
with POST enabled.
Fixed in FOS 6.3.0
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.
Fixed in FOS 6.3.0
Passive path LUN gets stuck in not ready (Get key from archive) state.
Fixed in FOS 6.3.0
Group leader node create a different key id for the dual path lun after
a configdownload.
Fixed in FOS 6.3.0
Workaround prior to code change:
De-register the secondary KV first.
Unable to de-register primary key vault when both primary and sec-
ondary key valuts are registered.
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.
Re-keying of LUNs for a VMware host are not completing successfully.
Fixed in FOS 6.3.0
In a 4-node Cluster rekey doesn't resume after slot poweron.
Fixed in FOS 6.3.0
Workaround prior to code change:
Avoid trespassing LUNs using
powerpath.
When running active/passive arrays with powerpath, if a subset of
the LUNs are trespassed, I/O does not properly fail over.
Fixed in FOS 6.3.0
Workaround prior to code change:
Slotpoweroff and slotpower on the
blade to recover.
Encryption blade went in to a faulty (79) state while running rekey
operation in four node encryption group with 200+ LUNs.
Fixed in FOS 6.3.0
During long running CP hafailover and slotpower cycle test, one En-
cryption blade came up faulty indicating BM-BC Heartbeat dead.
Fixed in FOS 6.3.0
Observed CRITICAL while switch was coming up after hareboot on
Viking.
64