How do I stitch a classic device to a unified discovery rule?
Purpose
If classic devices are already discovered in the NFM-P (brownfield scenario), they are synchronized to the NSP and appear in the Device Management, Managed Network Elements view. This synchronization does not provide gRPC mediation, which is required for telemetry and reporting.
To enable telemetry and reporting in NSP, the classic devices must be stitched to a unified discovery rule with gRPC mediation.
This is a one-time manual procedure.
Note: 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 TCAs. Disable equivalent MIB based statistics in NFM-P if gRPC telemetry is used.
Telemetry
If you are using NSP telemetry with classic devices, updates are required after you perform this procedure:
-
Baselines created using NFM-P statistics collection must be recreated; see “How do I create baselines?” in the NSP Data Collection and Analysis Guide.
-
For telemetry and indicators, any object filter elements that include nokia-nsp-source:fdn, for example, "networkDeviceId":"/network-device-mgr:network-devices/network-device[name='1.1.1.1']/root/nokia-nsp-source:fdn[id='fdn:realm:sam:network:1.1.1.1:shelf-1:cardSlot-12:card:port-4']", must be updated to device yang format, for example, "networkDeviceId":"/network-device-mgr:network-devices/network-device[name='1.1.1.1']/root/nokia-state:state/port[port-id='B/4']"
-
Saved baseline, indicator, and telemetry charts must be updated to include object filters in device yang format.