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.
Management type |
Management type definition |
Statistics configuration |
---|---|---|
Classic |
Device is discovered and managed exclusively by NFM-P |
Statistics collection and database storage must be previously configured in NFM-P before creating a subscription. 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. |
MDM |
Device is discovered and managed exclusively by NSP |
When the subscription is created, the NSP initiates collection of the Telemetry data from the NE at the specified interval. |
Dual managed |
Device is discovered and managed in both NFM-P and NSP, that is, both classic and MDM management Dual management enables gRPC telemetry on classic devices. All other management is through NFM-P. |
NSP uses MDM for dual managed NEs. When the subscription is created, CN telemetry initiates collection of the telemetry data from the NE at the specified interval. 1 |
Notes:
If statistics collection is set up in both NFM-P and Insights Administrator, the telemetry framework may receive the same information twice. The duplication could result in incorrect reports or duplicated indicator TCAs. For dual managed NEs, 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.