Brocade Fabric OS v7.0.2e Release Notes v1.0

Fabric OS v7.0.2e Release Notes v1.0 Page 38 of 53
Defect ID:
DEFECT000459102
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.0.2
Technology Area:
FC-FC routing
Symptom:
Domain change caused proxy devices to be stuck in "initializing" state.
Condition:
If a domain ID was previously changed, proxy devices could get stuck in "initializing" state after
adding a new switch to an edge fabric.
Recovery:
Deleting and re-adding an LSAN zone will permit the devices to recover.
Defect ID:
DEFECT000461189
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.2.0
Technology Area:
Web Tools
Symptom:
Unable to launch WebTools using Google Chrome browser and IE11 with Java update 45 or 51.
Condition:
This happens when using the latest Java update revision 45 or 51.
Workaround:
Use another browser or older Java update.
Defect ID:
DEFECT000462116
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.0.0
Technology Area:
Platform Services
Symptom:
After director reboot, CPs lost heartbeat and active CP was reset. Standby CP panicked while taking
over the Active role.
Condition:
Port blade hardware failure may trigger loss of heartbeat (between two CPs).
Recovery:
Switch is recovered after reboot; replace bad port blade to prevent re-occurrence.
Defect ID:
DEFECT000467263
Technical Severity:
Medium
Probability:
Low
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS7.0.2
Technology Area:
Frame Monitoring
Symptom:
The fwd daemon may crash and result in a switch panic while repeatedly performing addition and
deletion of frame monitors.
Condition:
This may be encountered when frame monitor deletion coincides with fabric watch polls (that occurs
periodically every 6 sec) to get the threshold values.
Defect ID:
DEFECT000468549
Technical Severity:
High
Probability:
High
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.0.2
Technology Area:
FC-FC routing
Symptom:
3rd party cluster application fails after device gets name server query rejected with reason
NSRJT_EXPL_NO_PORTID.
Condition:
This is a timing issue that occurs rarely for a node device that sends back to back FLOGIs within a
short time span on the same port.
Workaround:
Disable and enable ports manually to complete site swap.
Recovery:
Toggle affected ports.