Release Notes

Closed with Code Change in Fabric OS v7.2.1b
Fabric OS v7.2.1e Release Notes v1.0 Page 49 of 82
Defect ID:
DEFECT000467843
Technical Severity:
Medium
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS7.0.2
Technology Area:
End-to-end Performance Monitoring
Symptom:
The TX counter remains at "0x0000000100000000" after clears stats of EE performance monitors.
Condition:
No special condition is required: When EE monitor counters(TX/RX) are cleared on a port, 1 in top
value of EE monitor counters(Tx/Rx) are not cleared. There is no functional impact.
Defect ID:
DEFECT000471135
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.2.0
Technology Area:
Trunking
Symptom:
RTWR-1003 RASLOG messages: Loss of connectivity.
Condition:
This is a rare occurrence that may be encountered when both E-ports of a 2-E-port trunk go offline
during hafailover/hareboot.
Recovery:
Disable both ports in the 2-E-port trunk, then enable them again.
Defect ID:
DEFECT000471772
Technical Severity:
Medium
Probability:
Medium
Product:
FOS
Technology:
Other
Reported In Release:
FOS7.2.0
Technology Area:
Other
Symptom:
After issuing cfgsave, there may be a time delay before cfgsave confirmation message is displayed.
During the time delay, CPU load may be high on zoning.
Condition:
The issue may occur if the zone database is large.
Recovery:
The operation completes by itself without intervention.
Defect ID:
DEFECT000472904
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.1.0
Technology Area:
FC-FC routing
Symptom:
16G ASIC signal equalizer (DFE) running at 8G may drift due to IDLE fill words received resulting in
CRC errors and server tapes not accessible after reboot
Condition:
This may be encountered when 16G ASIC speed negotiates or is locked at 8G
Defect ID:
DEFECT000473289
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.2.0
Technology Area:
Routing
Symptom:
RTWR-1003 RAS logs.
Condition:
This problem may occur from the following sequence:
1. One switch is connected off a loop topology
2. The loop topology is physically changed to a linear topology
3. One of the switches that was in the loop undergoes an hareboot
Recovery:
Bounce an ISL connecting the switch originally outside the loop topology.