Brocade Fabric OS v7.2.0d Release Notes v1.0

Fabric OS v7.2.0d Release Notes v1.0 Page 38 of 52
Defects
Closed with Code Change in Fabric OS v7.2.0d
This section lists the defects with Critical, High and Medium Technical Severity closed with a code change as of
February 24, 2014 in Fabric OS v7.2.0d.
Defect ID:
DEFECT000494570
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.2.0
Technology
Area:
Routing
Closed In Release(s):
Symptom:
Upgrading to FOS7.2.0c (which contains a fix for defect 491192) with pre-existing user-defined
logical switches may lead to fabric wide performance issue or hosts not being able to see targets
after a slot offline event
Condition:
On FOS 7.2.0c, this affects Fabric IDs that do NOT contain a digit of 0, 1, 2, or 5; such as FID 3 or
FID 4. FID 35 would not be affected as it contains the digit 5.
Workaround:
Do not create or modify logical switches, or bounce ports until upgrading to a code revision with
fix.
Recovery:
Use CLI "portcfgdefault" for each port and then cold boot switch to recover, or upgrade to FOS
release with the fix - FOS7.2.0d, which will recover and also prevent future occurrence.
Defect ID:
DEFECT000492849
Technical Severity:
High
Probability:
High
Product:
FOS
Technology:
Distance
Reported In Release:
FOS7.2.0
Technology
Area:
FCIP
Closed In Release(s):
Symptom:
FCIP link became unstable after some run time and reported the following XTUN messages:
2014/02/03-09:50:40, [XTUN-1008], 12759, CHASSIS, WARNING, , FCIP Control block memory
usage slot=0 DP=1 Allocated=5209344 Free=196117248 Total=201326592.
2014/02/03-09:50:41, [XTUN-1001], 12760, FID 128, ERROR, , FCIP Tunnel 16 Memory
allocation failed tracker 1/247.
Condition:
On switch running with FOS 7.2.0b/c and FOS7.2.1, resource is lost when processing periodic
vendor unique message ELS-PRLI coming from a disk mirroring application every 5 seconds.
Defect ID:
DEFECT000487271
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.2.0
Technology
Area:
Brocade Network Advisor
Closed In Release(s):
Symptom:
Unable to create flow with Flow Mirror feature through BNA with FOS v7.2.0x
Condition:
This happens in a race condition when the non-default switch goes to active state prior to the
default switch in a VF environment, after a cold boot or hafailover.
Workaround:
The FOS CLI can be used to successfully create the flow
Recovery:
User can attempt to restart the flow. If it still fails and user has to use BNA to create flow, upgrade
to a FOS code revision with the fix.