Installing the Software

Before installing dsTest, ensure that the platform meets the minimum requirements:

- 64-bit Linux OS - We recommend Ubuntu Server 22.04 LTS. and currently support the following Operating Systems:

   Ubuntu Server 20.04 LTS

   Ubuntu Server 22.04 LTS

   Red Hat Enterprise Linux 9

- Minimum 1GB memory with at least 400MB free memory

- At least 2GB free disk space

In order to optimize performance, dsTest is tested against real and virtual systems that mirror standard CPU architecture and configurations. Non-standard configurations, such as those with odd number of cores and/or chip configurations may prevent dsTest from starting. 

The type of license issued for dsTest determines whether you can run dsTest within a VM. If you're not sure which type of license suits your test environment, see our Licensing topic for an explanation of the options available before proceeding. If you do choose to use VMs, refer to Configuring Your Virtual Machine to ensure that your VM will be compatible with dsTest and that it will produce the optimum performance.

Download dsTest from the secure website: https://support.developingsolutions.com/loads

Log in using the user name and password supplied by Support and then select the directory that corresponds to the release that you want to install.

Click on the desired software package depending upon your Linux distribution, or as instructed by Support:

RHEL: devsol-dsTest_<release>.<build date>-1.x86_64.rpm

Ubuntu (64-bit): devsol-dsTest_<release>.<build date>_amd64.deb

The selected package will be downloaded. Follow the instructions below to install dsTest.

During the installation a devsol user group and a devsol user account will be created. Please ensure that there is not an existing group or account with that name (unless they were created by a previous installation of dsTest).

Depending on how you plan to use dsTest, you may need to also install the following packages. Choose the latest version-compatible releases.

If operating a local license server, this functionality is included within the aforementioned dsTest package.

dsFilter - devsol-dsFilter_<release>.<build date>_amd64.deb or devsol-dsFilterModule_<release>.<build date>-1.x86_64.rpm - required for Packet Capture and non-native, optimized sockets.

dsClient Desktop - our graphical, desktop user interface

1. Log in to the dsTest platform

Log in to the platform that will host dsTest as you normally would using SSH or a utility such as PuTTY.

2. Copy the installation package

Copy the package to your home directory.

3. Log in as root

Root permission is required to install dsTest. Elevate your permissions if necessary.

devsol@demo2:~$ su

Password:

4. Install dsTest

Initial dsTest installations will almost always fail due to dependencies on other packages. Run the installation command first and note which packages will be required.

Debian (Ubuntu) Installation

dpkg -i  <package name>.deb

demo2:/home/devsol# dpkg -i devsol-dsTest_2.9.0_amd64.deb

Selecting previously deselected package devsol-dstest.

(Reading database ... 19066 files and directories currently installed.)

Unpacking devsol-dstest (from devsol-dsTest_2.9.0_amd64.deb) ...

dpkg: dependency problems prevent configuration of devsol-dstest:

 devsol-dstest depends on libsctp1; however:

  Package libsctp1 is not installed.

dpkg: error processing devsol-dstest (--install):

 dependency problems - leaving unconfigured

Errors were encountered while processing:

 devsol-dstest

RPM Installation

rpm -i <package name>.rpm

error: Failed dependencies:

    libsctp.so.1()(64bit) is needed by devsol-dsTest-2.9.0-1.x86_64

5. Resolve dependencies

Download/install each of the packages on which dsTest is dependent (e.g., libsctp1/libsctp.so.1, dmidecode, pciutils):

Debian (Ubuntu) Installation

The tool "apt-get install" will download and install the packages if the system is configured properly, otherwise manual installation will be required.

apt-get install libsctp1

Reading package lists... Done

Building dependency tree    

Reading state information... Done

Recommended packages:

  lksctp-tools

The following NEW packages will be installed:

  libsctp1

0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

1 not fully installed or removed.

Need to get 28.0kB of archives.

After this operation, 86.0kB of additional disk space will be used.

Get:1 http://ftp.us.debian.org lenny/main libsctp1 1.0.9.dfsg-1 [28.0kB]

Fetched 28.0kB in 1s (27.8kB/s)

Selecting previously deselected package libsctp1.

(Reading database ... 19076 files and directories currently installed.)

Unpacking libsctp1 (from .../libsctp1_1.0.9.dfsg-1_amd64.deb) ...

Setting up libsctp1 (1.0.9.dfsg-1) ...

Setting up devsol-dstest (2.9.0) ...

dsTest configure in progress...

created group: devsol

created user: devsol

configured permissions

Successfully generated system id: /usr/local/devsol/config/SystemId.ds

dsTest installed

demo2:/home/devsol#

Notice above that aptitude automatically completed the previously failed installation of dsTest once the dependency was resolved.

RPM/RHEL Installation

Use the "yum or dnf install" tool to download and install the packages indicated.

yum install lksctp-tools

or

dnf install lksctp-tools

Repeat the installation command in step 4, which should now run successfully.

Depending upon your specific installation, there may be other dependencies that must also be installed or resolved, such as dmidecode and pciutils.

6. Optional Configurations

If your system will be accessed by multiple users, consider whether you should create accounts for different users or groups of users. See Adding User Accounts for more information.

dsTest can be configured to send email notifications for critical items such as license expiration warnings. See Adding Email Support for more information.

You can configure these items at a later time if you are not ready to do so now.

7. Log out

Exit root and log out of the platform.

demo2:/home/devsol# exit

exit

8. Log in as a devsol group user

Log back in as the default user devsol. The password for the devsol user is also devsol. The devsol user group and this user account are automatically created during installation and are configured with permission to run dsTest.

devsol@demo2:~$ devsol

Password:
~>

9. Create a software repository

We recommend that you retain dsTest installation packages in a Loads directory within the devsol home directory. Create /home/devsol/Loads/ and copy or move the installation package to that directory.

10. Request license file

Before you can run dsTest it must be licensed. See our Licensing topic for a full discussion of the available licensing options and installation instructions. This topic focuses on obtaining your initial dsTest license.

Node-locked Licensing

For Node-locked licenses, dsTest must run in a native Linux OS environment. Virtual Machine (VM) environments are NOT supported with this type of license.

For Node-locked licensing, each server running dsTest must have a license file installed. Execute the following instructions in this section on each dsTest platform.

A file which identifies your system, "/usr/local/devsol/config/SystemId.ds", was created during installation.

          ~> ls -las /usr/local/devsol/config/

          total 24

          4 drwxrwxr-x 2 devsol devsol 4096 2009-07-14 08:16 ./

          4 drwxrwxr-x 4 devsol devsol 4096 2009-07-14 08:15 ../

          4 -rw-rwxr-- 1 devsol devsol   24 2009-07-07 11:22 bash_logout*

          4 -rw-rwxr-- 1 devsol devsol  403 2009-07-07 11:22 bashrc*

          4 -rw-rwxr-- 1 devsol devsol  585 2009-07-07 11:22 profile*

          4 -rw-r--r-- 1 root   root     62 2009-07-14 08:16 SystemId.ds

          ~>

If the file was not created, execute the following command to create it. You must be logged in as root, or operating with root permissions, in order to have write permission for the /usr/local/devsol/config directory.

          ~> /usr/local/devsol/bin/genSystemId

Send the SystemId.ds file from each server to DS-Support@mobileum.com, along with information identifying the Purchase Order associated with the product purchase.

Floating (Non-Hosted) Licensing

For Floating (non-hosted) licenses, the dsTest license server MUST run on a native Linux OS environment. Virtual Machine (VM) environments are NOT supported for the license server. Instances of dsTest CAN run on VMs that have connectivity to the license server, but the license server itself must run on a native Linux OS environment.

For Floating licensing, one server is designated as a License Server. The SystemId.ds file from the License Server is used to create the licenses for the License Server and all dsTest servers. Using the instructions above, obtain the SystemId.ds file from the License Server only, and send the following to DS-Support@mobileum.com:

The SystemID.ds file

The IP address on the License Server that will be used for communication between the License Server and the other dsTest platforms

Information identifying the Purchase Order associated with the product purchase

All of this information must be sent to Developing Solutions in order to create your floating license.

Floating (Hosted) Licensing

Developing Solutions hosts the licensing server and your dsTest platforms pull dsTest resources from the our license server. Your dsTest platforms are paired with the hosted license and will work only with the hosted floating license. Support will supply a license file that your can install on any platform that is to run dsTest.

11. Apply license file

See the Licensing topic for instructions.

12. Run the software

Your system is now ready to operate, and you'll find the command and options used to start dsTest in Launching dsTest. See Running dsTest as a Service if you would prefer that your server automatically run dsTest at boot time.

dsTest is a memory resident application, and will allocate the amount of memory it requires based upon the specified test parameters. Other applications may adversely affect the performance of dsTest or limit its capacity. We recommend that dsTest run as the sole application on your server when the tests are running to avoid competition for server resources such as memory.

dsTest Directories

The contents of the /usr/local/devsol/ directory, which was created during installation, are subject to change during the installation of any future upgrade. Those changes may include deleting, overwriting, or renaming the contents. You should never store or modify information within this structure.

If you are a dsAnalyzer licensee, there will also be dsAnalyzer files in the /usr/local/devsol/ directory and its subdirectories. Only the dsTest specific files are listed here.

Contents of  /usr/local/devsol/

Files

Comments

dictionary

link to the latest Diameter dictionary files

ssl

link to latest ssl utility

/lsLog

license server log files

/run

Example dsTest and licenseServer startup configuration files

/src

dsFilter files

/bin

executables

/dsTest

files specific to dsTest

/dsTest/examples

dsTest example configuration files

/dsAnalyzer

files specific to dsAnalyzer

/config

Schema and license files

Contents of  /usr/local/devsol/bin

Files

Comments

dsTest

dsTest application

dsClient

dsClient Terminal application

genSystemId

Utility that calculates the System ID (SystemId.ds)

dsAssist

Link to a customer-initiated utility that will allow our Support staff to remotely access your dsTest server

db2csv

Link to utility that creates CSV files from an OM database

cdr2db

Utility to create SQLite databases from CDR files

cdr2csv

Utility to create CSV files from CDR files

cdrPipe

provides CDR streaming to dsClient Desktop

add_devsol_user

link to utility to assist in creating user accounts with the same group association and profile as the 'devsol' user

licenseServer

The License Server application for floating licensing. To be used on the License Server only.

licenseServer.sh

Script that may be customized by the user to start up the license server application

packetPipe

link to utility that provides packet streaming to dsClient Desktop

getLicense.py

 

dsTest.sh

Example startup script to automatically start dsTest

dbrp

Utility that repairs OM databases that were downloaded before they were closed.

dbcc

Utility indexes an OM database and then performs a statistical analysis of the measurement values.

postinst

 

smartcontrol

Utility for demonstrating the dsTest SmartControl feature

Contents of  /usr/local/devsol/config

Files

Comments

SystemId.ds

System ID

license.dsl

License file (to be provided by Developing Solutions)

eula.pdf

End User License Agreement

eula.txt

 

bash_logout

Default bash_logout file

bashrc

Default bashrc file

profile

Default profile file

dsLicense.xsd

License XML schema

dsTest.xsd

dsTest XML schema

*.xsd

dsTest XML schema components

*.xml

Other XML configuration files

mcc_list.csv

List of MCC/MNC values

ManagementIP

Management IP address for this server

Contents of /usr/local/devsol/run

Files

Comments

dsTest.conf

Configuration file that can be customized for running dsTest as a service (overrides dsTest.opt settings)

licenseServer.conf

Configuration file that can be customized for running licenseServer as a service

Contents of /usr/local/devsol/dsTest/examples

Files

Comments

example_*.xml

Sample XML configuration files

Contents of /usr/local/devsol/src

Files

Comments

dsFilter

packet capture and optimized socket module

Contents of /usr/local/devsol/lsLog

Files

Comments

ls_log*

License Server log files