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
yumrepository (prepared with the
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
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:
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.
Displays a list of the missing packages required by NAM Probe on this particular system.
Displays a general list of all
rpmpackages 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
Sample test summary on a system installed without the kickstart
In the following sample output, you can see
- A sample command using the "
- Sample output, including a system description and a list of missing dependencies
[root@AMD CDROM]# ./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin --test-system AMD Installation and Upgrade Utility, Copyright (C) 2005-2016 Dynatrace Installation version: AMD 12.04.11.3194 with OpenSSL support Installation architecture: x86_64 Installation type: fresh installation Installation started on: Sun Jan 16 02:40:41 CST 2016 List of missing dependencies: apr-util bind-utils boost compat-expat1.i686 gcc hal libicu libstdc++.i686 lsof net-snmp net-snmp-perl net-snmp-utils ntp opencryptoki openssl098e pciutils perl-XML-Parser perl-XML-Simple stunnel time tomcat6 xerces-c kernel-devel java-1.8.0-openjdk
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.binto install the NAM Probe software.
- Other dependencies may be pulled in while installing the listed packages.
apr apr-util bind-utils boost bzip2 crontabs gcc gperftools-libs grub2 gzip kmod libicu libunwind libxslt lsof make net-snmp-libs numactl-libs ntp opencryptoki openssl passwd pciutils perl-Env perl-Switch perl-XML-Parser perl-XML-Simple rpm sed stunnel sudo tar tbb time tomcat which xerces-c yum java-1.8.0-openjdk wireshark
If you have
tomcat jss installed on your NAM Probe, remove it before upgrading.
- Log on to the NAM Probe as user
- Execute the following command from the system prompt:
[root@AMD ~]# rpm -e tomcatjss
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.
Additional Linux packages recommended for NAM Probe
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:
tcpdump openssh openssh-clients openssh-server vim-minimal
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.
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
file:/// . For example:
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
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:
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
- Analyze the list of NAM Probe software dependencies. For more information, Parameters for Testing System and Verifying Software Dependencies.
- Use an upgrade script with a parameter to pull all necessary files from the Linux installation medium, Red Hat Network, or local repository. For more information, see Resolving NAM Probe software dependencies.