-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
None
Currently we have a three step process to create a sub-wavelength services (1G, 10G, 100G, 200G, and 300G).
- Create OTU (OTUCn) connection-type: Infrastructure
- Create ODU (ODUCn) connection-type: infrastructure
- 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.