Brocade Fabric OS v6.4.3f Release Notes v1.0

Closed with Code Change in Fabric OS v6.4.3f
Fabric OS v6.4.3f Release Notes v1.0 Page 36 of 149
Defect ID:
DEFECT000418392
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.1.0
Technology Area:
Web Tools
Closed In Release(s):
FOS6.4.3f(Fixed)
Symptom:
Weblinker crash while the fabric is being monitored by BNA
Condition:
This may be encountered in a large fabric with security policy activated.
Defect ID:
DEFECT000421461
Technical Severity:
Medium
Probability:
Medium
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS6.4.2
Technology Area:
BB Credits
Closed In Release(s):
FOS6.4.3f(Fixed)
Symptom:
Detected "CRC error with good EOF" errors and it may cause buffer credit loss.
Condition:
On a DCX-4S with FC8-32 port blade installed in Slot 3 (3/56)
Recovery:
Auto tuning or manual tuning.
Defect ID:
DEFECT000432406
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS6.4.2
Technology Area:
Logging
Closed In Release(s):
FOS6.4.3f(Fixed)
Symptom:
Customer observes multiple supportsave processes on switch without actively initiating a recent
supportsave. These processes consume memory and may lead to switch panic when an additional
supportsave is initiated.
Condition:
Hung supportsave processes left on switch.
Workaround:
Kill stale supportsave PIDs
Recovery:
After switch panic, no further recovery is needed.
Defect ID:
DEFECT000440137
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.0.0
Technology Area:
BB Credits
Closed In Release(s):
FOS6.4.3f(Fixed)
Symptom:
"CRC with good EOF errors" observed and may cause buffer credit loss.
Condition:
This may occur on DCX-4S with FC8-16 port blades installed in slot 1, 2
Recovery:
Manual tuning or auto tuning.
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):
FOS6.4.3f(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 is configured on the active CP, inserting a new standby CP with its time set later than that
on Active CP & SSL is not already configured, then it may cause a panic & unnecessary additional
reboot of standby CP after insertion.
Workaround:
Do hadisabled before inserting standby CP. Then 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.