Information in this document applies to any platform.
Date of Workaround Release: 05-Mar-2014
Date of Resolved Release: 17-Sep-2014
__________________________________________
Description
Adding new devices to Brocade Fibre Channel Switches running Fabric Operating System (FOS) 7.2.0, 7.2.0a, 7.2.0b or FOS 7.2.1 and configured with non default logical switches and with an internal Custom Index value set to 1, 2, 3, or 5 in the default switch, will cause traffic passing across E or F ports within a user defined logical switch to cease. Oracle utilizes a Custom Index value of 5 from the factory.
Note: Switches with Logical Switch configurations and that are defined to have a Custom Configuration (Custom Index Value set to 1, 2, 3, or 5 in the default switch) should not be upgraded to Fabric Operating System (FOS) 7.2.0, 7.2.0a, 7.2.0b or FOS 7.2.1.
Occurrence
This issue can occur on the following platforms running Fabric Operating System (FOS) version 7.2.0 through 7.2.0b and 7.2.1 with Logical Switches configured:
- Brocade Fibre Channel Switches DCX, DCX-4S, 8510-8, 8510-4, 6510, 6520, 5100, 5300, 7800
Notes:
1. Switches running FOS versions below 7.2.0 are not at risk for this issue.
2. This issue will only affect systems that have configured user defined Logical Switches. Only ports within user defined logical switches will be susceptible to this issue. Ports within the default switch are not risk.
3. Switches that have a Custom Index value of 1, 2, 3, or 5 defined within the default switch will be at risk. Switches that have a Custom Index value of 0 or 4 are not at risk to this issue, even if they have logical switches configured. Oracle utilizes a Custom Index value of 5 from the factory.
To determine the current FOS version on the switch, do the following:
Login as "admin" user and use one of the following commands:
admin> version
Kernel: 2.6.14
Fabric OS: v5.3.0b
Made on: Fri Oct 5 21:19:49 2007
Flash: Tue Dec 9 13:35:30 2008
BootProm: 4.6.6
admin>
OR:
admin> firmwareShow
Appl Primary/Secondary Versions
------------------------------------------
FOS v5.3.0b
v5.3.0b
admin>
To verify the Custom Index on a switch, use the “configshow” command in the default switch context.
Example 1:
sw0:ABC123> configshow | grep -i custom
Custom.index:0
In Example 1 above, the switch is NOT at risk for this issue.
Example 2:
sw0:XYZ321> configshow | grep -i custom
Custom.index:3
In Example 2 above, the switch is at risk for this issue as the default switch has a Custom Index value of 1, 2, 3, or 5.
Symptoms
Should the described issue occur, hosts may be unable to reach targets due to frames being corrupted, or traffic flow may appear to stop.
Workaround
To avoid this issue until a fix is delivered:
A) If a switch has a Custom Index value of 1, 2, 3, or 5 and also has been configured with Logical Switches:
Do not upgrade to FOS 7.2.0, 7.2.0a, 7.2.0b or FOS 7.2.1.
B) If a switch with a Custom Index value of 1, 2, 3, or 5 is already running FOS 7.2.0, 7.2.0a, 7.2.0b or FOS 7.2.1:
Do not create any new Logical Switches.
C) Do not add any new devices to an existing Logical Switch.
This issue is addressed in the following releases:
- FOS 7.2.0d patch 151054-04 or later
- FOS 7.2.1a patch 151130-02 or later
Patches
<SUNPATCH:151054-04>
<SUNPATCH:151130-02>
History
05-Mar-2014: Document released; status Workaround
17-Sep-2014: FOS Patches released, issue is Resolved
This Technical Bulletin delivered Via Brocade defect 491192
Patch 151130-01 released FOS 7.2.1.
Patch 151054-01 released FOS 7.2.0b
7.2.0 and 7.2.0.a were not released by Oracle, by may have been
installed by customers direct from Brocade.
Oracle supports all revisions of FOS even if Oracle did not ship it.
Questions regarding this document should be addressed to
sunalertpublication_us_grp@oracle.com and copy the
responsible engineer/submitter listed below.
Internal Contributor/Submitter: felix.garcia@oracle.com
Internal Eng Responsible Engineer: felix.garcia@oracle.com
Oracle Knowledge Analys: david.mariotto@oracle.com
Internal Eng Business Unit Group: Disk, Network
References
Attachments
This solution has no attachment