Internal Ref. | Issue |
3336788 | Description: Fixed the issue in Firmware where MAD error responses might have been received in libsharp. |
Keywords: sharp_am; libsharp | |
Discovered in Version: 3.2.0 | |
Fixed in Release: 3.3.0 (Quantum-2 Firmware 31.2010.6064) | |
3343503 | Description: Fixed the issue where sharp_am installed from MLNX_OFED used an invalid range of job IDs, resulting in occasional errors when trying to establish new SHARP jobs. |
Keywords: MLNX_OFED; sharp_am | |
Discovered in Version: 3.2.0 | |
Fixed in Release: 3.3.0 | |
3368381 | Description: Fixed the issue of when no sufficient amount of retries was made to resend failed libsharp GroupJoin MADs, SHARP jobs failed before they even started. |
Keywords: libsharp; MADs | |
Discovered in Release: 3.0.0 | |
Fixed in Release: 3.3.0 | |
3393902 | Description: Fixed the issue where re-created virtual ports were not recognized by sharp_am, thus the correct tree was not built for them. This resulted in SAT jobs getting ibv_poll_cq failure in libsharp. |
Keywords: Virtual port; sharp_am; libsharp; SAT; ibv_poll_cq | |
Discovered in Version: 3.2.0 | |
Fixed in Release: 3.3.0 | |
3404474 | Description: Fixed an issue where failure of application allocation of all hosts done via /app/sharp/resources REST-API returned a successful job instead of error. |
Keywords: REST API; allocation | |
Discovered in Release: 3.2.0 | |
Fixed in Release: 3.3.0 | |
3406186 | Description: Fixed an issue where SHARP AM failed handling reports from OpenSM if some switch ports were down or isolated. |
Keywords: Aggregation Manager; Aggregation Node; OpenSM | |
Discovered in Release: 3.2.0 | |
Fixed in Release: 3.3.0 |