1. NetStorm Keywords Concepts
Cavisson System Inc

2. Agenda Keyword Definition Keyword Format
Understanding of Simple Group based FCU scenario
Designing of FCU Scenario
Execution and Monitoring of test
SystemStats and TCPStat Count monitors
Q & A

3. Keyword Definition
Keyword is a set of attributes, which signifies the behavior of NetStorm or Test Scenario.
Syntax and semantics of value(s) depend upon the keyword.
Default values of the keywords are used when a keyword is missing from configuration file.
Most keywords have default values

4. Keyword Format
<Keyword> <value1> <value2> …. <valueN>
For examples:
G_PAGE_THINK_TIME Static1kGrp ALL 0
G_SESSION_PACING Static1kGrp

5. How Keyword Value are taken from different files?
Setting for scenario are taken from the following files in this priority:
Scenario file
All keyword values are first taken from this file
sys/site_keywords.default
All keywords values in this file which are NOT present in the scenario file are taken from this file
include/VendorData.default
All keywords from this file which are NOT present in above files are taken from this file
etc/KeywordDefinition.dat
All keywords from this file which are NOT present in above files are taken from this file. These are default values.

6. Example: >> Scenario will have G_IDLE_MSECS 120000 Scenario file
No G_ IDLE_MSECS
sys/site_keywords.default
G_IDLE_MSECS ALL
include/VendorData.default
etc/KeywordDefinition.dat
G_IDLE_MSECS default value is 60000
>> Scenario will have G_IDLE_MSECS

7. How to verify what value is taken?:
TRXXXX
Sorted_username_scenarioname.conf
Grep G_IDLE_MSECS sorted*
>> Scenario will have G_IDLE_MSECS ALL

8. Keyword Types Keywords are on following types: Schedule Setting
Global Setting
Group Based Settings
Server Mapping
User Profile

9. Schedule Settings – Add Groups
Make sure Schedule Type is ‘Simple’ and Schedule By ‘Group’
Add groups by clicking on add button as per the requirement

10. Schedule Settings Start Phase
Use to give some delay before starting virtual user generations.
Useful if you want to collect monitor data before actual load starts
Options:
Immediate – No delay (Default)
Time mode – Specified delay
Start when Group finishes
After Group + Delay

11. Scenario requirements - Groups
Scenario Type: FCU scenario
Keyword Used
<STYPE FIX_CONCURRENT_USER>
Scenario Groups
Total Users
Number Mode
Two groups with Number as shown
G1 for Script HPDTours –100
G2 for Script static1K –200

12. Scenario requirements - Schedule
Schedule consists of following phases for group G1:
Start phase – IMMEDIATELY
Ramp Up – 10 Min LINEARLY
Stabilization – 0 seconds
Duration – 5 Minutes
Ramp Down – 1 Minutes

13. Scenario requirements - Schedule
Schedule consists of following phases for group G2:
Start phase – 1 Min
Ramp Up – 5 Min LINEARLY
Stabilization – 0 seconds
Duration – 10Minutes
Ramp Down – 2 Minutes

14. SERVER_HOST
SGRP G1 NA Internet 0 hpd_tours 100
SGRP G2 NA Internet 0 static1K 200
SCHEDULE_BY GROUP
SCHEDULE G1 G1RampUp RAMP_UP ALL TIME 00:10:00 LINEARLY
SCHEDULE G2 G1RampUp RAMP_UP ALL TIME 00:05:00 LINEARLY
SCHEDULE G1 G1duration DURATION TIME 00:05:00
SCHEDULE G2 G2duration DURATION TIME 00:10:00
SCHEDULE G1 G1RmpDown RAMP_DOWN ALL TIME 00:01:00 LINEARLY
SCHEDULE G2 G2RmpDown RAMP_DOWN ALL TIME 00:02:00 LINEARLY
SCHEDULE G1 G1start START IMMEDIATELY
SCHEDULE G2 G2start START AFTER TIME 00:01:00
G_KA_PCT ALL 100
MONITOR_PROFILE TCPstatcount

15. Expected Result Start phase G1 will start immediate
G2 will start after 1 minute

16. RampUp Phase Group Name Ramped Up users After 1 min
Ramped Up After 6 min
Ramped Up After10 min G1 10
10+50 G2
200

17. Total Connections
After 1 min total users are in the system are 10 from G1
we are using hpd_tours script in group G1 then only 40 connections will be after 1 min.
After 6 min total users are in the system are 260
From group G1 -60 users, then total connections are 240 due to hpd_tours.
From group G2-200 users, then total connections are 200 due to Static1K.
Then total connections after 6 minutes are 440.
After 10 minute total users are in the system are 300 users
From group G1-100 users, then total connections are 400 due to hpd_tours.
Total connections after 10 minutes are 600.

18. Stabilization Phase
Stabilize 0 second for both the groups.

19. Duration Phase G1 will run for 5 minutes G2 will run for 10 minutes
In Duration phase no. of connections of both group remain fixed until duration time for both group i.e.600 connections
After completing 5 minute, G1 will start RampDown, so established connection going to be decrease and after 10 minute of duration all established connection should be closed.

20. RampDown Phase G1 will be ramped down in 1 minute.

21. Total time taken in the execution of the scenario.
Group Name
Start phase(in min)
Ramp Up(in min)
Stabilize
Duration(in minute)
Ramp Down(in minute)
Total time(in minute) G1 10 5 1 16 G2 2 18
Total time taken in scenario execution = 18 minutes(expected)

22. QA
Q1. What is G_KA_PCT Q2. What is G_NUM_KA Q3. Which file has highest priority in case of keywords.