[TRNSPRTPCE-445] PCE doesn't find SRG client for Uni-directional SRG ports Created: 21/Apr/21 Updated: 23/Feb/22 Resolved: 11/Feb/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Silicon |
| Type: | Bug | Priority: | High |
| Reporter: | Shweta Vachhani | Assignee: | Shweta Vachhani |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 3 days | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Epic Link: | Unidir consolidation |
| Description |
|
While creating openroadm-network, code is adding a SRG CP port with type SRGTXRXCP irrespective of Roadm node supporting uni-directional or bi-directional ports. This is fine because we are only creating single SRG-CP TP in openroadm-topology. But PCE is using only CP type to find SRG port which fails path calculation for uni-directional ports. PCE code should be updated to fetch available SRG port. |
| Comments |
| Comment by Shweta Vachhani [ 19/May/21 ] |
|
Attached are Karaf log coming up with master branch. Look for error "doesn't have PP Client for CP SRG1-CP-TXRX". |