[TRNSPRTPCE-687] WorkAround handling Operational states notification Created: 14/Sep/22  Updated: 17/Nov/22  Resolved: 17/Nov/22

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

Type: Story Priority: High
Reporter: Olivier Renais Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days
Original Estimate: Not Specified

Epic Link: Demo SROL

 Description   

Based on UTD observations,:
When a fiber failure happens,
1. VendorA ROADM a) OTS interface and b) DEG port operational status will become outOfService. VendorA ROADM sends an AlarmNotification to T-PCE, but no a ChangeNotification. T-PCE will not start the restoration.
2. VendorB ROADM sends a ChangeNotification to T-PCE. But its a) OTS interface and b) DEG port operational status remains inService. So, T-PCE will not start the restoration also.
This means that we need to find a work around to handle SC22 demo.
1) Check implementation (netconf/openROADM stream
2) Define the way we handle the workaround

tianliang : Please could you provide the extract of the state-change notification sent by VendorB equipment, to provide a workaround in the shortest time.


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