[TRNSPRTPCE-492] Manage otn-topology update with OTN links at 400G Created: 30/Jul/21  Updated: 13/Oct/21  Resolved: 08/Sep/21

Status: Verified
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: Phosphorus

Type: Improvement Priority: Medium
Reporter: Gilles Thouenon Assignee: Gilles Thouenon
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 3 days
Original Estimate: 0 minutes


 Description   

Allow otn-topology update with OTUC4 and ODUC4 links at 400G.
Since some otn links have almost the same id since they are terminated on the same source and destination node/tpid, their prefix with otn-link-type allows distinguishing them. Take adavantage of this feature to bring few adaptations:

  • use otn-link-type enumeration as prefix for link name insteand of manual managed string
  • propagate and use otn-link-type to differentiate treatments between 100G and 400G supported links
  • use min and max trib slot and trib port comming from path-description to update ODU4/ODUC4 links
Generated at Wed Feb 07 20:43:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.