4x100g-service-request.json
tpce-error.log
[TRNSPRTPCE-768] PCE picks the wrong client ports Created: 18/Oct/23 Updated: 10/Jan/24 Resolved: 31/Oct/23 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | PCE |
| Affects Version/s: | Potassium |
| Fix Version/s: | ArgonSR3, PotassiumSR1, Calcium |
| Type: | Bug | Priority: | Medium |
| Reporter: | Balagangadhar Bathula | Assignee: | Gilles Thouenon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
4x100g-service-request.json
tpce-error.log
|
| Description |
|
When we specified client ports (100GE on a muxponder for example) to terminate a 100GE service carried over a 400Gbps (OCH/OTN) trail circuit, the path-computed by PCE is picking the wrong client port specified in the service-create request. This is incorrect and in some cases, the port used by the PCE does not exist in the node configuration. This causes the provisioning process to fail.
|