Administer > Create Groups of Nodes or Interfaces > Create Node Groups > Create Node Groups Using Filters or Hostname Lists > Specify Node Group Additional Filters

Specify Node Group Additional Filters

[Note to writers: do not show examples with * or ? wildcards at beginning of search string for this feature. It is allowed but performance is bad.]

Use the Additional Filters Editor to create expressions that refine the requirements for membership in a Node Group. Make sure to design any complex Additional Filters offline as a Boolean expression first. This method can help to minimize errors when entering your expressions using the Additional Filters Editor.

If any Additional Filters are created, NNMi combines any Device Filters and Additional Filters using the AND Boolean operator as follows: 

  • NNMi first evaluates any Device Filters. Nodes must match at least one Device Filter specification to belong to this Node Group.
  • NNMi then evaluates the Additional Filters expression. Nodes must also match all Additional Filters expression specifications to belong to this Node Group.

To create an Additional Filters expression:

  1. ClosedNavigate to the Node Group Form: Additional Filters tab.
    1. From the workspace navigation panel, select the Configuration workspace.
    2. Expand the Object Groups folder.
    3. Select Node Group.

    4. Do one of the following:

      • To create a Node Group definition, click the  New icon.
      • To edit a Node Group definition, click the  Open icon in the row representing the Node Group definition you want to edit.
    5. In the Node Group form, select the Additional Filters tab.

  2. Establish the appropriate settings for the Additional Filters you need (see the Additional Filters Editor Choices and Additional Filters Editor Buttons table). See Guidelines for Creating Additional Filters for Node Groups for more information.

    1. Plan out the logic needed for your Filter String.

    2. Use the buttons on the bottom half of the Additional Filters Editor to establish the logic structure.

      For example, to establish the following structure, select Insert, then click AND, then NOT, and then AND a second time:

      (( ) AND NOT ( ))

    3. Now place your cursor in a location within the displayed Filter String, and use the top half of the filter editor to define the parameters of the selected filter requirement.

      For example, select a set of parentheses and use the Insert button to specify the filter requirement within those parentheses:

  3. Click  Save and Close.
Additional Filters Editor Choices for Node Groups
Attribute Description
Attribute

NNMi provides Additional Filters codes for a subset of object attributes. For more information about the available Additional Filter codes for each NNMi object type, click the link:

  • Node attribute codes Closed[click here for a list of attribute codes]

    Values from the Basic Attributes listed on the Node Form:

    • hostname (Hostname, case-sensitive)

    • mgmtIPAddress (Management Address)

    • isSnmpNode (SNMP Agent Enabled)
    • isNnmSystemLocal (NNMi Management Server)

    • securityGroupName (Security Group)

      Note If you enter the Name value for a Security Group that you do not have permission to access, the Node Group will be empty.

    Values from the Node Form:General Tab:

    • sysName (System Name)
    • sysLocation (System Location)
    • sysContact (System Contact)
    • sysOidNode (System Object ID)

    Addresses from the Node Form: IP Addresses Tab:

    • hostedIPAddress (Address)

    Unique Keys from the Node Form: Capabilities Tab:

    • capability (Unique Key of the Capability)

    Values from the Node Form: Custom Attributes Tab:

    Tip When creating complex Filter Strings that include customAttrName and customAttrValue pairs as one component of an "or" statement, to prevent NNMi from excluding Nodes that have zero Custom Attributes, use EXISTS or NOT EXISTS criteria for the customAttrName and customAttrValue pair definitions.

    Otherwise Nodes that do not have any Custom Attributes are automatically excluded even if they have values that pass other aspects of your filter.

    • customAttrName (Custom Attribute Name) Concept Link IconSee Also
    • customAttrValue (Custom Attribute Value) Concept Link IconSee Also
  • Security Group attribute codes Closed[click here for a list of attribute codes]

    Values from the Security Group Form:

    Note If you enter the Name or UUID value for a Security Group that you do not have permission to access, the Node Group will be empty.

    • securityGroupName (Name)
    • securityGroupUuid (UUID)
  • Tenant attribute codes Closed[click here for a list of attribute codes]

    Values from the Tenant Form:

    • tenantName (Name)
    • tenantUuid (UUID)
  • Device Profile attribute codes Closed[click here for a list of attribute codes]

    Values from the Basics Attributes on the Device Profile Form:

    NNMi matches the Label attribute values from the Device Profile Form for each of the following: 

    • devCategoryNode (Device Category)
    • devVendorNode (Device Vendor)
    • devFamillyNode (Device Family)

    To filter on the SNMP system object ID number assigned to a particular make/model, use the sysOidNode attribute. See Values from the Node Form: General Tab.

  • Regional Manager attribute codes (NNMi Advanced) Closed[click here for a list of attribute codes]

    Values from the associated entry on the Regional Manager Form: Connection Tab:

    • nnmSystemName (Hostname, case-sensitive)

      (NNMi Advanced) If the Global Network Management feature is enabled, this attribute value identifies a Regional Manager (NNMi management server).
Operator

The standard query language (SQL) operations to be used for the search.

Note Only the is null Operator returns null values in its search.

Valid operators are described below.

  • = Finds all values equal to the value specified. ClosedClick here for an example.

    Example: sysName = cisco2811 finds all devices with system name equal to cisco2811.

  • != Finds all values not equal to the value specified. ClosedClick here for an example.

    Example: sysName != cisco2811 finds all system names other than cisco2811.

  • < Finds all values less than the value specified. ClosedClick here for an example.

    IPv4 example: mgmtIPAddress < 15.239.255.255 finds all IP address values less than 15.239.255.255

    IPv6 example: mgmtIPAddress < ::ffff:0:0 finds all IP address values less than ::ffff:0:0

  • <= Finds all values less than or equal to the value specified. ClosedClick here for an example.

    Example: mgmtIPAddress <= 15.239.255.255 finds all IP address values less than or equal to 15.239.255.255.

  • > Finds all values greater than the value specified. ClosedClick here for an example.

    IPv4 example: mgmtIPAddress > 15.238.0.0 finds all IP address values greater than 15.238.0.0

    IPv6 example: mgmtIPAddress > ::ffff:ffff:ffff finds all IP address values greater than ::ffff:ffff:ffff 

  • >= Finds all values greater than or equal to the value specified. ClosedClick here for an example.

    Example: mgmtIPAddress >= 15.238.0.0 finds all IP address values greater than or equal to 15.238.0.0.

  • between Finds all values equal to and between the two values specified. ClosedClick here for an example.

    Example: mgmtIPAddress between 15.238.0.10 15.238.0.120 finds all IPv4 address values equal to or greater than 15.238.0.10 and equal to or less than 15.238.0.120.

  • in Finds any match to at least one value in a list of values. ClosedClick here for an example.

    Example:

    sysName in


    finds all systems with names that are cisco2811 or cisco5500.

    Note As shown in the example, each value must be entered on a separate line.

    NNMi displays the list of attributes using comma-separated values enclosed in parentheses, for example (cisco2811, cisco550). However, the comma-separated list is used only for display purposes. The actual delimiter is the new line.

  • is not null Finds all non-blank values. ClosedClick here for an example.

    Example: sysName is not null finds all systems that have a name value.

  • is null Finds all blank values. ClosedClick here for an example.

    Example: sysName is null finds all systems that do not have an assigned name value.

  • like Finds matches using wildcard characters. ClosedClick here for more information about using wildcard characters.

    The following attributes cannot be used with the like operator:

    • hostedIPaddress
    • mgmtIPaddress

    The asterisk (*) character means any number of characters of any type at this location.

    Note For optimum performance, avoid beginning your search string with an asterisk (*).

    The question mark (?) character means any single character of any type at this location.

    Examples:

    • sysName like cisco* finds all system names that begin with cisco.
    • sysName like cisco??* finds all system names that start with cisco followed by two characters.
    • sysName like rtr??bld5* finds all system names that have specific characters at an exact location, positions 1-3 (rtr) and 6-9 (bld5).
  • not between finds all values except those between the two values specified. ClosedClick here for an example.

    Example: mgmtIPAddress not between 15.238.0.10 15.238.0.120 finds all IP address values less than 15.238.0.10 and greater than 15.238.0.120.

    See Node Groups of IPv4 or IPv6 Addresses for more examples of using the not between Operator.

  • not in Finds all values except those included in the list of values. ClosedClick here for an example.

    Example:

    sysName not in


    finds all system name values other than cisco2811 and cisco5500.

    Note As shown in the example, each value must be entered on a separate line.

    NNMi displays the list of attributes using comma-separated values enclosed in parentheses, for example, (cisco2811, cisco550). However, the comma-separated list is used only for display purposes. The actual delimiter is the new line.

  • not like Finds all that do not have the values specified (using wildcard strings). ClosedClick here for an example.

    The following attributes cannot be used with the not like operator:

    • hostedIPaddress
    • mgmtIPaddress

    The asterisk (*) character means any number of characters of any type at this location.

    The question mark (?) character means any single character of any type at this location.

    Examples:

    • sysName not like cisco* finds all system names that do not begin with cisco.
    • sysName not like cisco??* finds all system names that do not begin with cisco followed by two characters.
    • sysName not like rtr??bld5* finds all system names that do not have specific characters at an exact location, positions 1-3 (rtr) and 6-9 (bld5).
Value

The value for which you want NNMi to search.

Note the following:

  • The values you enter are case sensitive.
  • NNMi displays a variable number of value fields depending on the Operator selected. For example, the between Operator causes two value fields to be displayed.
  • The in and not in operators require that each value be entered on a separate line.

  • When entering a value for the Capability attribute, copy and paste the Unique Key value from the Node form: Capability tab.
Additional Filters Editor Buttons
Button Description
Append Appends the current expression (Attribute, Operator, and Value) to the selected expression already included in the Filter String.
Insert Inserts the current expression (Attribute, Operator, and Value) in front of the cursor location within the Filter String.
Replace Replaces the selected expression with the expression displayed in the Attribute, Operator, and Value fields.
AND

Inserts the AND Boolean Operator in the selected cursor location.

Note View the expression displayed under Filter String to see the logic of the expression as it is created.
OR

Inserts the OR Boolean Operator in the current cursor location.

Note View the expression displayed under Filter String to see the logic of the expression as it is created.
NOT

Can be used in any part of the Filter String to specify that NNMi should exclude nodes with values that pass the expression that immediately follows the NOT.

For example, when evaluating the following Filter String, NNMi includes nodes with a hostname that contains router, followed by any number of characters, followed by xyz.com and excludes any nodes with a Device Profile that includes Cisco as the Vendor value:

(hostname like router*.xyz.com OR NOT (devVendorNode = Cisco))

EXISTS

Used for filters that include Capabilities or Custom Attribute names and values in the Filer String. Indicates that you want NNMi to consider nodes that have Capabilities or Custom Attributes when evaluating the Filter String.

Tip When creating complex Filter Strings that include customAttrName and customAttrValue pairs as one component of an "or" statement, to prevent NNMi from excluding Nodes that have zero Custom Attributes, use EXISTS or NOT EXISTS criteria for the customAttrName and customAttrValue pair definitions.

Otherwise Nodes that do not have any Custom Attributes are automatically excluded even if they have values that pass other aspects of your filter.

For example, when evaluating the following Filter String, NNMi includes nodes with a hostname that includes router, followed by any number of characters, followed by xyz.com as well as any nodes that have the Custom Attribute edge and that edge value is true:

(hostname like router*.xyz.com OR EXISTS((customAttrName=edge AND customAttrValue=true)))

NOT EXISTS

Used for filters that include Capabilities or Custom Attribute names and values in the Filer String. Indicates that you want NNMi to consider nodes that do not have any Capabilities or Custom Attributes when evaluating the Filter String, but exclude the nodes that match the expression that follows the NOT EXISTS.

Tip When creating complex Filter Strings that include customAttrName and customAttrValue pairs as one component of an "or" statement, to prevent NNMi from excluding Nodes that have zero Custom Attributes, use EXISTS or NOT EXISTS criteria for the customAttrName and customAttrValue pair definitions.

Otherwise Nodes that do not have any Custom Attributes are automatically excluded even if they have values that pass other aspects of your filter.

For example, when evaluating the following Filter String, NNMi includes nodes with a hostname that includes router, followed by any number of characters, followed by xyz.com and excludes any nodes with Custom Attribute edge and that edge value is true.

(hostname like router*.xyz.com OR NOT EXISTS((customAttrName=edge AND customAttrValue=true)))

Delete

Deletes the selected expression.

Note If the Boolean Operator is selected, the Additional Filters Editor deletes all expressions associated with the Boolean Operator.

Send Help Center feedback