HP StorageWorks 1606 HP StorageWorks Fabric OS 6.3.0 release notes (5697-0358, - Page 65

Fixed in Fabric OS 6.3.0, Encryption blade went in to a faulty 79 state while running rekey

Get HP StorageWorks 1606 - Extension SAN Switch PDF manuals and user guides View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 65 highlights

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 Fabric OS 6.3.0 WWN mapping for certain storage systems is incorrect. Fixed in Fabric OS 6.3.0 RTWR max retries exhausted on DC04 SAN Director after stress test Fixed in Fabric OS 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 Fabric OS 6.3.0 Passive path LUN gets stuck in not ready (Get key from archive) state. Fixed in Fabric OS 6.3.0 Group leader node create a different key id for the dual path lun after Fixed in Fabric OS 6.3.0 a configdownload. Unable to de-register primary key vault when both primary and secondary key valuts are registered. Fixed in Fabric OS 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 Fabric OS 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 Fabric OS 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 Fabric OS 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 Fabric OS 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. Switchshow lines for FCoE ports should always be in short format. Fixed in Fabric OS 6.3.0 Fixed in Fabric OS 6.3.0 Fixed in Fabric OS 6.3.0 If user selects authentication type as "all", in interop modes the default authentication type is still FCAP between FOS switches. Fixed in Fabric OS 6.3.0 Workaround prior to code change: .csv file related changes are checked-in by the CLI gatekeeper. so resolving this TR. Fabric watch is allows setting of the Traits and Alarm configuration Fixed in Fabric OS 6.3.0 even when no alarms are available for all of the classes in WebTools. HP StorageWorks Fabric OS 6.3.0 release notes 65

  • 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
Fixed in Fabric OS 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 Fabric OS 6.3.0
WWN mapping for certain storage systems is incorrect.
Fixed in Fabric OS 6.3.0
RTWR max retries exhausted on DC04 SAN Director after stress test
with POST enabled.
Fixed in Fabric OS 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 Fabric OS 6.3.0
Passive path LUN gets stuck in not ready (Get key from archive) state.
Fixed in Fabric OS 6.3.0
Group leader node create a different key id for the dual path lun after
a configdownload.
Fixed in Fabric OS 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 Fabric OS 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 Fabric OS 6.3.0
In a 4-node Cluster rekey doesn't resume after slot poweron.
Fixed in Fabric OS 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 Fabric OS 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 Fabric OS 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 Fabric OS 6.3.0
Observed CRITICAL while switch was coming up after hareboot on
Viking.
Fixed in Fabric OS 6.3.0
Switchshow lines for FCoE ports should always be in short format.
Fixed in Fabric OS 6.3.0
Workaround prior to code change:
.csv file related changes are
checked-in by the CLI gatekeeper. so
resolving this TR.
If user selects authentication type as "all", in interop modes the default
authentication type is still FCAP between FOS switches.
Fixed in Fabric OS 6.3.0
Fabric watch is allows setting of the Traits and Alarm configuration
even when no alarms are available for all of the classes in WebTools.
HP StorageWorks Fabric OS 6.3.0 release notes
65