Bug Fixes in this Firmware Version
For a list of bug fixed from previous versions, see Bug Fixes History.
Internal Ref. |
Issues |
4129770 |
Description: In rare cases, when a SHARP job is stopped while ANDR operations were in used, the next job may fail and require switch reboot. |
Keywords: SHARP |
|
Discovered in Version: 31.2012.2234 |
|
Fixed in Version: 31.2012.2400 |
|
4100909 |
Description: In some cases where incorrect MAD handling causes the switch to become unresponsive to the SM, a switch reset is required. |
Keywords: MADs |
|
Discovered in Version: 31.2012.2234 |
|
Fixed in Version: 31.2012.2400 |
|
4041142 |
Description: In rare cases where the switch is busy handling GMP MADs, SMP MADs may be blocked and potentially make the switch unresponsive to SM. |
Keywords: MADs |
|
Discovered in Version: 31.2012.2234 |
|
Fixed in Version: 31.2012.2400 |
|
4172615 |
Description: Inaccurate credits configurations in switch data path which, in rare cases, can lead to unexpected behavior or performance degradation. |
Keywords: Credits, Data Path, Fatal Cause |
|
Discovered in Version: 31.2012.2234 |
|
Fixed in Version: 31.2012.2400 |
|
4048953 |
Description: In cases of repeating flapping links, the pFRN recovery mechanism might not be triggered. |
Keywords: SHIELDv2, pFRN |
|
Discovered in Version: 31.2012.2234 |
|
Fixed in Version: 31.2012.2400 |
|
4194752 |
Description: When setting N2N neighbor information parameters for network ports, NodeKey misconfiguration may occur. |
Keywords: Class Key |
|
Discovered in Version: 31.2012.2234 |
|
Fixed in Version: 31.2012.2400 |