Administer > Administer the NNM iSPI Performance for QA > Configure Discovery Filters

Configure Discovery Filters

You can have numerous probes configured in your entire network, but not all the QA probes are always useful to analyze, monitor, or measure the network performance. You can restrict the discovery to discover and monitor only a required set of probes in your network by using probe discovery filters.

Similarly, you may have numerous QoS elements (policies and classes) configured in your entire network. However, you may not need all of these QoS elements to analyze, monitor, or measure the performances of the business-critical network elements. You can restrict NNMi to discover, and NNM iSPI Performance for QA to monitor only a required set of QoS elements in your network using QoS discovery filters.

As an NNM iSPI Performance for QA administrator, you may want to perform the following tasks:

Configure File-Based Node Discovery

The file based node discovery configuration enables you to configure the NNM iSPI Performance for QA to exclude a set of nodes from being discovered in the network. This configuration setting can also be used to discover and monitor the QA data only for certain set of nodes.

File-Based Node Exclusion

To exclude a set of nodes from being discovered in the network, perform the following steps:

  1. Create a file discovery.exclude at the following location:

    Linux: /var/opt/OV/shared/qa/conf

    Windows: %NnmDataDir%\shared\qa\conf

  2. Update the file with the list of IP addresses of the nodes (one in each line) that you do not want to discover. You can also define an IP address range or use wild card character * (asterisk).
  3. Save and close the file.

  4. Synchronize the configuration by running the following command:

    nmsqadisco.ovpl -resyncConfig

The nodes listed in the discovery.exclude file are ignored and the remaining nodes are discovered.

If an already discovered node is listed in the exclusion filter, the discovery for that node stops but the polling continues for the existing QA data.

If a new node is seeded to the network and is listed in the exclusion filter, it will not be discovered by the NNM iSPI Performance for QA.

File-Based Node Inclusion

To discover a set of nodes in the network, perform the following steps:

  1. Create a file discovery.include at the following location:

    Linux: /var/opt/OV/shared/qa/conf

    Windows: %NnmDataDir%\shared\qa\conf

  2. Update the file with the list of IP addresses of the nodes (one in each line) that you want to discover. You can also define an IP address range or use wild card character * (asterisk).
  3. Save and close the file.

  4. Synchronize the configuration by running the following command:

    nmsqadisco.ovpl -resyncConfig

Only the nodes listed in the discovery.include file are discovered and the remaining nodes are ignored.

If an already discovered node is not listed in the in the discovery.include file, the discovery for that node stops but the polling continues for the existing QA data.

If a new node is seeded to the network and is listed in the inclusion filter, it will be discovered by the NNM iSPI Performance for QA.

If both discovery.exclude and discovery.include files are available, only the nodes listed in the discovery.include file are discovered in the network.

To define an IP address range or to use wild card character, follow the rules given below:

  • You can use "-" (the character hyphen) while defining an IP address range. For example, 192.168.4-9.137
  • Specify the range in ascending order, that is, the range must be from a lower value to a higher value.
  • Use the wild card character "*" to specify IP range between 0 to 255.
  • Addresses like 0.0.0.0 and 127.0.0.1 are considered as invalid.

Configure Probe Discovery Filters

Discovery filter allows you to exclude the QA probes (such as the interface health reporting QA probes) that produce a lot of output, and is not necessary for monitoring the network performance. It enables you to filter the discovery process, and exclude the QA probes based on the following attributes of the QA probe:

  • Owners associated with the QA probes

  • IP addresses of the source or destination device for which the QA probe is configured

  • Service types of the QA probe

If you filter the QA probes based on different attributes, the QA probes are excluded or filtered only if it fulfills all the criteria specified in this user interface. For example, if you specify the filters based on Owners, and Service, the discovery filter ensures that it meets the criteria and excludes only those QA probes.

After you apply the filters, the filtered QA probes are removed from the database. The poller stops polling these QA probes, which get excluded from the QA Probes view.

You cannot apply discovery filters in a Global Network Management environment. The discovery filters applied in the regional manager do not get reflected in the global manager. Similarly, discovery filters applied on the global manager applies only on the data polled by the global manager, and not on the data forwarded by the regional managers.

Add Probe Discovery Filters

To add a new discovery filter, follow the steps given below:

  1. Launch the Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > Probes. The Discovery Filter Configuration form opens.
  2. Select Enable Discovery Filters to activate the discovery filters.

  3. Click New in the Configured Filters panel in the Discovery Filter Configuration form.

    The Add Discovery Filter form opens.

  1. Enter the following:

    1. Name

      A name to identify the discovery filter. The name must not contain ' (single quotation marks).

    2. Type

      Select the type of discovery filter. The valid options are as listed below:

      • Discovery: Select this option to exclude the QA probes discovered in the network.
      • Global Receiver: Select this option to exclude the QA probes received by the global manager. This option appears only for global manager.
      • Regional Data Forwarding: Select this option to exclude the QA probes forwarded to the global manager. This filter is configured in the regional manager.

    1. Owner Names

      Type the QA probe owner name or a pattern suggesting the owner name to be filtered in the Owner Names box.
      You can specify a range of QA probe owner names using the wildcard character ? (to replace one character) and * (to replace multiple characters). This field is case-sensitive.
      Click Add. The new QA probe owner name is added to the list in the Owner Names box.
      You can select a QA probe owner name, and click Delete to remove it from the Owner Names box.
      You can click Delete All to select all the QA probe owner names listed in the Owner Names box and remove them.

    2. Source IP Addresses

      Type the Source IP address or IP address range to be filtered and click Add. You can add IPv4 and IPv6 addresses. If the Source IP Address is not configured, you can enter the Management IP Address.
      Select a Source IP address or IP address range and click Delete to remove it from the Source IP Addresses box.
      You can click Delete All to remove all the IP addresses listed in the Source IP Addresses box.

      Follow the rules given below, when defining an IP address range:
      • For IPv4 addresses, you can use "-" (the character hyphen) when defining a range of IPv4 addresses.
      • Specify the range in the ascending order. The range must be from a lower value to a higher value.
      • For IPv4 addresses, use the wild card character "*" to specify IP addresses between 0 to 255.
      • For both IPv4 and IPv6, specify an IP address range using "-" (hyphen).
      • For both IPv4 and IPv6, specify the IP address range in the ascending order. For example, 16.*.*, 17.1-100.*.*.
      • For IPv4, addresses such as 0.0.0.0 and 127.0.0.1 are considered invalid.

      • For IPv6 addresses, use the standard IPv6 shorthand notation.

    1. Destination IP Addresses
      Type the Destination IP address or IP address range to be filtered and click Add. You can add IPv4 and IPv6 addresses.
      Select an IP address or IP address range and click Delete to remove it from the Destination IP Addresses box.
      You can click Delete All to remove all the addresses listed in the Destination IP Addresses box.

      Follow the rules given below, when defining an IP address range:
      • For IPv4 addresses, you can use "-" (the character hyphen) when defining a range of IPv4 addresses.
      • Specify the range in the ascending order. The range must be from a lower value to a higher value.
      • For IPv4 addresses, use the wild card character "*" to specify IP addresses between 0 to 255.
      • For both IPv4 and IPv6, specify an IP address range using "-" (hyphen).
      • For both IPv4 and IPv6, specify the IP address range in the ascending order. For example, 16.*.*, 17.1-100.*.*.
      • For IPv4, addresses such as 0.0.0.0 and 127.0.0.1 are considered invalid.

      • For IPv6 addresses, use the standard IPv6 shorthand notation.

    1. Service

      Select one or more of the following services to filter and click Add.

      • UDP Echo
      • ICMP Echo
      • UDP
      • TCP Connect
      • VoIP
      • ICMP Jitter
      • HTTP
      • HTTPS
      • DNS
      • Oracle
      • DHCP

      2. The service is added to the list in the Service box.
      Select the service, and click Delete to remove it from the Service box.
      You can click Delete All to remove all the services listed in the box.

      The QA probes are excluded or filtered only if it fulfills all the criteria specified in this user interface. For example, if you specify the filters based on Owners, and Service, the discovery filter ensures that it meets both the criteria and excludes only those QA probes.

  1. You can perform the following tasks:
Icon Description
Close Closes the Discovery Filter Configuration form without saving the filter information you have entered.
Save Saves the new discovery filter information.
Save and Close Saves the discovery filter information and closes the Discovery Filter Configuration form.

You can perform the following tasks in the Discovery Filter Configuration form.:

Icon Description

Enable Discovery Filters

(in the Global Settings Panel )

Selecting this check box enables the filters to be applied for subsequent discoveries.

If this check box is not selected, you will not be able to click on Apply Filter Now.

Clicking the Apply Filter Now applies the discovery filters and deletes the filtered local QA Probes from the database. This functionality is applicable only for local QA probes and Discovery filter type.

The Registration panel provides the following detail about the selected discovery filter:

Attribute Description
Last Modified Date

Date when the selected discovery filter was last modified.

Edit Probe Discovery Filters

To edit a discovery filter:

  1. Launch the Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > Probes. The Discovery Filter Configuration form opens.

  2. Select a filter in the Configured Filters tab, and click Edit.

    The Edit Discovery Filter form opens.

  3. Select Enable Discovery Filters option to activate the discovery filters.

  4. Update the following values as required:

    1. Name

      A unique name to identify the discovery filter. The name must not contain ' (single quotation marks).

    2. Type

      3. Select the type of discovery filter. The valid options are listed below:

      • Discovery: Select this option to exclude the QA probes discovered in the network.

      • Regional Data Forwarding: Select this option to exclude the QA probes forwarded to the global manager.

      • Global Receiver: Select this option to exclude the QA probes received by the global manager. This option appears only for global manager.

    The following fields appear only if you select the type of discovery filter.

    1. Owner Names

      Type the QA probe owner name or a pattern suggesting the owner name to be filtered in the Owner Names box .

      You can specify a range of QA probe owner names using the wildcard character ? (to replace one character) and * (to replace multiple characters). This field is case-sensitive.

      Click Add. The new QA probe owner name is added to the list in the Owner Names box.

      You can select a QA probe owner name, and click to remove it from the Owner Names box.

      You can click Delete All to select all the QA probe owner names listed in the Owner Names box and remove them.

    2. Source IP Addresses

      Type the Source IP address or IP address range to filter and click Add. You can add IPv4 and IPv6 addresses. If the Source IP Address is not configured, you can enter the Management IP Address.
      Select a Source IP address or IP address range and click Delete to remove it from the Source IP Addresses box.
      You can click Delete All to remove all the addresses listed in the Source IP Addresses box.

      Follow the rules given below, when defining a Source IP address range:

      • For IPv4 addresses, you can use "-" (the character hyphen) when defining a range of IPv4 addresses.
      • Specify the range in the ascending order. The range must be from a lower value to a higher value.
      • For IPv4 addresses, use the wild card character "*" to specify IP addresses between 0 to 255.
      • For both IPv4 and IPv6, specify an IP address range using "-" (hyphen).
      • For both IPv4 and IPv6, specify the IP address range in the ascending order. For example, 16.*.*, 17.1-100.*.*.
      • For IPv4, addresses such as 0.0.0.0 and 127.0.0.1 are considered invalid.

      • For IPv6 addresses, use the standard IPv6 shorthand notation.

    3. Destination IP Addresses

      Type the Destination IP address or IP address range to filter and click Add. You can add IPv4 and IPv6 addresses. Select a Destination IP address or IP address range and click Delete to remove it from the Destination IP Addresses box.
      You can click Delete All to remove all the addresses listed in the Destination IP Addresses box.

      Follow the rules given below, when defining an IP address range:

      • For IPv4 addresses, you can use "-" (the character hyphen) when defining a range of IPv4 addresses.
      • Specify the range in the ascending order. The range must be from a lower value to a higher value.
      • For IPv4 addresses, use the wild card character "*" to specify IP addresses between 0 to 255.
      • For both IPv4 and IPv6, specify an IP address range using "-" (hyphen).
      • For both IPv4 and IPv6, specify the IP address range in the ascending order. For example, 16.*.*, 17.1-100.*.*.
      • For IPv4, addresses such as 0.0.0.0 and 127.0.0.1 are considered invalid.
      • For IPv6 addresses, use the standard IPv6 shorthand notation.

    4. Service

      Select one or more of the following services to filter from the drop-down list, and click Add

      • UDP Echo
      • ICMP Echo
      • UDP
      • TCP Connect
      • VoIP
      • ICMP Jitter
      • HTTP
      • HTTPS
      • DNS
      • Oracle
      • DHCP

      The service is added to the list in the Service box.
      Select the service, and click Delete to remove it from the Service box.
      You can click Delete All to remove all the services listed in the box.

      The QA probes are excluded or filtered only if it fulfills all the criteria specified in this user interface. For example, if you specify the filters based on Owners, and Service, the discovery filter ensures that it meets both the criteria and excludes only those QA probes.

  5. You can perform the following tasks:

    Icon Description
    Close Closes the Discovery Filter Configuration form without saving the filter information you have entered.
    Save Saves the new discovery filter information.
    Save and Close Saves the discovery filter information and closes the Discovery Filter Configuration form.

Delete Probe Discovery Filters

To delete an existing discovery filter:

  1. Launch the Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > Probes. The Discovery Filter Configuration form opens.
  2. Select a filter in the Configured Filters panel, and click Delete.
    or
    Click Delete All to delete all the discovery filters.
  3. Click Refresh in the Configured Filters panel to view the changes.

After you delete a discovery filter, the filtered probes are discovered in the next discovery cycle.

Export Probe Discovery Filters

To export the existing discovery filter configurations to an XML file:

  1. Launch the Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > Probes. The Discovery Filter Configuration form opens.
  2. Click Export.

  3. Enter the file name where you want to export the existing discovery filter configuration in the user prompt dialog.

    You must enter the file name with full path information. For example, C:\temp\disco_filter_conf.xml

    If you enter the XML file name without entering the absolute path, by default the file is 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 discovery filter using the following command line utility:

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

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

If the discovery filter 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 Probe Discovery Filters

To import discovery filter configurations from an XML file:

  1. Launch the Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > Probes. The Discovery Filter Configuration form opens.
  2. Click Import.

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

    You must enter the file name with full path information. For example, C:\temp\disco_filter_conf.xml

  4. Click OK.

    If a discovery filter is already defined and displayed in the Discovery Filter Configuration form, the import utility does not import the configuration information for this discovery filter from the XML file.

You can also import discovery filter using the following command line utility:

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

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

If the discovery filter import fails, check the following log files:

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

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

When you import a discovery filter from the previous version of NNM iSPI Performance for QA, the discovery filter name is automatically generated in this version of NNM iSPI Performance for QA.

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

Apply On-Demand Probe Discovery Filter

You can also apply the probe discovery filter using the nmsqadiscofilter.ovpl command:

Usage:

nmsqadiscofilter.ovpl -c [Probe] apply

Parameters

  • -u <username>: Type the NNMi administrator user name.
  • -p <password>: Type the NNMi administrator password.
  • -c [Probe]: Type this parameter to apply the discovery filter for QA probes.

  • -apply: Type this parameter to initiate the discovery filtering on local probes.

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

Configure QoS Discovery Filters

This feature allows you to exclude the QoS elements that may not be required for monitoring the network performance.

The Discovery Filter Configuration enables you to filter the discovery process, and exclude the QoS elements based on the following attributes:

  • QoS Policy Name
  • QoS Class Name
  • IP Range
  • Node Group
  • QoS Action Name

If you filter the QoS elements based on different attributes, the QoS elements are excluded or filtered only if it fulfills all the criteria specified in the discovery filter. For example, if you create a QoS discovery filter called Filter A based on Class Name, and Node Group, the discovery filter ensures that it meets both the criteria and excludes only those QoS elements.

You can also configure discovery filters for the following policy types:

  • A parent policy, that is, a policy that contains references to other policies, known as child policies. You can define discovery filters only on the parent policies. However, NNM iSPI Performance for QA applies the parent policy filters on the classes configured for the child policies too.
  • An independent policy, that is, a policy that does not refer to any other policies.

After creating the filters, NNM iSPI Performance for QA stops polling the filtered QoS interfaces, policies, classes, and actions in the next polling cycle. As a result, the excluded QoS elements get excluded from the related views.

You cannot apply QoS discovery filters in a Global Network Management environment. The QoS discovery filters applied in the regional manager do not get reflected in the global manager. Similarly, the QoS discovery filters applied on the global manager applies only on the data polled by the global manager, and not on the data forwarded by the regional managers.

Add QoS Discovery Filters

To add a new QoS discovery filter:

  1. Launch the QoS Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > QoS. The QoS Discovery Filter Configuration form opens.
  2. Click New in the Configured Filters panel in the QoS Discovery Filter Configuration form.

    The Add QoS Discovery Filter form opens.
  3. Specify the following criteria. The QoS elements are excluded or filtered only if they fulfill all the criteria specified in this form. For example, if you specify the filters based on Policy Name and Node Groups, the discovery filter ensures that it meets both the criteria and excludes only those QoS elements.

    1. QoS Filter Name

      A unique name to identify the QoS discovery filter. The name must not contain ' (single quotation marks) or special characters. This field supports only alphanumeric characters.

    2. Policy Name

      Name of the Policy map for the QoS element that you want to exclude from the next discovery

      After specifying a policy name, click any of the following buttons:

      • Click Add. The policy name is added to the list of policy names.
      • You can select a policy name, and click to remove it from the list of policy names.
      • You can click Delete All to remove all the policy names from the list.

    1. Class

      Name of the class configured for the QoS element that you want to exclude from the next discovery. For example, if you do not want to discover the classmap called ClassDefault, you can use this criteria to stop polling all QoS elements that have this classmap configured.

      After specifying a class name, click any of the following buttons:

      • Click Add to add the class name to the list of class names.
      • You can select a class name, and click to remove it from the list of class names.
      • You can click Delete All to remove all the class names from the list.

    2. Action

      Name of the action configured on the QoS elements that you want to exclude from the next discovery

      After specifying a action, click any of the following buttons:

      • Click Add to add the action to the list of actions.
      • You can select a action, and click to remove it from the list of actions.
      • You can click Delete All to remove all the actions from the list.

    1. IP Range

      The IP address range for the QoS elements that you want to exclude from the next discovery.

      Follow the rules as discussed below, while defining a IP address range:

      • For IPv4 addresses you can use "-" (the character hyphen) while defining a range of IPv4 addresses.
      • Specify the range in ascending order. The range must be from a lower value to a higher value.
      • For IPV4 addresses use the wild card character "*" to specify IP addresses between 0 to 255.
      • For both IPv4 and IPv6, specify an IP address range using "-" (hyphen).
      • For both IPv4 and IPv6, specify the IP address range in ascending order. For example, 16.*.*, 17.1-100.*.*.
      • For IPv4, addresses like 0.0.0.0 and 127.0.0.1 are considered as invalid.
      • For IPv6 addresses use the standard IPv6 shorthand notation.

      After specifying an IP range, click any of the following buttons:

      • Click Add to add the IP range to the list of IP ranges.
      • You can select an IP range, and click to remove it from the list of IP ranges.
      • You can click Delete All to remove all the IP ranges from the list.

    2. Node Group

      The node group name for the QoS elements that you want to exclude from the next discovery

      You must create a QoS node group in NNMi before using the node group for creating a discovery filter.

      After specifying a node group, click any of the following buttons:

      • Click Add to add the node group to the list of node groups.
      • You can select a node group, and click to remove it from the list of node groups.
      • You can click Delete All to remove all the node groups from the list.

    NNM iSPI Performance for QA enables you to use wildcard characters to define a discovery filter criteria.

  4. Click any of the following buttons to complete the task:
Icons Description
Close Closes the QoS Discovery Filter Configuration form without saving the filter information you have entered.
Save Saves the new QoS discovery filter information
Save and Close Saves the QoS discovery filter information and closes the QoS Discovery Filter Configuration form

Click Apply Filter Now in the QoS Discovery Filter Configuration form to apply the discovery filter immediately on the discovered QoS elements. The QoS elements affected by the modified discovery filters are not discovered in the next discovery cycle.

By default NNM iSPI Performance for QA discovers the changes in the discovery filters during each discovery cycle, and applies them on the respective QoS element. Clicking this button applies the following changes to the discovery filter:

  • If you create a new QoS discovery filter
  • If you edit an existing QoS discovery filter to associate it to a new policy, class, action, IP address range, or node group
  • If you delete existing QoS discovery filters

Edit QoS Discovery Filters

To edit a QoS discovery filter:

  1. Launch the QoS Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > QoS. The QoS Discovery Filter Configuration form opens.

  2. Select a filter in the Configured Filters tab in the QoS Discovery Filter Configuration Form, and click Edit.

    The Edit QoS Discovery Filter form opens.

  3. Update the following values as required:

    1. QoS Filter Name

    2. Policy Name

    3. Class

    4. Action

    5. IP Range

    6. Node Group

    For details about these fields, see Adding QoS Discovery Filters.

  4. Use any one of the following options to complete the task:
Icons Description
Close Closes the QoS Discovery Filter Configuration form without saving the filter information you have entered
Save Saves the new QoS discovery filter information
Save and Close Saves the QoS discovery filter information and closes the Discovery Filter Configuration form

Delete QoS Discovery Filters

To delete an existing QoS discovery filter:

  1. Launch the QoS Discovery Filter Configuration form.

    1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
    2. In the Configuration workspace, select Discovery Filters > QoS. The QoS Discovery Filter Configuration form opens.
  2. Select a filter in the Configured Filters panel in the Discovery Filter Configuration Form, and click Delete.
    or
    Click Delete All to delete all the discovery filters.
  3. Click Refresh in the Configured Filters panel to view the changes.

After you delete a QoS discovery filter, the filtered QoS elements are discovered in the next discovery cycle.

To refresh the QoS Policies Inventory view based on the deleted filter immediately, run the discovery process after you delete the discovery filter.

Export QoS Discovery Filters

To export the existing QoS discovery filter configurations to an XML file:

  1. Launch the QoS Discovery Filter Configuration form.

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

  3. In the user prompt dialog, enter the file name where you want to export the existing QoS discovery filter configuration.

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

    If you enter 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 QoS discovery filter using the following command line utility:

Linux: $NnmInstallDir/bin/nmsqadiscofilter.ovpl -u <username> -p <password> -c CBQoS -export <filename>

Windows:%NnmInstallDir%\bin\nmsqadiscofilter.ovpl -u <username> -p <password> -c CBQoS -export <filename>

If the QoS discovery filter 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 QoS Discovery Filters

To import QoS discovery filter configurations from an XML file:

  1. Launch the QoS Discovery Filter Configuration form.

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

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

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

  4. Click OK in the user prompt dialog.

    If a QoS discovery filter is already defined and displayed in the QoS Discovery Filter Configuration form, the import utility does not import the configuration information for this QoS discovery filter from the XML file.

You can also import discovery filter using the following command line utility:

Linux:$NnmInstallDir/bin/nmsqadiscofilter.ovpl -u <username> -p <password> -c CBQoS -import <filename>

Windows:%NnmInstallDir%\bin\nmsqadiscofilter.ovpl -u <username> -p <password> -c CBQoS -import <filename>

If the QoS discovery filter import fails, check the following log files:

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

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

While you import a QoS discovery filter from the previous version of NNM iSPI Performance for QA, the discovery filter name is automatically generated in this version of NNM iSPI Performance for QA.

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

Apply On-Demand QoS Discovery Filter

You can also apply the QoS discovery filter using the nmsqadiscofilter.ovpl command:

Usage:

nmsqadiscofilter.ovpl -c [CBQoS] apply

Parameters

  • -u <username>: Type the NNMi administrator user name.
  • -p <password>: Type the NNMi administrator password.
  • -c [CBQoS]: Type this parameter to apply the discovery filter for QoS elements in your network.

  • -apply: Type this parameter to initiate the discovery filtering on QoS elements.

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

Troubleshoot Discovery Filter Configuration Error Messages

The error log files are available in the following directory:

Linux:./var/opt/OV/log/qa/qa.log

Windows:%NnmdataDir%\log\qa\qa.log

QA probe filtering is not enabled. Please enable it.

Occurs if you have not enabled the Enable Discovery Filters option in the Discovery Filter Configuration form.

Reason and Resolution

Select the Enable Discovery Filters option in the Discovery Filter Configuration form.

Failed to import the discovery filter configuration. Please check the log files.

Occurs if the import file does not exist in the path you entered.

Reason and Resolution

NNM iSPI Performance for QA imports the discovery filter configuration from an XML file. If the file path is not correct, NNM iSPI Performance for QA fails to import the configuration information.

Check any of the following log files:

Linux:./var/opt/OV/log/qa/qa.log

Windows:%NnmdataDir%\log\qa\qa.log

Failed to export the discovery filter configuration. Please check the log files.

Occurs if the export file path that you entered is incorrect.

Reason and Resolution

NNM iSPI Performance for QA exports the discovery filter configuration to an XML file. If the file path is not correct, NNM iSPI Performance for QA fails to export the configuration information.

Check any of the following log files:

Linux:./var/opt/OV/log/qa/qa.log

Windows:%nnmdatadir%\log\qa\qa.log

Invalid QA probe owner name pattern.

Occurs if the Exclude Probe Owner Name Patterns field in the Discovery Filter Configuration form contains any illegal character.

Reason and Resolution

Avoid using '(Single quotation) as a QA probe owner name. NNM iSPI Performance for QA does not accept this character in a QA probe owner name.

Invalid Filter Name

Occurs when you try to save the discovery filter configuration details with an invalid filter name

Reason and Resolution

Avoid using '(Single quotation) in the filter name. NNMi does not accept this character in a filter name.

Service Already Chosen

Occurs when you selected a service from the Service drop down list in the Discovery Filter Configuration form

Reason and Resolution

Do not select the same service again and add to the list.

Send Help Center feedback