Network Virtualization

This section describes how Micro Focus Network Virtualization (NV) integrates with LoadRunner Enterprise to help you test point-to-point performance of network-deployed products under real-world conditions.

Note: Network Virtualization for LoadRunner no longer requires a license, and is provided for free as part of LoadRunner Enterprise. For installation instructions, see the LoadRunner Enterprise Installation Guide.

Network Virtualization overview

By incorporating Network Virtualization into your scenario, you can create more meaningful results by configuring several load generators or groups of Vusers with a unique set of network effects, depending on the route or location.

Example: You could define a location from New York to London and another one from Los Angeles to New York. As a result of this, your scenario performs the test in a more realistic environment that better represents the actual deployment of your application.

Network Virtualization starts and stops automatically as you start and stop the performance test. Network Virtualization monitors are assigned automatically when the performance test run starts and metrics are automatically collected during the performance test run.

You can view the results in the LoadRunner Enterprise graphs or in LoadRunner Analysis. You can also use the NV Insights, a comprehensive network analysis report that provides information about how your application performs over various types of networks (virtual locations). For details, see View the results.

Back to top

Integrate Network Virtualization into a performance test

This section describes how to integrate Network Virtualization into your performance test and how to view the metrics.

  1. Prerequisites

    • Make sure that you have Network Virtualization installed on the LoadRunner Enterprise server, the load generators, and the Controller machine. For details, see the Network Virtualization for LoadRunner Help.

      Note:  

      • The LoadRunner Enterprise setup wizard prompts you to install NV at the conclusion of the installation. If you did not install the NV components as part of the LoadRunner Enterprise installation, you can manually install NV at any time. The installation files are located in the <LRE installation directory>\Additional Components\Network Virtualization folder.

      • You can remotely install or upgrade NV packages on host machines using the Remote Installation feature. For details, see Manage remote installations.
    • Make sure that you have a properly designed performance test. For details, see Define test workloads.

  2. Enable Network Virtualization and choose a virtualization method

    1. From the LoadRunner Enterprise navigation toolbar, click and select Test Management. Select a performance test in the test management tree and click Edit Test.

    2. In the Performance Test Designer window, select the Groups and Workload tab.

    3. Select More > Virtual Location Editor.

    4. In the Virtual Location dialog box, set Virtual Location Mode to On.

    5. In the Virtual Location Mode section, select a virtualization method:

      Per Group

      Use to perform network virtualization per Vuser group. This option enables you to emulate multiple virtual locations on the same load generator. It makes it easier to switch between load generators used in your performance test.

      Select this method to generate the NV Insights report.

      Per Load Generator

      Use to perform network virtualization per load generator, where each machine can only emulate a single location.

  3. Define global settings

    1. Click Common Settings. The Configuration Editor opens, enabling you to apply the settings to all virtual locations that are included in the test.

    2. Set Enable Packet Capture to Yes and define packet capture settings (required for NV Insights report). For details, see the Network Virtualization for LoadRunner Help.

    3. In Exclude these IP's, specify any machines that you may want to exclude from network virtualization for all locations. For details on which machines to exclude, see Exclude machines from Network Virtualization.

    4. Click Finish to close the Configuration Editor.

  4. Add virtual locations

    1. In the Virtual Locations section of the Virtual Location dialog box, click the New Virtual Location button.

    2. Type a location name using the ANSI standard format and click OK. The name of the virtual location is added to the Virtual Locations list.

      Note: You cannot use the following characters: \ / : “ ? ‘ < > | * % ^ , ! { } ( ) ; = #

      You can perform other actions on virtual locations as required:

      Action Description
      Edit virtual location conditions

      Select a virtual location and click to configure or redefine the virtual location. For details, see the Network Virtualization for LoadRunner Help.

      Import virtual locations from other test
      1. Select a virtual location and click Import virtual locations from other test.

      2. Click the Test Set dropdown arrow, and select a performance test in the test management tree from which to import virtual locations.

      3. Click Select a Test in the Virtual Locations Preview section to display the virtual locations available in the test.

      4. Click OK to import the virtual locations.

      Duplicate virtual locations

      Select a virtual location and click Duplicate to duplicate the virtual location.

      Edit name and description Select a virtual location and click Edit name and description to open the Edit Location dialog box, enabling you to redefine the virtual location and description.
      Delete a virtual location Select a virtual location and click Delete to delete the selected virtual location from the Virtual Locations list and any associated groups or load generators.
    3. Click OK to save the settings and close the Virtual Location dialog box. The Virtual Location tab added to the right pane in the Groups and Workload page.

  5. Define the load generator settings

    1. In the Groups pane, select the groups for which you want to define load generators, and click Assign LGs. The Assign Groups to Load Generators dialog box opens.

    2. In the Groups column, select the Vuser groups to use in the test.

    3. In the Load Generators column, select one or more load generators from the Specific or Automatch tabs.

      Note: NV Insights is not supported when using elastic hosts.

      To assign additional automatch load generators, click Add LGs, enter the number of load generators in the adjacent box, and click Add.

      To define settings for automatch load generators, click the Properties link to open the Load Generator Management dialog box. Select the load generators for which you want to define the same settings, and select the location and host attributes. For user interface details, see Load Generator Management dialog box.

    4. After you have selected the load generators to assign to the groups, click Apply Assignment, and then click Close.

  6. Assign virtual locations

    Assign a virtual location according to the virtualization method you selected:

    Per group
    1. Select a group in the Groups pane.

    2. In the Virtual Location tab in the right pane, click Select.

    3. Choose a virtual location for the group and click Assign.

    4. (Optional) Select the NV Insights check box for each group you want to include in the NV Insights report in the performance test.

    5. Repeat for each group in your test.

    NV Insights is available for the following script types: Flex, SAP Web, Siebel Web, TruClient-Web, and Web HTTP/HTML.

    Per load generator

    1. Open the Virtual Location tab in the right pane.

    2. Select a load generator in the Virtual Location tab and click Assign Virtual Location. The Assign Location dialog box opens.

    3. Choose a virtual location for the load generator and click Assign.

    4. Repeat for each load generator.

    You can unassign virtual locations that have been assigned to groups or load generators by selecting the groups or load generators in the Virtual Location tab, and clicking Unassign.

  7. For load generator connected over a firewall - Add monitors manually

    If a load generator is connected over a firewall, add monitors manually using the Monitor Over Firewall component. For details, see Monitor over Firewall (MOFW) in the LoadRunner Professional Help Center.

  8. Run the performance test

    Run the test to check its performance. For more details, see Run performance tests.

    Note if you are using NV Insights:

    • For each group enabled with NV Insights, the script will run 2 additional iterations each with a single Vuser (free of charge). Note that the additional measurements will be included in the analysis reports and usage reports.
    • Clicking the Stop Now button also stops the process from generating the NV Insights report.
  9. View the results

    The following table lists the different options you can use to view network virtualization metrics:

    LoadRunner Enterprise graphs

    Network virtualization metrics are automatically collected, and are available for viewing in real time or after running a performance test from the Performance Test Run page.

    LoadRunner Analysis

    At the conclusion of the performance test, you can use LoadRunner Analysis to view a summary and graphs of the data collected from these monitors during the test run.

    For details, see the Analysis section in the LoadRunner Professional Help Center.

    NV Insights report

    NV Insights is a comprehensive network analysis report that shows you how your application performs over various types of networks (virtual locations).

    To view the NV Insights report:

    1. From the LoadRunner Enterprise navigation toolbar, click and select Test Runs (under Testing).

    2. Select a test run, and click View Results.

    3. Click NV Insights Report to open the NV Insights report. For in-depth descriptions of what the NV Insights report includes, see NV Insights.

    4. To download the NV Insights report, open the Results tab, select NVInsights.zip and click Download.

      Note: If you encounter an error that the file path is too long when extracting a report (because the transaction and/or script name is too long), you can manually download and open the NV Insights report.

    For details, see Manage test runs and results.

Back to top

Considerations for working with NV Insights

Below are considerations you should be aware of when using NV Insights:

  • When scheduling timeslots for running performance tests, make sure to allow additional time (of approximately 15 minutes) for an NV Insights enabled performance test.

  • Your Controller and load generators may require additional disk space for processing the NV Insights results.

  • An NV Insights report is not generated if the test run is deliberately stopped while Vusers are still running.

  • When using NV Insights, the Controller creates hidden Vusers (2 Vusers for each group) in addition to the Vusers defined in the scenario scheduler. If the scenario includes parameters with unique data, make sure that the list of parameter values includes several extra values for the additional Vusers.

  • By default, the Controller automatically allocates a unique block of parameter values for each Vuser in the scenario, and assigns the values to the parameter for each Vuser. When using NV Insights, you need to manually allocate data blocks for the Vusers. Open the Parameter List dialog box from VuGen, under Allocate Vuser values in the Controller, select Allocate x values for each Vuser. Alternatively, use VTS (LoadRunner Virtual Table Server) to set your unique parameters.

  • If your test includes several groups, you may need to increase the time needed to generate the report. Edit <LoadRunner Enterprise Host installation root folder>\config\wlrun7.ini. Under the [General] section, update the value for the NVAnalyticsTimeout parameter. By default, 10 minutes (in seconds).

For details on using the NV Insights report, see NV Insights report in the Network Virtualization for LoadRunner Help.

Back to top

Exclude machines from Network Virtualization

In some situations, you may need to exclude certain machines that may affect the virtualization emulation, from the network virtualization. A typical example is a software update server.

To exclude a machine, you configure the IP Filter settings of your network virtualization software. When you exclude a machine, their network effects will not be included in the network virtualization results.

Which machines should you exclude?

Any machine that if emulated, may affect the results of the actual scenario during its run, (for example, the Controller) should be excluded.

Machines excluded by default
  • MI Listener and proxy server machines.

  • The Diagnostics Commander server.

  • The LoadRunner Enterprise server.

  • A machine running SiteScope (configured to monitor LoadRunner Enterprise servers and hosts).

Situations to consider excluding a machine
  • In a Multi-protocol performance test that includes a web server and a database server; where information from the database server is not required as a part of the performance test. In such a case, you would exclude the database server.

  • Deployment and software upgrade servers.

  • Servers that run and store scripts on a shared network drive.

Back to top

Notes and limitations

This section describes notes and limitations for running Vusers with Network Virtualization. For other issues relating to Network Virtualization, see Network Virtualization.

  • NV Insights is not supported when using elastic hosts.

  • Network Virtualization configured with Load Generator emulation mode is not supported with IP Spoofing.

  • The bandwidth utilization measurement is represented in the graphs only when the bandwidth is configured as Shared Bandwidth. If the bandwidth is configured as Individual Bandwidth, bandwidth utilization data does not appear.

  • You cannot run Network Virtualization while using a Goal-Oriented schedule.

  • The NV Controller (LG or Host) is limited to 100 flows. If a performance test is configured with more than 100 flows per load generator, the test will fail.

    Resolution: See Software Self-solve knowledge base article KM03654067.

  • Installation of the Network Virtualization for Linux package (NV4LG) is partly supported on Ubuntu 16.04 (the last kernel that was tested is 4.4.0-66-generic). It is not currently supported on Ubuntu 18.04, due to NV Driver installation failure.

    • UFT One (GUI) scripts can run with Network Virtualization with Per Load Generator mode only; they cannot run with Per Group mode.

Back to top

See also: