How do subscriptions work?

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. ¹ 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 CN telemetry, on model driven NEs	When the subscription is created, the NSP initiates collection of the telemetry data from the NE at the specified interval.

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

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 CN telemetry, on model driven NEs

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

Notes:

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.