[TRNSPRTPCE-90] Handling of spanloss > 27 dB Created: 18/Feb/19 Updated: 12/Jul/19 Resolved: 20/Jun/19 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Jonas Mårtensson | Assignee: | Gilles Thouenon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 week, 3 days | ||
| Original Estimate: | 3 days | ||
| Issue Links: |
|
||||||||
| Description |
|
When a spanloss of 28 dB or higher is measured, the spanloss is not set. This causes a later service-power-setup to fail (when the setPower function in PowerMgmt.java cannot get the spanloss to calculate target power value) with the controller returning a 500 Internal Server Error. Also, when this happens, there are no helpful log messages for understanding what went wrong. I know that a spanloss > 27 db is outside the OpenROADM spec but maybe it would be better to anyway set the spanloss and then let the power setup fail with some helpful log message. |
| Comments |
| Comment by Guillaume Lambert [ 11/Jun/19 ] |
|
Gilles confirms the bug is present (OLM test modification) The Spanloss must be set even if >27 dB - we should generate a warning or an error in that case. The error can only be handled when OMS attributes will be implemented. |
| Comment by Guillaume Lambert [ 20/Jun/19 ] |
|