I am trying to do IP Spoofing on multiple load generators at diffrent locations and IP Spoofing is working from just one load generator. The main difference between these generators is OS. The one that is working is on WIN 2003 Server and others are on XP (SP3). I have set up all the machines exactly the same way but for some reason spoofing is not working on the XP machines. HP confirmed that spooing is supported XP machines. When I look at the controller logs it seems that users are getting connected to the load balancer with multiple ip's but load balancer log shows they are all coming from single IP (the static IP of the load generator). HP says that it is our network issue (based on the logs I agree with them) but our network team says it's load generator that is not spoofing correctly.
But here is something that caught my eye when I did a small test without IP Spoofing option.
For the generator where spoofing worked:
vuser_init.c(37): t=791ms: Connected socket from 10.100.155.97:9936 to 10.100.157.25:80 in 3 ms
For the all generators where spoofing didn't work:
vuser_init.c(37): t=384ms: Connected socket from 127.0.0.1:2174 to 10.100.157.25:80 in 1 ms.
For some reason even when there is no ip spoofing option the good generator is connecting using the Static IP of the machine 10.100.155.97 but in all the other generators they are getting connected using 127.0.0.1 (localhost).
I am not sure whether this is really what is casuing the Spoofing to fail on these machines, but I tried all the options on these machines like turing off firewalls, running load runner agent as process vs service but nothing seems to work.
Does anybody have an idea on why it is behaving differently even without spoofing enabled for all these machines?
OTOH, if you want to balance your HTTP sessions, you can forcefully tag each of your generators to a specific web server in the form. Again, you need to ensure the load is evenly distributed and supported with the equal number of generators to make it happen.