[DOCS-144] Path Computation client for sulfur shows error "no source vertex" . Graph is displayed correct Created: 24/May/22  Updated: 03/Jun/22

Status: Open
Project: docs
Component/s: General, User Guide
Affects Version/s: Silicon
Fix Version/s: None

Type: Bug Priority: High
Reporter: Aseem Rai Assignee: Luis Gomez
Resolution: Unresolved Votes: 0
Labels: pcep
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File response_bgp_linkstate_routes.json     File response_graph.json    
Priority: High

 Description   

version: sulfur
page: index

Log output of path computation client 

15:41:49.976 INFO [qtp1119293142-180] Got Path Computation Service request
15:41:49.977 INFO [qtp1119293142-180] Call Path Computation cspf algorithm for path from VertexKey{_vertexId=5} to VertexKey{_vertexId=2} with contraints Constraints{addressFamily=Ipv4, bandwidth=DecimalBandwidth{_value=100000000.0, _UNITS=bytes/second}, classType=0, teMetric=250}
15:41:49.977 INFO [qtp1119293142-180] Start CSPF Path Computation from VertexKey{_vertexId=5} to VertexKey{_vertexId=2} with constraints Constraints{addressFamily=Ipv4, bandwidth=DecimalBandwidth{_value=100000000.0, _UNITS=bytes/second}, classType=0, teMetric=250}
15:41:49.978 WARN [qtp1119293142-180] Found no source for Vertex Key VertexKey{_vertexId=5}
15:42:22.032 INFO [qtp1119293142-177] Got Path Computation Service request
15:42:22.033 INFO [qtp1119293142-177] Call Path Computation cspf algorithm for path from VertexKey{_vertexId=5} to VertexKey{_vertexId=2} with contraints Constraints{addressFamily=SrIpv4, bandwidth=DecimalBandwidth{_value=100000000.0, _UNITS=bytes/second}, classType=0, teMetric=250}
15:42:22.033 INFO [qtp1119293142-177] Start CSPF Path Computation from VertexKey{_vertexId=5} to VertexKey{_vertexId=2} with constraints Constraints{addressFamily=SrIpv4, bandwidth=DecimalBandwidth{_value=100000000.0, _UNITS=bytes/second}, classType=0, teMetric=250}
15:42:22.033 WARN [qtp1119293142-177] Found no source for Vertex Key VertexKey{_vertexId=5}

Graph Output 

REST : /restconf/operational/graph:graph-topology

Attached : response_graph.json 

Path computation Request 
REST: /restconf/operations/path-computation:get-constrained-path 
{
"input": {
"graph-name": "ted://example-linkstate-topology",
"source": 5,
"destination": 2,
"constraints":

{ "address-family": "sr-ipv4", "te-metric": 250, "bandwidth": 100000000, "class-type": 0 }

,
"algorithm": "cspf"
}
}
 
 

 Comments   
Comment by Aseem Rai [ 25/May/22 ]

Hi 

Please help to understand what could be the reason for this issue ? If there is something to do with the configuration or packages installed , please let mek now 

 

thanks

Aseem.

Comment by Olivier Dugeon [ 01/Jun/22 ]

Hello,

Like for BGPCEP-1008, it seems that the problem comes from the graph which is formed with wrong VertexID. Thus, the Path computation algorithm is unabled to determine source and destination vertices on the graph and failed to compute a path.

Here, I saw that you are using IS-IS as routing protocol which I validated. Thus, I suspect a problem with Decimal64 (already reported and corrected) in Sulfur SR1. I'll check on my side and verify the problem.

Comment by Aseem Rai [ 03/Jun/22 ]

Thanks odd22 

From BGPCEP-1008, I have also collected the ask of RPC get constrained path output  and I will paste it to that issue today . Do you also know why the PCE Server closes connection due to this and is there any setting/configuration to avoid that to happen. 

 

Aseem. 

Comment by Olivier Dugeon [ 03/Jun/22 ]

Hello,

The PCEP session closed due to the exception which is not catched correctly. In fact, I would call Path Computation within a Future<> but it is not working as expected. Thus, I should verify that nothing goes wrong which normally the code done. But, it seems you discover a new situation where Path computation is unable to compute a path and where JLNPE is raised.

Once problem determined, I will propose a global patch.

Regards

Olivier

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