Telemetry management using NSP

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, described in the NFM-P Statistics Management Guide.

The DCA functions of NSP are described in detail in the NSP Data Collection and Analysis Guide.

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 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.

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.

Use subject to agreed restrictions on disclosure and use.