Configure the Linux environment

This section describes the configuration steps you need to complete after installing the load generator, before you can begin working with the load generator.

In this topic:

Set the environment variables

Set the appropriate environment variables after installing the load generator.

To enable the load generator to run, the following environment variables must be defined:

• M_LROOT. The location of the Linux load generator root folder.
• PATH. The location of the Linux load generator bin directory.
• PRODUCT_DIR. The location of the Linux load generator root folder.

The Setup wizard performs the following tasks relating to the environment variables:

• Adds the environment variable definitions to the system-wide startup scripts.

  If the variable definitions were not correctly set during the setup, see Troubleshoot the load generator Linux installation for possible solutions.

• Sets environment variables for the current shell session if the source command was used to run the Setup wizard.

  This topic describes how to set the environment variables for the current shell session if a source command was not used to run the Setup wizard.

To determine if environment variables are set, run verify_generator (see Verify the Linux installation) or use the following command:

echo $M_LROOT

If the name of the load generator root folder is returned, then the environment variables are correctly set for current shell. If the name of the load generator root folder is not returned, then manually set the variables as described below.

To manually set the environment variables for the current shell session (if the source command was not used to run the Setup wizard), execute one of the following commands:

• Bash users:

  source <load generator root>/env.sh 

• C Shell users:

  source <load generator root>/env.csh

Back to top

Verify the Linux installation

The load generator installation includes a setup verification utility, verify_generator, that checks the load generator setup on your Linux machine. It is recommended that you run the utility after installing the load generator, before attempting to invoke the load generator.

The verification utility checks environment variables and your startup scripts (/etc/csh.cshrc, ${HOME}/.cshrc or /etc/profile, ${HOME}/.profile) to verify that they are set up correctly. It confirms the following:

• All the prerequisite software is installed. (This check is performed for 64-bit installations only.)

• There are at least 128 file descriptors
• The .rhosts permissions have been defined properly: -rw-r--r--
• The host can be contacted by using rsh to the host. If not, it checks for the host name in .rhosts
• M_LROOT is defined
• .cshrc or .profile defines the correct M_LROOT

• /etc/csh.cshrc, ${HOME}/.cshrc or /etc/profile, ${HOME}/.profile defines the correct M_LROOT

• .cshrc or .profile exists in the home directory
• The current user is the owner of the .cshrc or .profile
• A Linux load generator installation exists in $M_LROOT
• The executables have executable permissions
• PATH contains $M_LROOT/bin and /usr/bin

To run verify_generator:

1. From the <load generator root>/bin folder, run the following command:

   ./verify_generator

   For example:

   /opt/OT/OT_LoadGenerator/bin/verify_generator

   If you want to receive detailed information about the checks, you can use the -v option, as follows:

   ./verify_generator -v

2. View the results.

• If the settings are correct, verify_generator returns OK.

• If any of the settings are incorrect, verify_generator returns Failed, and suggestions on how to correct the setup.

Back to top

Check Controller connection

You can check the connection to Controller by starting the load generator, and making sure that Controller can access.

To start the load generator, run:

If Controller is to connect remotely to the load generator using rsh (remote shell), you need to make sure that the load generator can be remotely accessed by Controller. You can also configure Controller to connect to the load generator without using rsh. In this case, you need to activate the agent daemon on the load generator.

To check remote access:

1. On the load generator machine, locate the .rhosts file which is located in the user home directory.
2. In the .rhosts file, verify that Controller is included in the list of machines. If it is not listed, add it to the list.

If Controller still cannot connect to the load generator, contact your system administrator.

To connect to a Linux load generator without using rsh:

1. On the Linux load generator, run the agent daemon by entering the following command from <load generator root>/bin:

   ./m_daemon_setup -install

   This runs a daemon called m_agent_daemon, and if successful, you receive a message: m_agent_daemon <process ID>.

   The agent now keeps running, even if the user is logged off. You can stop the agent by using the command explained in step 9 below, or by rebooting the machine.

   Note: If you look at the m_agent_daemon[xxx].log log file in the temp directory, you may see communication errors, even if the installation succeeded.

2. In Controller, select Scenario > Load Generators. The Load Generators dialog box opens.

3. Click Add. The Add New Load Generator dialog box opens.

4. In the Name box, enter the name of the computer on which the load generator is running.
5. From the Platform list, select Linux.
6. Click More.
7. Click the Linux Environment tab, and make sure that the Don’t use RSH check box is selected.
8. Connect as usual.

9. To stop the agent daemon, run the following command from the <installdir>/bin directory:

   ./m_daemon_setup -remove

   This stops the m_agent_daemon daemon, and if successful, you receive the message: m_agent_daemon is down.

Back to top

See also:

• Install a load generator
• Prepare for installation