Share this page

# Configure the Linux source machine for network monitoring

This topic describes how to configure a UNIX source machine before running the network monitor. To learn more about network monitoring, see Network monitoring overview.

In this topic:

## Assign permissions for a local installation

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

To assign permissions for a local installation:

1. Sign in to the source machine as root.

2. Type: cd <installdir>/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.

Back to top

## Assign permissions for a network installation

In a 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.

To assign permissions for a network installation:

1. Copy merc_webtrace from <installdir>/bin to anywhere on the local disk of the source machine.

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, since they all use the same mdrv.dat.

2. Add the following line to the <installdir>/dat/mdrv.dat file, in the `[monitors_server]` section:

`ExtCmdLine=-merc_webtrace_path /local/xxx`

3. Sign in to the source machine as root.

4. Type: `cd <installdir>/bin` to change to the bin directory.

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

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

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

Back to top

## 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.

To connect to the Linux Source Machine Through RSH:

1. On the OpenText Enterprise Performance Engineering host machine, type `cd <installdir>/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 <installdir>/dat/monitors/ndm.cfg file, in the `[hosts]` section:

`Host = <encrypted string copied from clipboard>`

7. Close and open the current performance test. OpenText Enterprise Performance Engineering reads the updated configuration file and recognizes the source machine for monitoring.

Back to top

## 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.

To connect to the Linux Source Machine Through the Agent:

1. Type `m_daemon_setup -install` from the <installdir>/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:

- Monitors

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: