HP 1606 HP StorageWorks Fabric OS 6.3.1c Release Notes (5697-0509 September 2 - Page 47

Fabric OS 6.3.0 fixes, Table 7 Fabric OS 6.3.0 closed defects

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

Page 47 highlights

NOTE: When configuring multipath LUNs, care should be taken to add LUN 0 on all of the paths, subject to the following considerations: • If LUN 0 presented by the back-end target is a controller LUN (not a disk LUN; that is, not visible in the discoverLUN output), add LUN 0 to the container as a clear text LUN. Make sure all of the paths have this LUN 0 added for MPIO operation (EVA configuration, for example). • If LUN 0 presented by the back-end target is a disk LUN, LUN 0 can be added to the container either as clear text or encrypted (MSA configuration, for example). • For HP-UX, LUN 0 can appear as 0x0 or 0x400, but both of them are LUN 0 only and should be treated alike. Fabric OS 6.3.0 fixes Table 7 lists defects closed in the Fabric OS 6.3.0 firmware release. All fixes from Fabric OS 6.1.2b and 6.2.0g are merged into the 6.3.0 release. Table 7 Fabric OS 6.3.0 closed defects Closed defect summary FICON emulation failing. Solution Fixed in Fabric OS 6.3.0 Pending Merge:VTs/VIs disappear when rebooting the HP StorageWorks Encryption SAN Switch that has all the physical connections to targets and initiators. As a result of creating a cryptoLUN, a host can use a target even though they are not in the same zone. Fixed in Fabric OS 6.3.0 Fixed in Fabric OS 6.3.0 Workaround prior to code change: If a Host and Target are no longer zoned together, the user should also remove the associated container (the frame redirect zone) for this Host/Target pair. This prevents Host/Target communication for this pair via the container (that is, redirection). FICUD panic and reboot on DCX occurs after executing a host command to display the switch. Applications that write to a LUN that is being rekeyed may see I/O errors. Fixed in Fabric OS 6.3.0 Fixed in Fabric OS 6.3.0 Workaround prior to code change: When performing a rekeying operation on the LUN, HP recommends that you quiesce access to that LUN. Rekey of LUNs hosted through active/passive ports do not complete if started on the passive path. Fixed in Fabric OS 6.3.0 HP StorageWorks Fabric OS 6.3.1c Release Notes 47

  • 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
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
NOTE:
When configuring multipath LUNs, care should be taken to add LUN 0 on all of the paths, subject to
the following considerations:
•
If LUN 0 presented by the back-end target is a controller LUN (not a disk LUN; that is, not visible
in the
discoverLUN
output), add LUN 0 to the container as a clear text LUN. Make sure all of
the paths have this LUN 0 added for MPIO operation (EVA configuration, for example).
•
If LUN 0 presented by the back-end target is a disk LUN, LUN 0 can be added to the container
either as clear text or encrypted (MSA configuration, for example).
•
For HP-UX, LUN 0 can appear as 0x0 or 0x400, but both of them are LUN 0 only and should be
treated alike.
Fabric OS 6.3.0 fixes
Table 7
lists defects closed in the Fabric OS 6.3.0 firmware release. All fixes from Fabric OS 6.1.2b
and 6.2.0g are merged into the 6.3.0 release.
Table 7 Fabric OS 6.3.0 closed defects
Solution
Closed defect summary
Fixed in Fabric OS 6.3.0
FICON emulation failing.
Fixed in Fabric OS 6.3.0
Pending Merge:VTs/VIs disappear when rebooting the HP Storage-
Works Encryption SAN Switch that has all the physical connections
to targets and initiators.
Fixed in Fabric OS 6.3.0
Workaround prior to code change:
If
a Host and Target are no longer
zoned together, the user should also
remove the associated container (the
frame redirect zone) for this
Host/Target pair. This prevents
Host/Target communication for this
pair via the container (that is,
redirection).
As a result of creating a cryptoLUN, a host can use a target even
though they are not in the same zone.
Fixed in Fabric OS 6.3.0
FICUD panic and reboot on DCX occurs after executing a host com-
mand to display the switch.
Fixed in Fabric OS 6.3.0
Workaround prior to code change:
When performing a rekeying
operation on the LUN, HP
recommends that you quiesce access
to that LUN.
Applications that write to a LUN that is being rekeyed may see I/O
errors.
Fixed in Fabric OS 6.3.0
Rekey of LUNs hosted through active/passive ports do not complete
if started on the passive path.
HP StorageWorks Fabric OS 6.3.1c Release Notes
47