[TRNSPRTPCE-460] PCE picks wrong aendPceNode, zendPceNode and termination-tp

Wed, 23 Feb 2022 14:23:28 +0000

Current PCE code is picking up very first XPDR node as aendPceNode and zendPceNode. For example if a XPONDER-OUTPUT link exists only between TPDR1-XPDR3-NETWORK1-RDM1-SRG1-PP1, but PCE always assigns TPDR1-XPDR1 as aendPceNode.

During the testing with equipments we found even though we create Xponder links for certain TPs, PCE returns TP which doesn't have physical connections. We suggest updating following:

if (ServiceFormat.OTU.equals(this.serviceFormat) && nttp1 == null)

{ LOG.info("Tail attribute is null. Please continue"); continue; }

There is client TP for OTU service format. In that case, once network TP is found and service format is confirmed method should return. This is the correct code.

} else if (ServiceFormat.OTU.equals(this.serviceFormat))

{ LOG.info("Infrastructure OTU4 connection"); this.valid = true; return; }

PceLink only has just client attribute, as a result the path returns same client TP even through they are different. For example one end has CLIENT2 and other-side has CLIENT5. It would be a good idea to have them separated by having srcClient and destClient

OpenDaylight JIRA

[TRNSPRTPCE-460] PCE picks wrong aendPceNode, zendPceNode and termination-tp