Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

NAM Probe software dependencies and conflicts

When you use the recommended kickstart installation procedure to install Linux (see Installing Linux with kickstart), almost all packages that NAM Probe software depends on are also installed.

  • If you have used the kickstart, you probably don't need this help topic.
  • If you have installed Linux using a different method, however, dependencies may not be satisfied and software conflicts may occur. Resolution steps are described below.


Systems installed without the recommended kickstart method can be adjusted to provide full compatibility with the NAM Probe software. You can use the NAM Probe software installation script (upgrade.bin) as an aid to installing the missing pieces of software on your custom system. The update procedure depends on the yum software manager, which automatically installs missing packages from the repository pointed by you. Supported repository locations include:

  • Red Hat Network

  • Red Hat Enterprise Linux installation disk

  • Local yum repository (prepared with the createrepo command)

Each time you run the NAM Probe software installation script, the system is checked for packages necessary for further installation. On a dependency check fail, you are prompted to run the script with a parameter required to start dependencies resolution.


To run the NAM Probe software installation script and successfully complete the installation or upgrade, you must first install Perl and yum .

Parameters for testing system and verifying software dependencies

Without modifying the system, you can test to verify what actually needs to be done before the monitoring software can be installed. Supply the upgrade.bin with one of the following parameters:

  • --test-system
    Displays the system readiness status regarding NAM Probe software installation. The report lists the missing packages plus a list of enabled services or features that affect NAM Probe performance.
  • --list-missing-deps
    Displays a list of the missing packages required by NAM Probe on this particular system.
  • --list-all-deps
    Displays a general list of all rpm packages required by NAM Probe (including the packages that have already been installed and packages you still need to install). Note that the NAM Probe installation scripts list only the packages on which the software is directly dependent. The listed packages may have further dependencies that also need to be resolved and are pulled in automatically by package management software such as yum .

Sample test summary on a system installed without the kickstart

In the following sample output, you can see

  • A sample command using the "--test-system " parameter
  • Sample output, including a system description and a list of missing dependencies

Linux packages required by NAM Probe

The following is a list of Red Hat Enterprise Linux 7 packages the NAM Probe software directly depends on.

  • All of these packages must be installed before using upgrade.bin to install the NAM Probe software.
  • Other dependencies may be pulled in while installing the listed packages.
Tomcat conflict

If you have tomcat jss installed on your NAM Probe, remove it before upgrading.

  1. Log on to the NAM Probe as user root.
  2. Execute the following command from the system prompt:
    [root@AMD ~]# rpm -e tomcatjss
Why NAM Probe needs Wireshark?

The NAM Probe depends on Wireshark just to get one of its libraries - mergacap. This is the most convenient tool to merge the pcap trace files captured by the NAM Probe using the rcon nfdump command. The NAM Probe itself does not run Wireshark. See nfdump command for details.

In addition to the software that the NAM Probe uses for running and monitoring traffic (see list above), we recommend installing the following packages for maintenance purposes:


These packages are not installed during kickstart installation but can be pulled in when you install the NAM Probe software dependencies with the help of the installation script.

Parameters for resolving software dependencies

Depending on the repository location, you can use one of the following upgrade.bin parameters to facilitate the installation of the missing packages:

The missing packages will be installed from the Red Hat Network. If the machine has an active Internet connection and is registered with the Red Hat Network, the existing repository will be used. Other working repositories may be used depending on the actual machine configuration.

--install-deps-from-url [URL]
The missing packages will be installed from a yum repository in a specified location, where [URL] is a reference to the location containing the packages and where you ran the createrepo command. The allowed protocols are http://, ftp:// and file:/// . For example:

--install-deps-from-url **
Note that if the URL contains characters outside the ASCII set, the URL has to be converted to ASCII format using URL encoding. URLs cannot contain spaces. URL encoding normally replaces a space with a %20 representation.


When missing dependencies are pulled from the installation source, the script also silently adds packages necessary for NAM Probe maintenance. If you want to omit installation of these packages, use the --skip-recommended parameter together with --install-deps-from-*[source]*. The order of parameters is not important. For example:

upgrade.bin  --install-deps-from-net  --skip-recommended.

Each time you use the parameters to automate the dependencies resolution, the default yum repositories are supplemented with a temporary configuration pointing to the repository indicated as the parameter value. The original configuration is restored after the script ends. Note that if the Red Hat Network subscription is valid and yum can connect to the Internet, this package source will always take precedence.

Note that the NAM Probe installation scripts list only the packages on which the software is directly dependent. The listed packages may have further dependencies that also need to be resolved and are pulled in automatically by package management software such as yum .

Next steps