This section describes troubleshooting and limitations for running Vusers with Network Virtualization.
When installing the Network Virtualization driver on Windows Server 2008 R2 or Windows 7 SP1, and network adapters are configured as Teaming (also known as LBFO), the NV Agent crashes and the active adapter cannot be set.
Resolution: See this knowledge base article: Unable to retrieve Network Virtualization Active Adapter
- 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.
- If you upgraded from a LoadRunner Professional version with no Network Virtualization installed, to the current version with Network Virtualization installed and enabled, you will not see the virtual locations needed to work with Network Virtualization.
To enable this feature, do the following:
Click the highlighted globe Show Virtual Locations Settings on the Controller toolbar.
In the Virtual Locations Setting dialog box, select the Enable Network Virtualization check box, choose Per Group, and click OK.
In the Virtual Location column, where it says none for the virtual location, open the dropdown list and click Browse. A window without locations opens.
Browse to <LoadRunner root>\Network Virtualization\DefaultLocations\ and select DefaultLocations.xml.
You can now see the virtual locations, and can apply them to the scenario.
Note: Once you add a virtual location, and you have modified the .lrs file; make a backup of the file if you want to keep the original.
For very large tests, the report generation time may be slow.
- If the Network Virtualization service is restarted during a scenario run, the network virtualization may fail. Check the service and restart the scenario run. For Network Virtualization specific limitations and system requirements, see the Network Virtualization for LoadRunner Help (select the relevant version).
- Monitoring over a firewall is not supported for scenarios with network virtualization.
If WinInet replay is enabled in the runtime settings for a web Vuser (Replay > Runtime Settings > Internet Protocol > Preferences > Advanced), you must run the Vuser in per Load Generator mode when using Network Virtualization—running in per Group mode will cause the script to fail.
- Network Virtualization integration does not comply with all of the accepted Internationalization (I18N) conventions.
- The Network Virtualization software may consume large amounts of memory, since the technology delays traffic and captures traffic for later analysis. To verify that the load generator machine has sufficient memory, compare the load generator memory consumption with and without the virtualization.
When running scenarios with virtual locations, Vusers must communicate with the application servers over IPv4. Network Virtualization emulation is not supported for IPv6 network traffic.
- You cannot run a scenario on the same load generator from two different Controller machines, if they both have Network Virtualization enabled.
- Locations names cannot contain non-English characters.
In Windows 7, if the number of open filters is exceeded, the Network Virtualization setup may fail. Solution: Increase the value of the registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters
- Network Virtualization configured with load generator emulation mode is not supported with IP Spoofing.
A scenario is limited to 100 Network Virtualization emulation flows per load generator. If a scenario is configured with more than 100 flows per load generator, the test will fail. For more information, see this knowledge base article: Network Virtualization: The license for this feature has a limit of 100 flows
Resolution: Add load generators as needed, so that there will not be more that 100 flows on each load generator.