Install Network Virtualization on Windows

To gain access to the Network Virtualization (NV) functionality in either LoadRunner Professional or LoadRunner Enterprise, you must install the required NV components.

Upgrading from a previous version on Windows

If you are upgrading from a LoadRunner Professional or LoadRunner Enterprise version prior to 12.50, you must manually uninstall all Network Virtualization components before running the installer.

Back to top

Installing on Windows

At the end of LoadRunner Professional or LoadRunner Enterprise installation wizards, you are prompted to install Network Virtualization. You can continue with the NV installation, or choose to install manually at a later time, as described in Manual installation on Windows.

Via the installation wizard, you select one of the following installation modes:

  • Typical. Installs with default options.
  • Custom. Enables you to configure several options before installation. For details, see Setup wizard options for Windows.

The following are installed:

NV component name Installed with:
NV for LoadRunner Enterprise

LoadRunner Enterprise Server installation

NV for Controller

LoadRunner full installation

LoadRunner Enterprise Host installation

NV for Load Generator and VuGen

Load Generator (standalone) installation

LoadRunner full installation

LoadRunner Enterprise Host installation

VuGen installation

Back to top

Manual installation on Windows

If you do not install the NV components as part of the LoadRunner Professional or LoadRunner Enterprise installations, you can run the installations manually at any time.

The installation files are located in the following folder:

<LRP or LRE installation package>\Additional Components\Network Virtualization\

Run the installation files, according to your needs:

For this component... You need to install… NV installation file
LoadRunner full installation
  • NV for Controller
  • NV for Load Generator and VuGen
  • <LR/LRE installation package>/Additional Components/Network Virtualization/NV4ControllerSetup.exe
  • <LR/LRE installation package>/Additional Components/Network Virtualization/NV4LGSetup.exe
Load Generator (standalone) NV for Load Generator and VuGen <LR/LRE installation package>/Additional Components/Network Virtualization/NV4LGSetup.exe
VuGen

NV for Load Generator and VuGen

<LR/LRE installation package>/Additional Components/Network Virtualization/NV4LGSetup.exe
LoadRunner Enterprise Server NV for LoadRunner Enterprise <LR/LRE installation package>/Additional Components/Network Virtualization/NV4PCSetup.exe
LoadRunner Enterprise Host
  • NV for Controller
  • NV for Load Generator and VuGen
  • <LR/LRE installation package>/Additional Components/Network Virtualization/NV4ControllerSetup.exe
  • <LR/LRE installation package>/Additional Components/Network Virtualization/NV4LGSetup.exe

Back to top

Setup wizard options for Windows

If you run a custom installation during the setup wizard, or are installing the NV components manually, you can configure several options. Some options are enabled only when installing the first NV component on a machine.

Option NV component
Destination Folder

Enter a location on the file system to install the component or accept the default location.

Default: C:\Program Files\OpenText\NV

Data Folder

Stores temporary internal application data and user data, such as test run results.

Default: C:\ProgramData\OpenText\NV

Server Port

  • On NV for Load Generator: The port is used to retrieve Network Virtualization statistics.

  • On other components: The port is used for internal Network Virtualization communication on the machine.

Default: 8182

Enable Remote Connections

Adds an exception to Windows Firewall. Required for NV for Load Generator.

Back to top

Installation logs

Installation logs are located under C:\Temp\NV_Logs.

Back to top

Troubleshooting

Running a load or performance test with Network Virtualization enabled fails with "failed to set NV secret token".

Cause: The NV secret token fails to update the encoded password in the configuration file during deployment (valid on Windows machines only).

This behavior is usually caused when cloning machines (or VMs) with an NV for Load Generator installed.

Solution: Recreate a new token after deploying an instance from the source images.

  1. Open the command line as administrator.

  2. Run NV for Load Generator and VuGen setup with “template” flag on source image. For example:

    NV4LGSetup.exe /v"TEMPLATE=TRUE"

  3. After the installation has finished and you have customized your source image, shut down the machine, but do not reboot (select "No, I will restart my computer later").

  4. Deploy an instance from your image. A Task Scheduler runs (even with a non-admin user), and recreates a new secret token based on your machine ID.

    A log is created under the folder C:\Program Files\OpenText\NV\lib

For more details, see Software Self-solve knowledge base article KM02889919.

Back to top