HP 4400 HP StorageWorks Fabric OS 6.4.0c Release Notes (5697-0703, September 2 - Page 57

During portloopbacktest with DC SAN Backbone director Log function

Page 57 highlights

Closed defect summary Solution Switch panic after daemon iswitchd coredump. With two FCRs in the back bone and both are connected to same edge fabric through EXports, and edge fabric has MEOS in IM2 mode, upon receiving periodic GE_PT from M-EOS switches, FCR did not handle properly cause memory issues. Later iswitchd could coredump due to access to the bad memory. switch is reboot/hafailover when it happens. Fixed in Fabric OS 6.4.0 Encryption switch panic due to daemon termination. In corner case, Encryption SAN switch or Encryption FC blade did not handle an error case correctly with key attribute retrieval operation in daemon kacd. Before panic, raslog may have [CVLC-1022]. Fixed in Fabric OS 6.4.0 After upgrade from Fabric OS 6.2.x to 6.3.x, RSCNs are not sent to all devices the target is zoned with, so hosts are unable to see the target until all host ports are bounced. Fixed in Fabric OS 6.4.0 Workaround prior to upgrade: Bounce ports to recover, but it should be noted this is a disruptive procedure, so not recommended. portCfgFillWord enhancement for various 8Gb devices. Fixed in Fabric OS 6.4.0 The parameter of auditcfg is not Persistent after reboot. Fixed in Fabric OS 6.4.0 During portloopbacktest with DC SAN Backbone director (L)og function Fixed in Fabric OS 6.4.0 of a diag command is inoperative. Log function works fine with Fabric OS 6.1.0. After removing a blade other than 10/24 FCoE blade from the chassis, Fixed in Fabric OS 6.4.0 CEE tab disappears in the Portadmin GUI Window. Downloading a fabric watch configuration using configdownload after upgrading to 6.2 requires switchdisable. Fixed in Fabric OS 6.4.0 Workaround prior to upgrade: Disable the switchdisable/enable. The crypto device container is not active after configdownload. New crypto device configuration is not pushed to encryption blade. Fixed in Fabric OS 6.4.0 Workaround prior to upgrade: Issue disableEE/enableEE. While doing a disruptive CP reboot on a director class switch (reboot active CP when no standby CP is present), if simultaneous fabric update causes a large volume of F-Class traffic, a potential exists for an edge switch to be faulted due to lack of response from the core director. Fixed in Fabric OS 6.4.0 When FCoE max login has been reached, RASLOG message was intro- Fixed in Fabric OS 6.4.0 duced to indicate FCoE login has been reached. Switch gets nsd panic when connected to 3rd party switch with interop Fixed in Fabric OS 6.4.0 mode 3 with Fabric OS 6.2 sends invalid frames. RTT counters are not displayed correctly for FCIP tunnels on idle switch Fixed in Fabric OS 6.4.0 setup. After firmware upgrade on DC SAN Backbone director from 6.2.0e to 6.3.x, followed by switchdisable, policy change, and enabling some links, RTWRs were observed. This is caused by a route table getting corrupted and can lead to a host crash if on an IFL or ISL. Fixed in Fabric OS 6.4.0 HP StorageWorks Fabric OS 6.4.0c Release Notes 57

  • 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

Solution
Closed defect summary
Fixed in Fabric OS 6.4.0
Switch panic after daemon iswitchd coredump. With two FCRs in the
back bone and both are connected to same edge fabric through EX-
ports, and edge fabric has MEOS in IM2 mode, upon receiving periodic
GE_PT from M-EOS switches, FCR did not handle properly cause memory
issues. Later iswitchd could coredump due to access to the bad memory.
switch is reboot/hafailover when it happens.
Fixed in Fabric OS 6.4.0
Encryption switch panic due to daemon termination. In corner case,
Encryption SAN switch or Encryption FC blade did not handle an error
case correctly with key attribute retrieval operation in daemon kacd.
Before panic, raslog may have [CVLC-1022].
Fixed in Fabric OS 6.4.0
Workaround prior to upgrade:
Bounce ports to recover, but it should
be noted this is a disruptive
procedure, so not recommended.
After upgrade from Fabric OS 6.2.x to 6.3.x, RSCNs are not sent to
all devices the target is zoned with, so hosts are unable to see the target
until all host ports are bounced.
Fixed in Fabric OS 6.4.0
portCfgFillWord enhancement for various 8Gb devices.
Fixed in Fabric OS 6.4.0
The parameter of auditcfg is not Persistent after reboot.
Fixed in Fabric OS 6.4.0
During portloopbacktest with DC SAN Backbone director (L)og function
of a diag command is inoperative. Log function works fine with Fabric
OS 6.1.0.
Fixed in Fabric OS 6.4.0
After removing a blade other than 10/24 FCoE blade from the chassis,
CEE tab disappears in the Portadmin GUI Window.
Fixed in Fabric OS 6.4.0
Workaround prior to upgrade:
Disable the switchdisable/enable.
Downloading a fabric watch configuration using configdownload after
upgrading to 6.2 requires switchdisable.
Fixed in Fabric OS 6.4.0
Workaround prior to upgrade:
Issue disableEE/enableEE.
The crypto device container is not active after configdownload. New
crypto device configuration is not pushed to encryption blade.
Fixed in Fabric OS 6.4.0
While doing a disruptive CP reboot on a director class switch (reboot
active CP when no standby CP is present), if simultaneous fabric update
causes a large volume of F-Class traffic, a potential exists for an edge
switch to be faulted due to lack of response from the core director.
Fixed in Fabric OS 6.4.0
When FCoE max login has been reached, RASLOG message was intro-
duced to indicate FCoE login has been reached.
Fixed in Fabric OS 6.4.0
Switch gets nsd panic when connected to 3rd party switch with interop
mode 3 with Fabric OS 6.2 sends invalid frames.
Fixed in Fabric OS 6.4.0
RTT counters are not displayed correctly for FCIP tunnels on idle switch
setup.
Fixed in Fabric OS 6.4.0
After firmware upgrade on DC SAN Backbone director from 6.2.0e to
6.3.x, followed by switchdisable, policy change, and enabling some
links, RTWRs were observed. This is caused by a route table getting
corrupted and can lead to a host crash if on an IFL or ISL.
HP StorageWorks Fabric OS 6.4.0c Release Notes
57