NSP OAM reports overview

General information

NSP OAM reports show aggregated latency and loss information based on results of OAM testing. Information in the report inputs is optimized to reflect the configuration of the test in the NFM-P GUI, for example, only configured forwarding classes appear in the inputs. NSP OAM reports include OAM data for NEs managed by the NFM-P and MDM (model-driven Nokia NEs).

Forwarding classes are highlighted when latency or packet loss exceeds thresholds:

• Orange highlighting indicates that the maximum RTD is double or more the value of the average RTD

• Yellow highlighting indicates that the loss is greater than 0% but less than 5%.

• Red highlighting indicates that the loss is greater than 5%.

Both the NE name and its IP address display in the report.

Note: Gaps may appear in line graphs: These indicate a time during which no data was available.

There is a duplication of data in input controls when the NEs are dual managed.

Drill-down reports

NSP OAM reports can be run from the main NSP OAM reports folder. Some reports can also be run as drill-downs by clicking on a data point in another report. See the report characteristics table for each NSP OAM report for the drill-downs available.

Supported standards

The MEF35 test type is supported for the following reports:

• OAM-PM Bins and Delay (NSP)

• OAM-PM Latency (NSP)

• OAM-PM Loss (NSP)

• OAM-PM Multiple Session View (NSP)

• OAM-PM Network Site Summary (NSP)

• OAM-PM Network Summary (NSP)

• OAM-PM Service Summary (NSP)

• OAM-PM Service Site Summary (NSP)

• OAM-PM Service Site (NSP)

Prerequisites

Note: See Supported NEs for information about supported NEs.

The following must be configured for NSP OAM reports to be created:

• For classic (NFM-P)-managed NEs statistics collection, use the traditional NFM-P SNMP MIB statistics or accounting statistics

• For model driven-managed NEs, MDM is required to collect gRPC statistics. When MDM is used to collect statistics, persistence must be enabled in the subscription.

• An MDM adapter is required for MDM-mediated NEs; contact your technical support representative for more information. You must also enable statistics; see the Data Collection and Analysis Guide.

• OAM testing must be configured in the NFM-P.

  See the following in the NSP NFM-P Classic Management User Guide for information about the tests and policies that provide data for OAM reports:

  • PM bin policies

  • Configuring a PM session OAM diagnostic test from the STM

  • Configuring a CFM DMM session OAM diagnostic test from the STM

  • Configuring a TWAMP-Light session OAM diagnostic test from the STM

• The OAM test results must be stored in the auxiliary database. To enable auxiliary database storage of OAM test results, you must enable the oam-test-results parameter in the samauxdb section of each NFM-P main server configuration. See the NSP Installation and Upgrade Guide for information about using the samconfig utility to modify the NFM-P configuration.

• OAM statistics must be collected using an accounting policy. ETH-CFM Session and TWAMP-Light Session tests require a Complete-PM policy.

• To view the reports for granularities other than raw data, the OAM aggregation rules must be enabled; see How do I configure analytics aggregation?.

• PM bin group policies must be created.

• The following feature packs must be added when you create an NSP instance:

  • platform

  • platformMdm

  • serviceAssurance

  • serviceActivationAndConfiguration-intentBasedServiceFulfillment

  • intentBasedNetworkingFramework