HP 4400 HP StorageWorks Fabric OS 6.4.1 Release Notes (5697-0760, November 201 - Page 58

with DC SAN Backbone Director, - how to scan

Page 58 highlights

Closed defect summary Solution When an XML string is being converted internally in CALD when the system is running out of memory, it causes an invalid memory access and results in a CALD process crash. Fixed in Fabric OS 6.4.0 TCP connection dropped on encryption switch or encryption blade due Fixed in Fabric OS 6.4.0 to lack of clean-up of locally managed socket Qualys security scan causes Web Linker restart. Fixed in Fabric OS 6.4.0 Host hangs while scanning LUNs. You can scan cleartext LUNs (0 and 1), but cannot scan encrypted LUNs 2 - 7 on certain device types. Related to unsupported Solaris Host Cluster setup, where host sent zero byte length Write commands. 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 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, 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 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 58

  • 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

Solution
Closed defect summary
Fixed in Fabric OS 6.4.0
When an XML string is being converted internally in CALD when the
system is running out of memory, it causes an invalid memory access
and results in a CALD process crash.
Fixed in Fabric OS 6.4.0
TCP connection dropped on encryption switch or encryption blade due
to lack of clean-up of locally managed socket
Fixed in Fabric OS 6.4.0
Qualys security scan causes Web Linker restart.
Fixed in Fabric OS 6.4.0
Host hangs while scanning LUNs. You can scan cleartext LUNs (0 and
1), but cannot scan encrypted LUNs 2 - 7 on certain device types. Re-
lated to unsupported Solaris Host Cluster setup, where host sent zero
byte length Write commands.
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 hap-
pens.
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 dir-
ector.
58