Handling E2E service request for B100G (TRNSPRTPCE-413)

[TRNSPRTPCE-449] Changes to port mapping YANG to support muxp-profile Created: 28/Apr/21  Updated: 07/Sep/21  Resolved: 07/Sep/21

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

Type: Sub-task Priority: High
Reporter: Balagangadhar Bathula Assignee: Balagangadhar Bathula
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days
Original Estimate: Not Specified


 Description   

To provision ODU connection in a B100G muxponder use case, we need to know the trib-port number and the corresponding start/end slots. This information is listed under the "muxp-profile" of the 7.1 device. Here is the sample tree structure for logical connection point in the port-mapping.

+--rw mapping* [logical-connection-point]

| +--rw mpdr-restrictions

| | +--rw min-trib-slot? org-openroadm-otn-common-types:opucn-trib-slot-def

| | +--rw max-trib-slot? org-openroadm-otn-common-types:opucn-trib-slot-def

This data needs to appear only when we device model is 7.1 and LCP for port-qual "switch-client".


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