How do I enable NSP telemetry and reporting for NFM-P-managed classic devices?
Purpose
If classic devices are already discovered in the NFM-P, for example, in a brownfield scenario or after an upgrade from a previous release, the classic discovery rules, policies, and managed devices are automatically synced from NFM-P to NSP and are visible in the Device Discovery or Device Management views. Devices in an unmanaged state are not automatically synced.
To use NSP telemetry and reporting with a synced NE, the classic discovery rule used to discover the device must be associated with a unified discovery rule with gRPC mediation configured. The NSP uses the gRPC mediation policy configured in the unified discovery rule to collect statistics. Performing this procedure enables gRPC mediation for all classic devices discovered by a classic discovery rule.
Note: Only one classic discovery rule can be associated with a selected unified discovery rule. See How do I discover devices?to create additional unified discovery rules if needed.
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. To avoid duplication, disable equivalent MIB based statistics in NFM-P if gRPC telemetry is used.
Steps
1 |
Obtain required information about the NE:
|
Associate the classic discovery rule to the unified discovery rule | |
2 |
Open Device Discovery, Unified Discovery Rules. |
3 |
Select a discovery rule and click |
4 |
In the Edit Discovery Rule form, click in the Classic Discovery Rule field. In the form that opens, select a discovery rule and click SELECT. |
5 |
Verify that the IP addresses of the classic devices are in one of the included IP ranges. If needed, click |
6 |
Click UPDATE. The discovery rule is updated. The next time the discovery rule is run, the gRPC mediation information provided by the discovery rule is applied. Note: Only one classic discovery rule can be associated with a selected unified discovery rule. See How do I discover devices?to create additional unified discovery rules if needed. |
Restore collection and reporting | |
7 |
If you have upgraded your system from 23.11 or earlier, restore classic telemetry collection. See the Restore classic telemetry collection step in “To upgrade an NSP cluster” in the NSP Installation and Upgrade Guide. |
8 |
Verify the age-out policies for the telemetry types as needed. After an upgrade from 23.11 or earlier, the NE IDs for dual stack NEs have been changed, causing existing telemetry records to become stale. The stale records will be deleted according to the age-out policy for each telemetry type. See “How do I edit an age-out policy?” in the NSP Data Collection and Analysis Guide to update the policies as needed. |
9 |
If you created baselines in NSP using NFM-P statistics collection, and will be using NSP to collect statistics in future, create the baselines again. See “How do I create baselines?” in the NSP Data Collection and Analysis Guide. |
10 |
Update 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']", 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']". |
11 |
If you have saved charts using baselines or object filters you recreated in steps Step 9 and Step 10, plot and save the charts again. See the procedures to plot charts in the NSP Data Collection and Analysis Guide. End of steps |
) to find the associated classic discovery rule.
(Table row actions), Edit.
ADD to specify an IP address and mask bits.