NSP

Network Services Platform

Release 24.4

Data Collection and Analysis Guide

3HE-20004-AAAA-TQZZA
Issue 1
April 2024
© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms
 NSP

Legal notice

Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and consulting with standards
bodies to ensure that terminology is inclusive and aligned with the industry. Our future customer documentation will be updated accordingly.

This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without
the prior written consent of Nokia.

This document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a product purchased or licensed from any
company within Nokia Group of Companies. Use this document as agreed. You agree to notify Nokia of any errors you may find in this
document; however, should you elect to use this document for any purpose(s) for which it is not intended, You understand and warrant that
any determinations You may make or actions You may take will be based upon Your independent judgment and analysis of the content of
this document.

Nokia reserves the right to make changes to this document without notice. At all times, the controlling version is the one available on
Nokia’s site.

No part of this document may be modified.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY
DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA
THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR
OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be
trademarks of their respective owners.

© 2024 Nokia.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
2 3HE-20004-AAAA-TQZZA Issue 1
Contents NSP

Contents

About this document............................................................................................................................................7

Part I: Data collection, analysis, and visualization............................................................................................9

1 Overview .......................................................................................................................................................11
1.1 How does NSP support telemetry management? .............................................................................11
1.2 What should I know about telemetry data collection? .......................................................................12
1.3 What information can I find in the Telemetry Statistic Search Tool?..................................................14
1.4 What charts can I create in NSP? .....................................................................................................15

2 Telemetry ......................................................................................................................................................17
Telemetry collection.....................................................................................................................................17
2.1 How do I install telemetry artifacts? ..................................................................................................17
2.2 What is a subscription? .....................................................................................................................18
2.3 How do subscriptions work? .............................................................................................................19
2.4 What is an object filter?.....................................................................................................................19
2.5 How do object filters work? ...............................................................................................................20
2.6 What is a telemetry chart? ................................................................................................................23
2.7 How does telemetry charting work? ..................................................................................................23
2.8 How do I manage subscriptions? ......................................................................................................24
2.9 How do I plot a telemetry chart? .......................................................................................................25
Aggregation ..................................................................................................................................................28
2.10 What is aggregation? ........................................................................................................................28
2.11 How do I set the aggregation time zone?..........................................................................................28
2.12 How do I edit aggregation information? ............................................................................................29
Age-out policy ..............................................................................................................................................30
2.13 What is an age-out policy?................................................................................................................30
2.14 How do I edit an age-out policy?.......................................................................................................30

3 Baseline Analytics........................................................................................................................................31
3.1 What is a baseline?...........................................................................................................................31
3.2 What is an anomaly?.........................................................................................................................31
3.3 How do baselines and anomalies work?...........................................................................................31
3.4 What should I know about baseline and anomaly detector creation? ...............................................35
3.5 How do I create baselines?...............................................................................................................36
3.6 How do I edit or delete baselines? ....................................................................................................38
3.7 What is a baseline chart?..................................................................................................................39

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 3
Contents NSP

3.8 How do I plot a baseline chart?.........................................................................................................40

3.9 How do I chart an anomaly? .............................................................................................................41

4 NSP Indicators..............................................................................................................................................43
Indicators ......................................................................................................................................................43
4.1 What is an indicator?.........................................................................................................................43
4.2 How do indicators work? ...................................................................................................................43
4.3 How do indicator formulas work? ......................................................................................................46
4.4 What should I know about indicator creation and management? .....................................................47
4.5 What is an indicator chart?................................................................................................................49
4.6 What is a threshold crossing event? .................................................................................................49
4.7 How do I create an indicator? ...........................................................................................................49
4.8 How do I edit or delete an indicator? ................................................................................................51
4.9 How do I plot an indicator chart?.......................................................................................................52
4.10 How do I chart a threshold crossing event? ......................................................................................54
Indicator templates ......................................................................................................................................55
4.11 What is an indicator template?..........................................................................................................55
4.12 How do I create an indicator template?.............................................................................................55
4.13 How do I edit an indicator template?.................................................................................................57
4.14 How do I delete an indicator template?.............................................................................................57

5 OAM tests .....................................................................................................................................................59

Tests ..............................................................................................................................................................59
5.1 What can I test in NSP? ....................................................................................................................59
5.2 What is CFM? ...................................................................................................................................59
5.3 How do OAM tests work?..................................................................................................................60
5.4 How do I create an OAM test? ..........................................................................................................62
5.5 How do I execute an OAM test? .......................................................................................................64
5.6 How do I edit an OAM test? ..............................................................................................................64
5.7 How do I edit or delete an OAM test? ...............................................................................................65
5.8 How do I view OAM test results? ......................................................................................................66
5.9 How can I troubleshoot Twamp-light test issues? .............................................................................67
Test Suites ....................................................................................................................................................69
5.10 What is an OAM test suite?...............................................................................................................69
5.11 How do I create an OAM test suite? .................................................................................................69
5.12 How do I stop or start an OAM test suite? ........................................................................................70
5.13 How do I edit or delete an OAM test suite?.......................................................................................71
5.14 How do I view OAM test suite results?..............................................................................................71

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
4 3HE-20004-AAAA-TQZZA Issue 1
Contents NSP

Test Templates..............................................................................................................................................73
5.15 What is an OAM test template? ........................................................................................................73
5.16 How do test templates work? ............................................................................................................73
5.17 What is a system template? ..............................................................................................................73
5.18 How do I create an OAM test template? ...........................................................................................74
5.19 How do I edit an OAM test template? ...............................................................................................75
5.20 How do I delete an OAM test template? ...........................................................................................75
Config Objects..............................................................................................................................................76
5.21 What is a config object? ....................................................................................................................76
5.22 What config objects are available in NSP? .......................................................................................76
5.23 How do I create a config object?.......................................................................................................77
5.24 What can I do with config objects in NSP? .......................................................................................77

Part II: Use cases ................................................................................................................................................79

6 Telemetry management use cases .............................................................................................................81

6.1 Installing and locating specific telemetry types .................................................................................81
6.2 Setting up statistics and aggregation for Port Throughput on the 7750 SR ......................................84
6.3 Setting up baselines..........................................................................................................................87
6.4 Creating a simple indicator................................................................................................................92
6.5 Creating a complex indicator using a template .................................................................................98

7 Chart use cases..........................................................................................................................................107

7.1 Creating baseline and anomaly charts............................................................................................107
7.2 Creating an indicator chart ..............................................................................................................111

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 5
Contents NSP

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
6 3HE-20004-AAAA-TQZZA Issue 1
About this document NSP

About this document

Purpose
The NSP Data Collection and Analysis Guide introduces NSP Data Collection and Analysis
functions to operators and administrators by describing usage and features.

Scope
Some feature sets described in the document require the purchase and configuration of additional
feature packages.
See the NSP System Architecture Guide for more information about feature packages and
installation options.

Safety information
For your safety, this document contains safety statements. Safety statements are given at points
where risks of damage to personnel, equipment, and operation may exist. Failure to follow the
directions in a safety statement may result in serious consequences.

Document support
Customer documentation and product support URLs:
• Documentation Center
• Technical support

How to comment
Please send your feedback to [email protected].

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 7
About this document NSP

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
8 3HE-20004-AAAA-TQZZA Issue 1
Data collection, analysis, and visualization NSP

Part I: Data collection, analysis, and visualization

Overview
Purpose
Describes telemetry, baseline, and indicator management in NSP.

Contents

Chapter 1, Overview 11
Chapter 2, Telemetry 17
Chapter 3, Baseline Analytics 31
Chapter 4, NSP Indicators 43
Chapter 5, OAM tests 59

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 9
Data collection, analysis, and visualization NSP

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
10 3HE-20004-AAAA-TQZZA Issue 1
Overview NSP

1 Overview

1.1 How does NSP support telemetry management?

1.1.1 Definition
NSP Data Collection and Analysis (DCA) functions provide collection, processing, and analysis for
MDM and Cloud Native (CN) telemetry. NSP supports configuring telemetry subscriptions and using
baseline analytics, NSP indicators, and OAM tests for anomaly detection, metric customization, and
network tests.

The type and scope of statistics support is dependent on the NE source. NSP provides the following
statistics support by NE type:
• MDM-based telemetry—SNMP protocol for multi-vendor NEs
• Cloud Native telemetry—gNMI protocol for Nokia and multi-vendor NEs
• Classically managed NEs—SNMP protocol for Nokia classically managed NEs, not described
in this document, see the NSP NFM-P Statistics Management Guide.

1.1.2 Functionality

NSP provides the following DCA functions using collected telemetry data:
• visualization, in the form of telemetry charts
• aggregation, rules to combine stats for consumption by Analytics
• baseline analytics and anomaly detection, defining trends using telemetry data and identifying
outliers
• NSP indicators, customized metrics to define and track KPIs
• OAM tests, template-based tests

The DCA telemetry functions described in this document are distinct from:
• Cflowd AA stats and other flow statistics collected via Flow Collectors
• Analytics report catalogs, though stats collected using DCA aggregation functions are available
in Analytics. See the NSP Analytics Report Catalog for information about report generation and
visualizations, and reference lists of the available report catalogs. Baseline analytics and
analytics reporting are different functions, each with their own installation options.
NSP telemetry aggregation is configured using DCA functions, though only when an auxiliary
database is installed.

Telemetry artifacts
The telemetry types for NEs are defined using YANG files in the NE artifact bundles. NSP uses
custom resource (CR) definitions to translate the YANG data, map incoming telemetry to managed
objects in the network, and output data to Postgres, Vertica, and Kafka as required. These resource

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 11
Overview NSP
What should I know about telemetry data collection?

definition files can be viewed as part of the artifact archive. For information about the CRs that
accompany your NE adaptors, see the relevant artifact guide.
See 2.1 “How do I install telemetry artifacts?” (p. 17) for more information.

Note: You must install the relevant adaptors before managing the associated NE types to use
the telemetry definitions. NSP also includes a limited, generic set of default telemetry. Without
installing adaptors, you will only see the default telemetry.

Telemetry subscriptions
A subscription defines the parameters of telemetry collection and uses a filter definition to select the
NEs/objects. NSP deploys the specified data to the NE and registers the Kafka subscription, which
is used to transfer telemetry data from the NE to NSP.
See 2.2 “What is a subscription?” (p. 18) for more information.

1.2 What should I know about telemetry data collection?

1.2.1 Data collection prerequisites
All DCA functions, including baselines, indicators, and OAM testing, depend on telemetry data.
Telemetry data collection must be configured before any function in the Data Collection and
Analysis views can be used.
NSP has the following prerequisites for telemetry data collection.
• The NEs from which you want to collect data must be discovered, managed, and reachable by
the NSP.
• Mediation policies must be configured in the discovery rules used to discover and manage the
NEs:
− SNMP telemetry requires an SNMP mediation policy
− gNMI telemetry requires a GRPC mediation policy
See “Device discovery” in the NSP Device Management Guide for more information about NE
discovery and mediation.
• If you want to use a telemetry subscription to manage MIB statistics from classic NEs, statistics
collection must be configured in the NFM-P.
• Cloud native telemetry requires the gnmiTelemetry installation option.
• All required NE adaptors and telemetry custom resources must be installed on the NSP server:
− for the list of required telemetry artifacts for an NE family, see the artifact guide for the NE
family
− for information on installing the telemetry CRs, see 2.1 “How do I install telemetry artifacts?”
(p. 17).
• If you want to use statistics for Analytics reports with granularity other than raw data, you need
aggregation rules for the telemetry types you want to collect; see the Telemetry tutorial on the
Network Developer Portal
• You need to configure the aggregation time zone.
• To collect accounting statistics, an FTP mediation policy must be assigned to the NE. FTP

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
12 3HE-20004-AAAA-TQZZA Issue 1
Overview NSP
What should I know about telemetry data collection?

mediation policies are created and assigned using a REST API; see the LSOM Framework and
APIs tutorial on the Network Developer Portal.

1.2.2 Data available for collection

When NSP collects telemetry from NE devices using the gNMI protocol, only data in statistics
containers is available for collection. Furthermore, NSP may only make a subset of the attributes in
the statistic containers available in its telemetry types. If you cannot find the counter you are looking
for in the NSP telemetry types, verify that it is available in a statistics container in the relevant NE
state Yang path.
For example, the SR Linux search tool can be found here: (https://yang.srlinux.dev/). Click on the
NE release of interest and filter for the paths you need, as shown in the following example:

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 13
Overview NSP
What information can I find in the Telemetry Statistic Search Tool?

For more information about supported telemetry attributes for your NE family, see the NE artifact
guide. For more information about telemetry definitions, see the Telemetry collection API
documentation on the Network Developer Portal.

1.2.3 Automatic subscriptions

Subscriptions are automatically created for Baseline Analytics, NSP Indicators, and OAM testing. To
collect statistics for another purpose, create a subscription and set its state to enabled.
RESTCONF APIs are available for telemetry collection and aggregation; see the Network
Assurance API documentation on the Network Developer Portal.

1.2.4 Data storage

You can enable database storage for MDM managed NEs as part of subscription creation. By
default, the data collected is stored in Postgres unless there is an auxiliary database enabled, in
which case all collected data is stored in the auxiliary database. For NFM-P collected SNMP or
accounting statistics, the database parameter in the subscription is ignored.
Historical data, that is, data that is stored in a database, is retained according to the age-out policy;
see 2.14 “How do I edit an age-out policy?” (p. 30).

Note: For statistics to be available to the Analytics application for aggregated reports, they
must be stored in the auxiliary database.
The Telemetry data API also provides the functionality to subscribe, stream, and plot historical and
real-time data; see Use Case 5 in the Telemetry Collection tutorial on the Network Developer Portal.

1.3 What information can I find in the Telemetry Statistic Search Tool?
1.3.1 Telemetry Statistic Search Tool
The Telemetry Statistic Search Tool is found in the on-product NSP Help Center. From the Help
Center home screen, navigate to REFERENCE, Statistic Search, Telemetry Statistic Search.
The tool lists telemetry types available for statistics collection and is dynamically updated. Telemetry
types are added to the tool when the required feature packages, adaptor files, and mapping files for
cut-through telemetry are installed on the NSP.
Installation of the following files may be required for a telemetry type to appear in the tool,
depending on the telemetry type:
• vendor agnostic (va) CR bundles
• telemetry yang files
• cut-through (ct) CR bundles
For information about installing telemetry files; see 2.1 “How do I install telemetry artifacts?” (p. 17).

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
14 3HE-20004-AAAA-TQZZA Issue 1
Overview NSP
What charts can I create in NSP?

1.4 What charts can I create in NSP?

1.4.1 Data Collection and Analysis Visualizations
NSP charts allow you to see telemetry data collection in real time.
The following views are available, depending on the feature packages installed. You can navigate
from one view to another by choosing from the drop-down list at the top left.
The chart views display saved charts. You can plot a saved chart or create a new one.
The views display information in columns. Drag a column header to reorder the columns, drag a
column header separator to resize columns, or click on a column header to sort the data in the
column. An icon appears when the column is sorted.
Data Collection and Analysis Visualizations, Telemetry
• Telemetry Charts
Data Collection and Analysis Visualizations, Baseline Analytics
• Baseline Charts
• Anomalies
Data Collection and Analysis Visualizations, NSP Indicators
• Indicator Charts
• Threshold Crossing Events
You can click (Table settings & actions) in the column header on any view to manage the display
or export data.
Filter the list using the column header filters. To remove a filter, delete information from the filter
field or choose Clear filters from the (Table settings & actions) menu in the column header.
For information about charts created from Analytics reports, see the NSP Analytics Report Catalog.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 15
Overview NSP
What charts can I create in NSP?

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
16 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP

2 Telemetry
Telemetry collection

2.1 How do I install telemetry artifacts?

2.1.1 Purpose
Use this procedure to install the custom resource (CR) and yang files required for telemetry
collection.
Telemetry artifacts include vendor agnostic (va) CR bundles, telemetry yang files, and cut-through
(ct) CR bundles. There is no dependency between the two types of CRs, and no requirement to
install both. If the telemetry counters you need to collect are vendor agnostic, you can install only
the va bundle.
Cut-through custom resources may have dependency on cut-through telemetry yang files. Before
you install a cut-through CR bundle, verify the files in the telemetry yang collection to see if the
counters you need are present in any yang file. If you are installing cut-through telemetry yang files
and a cut-through CR bundle, the yang files must be installed first.
Nokia recommends that you only install the cut-through telemetry yang files required for your use
cases.

Note: Cut-through telemetry types are for gNMI-capable devices only.

2.1.2 Steps

1
Obtain any required vendor agnostic (va) CR bundles from the Nokia NSP software download
site:
1. Choose the release, Adaptors, and the adaptor type.
2. The list of available downloads is displayed. Choose the zip file with va and cr in the
filename, for example, nsp-telemetry-cr-va-sros-1.0.0-rel.10.zip

2
Install the artifact bundle from the Artifacts, Artifact Bundles view; see “How do I install an
artifact bundle?” in the NSP Network Automation Guide.
The telemetry types in the va bundle are now available in the Telemetry Statistic Search Tool.

3
Use the Telemetry Statistic Search Tool to see if you have the telemetry types you need:
1. Open the NSP Help Center. From the Help Center home screen, navigate to REFERENCE,
Statistic Search, Telemetry Statistic Search.
2. Enter search terms in the Counter Name field to filter on the counters you need.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 17
Telemetry NSP
Telemetry collection
What is a subscription?

Enter additional filters as needed to narrow the search.

3. Click on each row to see the Info panel. Verify whether the selected statistic is the one you
need.
4. If the telemetry types you need are found, this procedure is complete.
5. If the telemetry type is not found, proceed to the next step.

4
Perform the sequence in Step 1 to obtain any required telemetry yang files.

5
Extract the files from the zip and look for the telemetry types:
1. View the list of telemetry files. The filenames provide information about the telemetry types
included in the file.
2. Open the file and search for terms relevant to the counters you need. A counter, where
present, will be found in a leaf element. A list of telemetry types is provided in the leaf.
3. If you find a telemetry type you need, install the yang file using yang-file.bash; see
“How do I manage MDM model definitions?” in the NSP System Administrator Guide.

6
Obtain any required SR OS cut-through (ct) CR bundles from the Nokia Support Portal and
install them from the Artifacts, Artifact Bundles view; see “How do I install an artifact bundle?”
in the NSP Network Automation Guide.

Note: Cut-through telemetry types are for gNMI capable devices only.

7
Open the Telemetry Statistic Search Tool and search for your desired telemetry types.
If you do not find the definition or mapping you require, or you need to augment an existing
telemetry type, contact your Nokia service representative.

END OF STEPS

2.2 What is a subscription?

2.2.1 Subscription
A subscription represents a request for statistics information management.

2.2.2 User-configured subscriptions

You can configure telemetry subscriptions.
For an NE managed by NFM-P, the statistics you need must be collected by the NFM-P.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
18 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP
Telemetry collection
How do subscriptions work?

2.2.3 NSP-generated subscriptions

Baseline and indicator subscriptions are managed by Baseline Analytics and NSP Indicators
respectively, and are read-only in the Data Collection and Analysis, Subscriptions view.
Baseline Analytics is available with the Network Operation Analytics feature package, and NSP
Indicators is available with the Performance Indicators and Alerts installation option.

Note: To use Baseline Analytics and NSP Indicators with model-driven NEs, the
gnmiTelemetry installation option is also required.
NSP generates predefined OAM-related telemetry subscriptions in systems where MD-OAM is
deployed. OAM subscriptions appear in the Telemetry subscriptions list, prefixed with TestSuiteEx_
OAM. Do not edit predefined OAM subscriptions.

2.3 How do subscriptions work?

2.3.1 Statistics collection requirements
When you configure a telemetry subscription, you specify a set of statistics data and notification
and storage options for the data. To configure the data set, you select the type of statistics you are
interested in, the frequency of collection, and configure filtering by NE and counters as needed.
Statistics collection requirements and behavior depend on the NE management type, as described
in the following table.

Telemetry type Statistics configuration

MIB statistics for classic NEs Statistics collection and database storage must be configured in
NFM-P before creating a subscription in NSP.
The subscription tells NFM-P to publish any statistics that match
subscription requirements to Kafka as they are collected. 1
The interval specified in the subscription request is ignored.

CN telemetry using gRPC When the subscription is created, the NSP initiates collection of the
telemetry data from the NE at the specified interval.

MDM telemetry for statistics not supported by When the subscription is created, the NSP initiates collection of the
CN telemetry, on model driven NEs telemetry data from the NE at the specified interval.

Notes:
1. If statistics collection is set up in both NFM-P and NSP, the telemetry framework may receive the
same information twice. The duplication could result in incorrect reports or duplicated indicator
TCAs. Verify that data being used for telemetry, baseline, or indicator subscriptions is only
collected once. Disable equivalent MIB based statistics in NFM-P if gRPC telemetry is used.

2.4 What is an object filter?

2.4.1 Object filters
Object filters use XML Path (XPath) expressions against the NSP object YANG model to determine
which objects a subscription applies to.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 19
Telemetry NSP
Telemetry collection
How do object filters work?

The object filter is combined with the telemetry type to create the list of relevant statistics data.

2.5 How do object filters work?

2.5.1 Object filter components
An object filter is an XPath expression representing one or more network objects. The object filter
indicates the objects to collect telemetry data from, such as an NE or a list of ports.
An XPath is composed of a series of XPath elements. Each element represents a step on the
YANG model tree from left (root) to right (leaf or container). An element contains a name and a
series of optional predicates.
Example: network-element[ne-id='10.1.0.0']

2.5.2 Predicates
A predicate is an expression within square brackets that identifies the instance of each XPath
element. Keys and attributes of the object (as defined in the NSP model YANG) may be included.

Predicates can contain the following operators:

• =
• >
• <
• >=
• <=
• !=
• and
• or
Subexpressions can be enclosed in parentheses to enforce order of operations.

Note: Comparison operators use string comparators, so “value2” is greater than “value11”.
Examples:

[ne-id='10.1.0.0' or ne-id='10.1.1.1']

[(type='7750 SR-12' and product='7750 SR') and (version='TiMOS-B 19.0.R1'

or contains('version','15.0'))]

2.5.3 Predicate functions

The following functions are supported within a predicate:
• contains('attribute', 'search-text')
searches for all objects where the named attribute contains the search text
• containsIgnoreCase('attribute-name', 'search-text')

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
20 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP
Telemetry collection
How do object filters work?

same as contains() but conducts a case-insensitive search

• not(<binary-expression>|<function-expression>)
negates the result of the argument expression
• boolean ()
A boolean function may be used to find objects by searching through an object’s children and
references.
The boolean function returns true if at least one of the specified object references or children
satisfies the condition.
If a boolean function includes an instance-identifier object, the following requirements apply:
− the instance-identifier must be the only object in the predicate.
− the operator in the predicate must be =
− if there are multiple predicates, the format must be [predicate] [predicate]
Examples:
• [contains('component-id','port=1')]
• [not(contains('component-id','port=1'))]
• [contains('component-id','port=1') and not(contains('component-id',
'breakout'))]
• To find endpoints on a specified service:
/nsp-service:services/service-layer/eline[service-id='service_epipe_
12']/endpoint[boolean(service[nsp-model:schema-nodeid='/nsp-service:
services/service-layer/eline'][name='service_epipe_12'])]
• To find all ports with id 1/1/1/1 where mtu-value in the port-details has value 888:
/nsp-equipment:network/network-element/equipment/port[contains
(component-id,'shelf=1/slot=1/card=1/port=1') and boolean(port-details
[mtu-value = 888])]
In this example, the boolean function returns true only if an mtu-value of 888 is found in the
port details.
• To find the NEs associated with a specified controller:
/nsp-ne-control:ne-control/discovered-ne[boolean(controller[nsp-model:
schema-nodeid='/nsp-ne-control:ne-control/controller'][ne-id=
'NSP-24'])]

2.5.4 XPath expressions

An XPath expression is an XPath that can be evaluated to produce a list of XPath identifiers. For
the purpose of an object filter, the XPath expression must resolve to a NodeSet of NSP model
identifiers.
XPath expressions can be chained together using a union “|” operator, which evaluates each
subexpression independently into NodeSets and performs a set union operation to combine the
NodeSets into a single NodeSet result.
Expressions can be static expressions, which resolve to the same result every time, or wildcard
expressions, which can produce different results. The dynamic effect is created by using syntax that
does not specifically identify a set of NSP model objects: there is no wildcard character.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 21
Telemetry NSP
Telemetry collection
How do object filters work?

Examples:
MDM equipment: component-id='shelf=1/cardSlot=1/card=1/mdaSlot=1/mda=
1/port=1/1/1'
Classic equipment: component-id='shelf=1/slot=1/card=1/slot=1/card=1/port=1'
Example of a static expression:

/nsp-equipment:network/network-element[ne-id='10.1.0.0']
/hardware-component/port[component-id='shelf=1/cardSlot=1/card=1/mdaSlot=
1/mda=1/port=1/1/1' or component-id='shelf=1/cardSlot=1/card=1/mdaSlot=
1/mda=1/port=1/1/2'] | /nsp-equipment:network/network-element[ne-id=’10.
1.0.1’]/hardware-component/port[component-id='shelf=1/cardSlot=1/card=
1/mdaSlot=1/mda=1/port=1/1/3' or component-id='shelf=1/cardSlot=1/card=
1/mdaSlot=1/mda=1/port=1/1/4']
Examples of wildcard expressions:

Create a wildcard expression by not including all keys in the predicates.

• The following expression chooses all objects of type port on NE 1.1.1.1.
/nsp-equipment:network/network-element[ne-id='1.1.1.1']
/hardware-component/port
• The following expression chooses all objects of type port for all NEs.
/nsp-equipment:network/network-element/hardware-component/port
• The following expression returns all child objects that can respond to the selected telemetry type
and counters.
/nsp-equipment:network/network-element[ne-id='10.1.0.0']

2.5.5 Filtering models

Paths for MDM-managed NEs are based on the NE YANG models.

Device model
The NE YANG model used by NSP is network-device-mgr.
• This model uses device model xpath notation—this means that the filter can support all the paths
as implemented by the node. Creating a path using the device model is useful when the object is
not supported by, or not defined in, the NSP model.
• The device model provides a view of the device-specific paths. For example, an SR OS NE
defines an LSP object using a path similar to /network-device-mgr:
network-devices/network-device[name='10.1.0.0']/root/nokia-state:
state/router[router-name='Base']/mpls/statistics/lsp-egress[lsp-name=
'LSP1'].
The telemetry mapping artifact must contain a definition for the device path for telemetry to be
collected.
The following is an example of a network-device-mgr model filter type for an NFM-P managed
device. This filter targets a specific object instance by its FDN:

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
22 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP
Telemetry collection
What is a telemetry chart?

/network-device-mgr:network-devices/network-device[name='10.1.0.0']
/root/nokia-nsp-source:fdn[id='fdn:realm:sam:lsp:from-11.50.150.30-id-2']

Equipment model
The nsp-equipment:network model is a normalized NSP YANG model that provides a view of the
equipment for all network elements, abstracting the device specifics. Using NSP equipment model
identifiers is recommended because the models are supported by NSP applications. In addition,
filters based on the NSP equipment model can use operators such as AND or CONTAINS.
For example, the following path represents an individual port./nsp-equipment:
network/network-element[ne-id='10.1.0.0']/hardware-component/port[name=
'1/1/1']
Equipment model information can be found using the Network Inventory API; see the Postman
collection on the API Documentation page.
To assemble a filter, find the relevant model details and add predicates and predicate functions as
needed. For example, a get port operation provides the path to the port.

2.6 What is a telemetry chart?

2.6.1 Telemetry charts
A telemetry chart plots historical information if available, then streams real-time data on the same
chart.
For example, you can configure a chart to plot data from the last 12 hours, followed by current data.
This information can be useful in assessing changes.

Note: Historical data must be available; that is, data must have been collected and retention
polices must allow for the data to remain in the database.

2.7 How does telemetry charting work?

2.7.1 Telemetry charting
When you configure a telemetry chart in Data Collection and Analysis Visualizations, a new
telemetry data subscription is created to request historical and/or real time telemetry, as required by
the chart configuration.
If historical telemetry data is requested, the data is retrieved from the database. Historical data
must already be available in the database.

Note: The telemetry data subscription requests data from the database based on the
requirements configured for the chart, not on the subscription that collected the data.
If real time telemetry data is requested, a new telemetry subscription is automatically created to
request the data from the NEs. The telemetry chart plots data from the subscriptions created for
plotting.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 23
Telemetry NSP
Telemetry collection
How do I manage subscriptions?

If you open Data Collection and Analysis Visualizations by cross-launching from a telemetry
subscription in the Data Collection and Analysis Management, Subscriptions view, the New
Chart form displays the parameters configured in the telemetry subscription you cross-launched
from. When you click PLOT, Data Collection and Analysis Visualizations creates telemetry
subscriptions as needed to collect the data, and plots the data from the subscriptions it creates.
The subscriptions created for plotting do not save to the database or create file output.

2.8 How do I manage subscriptions?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

2.8.1 Steps

1
Open Data Collection and Analysis Management, Subscriptions.

2
To create a subscription:
1. Click SUBSCRIPTION.
2. In the Create Subscription form that opens, configure the General parameters as needed.
• Enable database (DB) subscriptions as needed to save subscription information to the
auxiliary database. For subscription data to be available to Analytics, it must be in the
auxiliary database.
• The subscription is enabled by default: it will start running immediately.
Choose Disabled in the State field if you want to enable your subscription later.
3. In the Object Filter field, enter filtering information as needed to filter the collected data.
As you type, the field provides suggestions for available filters to match your input and
identifies incorrect syntax.
4. Enter information in the Telemetry Type field. As you type, the field filters for available
telemetry types to match your input.
Choose the telemetry type you need from the list of matches.
5. When you enter a telemetry type, all counters are enabled by default.
To customize the counters, enable the Enable notifications and notification counters
check box.
Click Remove to remove a counter.
Click COUNTERS to add a counter that was removed.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
24 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP
Telemetry collection
How do I plot a telemetry chart?

6. Click CREATE.
The subscription begins collection when it is enabled.

3
To edit a subscription:
1. Choose a subscription and click (Table row actions), Edit.
2. In the form that opens, update the parameters as needed and click UPDATE.

4
To delete a subscription:
Choose a subscription and click (Table row actions), Delete.
The subscription is removed immediately.

Note: Removing a subscription does not remove data from the database. The data
collected by the subscription is retained according to the database retention policy.

END OF STEPS

2.9 How do I plot a telemetry chart?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

2.9.1 Before you begin

When you create a telemetry chart, you configure a telemetry filter. For historical data to be
displayed, the data must be available in the database; see 2.8 “How do I manage subscriptions?”
(p. 24).
Charts are created by streaming to the plotter: historical data is queried and streamed to the plotter,
then real time telemetry subscriptions are created and the data from these subscriptions is
streamed to the plotter.
Data Collection and Analysis Visualizations times out if telemetry data is not received. The time-out
limit is either double the collection interval or two minutes, whichever is greater.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 25
Telemetry NSP
Telemetry collection
How do I plot a telemetry chart?

2.9.2 Steps

Create a chart

Open the New Chart window:

• From Data Collection and Analysis Visualizations, Telemetry Charts, click CHART.
• From Data Collection and Analysis Management, Subscriptions, choose a subscription
and click (Table row actions), Open in Data Collection and Analysis Visualizations.

2
In the window that opens, configure the parameters in the top panel:
1. Configure the Collection Interval parameter. If you are using NFM-P telemetry data, verify
that the collection interval is long enough to allow time for Visualizations to receive the data
before timing out.
2. From the Time Range drop-down list, choose the amount of historical data to display.
3. Click Combine charts to plot data from multiple data series on the same chart.

3
Click DEFINITION.
The telemetry and resource filter definition panels are displayed.

4
Enter information in the Telemetry Type field. As you type, the field filters for available
telemetry types to match your input.
Choose the telemetry type from the list of matches.

5
Choose counters to display from the Counters drop-down list.

6
In the Object Filter field, enter filtering information to filter the collected data.

If you need to save the configuration as a chart:

1. Click SAVE AS.
2. In the window that opens, enter a name for the chart and add a description if needed.
3. Click SAVE.
The chart is added to the list.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
26 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP
Telemetry collection
How do I plot a telemetry chart?

8
Click PLOT.

END OF STEPS

2.9.3 Steps

Plot an existing chart

1
To plot an existing chart with no changes:
1. Open Data Collection and Analysis Visualizations, Telemetry Charts.
2. Choose a chart and click (Table row actions), Chart.

2
To edit a chart and plot it, choose the chart and click (Table row actions), Edit.

3
Edit the parameters as needed and click PLOT.

END OF STEPS

Result
Visualizations displays a chart view showing the streaming data. While data is streaming, you can
configure the Group by parameter in the upper left of the chart view to change how the data is
grouped or click Configure in the upper right to view or change the configuration of the chart.
Click (Chart Details) to open the Chart Details panel on the right side of the chart view to show
details about the resources.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 27
Telemetry NSP
Aggregation
What is aggregation?

Aggregation

2.10 What is aggregation?

2.10.1 Aggregation
Aggregation is the practice of combining measurements for analysis. In the NSP, telemetry data is
aggregated based on time period of collection: hourly, daily, weekly, or monthly. When a report is
run in Analytics, the granularity parameter in the report determines which aggregated data set is
analyzed. For example, if you select hourly granularity, the report shows the hourly aggregated
data. Some reports can use raw data, that is, data that is not aggregated, but this is not available
for all reports.

2.10.2 What is an aggregation rule?

An aggregation rule defines how the data for a specified telemetry type is aggregated and how long
each aggregated data set is retained.
Aggregation rules for model-driven telemetry are configured on the NSP server. They can be
viewed and edited in NSP.
For aggregation information to be available, the auxiliary database must be configured and running.
Use the NFM-P to configure aggregation rules for data collected by the NFM-P; see the NSP
Analytics Report Catalog.

2.10.3 What is the aggregation time zone?

The aggregation time zone is the time zone that is used to determine the start and end time of data
to be aggregated:
• hourly aggregation: from xx:00 to xy:00
• daily aggregation: from midnight to midnight
• weekly aggregation: from midnight Monday to midnight Monday
• monthly: from midnight on the 1st of the month until midnight on the first of the following month

2.11 How do I set the aggregation time zone?

NOTICE

Changing the aggregation time zone changes the start and end times of all future
aggregations. The first aggregation following the change may miss data or count data twice
due to the difference in time zones.

2.11.1 Steps

1
Open Data Collection and Analysis Management, Aggregation.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
28 3HE-20004-AAAA-TQZZA Issue 1
Telemetry NSP
Aggregation
How do I edit aggregation information?

2
Click (More Actions), Time Zone Setting

3
In the form that opens, enter a time zone in the Aggregation Time Zone field.
As you type, the list of available time zones is refined to match your input.

4
Choose the time zone from the list.

5
Click OK in the confirmation dialog.

6
Click SAVE.

END OF STEPS

2.12 How do I edit aggregation information?

Note: For the Aggregation view to be available, the auxiliary database must be configured and
running.

2.12.1 Steps

1
Open Data Collection and Analysis Management, Aggregation.

2
Choose an aggregation rule and click (Edit).

3
In the form that opens, edit the parameters as needed and click UPDATE.

END OF STEPS

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 29
Telemetry NSP
Age-out policy
What is an age-out policy?

Age-out policy

2.13 What is an age-out policy?

2.13.1 Age-out policy
An age-out policy is a retention policy for stored data. Data older than the retention period is purged
from the database.
NSP creates a policy for each telemetry type, a policy for baselines, and a policy for indicators.

2.14 How do I edit an age-out policy?

2.14.1 Steps

1
Open Data Collection and Analysis Management, Age-Out Policy.

2
Open the Edit form:
a. To edit a telemetry policy, choose Telemetry from the drop-down list, choose a policy and
click (Edit).
b. To edit the baseline or indicator policy, choose the policy type from the drop-down list.

3
Edit the retention period and click UPDATE.

END OF STEPS

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
30 3HE-20004-AAAA-TQZZA Issue 1
Baseline Analytics NSP

3 Baseline Analytics

3.1 What is a baseline?

3.1.1 Baselines and anomalies
Baselines and anomaly detection are included with NSP Baseline Analytics.
A baseline detects a historical trend and generates expected values based on the trend.
Baseline and anomaly charts and the list of anomalies are available in Data Collection and Analysis
Visualizations.
To open Data Collection and Analysis Visualizations for a baseline, choose the baseline and click
(Table row actions), Open in Data Collection and Analysis Visualizations. The view opens to
a New Chart form with the baseline selected.
RESTCONF APIs are available for Baseline Analytics; see the Network Infrastructure Management
API documentation on the Network Developer Portal.

3.2 What is an anomaly?

3.2.1 Anomalies
An anomaly is a value that deviates enough from a baseline’s expected value to be flagged for
attention. You can configure anomaly thresholds as part of baseline creation.

Note: A baseline must be trained for at least one season before expected values can be
charted. Detection of anomalies requires one or more seasons depending on the detector.
See 3.3 “How do baselines and anomalies work?” (p. 31) for more information.

3.3 How do baselines and anomalies work?

3.3.1 Components
A baseline provides the logic for the collection of baseline statistics, and for the detection of
anomalies.
When you create baselines, you specify a resource or group of resources to collect a set of
statistics over a defined time window. Information collected during that window is used to calculate
a data point for the baseline. You also define a season, which is the length of time statistics need to
be measured to assess trends. For example, to assess network traffic, you could set up a 15-
minute window with a one-week season, which provides values calculated every 15 minutes over a
one-week period.
Creation of a baseline creates a baseline subscription to collect the required data.

Note: Baseline subscriptions and telemetry subscriptions are separate. A baseline cannot be
generated from data collected by a telemetry subscription.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 31
Baseline Analytics NSP
How do baselines and anomalies work?

On-demand NFM-P statistics cannot be used to create baselines.

A baseline consists of the following components. The components appear in the Create and Edit
forms.
• General parameters
• Filter & Counters
• Anomaly Detectors
Baselines are created on a per-resource basis. A resource is an entity that can collect the desired
statistics. In the Create Baselines form, you configure the required parameters and choose the
resources to collect the statistics.
If the NE is managed using MDM, configuration of a baseline initiates statistics collection. If the NE
is managed by NFM-P, statistics collection must be configured on the NFM-P and the resource
must already be collecting the desired statistics for a baseline to be created.

Note: Baseline Analytics is different from the NSP Analytics application.

Baseline Analytics provides near-real-time baseline and anomaly detection from telemetry
counters, for example, received octets for the /telemetry:
base/interfaces/interface telemetry type.
The Analytics application computes a baseline for data configured for reporting, for example,
utilization and throughput for a port in a Port LAG Details report, or bandwidth and data for an
application group in a Router Level Usage Summary report with Baseline. See the Analytics
Report Catalog and the NSP User Guide for more information about Analytics.

3.3.2 Baseline Analytics data storage

Baseline data is stored in Postgres, unless there is an auxiliary database enabled, in which case all
collected data goes in the auxiliary database.

The following data is stored:

• statistics data collected during the configured window; see General parameters
• the calculated baseline for the window
• anomalies
By default, data is stored in Postgres for 35 days and in the auxiliary database for 90 days. These
values can be changed using the RESTCONF API or by updating the age-out policy; see 2.14 “How
do I edit an age-out policy?” (p. 30).

3.3.3 General

The general parameters include the following:

• Description
Add an optional description for filtering on the Baselines view.
• Collection interval

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
32 3HE-20004-AAAA-TQZZA Issue 1
Baseline Analytics NSP
How do baselines and anomalies work?

For MDM managed NEs, this represents the interval at which to collect the statistics, for
example, every 30 seconds. For NEs managed by the NFM-P, this value is ignored and statistics
are collected according to the settings configured in the NFM-P.
• Season
A season is the length of time statistics must be collected for a pattern to be seen. For example,
for network traffic you can expect the data pattern to repeat on a weekly basis.
• Window duration
Window duration is the size of the data bucket for telemetry calculation. For example, a counter
calculates the change between the first and last values taken during the window. The calculation
used depends on the counter type parameter in the Filters & Counters panel.
• Admin State and Training Status
These parameters are enabled by default when a baseline is created. They can be changed in
the Edit form.
− Admin State
If the Admin State of a baseline is Enabled, NSP is monitoring the statistics.
− Training Status
If the Training Status is Active, NSP is incorporating new information into the baseline’s
model. If the Training Status is paused, future anomalies will be detected against the
expected values that are already calculated.
If you are monitoring for error counters, such as packet loss, you can pause learning after a
season with no errors, which sets the expected number of errors to zero, while continuing to
monitor.
For example, if you create a baseline and set the Collection Interval to 30, the Season to 1 week,
and the Window Duration to 15 minutes, the baseline subscription collects the statistics values
every 30 seconds, calculates a baseline data point every 15 minutes, and assesses trends based
on one week of data.

3.3.4 Filter & Counters

The Filter & Counters parameters declare the telemetry values to be collected, the counter types,
and the resources of interest.
When a telemetry type is selected, the COUNTERS button becomes available.

You can configure one of the following counter types:

• Counter: a counter takes input counter values and calculates the change in value over the
window. For example, if the counter represents the number of transmitted octets and windows
are 15 minutes, a counter baseline value is the number of octets transmitted over 15 minutes.
• Gauge: a gauge takes input values and calculates the mean value over the window. For
example, if the input value is octets per second over a 30 second period and windows are 15
minutes, a gauge baseline value is the mean octets per second over 15 minutes.
An example of a gauge is CPU usage: it is a bounded value between 1 and 100%.
• Sampled: a sampled baseline takes sampled values and calculates the sample mean value over
the window. Sampled values represent the value at the exact time the sample was taken, not the

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 33
Baseline Analytics NSP
How do baselines and anomalies work?

value since the last sample was taken. For example, if CPU % is sampled every 2 minutes and
windows are 15 minutes, a sampled baseline value is the sampled mean over the samples
collected in the 15 minutes.
An example of a sampled value is latency.
Configure an object filter as needed to filter the available resources; see 2.5 “How do object filters
work?” (p. 20).
When at least one counter is added and a counter type is specified, the VERIFY RESOURCES
button becomes available.

3.3.5 Detectors
A detector defines the rules for anomaly detection. The detector rule provides an acceptable range
of expected values. If a detected value exceeds the range, it is marked anomalous.
Anomaly detection is optional.

A detector rule is composed of the following:

• algorithm — the formula to use to compare the expected and measured values
• comparison — greater than or less than
• evaluate what — value, rate, or bandwidth
The measured values may be converted to a rate or bandwidth to perform the evaluation:
− rate — value / window
− bandwidth — (value *8) / window
• threshold —the end of the acceptable range
The comparison and threshold parameters define the range of acceptable values. For example, a
rule could state that a value with an absolute Z-score greater than 2 is an anomaly.

Algorithms
You can define a rule based on an algorithm.

The following algorithms are suitable for most purposes:

• Z-score
This refers to the Z-score (number of standard deviations) of the measured value against the
expected values. In this case, the expected value is the mean.
Formula: (measured - expected) / stddev
• Z-score absolute
This refers to the absolute value of the Z-score of the measured value against the expected
values. In this case, the expected value is the mean.
Formula: |(measured - expected) / stddev|
The Z-score algorithms are useful because they incorporate the standard deviation: in addition to
recording how far the current value is from the mean, the algorithm also factors in the variability of

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
34 3HE-20004-AAAA-TQZZA Issue 1
Baseline Analytics NSP
What should I know about baseline and anomaly detector creation?

the values. This can be very important when deciding if a value is anomalous. If your values are
highly variable, that is, the standard deviation is high, it is important to choose a Z-score algorithm.

You can also use one of the following:

• relative difference mean
This is the relative difference using the absolute value of the arithmetic mean of the measured
and expected values.
Formula: |measured - expected| / (|measured + expected| * 0.5)
This algorithm could be suitable if the standard deviation is very small, that is, if there is very little
variation in the values.
• relative change signed
This is the relative change (including the positive or negative sign) between the measured and
expected values.
Formula: (measured - expected) / |expected|
• relative change
This is the relative change (with no sign) between the measured and expected values.
Formula: |measured - expected| / |expected|
• change over mean
This is the change of the measured and expected values over the absolute value of the
arithmetic mean.
Formula: (measured - expected) / (|measured + expected| * 0.5)
• change max score
This is a score that becomes more sensitive as the measured or expected value approaches
+/–100. This detector algorithm works well with percentages although it may have use with other
types of values.
Formula: (sign(measured - expected) * (|measured - expected| +
max(measured,expected))) / 200

3.4 What should I know about baseline and anomaly detector

creation?
3.4.1 Baseline best practices
When baselines are configured, NSP creates a baseline with the parameter values for each
resource selected. For example, if you want to collect baseline values for 20 ports with the same
telemetry type, configure the Create Baselines parameters and NSP will create 20 baselines.
Bulk creation of baselines can take significant time and resources to complete. If the bulk creation
process is interrupted by a network disruption or user action, it results in failed or partial creation.
If a baseline creation process has been interrupted by a network problem or user action (such as a
page refresh), incorrect entries may exist in the database. Contact Nokia support.
Keep these suggestions in mind:
• The collection interval configured in NSP is ignored by resources that are managed by NFM-P.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 35
Baseline Analytics NSP
How do I create baselines?

Instead, the collection interval of resources managed by NFM-P is determined by the

corresponding NFM-P MIB entry policy.
• Use object filters in the Create Baselines form to target the resources you need.
• Avoid unfiltered baseline creation requests unless the network is limited in size.
• If you configure the Convert to Bitrate parameter for a baseline counter and want to detect
anomalies, set the Evaluate What parameter in the detector rule to Bandwidth. Using a different
evaluation setting results in a mismatch between the Anomalies list in Visualizations and the
baseline and anomaly chart generated for the baseline.
• Ensure that you have enough time to wait for the creation operation to complete before
configuring baseline creation.
The following table shows some average time frames for bulk baseline creation.

Number of baselines Average maximum time required

100 30 s

1000 3 min

5000 15 min

10 000 30 min

Note: The baseline subscriptions are created last, therefore no statistics are collected for any
baseline in the group until the bulk creation is completed.

3.5 How do I create baselines?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

Important! If you are creating multiple baselines, the create operation may take a long time
and cannot be stopped. Ensure that you are able to wait for the operation to complete before
proceeding. For example, average maximum time required for creation of 100 baselines is 30
s; average maximum time required for creation of 10 000 baselines is 30 min.

3.5.1 Steps

1
Open Data Collection and Analysis Management, Baselines.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
36 3HE-20004-AAAA-TQZZA Issue 1
Baseline Analytics NSP
How do I create baselines?

2
Click BASELINES.

3
In the Create Baselines form that opens, configure the General parameters as needed.

4
Enter information in the Telemetry Type field. As you type, the field filters for available telemetry
types to match your input.
Choose the telemetry type you need from the list of matches.

5
Click COUNTERS .

6
In the Add Counters form that opens, choose the required counters and click ADD.

7
Configure the Counter parameters as needed.

8
Click COUNTERS to add additional counters.

9
In the Object Filter field, enter filtering information as needed to filter the collected data.
As you type, the field provides suggestions for available filters to match your input and identifies
incorrect syntax.

10
Click VERIFY RESOURCES.
NSP searches for resources that are collecting statistics to match the telemetry type and object
filter.

Note: NFM-P resources appear in the list after the NFM-P collects the statistics.
Therefore, you need to wait for the current collection interval to end before the NFM-P
resource appears in the list.
If needed, you can click STOP VERIFICATION at any time and Edit Filters & Counters to
update the configuration and restart the verification process.

11
When the resources you need appear in the resources list, click STOP VERIFICATION.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 37
Baseline Analytics NSP
How do I edit or delete baselines?

12
Select the resources you need in the resources list.

13
In the Detectors panel, add a rule for each counter as needed:
1. Click RULE.
2. Configure the rule parameters.
Repeat steps 1 and 2 to add detector rules for other counters.

14
Click CREATE.

END OF STEPS

3.6 How do I edit or delete baselines?

3.6.1 Steps

1
Open Data Collection and Analysis Management, Baselines.

2
Choose a baseline and click (Table row actions), Edit.

3
To stop or restart monitoring, change the Admin State parameter.
If the admin state is Disabled, NSP stops monitoring the statistics.

4
To stop or restart training, change the Training Status parameter.
If the training status is Paused, new data will no longer affect the calculated baseline.

5
To reset training:
1. If the Admin State is Enabled, select Disabled from the drop-down list and click UPDATE.
2. Click RESET BASELINE WINDOWS and click APPLY to confirm.
3. Wait a minimum of 15 min.
You can close the form while you are waiting, if needed.
4. Click RESET BASELINE WINDOWS again and click APPLY to confirm.
5. Set the Admin State to Enabled and click UPDATE.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
38 3HE-20004-AAAA-TQZZA Issue 1
Baseline Analytics NSP
What is a baseline chart?

To edit detectors:
1. Click (Delete) to remove the existing detector.
2. Click RULE.
3. In the Detector Rule form that opens, configure the new parameters.
4. Click TEST to preview how your changes will impact the range of expected values.
5. Click ADD.

7
Click UPDATE.

8
To delete baselines:
a. Select one or more baselines and click (Table row actions), Delete.
In the form that opens, confirm the deletion.
b. From Data Collection and Analysis Management, Subscriptions, select a baseline
subscription and click (Table row actions), Delete.
Deleting the subscription also deletes all associated baselines.

END OF STEPS

3.7 What is a baseline chart?

3.7.1 Baseline charts
A baseline chart plots captured telemetry data for a specified period, along with baseline expected
values and the range relative to the expected value that is considered normal by the anomaly
detectors, that is, the range of values that are not anomalies.
Anomalies are indicated where they are detected.

Note: A baseline must be trained for at least one season before expected values can be
charted. Detection of anomalies requires one or more seasons depending on the detector.
See 3.3 “How do baselines and anomalies work?” (p. 31) for more information.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 39
Baseline Analytics NSP
How do I plot a baseline chart?

3.8 How do I plot a baseline chart?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

3.8.1 Steps

Create a chart

Open the New Chart form:

• From Data Collection and Analysis Visualizations, Baseline Charts, click CHART.
• From Data Collection and Analysis Management, Baselines, choose a baseline and click
(Table row actions), Open in Data Collection and Analysis Visualizations.

2
In the form that opens, configure the parameters in the top panel as needed:
• From the Time Range drop-down list, choose the amount of historical data you need to
display.
• Click Combine charts to plot data from multiple data series on the same chart.

3
Click BASELINES.
The list of available baselines is populated.

4
Choose one or more baselines from the list and click ADD.

To save the chart:

1. Click SAVE AS.
2. In the window that opens, enter a name for the chart and add a description if needed.
3. Click SAVE.
The chart is added to the list.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
40 3HE-20004-AAAA-TQZZA Issue 1
Baseline Analytics NSP
How do I chart an anomaly?

6
Click PLOT.

END OF STEPS

3.8.2 Steps

Plot an existing chart

1
To edit a chart before you plot it, choose the chart and click (Table row actions), Edit.

2
Edit the parameters as needed and click PLOT.

END OF STEPS

Result
Visualizations displays a chart view showing the baseline and anomaly data. From the chart view,
you can change the information displayed: choose a different time range, click Configure to change
the list of baselines or click , Combine charts to turn combined charts on or off.
Click (Chart Details) to open the Chart Details panel on the right side of the chart view to show
details about the resources.
Hover over any point on the chart to see measured values, expected values, and range at the
indicated point.

3.9 How do I chart an anomaly?

3.9.1 Purpose
The Anomalies view shows the table of anomalies that have been detected and saved to the
database. The table provides information about each anomalous value and why the value was
flagged as an anomaly. You can filter the table according to the baseline name, resource, counter,
or telemetry type.

3.9.2 Procedure
You can chart an anomaly from the Data Collection and Analysis Visualizations, Anomalies
view.
1. Select the anomaly and click Chart .
The chart displays, showing the three hours before and after the selected anomaly.
2. From the chart form, click Configure to change the time range or add additional baselines if
needed.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 41
Baseline Analytics NSP
How do I chart an anomaly?

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
42 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP

4 NSP Indicators
Indicators

4.1 What is an indicator?

4.1.1 Indicators
An indicator is a subscription to a customized metric. Indicators allow you to define and track KPIs
using a combination of telemetry data, arithmetic operators, and aggregation functions. Thresholds
can also be included in the indicator, with actions that are triggered by threshold violations.
For example, you can create an indicator to track the average utilization of a three-node ring:
utilization counters on the selected ports and LAGs in the ring are tracked and aggregated.
Thresholds are set for rising and falling average utilization at specified values, generating alarms
when the average utilization is outside the preferred range.
Creation of an indicator creates an indicator subscription to collect the required data.

Note: Indicator subscriptions and telemetry subscriptions are separate. An indicator cannot be
generated from data collected by a telemetry subscription.
On-demand NFM-P statistics cannot be used to create indicators.
Indicator charts and a list of threshold crossing events are available in Data Collection and Analysis
Visualizations.
To open Data Collection and Analysis Visualizations for a selected indicator, choose the indicator
and click (Table row actions), Open in Data Collection and Analysis Visualizations. If the
indicator has multiple outputs, choose the resources in the form that opens, click (Add) and click
OPEN IN DATA COLLECTION AND ANALYSIS VISUALIZATIONS. The view opens to a New
Chart form with the indicator resources selected.
RESTCONF APIs are available for NSP Indicators; see the Network Infrastructure Management API
documentation on the Network Developer Portal.

4.2 How do indicators work?

4.2.1 Indicator components
An indicator consists of the following components:
• General parameters
• Filter & Counters
• Thresholds
The components appear in the Create and Edit forms.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 43
NSP Indicators NSP
Indicators
How do indicators work?

4.2.2 Sample indicator

An example indicator tracks average utilization for a three-node ring, sampling from four ports and a
LAG in the ring. Alarms are generated if average utilization is increasing above 50% or decreasing
below 5%.

4.2.3 General

The general parameters include the following:

• unique name and optional description
• collection interval
For NEs managed by MDM, this represents the interval for collecting the statistics (for example,
every 30 s), while for NEs managed by the NFM-P, this value is ignored and statistics are
collected according to the settings configured in the NFM-P.
• window duration
Window duration is the size of the data bucket for telemetry calculation.

Note: For simple indicators, that is, indicators with only one counter and no formula, there is
no data bucket. The window duration is ignored; KPI values are calculated at the collection
interval.

4.2.4 Counters&Formula
The Counters & Formula parameters declare the telemetry values to be collected and the
operations and aggregation functions to apply. An object filter ensures that the data is collected on
the resources of interest.
• counters
When a telemetry type is selected, the ADD COUNTERS button becomes available.
For the sample indicator, selecting the /telemetry:base/interfaces/utilization telemetry type allows
collection of the input-utilization counter.
• formula
A formula applies arithmetic operators and aggregation functions to the counters. The following
can be applied:
− arithmetic operators: addition, subtraction, multiplication, division, absolute value
− aggregation functions: minimum, maximum, sum, average
For the sample indicator, the formula is configured to provide an average of the counter value data.
See 4.3 “How do indicator formulas work?” (p. 46) for details.

Object filter
Configure an object filter as needed to filter the available resources; see 2.5 “How do object filters
work?” (p. 20).
When at least one counter has been selected, the VERIFY RESOURCES button becomes
available. Check the contents of the resource list to ensure that your object filter is retrieving the
correct objects.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
44 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicators
How do indicators work?

For the sample indicator, the object filter determines the ports and LAGs to collect information from.

4.2.5 Thresholds
Thresholds define the preferred range of data values for the indicator. Thresholds are optional: you
can create zero, one, or multiple thresholds, for increasing or decreasing values.
When the indicator is plotted in Visualizations, thresholds appear on the plot and threshold crossing
events are indicated.

Each threshold can be configured to trigger one or more actions:

• raise a threshold crossing alarm (TCA)
The TCA is raised in Current Alarms.
• generate email
An email can be generated for each threshold crossing event or aggregated by time period or
number of events.
Email server settings must be configured in NSP Settings by an administrator.
• output a message to a Kafka topic
The Kafka topic must already be created. The default topic is nsp-act-action-event.

Note: Indicator alarms may still be raised shortly after a resource (for example, an NE) is
unmanaged in NSP if statistics messages are already in the system waiting to be processed.
For the sample indicator, you can configure an example threshold, with:
• an increasing threshold for a value of 50
• an alarm action with major severity
• a falling threshold for a value of 5 with a Kafka message showing low utilization
This configuration allows for high and low utilization to be handled differently according to differing
levels of urgency. If needed, another increasing threshold could be set at 40, for example, with
warning severity, to tell operators that the ring may need attention.

Threshold crossing alarms

Indicator TCAs appear in Current Alarms as alarms with Source System “fdn:app:nsp-indicator” and
Alarmed Object Type “nsp-indicator:rta-indicator-rules/rule”. The Alarmed Object ID contains the
indicator rule name and the Additional Text contains the threshold violation details.
The Object Full Name field contains the indicator name and the specific object instance. For
aggregate TCAs, where the aggregation functions such as avg() or sum() are used, the threshold
violation may be based on statistics from multiple objects, and therefore cannot be attributed to a
single object instance. In this case, the Object Full Name field contains the name of the indicator
rule.
Visibility of TCAs depends on user access control settings.
• Aggregate TCAs do not contain a Site ID or Site name, and are considered system level alarms.
To view these alarms, the user must either have the Administrator role, or have both Access to
all Equipment and Access to all Services enabled.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 45
NSP Indicators NSP
Indicators
How do indicator formulas work?

• If the user has access to certain NEs only, the user sees Indicator TCAs for those NEs, but no
aggregate TCAs.

4.2.6 Simple and complex indicators

Simple indicators use a single counter and no formula. A simple indicator is evaluated every
collection interval, for every resource returned by the object filter.
Complex indicators use one or more counters and a formula. A complex indicator uses counter
statistics received during each window duration to aggregate each incoming counter from each
resource into a counter function. This output is then, depending on the formula, used in arithmetic
or aggregation operations, or both, to calculate the KPI.

4.2.7 Indicator data storage

Indicator data is stored in Postgres unless there is an auxiliary database enabled, in which case all
collected data is stored in the auxiliary database.
By default, data is stored in Postgres for 35 days, and in the auxiliary database for 90 days. These
values can be changed using the RESTCONF API or by updating the age-out policy; see 2.14 “How
do I edit an age-out policy?” (p. 30).

4.3 How do indicator formulas work?

4.3.1 Formula components
An indicator formula defines the calculation of a KPI value. A formula is optional if only one counter
is configured.
Formulas are composed of the following components, combined as needed.

Component Definition Notes

Counter functions Aggregation functions performed on a per-counter basis The following function types are
with one value output per counter for each resource. The available on a counter:
output of the counter function is then used in the rest of • sum: adds up all samples received
the formula calculation. for the counter during the window
Counter functions are expressed as counter_function, for duration. Sum is used for counted
example, input-utilization_avg. statistics such as octets or packets.
• avg: the average of all samples
received for the counter during the
window duration. Avg is used for rate
or value statistics such as
percentage or temperature.
• min/max: the minimum or maximum
value of all samples received for the
counter during the window duration.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
46 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicators
What should I know about indicator creation and management?

Component Definition Notes

Arithmetic Simple arithmetic operations using one or more counters The following arithmetic operations
operations received from each unique resource. These operations can be performed:
produce n KPI outputs (one per resource), per window
• addition (+)
period. Operations can include counter functions and
numbers. Negative numbers must be in parentheses. • subtraction ( — )
An example of an arithmetic expression is: • multiplication (*)
|({received-octets-periodic_sum} — {transmitted-octets-
• division (/)
periodic_sum})| * 8 / 60
• absolute value (| |)

Aggregation A formula can perform aggregations on one or more The following aggregation operations
functions counters received from every resource. This aggregation are available:
produces a single indicator output (one KPI value for all
• min
resources) per window period.
An aggregation operation can perform multiple • max
aggregation operations and can include arithmetic • sum
operations. For example, a formula for average
• avg
utilization in the sample indicator is: avg({input-
utilization_avg})

An example formula combining the components is: max(({transmitted-octets-periodic_

sum}+{received-octets-periodic_sum})*8/60)/sum({speed_avg})*100
This formula creates a single mixed-expression-operator that has two aggregation operations: the
first outputs the port with the maximum value of ((tx+rx)*8/60), the second sums the speed of all
ports. These two outputs are then divided and the result multiplied by 100.

4.4 What should I know about indicator creation and management?

4.4.1 Indicator best practices

Keep the following notes in mind when creating and managing indicators:
• Consider the following when you set the collection interval and window duration:
− The collection interval configured in NSP is ignored by resources that are managed by
NFM-P. Instead, the collection interval of resources managed by NFM-P is determined by the
corresponding NFM-P MIB entry policy.
− When configuring an indicator with a formula for resources managed by NFMP, the window
duration must be at least twice as long as, and be a multiple of, the NFM-P MIB policy. An
example is a 5 min MIB policy and a 15 min window duration.
− When configuring an indicator with a formula for resources managed by MDM, the window
duration must be at least twice as long as, and be a multiple of, the collection interval.
• Avoid divide-by-zero scenarios when constructing formulas. Arithmetic operations that are
divided by zero produce no output, while aggregation operations output zero from the operation
that is divided by zero.
• Before completing indicator creation, it is the best practice to verify resources to ensure you see
a reasonable value for each counter.
Certain counters may not be fully supported in an NE managed by NFM-P and they default to
zero, which causes an unexpected calculated KPI value. Other counters may have an actual

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 47
NSP Indicators NSP
Indicators
What should I know about indicator creation and management?

value of zero. For example, a value of zero for a speed counter can indicate a down port—that
is, an actual value of zero speed—or a counter that does not appear in the relevant mapping
artifact.
• Clicking VERIFY RESOURCES in an indicator shows the network device identifiers for the
resources that respond to the object filter. The network device identifier is the unique identifier
included by the NE in the telemetry messages.
The network device indicator is also the NE identifier used for indicator charting and threshold
events in Visualizations.
• If an indicator configuration is updated, the indicator restarts, causing an expected gap in data
until it can start collecting data with the new window duration.
• Indicator data points are normalized to the start of the window duration. For example, for an
indicator with a window duration of 15 min, the data point or threshold event at 16:15 on the
chart represents the window from 16:15 to 16:30.
• Data points for simple indicators are output immediately after the window duration ends.
• Output from Indicators with formulas:
The data required by the formula must be received and processed after the window duration
ends before generating the Indicator value.
Example: Indicators with a 5-minute collection interval and 15-minute window duration. The
15-minute collection window starts at midnight (00:00 to 00:15).
After the window closes, the indicator waits for the next set of messages to be received before
proceeding to calculate the indicator value for the previous window. When a message is received
with a time stamp after 00:15, it confirms that all messages from the 00:00 to 00:15 window have
been received and the value can be calculated.
− Indicators with arithmetic operations require one additional collection interval.
− Indicators with aggregation operations require one additional collection interval and one
window duration.
− Output from an indicator with an arithmetic formula requires an additional 5 minutes (the
collection interval).
For example, consider formula: {received-octets-periodic_sum}+{transmitted-octets-periodic_
sum}
The data point for the 00:00 to 00:15 collection window is processed at 00:20. The sum can
be calculated when the next collection occurs and a value for after 00:15 is received.
− Output from an indicator with an aggregate formula requires an additional 20 minutes (the
collection interval, plus the window duration).
For example, consider formula: sum({received-octets-periodic_sum}+{transmitted-octets-
periodic_sum})
The data point for the 00:00 to 00:15 window is processed at 00:35.
The example formula is a sum of values which are collected at an interval. Each of these
values is confirmed when the next interval starts, at 00:20. After the values are confirmed, the
sum can be calculated. The sum is confirmed when another aggregated message from after
00:15 is received, at 00:35.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
48 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicators
What is an indicator chart?

4.5 What is an indicator chart?

4.5.1 Indicator charts
Indicator charts are available with the NSP Network Infrastructure Management feature package.
An indicator chart plots calculated KPI data for a specified period along with configured thresholds.
If at least one threshold has been defined; that is, the Thresholds Configured parameter is True, the
threshold values are displayed when hovering on the far right-hand edge of the indicator chart.
Rising and falling thresholds appear on the chart as dotted lines. Threshold crossing events are
indicated where they are detected.

4.6 What is a threshold crossing event?

4.6.1 Threshold crossing events (TCEs)
A threshold crossing event is a value that exceeds an indicator threshold. You can configure
thresholds as part of indicator creation.

4.7 How do I create an indicator?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

4.7.1 Steps

1
Open Data Collection and Analysis Management, Indicators.

2
Click INDICATOR

3
In the Create Indicator form that opens, enter a unique name for the indicator.

4
Configure the collection interval and window duration parameters.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 49
NSP Indicators NSP
Indicators
How do I create an indicator?

5
If needed, click APPLY TEMPLATE at the top right of the window, select a template from the
list, and click APPLY.
The parameters configured in the template appear in the Create Indicator form. These
parameters can be changed.

Configure the counters and formula as needed:

1. Enter information in the Telemetry Type field. As you type, the field filters for available
telemetry types to match your input.
Choose the telemetry type from the list of matches.
2. Click COUNTERS.
3. If you have chosen more than one counter, a formula is required; see 4.3 “How do indicator
formulas work?” (p. 46).
Enter information in the Formula field. As you type, the field identifies incorrect syntax.

7
In the Object Filter field, enter filtering information as needed to filter the collected data; see
2.5 “How do object filters work?” (p. 20).
As you type, the field provides suggestions for available filters to match your input and identifies
incorrect syntax.

8
Click VERIFY RESOURCES to ensure that the resources found by the object filter are correct
for your requirements and that counter values are returned.

Configure thresholds as needed:

1. Click THRESHOLD.
2. In the Add Threshold window that opens, enter a threshold value in the Threshold field.
3. Choose a direction from the drop-down list.
4. Click ADD.
5. Add additional thresholds as needed.

10

Configure threshold actions as needed:

1. Click on a threshold you created in Step 9.
2. Click ACTION and choose Alarm, Email, or Kafka from the drop-down list.
• To configure an alarm, choose the severity from the drop-down list.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
50 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicators
How do I edit or delete an indicator?

• To configure an email action, enter recipient email addresses, separated with commas,
and enter boilerplate information in the Subject and Content fields.
To aggregate emails, enable the Aggregation toggle and configure the parameters. For
example, the default value of 5 in the Period and Number of Events fields will send an
email every five min, and for every five threshold crossing events, whichever comes
sooner.
• To configure a Kafka message, enter an existing topic name and enter the message
information in the Content field.
3. Add additional actions for each threshold as needed.
4. Click SAVE.

11
Click CREATE.

Note: If your formula does not include all the counters you selected, the CREATE button
is dimmed. If you cannot create the indicator, check the Formula field to ensure all
counters you selected are part of the formula and spelled correctly.

END OF STEPS

4.8 How do I edit or delete an indicator?

Important! When an indicator is changed, the current data window becomes invalid and a
new data bucket is created starting from the next interval. Depending on the timing, up to two
window periods of data could be missed.

4.8.1 Steps

1
Open Data Collection and Analysis Management, Indicators.

2
Choose an indicator and click (Table row actions), Edit.

3
In the form that opens, update the parameters as needed and click UPDATE.

4
To delete an indicator:
Choose an indicator and click (Table row actions), Delete .

END OF STEPS

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 51
NSP Indicators NSP
Indicators
How do I plot an indicator chart?

4.9 How do I plot an indicator chart?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

4.9.1 Steps

Create a chart

Open the New Chart form:

• From Data Collection and Analysis Visualizations, Indicator Charts, click CHART.
• From Data Collection and Analysis Management, Indicators, choose an indicator and
click (Table row actions), Open in Data Collection and Analysis Visualizations.
− If the indicator has multiple outputs, choose resources in the form that opens and click
OPEN IN DATA COLLECTION AND ANALYSIS VISUALIZATIONS.

2
In the window that opens, configure the parameters in the top panel as needed:
• From the Time Range drop-down list, choose the amount of historical data to display.
• Click Combine charts to plot data from multiple data series on the same chart.

3
Add indicator resources.
a. Click INDICATORS.
b. If a file icon appears in the Multiple column, the indicator resources are aggregated for the
calculated KPI. Click to add it to the chart.
c. If a folder icon appears in the Multiple column, the KPI is calculated at the resource level for
the indicator.
Add resources.
1. Choose an indicator and click Select Resources .
2. Choose a resource and click Add .
Choose up to 10 indicator resources and click ADD at the bottom right of the window.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
52 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicators
How do I plot an indicator chart?

If you need to save the configuration as a chart:

1. Click SAVE AS.
2. In the window that opens, enter a name for the chart and add a description if needed.
3. Click SAVE.
The chart is added to the list.

5
Click PLOT.

END OF STEPS

4.9.2 Steps

Plot an existing chart

1
a. To plot an existing chart with no changes, choose a chart and click (Table row actions),
Chart .
b. To edit a chart and plot it, choose the chart and click (Table row actions), Edit .

2
Edit the parameters as needed and click PLOT.

END OF STEPS

Result
Visualizations displays a chart view showing the KPI data. From the chart view, you can change the
information displayed: choose a different time range, click Configure to change the list of
indicators, or click More , Combine charts to toggle between a combined chart for all selected
indicators and separate charts.
Click (Chart Details) to open the Chart Details panel on the right side of the chart view to show
details about the resources.
Hover over any point on the chart to see measured values at the indicated point. Hover over the far
right edge of the chart to show the configured thresholds.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 53
NSP Indicators NSP
Indicators
How do I chart a threshold crossing event?

4.10 How do I chart a threshold crossing event?

4.10.1 Purpose
The Data Collection and Analysis Visualizations, Threshold Crossing Events view shows the
table of threshold crossing events that have been detected and saved to the database. The table
provides information about each threshold crossing value and the indicator the threshold is
configured on.

4.10.2 Procedure
You can chart a threshold crossing event from the Data Collection and Analysis Visualizations,
Threshold Crossing Events view.
1. Open Data Collection and Analysis Visualizations, Threshold Crossing Events.
2. Select the threshold crossing event and click Chart .
The chart displays, showing the three hours before and after the selected event.
3. From the chart, click Configure to change the time range or add additional indicators if needed.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
54 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicator templates
What is an indicator template?

Indicator templates

4.11 What is an indicator template?

4.11.1 Indicator templates
An indicator template is a set of parameters that a user can optionally employ to create an indicator.
When a template is applied, the configuration information in the template is copied to the indicator
configuration. The indicator parameters provide the object filter, collection interval, and window.
That is, the KPI is defined in the template and the KPI object and collection details are defined in
the indicator. Thresholds are optional and can be configured in the template or the indicator.
For example, a template can be created for average port utilization. An indicator created from the
template specifies the port and configures the data collection.

4.12 How do I create an indicator template?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

4.12.1 Steps

1
From the Data Collection and Analysis Management, Indicator Templates view, click
TEMPLATE.

2
In the Create Indicator Template form that opens, enter a name for the template.
The name must be unique.

3
Enter a description and units as needed.

4
Enter information in the Telemetry Type field. As you type, the field filters for available
telemetry types to match your input.
Choose the telemetry type from the list of matches.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 55
NSP Indicators NSP
Indicator templates
How do I create an indicator template?

5
Click COUNTERS.

6
If you have chosen more than one counter, a formula is required; see 4.3 “How do indicator
formulas work?” (p. 46).
Enter information in the Formula field. As you type, the field identifies incorrect syntax.

Configure thresholds as needed:

1. Click THRESHOLD.
2. In the Add Threshold window that opens, enter a threshold value in the Threshold field.
3. Choose a direction from the drop-down list.
4. Click ADD.
5. Add additional thresholds as needed.

Configure threshold actions as needed:

1. Click on a threshold you created in Step 7.
2. Click ACTION and choose Alarm, Email, or Kafka from the drop-down list.
• To configure an alarm, choose the severity from the drop-down list.
• To configure an email action, enter recipient email addresses, separated with commas,
and enter boilerplate information in the Subject and Content fields.
To aggregate emails, enable the Aggregation toggle and configure the parameters. For
example, the default value of 5 in the Period and Number of Events fields sends an email
every 5 min and for every five threshold crossing events, whichever comes sooner.
• To configure a Kafka message, enter an existing topic name and enter the message
information in the Content field.
3. Add additional actions for each threshold as needed.
4. Click SAVE.

9
Click CREATE.

Note: If your formula does not include all the counters you selected, the CREATE button
is dimmed. If you cannot create the template, check the Formula field to ensure all
counters you selected are part of the formula and spelled correctly.

END OF STEPS

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
56 3HE-20004-AAAA-TQZZA Issue 1
NSP Indicators NSP
Indicator templates
How do I edit an indicator template?

4.13 How do I edit an indicator template?

4.13.1 Steps

1
From the Data Collection and Analysis Management, Indicator Templates view, choose a
template.

2
Click (Table row actions), Edit.

3
In the form that opens, update the parameters as needed and click UPDATE.

END OF STEPS

4.14 How do I delete an indicator template?

4.14.1 Steps

1
From the Data Collection and Analysis Management, Indicator Templates view, choose a
template.

2
Click (Table row actions), Delete.

END OF STEPS

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 57
NSP Indicators NSP
Indicator templates
How do I delete an indicator template?

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
58 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP

5 OAM tests
Tests

5.1 What can I test in NSP?

5.1.1 Available test types

You can create the following OAM tests:

• CFM DMM
• CFM Linktrace
• CFM LMM
• CFM Loopback
• CFM SLM
• Twamp-light
Tests are created using test templates. Before a test can be created, at least one test template
must exist for the test type.
Tests can be created at any time. No additional configuration is required on the tested objects for
testing to be performed.
RESTCONF APIs are available for MD-OAM configuration and testing; see the Network and
Service Assurance API documentation on the Network Developer Portal.

5.1.2 Data storage for OAM results

By default, OAM test data is stored in Postgres unless there is an auxiliary database enabled, in
which case result data is stored in the auxiliary database.
NFM-P SNMP test results are collected from Kafka. Kafka must be enabled in the NFM-P for NSP
to receive the results. Kafka is enabled by default for most test types except NFM-P resynched
tests. You must enable Kafka in the NFM-P for NSP to receive the results of these tests.

5.2 What is CFM?

5.2.1 Connectivity Fault Management
Ethernet Connectivity Fault Management in NSP is implemented based on the IEEE Y.1731 and
802.1ag OAM standards. The standards describe protocols for detecting, isolating, and reporting
connectivity faults in an Ethernet network. CFM is a Layer 2 OAM object infrastructure.

You can use Ethernet CFM for the following:

• path discovery
• fault detection
• fault isolation

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 59
OAM tests NSP
Tests
How do OAM tests work?

• fault notification
The following table describes terms relevant to CFM in NSP.

Term Expansion Notes

MD Maintenance domain MD is the administrative container

that defines the scope, reach and
boundary for CFM message handling.
It is typically the area of ownership
and management responsibility.
MD levels are in the range of 0 to 7,
where the larger the domain, the
larger the MD level assigned.

MA Maintenance association MA is the construct where the

different management entities such
as MEPs are contained. An MA is
created within an MD.
There is also an administrative
context where a linkage is made
between the domain and the service
using the MA bridging-identifier
configuration option.

MEG Maintenance entity group Typically, a MEG represents one

service and consists of a group of
MEPs. Only one MEG can be
associated with a service, but one
service can be associated with
multiple MEGs.
MDs and MEGs are distributed to
NEs using policy distribution.

MEP Maintenance end point MEPs are the entities at the edge of a
CFM MD and define the boundary for
the domain. MEPs are responsible for
initiating, processing, and terminating
CFM messages.
Each MEP with the same MD and MA
represent endpoints for a single
service.

5.3 How do OAM tests work?

5.3.1 CFM test types
CFM and Twamp-light session tests are supported.
PM session CFM testing is based on Metro Ethernet Forum Specification 35 - Service OAM
Performance Monitoring Implementation Agreement, which details a standardized method to test
and report network delay and loss using CFM messaging. This testing is performed in Layer 2
networks.
The PM session testing framework can also be used in the IP domain to perform TWAMP IP level
monitoring, and runs over IPv4 and IPv6 addresses. TWAMP Light tests target Layer 3 interfaces,
providing an option to monitor IP SLA performance as related to KPIs.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
60 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Tests
How do OAM tests work?

5.3.2 CFM DMM

For CFM Delay Measurement Message (DMM) tests, calculations are made to report on three
criteria: frame delay, frame delay range, and interframe delay variation. DMM test frames are issued
at regular intervals from a source MEP. Delay measurement information for the forward, backward,
and round trip paths is determined from the DMR frames received from the destination MEP.

5.3.3 CFM linktrace

CFM link trace messages that contain a target unicast MAC address are sent to multicast
destination MAC addresses. Each MIP at the same MD level replies with a link trace response.
Messages are forwarded to the next hop until they reach the destination MAC address.

5.3.4 CFM LMM

The CFM Loss Measurement Message (LMM) single-ended session test is a method of exchanging
transmit and receive counters between peer MEPs to determine exact loss on a point-to-point
Ethernet virtual circuit.
The following validations are performed:
• The LMM test suite tests can only be created or executed for MEG subgroups with exactly two
MEPs.
• The LMM test suite tests can only be executed if the source and target MEPs are not already the
source or target MEPs (respectively) of a currently running LMM test.

5.3.5 CFM loopback

CFM loopback messages are sent to a unicast destination MAC address. The MEP at the
destination responds to the loopback message with a loopback reply. A MEP or a MIP can reply to a
loopback message if the destination MAC address matches the MAC address of the MEP or MIP.
CFM loopback tests verify connectivity to a specific MEP or MIP.
You can also perform multicast loopbacks by providing a multicast address (class 1 multicast
destination) that aligns with the level that the originating MEP is configured on. Only one multicast
test can be run at a time per NE, and results from the previous test are deleted when a new test is
started. The stored values include the responding MEP MAC address, the sequence number, and a
locally-assigned Rx index (allowing you to detect out-of-order responses).

5.3.6 CFM SLM

The CFM Synthetic Loss Measurement (SLM) session test is an extension of the Y.1731 standard
that provides a method of exchanging transmit and receive counters to determine frame loss
between a MEP and the destination MAC address or remote MEP ID of another node in the
network. This test is used to verify MEP-MEP connectivity in the network and can be used to
approximate the frame loss of actual data traffic. CFM SLM session tests measure frame loss using
synthetic frames rather than data traffic. Frame loss is measured by calculating the difference
between the number of synthetic frames that are sent and received.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 61
OAM tests NSP
Tests
How do I create an OAM test?

5.3.7 Twamp-light
Twamp is a delay/loss measurement protocol that uses both the TCP connection service and the
UDP session service.
Twamp-light tests can operate on a base router or on routing instances belonging to L3VPNs. The
target, or destination entity, requires configuration of a Twamp-light reflector with a prefix associated
with the Twamp-light test source IP address and a specified UDP listening port in the range
specified for the NE type. For example, the 7750 SR Twamp-light reflector destination port range is
864, 64364-64373. A target node requires a configured reflector for the base router instance or for
each of the tested L3VPN-based virtual routing instances.
Twamp-light tests require a UDP source port in range undefined or configured in the NE range and
a UDP destination port that matches the target device reflector UDP listening port.
Twamp reflectors, Twamp servers, and streaming templates cannot be configured in NSP. They can
be discovered from the router configuration or configured using RESTCONF; see the OAM Tests
tutorial on the Network Developer Portal for RESTCONF information.
See the Data Collection and Analysis Management, Config Objects view for the list of
configured Twamp reflectors.

Twamp-light test types

You can configure a Twamp-light test to record delay, loss, or delay and loss statistics. Delay tests
provide streaming results, accounting-session, and accounting-bin type results; loss tests provide
accounting-loss-session type results. Streaming results require configuration of a streaming delay
template. The streaming template defines the frequency at which real-time streaming results are
received.
Accounting type results require configuration of an accounting policy, a file policy, and associated
Twamp-light measurement interval configuration.

5.4 How do I create an OAM test?

5.4.1 Steps

1
Open Data Collection and Analysis Management, Tests.

2
Click TEST.

3
In the Create OAM Test form that opens, select the Test type and Entity type.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
62 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Tests
How do I create an OAM test?

Click on the Service field if applicable.

1. Select an attribute in the drop-down list, then enter values for that attribute in the field. As
you type, the list is filtered for services that match your input.
2. Click as required to add additional filter criteria.
3. Choose an entity from the list and click SELECT.

5
Select an entity reference type if applicable.

Click on the Source test entity field.

1. Select an attribute in the drop-down list, then enter values for that attribute in the field. As
you type, the list is filtered for entities that match your input.
2. Click as required to add additional filter criteria.
3. Choose an entity from the list and click SELECT.

Click on the Destination test entity field.

1. Select an attribute in the drop-down list, then enter values for that attribute in the field. As
you type, the list is filtered for entities that match your input.
2. Click as required to add additional filter criteria.
3. Choose an entity from the list and click SELECT.

8
Choose a test template. The test parameters are displayed.

9
Configure the test parameters.

10
Verify the parameters in the Advanced field.

11
Click CREATE. The test appears in the list of tests.

END OF STEPS

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 63
OAM tests NSP
Tests
How do I execute an OAM test?

5.5 How do I execute an OAM test?

5.5.1 Steps

1
Open Data Collection and Analysis Management, Tests.

2
In the Filter column at the left of the view, configure a filter and click RETRIEVE. The list of
tests is populated, filtered according to your input.

Note: You can sort the list by clicking on a column header; however, the sorting function is
not available for all columns.

3
Choose a test and click to open the Test Details panel to verify that the test parameters
meet your needs. If the Deployed state parameter is Deployed, the NSP has received
confirmation from the MDM server that mediation was successful.

4
From your selected test row, click (Table row actions), Execute. The Execute dialogue
opens.

5
Configure the required parameters and click EXECUTE.
• The Sync mode parameter specifies whether or not execution requests generate notifications
in the GUI. The Sync-execute option (default) provides a notification if the execution fails.
• The Result Classifier parameter specifies the name of the result classifier used to determine
test success or failure. Result classifiers are configurable using a REST API.
Check the Perform result classification check box to apply the classifications.
• The Publish results check box publishes results to Kafka.
• The Save results to database check box makes results available to the NSP GUI. If this box
is not checked, the GUI does not display results of the test.

6
To stop a test that is running, choose the test in the list and click (Table row actions), Stop.

END OF STEPS

5.6 How do I edit an OAM test?

Note: The Edit function is not available for tests that are discovered from the NE.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
64 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Tests
How do I edit or delete an OAM test?

5.6.1 Steps

1
Open Data Collection and Analysis Management, Tests.

2
In the Filter column at the left of the view, configure a filter and click RETRIEVE. The list of
tests is populated, filtered according to your input.

Note: You can sort the list by clicking on a column header; however, the sorting function is
not available for all columns.

3
Choose a test and click (Table row actions), Edit.

4
In the form that opens, update the parameters as needed and click UPDATE.

END OF STEPS

5.7 How do I edit or delete an OAM test?

5.7.1 Steps

1
Open Data Collection and Analysis Management, Tests.

2
In the Filter column at the left of the view, configure a filter and click RETRIEVE. The list of
tests is populated, filtered according to your input.

Note: You can sort the list by clicking on a column header; however, the sorting function is
not available for all columns.

3
Choose a test and click (Table row actions), Delete.

END OF STEPS

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 65
OAM tests NSP
Tests
How do I view OAM test results?

5.8 How do I view OAM test results?

5.8.1 Purpose
Use this procedure to view results of tests. Test results are available in the NSP GUI for tests
configured from the GUI or from the RESTCONF API, as long as the original configuration specifies
that results are published to the database. Tests created from NE CLI or another network manager
are not processed within the NSP. .
Twamp-light delay results can also be provided in an accounting file, in the classes
telemetry:/base/oampm-accounting/twl-session-acc-stats and telemetry:
/base/oampm-accounting/twl-bin-acc-stats. Twamp-light loss results are available in an
accounting file in the class telemetry:
/base/oampm-accounting/twl-session-loss-acc-stats

5.8.2 Steps

1
Open Data Collection and Analysis Management, Tests.

2
In the Filter column at the left of the view, configure a filter and click RETRIEVE. The list of
tests is populated, filtered according to your input.

Note: You can sort the list by clicking on a column header; however, the sorting function is
not available for all columns.

3
To view test information, choose a test and click Test Details .
The Test Details panel shows the test attributes, and the Tested Entities panel shows the list of
entities. Information provided depends on the test type.

4
To view results of a test, select the test and click (Table row actions), View Results.
The Test executions page opens, showing the executions and their results. Use the drop-down
lists to filter by time frame and telemetry type as needed.

Note: After a test has executed, there is a brief processing delay before results are
available. For tests that have just finished running, Nokia recommends that you wait a
minimum of 5 s before viewing results.

5
Select a different time range for the test executions, if required. Choose a range from the drop
down list, or configure a customized time range.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
66 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Tests
How can I troubleshoot Twamp-light test issues?

6
If required, choose a telemetry type from the drop-down list.

7
To see additional information columns on the Test executions page, click (Table row actions),
Manage Columns. Select or de-select columns to suit your information needs.

Note: The sorting function is not available for columns on the Test executions page. By
default, executions are sorted by Time Captured.

8
For more detailed information about a specific test, choose an execution and click Test result
details .
Information provided depends on the test type.

END OF STEPS

5.9 How can I troubleshoot Twamp-light test issues?

5.9.1 Troubleshooting suggestions
The following guidelines apply to Twamp-light tests, but may also be useful for other test types.
Contact support if you need further assistance.
• The test doesn’t start.
Usually, errors on test execution occur when there is a difference in state between the NSP and
the NE or if test attributes are outside the accepted range of the NE. In this case, follow
guidance from the error or warning message returned when the test is started. Executing the test
in sync-mode “sync-execute” ensures that the most complete error and warning messages are
shown.
• The test starts and results are received, but the packet counts and delay values are all zero.
− Confirm that the destination address is reachable from the NE executing the test.
− Confirm that the Twamp-light reflector is enabled, that the test dst-udp-port parameter
matches the reflector listening port, and that the Twamp-light reflector has a matching prefix
for the test src IP address parameter.
• The test starts but no results are observed.
− Check the execution status to confirm that the test is executing.
− Confirm the test type and the expected result classes. Verify from the results class (streaming
or accounting) the expected delay until the first result should arrive. Confirm that the correct
class of result is selected, and click Refresh Results to trigger result retrieval from results
stored to the database.
− Confirm that the configuration is correct and complete: the deployment state is “deployed”,
the streaming template is defined (for intended streaming delay results), the bulk result is true
(for intended accounting results), and properties (IP addresses, UDP ports, measurement
interval) are correct.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 67
OAM tests NSP
Tests
How can I troubleshoot Twamp-light test issues?

− If streaming test results are intended, validate the configuration and status of the streaming
delay template (especially the admin state and sample window period).
− Validate telemetry subscriptions for the test classes: telemetry subscriptions are created
automatically for tests created in the NSP. The subscription name format is TestSuiteEx_
OAM-PM-test_type-statistic-type; for example, the subscription for Twamp-light
delay streaming statistics would be named TestSuiteEx_OAM-PM-TWAMP-streaming.
− Validate the Twamp-light reflector configuration:
Does the target node have a deployed, enabled reflector?
Does the UDP port match those of configured tests?
Is the reflector on the correct routing instance (router- or service-based)? Twamp-light
reflector prefixes can be viewed from the RESTCONF API.
− Validate the bin group information for accounting type results: confirm that the bin group
configured in the test is configured on the node and that admin state is enabled. Details of bin
groups may be configured or retrieved using RESTCONF API or discovered from node
configuration.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
68 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Test Suites
What is an OAM test suite?

Test Suites

5.10 What is an OAM test suite?

5.10.1 OAM test suite
A test suite is a collection of tests that are grouped together to allow for multiple tests to be
executed together or run in sequence. The suite includes both the tests and, where applicable,
instructions for running tests sequentially or in parallel. Test suites can provide improved automation
for OAM testing.
NSP provides a read-only list of test suites created in the MD-OAM RESTCONF API and in NSP.
See the OAM Tests tutorial on the Network Developer Portal for information about using the API.

Note: On-demand test suites can be created and executed for LMM and SLM tests, but
results may not be available to be shown.

5.11 How do I create an OAM test suite?

5.11.1 Steps

1
Open Data Collection and Analysis Management, Test Suites.

2
Click SUITE.

3
In the Generate OAM Tests form that opens, choose a Test type.
The list of templates in the Template field is updated based on your selection.

4
Choose a test template if needed.
If a template is not selected, an appropriate system template is automatically selected based on
the value of the execute type field. If a template is selected, the value of the execute type field
is imported from the template and is read-only in the form.

5
Add one or more entities:
1. Choose an entity type from the Entity type drop down.
2. Click SELECT to open a selection form.
3. Choose one or more entity objects from the list to add them to the Bin. Use the page
selectors to navigate the list.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 69
OAM tests NSP
Test Suites
How do I stop or start an OAM test suite?

4. Verify the list of entity objects in the Bin and click SELECT.
5. To change the list of selected entities, repeat the previous steps to re-create the list.

Click on the Service field if applicable.

1. Select an attribute in the drop-down list, then enter values for that attribute in the field. As
you type, the list is filtered for entities that match your input.
2. Click as required to add additional filter criteria.
3. Choose entities from the list and click SELECT.

7
Configure the test parameters as needed.

8
Generate the test suite.
a. To automatically execute the test suite after generation, enable Execute and click
GENERATE & EXECUTE.
b. To create the test suite without automatically executing, disable Execute and click
GENERATE.

END OF STEPS

5.12 How do I stop or start an OAM test suite?

5.12.1 Steps

1
Open Data Collection and Analysis Management, Test Suites.

2
Choose a test suite and click (Table row actions), Execute.

3
In the form that opens, update the parameters if needed and click EXECUTE. The execution
status is updated to Running.

Tip: Disable the Publish results parameter if you don’t need results published to kafka.
This may reduce processing impact.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
70 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Test Suites
How do I edit or delete an OAM test suite?

4
To stop a test suite that is running, choose the test suite in the list and click (Table row
actions), Stop.

END OF STEPS

5.13 How do I edit or delete an OAM test suite?

5.13.1 Supported functions
Test suites can only be modified using the MD-OAM RESTCONF API.
To delete a test suite, choose a test suite and click (Table row actions), Delete.
Deleting a test suite deletes all associated tests.

5.14 How do I view OAM test suite results?

Note: After a test has executed, there is a brief processing delay before results are available.
For tests that have just finished running, Nokia recommends that you wait a minimum of 5 s
before viewing results.

5.14.1 Steps

1
Open Data Collection and Analysis Management, Test Suites.

2
Choose a test suite and click (Table row actions), View Details.
The View Test Suite Details page opens, showing the following:

Tab Notes

AGGREGATED RESULTS Each row of the aggregated results table corresponds to an execution of the
test suite. Whenever the test suite is successfully started, a new aggregated
results row is added.
To view the individual results for a specific test suite execution, select the
aggregated results row corresponding to the execution you are interested in
and click View individual results .

LIFECYCLE RESULTS The LIFECYCLE RESULTS table shows events from the execution of the
test suite, such as stop and start timestamps and error events.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 71
OAM tests NSP
Test Suites
How do I view OAM test suite results?

Tab Notes

INDIVIDUAL RESULTS The page displays the results of each test executed.
By default, the results from the most recent test suite execution are shown,
that is, the execution ID from the first row of the aggregated results table is
chosen automatically. You can view results for other test suite executions by
specifying another execution ID in the Test suite execution ID field or by
returning to the AGGREGATED RESULTS tab and clicking View individual
results .
For more detailed information about a specific test, choose an execution
and click View Results .
Note: If a test suite was created from the NSP, the tests will all be the same
type. If the test suite was created using RESTCONF, multiple test types
could be included. To view results from a different type than is currently
displayed, choose the telemetry type from the drop down list.
See the TESTS tab for a list of tests in the suite.

GENERATION LOG The page displays log information from the generation of the suite and
tests.

TESTS The page lists the test identifiers included in the suite.
If the test suite is an on-demand suite, the TESTS tab shows the included
tests grouped by stage.
Stages are executed sequentially, but tests within each stage will be
executed either sequentially or in parallel depending on how the stage is
configured.
For more detailed information about a specific test, double click on an
execution or choose an execution and click View Results .

END OF STEPS

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
72 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Test Templates
What is an OAM test template?

Test Templates

5.15 What is an OAM test template?

5.15.1 OAM test template
An OAM test template is a set of parameters that a user can employ to create or customize a test
for a particular use case. You can create a template for each test type, or create separate templates
for different use cases. The test template becomes the form used to create and run the test in the
future.
On-demand templates are for tests that run a single execution; proactive templates are for tests
that execute repeatedly.

5.16 How do test templates work?

5.16.1 Template parameters
A test template includes all the parameters for a test. The template creator can set the parameters
or leave them blank and can choose whether the parameter is visible or editable when the template
is used.

When a test is created from the template, the parameters are applied as follows.
• If the template creator sets the parameter value in the template and does not set the parameter
instance as editable, the test runs with the value set in the template.
• If the template creator sets the parameter instance as editable, the test runs with the value set
by the user who creates the test. The template creator can also set the parameter value,
creating a template default.
• If the template creator does not set the parameter value and does not set the parameter instance
as editable, the test runs with the default value in the YANG model, if applicable.
Test templates can use variable substitution to autopopulate some values, based on entity mapping
in the YANG model. The definition of a variable has the following syntax:
${variable-name}
For example, "service:${service-name}" is resolved from the current test object after any
source/destination entities are resolved.
For more information about variable substitution, see the OAM Tests tutorial on the Network
Developer Portal.

5.17 What is a system template?

5.17.1 System template
System templates are available to NSP for test creation.
An operator can create tests using any template. However, when the NSP creates a test, it must
use a system template. This requirement includes test suites created by an operator.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 73
OAM tests NSP
Test Templates
How do I create an OAM test template?

Default system templates are provided with installation of the NSP. You can modify these templates
and add additional ones.

5.18 How do I create an OAM test template?

CAUTION

Service Disruption
The name of an object, including subscriptions, baselines, indicators, templates, and chart profiles,
cannot contain a semicolon (;) or backslash (\).
The use of these characters in an object identifier will result in corrupted data that must be deleted
by Nokia support.

5.18.1 Steps

1
Open Data Collection and Analysis Management, Test Templates.

2
Click TEMPLATE.

3
In the Create Test Template form that opens, configure the template settings in the panel on the
left.
By default, the settings are not visible or editable at test creation. Enable visibility or editing for
each setting as needed. When you enable editing, visibility is automatically enabled.
• Configure the Execute type parameter to configure the template as On-demand or
Proactive.
• Select System Template to configure the template as a system template.

4
View the test creation form layout in the panel on the right side of the page. Drag the fields to
change the order if needed.

5
Click CREATE.

END OF STEPS

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
74 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Test Templates
How do I edit an OAM test template?

5.19 How do I edit an OAM test template?

5.19.1 Steps

1
Open Data Collection and Analysis Management, Test Templates.

2
Choose a template and click (Table row actions), Edit.
Use the All Templates drop-down list if required to filter the list to show only on-demand or
proactive templates.

3
In the form that opens, update the parameters as needed and click UPDATE.

END OF STEPS

5.20 How do I delete an OAM test template?

5.20.1 Steps

1
Open Data Collection and Analysis Management, Test Templates.

2
Choose a template and click (Table row actions), Delete.

3
Click DELETE to confirm the deletion.

END OF STEPS

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 75
OAM tests NSP
Config Objects
What is a config object?

Config Objects

5.21 What is a config object?

5.21.1 Definition
A config object represents an OAM configuration object that is used for testing, other than the test
object itself.
NSP provides a list of configuration objects. Click on the object type drop-down list to switch to the
list for a different object type.

5.22 What config objects are available in NSP?

5.22.1 Objects presented
The following table describes the available configuration objects.

Configuration object type Description Notes

Bin Group A bin group is a template of Bin groups define a service level
Performance Measurement histogram agreement quality quantitatively.
measurement bin definitions. Bin Service offerings with differentiated
groups contain measurement bins, service level agreements may be
which count instances of frame delay measured using different bin groups.
(FD), frame delay range (FDR), or
interframe delay variation (IFDV)
metrics within a defined range of
lower to upper threshold values. Bin
group definitions may also include
definitions for delay-event thresholds
and calculation of average FD, FDR,
and IFDV values.

CFM Domain CFM Maintenance Domain (level 0 to Each MD can include multiple MAs.
7)

CFM Association CFM maintenance associations. Auto-configuration of MAs is

supported when creating CFM based
tests

CFM MEP CFM maintenance entity point. A MEP Auto-configuration of MEPs is

is an end point in an MA, on which supported when creating CFM based
CFM tests can be performed. tests. Service MEPs, such as SAPs,
Each MEP with the same MD and MA and facility MEPs, such as LAGs, are
represents endpoints for a single supported.
service.

Streaming Delay Template A template that defines real-time NSP supports delay streaming using
measurement of FD and IFDV from gNMI, for 7750 SR NEs.
delay-based Performance
Management tests. Average values
are calculated over 10-to-60 second
intervals and stream in real-time.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
76 3HE-20004-AAAA-TQZZA Issue 1
OAM tests NSP
Config Objects
How do I create a config object?

Configuration object type Description Notes

Twamp Server TWAMP is a delay/loss measurement —

protocol that uses both the TCP
connection service and the UDP
session service. A TWAMP server
may be configured to accept TCP
control connections from a specified
range of IP networks and TCP
ports; also, it will accept requests for
clients to initiate UDP test sessions
for specific IP address or UDP port
pairs on the service router.

Twamp-light Reflector (Router) A Twamp-light reflector controls the Auto-create/update of TWAMP-light

set of IP network and UDP ports reflectors is supported when starting
where the service router replies to TWL based tests.
TWAMP-light test messages. TWAMP
Twamp-light Reflector (Service) light reflectors may be configured for
both base and service routing
instances.

5.23 How do I create a config object?

5.23.1 Creation support
Config objects are created using RESTCONF, using classic IP mediation, or, for CFM objects in
particular, can be auto-generated when CFM tests are created.

5.24 What can I do with config objects in NSP?

5.24.1 Supported operations
You can sort or filter the lists or click (Delete) to delete a config object.
Any other actions must be done using RESTCONF or classic IP mediation, depending on how the
object was created.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 77
OAM tests NSP
Config Objects
What can I do with config objects in NSP?

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
78 3HE-20004-AAAA-TQZZA Issue 1
Use cases NSP

Part II: Use cases

Overview
Purpose
Describes use cases for Data Collection and Analysis Management and Data Collection and
Analysis Visualizations.

Contents

Chapter 6, Telemetry management use cases 81

Chapter 7, Chart use cases 107

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 79
Use cases NSP

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
80 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP

6 Telemetry management use cases

6.1 Installing and locating specific telemetry types

6.1.1 Purpose
This use case shows how to use NSP to set up and locate the telemetry types needed for a sample
use case.
In this scenario, we want to start monitoring the aggregate dropped packet count for egress traffic
on VPRN SAPs on SR OS devices. We need to install the required files and confirm the telemetry
types we’ll need to create subscriptions for.

6.1.2 Steps

1
Obtain the required vendor agnostic (va) CR bundles from the Nokia NSP software download
site:
1. Choose the release, Adaptors, and the adaptor type.
For this example, we’ll choose 23.11, Adaptors, Nokia_SROS.
2. The list of available downloads is displayed. Choose the zip file with va and cr in the
filename.
For this example, we’ll choose nsp-telemetry-cr-va-sros-1.0.0-rel.10.zip.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 81
Telemetry management use cases NSP
Installing and locating specific telemetry types

2
Install the artifact bundle from the Artifacts, Artifact Bundles view; see “How do I install an
artifact bundle?” in the NSP Network Automation Guide.
The telemetry types in the va bundle are now available in the Telemetry Statistic Search Tool.

3
Check the Telemetry Statistic Search Tool:
1. Open the NSP Help Center. From the Help Center home screen, navigate to REFERENCE,
Statistic Search, Telemetry Statistic Search.
2. Enter “aggregate-dropped” in the Counter Name field. The search tool filters for telemetry
types with aggregate-dropped in the counter name.
Enter additional filters as needed to narrow the search.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
82 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Installing and locating specific telemetry types

3. Click on each row to see the Info panel. Verify whether the selected telemetry type will
monitor the counters you need.
4. If the telemetry type is found, you are ready to set up your subscriptions.
For our example, the telemetry type we need is not installed yet. Next, we’ll check the telemetry
yang files. After the telemetry yang files have been installed, we can also install cut-through
telemetry files.

4
Perform the sequence in Step 1 to obtain the telemetry yang files for the NE family.
For this example, we’ll download nsp-telemetry-yang-sros-23_11.zip.

5
Extract the files from the zip and look for the telemetry types:
1. View the list of telemetry files. The filename sros-service-vprn-telemetry.yang
suggests it could contain the telemetry types we need.
2. Open the file and search for “aggregate”. The desired counter is present in a leaf element.
The telemetry type appears in the list:

3. Install the yang file using yang-file.bash; see “How do I manage MDM model
definitions?” in the NSP System Administrator Guide.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 83
Telemetry management use cases NSP
Setting up statistics and aggregation for Port Throughput on the 7750 SR

6
Now that the yang file we need has been installed, we can install cut-through CRs.
Obtain the SR OS cut-through (ct) CR bundles from the Nokia Nokia NSP software download
site and install them from the Artifacts, Artifact Bundles view; see “How do I install an artifact
bundle?” in the NSP Network Automation Guide.

Note: Cut-through telemetry types are for gNMI-capable devices only.

7
Check the Telemetry Statistic Search Tool :
1. Open the NSP Help Center. From the Help Center home screen, navigate to REFERENCE,
Statistic Search, Telemetry Statistic Search.
2. Enter “aggregate-dropped-packets” in the Counter Name field to verify that the artifacts
have loaded successfully.
3. Click on each row to see the Info panel and obtain further details about the counter, such
as device types and releases supported.

END OF STEPS

We’re done
The counters we need are available in the NSP, and we have the information we need to configure
a subscription.

6.2 Setting up statistics and aggregation for Port Throughput on the

7750 SR
6.2.1 Purpose
This use case shows how to use NSP to set up the data collection and aggregation required to run
a Port Throughput report in Analytics for 7750 SR NEs managed using MDM.
The following prerequisites must be completed.
• Telemetry types for port throughput have been installed.
• At least one 7750 SR NE has been discovered in the network and is reachable.
• Aggregation rules have been deployed.

6.2.2 Steps

1
From Data Collection and Analysis Management, Subscriptions, we’ll create a subscription.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
84 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Setting up statistics and aggregation for Port Throughput on the 7750 SR

We need interface utilization statistics for 7750 SR NEs. An object filter that contains “7750”
ensures that we receive data whether the NE type says “7750 SR” or “7750 SR-12”.

2
Let’s look at the aggregation rule for interface data. From the Aggregation view, choose the
aggregation rule and click Edit Aggregation Rule to see the details.
The Retention Period fields show how long aggregated data is stored in the auxiliary
database. The default retention period for daily aggregation is 90 days. That means that daily
granularity is available in Analytics for up to 90 days of data.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 85
Telemetry management use cases NSP
Setting up statistics and aggregation for Port Throughput on the 7750 SR

3
Changing the retention period to 120 days makes daily granularity available for a longer time.
Change the retention time and click UPDATE.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
86 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Setting up baselines

END OF STEPS

We’re done
We’ve set up a subscription for interface utilization data, and aggregation is deployed. When data
has been successfully collected and aggregated, we’ll be able to run a Port Throughput Summary
(NSP) report in the Analytics application.

6.3 Setting up baselines

6.3.1 Purpose
This use case shows how to use NSP to create baselines to monitor transmitted and received
octets on a network port. These baselines can be used to detect anomalies and to create baseline
and anomaly charts.
The following prerequisites must be completed.
• The NE we need to monitor has been discovered in the network and is reachable.
• If the NE we need to monitor is managed by NFM-P, statistics collection has been configured
and started in the NFM-P.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 87
Telemetry management use cases NSP
Setting up baselines

6.3.2 Steps

1
From Data Collection and Analysis Management, Baselines, we’ll create baselines.

Creating an object filter to specify the NE and port makes finding the resources easier.

2
A form opens, showing the available counters. We’ll choose transmitted and received octets.
Select the counters and click ADD.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
88 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Setting up baselines

3
We can configure the counter type or conversion to bitrate if needed. We’ll use the defaults for
these baselines.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 89
Telemetry management use cases NSP
Setting up baselines

4
NSP checks for resources corresponding to the filters and counters specified. When the
resources we need appear in the resources list, click STOP VERIFICATION. The verification
does not stop on its own.

5
Select the resources in the resources list.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
90 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Setting up baselines

6
The final step is configuring anomaly detection. Then we can click CREATE.

END OF STEPS

We’re done
NSP creates a baseline for each resource. When complete, they appear in the list in Data
Collection and Analysis Management, Baselines.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 91
Telemetry management use cases NSP
Creating a simple indicator

6.4 Creating a simple indicator

6.4.1 Purpose
This use case shows how to use NSP to create an indicator with a single counter and no formula.
This indicator outputs the input utilization of each port on NE 4.4.4.4.
The following prerequisites must be completed:
• The NE we need to monitor has been discovered in the network and is reachable.
• If the NE we need to monitor is managed by NFM-P, statistics collection has been configured
and started in the NFM-P.

6.4.2 Steps

1
From Data Collection and Analysis Management, Indicators, we’ll create an indicator.

Enter a name for the indicator, and configure the collection interval and window duration.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
92 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a simple indicator

2
Configure the telemetry type.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 93
Telemetry management use cases NSP
Creating a simple indicator

3
A form opens showing the available counters. We’ll choose input utilization.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
94 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a simple indicator

4
Configure an object filter to collect statistics from a specific port, and click VERIFY
RESOURCES to make sure the filter is correct.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 95
Telemetry management use cases NSP
Creating a simple indicator

5
When the resources we need appear in the resources list, click STOP VERIFICATION. The
verification does not stop on its own.

6
Create thresholds as needed. We’ll create thresholds for utilization increasing past 60% and for
decreasing below 5%.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
96 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a simple indicator

7
Configure threshold actions. We’ll configure a Threshold Crossing Alarm alarm to be generated
for each threshold. The alarm for the increasing threshold has Major severity, and the alarm for
the decreasing threshold has Minor severity.

8
When both thresholds are configured, we can click CREATE to create the indicator.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 97
Telemetry management use cases NSP
Creating a complex indicator using a template

END OF STEPS

We’re done
The indicator appears in the list in Data Collection and Analysis Management, Indicators.

6.5 Creating a complex indicator using a template

6.5.1 Purpose
This use case shows how to use NSP to create an indicator template with a formula and apply the
template to an indicator.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
98 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a complex indicator using a template

6.5.2 Steps

1
From Data Collection and Analysis Management, Indicator Templates, we’ll create a
template.

2
A form opens showing the available counters. We’ll choose input utilization.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 99
Telemetry management use cases NSP
Creating a complex indicator using a template

3
Enter a formula for the indicator to use to calculate KPI values. Our formula calculates average
input utilization.
Click CREATE to create the template.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
100 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a complex indicator using a template

4
Now we can create the indicator. From the Indicators view, click INDICATOR. Enter a name
for the indicator and configure the collection settings.
Click APPLY TEMPLATE.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 101
Telemetry management use cases NSP
Creating a complex indicator using a template

5
In the window that opens, choose the template and click APPLY.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
102 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a complex indicator using a template

The template has provided most of the parameters for the indicator, including defining how we
want to calculate ring utilization. Next we can apply an object filter to define the resources to
monitor.

6
Click VERIFY RESOURCES to show the resources found by the filter and ensure that they are
returning values.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 103
Telemetry management use cases NSP
Creating a complex indicator using a template

7
When the resources of interest appear in the resources list, click STOP VERIFICATION. The
verification does not stop on its own.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
104 3HE-20004-AAAA-TQZZA Issue 1
Telemetry management use cases NSP
Creating a complex indicator using a template

8
Add thresholds if needed and click CREATE. See 6.4 “Creating a simple indicator” (p. 92) for
steps to create a threshold.

END OF STEPS

We’re done
The indicator appears in the list in Data Collection and Analysis Management, Indicators.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 105
Telemetry management use cases NSP
Creating a complex indicator using a template

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
106 3HE-20004-AAAA-TQZZA Issue 1
Chart use cases NSP

7 Chart use cases

7.1 Creating baseline and anomaly charts

7.1.1 Purpose
This use case shows how to use NSP to chart baselines and anomalies.

The following prerequisites must be completed:

• The required baselines have been created.
• The baselines have been in active learning status for enough time to detect anomalies.
Depending on the anomaly detector, this can be one or two seasons.

7.1.2 Steps

1
From Data Collection and Analysis Visualizations, Baseline Charts, we’ll create a chart.

2
Configure the time range parameter. To display multiple baselines on the same chart, enable
the Combine Charts check box.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 107
Chart use cases NSP
Creating baseline and anomaly charts

3
In the Add Baselines form, choose the baselines to chart and click ADD.

4
If you want to save the configuration for future use, click SAVE AS and enter a name for the
chart.
Click PLOT to plot the chart.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
108 3HE-20004-AAAA-TQZZA Issue 1
Chart use cases NSP
Creating baseline and anomaly charts

END OF STEPS

We’re done
Visualizations displays a chart for each baseline.
The dotted line shows the expected values. The shading shows the detector threshold range, that
is, the range of values that is not considered anomalous.
The solid line shows the actual values. Anomalies are indicated with red dots.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 109
Chart use cases NSP
Creating baseline and anomaly charts

Click Chart Details at the top right to display the Chart Details panel.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
110 3HE-20004-AAAA-TQZZA Issue 1
Chart use cases NSP
Creating an indicator chart

7.2 Creating an indicator chart

7.2.1 Purpose
This use case shows how to use NSP to chart an indicator.

The following prerequisites have been completed:

• The indicator we need has been created.
• The indicator has been operating for at least one window duration.

7.2.2 Steps

1
From Data Collection and Analysis Management, Indicator Charts, we’ll create a chart.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 111
Chart use cases NSP
Creating an indicator chart

2
Configure the time range parameter. To display multiple indicators on the same chart, enable
the Combine Charts check box.
Click INDICATORS.

3
In the Add Indicators form, choose the indicators to chart and click Add. The indicator we want
to add has a file icon in the Multiple column, so the resources are aggregated and there is no
need to select resources. We can just choose the Ring Ingress Util indicator and click Add.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
112 3HE-20004-AAAA-TQZZA Issue 1
Chart use cases NSP
Creating an indicator chart

4
If you want to save the configuration for future use, click SAVE AS and enter a name for the
chart.
Click PLOT to plot the chart.

© 2024 Nokia.
Release 24.4 Use subject to Terms available at: www.nokia.com/terms
April 2024
Issue 1 3HE-20004-AAAA-TQZZA 113
Chart use cases NSP
Creating an indicator chart

END OF STEPS

We’re done
Visualizations displays a chart for the indicator.
The dotted lines shows the thresholds. Threshold crossing events are indicated with dots.

© 2024 Nokia.
Use subject to Terms available at: www.nokia.com/terms Release 24.4
April 2024
114 3HE-20004-AAAA-TQZZA Issue 1