Brocade Fabric OS v7.2.1a Release Notes v1.0

Closed with Code Change in Fabric OS v7.2.1
This sections lists the defects with Critical, High, and Medium Technical Severity closed with a code change as
of December 13, 2013 in Fabric OS v7.2.1. Note: these defects are formatted with an updated defect table
structure applying to all new or previously unpublished defects.
Defect ID:
DEFECT000415126
Technical Severity:
High
Probability:
High
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.1.0
Technology Area:
CLI
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
User may see "Maximum number of rules created" when editing inactive policies (adding or
removing rules from policies)
Condition:
It happens when the maximum number of ipfilter policies are present
Workaround:
Reduce the number of ipfilter policies.
Defect ID:
DEFECT000427692
Technical Severity:
Medium
Probability:
Low
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS6.4.2
Technology Area:
Fabric Watch
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
False alarm reported about FAN with FW-1006 raslog in heavy CPU utilization switches :
2012/10/28-18:45:42, [FW-1006], 67128, SLOT 6 | FID 128, WARNING, , Env Fan 2, is below low
boundary(High=3400, Low=1600). Current value is 0 RPM.
Condition:
Under heavy CPU utilization switch reported false alarm about the fan with FW-1006 raslog.
Workaround:
Issue will not be seen if switch CPU utilization is less.
Defect ID:
DEFECT000442978
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.1.0_blv
Technology Area:
Platform Services
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
Embedded switch BR6458's internal copper port may be stuck at No_Sync after its peer server blade
is reseated.
Condition:
A reseat of the server blade is required.
Workaround:
A gentle reseat of the server blade did not recreate the issue.
Recovery:
A gentle reseat of the server blade.
Defect ID:
DEFECT000454580
Technical Severity:
Medium
Probability:
Low
Product:
FOS
Technology:
Security
Reported In Release:
FOS6.4.2
Technology Area:
Fabric Authentication
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
With SSL configured on Active CP, a newly inserted Standby CP may panic and go through an
unnecessary additional reboot.
Condition:
When SSL configured in the active CP, inserting a new standby CP whose time is later than that of
Active CP & don't have SSL configured already can cause a panic & unnecessary additional reboot of
standby CP after insertion.
Workaround:
Insert standby CP with hadisabled state. Login to standby CP, change standby CP's date to earlier
than that of the active CP using "/bin/date" command and then execute haEnable.
Recovery:
No action required. Previous switch reboot will fix the SSL configuration issue.