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

Fabric OS 6.4.0b fixes

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 69 highlights

Closed defect summary Solution Multiple critical CDR-1003 raslog during supportsave. After a non-disruptive upgrade from Fabric OS version 6.1.x to Fabric OS version 6.2.x, CDR-1003 CRITICAL messages may be posted during a supportSave operation on Brocade 4Gb platforms. With the fix in this release, the critical message is update to Warning and it can be ignored unless it's persistent and not happening during supportsave. Fixed in Fabric OS 6.4.0a Workaround prior to upgrade: Ignore if CDR-1003 happens during supportsave and not persistent. With FICON emulation, core hangs during error recovery. After an Fixed in Fabric OS 6.4.0a FCIP link failure, an FFDC will occur and some traffic across remaining FCIP links will continue to be disrupted. Data Encryption, Manual HA failback command on Fabric OS 6.4.0 fails. Manual failback command (cryptocfg --failback -EE ) issued from node other than failed over node fails with an error. Fixed in Fabric OS 6.4.0a Workaround prior to upgrade: Issue the manual failback command from the node hosting the failed over containers. Fabric OS 6.4.0b fixes Table 11 lists defects closed in the Fabric OS 6.4.0b firmware release. Table 11 Fabric OS 6.4.0b closed defects Closed defect summary Solution A device with a node WWN of zero connected to an NPIV port causes Fixed in Fabric OS 6.4.0b. the switch to panic and reboot about every 20 to 30 minutes when queried by CALD. IP addresses are allowed to be deleted, even when in use by a route, on tunnel configurations with the 1606 Extension SAN Switch, Multiprotocol Extension Blade, 400 MP Router, or Multiprotocol Router Blade. Fixed in Fabric OS 6.4.0b. Workaround prior to upgrade: Issue portcfgshow iproute to find any invalid route entries and delete them. With either two Encryption SAN Switches or Encryption FC blades connected via a single path through a non-encryption switch, the LUNs contained in a CTC (Crypto Target Container) can lose their paths when the non-encryption switch is rebooted. Occurs only when the HA Cluster (HAC) is set for manual failback. This defect is not seen if there are multiple paths through the fabric, so loss of one switch does not create a temporary loss of path. Fixed in Fabric OS 6.4.0b. When F_Port trunking is activated and after the master trunk goes offline, the switch adds the new master trunk to the list of ports, which sends EFP/BF/DIA flood. The ports remain in this state until all N_Ports are taken offline and logged back into the fabric again. Build Fabric (BF) is sent to the AG. AG forwarding the BF to the redundant fabric caused fabric disruption. Fixed in Fabric OS 6.4.0b. When a Multiprotocol Extension Blade and Encryption FC Blade are installed in the same director and the user attempts to set the routing policy to port-based via VE_Port "aptpolicy port_based," it may not take effect and the internal policy could remain as exchanged based routing. Fixed in Fabric OS 6.4.0b. HP StorageWorks Fabric OS 6.4.0c Release Notes 69

  • 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.0a
Workaround prior to upgrade:
Ignore if CDR-1003 happens during
supportsave and not persistent.
Multiple critical CDR-1003 raslog during supportsave. After a non-dis-
ruptive upgrade from Fabric OS version 6.1.x to Fabric OS version
6.2.x, CDR-1003 CRITICAL messages may be posted during a sup-
portSave operation on Brocade 4Gb platforms. With the fix in this re-
lease, the critical message is update to Warning and it can be ignored
unless it's persistent and not happening during supportsave.
Fixed in Fabric OS 6.4.0a
With FICON emulation, core hangs during error recovery. After an
FCIP link failure, an FFDC will occur and some traffic across remaining
FCIP links will continue to be disrupted.
Fixed in Fabric OS 6.4.0a
Workaround prior to upgrade:
Issue the manual failback command
from the node hosting the failed over
containers.
Data Encryption, Manual HA failback command on Fabric OS 6.4.0
fails. Manual failback command (cryptocfg
–
-failback -EE ) issued from
node other than failed over node fails with an error.
Fabric OS 6.4.0b fixes
Table 11
lists defects closed in the Fabric OS 6.4.0b firmware release.
Table 11 Fabric OS 6.4.0b closed defects
Solution
Closed defect summary
Fixed in Fabric OS 6.4.0b.
A device with a node WWN of zero connected to an NPIV port causes
the switch to panic and reboot about every 20 to 30 minutes when
queried by CALD.
Fixed in Fabric OS 6.4.0b.
Workaround prior to upgrade:
Issue
portcfgshow iproute
to
find any invalid route entries and
delete them.
IP addresses are allowed to be deleted, even when in use by a route,
on tunnel configurations with the 1606 Extension SAN Switch, Multipro-
tocol Extension Blade, 400 MP Router, or Multiprotocol Router Blade.
Fixed in Fabric OS 6.4.0b.
With either two Encryption SAN Switches or Encryption FC blades
connected via a single path through a non-encryption switch, the LUNs
contained in a CTC (Crypto Target Container) can lose their paths when
the non-encryption switch is rebooted. Occurs only when the HA Cluster
(HAC) is set for manual failback. This defect is not seen if there are
multiple paths through the fabric, so loss of one switch does not create
a temporary loss of path.
Fixed in Fabric OS 6.4.0b.
When F_Port trunking is activated and after the master trunk goes offline,
the switch adds the new master trunk to the list of ports, which sends
EFP/BF/DIA flood. The ports remain in this state until all N_Ports are
taken offline and logged back into the fabric again. Build Fabric (BF)
is sent to the AG. AG forwarding the BF to the redundant fabric caused
fabric disruption.
Fixed in Fabric OS 6.4.0b.
When a Multiprotocol Extension Blade and Encryption FC Blade are
installed in the same director and the user attempts to set the routing
policy to port-based via VE_Port "aptpolicy port_based,
”
it may not
take effect and the internal policy could remain as exchanged based
routing.
HP StorageWorks Fabric OS 6.4.0c Release Notes
69