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

With either the 1606 Extension SAN Switch or Multiprotocol Extension

Page 70 highlights

With either the 1606 Extension SAN Switch or Multiprotocol Extension Blade, VE tunnel did not come up due to configuration mismatch for tape pipelining. One side shows Write only and the other side shows Write/Read. Fixed in FOS 6.3.0a High CPU load from DCFM performing supportsave causes port to Fixed in FOS 6.3.0a go offline with laser FLT/link reset. Name server database counts do not match for FOS (6.2.1) and MEOS (9.9.0) switches in the same fabric, so host cannot see the device. This occurs when an HBA capable of a FDMI Register HBA (RHBA) command and M-EOS switch are in the same fabric. Fixed in FOS 6.3.0a Switch panic triggered by size-64 kernel message buffer being used up in virtual fabric with logical ISL configured. Fixed in FOS 6.3.0a Workaround prior to code change: Configure only DISLs between switches. During factory install, configdownload does not download some of the FCoE settings in FOS 6.3.0. This issue pertains to the factory only and will not be encountered in the field. Fixed in FOS 6.3.0a Port reference provided to FICON host by Director History Buffer incorrectly references port address rather than port number. This can cause Fixed in FOS 6.3.0a the host to reference the wrong port. With FOS 6.2, B-series switch in interopmode 3 experiences an NSD Fixed in FOS 6.3.0a panic with C-series switch in interop mode. Transient detected error on internal link caused 8-Gb blade to be faulted with reason=5. Fixed in FOS 6.3.0a Workaround prior to code change: Use slotpoweroff and slotpoweron to clear the fault. After downgrading to 6.2.0x from 6.3.0, when you execute the fwconfigure --eport --ST command runs, the threshold will be set to 63, which is not allowed in FOS 6.2. Fixed in FOS 6.3.0a Software verify error detected appears on console during upgrade to 6.3.0 from RC builds on HP StorageWorks 8/80 SAN Fixed in FOS 6.3.0a Switch. This issue will not be seen in the field. Retransmit and Out of Order counters displayed in the portshow fciptunnel command do not show correct values. Fixed in FOS 6.3.0a If the first circuit in the first tunnel is not numbered 0, portshow fciptunnel all -c displays incorrect value (adds line 16 0 un- Fixed in FOS 6.3.0a knwn Disable ---- 0s 0.00 0.00 0 0/0 0). With 1606 Extension SAN Switch or Multiprotocol Extension Blade, FCIP configuration cannot be restored to default setting by using configdefault, even after chassis reboot. Fixed in FOS 6.3.0a HP StorageWorks Encryption SAN Switch or encryption blade drops frames received from the host when the back-end tape becomes unresponsive. Fixed in FOS 6.3.0a HP StorageWorks Multiprotocol Extension Blade faceplate image in WebTools 10-GbE ports should be renamed as XGE ports. Fixed in FOS 6.3.0a 70

  • 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.0a
With either the 1606 Extension SAN Switch or Multiprotocol Extension
Blade, VE tunnel did not come up due to configuration mismatch for
tape pipelining. One side shows
Write only
and the other side
shows
Write/Read
.
Fixed in FOS 6.3.0a
High CPU load from DCFM performing
supportsave
causes port to
go offline with laser FLT/link reset.
Fixed in FOS 6.3.0a
Name server database counts do not match for FOS (6.2.1) and M-
EOS (9.9.0) switches in the same fabric, so host cannot see the device.
This occurs when an HBA capable of a FDMI Register HBA (RHBA)
command and M-EOS switch are in the same fabric.
Fixed in FOS 6.3.0a
Workaround prior to code change:
Configure only DISLs between
switches.
Switch panic triggered by size-64 kernel message buffer being used
up in virtual fabric with logical ISL configured.
Fixed in FOS 6.3.0a
During factory install,
configdownload
does not download some
of the FCoE settings in FOS 6.3.0. This issue pertains to the factory
only and will not be encountered in the field.
Fixed in FOS 6.3.0a
Port reference provided to FICON host by Director History Buffer incor-
rectly references port address rather than port number. This can cause
the host to reference the wrong port.
Fixed in FOS 6.3.0a
With FOS 6.2, B-series switch in interopmode 3 experiences an NSD
panic with C-series switch in interop mode.
Fixed in FOS 6.3.0a
Workaround prior to code change:
Use
slotpoweroff
and
slotpoweron
to clear the fault.
Transient detected error on internal link caused 8-Gb blade to be
faulted with
reason=5
.
Fixed in FOS 6.3.0a
After downgrading to 6.2.0x from 6.3.0, when you execute the
fw-
configure --eport --ST
command runs, the threshold will be
set to 63, which is not allowed in FOS 6.2.
Fixed in FOS 6.3.0a
Software verify error detected
appears on console during
upgrade to 6.3.0 from RC builds on HP StorageWorks 8/80 SAN
Switch. This issue will not be seen in the field.
Fixed in FOS 6.3.0a
Retransmit and Out of Order counters displayed in the
portshow
fciptunnel
command do not show correct values.
Fixed in FOS 6.3.0a
If the first circuit in the first tunnel is not numbered 0,
portshow
fciptunnel all -c
displays incorrect value (adds line
16 0 un-
knwn Disable ---- 0s 0.00 0.00 0 0/0 0
).
Fixed in FOS 6.3.0a
With 1606 Extension SAN Switch or Multiprotocol Extension Blade,
FCIP configuration cannot be restored to default setting by using
configdefault
, even after chassis reboot.
Fixed in FOS 6.3.0a
HP StorageWorks Encryption SAN Switch or encryption blade drops
frames received from the host when the back-end tape becomes unre-
sponsive.
Fixed in FOS 6.3.0a
HP StorageWorks Multiprotocol Extension Blade faceplate image in
WebTools 10-GbE ports should be renamed as XGE ports.
70