Configure Site Thresholds

This topic includes the following sections:

• Add Threshold Configuration
• Edit Threshold Configuration
• Delete Thresholds
• Export Thresholds
• Import Thresholds

To configure a threshold for a site, you must have a source site, but may not have a destination site. If you do not assign a destination site to the threshold, the threshold is applied to all the QA probes run from the source site.

You can configure thresholds for the following Quality Assurance metrics derived from the QA probes configured for an existing site:

• Round Trip Time (RTT)
• Jitter
• Packet Loss (Can be from source to destination, and from destination to source.)
• Mean Opinion Score (MOS)

For configuring thresholds for probes, it is recommended to use the QA group–based threshold configuration than the site-based threshold configuration.

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

• Sets the QA probe status to Major.
• Creates an incident for the violated threshold.
• Sends the threshold violation details to the Network Performance Server for generating reports.
• 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.

For information about overriding thresholds of probes specific to a site, see Configure Probe Thresholds.

In a GNM environment, the global manager receives the threshold states from the sites in the regional managers. You cannot configure thresholds for remote sites. The thresholds configured for the sites of the global managers are not applicable for the sites of regional managers.

You can monitor the network performance and generate an incident based on the count-based threshold or time-based threshold configuration.

You can only configure threshold for a combination of a site, service, and metric.

Threshold Configurations

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 a baseline monitoring based on the baseline deviation setting configuration in NNM iSPI Performance for QA. You can do a baseline deviation setting configuration for the selected site, 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 Lower Baseline Limit Deviations for the selected metric 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 site for the Baseline Threshold feature to work effectively.

Add Threshold Configuration

To add a new threshold configuration:

1. Launch the Threshold Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > Probes > Sites/QA Group. The Threshold Configuration form opens.

2. Click New in the Threshold Configuration panel.

   The Add Threshold Configuration form opens.
   

3. Select Site in Threshold Type field.

4. Specify the following information in the Threshold Configuration panel:

   Field Name	Description
   Threshold Type	In the Threshold Type, select Site Based.
   Order	Specify a numeric value. NNM iSPI Performance for QA checks the configuration settings in the order you define (lowest number first)
   Source Site	Select the name of the source site. This field is mandatory.
   Destination Site	Select the destination site for the QA probes. This field is optional.
   Service	The type of the discovered QA probe. This field is mandatory. NNM iSPI Performance for QA recognizes the following QA probe types: UDP Echo ICMP Echo UDP TCP Connect HTTP HTTPS VoIP DNS DHCP Oracle ICMP Jitter

You can view the two tabs; Threshold Settings and Baseline Settings.

5. You can perform the following tasks when you click on the Threshold Settings tab.

   Icon	Description
   New	Adds threshold settings for the site.
   Delete	Deletes the selected threshold settings for the site.
   Refresh	Retrieves the last saved threshold configuration from the database and displays the data.
   Delete All	Deletes all the thresholds configured for the site.

6. You can perform the following tasks when you click on the Baseline Settings tab.

   Icon	Description
   New	Adds baseline settings for the site.
   Delete	Deletes the selected baseline settings for the site.
   Refresh	Retrieves the last saved threshold configuration from the database and displays the data.
   Delete All	Deletes all the baseline settings configured for the site.

Add Threshold Settings

To add a new threshold setting:

1. Make sure that you selected the Source Site, and Service when Adding Threshold Configuration.

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.
   Metric	Select the metric for which you are configuring the threshold. The metrics are populated based on the service. For information about the metrics for each service type, see Supported Threshold Configuration Metrics.

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 Round Trip Time (RTT) you must generate an incident when the RTT is 150 and clear the incident when the RTT value comes down to 100. Set the following values for the threshold: High Value: 150 High Value Rearm: 100 This value enables you to be aware when a network performance problem starts to improve.
   Low Value	Enter the low threshold value. This value indicates the minimum value below which the metric will be considered to have violated the Nominal range.
   Low Value Rearm	Enter the low value rearm for the threshold. For Packet Loss metric, enter the Low Rearm Value in percentage. The low value rearm is used to indicate the end of the low threshold state and NNM iSPI Performance for QA clears the incident once it reaches above this value. The low value rearm must be greater than the low value. Example For the Mean Opinion Score (MOS) you must generate an incident when the MOS score is 3 and clear the incident when the score is improved to 4.5. Set the following values for the threshold: Low Value: 3 Low Value Rearm: 4.5 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 NNM iSPI Performance for QA must alert the operator by transitioning the threshold state to High or Low accordingly.

   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, NNM iSPI Performance for QA 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 NNM iSPI Performance for QA 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 NNM iSPI Performance for QA uses a sliding window. Each time the High Window Duration is reached, NNM iSPI Performance for QA 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, NNM iSPI Performance for QA considers the threshold to be violated if the Packet Loss Percentage is high for 20 out of 30 minutes.

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

   Low Duration

   Designate the minimum time within which the metric value must remain in the Low range. For example if you specify this value to be 20 minutes for MOS metric, NNM iSPI Performance for QA considers the threshold to be violated if the MOS is low for 20 minutes. You define the low threshold value in the Low Value field. The polling interval should be less than or equal to the Low Duration.

   Low Duration Window

   Designate the window of time within which the Low Duration criteria must be met. For example, if you specify this value to be 30 minutes for MOS metric, NNM iSPI Performance for QA considers the threshold to be violated if the MOS is low for 20 out of 30 minutes. To enable this setting, the value must be: greater than 0 (zero) the same as or greater than the Low Duration value The NNM iSPI Performance for QAuses a sliding window. Each time the High Window Duration is reached, NNM iSPI Performance for QA drops the oldest polling interval and adds the most recent.

5. 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. By default this option is selected.

6. 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

7. Click Refresh to view the changes.
8. Click Save or Save and Close in the Threshold Configuration form.

The new threshold is not saved unless you click Save or Save and Close in the Threshold Configuration form.

NNM iSPI Performance for QA applies the following rules when creating thresholds for a site using this form:

• You can create thresholds only for the existing sites.
• You must select a source site and service for the new threshold.
• You could select the destination site for the new threshold
• If you do not specify a destination site for the threshold, the threshold is applied to all the destination sites of the source sites.
• You cannot configure thresholds for remote sites.

Time-Based Threshold cannot be configured for QA probes, if the polling interval is greater than the High Duration or Low Duration value. A list of these QA Probes, the UUID, and other details can be viewed in the log file, which is available in the following directory:

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

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

Add Baseline Settings

To add a new baseline setting configuration:

1. Make sure that you selected the Source Site, and Service in the adding threshold configuration .

2. Click New in the Baseline Settings tab.
   The Add Baseline Settings form opens.

3. Specify the following to configure the baseline deviation settings:

   Field Name	Description
   Metric	Select the metric for which you require to configure baseline deviation settings. The valid metrics for baseline deviation setting configuration are as below: RTT (ms) RTT (microS) Two Way Jitter (microS) Two Way Packet Loss (%) MOS

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

   Field Name	Description
   Upper Baseline Limit Enabled	If enabled, NNM iSPI Performance for QA uses the Upper Baseline Limit attribute value to determine the number of standard deviations above the average that defines the upper baseline limit. If disabled, NNM iSPI Performance for QA does not define the upper baseline limit. This field is not applicable to MOS metric.
   Upper Baseline Limit Deviations - Above Average	Enter the number of standard deviations above the average values that NNM iSPI Performance for QA should use to determine the upper baseline limit. This field is not applicable to MOS metric.
   Lower Baseline Limit Enabled	If enabled, NNM iSPI Performance for QA uses the Lower Baseline Limit attribute value to determine the number of standard deviations below the average that defines the lower baseline limit. If disabled, NNM iSPI Performance for QA does not define the lower baseline limit. This field is applicable to MOS metric only.
   Lower Baseline Limit Deviations - Below Average	Enter the number of standard deviation below the average values that NNM iSPI Performance for QA should use to determine the lower baseline limit. This field is applicable to MOS metric only.
   Duration	The minimum time for which the standard deviation must persist to deviate from the configured Baseline Range before the baseline state transitions to Abnormal Range and generates an incident. The Polling Interval should be less than or equal to the Duration.
   Window Duration	The window duration within which the Upper Baseline Limit or Lower Baseline Limit Deviation criteria must be met. The value must be greater than 0 (zero) and can be the same as the Duration value. The NNM iSPI Performance for QAuses a sliding window. Each time the High Window Duration is reached, NNM iSPI Performance for QA drops the oldest polling interval and adds the most recent.

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

   Icon	Description
   Close	Closes the Add Baseline Settings form without saving the baseline setting information you have entered.
   Save and Close	Saves the baseline setting information and closes the Add Baseline Settings form.

6. Click Save and Close in the Add Baseline Settings form to save the baseline setting information.
7. Click Save or Save and Close in the Threshold Configuration form.

The new baseline settings configuration is not saved unless you click Save or Save and Close in the Threshold Configuration form.

NNM iSPI Performance for QA applies the following rules while configuring baseline deviation settings for a site using this form:

• You can configure baseline settings only for the QA probes of the existing sites.
• You must select a source site, service, and metric to configure the baseline settings.
• Optionally, you can select the destination site
• If you do not specify a destination site for the baseline setting, the configuration is applied to all the QA probes of the destination sites from the source sites.

• You cannot configure baseline settings for remote sites.

Edit Threshold Configuration

To edit a threshold configuration:

1. Launch the Threshold Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > Probes > Sites/QA Group. The Threshold Configuration form opens.

2. Select the threshold configuration settings to modify, and click Edit. 

   The Edit Threshold Configuration form opens.

   When you edit a QA Group threshold configuration setting, NNM iSPI Performance for QA enables you to edit only the metric values, and does not enables you to edit the following fields:

   • Threshold Type
   • Order
   • Source Site
   • Destination Site
   • Service

   If you want to edit the above mentioned fields, delete the existing configuration settings and configure a new threshold setting, based on your requirements.
   

3. Follow the steps given for editing threshold settings to modify the metric values.

   You can view two tabs; Threshold Settings and Baseline Settings.

You can perform the following tasks when you click on the Threshold Settings tab.

Icon	Description
New	Adds threshold settings for the site.
Edit	Edits the selected threshold settings for the site.
Delete	Deletes the selected threshold setting for the site.
Refresh	Retrieves the last saved threshold configuration from the database and displays the data.
Delete All	Deletes all the threshold settings configured for the site.

You can perform the following tasks when you click on the Baseline Settings tab:

Icon	Description
New	Adds baseline deviation settings for the site.
Edit	Edits baseline deviation settings for the site.
Delete	Deletes the selected baseline deviation setting for the site.
Refresh	Retrieves the last saved baseline deviation setting configuration from the database and displays the data.
Delete All	Deletes all the baseline deviation settings configured for the site.

Edit Threshold Settings

To edit an existing threshold setting:

1. Specify all the mandatory fields when editing threshold configuration.

   1. Select the metric, and click Edit in the Threshold Settings tab.

      The Edit Threshold Settings form opens.

      You cannot edit the metric type and threshold type (Time-based or Count-based). If you want to edit the metric type or threshold type (Time-based or Count-based), delete the existing configuration settings and configure a new threshold settings, based on your requirements.

2. You can specify the following values to edit the threshold:

For probe based threshold configuration, you can view the threshold that was configured for the Remote QA probes, but you cannot configure thresholds for remote QA probes.




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 Round Trip Time (RTT) you must generate an incident when the RTT is 150 and clear the incident when the RTT value comes down to 100. Set the following values for the threshold: High Value: 150 High Value Rearm: 100 This value enables you to be aware when a network performance problem starts to improve.
Low Value	Enter the low value.
Low Value Rearm	Enter the low value rearm for the threshold. For Packet Loss metric, enter the Low Rearm Value in percentage. The low value rearm is used to indicate the end of the low threshold state and NNM iSPI Performance for QA clears the incident once it reaches above this value. The low value rearm must be greater than the low value. Example For the Mean Opinion Score (MOS) you must generate an incident when the MOS score is 3 and clear the incident when the score is improved to 4.5. Set the following values for the threshold: Low Value: 3 Low Value Rearm: 4.5 This value enables you to be aware when a network performance problem starts to improve.

The following fields appear, if the Type is Count-Based, and you can modify the information if required

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 or Low accordingly.

The following fields appear if the Type is Time-Based, and you can modify the information if required:

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, NNM iSPI Performance for QA 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 NNM iSPI Performance for QA 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 NNM iSPI Performance for QA uses a sliding window. Each time the High Window Duration is reached, NNM iSPI Performance for QA 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, NNM iSPI Performance for QA considers the threshold to be violated if the Packet Loss Percentage is high for 20 out of 30 minutes.

The following fields appear, if you selected the Type as Time-Based and the metric as MOS:

You can modify the information if required.

Low Duration

Designate the minimum time within which the metric value must remain in the Low range. For example if you specify this value to be 20 minutes for MOS metric, NNM iSPI Performance for QA considers the threshold to be violated if the MOS is low for 20 minutes. You define the low threshold value in the Low Value field. The polling interval should be less than or equal to the Low Duration.

Low Duration Window

Designate the window of time within which the Low Duration criteria must be met. For example, if you specify this value to be 30 minutes for MOS metric, NNM iSPI Performance for QA considers the threshold to be violated if the MOS is low for 20 out of 30 minutes. To enable this setting, the value must be: greater than 0 (zero) the same as or greater than the Low Duration value The NNM iSPI Performance for QAuses a sliding window. Each time the High Window Duration is reached, NNM iSPI Performance for QA drops the oldest polling interval and adds the most recent.

3. 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.

4. 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

5. Click Refresh in the Threshold Settings panel to view the changes.
6. Click Save or Save and Close in the Threshold Configuration form.

The changes you have made in the threshold is not saved unless you click Save or Save and Close in the Threshold Configuration form.

NNM iSPI Performance for QA applies the following rules while updating thresholds:

• You can define thresholds only for the existing sites.
• Any modification in the threshold directly updates the state poller.

Time-Based Threshold cannot be configured for QA probes, if the polling interval is greater than the High Duration or Low Duration value. A list of these QA Probes, the UUID, and other details can be viewed in the log file, which is available in the following directory:

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

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

You can select all the threshold configured settings and click Edit option, but edit form will open for only one threshold group.

Edit Baseline Settings

To edit a baseline setting configuration:

1. Make sure that you selected the Source Site, and Service when editing threshold configuration if you are launching the form from Site Wide threshold configuration. You can ignore this step if you are launching this form from Probe-based threshold configuration.

2. Select the baseline settings, and click Edit in the Baseline Settings panel.

   The Edit Baseline Settings form opens.

3. In the Baseline Deviations Settings panel:

   1. You can view the following details:
      

   Field Name	Description
   Metric	The metric for which you require to edit the baseline deviations settings configuration.

   2. You can edit the following baseline deviation settings configuration:

      The following fields appear depending on the metric:

      Field Name	Description
      Upper Baseline Limit Enabled	If enabled, NNM iSPI Performance for QA uses the Upper Baseline Limit attribute value to determine the number of standard deviations above the average that defines the upper baseline limit. If disabled, NNM iSPI Performance for QA does not define the upper baseline limit. This field is not applicable to MOS metric.
      Upper Baseline Limit Deviations - Above Average	Enter the number of standard deviations above the average values that NNM iSPI Performance for QA should use to determine the upper baseline limit. This field is not applicable to MOS metric.
      Lower Baseline Limit Enabled	If enabled, NNM iSPI Performance for QA uses the Lower Baseline Limit attribute value to determine the number of standard deviations below the average that defines the lower baseline limit. If disabled, NNM iSPI Performance for QA does not define the lower baseline limit. This field is applicable to MOS metric only.
      Lower Baseline Limit Deviations - Below Average	Enter the number of standard deviation below the average values that NNM iSPI Performance for QA should use to determine the lower baseline limit. This field is applicable to MOS metric only.
      Duration	The minimum time for which the standard deviation must persist to deviate from the configured Baseline Range before the baseline state transitions to Abnormal Range and generates an incident. The Polling Interval should be less than or equal to the Duration.
      Window Duration	The window duration within which the Upper Baseline Limit or Lower Baseline Limit Deviation criteria must be met. The value must be greater than 0 (zero) and can be the same as the Duration value. The NNM iSPI Performance for QAuses a sliding window. Each time the High Window Duration is reached, NNM iSPI Performance for QA drops the oldest polling interval and adds the most recent.

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

   Icon	Description
   Close	Closes the Edit Baseline Settings form without saving the baseline setting information you have entered.
   Save and Close	Saves the baseline setting information and closes the Edit Baseline Settings form

5. Click Save and Close in the Edit Baseline Settings form to save the baseline setting information.
   
6. Click Save or Save and Close in the Site Wide Threshold Configuration form.

The new baseline settings configuration is not be saved unless you click Save or Save and Close in the Threshold Configuration form.

NNM iSPI Performance for QA applies the following rules while configuring baseline deviation settings for a site using this form:

• You can configure baseline settings only for the QA probes of the existing sites.
• You must select a source site and service to configure the baseline settings.
• Optionally, you could select the destination site.
• If you do not specify a destination site for the baseline setting, the configuration is applied to all the QA probes of the destination sites from the source sites.
• You cannot configure baseline settings for remote sites.

Delete Thresholds

To delete an existing threshold:

1. Launch the Threshold Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > Probes > Sites/QA Group. The Threshold Configuration form opens.
2. Select a threshold in the Threshold Settings panel and click Delete.
   or
   Click Delete All to delete all thresholds.
3. Click Refresh in the Threshold Settings panel to view the changes.

The following changes occur after deleting a site based threshold configuration:

The selected thresholds configured for the metrics of the site are deleted and the threshold state is set to Threshold Not Set for the metric in the site. If any probe based configuration exists for the metric, the deletion of the site based threshold configuration has no impact on the probe based threshold configuration. The QA Probe status for the probes in the site is set to the most severe status. The incidents and conclusions are updated accordingly.

Example 1  

Consider the following scenario:

Before Deleting the Threshold(s) Configured for the Site:

QA Probe Status : Major

Threshold State: High

The threshold state is high for RTT and Packet Loss

Conclusion: RttThresholdStateHigh, TwoWayPktLossThresholdStateHigh, RTTAbnormal

After Deleting the Threshold(s) Configured for the Site:

QA Probe Status : Major

Threshold State: Threshold Not Set

The threshold state is set to Threshold Not Set for RTT and Packet Loss.

Conclusion: RTTAbnormal

The QA Probe Status for the probes in the site is still set to Major as the Baseline State is in the Abnormal Range.

Example 2  

Consider the following scenario:

Before Deleting the Threshold(s) Configured for the Site:

QA Probe Status : Major

Threshold State: High

Conclusion: TestUp, RttThresholdStateHigh,TwoWayPktLossThresholdStateHigh

Deleting the Threshold(s) Configured for the Site:

QA Probe Status : Normal

Threshold State: Threshold Not Set

Conclusion: TestUp

Export Thresholds

To export the existing threshold configurations to an XML file:

1. Launch the Threshold Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > Probes > Sites/QA Group. The Threshold Configuration form opens.
2. Click Export.

3. Type the file name where you want to export the existing threshold configuration in the user prompt dialog.

   You must type the file name with full path information; for example, C:\temp\threshold_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 threshold configuration using the following command line utility:

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

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

The threshold export utility does not export a threshold unless the threshold is associated with at least one site.

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.

Import Thresholds

To import threshold configurations from an XML file:

1. Launch the Threshold Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Threshold Configuration > Probes > Sites/QA Group. The Threshold Configuration form opens.
2. Click Import.

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

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

4. Click OK in the user prompt dialog.

   If a threshold is already defined and displayed in the Site Wide Threshold Settings 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 <filename>

Windows:%NnmInstallDir%\bin\nmsqathresholdconfigutil.ovpl –u <username> –p <password> –import <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.