login vsi company logo login vsi company logo 250x40
header-03.jpg

Forum Announcement

The Login VSI forum has been disabled and now only serves as an archive. If you would like to submit a new support ticket, please send an email to support@loginvsi.com.

Script not started. Latency related?

  • pa_hansson
  • pa_hansson's Avatar Topic Author
18 Apr 2013 13:02 #902

Hi,

We're using LoginVSI to generate traffic over a simulated WAN in order to evaluate the effect of WAN accelerators and Citrix (ICA) in our network.

We're using the Citrix Connector with the target system being a virtual Win 2008 R2 server (lots of processing power and RAM).

We've run into two problems that we need help with;

1. When we increase the latency over the WAN, the time it takes to start the scripts also increases. To the extent that with 10 VSI users and a RTT(Round Trip Time) of 250 ms the tenth users never starts the script. There is never any problem with the users logging in. Target and Launcher setup is also correct, everything works fine if we reduce the latency.

2. When the test stops any user that hasn't logged off hangs for quite a long time (feels like at least a minute) before resuming the script.

Saw a earlier post about changing the GPO for the LoginVSI users to enable the login scripts to run when connected over a slow WAN. So we've enabled that but it doesn't seem to help a lot.

Any help would be much appreciated.

Best Regards
Per-Arne Hansson

Please Log in to join the conversation.

More
23 Apr 2013 20:09 #908

1. Did you already try to increase the auto logoff time in the management console?

What I can imagine is that the simulated WAN can cause some delay for both parts (launching/starting).
You are also saying that when you reduce the WAN latency some do start and others not.

Did you ran a successful test without WAN sim's?

Is the target-host a XenApp/XenDesktop environment?

2. Is VSImax hit in this specific test?

Are you sure there are no 'stuck sessions'?

Regards,

Omar

Please Log in to join the conversation.

  • pa_hansson
  • pa_hansson's Avatar Topic Author
26 Apr 2013 14:40 #916

Hi,

Yes, we have increased the auto logoff timer. Have even tried to turn it off all together. There is never any problem logging on, only starting the script.

When we run the test without the WAN emulator most sessions start correctly. Ran two tests with 25 users again this morning and user 20 failed to start the script in one of the tests.

Target host is a Win2008R2 server with Xenapp 6.0.

We do not hit VSImax in any of the tests.

Not sure what you mean with "stuck-sessions", but we check the server before starting a new tests. There are no old session left at that point.

Best Regards
PA

Please Log in to join the conversation.

More
26 Apr 2013 17:45 #917

Hi PA,

If the problem still occurs (reproducible) I would really like to setup an meeting (gotomeeting) and troubleshoot this together.

Please let me know if this is possible and when this suites you best.

Regards,

Omar

Please Log in to join the conversation.

More
15 May 2013 09:18 #1000

Hi PA,

Login VSI uses standard Windows file share and Windows logon script. These should work even in high latency environments. However, there is a GPO; technet.microsoft.com/en-us/library/cc781031%28v=ws.10%29.aspx
This might explain the behavior that your seeing.

Note; by default the policy is set to a value of 500. This does not change the behavior of the slow link detection as it’s threshold is 500 by default. I suggest setting it to 0 which disables the slow link detection completely.
I also suggest setting the attached computer policy just to be sure.

PS, Customers have been doing Login VSI tests using latencies up to 500ms. See the specific review here: review.techworld.com/networking/3359592/...ed-steelhead-review/

Regards,

Omar.

Attachments:

Please Log in to join the conversation.

  • pa_hansson
  • pa_hansson's Avatar Topic Author
23 May 2013 08:05 #1051

Hi,

Just wanted to report back with the solution to our problem.

Both the launcher/s and the target systems have to access the VSIShare. The problem in our case was that the VSIShare was configured on the launcher and the target was on the other side of the slow WAN-link. So when the number of users and the traffic they generate started to increase over the WAN(with the extra latency added) the target system wasn't able to read the VSIShare, and so the script didn't run.

We have now configured the VSIShare on a different system with two NIC's so that the share is reachable from both launcher and target systems without having to use the WAN-link. The actual LoginVSI user generated traffic is still going over the WAN so we can continue with our tests.

We would like to thank Omar and Dennis from Login VSI for explaining this during a online session yesterday. Great support and we really appreciate it!

Best Regards
PA

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200