This section describes troubleshooting and limitations for running Vusers with Network Virtualization.
- For scenarios created with an earlier version of Network Virtualization (previously known as Shunra NV) such as 8.6, the bandwidth utilization measurement will be represented in the graphs only when the bandwidth is configured as Shared Bandwidth. If the bandwidth is configured as Individual Bandwidth, bandwidth utilization data will not appear.
- If you upgraded from a LoadRunner 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 C:\Program Files (x86)\HPE\NV\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, 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 and Performance Center 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.
- Network Virtualization software integration is not supported for the Linux platform.
- 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