Configure QoS Thresholds for QA Groups

This topic includes the following sections:

• Add QoS Threshold Configuration to QA Groups
• Edit QoS Threshold Configuration of QA GroupsDelete QoS Threshold Settings of QA Groups
• Delete QoS Threshold Settings of QA Groups
• Import QoS Thresholds of QA Groups
• Export QoS Thresholds of QA Groups

NNM iSPI Performance for QA enables you to track the health and performance of the QA groups, which you have configured and discovered. You can configure thresholds for both QA probes and QoS probes, and create incidents whenever the performance value assigned to the QA groups breaches the threshold.

NNM iSPI Performance for QA performs the following actions, if a threshold is breached:

• Sets the QA Groups (QA Probes or QoS) probes’ status to major.

• Creates an incident for the violated threshold.
• Retains the threshold state as Nominal, or sets the threshold state to High or Low depending on the count-based, or time-based threshold configuration.

You can monitor the QA Groups entities for both QA Probes and QoS, and generate an incident based on the count-based threshold configuration or time-based threshold configuration.

Threshold Configuration

Count-Based Threshold Configuration

You can generate an incident based on the count or number of consecutive times a metric violates the threshold value. You can define this count in the Threshold Configuration form.

Time-Based Threshold Configuration

Time-Based threshold configuration enables you to raise an alert when the threshold breached state persists for more than a specific time period. This is derived by specifying X as the duration of time in minutes when the metric is in a threshold breached state within Y number of minutes specified in the sliding window.

Example for Time-Based Threshold Configuration

Consider a scenario, where the polling interval is 5 minutes; High duration is 10 minutes; and High Duration Window is 60 minutes. In this scenario, an incident is generated whenever the High Duration exceeds 10 minutes within the 60 minute duration. NNM iSPI Performance for QA uses a sliding window wherein each time the High Duration (10 minutes) is reached, NNM iSPI Performance for QA drops the oldest polled value (first 5 minutes) and adds the most recent (between 60 to 65 minutes). This procedure continues and enables you to determine time-based threshold violation.

You can make utmost use of the Time-Based threshold violation by ensuring that the duration specified in the sliding window is greater than or equal to the polling interval.

Baseline Settings Configuration

Baseline Deviation Settings Configuration

Apart from the time-based and count-based threshold configuration, you can also do baseline monitoring based on the baseline deviation setting configuration in NNM iSPI Performance for QA. You can do baseline deviation setting configuration for the selected probe, service, and metric. An incident is generated and the baseline state transitions to Abnormal Range only if it meets all the criteria listed below:

• Exceeds the count or the number of standard deviation that is above the average value for the metric, or exceeds the count or the number of standard deviation that is below the average value for the metric. This count is specified in the Upper Baseline Limit Deviations or the Lower Baseline Limit Deviations in the baseline deviation settings configuration
• Exceeds the duration for which the upper or lower baseline deviation persists in the specified sliding window duration.

recommends that you have the probes with same frequency in a QA group for the Baseline Threshold feature to work effectively.

Add QoS Threshold Configuration to QA Groups

To add threshold configuration to a QA Group:

1. Launch the QoS Threshold configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > QoS. The QoS Threshold Configuration form opens.
2. Click New in the QoS Threshold Configuration form panel. The Add QoS threshold configuration form opens.

3. Specify the following to configure the threshold:

   Field Name	Description
   Name	The name of the Threshold setting. The name should be unique.
   Order	Specify a numeric value. NNM iSPI Performance for QA checks the configuration settings in the order you define (lowest number first).
   Threshold Type	In the Threshold Type, select QA Group Based.
   QA Group condition	Lists the configured and discovered QoS QA Groups. You can select any one of the configured and discovered QoS QA Groups, from the drop down list to configure the threshold.

4. You can perform the following tasks in the Threshold Settings Tab:

   Icon	Description
   New	Adds QA Group threshold settings.
   Edit	Edits QA Group threshold settings.
   Delete	Deletes QA Group threshold settings.
   Refresh	Retrieves the last saved threshold configuration from the database and displays the data.
   Delete All	Deletes all QA Group threshold settings.

Add QoS Threshold Settings to QA Groups

To add a new threshold setting, do the following:

1. Specify all the mandatory fields when adding QoS threshold configuration to QA groups.

2. Click New in the Threshold Settings tab.

   The Add Threshold settings form opens.

3. Specify the following to configure the threshold settings:
   

Field Name	Description
Type	Select the type of threshold violation. The valid types are Count-Based and Time-Based.

After you select the metric to configure the threshold, the list of fields relevant to the selected metric appear. You can specify the following values to configure the new threshold:

1. The following field appears, if you selected the Type as Count Based:
   

Field Name	Description
High Value	Enter the threshold value. This value indicates the maximum value above which the metric will be considered to have violated the Nominal range. For Packet Loss metric, enter the High Value in percentage.
High Value Rearm	Enter the high value rearm for the threshold. For Packet Loss metric, enter the High Value Rearm in percentage. The High Value Rearm is used to indicate the end of the high threshold state and NNM iSPI Performance for QA clears the incident once it reaches below this value. The high value rearm must always be lower than the high value. Example For the Discarded Packets percentage, you must generate an incident when the percentage is 90 and clear the incident when the percentage comes down to 60. Set the following values for the threshold: High Value: 90 High Value Rearm: 60 This value enables you to be aware when a network performance problem starts to improve.

Field Name	Description
Trigger Count	Specify after how many consecutive threshold violations NNM iSPI Performance for QA must alert the operator by transitioning the threshold state to High.

The following fields appear if you selected the Type as Time-Based:


Field Name	Description
High Duration	Designate the minimum time within which the metric value must remain in the High range. For example if you specify this value to be 20 minutes for Packet Loss Percentage metric, NNMi considers the threshold to be violated if the Packet Loss Percentage is high for 20 minutes. You define the high threshold value in the High Value field. The High Duration should be equal to or greater than the associated Polling Interval setting, because that is how often NNMi provides a data point..
High Duration Window	Designate the window of time within which the High Duration criteria must be met. To enable this setting, the value must be: greater than 0 (zero) the same as or greater than the High Duration value The NNMi uses a sliding window. Each time the High Window Duration is reached, NNMi drops the oldest polling interval and adds the most recent. For example, if you specify this value to be 30 minutes for Packet Loss Percentage metric, NNMi considers the threshold to be violated if the Packet Loss Percentage is high for 20 out of 30 minutes.

4. Select the following to generate an incident when the time-based threshold or count-based threshold value is violated:
   

Field Name	Description
Generate Incident	Select this option if you want NNM iSPI Performance for QA to generate an incident for count-based or time-based threshold violations. By default this option is selected.

5. Use any one of the following options to complete the task:

Icons	Description
Close	Closes the Add Threshold Configuration form without saving the threshold information you have entered.
Save and Close	Saves the threshold information and closes the Threshold Configuration form.

After you configure the threshold settings, you can view the configured threshold details in the Configured QoS Thresholds tab.

6. Continue creating the threshold in the Add QoS Threshold Configuration form.
7. After you configure the threshold settings, Click Apply Threshold Now in the QoS Threshold Configuration form, to apply the configured thresholds.

Edit QoS Threshold Configuration of QA Groups

To edit an existing threshold setting for a QA Group:

1. Launch the QoS Threshold configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > QoS. The QoS Threshold Configuration form opens.
2. Select the configured threshold settings to modify, and click Edit in the QoS Threshold Configuration form.

The Edit QoS threshold configuration form opens.

3. Specify the following to configure the threshold:

Field Name	Description
Name	The name of the Threshold setting. The name should be unique.
Order	Specify a numeric value. NNM iSPI Performance for QA checks the configuration settings in the order you define (lowest number first).
Threshold Type	In the Threshold Type, select QA Groups Based.
QA Group condition	Lists the configured and discovered QoS QA Groups. You can select any one of the configured and discovered QoS QA Groups, from the drop down list.

You can perform the following tasks in the Threshold Settings Tab:

Icon	Description
New	Adds QA Group threshold settings.
Edit	Edits QA Group threshold settings.
Delete	Deletes QA Group threshold settings.
Refresh	Retrieves the last saved threshold configuration from the database and displays the data.
Delete All	Deletes all QA Group threshold settings.

Edit QoS Threshold Settings of QA Groups

To edit an existing threshold setting for a QA Group:

1. Specify all the mandatory fields when editing QoS threshold configuration of QA groups.

2. Select the threshold setting to modify, and Click Edit in the Configured QoS Thresholds panel.

   The Edit QoS Threshold Settings form opens.

3. Specify the following to configure the threshold settings:
   

Field Name	Description
Type	Select the type of threshold violation. The valid types are Count-Based and Time-Based.
Metric

4. After you select the metric to configure the threshold, the list of fields relevant to the selected metric appear. You can specify the following values to configure the new threshold:

Field Name	Description
High Value	Enter the threshold value. This value indicates the maximum value above which the metric will be considered to have violated the Nominal range. For Packet Loss metric, enter the High Value in percentage.
High Value Rearm	Enter the high value rearm for the threshold. For Packet Loss metric, enter the High Value Rearm in percentage. The High Value Rearm is used to indicate the end of the high threshold state and NNM iSPI Performance for QA clears the incident once it reaches below this value. The high value rearm must always be lower than the high value. Example For the Discarded Packets percentage, you must generate an incident when the percentage is 90 and clear the incident when the percentage comes down to 60. Set the following values for the threshold: High Value: 90 High Value Rearm: 60 This value enables you to be aware when a network performance problem starts to improve.

The following field appears, if you selected the Type as Count-Based:


Field Name	Description
Trigger Count	Specify after how many consecutive threshold violations NNMi must alert the operator by transitioning the threshold state to High.

The following fields appear if you selected the Type as Time-Based:


Field Name	Description
High Duration	Designate the minimum time within which the metric value must remain in the High range. For example if you specify this value to be 20 minutes for Packet Loss Percentage metric, NNMi considers the threshold to be violated if the Packet Loss Percentage is high for 20 minutes. You define the high threshold value in the High Value field. The High Duration should be equal to or greater than the associated Polling Interval setting, because that is how often NNMi provides a data point..
High Duration Window	Designate the window of time within which the High Duration criteria must be met. To enable this setting, the value must be: greater than 0 (zero) the same as or greater than the High Duration value The NNMi uses a sliding window. Each time the High Window Duration is reached, NNMi drops the oldest polling interval and adds the most recent. For example, if you specify this value to be 30 minutes for Packet Loss Percentage metric, NNMi considers the threshold to be violated if the Packet Loss Percentage is high for 20 out of 30 minutes.

Select the following to generate an incident when the time-based threshold or count-based threshold value is violated:


Field Name	Description
Generate Incident	Select this option if you want NNM iSPI Performance for QA to generate an incident for count-based or time-based threshold violations. By default, this option is selected.

5. Use any one of the following options to complete the task:

   Icons	Description
   Close	Closes the Edit Threshold Configuration form without saving the threshold information you have entered.
   Save and Close	Saves and applies the changes made.

6. Click Refresh to view the changes in the Configured QoS Thresholds tab.
7. Click Save or Save and Close in the QoS Threshold Configuration form.
8. Click Apply Threshold Now to enable the threshold.

Delete QoS Threshold Settings of QA Groups

To delete an existing QoS threshold setting for a QA Group:

1. Launch the QoS Threshold configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > QoS. The QoS Threshold Configuration form opens.
2. Select one or more configured threshold settings in the Configured QoS Thresholds tab, and click Delete.
   or
   Click Delete All to delete all QoS QA group threshold settings.
   
3. Click Refresh in the QoS Threshold Configuration panel to view the changes.

However, NNMi does not delete the incidents that are already generated for an existing threshold.

Import QoS Thresholds of QA Groups

To import threshold configurations from an XML file:

1. Launch the QoS Threshold configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > QoS. The QoS Threshold Configuration form opens.
2. Click Import.

3. In the user prompt dialog, enter the file name from where you want to import the QA Groups for QoS threshold configuration information.

   You must enter the file name with full path information; for example, C:\temp\QAGroupCBQoSthreshold_conf.xml

4. Click OK in the user prompt dialog.

   If a threshold is already defined and displayed in the Configured QoS Thresholds panel, the import utility does not import the configuration information for this threshold from the XML file.

You can also import threshold configuration information using the following command line utility:

Linux: $NnmInstallDir/bin/nmsqathresholdconfigutil.ovpl –u <username> –p <password> –import –type cbqos <filename>

Windows:%NnmInstallDir%\bin\nmsqathresholdconfigutil.ovpl –u <username> –p <password> –import –type cbqos <filename>

If the threshold import fails, check the following log files:

Linux: $NnmDataDir/log/qa/qa.log

Windows:%NnmDataDir%\log\qa\qa.log

-u <username> -p <password> are optional parameters.

Export QoS Thresholds of QA Groups

To export the existing QA Group threshold configurations:

1. Launch the QoS Threshold configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > QoS. The QoS Threshold Configuration form opens.
2. Click Export.

3. Type the file name where you want to export the existing QA Groups for QoS threshold configurations in the user prompt dialog.

   You must type the file name with full path information; for example, C:\temp\QAGroupsCBQoSthreshold_conf.xml

   If you type the XML file name without entering the absolute path, by default the file gets saved in the following directory:

   Linux: $NnmDataDir/shared/qa/conf

   Windows : %NnmDataDir%\shared\qa\conf

4. Click OK in the user prompt dialog.

You can also export the existing QA Groups for QoS threshold configurations using the following command line utility:

Linux: $NnmInstallDir/bin/nmsqathresholdconfigutil.ovpl –u <username> –p <password> –export –type cbqos <filename>

Windows: NnmInstallDir%\bin\nmsqathresholdconfigutil.ovpl –u <username> –p <password> –export –type cbqos <filename>

The threshold export utility does not export a threshold unless the threshold is associated with a QA Group.

If the threshold export fails, check the following log files:

Linux: $NnmDataDir/log/qa/qa.log

Windows: %NnmDataDir%\log\qa\qa.log

-u <username> -p <password> are optional parameters.