Enable latency parameters using an API

Allow Path Control to receive the bandwidth measurements from the network

Now that the tests are running, the next step is to allow latency collection in NSP's Path Control module. By default, Path Control's latency configuration is displayed. To enable latency collection in Path Control, a specific NSP Path Control API call is used.

For more information about the API, see the Swagger documentation for the NSP Path Control API on the Nokia Developer Portal.

See the following example:

View the figure

In this example, the "modelDriven" parameter is the parameter to be enabled. That is because we need Path Control to report link latency based on the measurements coming from Data Collection and Analysis Management.  

When the call is successful, real-time latency measurements in Path Control for both LSP and link objects are displayed. The measurements are updated approximately every minute.

View the figure
View the figure