Wavence example object filters for the NSP
Insights Administrator
You can use the NSP to manage YANG-based telemetry from Wavence nodes. When you use the NSP to view indicators, you must use object filters to focus the scope of the indicators to the nodes you need to monitor. This section contains a few example object filters to assist in using the NSP to monitor Wavence nodes.
Finding NE, radio, and lag objects
You can filter for network elements by ID, type, or other attributes. The following examples show how to find NEs, LAGs, and radio ports - either as a broad category, or specific elements:
-
/nsp-equipment:network/network-element[ne-id='203.0.113.169']
-
/nsp-equipment:network/network-element[contains('ip-address', '203.0.113.1')]/lag
-
/nsp-equipment:network/network-element/hardware-component/port[description='Radio']
-
/network-device-mgr:network-devices/network-device[name='203.0.113.169']/root/nokia-nsp-source:fdn[id='fdn:realm:sam:network:203.0.113.169:shelf-1:cardSlot-1:card:port-5']
-
/network-device-mgr:network-devices/network-device[name='203.0.113.169']/root/nokia-nsp-source:fdn[id='fdn:realm:sam:network:203.0.113.169:lag:interface-1']
You can join together statements in an object filter using the | logical operator, and the filter will return the results of all the joined statements. For example, the following filter returns both NEs that match the specified NE-IDs:
/nsp-equipment:network/network-element[ne-id='203.0.113.169'] | /nsp-equipment:network/network-element[ne-id='203.0.113.170']
The same format can be used to combine any of the examples above. For more information about indicators and building object filters, see the NSP Data Collection and Analysis Guide.