Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Manage the Orion Web Console > Using Node Filters

Using Node Filters

Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Jan 25, 2017

Views: 37 Votes: 0 Revisions: 2

When you are managing or monitoring large numbers of network devices, node list resources can easily 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. For more information about defining custom properties, see Create custom properties

Apply a node filter

  1. Click Edit in any node list resource.
  2. Provide an appropriate SQL query in the Filter Nodes (SQL) field, and then click Submit.

Example filters with associated SQL queries

By default, node list resources are designed to sort nodes alphabetically by node caption. This configuration can not 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:

    Status<>1

  • 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'

Valid status levels

0 Unknown (current up/down status of the node is unknown)
1 Up (node is responding to PINGs)
2 Down (node is not responding)
3 Warning (node may be responding, but the connection from the server to the Node is dropping packets)
 
Last modified
20:56, 24 Jan 2017

Tags

Classifications

Public