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

FOS-FVT- Check Condition Not Propagated On Read to Physical Initi

Page 68 highlights

Rare Instances of warm recovery failure during upgrade due to small timing window in library used by some services. Fixed in FOS 6.3.0 Workaround prior to code change: Issue an additional reboot or hafailover. Fabstateshow log wrapping overwrites useful fabstate data on the switch when interoperating with McDATA switches. Fixed in FOS 6.3.0 Data miscompare during path failover in active/passive array. Fixed in FOS 6.3.0 About the Severity Level on FOS Message Reference. Fixed in FOS 6.3.0 I/O timeouts observed during first time re-key of disk LUNs Fixed in FOS 6.3.0 Adding a tapepool (commit) cause hacluster failover even the (container Fixed in FOS 6.3.0 owner) switch is still disabled. Error message may be seen on console under heavy utilization of in- Fixed in FOS 6.3.0 terface to key vault. Re-key starts and host IO is blocked on failover/failback with mismatched time on EE nodes. Fixed in FOS 6.3.0 FOS-FVT- Check Condition Not Propagated On Read to Physical Initi- Fixed in FOS 6.3.0 ator (PI). Fixed in FOS 6.3.0 FCIP tape pipelining does not propagate task retry identification (TRI). Workaround prior to code change: Disable FCIP Tapepipelining. Several harmless messages gets generated when DCFM tries to discover Fixed in FOS 6.3.0 a large fabric. During stress-to-fail testing of Cold Start/Recovery on a switch with multiple Logical Switches, the local Name Server misses some device entries. Fixed in FOS 6.3.0 Workaround prior to code change: Perform switchdisable/enable on the affected switches. Same device ( WWN ) is visiable in more than 2 fabric using VF function and VT not getting imported. Fixed in FOS 6.3.0 Port Auto Disable - Wrong message when disabling port auto disable. Fixed in FOS 6.3.0 After few hafailovers, FC fast write I/O times out and a few unexpected frame drops are seen on 1 to 2 ports out of 7-8 ports running. Fixed in FOS 6.3.0 Workaround prior to code change: Disable FCFW feature or limit the number of HA Failover sequences to times when IO is not active. Desired distance is editable for the long distance mode L0:Normal initially when the page loads. Fixed in FOS 6.3.0 68

  • 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
Workaround prior to code change:
Issue an additional reboot or
hafailover.
Rare Instances of warm recovery failure during upgrade due to small
timing window in library used by some services.
Fixed in FOS 6.3.0
Fabstateshow log wrapping overwrites useful fabstate data on the
switch when interoperating with McDATA switches.
Fixed in FOS 6.3.0
Data miscompare during path failover in active/passive array.
Fixed in FOS 6.3.0
About the Severity Level on FOS Message Reference.
Fixed in FOS 6.3.0
I/O timeouts observed during first time re-key of disk LUNs
Fixed in FOS 6.3.0
Adding a tapepool (commit) cause hacluster failover even the (container
owner) switch is still disabled.
Fixed in FOS 6.3.0
Error message may be seen on console under heavy utilization of in-
terface to key vault.
Fixed in FOS 6.3.0
Re-key starts and host IO is blocked on failover/failback with mis-
matched time on EE nodes.
Fixed in FOS 6.3.0
FOS-FVT- Check Condition Not Propagated On Read to Physical Initi-
ator (PI).
Fixed in FOS 6.3.0
Workaround prior to code change:
Disable FCIP Tapepipelining.
FCIP tape pipelining does not propagate task retry identification (TRI).
Fixed in FOS 6.3.0
Several harmless messages gets generated when DCFM tries to discover
a large fabric.
Fixed in FOS 6.3.0
Workaround prior to code change:
Perform switchdisable/enable on the
affected switches.
During stress-to-fail testing of Cold Start/Recovery on a switch with
multiple Logical Switches, the local Name Server misses some device
entries.
Fixed in FOS 6.3.0
Same device ( WWN ) is visiable in more than 2 fabric using VF
function and VT not getting imported.
Fixed in FOS 6.3.0
Port Auto Disable - Wrong message when disabling port auto disable.
Fixed in FOS 6.3.0
Workaround prior to code change:
Disable FCFW feature or limit the
number of HA Failover sequences to
times when IO is not active.
After few hafailovers, FC fast write I/O times out and a few unexpected
frame drops are seen on 1 to 2 ports out of 7-8 ports running.
Fixed in FOS 6.3.0
Desired distance is editable for the long distance mode L0:Normal
initially when the page loads.
68