HP 1606 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 53

OS 6.3.0 from RC builds on HP StorageWorks 8/80 SAN Switch. This issue

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 53 highlights

Table 9 Fabric OS 6.4.0 closed defects (continued) Closed defect summary Solution Switch panic occurs after daemon iswitchd coredump. With two FCRs Fixed in Fabric OS 6.4.0 in the backbone and both 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, which caused memory issues. Later, iswitchd could coredump due to access to the bad memory. switch is reboot/hafailover when it happens. Encryption switch panic due to daemon termination. In corner case, Fixed in Fabric OS 6.4.0 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]. 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. The parameter auditcfg is not Persistent after reboot. Fixed in Fabric OS 6.4.0 During portloopbacktest with DC SAN Backbone Director, the (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 Fixed in Fabric OS 6.4.0 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 performing a disruptive CP reboot on a director class switch (reboot Fixed in Fabric OS 6.4.0 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. When FCoE max login has been reached, RASLOG message was introduced Fixed in Fabric OS 6.4.0 to indicate FCoE login has been reached. Switch gets nsd panic when connected to a third-party switch with interop Fixed in Fabric OS 6.4.0 mode 3; Fabric OS 6.2 sends invalid frames. 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 Fabric OS Fixed in Fabric OS 6.4.0 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. Software verify error detected appears on console during upgrade to Fabric Fixed in Fabric OS 6.4.0 OS 6.3.0 from RC builds on HP StorageWorks 8/80 SAN Switch. This issue will not be seen in the field. Display of the CP disappeared from Web Tools when the blade experienced Fixed in Fabric OS 6.4.0 a fault. Web Tools message Maximum length reached for your input in Fixed in Fabric OS 6.4.0 Performance Monitoring on Port Throughput and Port Error setup window. Fabric OS 6.4.0 fixes 53

  • 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
Table 9 Fabric OS 6.4.0 closed defects
(continued)
Solution
Closed defect summary
Fixed in Fabric OS 6.4.0
Switch panic occurs after daemon
iswitchd coredump
. With two FCRs
in the backbone and both 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, which caused 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
The parameter
auditcfg
is not Persistent after reboot.
Fixed in Fabric OS 6.4.0
During
portloopbacktest
with DC SAN Backbone Director, the (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 performing 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 introduced
to indicate FCoE login has been reached.
Fixed in Fabric OS 6.4.0
Switch gets nsd panic when connected to a third-party switch with interop
mode 3; 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 Fabric OS
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
Software verify error detected appears on console during upgrade to Fabric
OS 6.3.0 from RC builds on HP StorageWorks 8/80 SAN Switch. This issue
will not be seen in the field.
Fixed in Fabric OS 6.4.0
Display of the CP disappeared from Web Tools when the blade experienced
a fault.
Fixed in Fabric OS 6.4.0
Web Tools message
Maximum length reached for your input
in
Performance Monitoring on Port Throughput and Port Error setup window.
Fabric OS 6.4.0 fixes
53