When a host is highlighted in the Load Generators group box, the Load Generators settings dialog is displayed either with:
In the Load Generators settings dialog box, the Network tab shows the following information:
Defining several IP addresses allows the user to test applications that use a load balancer based on IP addresses. In this case, a random IP address is assigned to each Virtual User. The IP addresses must be available, i.e. not used by other machines within the network. It is necessary to check with a system administrator to make sure these addresses may be used.
To define IP addresses in the list, it is necessary to define additional IP addresses in the Load Generator operating system settings.
These parameters will modify the Load Generator network settings. It is advised to check this with a system administrator before changing the host settings. In some documentation, multiple IP address settings are referred to as virtual IP settings.
ifconfigcommand to add a new IP address.
For example, the command line for adding 2 new IP addresses (say, 192.168.1.10 and 192.168.1.11) to the eth0 network interface would be:
ifconfig eth0:0 192.168.1.10
ifconfig eth0:1 192.168.1.11
In the Advanced Host Configuration dialog box, the Load Balancing tab allows setting the number of Virtual Users on the Load Generators.
The Virtual Users used in the test are spread among all the available Load Generators. All the Load Generators generate the same number of Virtual Users by default.
Increasing the load factor proportionally increases the number of Virtual Users created by each Load Generator. For example, where NeoLoad needs to creates five more Virtual Users and Load Generator A has a load factor of "3" and Load Generator B a load factor of "2", A will create three Virtual Users and B will create two. The more powerful machines may be configured to create a greater number of Virtual Users.
In the Advanced Host Configuration dialog box, the Information tab allows updating Load Generators.
A NeoLoad Controller can automatically update obsolete Load Generators (orange indicator in the list). This is particularly useful after a Controller update.
When the test is launched, NeoLoad checks the versions of the Load Generators being used and prompts the user to update those that are obsolete. Once the Load Generators have been updated, the test continues as normal.
A Controller cannot update a Load Generator handled by a different Controller or launched in Terminal Services mode. In this case, a manual update needs be performed using the standard installer.
When the Load Generator Agent has been started in non-privileged mode and does not have privileges required to update the program, then the Load Generator cannot be updated automatically. In this case, restart that agent in administrator mode or perform a manual update using the standard installer.