Difference between revisions of "Start your first test"

From Login VSI Documentation
Jump to: navigation, search
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Start your first test=
+
This chapter describes the steps to start your first test.
 
 
In this chapter the steps required to start your first test are described.
 
  
 
==Requirements==
 
==Requirements==
Line 20: Line 18:
 
|-
 
|-
 
|
 
|
First we are going to start the Session monitor. The Session Monitor needs to run on the server that is hosting the VSIshare.  
+
First, we are going to start the Session Monitor. The Session Monitor needs to run on the server that is hosting the VSIshare.  
  
Browse to the local VSIshare to the following location: {VSIshare}\_VSI_Binaries\Launcher\
+
Browse to the local VSIshare at the following location: {VSIshare}\_VSI_Binaries\Launcher\
  
 
Start the <nowiki>SessionMonitor.ex</nowiki>e.
 
Start the <nowiki>SessionMonitor.ex</nowiki>e.
Line 36: Line 34:
 
|-
 
|-
 
|
 
|
Click on start to start the session monitor
+
To start the Session Monitor, click the Start button.
  
 
|
 
|
Line 43: Line 41:
 
|-
 
|-
 
|
 
|
Start the Login VSI Management Console
+
Now open the Login VSI Management Console.
  
  
Line 52: Line 50:
 
|-
 
|-
 
|
 
|
Click on 6. Start Test
+
Click 6. Start Test.
  
 
|
 
|
Line 59: Line 57:
 
|-
 
|-
 
|
 
|
This page will contain an overview of the current configured settings.
+
This page contains an overview of the current configured settings.
  
Click in the top right corner start test.
+
Click start test, in the top right corner.
  
 
|
 
|
Line 68: Line 66:
 
|-
 
|-
 
|
 
|
Click next.
+
This opens the start test wizard, click next.
  
 
|
 
|
Line 75: Line 73:
 
|-
 
|-
 
|
 
|
To automatically logoff all sessions mark the Logoff sessions when all session have been launched. By default 120 seconds is configured.
+
 
 +
(If using version 4.1.24 then skip to next step)
 +
<br>
 +
 
 +
To automatically logoff all sessions when they have been launched, mark the Logoff users checkbox. By default, 120 seconds is configured.
  
 
Click next.
 
Click next.
Line 82: Line 84:
  
 
[[File:2013-11-04 01 49 18-Start Test Wizard.png|400px|thumb]]
 
[[File:2013-11-04 01 49 18-Start Test Wizard.png|400px|thumb]]
 +
 +
 +
|-
 +
|
 +
Login VSI now includes upgrades for SOAK testing that improve the overall stability during long-term testing. SOAK testing now runs faster than before, does not run out of memory during large scale data tests, and can be run continuously if required. This type of test can help identify issues relating to memory allocation/leaks, log file handles, storage problems and database resource utilization.
 +
 +
If you want to run a SOAK test to evaluate your system's long-term stability, you can define how long the test should run in the start test wizard. If you want to run a test continuously, please set the toggle to 0. We also advise disabling (unchecking) certain charts in the Analyzer Preferences that are not required when running a SOAK test. 
 +
 +
[https://www.loginvsi.com/documentation/index.php?title=Login_VSI_Analyzing_Results#Analyzer_preferences_.E2.80.93_Analyzer_Tabs Login VSI Analyzing Results - Analyzer preferences - Analyzer tabs]
 +
|
 +
[[File:soak_test_mmc_wizard_verbiage_update.png|400px|thumb]]
 +
 +
 
|-
 
|-
 
|
 
|
Provide a name for the first test.
+
Enter a name for the first test.
  
 
Click next.
 
Click next.
Line 121: Line 136:
 
|-
 
|-
 
|
 
|
Click on next.
+
Click next.
  
 
|
 
|
Line 143: Line 158:
 
|-
 
|-
 
|
 
|
When the launcher <nowiki>agent.ex</nowiki>e is running he will inform the Management Console that he is ready.
+
When the launcher <nowiki>agent.ex</nowiki>e is running, it will inform the Management Console when ready.
  
 
|
 
|
Line 150: Line 165:
 
|-
 
|-
 
|
 
|
The launcher will give the status ready.
+
The launcher will give the status: ready.
  
Click on next.
+
Click next.
  
  
Line 161: Line 176:
  
 
[[File:2013-11-04 01 50 54-Start Test Wizard.png|400px|thumb]]
 
[[File:2013-11-04 01 50 54-Start Test Wizard.png|400px|thumb]]
 +
 +
|-
 +
|
 +
If you have configured the VMware ESXtop performance logs in the MMC, then you will see the status of your VMware server connection here.
 +
<br>
 +
[https://www.loginvsi.com/documentation/index.php?title=Configuration_of_the_MMC#ESXtop_integration_and_configuration_.28ver4.1.24.2B.29 ESXtop integration and configuration]
 +
|
 +
[[file:Esxtop_server_connect_starttestwizard.png|400px]]
 
|-
 
|-
 
|
 
|
Click on finish
+
Click finish.
  
 
|
 
|
Line 179: Line 202:
 
The dashboard will open automatically and will provide you the information of current test.
 
The dashboard will open automatically and will provide you the information of current test.
  
For a detailed overview of the dashboard please see chapter ….
+
 
 +
(Login VSI ver4.1.24+)
 +
<br>
 +
The Login VSI dashboard now includes more information on how many active sessions are being run per launcher. When a test is running, there is now an extra column in the Launchers section, called active sessions, which contains this detailed information.  
 +
 
  
 
|
 
|
  
[[File:Dashboard info.png|400px|thumb]]
+
[[File:test_inprogress_dashboard_launchers.png|400px|thumb]]
 
|}
 
|}
  
Line 214: Line 241:
 
==LoginVSI Dashboard==
 
==LoginVSI Dashboard==
  
The dashboard will always display the information you need for a test. It will tell you how many users have launcher, how many have run the logon script and become active, and how many have successfully ended their portion of the test and logged off. You will want the Launched and Active numbers to be close in number, as the logon rate and the active rate should be close. The last part is the Logoff number. You will want this bar to be completely full and the number to be the same as the Launched and the Active numbers. The logon timer will have a graph that will show how fast the users are becoming active. If you see erratic spikes, it could indicate issues with logging users on. There there are errors that appear, whither it be on the launcher machine or the test machines, there will be screenshots. Clicking on the screenshots can help resolve what the issue with the test was.  
+
The dashboard will always display the information you need for a test. It will tell you how many users have launcher, how many have run the logon script and become active, and how many have successfully ended their portion of the test and logged off. You will want the Launched and Active numbers to be close in number, as the logon rate and the active rate should be close. The last part is the Logoff number. You will want this bar to be completely full and the number to be the same as the Launched and the Active numbers. The logon timer will have a graph that will show how fast the users are becoming active. If you see erratic spikes, it could indicate issues with logging users on. If there are errors that appear, whether it be on the launcher machine or the test machines, there will be screenshots. Clicking on the screenshots can help resolve what the issue with the test was.
 
 
[[File:Dashboard]]
 

Latest revision as of 16:01, 9 May 2017

This chapter describes the steps to start your first test.

Requirements

  • VSIshare
  • Login VSI Management Console
  • At least 1 launcher

Steps

Description

Screenshot

First, we are going to start the Session Monitor. The Session Monitor needs to run on the server that is hosting the VSIshare.

Browse to the local VSIshare at the following location: {VSIshare}\_VSI_Binaries\Launcher\

Start the SessionMonitor.exe.

2013-11-04 01 45 31-Launcher.png

To start the Session Monitor, click the Start button.

2013-11-04 01 45 34-Login VSI Session Monitor.png

Now open the Login VSI Management Console.



Click 6. Start Test.

2013-11-04 01 47 01-Login VSI Management Console 4.0.7.162 - Express.png

This page contains an overview of the current configured settings.

Click start test, in the top right corner.

2013-11-04 01 48 59-Login VSI Management Console 4.0.7.162 - Express.png

This opens the start test wizard, click next.

2013-11-04 01 49 10-Start Test Wizard.png

(If using version 4.1.24 then skip to next step)

To automatically logoff all sessions when they have been launched, mark the Logoff users checkbox. By default, 120 seconds is configured.

Click next.

2013-11-04 01 49 18-Start Test Wizard.png


Login VSI now includes upgrades for SOAK testing that improve the overall stability during long-term testing. SOAK testing now runs faster than before, does not run out of memory during large scale data tests, and can be run continuously if required. This type of test can help identify issues relating to memory allocation/leaks, log file handles, storage problems and database resource utilization.

If you want to run a SOAK test to evaluate your system's long-term stability, you can define how long the test should run in the start test wizard. If you want to run a test continuously, please set the toggle to 0. We also advise disabling (unchecking) certain charts in the Analyzer Preferences that are not required when running a SOAK test.

Login VSI Analyzing Results - Analyzer preferences - Analyzer tabs

Soak test mmc wizard verbiage update.png


Enter a name for the first test.

Click next.

2013-11-04 01 49 30-Start Test Wizard.png

Mark the checkbox Use launcher workflow.

Enter the Launcher username: Launcher-v4

Enter the Launcher password: Password!

Click next.


This feature is only available in Login VSI PRO, express users can skip this step.

2013-11-04 01 50 07-Start Test Wizard.png

Click next.


This feature is only available in Login VSI PRO, express users can skip this step.

2013-11-04 01 50 13-Start Test Wizard.png

Click next.

2013-11-04 01 50 16-Start Test Wizard.png

The launcher workflow will launch a RDP connection to the launcher.


The automatic agent start feature (launcher workflow) is only available in Login VSI PRO, express users have to make sure that \\server\VSIshare\_VSI_binaries\Launcher\Agent.exe is running at the Launcher machine.



2013-11-04 01 51 19-Launcher.png

When the launcher agent.exe is running, it will inform the Management Console when ready.

VSI Launcher version agent.png

The launcher will give the status: ready.

Click next.


Make sure the launcher is added by either Host name, FQDN, and IP address.

2013-11-04 01 50 54-Start Test Wizard.png

If you have configured the VMware ESXtop performance logs in the MMC, then you will see the status of your VMware server connection here.
ESXtop integration and configuration

Esxtop server connect starttestwizard.png

Click finish.

2013-11-04 01 51 25-Start Test Wizard.png

The launcher will start the connections to the target.

Connection to target.png

The dashboard will open automatically and will provide you the information of current test.


(Login VSI ver4.1.24+)
The Login VSI dashboard now includes more information on how many active sessions are being run per launcher. When a test is running, there is now an extra column in the Launchers section, called active sessions, which contains this detailed information.


Test inprogress dashboard launchers.png

Finishing your first test

Steps

Description

Screenshot

The Dashboard will indicate when a test is finished. On the bottom the message “The test is finished, please click “reload” to reload this page.”

For more information about the LoginVSI dashboard and what each part means, please scroll below.

Dashboard updated new.png


LoginVSI Dashboard

The dashboard will always display the information you need for a test. It will tell you how many users have launcher, how many have run the logon script and become active, and how many have successfully ended their portion of the test and logged off. You will want the Launched and Active numbers to be close in number, as the logon rate and the active rate should be close. The last part is the Logoff number. You will want this bar to be completely full and the number to be the same as the Launched and the Active numbers. The logon timer will have a graph that will show how fast the users are becoming active. If you see erratic spikes, it could indicate issues with logging users on. If there are errors that appear, whether it be on the launcher machine or the test machines, there will be screenshots. Clicking on the screenshots can help resolve what the issue with the test was.