Creating Setup for NetCloud

User needs to follow the below mentioned steps for creating setup for NetCloud:

To make target machines as Generators, make an entry in /etc/.netcloud/generators.dat

Syntax:

GeneratorName|IP|CaMonAgentPort|Location|Work|Type|ControllerIp|ControllerName|ControllerWork|Team|
NameServer|DataCenter|Future1|Future2|Future3|Future4|Future5|Future6|Future7|Comments

Example:

VP-E-FL-Dallas-RDP-15|10.10.30.15|7891|Loc1|/home/cavisson/work|Internal|10.10.30.13|work|/home/cavisson/work|NS|NA|NA|NA|NA|NA|NA|NA|NA|NA|NA

Login to NetCloud

  1. Open the web browser, type the following address in the address bar, and press ENTER. http://<hostname>/netcloud. The NetCloud login window is displayed.

2

  1. Enter the Username and Password and click Login. This displays the NetCloud Home page.

The product home page consists of a left pane and a right pane. The left pane contains a menu from where the user can view details on test runs, scenarios, monitors, and various other sections. Using the menu, users can access further sections of the web dashboard and can perform various operations, such as compare test runs, generate reports, access various features of the web dashboard, and so on. In the right pane, a summary of the important aspects is displayed, be it a release version, CPU usage, memory utilization, or alerts generated in the system.

Left Pane:

It contains the following menu represented with icons:

View

  • Dashboard: This displays the current Dashboard.
  • Test Runs: Shows the test runs window.
  • Scripts: To launch script manager and create a script.
  • Scenarios: To create scenarios.
  • Run Time Progress: This shows the run time progress of the test. This is only available when the test is running currently.
  • Virtual User Trace: This is used for tracing the users for different group(s).
  • Transactions: This displays detailing of all transaction(s) in current test run.
  • System Logs: To view system related logs, such as Kubernetes logs, RBU access logs, peripheral device logs, and system events.  
  • Logs
    • Test Output: This shows the test output in browser as well as on panel.
    • Debug Trace Log: This displays debug trace logs if Debug feature is enabled in scenario.
    • Pause Resume Log: This is used to pause or resume logs (if any).
  • Application Health: This shows a snapshot / summary of application health in terms of heap memory, CPU utilization, available memory, disk space utilization, and so on.
  • Application End to End View: To view end to end monitoring approach.
  • Geo Map: To view Geo map.
  • DB Monitoring: This is a powerful feature to measure the performance of each query contributing in a session execution. It provides complete monitoring of MSSQL queries with insights into SQL activity, wait statistics, databases, support services, Temp DB, and high availability. It enables a user to detect such queries, which are consuming more resources as compare to normal ones. Once identified, user can diagnose the issue and perform corrective measures.
  • Generator Information: To view the detailed information regarding various generators.

Analytics

  • Compare: This feature is used to compare two test runs. User can perform further actions for post compare operation:
    • Enable Compare: To apply the comparison.
    • Disable Compare: To disable the comparison applied and back to original form.
    • Update Compare: To update the inputs provided for comparison.
    • Scenario Difference: This displays scenario difference between current and baseline test run.
    • Script Difference:  This displays script difference between current and baseline test run.
    • Server Signature Difference: This displays server signature used in current test.
  • Derived Metrics: This feature is used to create a derived graph from two or more graphs.

Favorites: Favorite allows a user to save current view of Real Time Graphs (RTG). User can create a new profile by saving current view of RTG UI as a profile. If user wants to see current view of graphs next time in Web Dashboard, then user needs to add graphs in favorite. When user loads saved favorite, then all graphs of favorite are displayed in Web dashboard’s graph panel.

Alerts

  • Alert Maintenance Window: This window provides alert maintenance configuration to disable generation of alerts at the time of maintenance or server goes down.
  • Alert Settings: This is used to enable/disable alert configuration, such as alert mail, capacity/ behavior alert, and thread dump.
  • Baseline: In case of behavior alert, alerts are generated based on trends and trends are defined in baseline.
  • Alert Policy: This is used to create policy for specified condition and rules.
  • Alert Actions: This is used to create actions, such as alert mail, thread dump, and TCP dump.
  • Rules: This is used to activate/deactivate/add/delete/update rules.
  • Active Alerts: This is used to see generated alerts, such as capacity and behavior alerts.
  • Alert History: This is used to see the alerts generated in the past.
  • Active Alert Graphs: This is used to generate graphs for active alerts.
  • Alert Stats Report: This is used to generate stats report for alerts.
  • Alert Action History: It contains details of action taken by alerts, such as SNMP Trap Sent / Email Sent / Cisco Spark Chat sent and so on.
  • System Status: The status of all the tiers and their related servers is displayed. It also displays how many instances are connected with each server. The status of tiers/server/instances are categorized into critical, major, and normal state, which is represented by red, orange, and green color respectively.

Configuration

  • Monitors: To configure the monitors.
  • Topology: To configure topology.
  • Batch Jobs: To configure batch group and batch jobs.
  • Tier Group: To configure tier group list.
  • Agent Config: For ND agent configuration.
  • Configuration Settings: For various settings, such as dashboard settings, multi-node configuration, show vector in title, and graph tree.
  • Color Management: It is used to define the color of the graphs.
  • Manage Catalogue: It provides a common platform for the selection of graphs and storing them as a catalogue.

Reports: Reports menu is used to create various types of reports, such as stat report, compare/trend report, hierarchical report, and so on. These reports are generated using templates and have other advanced options to include all or selected metrics. The reporting format may be selected as Word, HTML or Excel. It includes tabular data with or without graphical illustration.

Actions

  • Thread Dump: To take thread dump, analyse thread dump, and schedule thread dump.
  • Heap Dump: A heap dump is a dump of the state of the Java heap memory. This is useful for analysing the use of memory i.e.an application is making at some point in time so handy in diagnosing some memory issues, and if done at intervals handy in diagnosing memory leaks. User can take heap dump from here.
  • Process Dump: To take process dump.
  • TCP Dump: This option is used to take the TCP dump.
  • Mission Control: It is a property through which user can get thread JVM information for JRocket. This includes two features – Memory Analyzer and Flight Recorder.
  • Java Flight Recording: To view all java flight recordings
  • Run command: This is used to run command on server.
  • Download File: To download a file from the system.
  • Import data from Access Log file: This imports data from access log file.
  • Update:
    • Update User/Session Rate: This updates user/session rate (Online mode only).
    • Update Data File: To update data file, it is supported in online mode only.
    • Update Running Scenario: To update running scenario (in online mode only).
  • Manage Vusers: To manage Vusers, such as start, stop, pause, and so on.
  • Running Generator Information: To view the detailed information regarding running generators.

Admin

  • Projects: Displays the Project Administration window to add, delete, rename a project / sub-project.
  • LDAP Server Settings: To configure LDAP Server settings.
  • Servers: DisplaysServer Administration window to configure a server.
  • Settings: To configure module tab settings.
  • Manage Controllers: To manage controller with details, such as appliance name, controller name, controller URL, and Service End point IP.
  • GIT Settings: To perform GIT Remote Server settings.
  • Retention Policy: To configure the data retention / data backup policy (NDE Purge)
  • Access Control: To perform identification, authentication and accountability of entities through login credentials including passwords.
  • Agent Info: To view machine agent status and application agent status.
  • NetHavoc: A feature to implement resilience testing.
  • Generator Management: The user can view all the information about the generators and perform various actions from the UI.

Advanced

  • Automation: This constitutes Test Suite, Test case, and Test Reports.
    • Test Suite: Test Suite is the NetCloud entity to control the execution of tests together with the comparison of actual outcome to the predicted outcome (SLA).
    • Test Case: Test Case provides an automated way to run a Test scenario.
    • Test Reports: HTML report generated after test execution.
  • JMeter: A user can convert a JMeter script into Cavisson Script using the script convertor provided by Cavisson.

Postgres Stats: This displays overall connection stats that includes Max connections, reserved connections, used connections, and available connections. Apart from this, a user can view detailed connection stats based on database and application.

Right Pane:

This section provides a summary of the most details related to release, memory, and CPU utilization. It contains the following sections:

Release Details

This section provides release details of the product, such as release version and build number, the time when the release is installed on the server. It also provides a tabular view where the user can see the release details, such as installation date/time, release version, and build number.

 Test Assets Summary

This section provides a summarized and consolidated view of the tests, scripts, and scenarios execution in the system. It contains total tests, achieved tests, locked tests, total scripts, total scenarios, and running tests.

 Alert Summary

In this section, user can view a summary of the alerts, such as date/time when the alert is generated, severity of the alert, such as critical, major, minor and the description of the alert.

 Tomcat Heap Memory

In this section, stats on the total heap memory is displayed. Heap memory is a memory used for dynamic allocations. Used heap memory is displayed (in GB) with blue color, and free heap memory is displayed with yellow color along with its percentage.

 CPU Utilization Vs Load Average

This section displays CPU utilization vs load average in the form of a graph. Various parameters, such as user, system, I/O ae displayed with different colors. The load average among all these is displayed with black color.

 Available Memory

This section displays stats on available memory (in GB) in the form of a graph. Cached memory is displayed with blue color and free memory is displayed with black color.

 Disk Space Utilization

This section provides a summary of the disk space utilization by various directories in the system. It contains information such as total space assigned to a particular directory (in GB), free space, used space, along with used percentage.

3. Click Total Test(s) or go to View > Test Runs. The Test Run(s) window is displayed.

Adding Scenarios from GUI

User needs to follow the below mentioned steps for adding scenario:

  1. Login to NetCloud, the NetCloud home page is displayed.

  1. Go to View > Scenarios > Scenarios or click Total Scenarios in the “Test Assets Summary” section in the right pane. The Scenario Management window is displayed.

3. Scenario can be created in two ways, one is via wizard and another one via Advance settings. First, scenario creation via wizard is described. In the next section, scenario creation via advance settings is described.

Scenario Creation via Wizard

Scenario creation using wizard is a step by step approach for scenario creation with a series of screens. Follow the below mentioned steps for scenario creation using wizard:

  1. Click the Wizard button on the scenario window, the welcome screen of scenario configuration wizard is displayed.

2

2. Post few seconds, various steps for scenario creation is displayed. At first, only the initial step is enabled. Rest other are enabled sequentially on the completion of each step only.

Step – 1: Scenario Name

In this step, user needs to select the project and subproject under which the scenario is to be created. Post that, specify a valid scenario name. First character must be alpha, other characters can be alpha, numeric, dash or underscore. Then, click the Next button to move to the next step.

Step – 2: Scenario Profile (Optional)

In this section, user can select an already created scenario profile (how to create a scenario profile is discussed later). NetStorm has scenario profiles to keep default configurations specific to a subproject at a commonplace. To use a scenario profile, select the Use Scenario Profile for Scenario Settings checkbox and specify the project, sub-project, and profile name. Then, click the Next button to move to the next step.

Step – 3: Add Generator

In this step, user needs to add generator(s) for scenario groups. Select one or more generators from the list. To add all the generators, select the Use all Selected Generator(s) for all scenario group(s) check box.  Click the Next button to move to the next step.

Step – 4: Scenario Group  

Select the Scenario type, either Fix Concurrent Users (FCU) or Fixed Session Rate (FSR). Specify the script from the drop-down list and mention the number of users (in case if FCU is selected) and number of sessions per minute (in case FSR is selected). User can add more records using the Add button. Then, click the Next button to move to the next step. Below is an example of FCU, where 10 users are added in group G1 and 20 users are added in group G2. All generators are selected for both the groups.

Step – 5:  Ramp Up

The Ramp-up phase signifies the action of mounting any sort of operation. This phase is needed, so that in test execution of a scenario, users are ramped by spacing them appropriately. This ramping up reduces overload on Servers.

FCU

Ramp-up can be done by any of the four ways:

  • Immediate Ramp-up

Selecting the Simultaneously option results in all virtual users of the Virtual Group to access site Immediately. This is called Immediate Ramp-up. For example, 80 Virtual users access site instantly for a group.

  • Stepwise Ramp-up

Select a specific number of Virtual users to repeatedly access a site after inserting a time delay (in HH:MM:SS). The users are ramped up in steps. For example, 25 Virtual users are ramped-up followed by next 25 after a delay of 5 seconds, till all 100 are ramped-up.

  • Time Mode Ramp-up

All Virtual users access site after inserting time delay (in HH:MM:SS). This is called Time Mode Ramp-up. For example, 100 Virtual users ramp-up after inserting time delay of (HH:MM:SS). This Time Mode Ramp-up can be further achieved by 2 modes.

    • Linear Time Mode Ramp-up

Users ramp linearly means that the users are created at a constant inter arrival time. All Virtual users access site after inserting a time delay (in HH:MM:SS). System decides to pick a fixed number of users to Ramp-up. For example, System decides to Ramp-up 25 users after every 5 seconds till all 100 users are ramped-up.

    • Random Time Mode Ramp-up

All Virtual users access site after inserting a time delay (in HH:MM:SS). System decides to pick a fixed number of users randomly to Ramp-up. For example, System decides to Ramp-up 20 users after every 5 seconds then ramps up 30 after delay of further 5 seconds and later ramps up 10 users and so on till all 100 users are ramped-up.

  • Rate Mode Ramp-up

Specify a fixed number of Virtual users to ramp-up per Second/per Minute/per Hour.  This Rate Mode Ramp-up can be further achieved by 2 modes:

 NoteThese options are activated by deselecting the Default Rate check box.
    • Linear Rate Mode Ramp-up

Users are created at a constant inter arrival time. Specify a fixed number of Virtual users to ramp-up per Second/per Minute/per Hour. System decides to pick a fixed number of users to Ramp-up. For example, 20 Virtual users ramp-up followed by delay per 1 second, next 20 users ramp-up and after further 1 second delay, 20 more users ramp-up and so on.

    • Random Rate Mode Ramp-up

Specify a fixed number of Virtual users to ramp-up randomly per Second/per Minute/per Hour.  System decides to pick random number of users randomly to Ramp-up. For example, 20 Virtual users ramp-up followed by delay per 1 second, next 30 users ramp-up and after further 1 second delay, 10 more users ramp-up and so on.

 NoteThe default rate is 120 users per minute for our system.

 

FSR

There are following options under this section:

  • Immediate Ramp-up

Selecting the Simultaneously option results in all virtual users of the Virtual Group to access site Immediately. This is called Immediate Ramp-up. For example, 80 Virtual users access site instantly for a group.

  • Time based Ramp-up

All Virtual users access site after inserting time delay (in HH:MM:SS). This is called Time Mode Ramp-up. For example, 100 Virtual users ramp-up after inserting time delay of (HH:MM:SS). This Time Mode Ramp-up can be further achieved by 3 modes:

    • Default Steps: Using this option, a pre-configured steps (i.e. 2) are applied for the sessions’ completion.
    • Steps of specified seconds: Using this option, user can specify the duration for each step.
    • Number of specified steps: Here, user can specify the number of steps to complete a session.

Step – 6: Duration

The Duration phase signifies the time for which the process runs without any change in any settings.

FCU

This Duration phase can further be achieved by 3 modes:

  • Time Mode Duration Phase             

This Time Mode duration phase means that the Scenario runs for a specific defined time. Select the Run for option and specify number of days and time delay in (HH:MM:SS). For example, 100 Virtual users accessing a site remain there for 1 day, 01:12:24, i.e., 01 hour, 12 minutes & 24 seconds.

  • Session Mode Duration Phase

This Session Mode duration phase means that the Scenario runs for a specific number of sessions. For example, 100 Virtual users accessing a site run for 10 sessions.

  • Indefinite Mode Duration Phase

In this phase, the Scenario doesn’t stop if Run Indefinite mode is selected. For example, 100 Virtual users accessing a site remain there for indefinite time.

 NoteThis is the default option.

FSR

There are following options under this section:

  • Time Mode Duration Phase             

This Time Mode duration phase means that the Scenario runs for a specific defined time. Select the Run for option and specify number of days and time delay in (HH:MM:SS). For example, 100 Virtual users accessing a site remain there for 1 day, 01:12:24, i.e., 01 hour, 12 minutes & 24 seconds.

  • Indefinite Mode Duration Phase

In this phase, the Scenario doesn’t stop if Run Indefinite mode is selected. For example, 100 Virtual users accessing a site remain there for indefinite time.

 NoteThis is the default option.

Step – 7: Ramp Down

The Ramp-down phase means a gradual decrease in number of Virtual Users from system. This is reverse of Ramp-up Phase.

FCU

Ramp-Down can be done by any of the three ways:

  • Immediate Mode Ramp-Down Phase            

Selecting the Simultaneously option results in all virtual users to be removed from the site Immediately. For example, 100 Virtual users accessing a site are removed from the system immediately.

  • Step Mode Ramp-Down Phase

Select a specific number of Virtual users to repeatedly removing from the system after a time delay (in HH:MM:SS). For example, 25 Virtual users are ramped-down followed by next 25 after a delay of 5 seconds, till all 100 users are removed from the site.

  • Time Mode Ramp-Down Phase

All Virtual users are removed from system after a time delay (in HH:MM:SS). This Time Mode Ramp-Down can be done by any of the two ways:

    • Time Mode Ramp-down – Linearly

All Virtual users are removed from system after inserting time delay of (HH:MM:SS) in a Linear mode. System decides to pick a fixed number of users to Ramp-down. For example, System decides to Ramp-down 20 users after   every 5 seconds and so on till all 100 users are ramped-down.

    • Time Mode Ramp-down – Randomly

All Virtual users are removed from system after inserting time delay of (HH:MM:SS) in a Random mode. System decides to pick a fixed number of users to Ramp-down. For example, System decides to Ramp-down 20 users after every 5 seconds, followed by 10 users in next 5 seconds followed by 30 users ramped down in next 5 seconds and so on till all 100 users are ramped-down.

FSR

There are following options under this section:

  • Immediate Mode Ramp-Down Phase            

Selecting the Simultaneously option results in all virtual users to be removed from the site Immediately. For example, 100 Virtual users accessing a site are removed from the system immediately.

  • Time based Ramp-down

All Virtual users are removed from system after a time delay (in HH:MM:SS). This Time Mode Ramp-down can be further achieved by 3 modes:

Default Steps: Using this option, a pre-configured steps (i.e. 2) are applied for the sessions’ completion.

Steps of specified seconds: Using this option, user can specify the duration for each step.

Number of specified steps: Here, user can specify the number of steps to complete a session.

Step – 8: Page Think Time

Page Think Time is the Page View Time (after a page is downloaded).

FCU and FSR

There are following options under this section:

Think Time Options

  • No Think Time: No time is spent in viewing the pages. This is the default option selected. 
  • Random (Internet type distribution) think time with median of value specified in seconds: The think time is taken randomly in internet type distribution pattern with median of the value specified. For internet type distribution, median is roughly around ¼th of the mean.
  • Constant think time of value specified in seconds: By selecting this option, constant think time can be taken for each page. The time needs to be specified in seconds.
  • Random (Uniform distribution) think time from specified range in seconds: It randomly takes the value of think time from the range specified in uniform distribution.
  • Custom think time returned by C method: Enter the method name.

Override Recorded Think Time

This setting overrides the setting of the page think time for the particular pages. To override recorded think time, following options are available:

  • Use recorded think time: If user selects this option, the default think time of the script is applied.
  • Multiply recorded think time by some value: On selecting this option, user has to provide some value (number) so that the given page think time is multiplied by the value provided in this textbox. By default, it is 0. 
  • Use random percentage of recorded think time: On selecting this option, user needs to provide the minimum and maximum % value so that the page think time is in between the minimum and maximum % of the above provided page think time.

Step – 9: Session Pacing

Session pacing is an interval between two sessions executed by a virtual user.

FCU

There are following options under this section:

Start New Session

This specifies when the next session is started after a VUser completes previous session. It can have one of the possible values:

  • As soon as the previous session ends: The new session begins as soon as possible after the previous iteration ends. This mode is good for loading the SUT maximally. (This is the Default mode)
  • After the previous session ends: The new session starts after the end of previous session. There are following options:
    • With fixed delay: The next session is started after a fixed delay. Specify the delay in seconds.
    • With random (Internet type distribution) average delay: The delay is random average delay of the time specified in seconds.
    • With random (Uniform distribution) delay: The delay is of random but uniform distribution and within the range specified in seconds.
  • Once every interval (Provided that the previous session ends by that time else next session starts as soon as previous session ends):
    • At fixed interval: The next session starts after a fixed interval of time specified in seconds.
    • At random (Internet type distribution) average interval: The delay is random average delay of the time specified in seconds.
    • At random (Uniform distribution) interval: The delay is of random but uniform distribution and within the range specified in seconds.

Example: Consider a situation where previous session took 10 seconds and user has pacing time of 15 seconds. In this case, next session would be started after 5 seconds of completing the last session. This mode tries to keep the average session rate same even if the server response time changes. This is more similar to real life situations where the typical session rate (sessions/hours) does not change for an application if the response time is increased. If the last session takes more than pacing time, next session would be started immediately after completing previous session.

Introduce delay before first Session too (By randomized mean pacing time): By enabling this check box, a delay can also be applied before start of first session. This delay is calculated by randomized mean pacing time.

Simulate a new user on each session: By selecting this option, a new user is simulated on each session.

  1. This completes the scenario creation using wizard and scenario summary report is displayed.

4. Click the Save button to save the settings. A confirmation message is displayed that scenario has been successfully created.

5. Click the Close button to close the window and exit from the wizard. Clicking the Advance Settings button navigates the user to the scenario settings window.

Scenario Creation – Using Advance Settings

Scenario Creation Using Advance Settings

On the Scenario window, click the Create button, the Create Scenario dialog box is displayed.

2

2. Enter the Scenario details:

  • Project
  • Sub-Project
  • Scenario Name

To use a scenario profile, select the Use Profile check box and specify the project, sub-project, and scenario profile name.

3. Click the Next button, the Scenario is created and Scenario Management window is displayed. Click the scenario name, the Scenario Settings window is displayed.

4. Add a group by clicking the Add Group () icon. The Add Group dialog box is displayed.

5. Enter the Group Details:

  • Group Name: The group should have a proper name specifying the exact task the group performs. Name can be alphanumeric but first character should be an alphabet.User Profile: The User Profile is User Location based. An existing User Profile from drop- down can be selected. The default is “Internet”.Type: The available options are:
    • Script: An existing script can be selected from drop-down list. The script name should be self-explanatory. For example: QAT_Smtp_Include_Body
    • URL: A URL name is the name under test for performance. The URL name has to be specified as per exact format. For example, http://www.Aol.com/ or https://www.google.com/
    Ensure that URL is ended by forward slash “/”.

     

    • JMeter Script: JMeter test can be run from NC test by running JMeter instance from NetCloud. JMeter instance runs its own JMXscript. NetCloud reads data from JMeter logs and plotting HTTP graphs on dashboard.

     

    • RDT URLs: NetCloud / RDT provides a versatile mobile application testing platform using real iOS and Android devices on cloud. NetCloud / RDT has the largest device farm of real mobile devices, gathered from different regions globally, including the most versatile OS, OEM and hardware configurations for Android and iOS developers. This helps in test automation, remote manual access and REST API to access, run and manage any tests with these devices.

    To know more about RDT, ask your Cavisson representative.

    Session / URL: On selecting the Type as Script, user needs to provide the Session. On selecting the Type as URL, user needs to provide the URL.

    Number of user(s): It is the measure of number of Virtual users assigned to the group. For example: 80.

6. Click OK, the group is added to the scenario.

 To avoid the test to run in indefinite mode, make changes in the duration phase.

Click the Save () icon to save the group.

7. For Server mapping, click the Server Mapping link on the left pane. The Server Mapping window is displayed.

8. Click the Add button and enter the Server Mapping Details:

  • Recorded Server
  • Actual Server
  • Location

9. Click OK and then Save button.

Adding Generator File

  1. Open the Scenario Settings window and click the Generators icon on the top pane.

  1. The Add Generators dialog box is displayed. Select the generators from the list. To use all selected generators for all scenario groups, select the specified check box and click OK.
  2. Click the Start Scenario icon.

4. Provide the Test name and click the Start Scenario button. The test starts and its initialization status can be viewed in the Test Initialization Status window that displays the different stages of the test initialization for both controller and generators. On the right panel, the window also displays information like User, Start Date Time, Duration, Scenario Type, Warning Count, Test Initialization Elapsed Time, and Generator Count. The stages of test initialization for a controller looks like below:

The stages of test initialization for a generator looks like below:

If any generator fails, an error message having the test run number is displayed on the controller page.

The test can be seen in Web Dashboard.

You can also check the generator status by clicking Generator Count on the right panel. The Generator Test Init Status window is displayed.

In this window, you can track the progress of every stage of a generator. You can:

  • View the details of all the generators, such as generator name, generator IP, generator health check status, scenario file upload status, script file upload status, script’s external data file upload status, and action.
  • View the logs of a generator by clicking the View Logs icon under the ‘Action’ column.

The user can also perform the following actions:

  • Refresh : Refresh the data of generator test initialization status.
  • Filter : Filter the results by searching or selecting from the drop-down lists. The search option is applicable for ‘Name’ and ‘IP’ columns only where the user can search for a string/substring. For the other fields, drop-down options are provided from where the user can search from pre-defined values.
  • Download : Download the status report in an excel file.
  • Maximize / Minimize : Maximum or minimize the panel.

Note: In case of failure in any phase of test initialization or if test is not started on that generator, the border of the corresponding row is highlighted with Red color.

Health Check Settings

Using the Health Check Settings, you can check the generators health before running a test. You can specify the pre-requisites for the generators and if it meets the prerequisites, the test runs, else an exception is generated. This helps in optimizing the loading time of components which consumes overall time on initialization.

After enabling the “Enable Generator Health Check before start of test. Test will not start, if any Generator Health Check fails.” check box, user can check the generator health by specifying the following pre-requisites:

  • Minimum Free Disk Space: This enables checking of disk availability on generators. This is minimum value of disk availability that should be present. This should be between 0 and 1024 in GB. Default value is 50 GB.
  • Maximum CPU Utilization: This mode enables checking CPU utilization. On generator, CPU availability should be between 0 and 100 in percentage. Default value is 50%.
  • Minimum Available Memory: This mode enables checking memory utilization of generator, which is minimum memory value, which should be present in generator. It should be between 0 and 1024 in GB. Default value is 4 GB.
  • Minimum Interface Speed: This enables checking bandwidth between controller and generator that should be available. This value should be between 0 and 100 in Mbps. Default value is 100 Mbps.

Generators in Scenario

Generator Management

The user can view all the information about the generators and perform various actions from the UI. To do this, go to Admin on the left panel and click Generator Management.

This displays a window that contains a list of all the available generators.

The user can perform the following actions:

  • Add a generator
  • Edit the details of a generator
  • Delete a generator

Add a generator

To add a generator, click the Add icon . The Add Generator window is displayed.

The user needs to type the details, such as Generator Name, Generator IP, Generator Blade, CMON Port (by default it is 7891), Location, and Description. Click OK to add the generator.

Edit a generator

The user can edit the details of one generator at a time. Click the Edit icon  against the generator name under the Action column.

The Edit Generator window is displayed. The user can edit the details, such as Generator Name, Generator IP, Generator Blade, CMON Port, Location, and Description. To save the changes made, click OK.

Delete a generator

The user can delete a generator by clicking the Delete icon  against the generator name under the Action column.

To delete more than one generator at once, select the check boxes against the generator names, and then click the Delete icon  at the upper-right corner of the window. To delete all the generators at once, select the topmost check box.

A confirmation message is displayed to delete the selected generator(s). Click OK.

Continue test on generator failures

By selecting the check box, the user can continue to run the test even if the generators fail to start. These are the following options under this section:

Minimum percentage of healthy generators needed for test to start: The user needs to provide the minimum percentage of generators that are required to run the test.

Minimum percentage of healthy generators during a test: This percentage of generators decides whether the controller continues or fails while the test is running.

Stop test on generator if connection with controller does not establish in: In case of the test triggered on generator, the user needs to provide the time (in seconds) for which the controller must wait for the generators to start test.

Stop test on generator if missed progress samples equal: The user needs to provide the number of progress samples. The test on generator stops if it is unable to send this number.