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

FOS 6.3.0 fixes, either as clear text or encrypted MSA configuration, for example.

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 43 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. FOS 6.3.0 fixes Table 10 lists defects closed in the FOS 6.3.0 firmware release. All fixes from FOS 6.1.2b and 6.2.0g are merged into the 6.3.0 release. Table 10 FOS 6.3.0 closed defects Closed defect summary FICON emulation failing. Solution Fixed in FOS 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 FOS 6.3.0 Fixed in FOS 6.3.0 Workaround prior to code change: If a Host and Target are no longer zoned together, then the user should also remove the associated container (i.e., frame redirect zone) for this Host/Target pair. This will prevent Host/Target communication for this pair via the container (i.e. redirection). FICUD panic and reboot on DCX occurs after executing host command Fixed in FOS 6.3.0 to display the switch. Applications that write to a LUN that is being rekeyed may see I/O errors. Fixed in FOS 6.3.0 Workaround prior to code change: When performing a rekeying operation on the LUN, it is recommended that the customer quiesce access to that LUN. Rekey of LUNs hosted through active/passive ports will not complete Fixed in FOS 6.3.0 if started on the passive path. HP StorageWorks FOS 6.3.0b Release Notes 43

  • 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
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.
FOS 6.3.0 fixes
Table 10
lists defects closed in the FOS 6.3.0 firmware release. All fixes from FOS 6.1.2b and 6.2.0g
are merged into the 6.3.0 release.
Table 10 FOS 6.3.0 closed defects
Solution
Closed defect summary
Fixed in FOS 6.3.0
FICON emulation failing.
Fixed in FOS 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 FOS 6.3.0
Workaround prior to code change:
If
a Host and Target are no longer
zoned together, then the user should
also remove the associated container
(i.e., frame redirect zone) for this
Host/Target pair. This will prevent
Host/Target communication for this
pair via the container (i.e.
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 FOS 6.3.0
FICUD panic and reboot on DCX occurs after executing host command
to display the switch.
Fixed in FOS 6.3.0
Workaround prior to code change:
When performing a rekeying
operation on the LUN, it is
recommended that the customer
quiesce access to that LUN.
Applications that write to a LUN that is being rekeyed may see I/O
errors.
Fixed in FOS 6.3.0
Rekey of LUNs hosted through active/passive ports will not complete
if started on the passive path.
HP StorageWorks FOS 6.3.0b Release Notes
43