[TRNSPRTPCE-610] 2.2.1 port-capabilities support in port-mapping Created: 08/Feb/22 Updated: 20/Sep/23 Resolved: 23/Feb/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus, Sulfur |
| Type: | Bug | Priority: | Medium |
| Reporter: | Balagangadhar Bathula | Assignee: | Balagangadhar Bathula |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 3 days | ||
| Original Estimate: | 0 minutes | ||
| Epic Link: | Device Management |
| Description |
|
According to the device model, there are two ways to get the port-capabilities of the device in 2.2.1 models:
| +--rw ports* [port-name] | +--ro supported-interface-capability* identityref 2. Port-capabilities under, ports sub-tree. +--rw circuit-packs* [circuit-pack-name] | +--rw ports* [port-name] | +--ro org-openroadm-port-capability:port-capabilities Currently port-mapping only supports the #1. Add the code to enable to get the supported-interface-capability from port-capabilities as well.
|