You are on page 1of 3

TE CHNI C AL SUPPORT BUL LETIN

Se pte mb er 2 3, 2 00 9

TSB 2009- 059- A


(REVISED)

SEVERITY: Medium - Operational

PRO D U CT S A FF E CT E D:

Brocade Access Gateways running FabricOS firmware prior to FabricOS v6.0.1.


CORRECTED IN RELEASE:

The resolution for this issue is included in FabricOS v5.3.2c (available 9/30/09), v6.0.1 and higher.

BULLETIN OVERVIEW
F_Port devices attached to a Brocade Access Gateway (AG) fail to login to the core fabric through
the attached N_Port.

PROBLEM STATEMENT
At some point, certain HBAs will do explicit LOGO (logout) from the fabric, which removes the
original device area route internal to the AG. When the device tries to log back into the fabric, the
switch may fail to re-add this area device route back into the AG. Any attempt to bring this F_Port
back online will fail until the N_port where this F_Port is mapped is toggled or this F_Port is
mapped to a different N_Port or switch is rebooted or the firmware is upgraded to the corrected
version.
RISK ASSESSMENT
Customer may lose connectivity between host attached to AG and the rest of the fabric.

2009 Brocade Communications Systems, Inc. All Rights Reserved. TSB 2009-059-A

SYMPTO MS

Customers host device attached to an AG will be offline and will show a G_Port status.
Customer will see the following error on the AG when executing the switchshow command:
(Fabric Login failed zero/duplicate AL_PA)

WORKAROUND
Three workarounds exist:
1. Customer can toggle (portdisable/enable) the Nport where the Fport in G-port state is
mapped. When the Nport comes back online, the routes are rewritten correctly.
2. Customer can remap the F-Port from the originally assigned N_Port to an alternate N_Port
in the attached fabric using the ag mapset command.
3. Customer can reboot the AG and the routes will be re-written correctly.
If the workaround#2 is attempted, customer may see warning message like duplicate WWN in the
fabrics Nameserver. Customer can locate the duplicate WWN in the fabrics Nameserver using the
nsshow command and then locating the phantom device in the Nameserver. A
portdisable/portenable of this phantom device will then clear the issue.
The ag --show command is the only way to know where the device is actually logged in when this
issue occurs Execute the following commands to determine the phantom Nameserver entry and
bounce this port to clear from the Nameserver.
Example of command sequence:
1) Run ag --show (on AG gateway) showing correct device PID:
ag_gateway:

3 0x844401 50:01:43:80:03:ba:a7:40 0

2) Run nsshow on any switches that have direct connection to N_Ports from this AG gateway. In the
example case, 2 N_Ports are connected to 48K_1 and 48K_2
Nsshow from 48K_1 (correct)
Port 68 844401;
3;50:01:43:80:03:ba:a7:40;50:01:43:80:03:ba:a7:41; na
Nsshow from 48K_2 (incorrect)
Port 68 854401;
3;50:01:43:80:03:ba:a7:40;50:01:43:80:03:ba:a7:41; na
3) Correct login is on port 68 (0x44) s7/P4 on domain 132 because it matches the same PID as the
device PID shown in the ag show output above. In order to clear the old login and NS entries we
need to bounce port 68 on domain 133 because its PID is incorrect (phantom).

2009 Brocade Communications Systems, Inc. All Rights Reserved.

TSB 2009-059-A

CORRECTIVE ACTION
This issue was corrected in FabricOS v5.3.2c (available 9/30/09), v6.0.1 firmware versions and
higher via Defect 209077. This firmware must be installed on the Access Gateway side (not the
attached fabric side). After the firmware is upgraded, the switch will need to be rebooted or the
multiple N_Ports disabled and enabled in order to reassign the device area route correctly.

2009 Brocade Communications Systems, Inc. All Rights Reserved. TSB 2009-059-A