Configure the Linux source machine for network monitoring

This task describes how to configure a UNIX source machine before running the network monitor.

To lean more about network monitoring, see Network monitoring overview.

  1. Assign permissions where LoadRunner Enterprise is installed locally

    Follow these steps to assign root permissions to the merc_webtrace process:

    1. Log in to the source machine as root.

    2. Type: cd <LoadRunner Enterprise_installation>/bin to change to the bin directory.

    3. Type: chown root merc_webtrace to make the root user the owner of the merc_webtrace file.

    4. Type: chmod +s merc_webtrace to add the s-bit to the file permissions.

    5. To verify, type ls -l merc_webtrace. The permissions should look like this: -rwsrwsr-x.

  2. Assign permissions where LoadRunner Enterprise is installed on the network

    In a LoadRunner Enterprise network installation, the merc_webtrace process is on the network, not on the source machine disk. The following procedure copies the merc_webtrace file to the local disk, configures mdrv.dat to recognize the process, and assigns root permissions to merc_webtrace:

    1. Copy merc_webtrace from <LoadRunner Enterprise_installation>/bin to anywhere on the local disk of the source machine. For example, to copy the file to the /local/<LoadRunner Enterprise> directory, type: cp /net/tools/LoadRunner Enterprise_installation/bin/merc_webtrace/local/<LoadRunner Enterprise>

    2. Note: All of the source machines that use the same network installation must copy merc_webtrace to the identical directory path on their local disk, for example, /local/<LoadRunner Enterprise>, because all of them use the same mdrv.dat.

    3. Add the following line to the <LoadRunner Enterprise_installation>/dat/mdrv.dat file, in the [monitors_server] section:

    4. ExtCmdLine=-merc_webtrace_path /local/xxx

    5. Log in to the source machine as root.

    6. Type: cd LoadRunner Enterprise_installation/bin to change to the bin directory.

    7. Type: chown root merc_webtrace to make the root user the owner of the merc_webtrace file.

    8. Type: chmod +s merc_webtrace to add the s-bit to the file permissions.

    9. To verify, type ls -l merc_webtrace. The permissions should look like:
      -rwsrwsr-x.

  3. Connect to the Linux Source Machine Through RSH

    Follow these instructions if the Controller is connected to the source machine through RSH (default connection mode). In this case you do not need to activate the agent daemon.

    Before running the Network monitor the first time, you enter an encrypted user name and password in the Network monitor configuration file.

    1. On the LoadRunner Enterprise host machine, type cd <LoadRunner Enterprise installation>/bin to change the bin directory.

    2. Run CryptonApp.exe.

    3. In the Password box, type your RSH user name and password, separated by a vertical bar symbol. For example, myname|mypw.

    4. Click Generate. An encoded string is displayed in the Encoded string field.

    5. Click Copy to copy the encoded string to the clipboard.

    6. Add the following line to the <LoadRunner Enterprise_installation>/dat/monitors/ndm.cfg file, in the [hosts] section:

    7. Host = <encrypted string copied from clipboard>

    8. Close and open the current performance test. LoadRunner Enterprise reads the updated configuration file and recognizes the source machine for monitoring.

  4. Connect to the Linux Source Machine Through the Agent

    Follow these instructions for activating agent daemon on the source machine if the Controller is not connected to the source machine through RSH.

    1. Type m_daemon_setup -install from the <LoadRunner Enterprise_installation>/bin directory.

    2. Make sure that the agent daemon is running whenever you activate the Network monitor.

    3. To stop the Network Delay Monitor agent daemon, type m_daemon_setup -remove.

Back to top

See also: