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 > Monitor Network Health > Create Custom Polling Configurations > Create a Custom Poller Collection > Configure Threshold Information for a Custom Poller Collection

Configure Threshold Information for a Custom Poller Collection

Note: The Threshold Configuration feature applies to only Instance Custom Poller Collection Types.

Thresholds specify the high and low values from the MIB Expression results that indicate a High Threshold situation or Low Threshold situation. NNMi administrators can configure NNMi to change the associated High State and Low State for the Custom Polled Instance and generate an incident based on the Custom Polled Instance's State.

Tip Check to see if the threshold you want is already defined. See About Threshold Settings Provided by NNMi.

When configuring Threshold settings, note the following:

If a polled value is between the high range and the low range, the Polled Instance state is Normal.
You can configure Comparison Maps, which also contribute to State calculations. If you configure both Thresholds and Comparison Maps, NNMi first checks the Threshold settings to determine State values. If the threshold evaluates to non-Normal, NNMi uses the Threshold settings to determine State values. if the Threshold evaluates to Normal, NNMi checks for a non-Normal State using any Comparison Map configuration. See Configure Comparison Maps for a Custom Poller Collection for more information about configuring Comparison Maps.
The MIB Expression must evaluate to a numeric type. (OCTET STRING type is not supported.)
When evaluating Threshold configurations with MIB Expressions that include one or more MIB Variables of type Counter or Counter64, NNMi evaluates the MIB Variable value using the difference in value between the most recent poll and the poll before it.

To configure thresholds for a MIB Variable:

Prerequisite: You must specify the MIB Expression you want to poll. See Specify the MIB Variable Information for a Custom Poller Collection for more information.
Navigate to the Custom Poller Collection form.
1. From the workspace navigation panel, select the Configuration workspace.
2. Expand the Monitoring folder.
3. Select the Custom Poller Configuration form.
4. Navigate to the Custom Poller Collections tab.
5. Do one of the following to open the Custom Poller Collection form:
  - To create a collection, click the New icon.
  - To edit a collection, double-click the row representing the configuration you want to edit.
6. Navigate to the MIB Variables tab.
7. Do one of the following to open the MIB Variable form:
  - To create a collection, click the New icon.
  - To edit a collection, double-click the row representing the configuration you want to edit.
8. Locate the Threshold tab.
Make your configuration choices (see table).
Click Save and Close to close the Custom Poller Collection form.
Complete the configuration for this Custom Poller Collection configuration, if you have not already done so: See Also
Click Save and Close to close the Custom Poller Configuration form.

High Threshold Attributes for a Custom Polled Instance
Monitored Attribute	Description
Threshold Setting Type	Select one of the following: Count to configure count-based thresholds. Count-based threshold settings enable you to determine as soon as a threshold is crossed (for example, the results of polling the MIB Expression are above 90 percent for 4 consecutive polls). See Examples of Count-Based Threshold Monitoring for more information. Time to configure time-based thresholds. Time-based threshold settings enable you to determine whether a threshold is crossed within a particular duration of time (for example, the results of polling the MIB Expression are above 90 percent for 20 out of 30 minutes). See Examples of Time-Based Threshold Monitoring for more information.
High State	The Custom Polled Instance's State when the results of polling the MIB Expression exceed the specified High Value for the specified Count or Duration. Possible values are: Normal Warning Minor Major Critical
High Value	The value that above which becomes a threshold situation. Use one of the following: Designate a percentage between 0.00 and 100.00. For special situations, the following values can be used: 0.000000000000001 (or 1E-15 in Scientific Notation) for the smallest value greater than zero. 99.99999999999999 for the highest value less than one hundred. Designate any appropriate integer value (for example, a Management Address ICMP Response Time of 0 or greater milliseconds ). The High Value must be greater than or equal to the designated Low Value. If you use the highest possible value, the threshold is disabled because it cannot be crossed.
High Value Rearm	The High Value Rearm designates the lower boundary of the High Threshold range of values. Designate a numeric value appropriate for the MIB Expression definition. After entering a High threshold situation, when a returned value is below the specified High Value Rearm, the following happens: For Time-Based Thresholds: The current polling interval does not contribute toward High Duration. The criteria for High Duration and High Duration Window determine when the High Threshold situation ends. For Count-Based Thresholds: After entering a High threshold situation, when a returned value is below the specified High Value Rearm, the High Threshold situation ends. Note The High Value Rearm must be less than or equal to the High Value and greater than or equal to the Low Value Rearm (if any).
If you chose Threshold Setting Type = Count configure the following:
High Trigger Count	Designate the number of consecutive polling intervals the returned value must be greater than the specified High Value to meet the High Threshold criteria. The default value is 1.
If you chose Threshold Setting Type = Time configure the following (setting both of these to zero disables the High Threshold):
High Duration	Designate the minimum time within which the value must remain in the High range before the threshold state changes to High and (optionally) an incident is generated. The High Duration should be equal to or greater than the associated Polling Policy's Polling Interval setting, because that is how often NNMi provides a data point. Note The polling interval should be less than or equal to the High Duration. The High Duration should be a multiple of the polling interval. For example, if the polling interval is 5 minutes, use multiples of 5 (10, 15, or 20). Setting both the Low Duration and Low Duration Window to zero disables the Low threshold.
High Duration Window	Designate the window of time within which the High Duration criteria must be met. Note Setting both the High Duration and High Duration Window to zero disables the High threshold. To enable this setting, the value must be: greater than 0 (zero) the same as or greater than the High Duration value NNMi uses a sliding window. Each time the High Window Duration is reached, NNMi drops the oldest polling interval and adds the most recent. See Examples of Time-Based Threshold Monitoring for more information.

Low Threshold Attributes for a Custom Polled Instance
Monitored Attribute	Description
Threshold Setting Type	Select one of the following: Count to configure count-based thresholds. Count-based threshold settings enable you to determine as soon as a threshold is crossed (for example, the results of polling the MIB Expression are above 90 percent for 4 consecutive polls). See Examples of Count-Based Threshold Monitoring for more information. Time to configure time-based thresholds. Time-based threshold settings enable you to determine whether a threshold is crossed within a particular duration of time (for example, the results of polling the MIB Expression are above 90 percent for 20 out of 30 minutes). See Examples of Time-Based Threshold Monitoring for more information.
Low State	The Custom Polled Instance's State when the results of polling the MIB Expression are below the specified Low Value for the specified Count or Duration. Possible values are: Normal Warning Minor Major Critical
Low Value	The value that below which becomes a threshold situation. Use one of the following: Designate a percentage between 0.00 and 100.00. For special situations, the following values can be used: 0.000000000000001 (or 1E-15 in Scientific Notation) for the smallest value greater than zero. 99.99999999999999 for the highest value less than one hundred. Designate any appropriate integer value (for example, a Management Address ICMP Response Time of 0 or greater milliseconds ). The Low Value must be less than or equal to the designated High Value. If you use the minimum possible value, the Low threshold is disabled because it cannot be crossed.
Low Value Rearm	The Low Value Rearm designates the upper boundary of the Low Threshold range of values. Designate a numeric value appropriate for the MIB Expression definition. After entering a Low threshold situation, when a returned value is above the specified Low Value Rearm, the following happens: For Time-Based Thresholds: The current polling interval does not contribute toward Low Duration. The criteria for Low Duration and Low Duration Window determine when the Low Threshold situation ends. For Count-Based Thresholds: After entering a Low threshold situation, when a returned value is above the specified Low Value Rearm, the Low Threshold situation ends. Note The Low Value Rearm must be greater than or equal to the Low Value and less than or equal to the High Value Rearm (if any).
If you chose Threshold Setting Type = Count configure the following:
Low Trigger Count	Designate the number of consecutive polling interval the returned value must be less than the specified Low Value to meet the Low Threshold criteria. The default value is 1.
If you chose Threshold Setting Type = Time configure the following (setting both of these to zero disables the Low Threshold):
Low Duration	Designate the minimum time within which the value must remain in the Low range before the threshold state changes to Low and (optionally) an incident is generated. Note The polling interval should be less than or equal to the Low Duration. The Low Duration should be a multiple of the polling interval. For example, if the polling interval is 5 minutes, use multiples of 5 (10, 15, or 20).
Low Duration Window	Designate the window of time within which the Low Duration criteria must be met. Note Setting both the Low Duration and Low Duration Window to zero disables the Low threshold. To enable this setting, the value must be: greater than 0 (zero) the same as or greater than the Low Duration value NNMi uses a sliding window. Each time the High Window Duration is reached, NNMi drops the oldest polling interval and adds the most recent. See Examples of Time-Based Threshold Monitoring for more information.

Send Help Center feedback