Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This article provides steps on how to use node filters.
When managing or monitoring large numbers of network devices, node list resources can become very large and difficult to navigate. Filters are optional SQL queries that are used to limit node list displays for easier resource navigation. SQL queries can be made on any predefined or custom properties.
To apply a node filter:
The following are a few example filters with associated SQL queries.
Note: By default, node list resources are designed to sort nodes alphabetically by node caption. This configuration cannot be overwritten using a SQL filter, so Order By clauses included in SQL filters are redundant and will result in Custom
SQL filter formatting errors.
Filter the results to only show nodes that are not Up:
The following are valid status levels:
0 = Unknown(current up/down status of the node is unknown)
1 = Up(The node is responding to PINGs)
2 = Down(The node is not responding)
3 = Warning (The node may be responding, but the connection from the server to the Node is dropping packets)
Only show Cisco devices: Vendor = 'Cisco'
Only show devices in Atlanta. (Using a custom property named City):
City = 'Atlanta'
Only show devices beginning with "AX3-": Caption Like 'AX3-*'
Only show Nortel devices that are Down:
Vendor Like 'Nortel*' AND Status=2
Only show devices ending in '-TX':
Vendor Like '*-TX'