[TRNSPRTPCE-629] Combine OTU (OTUCn) infrastructure service with ODU (ODUCn) infrastructure Created: 02/Mar/22  Updated: 16/Jan/24

Status: Open
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Medium
Reporter: Balagangadhar Bathula Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 1 week, 3 days
Time Spent: Not Specified
Original Estimate: 1 week, 3 days


 Description   

Currently we have a three step process to create a sub-wavelength services (1G, 10G, 100G, 200G, and 300G). 

  1. Create OTU (OTUCn) connection-type: Infrastructure 
  2. Create ODU (ODUCn) connection-type: infrastructure
  3. Create Ethernet service

However, as of now we did not find a use-case to have OTU and ODU service creation separately.

Also, we found the the PM values are unavailable until the creation of the respective ODU service, without which we cannot perform OLM and calculate preFEC BER.

Either we combine Step (1) and (2) and make the process a two-step process instead of (3) or preform OLM/ BER calculations after the creation ODU service.

Preferred option would be make it a two-step process.
Without the presence of ODU (or ODUCn) interfaces, devices does not report PM and it causes the BER test to fail. Change the behavior to perform OLM and BER test after the creation of the ODU (ODUCn) interfaces.

 

 

 

 

 


Generated at Wed Feb 07 20:43:37 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.