Configure Sites

NNM iSPI Performance for QA enables you to monitor the network performance of different network elements. Logically grouping the networking devices into sites enables to monitor a similar set of QA probes. This topic includes the following sections:

• Launch the Site Configuration Form
• Add Sites
• Edit Sites
• Delete Sites
• View Sites
• Export Sites
• Import Sites
• Associate Probes with Sites
• Clone (Copy) Site Configurations
• Troubleshoot Site Configuration Error Messages

Example

An enterprise network with branch offices is connected to the head office via WAN links. You can measure the network performances across all the offices and compare the network performance of the head office and the branch offices. This is useful to get an overview of health or performance of the network.

You can configure QA probes between individual nodes or node groups and assign them to the sites. Also, you can configure the threshold for a site using the Threshold Configuration form. The threshold configured for a site is applied to all the QA probes of that site. This procedure takes very less time compared to configuring the threshold for each probe. You can view the measured value of the metrics for a site, which enables you to analyze the site and inter-site performance as well.

In a Global Network Management (GNM) environment, you can configure sites on a global manager or a regional manager. Based on this configuration, sites can be categorized as follows:

• Local Sites: Sites configured in the local NNMi management server are referred to as Local Sites. The local sites are owned by the manager on which it is configured.
• Remote Sites: The sites exported from the regional manager to the global manager are known as Remote Sites.

Whenever you create, edit, or delete a site in the regional manager, the changes are propagated to the global manager. You can export local sites, but you cannot export or delete remote sites. The advantage of exporting sites is that you need not configure the sites again.

The sites configured and exported in the previous version of NNM iSPI Performance for QA can be imported and used in this version as well.

QA Probes Association

QA probes can be associated with either a local site or a remote site. Probes can be categorized as follows:

• Local QA Probes: Local QA probes are QA probes owned by the local manager.
• Remote QA Probes: Remote QA probes are primarily discovered and polled at the regional manager.
  
  

  If a QA probe associated with the remote site matches the local site, the QA probes of the local site overrides the remote site QA probes. In such instances, NNM iSPI Performance for QA overrides the site configuration and not the thresholds configured for the site.

  However, if there is no local site that matches the remote site, the QA probes are associated with the remote site.
  

Example

Consider a network managed in a GNM environment with branch offices 1 and 2 monitored by regional managers R1 and R2 with the global manager as G1. Consider a set of sites configured in R1 and R2, which are exported to G1. The probes obtained from R1 and R2 are consolidated in G1.

If the sites matching the remote probes are configured in G1, the QA probes of G1 override the remote site QA probes. If there is no match, the remote QA probes are available in G1.

Launch the Site Configuration Form

Perform the following steps to launch the site configuration form:

1. Log on to NNMi console using your user name and password.

   You must have administrator privileges.

2. From the workspace navigation panel, select Configuration workspace.

3. Select Quality Assurance Configuration Console.

   The console opens.

4. In the Configuration workspace, select Site (QA Probes).

   The Site Configuration form opens.

5. You can perform the following tasks using the Site Configuration form:

Icon	Description
Close	Closes the Site Configuration form without saving the current configuration.
Save	Saves the current configuration.
Save and Close	Saves the current configuration and closes the Site Configuration form.
Refresh	Retrieves the last saved site configuration from the database and displays the data in the Configured Sites panel of the Site Configuration form.
Recompute Probes Associations	Associates probes with sites.
Export	Exports sites.
Import	Imports sites.
Icons Available in the Global Settings Panel	Description
Enable Site Configuration	Enables to associate the configured sites to the probes.
Icons Available in the Configured Sites Tab	Description
New	Adds a site
Clone	Clones (copies) the selected site
Open	View an existing site
Edit	Edits an existing site
Delete	Deletes the selected site
Refresh	Refreshes the Configured Sites panel and displays the last saved site configurations
Delete All	Deletes all the existing sites.

You can view the following in the Configured Sites panel:

Field Name	Description
Site Name	The name of the site configured.
Regional Manager	The regional manager where the sites are configured.
Order	The ordering number assigned to the site.
Node Group Rule	The node group rule configured for the site.
IP Range Rule	The IP range rule configured for the site.
Probe Name Rule	The probe name rule configured for the site.
VRF Name Rule	The VRF name rule configured for the site.

Add Sites

To add a site, follow the steps given below:

1. Launch the Site Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Sites/QA Groups > Site (QA Probes). The Site Configuration form opens.

2. Click New in the Configured Sites panel.

   The Add Site Configuration form opens.

3. Enter values for the following site rules:

   1. Site Name:

      Enter the name you want to assign to the site.

      Site names are case sensitive. That is SiteA and Sitea are considered two different sites.

      Site names must be unique. Also, it is recommended to use unique site names across the sites in a GNM environment.

      Site names cannot contain ' (single quotation marks).

      When you rename a site, it is identified by the new name.

   2. Order:

   3. A QA probe can be associated with only one source or destination site. Specify an ordering number for the site in this field to resolve conflicts in case a QA probe matches multiple sites. The NNM iSPI Performance for QA associates the QA probe with the site that has the lowest ordering number.

   4. If you do not provide an ordering number for the site, the NNM iSPI Performance for QA assigns default ordering. Default ordering for a site is given the lowest priority.

   5. The QA probe is associated with the site which has the lowest ordering in case the QA probe matches multiple sites.

   6. Example 1

   7. The discovered QA probe name "UDP QA probe from Site A over WAN link to SiteB" is associated with both SiteA and SiteB. The ordering number for SiteA is 1, and the ordering number for SiteB is 2. SiteA is given priority to the QA probe — UDP QA probe from Site A over WAN link to SiteB.

   8. If a QA probe is associated with multiple sites and the ordering is the same for both sites, the weights of the site rules are used to resolve the conflict. The weights are inherent to the site rules.

   9. Example 2

   10. The discovered QA probe name "UDP QA probe from Site A over WAN link to SiteB" is associated with both SiteA and SiteB. The ordering number for both SiteA and SiteB is 1.

   11. However, QA probe "UDP QA probe from Site A over WAN link to SiteB" matches the Node Group rule for SiteA and the QA Probe Name Pattern rule for SiteB. This QA probe is therefore associated with SiteA because the Node Group rule has a higher priority than the QA Probe Name Pattern rule.

   12. If the inherent site rules also match for the conflicting sites, the NNM iSPI Performance for QA uses the last modified time to prioritize the sites. In this case, the QA probe is associated to the most recently configured site.

   13. Node Group:

       Enter the node group that you want to assign to the site.

       You can classify the node groups based on their types, geographic locations etc, when you add them to a site.

       The node group must be discovered by Network Node Manager i Software and must be already present in the NNMi database.

   14. Select an NNMi tenant from the list of tenants created in NNMi.

       NNMi provides a tenant named Default Tenant and assigns each newly discovered node to the Default Tenant and the Security Group attribute value configured for the Default Tenant. As an NNMi administrator, you can create new tenants and security groups. See Configure Tenants and Configuring Security in Network Node Manager i Software Online Help: Help for Administrators.

   15. IP Address Range:

       Type the IP address or IP address range and click Add to associate an IP address or IP address range to the site. The new IP address is added to the list in the IP Address Range box. You can add IPv4 and IPv6 addresses.

       Select an IP address or IP address range and click Delete to remove it from the IP Address Range box.

       You can click Delete All to remove all the addresses listed in the IP Address Range 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.

         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 as invalid.
       • For IPv6 addresses, use the standard IPv6 shorthand notation.

   16. Probe Name Patterns:

       The Probe Name Patterns box lists the QA probes associated with the node group.

       By default, NNM iSPI Performance for QApopulates the Probe Name Patterns box with the QA probe names associated with the node group assigned to the site.

       You can associate a different QA probe with the site. Type the QA probe name patterns and click Add to associate a different group of QA probes to the site. The new QA probe name is added to the list in the Probe Name Patterns box.

       You can specify a range of QA probe names using the wildcard character "?" (to replace one character) and "*" (to replace multiple characters).

       The QA probe name pattern is split into three parts. Follow the rules given below, when specifying a QA probe pattern:

       • If the QA probe name pattern includes both source and destination information, use a delimiter to differentiate them.

         The QA probe pattern must be in the following format:

         <pattern for source of the QA probe>|Delimiter| <pattern for destination of the QA probe>

       • The string on the left hand side of the delimiter is considered as the source information.
       • The string on the right hand side of the delimiter is considered as the destination information.

       Example 1

       QA Probe Name Pattern: SiteA|over|*SiteB

       If you specify the delimiter between two "|" (vertical bar) characters, NNM iSPI Performance for QA considers the QA probe names that contain the word "over". It also considers the following:

       • The source information on the left hand side of the delimiter "over" must contain the string "SiteA".
       • The destination information on the right hand side of the delimiter "over" must contain the string "SiteB" preceding any number of characters.

       If you have two QA probes named "UDP QA probe From SiteA over Provider WAN to SiteB" and "ICMP QA probe From SiteA over Provider WAN to SiteB", NNM iSPI Performance for QA retrieves both QA probe names.

       Example 2

       QA Probe Name Pattern: remote???|to|central*

       This QA probe pattern retrieves QA probe names that match the following criteria:

       • The source information on the left hand side of the delimiter "to" must contain the string "remote", followed by three characters.
       • The destination information on the right hand side of the delimiter "to" must contain the string "central" followed by any number of characters.

       If you have QA probes named "remoteABC to centralHQ", and "remote123 to centralsite, NNMi retrieves both the QA probe names.

       • You cannot include blank spaces in QA probe name pattern, but you must enter the wild card "*" (asterisk) wherever required. See the example below:

       Example 3

       QA Probe Name Pattern: *|to|test_location

       The wildcard "*" must be entered in the source information if you want to leave the source information blank, and you want to retrieve the QA probe names of the destination test_location. In this example, the NNM iSPI Performance for QAdoes not check for the source information, and it retrieves all the probes with the destination test_location. Use this expression if you want to configure a site with all the probes that have test_location as the destination.

       The above expression also retrieves probes that include the term "to" in the probe source name but not do not have their destination set to test_location.

       Select a QA probe name and click Delete to remove it from the Probe Name Patterns box.

       You can click Delete All to select all the QA probes listed in the Probe Name Patterns box and remove them from the Probe Name Patterns box.

   17. VRF Wildcards:
       

   18. If your site is associated with a Virtual Private Network (VPN), NNM iSPI Performance for QA populates the VRF Wildcards box with the available VRF ranges. Make sure that the VRF name is associated with the IP address rule that is defined.

   19. You can associate a different VRF range with the site. Type the VRF range and click Add to associate another VRF range to the site. The new VRF range is added to the list in the VRF Wildcards box.

   20. You can specify a range of VRF using the wildcard character "?" (to replace one character) and "*" (to replace multiple characters).

   21. Select a VRF range and click Delete to remove it from the VRF Wildcards box.

   22. You can click Delete All to remove all the VRF ranges listed in the VRF Wildcards box.

4. You can also perform the following actions:

   Icon	Description
   Close	Closes the Add Site Configuration form without saving the site information you have entered.
   Save	Saves the new site information.
   Save and Close	Saves the site information and closes the Add Site Configuration form.

5. Click Refresh in the Configured Sites panel to view the changes.
6. On the Site Configuration form, click Save.

On the Site Configuration form, select the Enable Site Configuration check box to associate probes with the sites in the next configuration poll.

Edit Sites

To edit an existing site:

1. Launch the Site Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Sites/QA Groups > Site (QA Probes). The Site Configuration form opens.

2. Select a site in the Configured Sites tab and click Edit.

   The Edit Site Configuration form opens.

   From the global manager, you can only view the remote sites and not edit them.

3. Update the following values as required:

1. Site Name:

Enter the name you want to assign to the site.

Site names are case sensitive. That is SiteA and Sitea are considered two different sites.

Site names must be unique. Also, it is recommended to use unique site names across the sites in a GNM environment.

Site names cannot contain ' (single quotation marks).

When you rename a site, it is identified by the new name.

2. Ordering:
   

   A QA probe can be associated with only one source or destination site. Specify an ordering number for the site in this field to resolve conflicts in case a QA probe matches multiple sites. The NNM iSPI Performance for QA associates the QA probe with the site that has the lowest ordering number.

   If you do not provide an ordering number for the site, the NNM iSPI Performance for QA assigns default ordering. Default ordering for a site is given the lowest priority.

   The QA probe is associated with the site which has the lowest ordering in case the QA probe matches multiple sites.

   Example 1

   The discovered QA probe name "UDP QA probe from Site A over WAN link to SiteB" is associated with both SiteA and SiteB. The ordering number for SiteA is 1, and the ordering number for SiteB is 2. SiteA is given priority to the QA probe — UDP QA probe from Site A over WAN link to SiteB.

   If a QA probe is associated with multiple sites and the ordering is the same for both sites, the weights of the site rules are used to resolve the conflict. The weights are inherent to the site rules.

   Example 2

   The discovered QA probe name "UDP QA probe from Site A over WAN link to SiteB" is associated with both SiteA and SiteB. The ordering number for both SiteA and SiteB is 1.

   However, QA probe "UDP QA probe from Site A over WAN link to SiteB" matches the Node Group rule for SiteA and the QA Probe Name Pattern rule for SiteB. This QA probe is therefore associated with SiteA because the Node Group rule has a higher priority than the QA Probe Name Pattern rule.

   If the inherent site rules also match for the conflicting sites, the NNM iSPI Performance for QA uses the last modified time to prioritize the sites. In this case, the QA probe is associated to the most recently configured site.

This field displays "Default" if you have not specified a value for this field while creating the site. By default the NNMi assigns a site the lowest ordering value.

3. Node Group:

   Enter the node group that you want to assign to the site.

   You can classify the node groups based on their types, geographic locations etc, when you add them to a site.

   The node group must be discovered by Network Node Manager i Software and must be already present in the NNMi database.

4. Select an NNMi tenant from the list of tenants created in NNMi.

   NNMi provides a tenant named Default Tenant and assigns each newly discovered node to the Default Tenant and the Security Group attribute value configured for the Default Tenant. As an NNMi administrator, you can create new tenants and security groups.

5. IP Address Range:

   Type the IP address or IP address range and click Add to associate an IP address or IP address range to the site. The new IP address is added to the list in the IP Address Range box. You can add IPv4 and IPv6 addresses.

   Select an IP address or IP address range and click Delete to remove it from the IP Address Range box.

   You can click Delete All to remove all the addresses listed in the IP Address Range 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.

     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 as invalid.
   • For IPv6 addresses, use the standard IPv6 shorthand notation.

6. Probe Name Patterns:
   

   The Probe Name Patterns box lists the QA probes associated with the node group.

   By default, NNM iSPI Performance for QApopulates the Probe Name Patterns box with the QA probe names associated with the node group assigned to the site.

   You can associate a different QA probe with the site. Type the QA probe name patterns and click Add to associate a different group of QA probes to the site. The new QA probe name is added to the list in the Probe Name Patterns box.

   You can specify a range of QA probe names using the wildcard character "?" (to replace one character) and "*" (to replace multiple characters).

   The QA probe name pattern is split into three parts. Follow the rules given below, when specifying a QA probe pattern:

   • If the QA probe name pattern includes both source and destination information, use a delimiter to differentiate them.

     The QA probe pattern must be in the following format:

     <pattern for source of the QA probe>|Delimiter| <pattern for destination of the QA probe>

   • The string on the left hand side of the delimiter is considered as the source information.
   • The string on the right hand side of the delimiter is considered as the destination information.

   Example 1

   QA Probe Name Pattern: SiteA|over|*SiteB

   If you specify the delimiter between two "|" (vertical bar) characters, NNM iSPI Performance for QA considers the QA probe names that contain the word "over". It also considers the following:

   • The source information on the left hand side of the delimiter "over" must contain the string "SiteA".
   • The destination information on the right hand side of the delimiter "over" must contain the string "SiteB" preceding any number of characters.

   If you have two QA probes named "UDP QA probe From SiteA over Provider WAN to SiteB" and "ICMP QA probe From SiteA over Provider WAN to SiteB", NNM iSPI Performance for QA retrieves both QA probe names.

   Example 2

   QA Probe Name Pattern: remote???|to|central*

   This QA probe pattern retrieves QA probe names that match the following criteria:

   • The source information on the left hand side of the delimiter "to" must contain the string "remote", followed by three characters.
   • The destination information on the right hand side of the delimiter "to" must contain the string "central" followed by any number of characters.

   If you have QA probes named "remoteABC to centralHQ", and "remote123 to centralsite, NNMi retrieves both the QA probe names.

   • You cannot include blank spaces in QA probe name pattern, but you must enter the wild card "*" (asterisk) wherever required. See the example below:

   Example 3

   QA Probe Name Pattern: *|to|test_location

   The wildcard "*" must be entered in the source information if you want to leave the source information blank, and you want to retrieve the QA probe names of the destination test_location. In this example, the NNM iSPI Performance for QAdoes not check for the source information, and it retrieves all the probes with the destination test_location. Use this expression if you want to configure a site with all the probes that have test_location as the destination.

   The above expression also retrieves probes that include the term "to" in the probe source name but not do not have their destination set to test_location.

   Select a QA probe name and click Delete to remove it from the Probe Name Patterns box.

   You can click Delete All to select all the QA probes listed in the Probe Name Patterns box and remove them from the Probe Name Patterns box.

7. VRF Wildcards
   

8. If your site is associated with a Virtual Private Network (VPN), NNM iSPI Performance for QA populates the VRF Wildcards box with the available VRF ranges. Make sure that the VRF name is associated with the IP address rule that is defined.

9. You can associate a different VRF range with the site. Type the VRF range and click Add to associate another VRF range to the site. The new VRF range is added to the list in the VRF Wildcards box.

10. You can specify a range of VRF using the wildcard character "?" (to replace one character) and "*" (to replace multiple characters).

11. Select a VRF range and click Delete to remove it from the VRF Wildcards box.

12. You can click Delete All to remove all the VRF ranges listed in the VRF Wildcards box.

4. You can perform the following actions:

   Icons	Description
   Close	Closes the Edit Site Configuration form without saving the site information you have entered.
   Save	Saves the new site information.
   Save and Close	Saves the site information and closes the Edit Site Configuration form.

5. Click Refresh in the Configured Sites panel to view the changes.
6. On the Site Configuration form, click Save.

Delete Sites

To delete an existing site:

1. Launch the Site Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Sites/QA Groups > Site (QA Probes). The Site Configuration form opens.
2. Select a site in the Configured Sites panel and click Delete.
   or
   Click Delete All to delete all the sites.
3. Click Refresh in the Configured Sites panel to view the changes.

The QA probe associations for the site are deleted automatically once you delete a site. You do not need to recompute the QA probe associations after deleting a site.

In a GNM environment, the global manager cannot delete remote sites. The sites deleted at the regional manager are propagated to the global manager. In case, the synchronization takes more time, you can run the following commands to trigger synchronization: 

To synchronize the deletion of sites at regional manager to the global manager:

nmsqasiteconfigutil -synchronize <regional manager name>

To synchronize the deletion of sites at all regional managers to the global manager:

nmsqasiteconfigutil -synchronize all

View Sites

To view a site configuration:

1. Launch the Site Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Sites/QA Groups > Site (QA Probes). The Site Configuration form opens.

2. Select a site in the Configured Sites panel and click Open.

   The View Site Configuration Details form opens.

   You can view the following details:

Field Name	Description
Site Name	The name of the site.
Order	The ordering number for the site. This field displays "Default" if you have not specified a value for this field when creating the site.
Regional Manager	The name of the Regional Manager where the site was configured.
Node Group	The node group assigned to the site.
Tenant	The NNMi tenant name associated with the site.
IP Address Range	The set of IPv4 or IPv6 addresses associated with the site.
Probe Name Pattern	The QA probes or the Probe Name patterns of the QA probes that are associated with the site.
VRF Wildcards	The VRF name associated with the site.

Export Sites

To export the existing site configurations to an XML file:

1. Launch the Site Configuration form.

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

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

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

   If you enter the XML file name without entering the absolute path, by default the file is saved in the following directory of the NNMi management server where NNM iSPI Performance for QA is installed:

   Linux: $NnmDataDir/shared/qa/conf

   Windows : %NnmDataDir%\shared\qa\conf

4. Click OK in the user prompt dialog.

You can also export the existing site configuration using the following command line utility:

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

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

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

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

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

You can export local sites, but you cannot export remote sites.

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

Import Sites

To import site configurations from an XML file:

1. Launch the Site Configuration form.

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

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

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

      You can import the sites configured in the previous version of NNM iSPI Performance for QA as well.

4. Click OK in the user prompt dialog.

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

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

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

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

If the site 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.

Associate Probes with Sites

To associate probes with the new or updated sites, do one of the following:

• On the Site Configuration form, select the Enable Site Configuration check box at the time of creating or updating sites and click Save. Selecting this check box associates probes with the sites in the next configuration poll. If you do not select this check box, sites still get created or updated but probes do not get associated with them.

• On the Site Configuration form, click the Recompute Probes Associations button to associate probes with the new or updated sites immediately.

• Use the following command line utility to associate probes with the new or updated sites immediately:

  • Linux: /opt/OV/bin/nmsqasiteconfigutil.ovpl –u <username> –p <password> –recompute

  • Windows:%NnmInstallDir%\bin\nmsqasiteconfigutil.ovpl –u <username> –p <password> –recompute

    By default, the /opt/OV/bin and %NnmInstallDir% is <drive>:\Program Files(x86)\HP\HP BTO Software\

    If the re-computation does not occur due to an internal error, you can run the following command to reset the internal queue and the gateway flag to allow subsequent probe associations:

    nmsqasiteconfigutil.ovpl -resetrecomputeQ

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

User Scenario

The head office of an organization is connected to its branch office via WAN links. To monitor the network performances of the branch office, a new site is created using the NNM iSPI Performance for QA Site Configuration form. The new site contains the following parameters:

Site Name: SiteA

Order: 1

Node Group: Routers

IP Address Range: 17.1-100.*.*

Probe Name Patterns: *SiteA|to|Central

VRF Wildcards: None

Later, you want to add the following QA probe name patterns to SiteA:

• SiteA???|to|*Central
• SiteA*|over|Central*

Also, you want to add the following VRF groups:

• VRF 1-SiteA
• VRF 2-SiteA

After the site is reconfigured, the QA probes matching the specified QA probe patterns for the node group "Routers" are associated with SiteA in the next configuration poll. Use the Recompute Probes Associations button to associate the QA probes to the new or updated sites immediately.

Clone (Copy) Site Configurations

To clone the existing configuration for a selected site:

1. Launch the Site Configuration form.

   1. Select Configuration workspace > Quality Assurance Configuration Console. The configuration console opens.
   2. In the Configuration workspace, select Sites/QA Groups > Site (QA Probes). The Site Configuration form opens.
2. Select the site you want to copy.

2. Click Clone in the Configured Sites panel.

   The Edit Site Configuration form opens.

3. You can update values for the following site rules:

   1. Site Name:

      Enter the name you want to assign to the site.

      Site names are case sensitive. That is SiteA and Sitea are considered two different sites.

      Site names must be unique. Also, it is recommended to use unique site names across the sites in a GNM environment.

      Site names cannot contain ' (single quotation marks).

      When you rename a site, it is identified by the new name.

   2. Order:

   3. A QA probe can be associated with only one source or destination site. Specify an ordering number for the site in this field to resolve conflicts in case a QA probe matches multiple sites. The NNM iSPI Performance for QA associates the QA probe with the site that has the lowest ordering number.

   4. If you do not provide an ordering number for the site, the NNM iSPI Performance for QA assigns default ordering. Default ordering for a site is given the lowest priority.

   5. The QA probe is associated with the site which has the lowest ordering in case the QA probe matches multiple sites.

   6. Example 1

   7. The discovered QA probe name "UDP QA probe from Site A over WAN link to SiteB" is associated with both SiteA and SiteB. The ordering number for SiteA is 1, and the ordering number for SiteB is 2. SiteA is given priority to the QA probe — UDP QA probe from Site A over WAN link to SiteB.

   8. If a QA probe is associated with multiple sites and the ordering is the same for both sites, the weights of the site rules are used to resolve the conflict. The weights are inherent to the site rules.

   9. Example 2

   10. The discovered QA probe name "UDP QA probe from Site A over WAN link to SiteB" is associated with both SiteA and SiteB. The ordering number for both SiteA and SiteB is 1.

   11. However, QA probe "UDP QA probe from Site A over WAN link to SiteB" matches the Node Group rule for SiteA and the QA Probe Name Pattern rule for SiteB. This QA probe is therefore associated with SiteA because the Node Group rule has a higher priority than the QA Probe Name Pattern rule.

   12. If the inherent site rules also match for the conflicting sites, the NNM iSPI Performance for QA uses the last modified time to prioritize the sites. In this case, the QA probe is associated to the most recently configured site.

   13. Node Group:

       Enter the node group that you want to assign to the site.

       You can classify the node groups based on their types, geographic locations etc, when you add them to a site.

       The node group must be discovered by Network Node Manager i Software and must be already present in the NNMi database.

   14. Select an NNMi tenant from the list of tenants created in NNMi.

       NNMi provides a tenant named Default Tenant and assigns each newly discovered node to the Default Tenant and the Security Group attribute value configured for the Default Tenant. As an NNMi administrator, you can create new tenants and security groups. See Configure Tenants and Configuring Security in Network Node Manager i Software Online Help: Help for Administrators.

   15. IP Address Range:

       Type the IP address or IP address range and click Add to associate an IP address or IP address range to the site. The new IP address is added to the list in the IP Address Range box. You can add IPv4 and IPv6 addresses.

       Select an IP address or IP address range and click Delete to remove it from the IP Address Range box.

       You can click Delete All to remove all the addresses listed in the IP Address Range 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.

         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 as invalid.
       • For IPv6 addresses, use the standard IPv6 shorthand notation.

   16. Probe Name Patterns:

       The Probe Name Patterns box lists the QA probes associated with the node group.

       By default, NNM iSPI Performance for QApopulates the Probe Name Patterns box with the QA probe names associated with the node group assigned to the site.

       You can associate a different QA probe with the site. Type the QA probe name patterns and click Add to associate a different group of QA probes to the site. The new QA probe name is added to the list in the Probe Name Patterns box.

       You can specify a range of QA probe names using the wildcard character "?" (to replace one character) and "*" (to replace multiple characters).

       The QA probe name pattern is split into three parts. Follow the rules given below, when specifying a QA probe pattern:

       • If the QA probe name pattern includes both source and destination information, use a delimiter to differentiate them.

         The QA probe pattern must be in the following format:

         <pattern for source of the QA probe>|Delimiter| <pattern for destination of the QA probe>

       • The string on the left hand side of the delimiter is considered as the source information.
       • The string on the right hand side of the delimiter is considered as the destination information.

       Example 1

       QA Probe Name Pattern: SiteA|over|*SiteB

       If you specify the delimiter between two "|" (vertical bar) characters, NNM iSPI Performance for QA considers the QA probe names that contain the word "over". It also considers the following:

       • The source information on the left hand side of the delimiter "over" must contain the string "SiteA".
       • The destination information on the right hand side of the delimiter "over" must contain the string "SiteB" preceding any number of characters.

       If you have two QA probes named "UDP QA probe From SiteA over Provider WAN to SiteB" and "ICMP QA probe From SiteA over Provider WAN to SiteB", NNM iSPI Performance for QA retrieves both QA probe names.

       Example 2

       QA Probe Name Pattern: remote???|to|central*

       This QA probe pattern retrieves QA probe names that match the following criteria:

       • The source information on the left hand side of the delimiter "to" must contain the string "remote", followed by three characters.
       • The destination information on the right hand side of the delimiter "to" must contain the string "central" followed by any number of characters.

       If you have QA probes named "remoteABC to centralHQ", and "remote123 to centralsite, NNMi retrieves both the QA probe names.

       • You cannot include blank spaces in QA probe name pattern, but you must enter the wild card "*" (asterisk) wherever required. See the example below:

       Example 3

       QA Probe Name Pattern: *|to|test_location

       The wildcard "*" must be entered in the source information if you want to leave the source information blank, and you want to retrieve the QA probe names of the destination test_location. In this example, the NNM iSPI Performance for QAdoes not check for the source information, and it retrieves all the probes with the destination test_location. Use this expression if you want to configure a site with all the probes that have test_location as the destination.

       The above expression also retrieves probes that include the term "to" in the probe source name but not do not have their destination set to test_location.

       Select a QA probe name and click Delete to remove it from the Probe Name Patterns box.

       You can click Delete All to select all the QA probes listed in the Probe Name Patterns box and remove them from the Probe Name Patterns box.

   17. VRF Wildcards:
       

   18. If your site is associated with a Virtual Private Network (VPN), NNM iSPI Performance for QA populates the VRF Wildcards box with the available VRF ranges. Make sure that the VRF name is associated with the IP address rule that is defined.

   19. You can associate a different VRF range with the site. Type the VRF range and click Add to associate another VRF range to the site. The new VRF range is added to the list in the VRF Wildcards box.

   20. You can specify a range of VRF using the wildcard character "?" (to replace one character) and "*" (to replace multiple characters).

   21. Select a VRF range and click Delete to remove it from the VRF Wildcards box.

   22. You can click Delete All to remove all the VRF ranges listed in the VRF Wildcards box.

4. You can perform the following actions::

   Icons	Description
   Close	Closes the Edit Site Configuration form without saving the site information you have entered.
   Save	Saves the new site information.
   Save and Close	Saves the site information and closes the Edit Site Configuration form.

5. Click Refresh in the Configured Sites panel to view the changes.

Troubleshoot Site 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

Failed to create the site. Please check the log files.

May occur for various reasons. Some of the reasons are as follows:

• If a site with the same name already exists. NNMi recognizes a site by its name. Site names must be unique.
• If the IP address range is not valid.
• If the node group you specified does not exist in the NNMi database.

Reason and Resolution

Check any of the following log files:

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

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

 

Invalid Probe Name Pattern

Occurs under any of the following circumstances:

• If the Probe Name Patterns field in the Add Site Configuration form contains any illegal character.
• If the Probe Name Patterns field in the Add Site Configuration form does not contain the delimiter "|" (VERTICAL BAR).

Reason and Resolution

• Avoid using '(SINGLE QUOTE) as a probe name pattern. NNM iSPI Performance for QA does not accept this character in a probe name pattern.
• You must use the delimiter to separate the source information and the destination information for the QA probe name pattern.

 

Order cannot be less than 0.

Occurs when you specify a negative site ordering. For example, -1 (MINUS ONE).

Reason and Resolution

The minimum site ordering accepted is 0 (ZERO).

 

Invalid Site Name

Occurs if the Site Name field in the Add Site Configuration form contains any illegal character.

Reason and Resolution

Avoid using '(SINGLE QUOTE) as a site name. NNM iSPI Performance for QA does not accept this character in a site name.

 

Failed to import the site configuration. Please check the log files.

Occurs under any of the following circumstances:

• If the import file does not exist in the path you entered.
• If a site is already defined and displayed in the Configured Sites panel.

Reason and Resolution

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

Also the import utility does not import the site configuration if the configuration is unchanged since the last import

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 site 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 site 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

 

Site name already exists, cannot add new site

Occurs when you try to save site configurations with a site name that already exists

Reason and Resolution

You must enter a unique name for the site in the Site Configuration form. Site names are unique for a manager or NNMi management server.

 

Invalid Node Group Name cannot add new site

Occurs when you enter an invalid Node Group Name in the Site Configuration form.

Reason and Resolution

Enter a valid node group name

 

Update failed, invalid node group specified

Occurs when you try to save the site details in the Edit Site Configuration form, and you specified an invalid node group

Reason and Resolution

You must enter a valid node group configured in NNMi

 

Unable to write/retrieve data from the server

Occurs due to any exceptions raised while retrieving data from the server

Reason and Resolution

Check any of the following log files:

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

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