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

stuck as G_Port. F_Ports get stuck as G_Ports after AG N_Port failover.

Page 70 highlights

Closed defect summary Solution Data Encryption, tape containers get stuck in login busy state after performing ISL disruption tests. Performing HA failover by toggling ISL between HA cluster members can cause containers to be not hosted with reason login busy. Fixed in Fabric OS 6.4.0a Workaround prior to upgrade: Do not connect target devices to BES directly; connect them to an L2 switch. In AG mode, N_Port failover results in F_Ports with attached hosts getting stuck as G_Port. F_Ports get stuck as G_Ports after AG N_Port failover. This occurs when there is a change in the base address for the N_Port due to failover, or when there is no wwn-area mapping for few devices and due to the login sequence of these devices, the PIDS assigned conflicted with the already allocated PID to another device, resulting in the F_Ports getting stuck as G_Ports. Fixed in Fabric OS 6.4.0a Workaround prior to upgrade: Use portdisable/enable. In FICON environment, when CHPs are very busy, CUP may report many IFCCs. Fixed in Fabric OS 6.4.0a When running 200 ms delay and 1% packet loss after four days of run Fixed in Fabric OS 6.4.0a time, an IPSec enabled FCIP circuit bounced. Tape drives fail when running over FCR with EX_Ports in Open mode. The REC accept payload is incorrect. If host to tape I/O traverses FCR and includes an edge fabric, the tape drives run for a bit and then fail due to REC ACC is not processed correctly if the EX_Port is operating in IM3/Open mode. Fixed in Fabric OS 6.4.0a Abort in FICON Tape Read emulation if Attention status received between status and status accept. Fixed in Fabric OS 6.4.0a Workaround prior to upgrade: Disable FICON Emulation. In FICON environment, IFCCs are seen when enabling ICL ports with Fixed in Fabric OS 6.4.0a Lossless DLS enabled, traffic can be adversely affected. Port-based routing frames were out of order when FCP image pairs concurrently initiated exchanges as originators over GE ports. Thirdparty device has very poor performance over FCIP link between two 1606 Extension SAN Switches over 1G GE port. Same issue applies to multiprotocol extension blades. Fixed in Fabric OS 6.4.0a Multiple critical CDR-1003 raslog during supportsave. After a nondisruptive upgrade from Fabric OS 6.1.x to 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 is persistent and not occurring during supportsave. Fixed in Fabric OS 6.4.0a Workaround prior to upgrade: Ignore if CDR-1003 occurs during supportsave and is not persistent. With FICON emulation, core hangs during error recovery. After an FCIP link failure, an FFDC occurs and some traffic across remaining FCIP links continue to be disrupted. Fixed in Fabric OS 6.4.0a 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. 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
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80

Solution
Closed defect summary
Fixed in Fabric OS 6.4.0a
Workaround prior to upgrade:
Do not connect target devices to BES
directly; connect them to an L2
switch.
Data Encryption, tape containers get stuck in login busy state after
performing ISL disruption tests. Performing HA failover by toggling ISL
between HA cluster members can cause containers to be not hosted
with reason
login busy
.
Fixed in Fabric OS 6.4.0a
Workaround prior to upgrade:
Use
portdisable/enable
.
In AG mode, N_Port failover results in F_Ports with attached hosts getting
stuck as G_Port. F_Ports get stuck as G_Ports after AG N_Port failover.
This occurs when there is a change in the base address for the N_Port
due to failover, or when there is no wwn-area mapping for few devices
and due to the login sequence of these devices, the PIDS assigned
conflicted with the already allocated PID to another device, resulting in
the F_Ports getting stuck as G_Ports.
Fixed in Fabric OS 6.4.0a
In FICON environment, when CHPs are very busy, CUP may report
many IFCCs.
Fixed in Fabric OS 6.4.0a
When running 200 ms delay and 1% packet loss after four days of run
time, an IPSec enabled FCIP circuit bounced.
Fixed in Fabric OS 6.4.0a
Tape drives fail when running over FCR with EX_Ports in Open mode.
The REC accept payload is incorrect. If host to tape I/O traverses FCR
and includes an edge fabric, the tape drives run for a bit and then fail
due to REC ACC is not processed correctly if the EX_Port is operating
in IM3/Open mode.
Fixed in Fabric OS 6.4.0a
Workaround prior to upgrade:
Disable FICON Emulation.
Abort in FICON Tape Read emulation if Attention status received
between status and status accept.
Fixed in Fabric OS 6.4.0a
In FICON environment, IFCCs are seen when enabling ICL ports with
Lossless DLS enabled, traffic can be adversely affected.
Fixed in Fabric OS 6.4.0a
Port-based routing frames were out of order when FCP image pairs
concurrently initiated exchanges as originators over GE ports. Third-
party device has very poor performance over FCIP link between two
1606 Extension SAN Switches over 1G GE port. Same issue applies
to multiprotocol extension blades.
Fixed in Fabric OS 6.4.0a
Workaround prior to upgrade:
Ignore if CDR-1003 occurs during
supportsave
and is not persistent.
Multiple critical CDR-1003 raslog during
supportsave
. After a non-
disruptive upgrade from Fabric OS 6.1.x to 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 is persistent and not occurring
during
supportsave
.
Fixed in Fabric OS 6.4.0a
With FICON emulation, core hangs during error recovery. After an
FCIP link failure, an FFDC occurs and some traffic across remaining
FCIP links 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.
70