Admin

Here, the user can perform some admin related activities, such as setting up projects, LDAP server settings, setting up servers, controllers, GIT settings, data retention policy, access control, agent info, and NetHavoc. In the subsequent sections, description of these are provided.

Projects

Project administration is used for managing Project and subproject, users are categorized accordingly. It involves overall administration of projects.

Projects enable easy organization and management of individual users of the NetStorm.

A Project, in essence, is a self-contained entity that can perform all of its work without affecting the work of another user. Project and subproject can be added from user management GUI and used in scenario and analyze GUI.

Following things need to be ensured in Project Administration window:

• Make sure sorting is done on every column.
• Make sure all check boxes are enabled.
• Project name should not have spaces in between.
• A project should have at least one subproject.
• A project can have multiple subprojects.
• Name of project and subproject can be same.
• Multiple projects can’t be deleted at a time.

• A subproject can’t be deleted without deleting the project to which it belongs.

This section describes the following tasks:

• Add project/subproject
• Delete project/subproject
• Delete Forcefully project/subproject
• Rename project
• Rename subproject

Adding a Project/Subproject

Admin user needs to follow the below mentioned steps for adding a project/sub project:

1. Login to NetDiagnostics as an admin user and click the Projects option under the Admin menu on the tool bar. The NetDiagnostics Enterprise – Project Administration window is displayed with a list of projects.

2. Enter the Project name and sub-project name and click Add. The project and sub-project is added in the list.

If user provides an existing Project name, system flashes an alert message “Record with same key (proj, sub_proj) already exists in the Project. Please enter different value of key”.

Deleting a User Project/Subproject

Admin user needs to follow the below mentioned steps for deleting a project/sub project:

1. Select the project/sub-project that needs to be deleted and click the Delete button. A confirmation message is displayed as shown below:

2. Click OK. The project/sub-project is deleted.

Using Delete button, Admin user can delete only that projects/sub- projects that do not contains Scenarios and Scripts.

Delete Forcefully a User Project/Subproject

Delete forcefully functionality is used to delete a project/sub-project that contains Scenarios and Scripts. Such projects cannot be deleted using the Delete button. Admin user needs to use the Delete Forcefully button for deleting such projects.

Admin user needs to follow the below mentioned steps for deleting a project/sub project that contains Scenarios and Scripts:

1. Select the project/sub-project that needs to be deleted and click the Delete Forcefully button. A confirmation message is displayed.

2. Click OK. The project/sub-project is deleted.

If admin user selects more than one record to delete, system generates an alert message” Select only one record and try again”.

Rename a User Project

Admin user needs to follow the below mentioned steps for renaming a user project:

1. Select the user project that needs to be renamed. The project and sub-project is displayed in editable mode at the top of the list.

2. Rename the project name and click the Rename Project button. A confirmation message is displayed, click OK. The project is renamed and updated in the list.

Rename a User Subproject

Admin user needs to follow the below mentioned steps for renaming a user sub-project:

1. Select the user sub-project that needs to be renamed. The project and sub-project is displayed in editable mode at the top of the list.

2. Rename the sub-project name and click the Rename Project  button. A confirmation message is displayed, click OK. The sub-project is renamed and updated in the list.

LDAP Server Settings

LDAP, Lightweight Directory Access Protocol, is an Internet protocol that email and other programs use to look up information from a server.

The user can configure the following settings:

• Host:Port: Enter the Host name or IP address of your LDAP server. Enter the Port number used for LDAP communication (389 by default). If your server is an Active Directory Global Catalog server, you can specify port 3268 for a plain connection, or port 3269 for SSL.
• Base Domain: A base dn is the point from where a server will search for users. For example, dc=ldap, dc=cavisson, dc=com
• Enable user authentication: You can use the Lightweight Directory Access Protocol (LDAP) to authenticate users. Specify user roles by using group DNs for users who log in as an Administrator, Operator, or as a Viewer. The system has only one admin user and one operator.
• Bind Domain: An LDAP client transmits a BIND request to a server in order to change the authorization state of the client connection. When a client first connects to an LDAP directory server, the server sets the authorization state of the connection to unauthenticated. For example, cn=admin, dc=ldap, dc=cavisson, dc=com.
• Password: Enter the password.
• Enable communication over secure protocol: Secure LDAP (LDAPS) allows you to enable the Secure Lightweight Directory Access Protocol for your Active Directory managed domains to provide communication over SSL (Secure Socket Layer)/TLS (Transport Layer Security). By default, LDAP communications between client and server applications are not encrypted.

Servers

Defining server’s information in Custom Monitor increases the complications for the features (Server name or IP, user name, password, Local/Remote Specifications).

This section describes the following tasks:

• Add Server
• Delete Server
• Update Server
• Upgrade CMon
• Start CMon
• Restart CMon
• Stop CMon
• Show CMon
• CMon Version
• Show Running Monitors
• Run Command
• Cavmon Stats
• Upload File

Add Server

Admin user needs to follow the below mentioned steps for adding a server:

1. Login to NetDiagnostics as an admin user and click the Servers option under the Admin menu on the tool bar. The NetDiagnostics Enterprise – Server Administration window is displayed with a list of servers.

2. Click the Add button, the NetDiagnostics Enterprise – Add Server window is displayed.

3. Enter Server name, server type, installation directory, java home, agentless, port, SSH available, user name, password, and confirm password and click OK. The server is added to the servers list.

Installation Dir and JAVA_HOME should have absolute path.If server is Agentless is ‘yes’ and SSH Available is ‘No’. It gives an alert message. If SSH Available is ‘No’ User Name, Password and Confirm Password all are disable.

Delete Server

Admin user needs to follow the below mentioned steps for deleting a server:

1. Select the server that needs to be deleted and click the Delete button. A confirmation message is displayed.

2. Click OK. The server is deleted.

Update Server

Admin user needs to follow the below mentioned steps for updating a server:

1. Select the server that needs to be updated and click the Update button. The NetDiagnostics Enterprise – Update Server window is displayed.

2. Update the required server information and click the OK button.

Server name cannot be changed. One record can be updated at a time. Otherwise, system generates an alert message.

Upgrade CMon

Admin user needs to follow the below mentioned steps for upgrading CMon:

1. Select the Server and click the Upgrade Cmon button. A dialog box is displayed.

2. Admin user needs to specify the package name with full path that needs to be upgraded. The package should be on NetStorm machine. It shows upgrade output in text area.

3. Click the Close button.

Start CMon

Admin user needs to follow the below mentioned steps for starting CMon:

1. Select the server and click the Start Cmon button. The NetStorm – Start Cmon window is displayed and CMon is started (if not running currently).

2. Click the Close button to close the window.

Restart CMon

Admin user needs to follow the below mentioned steps for restarting CMon:

1. Select the server and click the Restart Cmon button. The NetDiagnostics Enterprise – Restart Cmon window is displayed and CMon is restarted.

2. Click the Close button to close the window.

Stop CMon

Admin user needs to follow the below mentioned steps for stopping CMon:

1. Select the server and click the Stop Cmon button. The NetDiagnostics Enterprise – Stop Cmon window is displayed and CMon is stopped.

2. Click the Close button to close the window.

Show CMon

Admin user needs to follow the below mentioned steps for showing CMon:

1. Select the server and click the Show Cmon button. The NetDiagnostics Enterprise – Show Cmon window is displayed with a message that CMon is running along with its pid.

2. Click the Close button to close the window.

CMon Version

Admin user needs to follow the below mentioned steps for getting CMon version:

1. Select the server and click the Cmon Version button. The NetDiagnostics Enterprise – Cmon Version window is displayed with CMon version.

2. Click the Close button to close the window.

Show Running Monitors

Admin user needs to follow the below mentioned steps for getting running monitors:

1. Select the server and click the Show Running Monitors button. The NetDiagnostics Enterprise – Running Monitors window is displayed showing all the running monitors.

2. Click the Close button to close the window.

Run Command

Admin user needs to follow the below mentioned steps for running a command:

1. Select the server and click the Run Command button. The NetDiagnostics – Run Command On Server window is displayed.

2. Enter the command in the Command text box and click the Run button. The command gets executed and result is displayed in Command Result.

3. Click the Close button to close the window.

Cavmon Stats

Admin user needs to follow the below mentioned steps for getting the CavMon statistics:

1. Select the server and click the Cavmon Stats button. The NetDiagnostics Enterprise – CavMon Stats window is displayed.

2. The NetDiagnostics – CavMon Stats window contains CavMon stats, such as heap info. It also contains Active threads info, such as thread id, thread type, test run, program name, program argument and start date & time.
3. Click Refresh to refresh the data, click Cancel to close the window.

Admin User can filter the records by entering the keyword and clicking the Apply button.Clicking the Show All button displays all records. Records can be auto-refreshed by selecting the Auto Refresh checkbox and specifying the interval.

Upload File

Admin user needs to follow the below mentioned steps for uploading a file to a server:

1. Select the server and click the Upload File button. The NetDiagnostics Enterprise – Upload File To Server window is displayed.

Admin User can also select the server from the Server drop-down list in the NetDiagnostics – Upload File To Server window.

2. Enter the NetDiagnostics source file path and destination path and click Upload. The file is uploaded to the on the server at the destination path.
3. Click the Close button to close the window.

Settings

Here, the user can configure the module tab settings.

• To open the module in application tab, select the Open in Application Tab
• To open the module in browser tab, select the Open in Browser Tab option.

Manage Controllers

Controllers are the shared blades in a specific hardware. These are multiple soft appliances in a single hardware with shared resources. This window displays – appliance name, controller name, controller URL, and Service Endpoint IP.

Here, the user can manage controllers, such as add or delete. To add a controller, the user needs to click the Add button. This displays the Add Controller window.

The user needs to provide the following inputs:

• Controller Name
• Controller Type
• Appliance Name
• Controller IP
• Controller Port (HTTP and HTTPs)
• Service End Point IP
• Recorder Port Range (Start Port and End Port)

GIT Settings

it is used to manage a project or a set of files as they change over time. Git stores this information in a data structure called a Git repository. The repository is the core of Git. A Git repository is the directory where all of your project files and the related metadata resides.

To configure Git settings, the user needs to perform the following operations:

1. Go to Advanced > Git Settings.
2. This displays the Git Remote Server Settings window where user needs to provide the following inputs:

1. • Enable Git: On selecting this check box, the Git is enabled in scenario and displays buttons, such as GIT Commit, GIT Pull, GIT Clone, and Version Control in the Scenario UI.
   • Repository IP: The IP of the machine where the files are stored.
   • Repository Port: Port of the machine.
   • User Name: Git user name.
   • Password: Password of the Git user.
   • Pass Phrase: A pass phrase is a sequence of words or other text used to control access to a computer system, program or data. A passphrase is similar to a password in usage, but is generally longer for added security.
2. Click OK.

Once these settings are enabled, following options are displayed in Scenario UI:

• Git Clone: First time user needs to do Git clone
• Git Pull: Pull the data from the remote repository
• Git Commit: In NS commit works as Git Add > Commit > Push
• Git Push: User pushes the committed changes in remote repository

Retention Policy

A user can configure the kind of data/directory that should be backed up from the current machine. Go to Admin > Retention Policy.

Purging NetDiagnostics Data in Local Mode: By default, purge mode is in local mode in UI, with Data Back-Up Enabled by default.

NDE Purge Tool (Data Back-Up) UI Fields:

• Test Run: Select test run for cleanup/backup.
• Back up Mode: Select Backup mode: Local or Cloud.
• Component Type: Select which component to clean/backup:

1. • Raw data
   • CSV
   • Logs
   • DB
   • Graph Data

• Clean up Time: Provide a time period for which a user wants to clean up ND data for selected component.
• Back up Path: Provide backup path where data needs to be backed up locally.
• Back up Time: Provide backup time for which a user wants to backup ND data for selected component.
• Negative Date: Provide time period for which data should not be cleaned up/backed up.
• Add: Add configuration to data list.
• Update: Select a configuration from data list to update.
• Clear: Clear filled configurations.
• Delete: Delete selected configuration from data list.

Purging ND Data in Cloud Mode: By default, Data Back-up Enabled field is unchecked.

 NDE Purge Tool (Data Back-Up) UI Fields:

• Test Run: Select test run for cleanup/backup.
• Back up Mode: Select Backup Mode: Local or Cloud.
• Component Type: Select the component a user wants to clean/backup:

1. • Raw data
   • CSV
   • Logs
   • DB
   • Graphdata

• Warm Bucket Name: Provide a name for Hot Bucket.
• Warm Path: Provide the path of google cloud storage bucket (nearline) where old data (approx. 1 to 6 months) can be moved. This data can still be accessed via soft links.
• Cold Bucket Name: Provide a name for Cold Bucket.
• Cold Path: Provide the path of Google cloud storage bucket (coldline) where old data (approx.6 to 12 months old) can be moved in archived form.
• Hot Time: Provide hot time period. (Hot Path: This is the machine’s local environment where all data is collected.)
• Warm Time: Provide warm time period.
• Cold Time: Provide cold time period.
• Negative: Provide time period of which data should not be cleaned up/backed up.
• Add: Add configuration to data list.
• Update: Select a configuration from data list to update.
• Clear: Clear filled configurations.
• Delete: Delete selected configuration from data list.

Agent Info

ND Agent is an agent running on the host where ND application under test is running. Its task is to provide communication channel between BCI Agent and ND Collector. In this section, user can view a list of ND agents along with their status. To view the ND agents list, click the Agent Info option within the Admin section.

On clicking this link, a new window is displayed. This window provides the status of machine agents and application agents. Machine agents are the cavisson monitoring agents (CMON) and application agents are the BCI agents or the ND agents.

Machine Agent Status

This section provides machine agent information, such as process id (PID), tier, server, server IP, operating system, version, agent start time, setting last updated time, status (either active/inactive), and action(s).

Application Agent Status

This section provides application agent information, such as PID, tier, server, instance, installation directory, agent type, version, agent start time, and status.

Operations on Agents

A user can perform the following operations on machine agent and application agent:

• Searching an agent
• Apply filters on agents
• Download reports
• Restart an agent
• Refresh agent status list
• View or update the settings

Searching an Agent

For searching an agent, use the search bar at the top-left section of the window. Enter the desired value to perform a search (in any column), the searched results are displayed accordingly. In the below image, we have searched ‘Instance1’ and system displays the results containing this text.

Apply Column Filters

A user can also apply column filters, which can work same as search, but can also be applied on multiple columns. To do this, click the  icon on the top-right corner of the window. The filter panel is displayed. Here, we have applied filter on two columns – ‘Instance’ and ‘Agent Start Time’.

To hide column filters, click the  icon again .

Download Reports

A user can also download reports of agent status in various formats, such as word, excel, and pdf. To do this, click the desired format, which is displayed at the bottom-left section of the screen.

Restart an Agent

The user can restart the machine agent. To do this, click the Restart icon .

Refresh Agent Status List

On clicking the Refresh icon , the agent list gets refreshed and updated list id displayed on the panel.

View or Update the Settings

The user can view or update the machine configuration by clicking  or  icon in the Action(s) column.

• View Configuration

On clicking the  icon, the following window is displayed where the user can view the current settings and advance settings of the machine.

• Update Configuration

On clicking the  icon, the following window is displayed where the user can edit the settings of the machine.

NetHavoc

The overall performance of a service is directly linked, among other things, to its ability to tolerate failures. This aspect of an application/software can be tested by deliberately injecting random faults and failures into the application infrastructure.

NetHavoc is a powerful feature added to NetStorm, which allows users to test the resilience of the applications. NetHavoc can be used to inject various faults into the application infrastructure during a load test. The after effects of the fault injection can be monitored through NetStorm’s powerful monitoring capabilities.

For more details, refer the NetHavoc section.