Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Create Groups of Nodes or Interfaces > Create Interface Groups > Create Interface Groups Using ifType Values and Filters > Specify Interface Group Additional Filters

Specify Interface 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.]

The Additional Filters Editor enables you to create expressions to further define the interfaces to be included in an Interface 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 first evaluates any Interface Type filter. Nodes must match at least one specification to belong to this Interface Group.
NNMi then evaluates the Additional Filters expression. Nodes must also match all Additional Filters expression specifications to belong to this Interface Group.

To create any Additional Filters expression:

Navigate to the Interface Group Form: Additional Filters tab.
1. From the workspace navigation panel, select the Configuration workspace.
2. Expand the Object Groups folder.
3. Select Interface Groups.
4. Do one of the following:
  - To create an Interface Group definition, click the New icon.
  - To edit an Interface Group definition, click the Open icon in the row representing the configuration you want to edit.
5. In the Interface Group form, select the Additional Filters tab.
Establish the appropriate settings for the Additional Filters you need.
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:
Click Save and Close.

Additional Filters Editor Choices for Interface Groups
Attribute	Description
Attribute	NNMi provides Additional Filters codes for a subset of object attributes. For more information about each one, click the link: Interface attribute codes [click here for a list of attribute codes] Values from the Basic Attributes listed on the Interface Form: ifName (Name) hostedOn (Hosted On Node) ifPhysAddress (Physical Address) Values from the Interface Form: General Tab: ifAlias (Interface Alias) Note the following when using the ifAlias attribute: To include empty (or null) ifAlias entries in your search criteria, match the value "null" (for example: `ifAlias is null`) If you search for an empty ifAlias in your search criteria, the empty value will not be matched (for example do not use : `ifAlias != <string>)` ifDesc (Interface Description) ifIndex (Interface Index) ifSpeed (Interface Speed) Addresses from the Interface Form: IP Addresses Tab: ipAddress (IP Address associated with the interface) Unique Keys from the Interface Form: Capabilities Tab: capability (Unique Key of the Capability) Values from the Interface Form: Custom Attributes Tab: Note When using `customAttrName`and `customAttrValue` pairs, use EXISTS if you want NNMi to consider Nodes that do not have Custom Attributes when evaluating the entire Filter String. Otherwise Nodes that do not have Custom Attributes are automatically excluded from the Node Group even if they have values that pass other aspects of your filter. customAttrName (Custom Attribute Name) See Also customAttrValue (Custom Attribute Value) See Also Node attribute codes [click here for a list of attribute codes] Values from the Basics information on the Node Form: isSnmpInterface (SNMP Agent Enabled) Values from the Node Form: General Tab. sysOidInterface (System Object ID) Device Profile attribute codes [click here for a list of attribute codes] Values from the Basics information on the Device Profile Form: NNMi matches the Label attribute values from the Device Profile Form for each of the following: devCategoryInterface (Device Category) devVendorInterface (Device Vendor) devFamilyInterface (Device Family) To filter on the parent node's SNMP system object ID number (assigned to a particular make/model), use the sysOidInterface attribute. VLAN attribute codes [click here for a list of attribute codes] Values from the Basic Attributes on the VLAN form:: Note To maximize performance, when you want to filter interfaces based on a VLAN Id or VLAN Name, avoid using multiple filter expressions. For example, use the `between` operator instead of the greater than or equal to (>=) and less than or equal to (<=) operators. vlanid (VLAN Id) vlanName (Global VLAN Name) Port attribute codes [click here for a list of attribute codes] Values from the Basic Attributes on the Port form:: Note If the interface has multiple ports, the interface is selected if there is a match on any one port associated with the interface. configuredDuplexSetting (Configured Duplex Setting)
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. Click here for an example. Example: `ifName=Fa0/14` finds all interface names that are equal to Fa0/14. != Finds all values not equal to the value specified. Click here for an example. Example:`ifName !=` `lan0` finds all interface names other than lan0. < Finds all values less than the value specified. Click here for an example. Example: `ifSpeed <= 100000000` finds all interfaces with an (interface speed) ifSpeed less than 100 Mbps. <= Finds all values less than or equal to the value specified. Click here for an example. Example: `ifSpeed <= 100000000` finds all interfaces with an (interface speed) ifSpeed less than or equal to 100 Mbps. > Finds all values greater than the value specified. Click here for an example. Example: `ifSpeed >= 10000000` finds all interfaces with an (interface speed) ifSpeed greater than 10 Mbps. >= Finds all values greater than or equal to the value specified. Click here for an example. Example: `ifSpeed >= 10000000` finds all interfaces with an (interface speed) ifSpeed greater than or equal to 10 Mbps. between Finds all values equal to and between the two values specified. Click here for an example. Example: `ifSpeed between 10000000 100000000` finds all interfaces with an (interface speed) ifSpeed equal to or greater than 10 Mbps and equal to or less than 100 Mbps. in Finds any match to at least one value in a list of values. Click here for an example. Example: `ifName` `in` finds all interfaces with names that are Fa0/14 or Fa0/15. 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, (Fa0/14, Fa0/15). 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. Click here for an example. Example: `ifName is not null` finds all interfaces that have a name value. is null Finds all blank values. Click here for an example. Example:`ifName is null` finds all interfaces that do not have an assigned name value. like Finds matches using wildcard characters. Click here for more information about using wildcard characters. The following attributes cannot be used with the `like` operator: ifIndex ifSpeed IPAddress 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: `ifName like ATM` finds all interface names that begin with ATM. `ifName like Ethernet??` finds all interface names that begin with*Ethernet followed by two characters. `ifName like 10/???BASE-TX` finds all interface names that have specific characters at an exact location, positions 1-3 (10/) and 7-13 (BASE-TX). not between* Finds all values except those between the two values specified. Click here for an example. Example: `ifSpeed not between 10000000 100000000` finds all interfaces with an (interface speed) ifSpeed less than 10 Mbps and greater than 100 Mbps. not in Finds all values except those included in the list of values. Click here for an example. Example: `ifName` `not in` finds all interface name values other than Fa0/14 or Fa0/15. 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, (Fa0/14, Fa0/15). 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). Click here for an example. The following attributes cannot be used with the `not like` operator: ifIndex ifSpeed IPAddress 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: `ifName not like ATM` finds all interface names that do not begin with ATM. `ifName not like Ethernet??` finds all interface names that do not begin with*Ethernet followed by two characters. `ifName not like 10/???BASE-TX` finds all interface names that do not have specific characters at an exact location*, positions 1-3 (10/) and 7-13 (BASE-TX).
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 Interface 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 interfaces with values that pass the expression that immediately follows the NOT. For example, when evaluating the following expression, NNMi includes interfaces with (interface description) ifDesc containing VLAN, and excludes any Interfaces that have VLAN10 for the (interface name) ifName value: `(ifDesc like VLAN AND NOT (ifName=VLAN10))` Note: View the expression displayed under Filter String to see the logic of the expression as it is created.
EXISTS	Used for filters that include Capabilities or Custom Attribute names and values in the Filer String. Indicates that you want NNMi to consider interfaces 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 interfaces with (interface description) ifDesc containing VLAN, as well as any Interfaces Custom Attribute Role value is LAN Connection to Oracle Server: `(ifDesc like VLAN OR EXISTS((customAttrName=Role AND customAttrValue=LAN Connection to Oracle Server)))` Note View the expression displayed under Filter String to see the logic of the expression as it is created.
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 interfaces that do not have any Capabilities or Custom Attributes when evaluating the Filter String, but exclude the interfaces 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 expression, NNMi includes interfaces with (interface description) ifDesc containing VLAN, and excludes any Interfaces that have the Custom Attribute Role and that Role value is LAN Connection to Oracle Server: `(ifDesc like VLAN OR NOT EXISTS((customAttrName=Role AND customAttrValue=LAN Connection to Oracle Server)))` Note: View the expression displayed under Filter String to see the logic of the expression as it is created.
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