Upgrading NAM Probe

Renamed components after upgrade from NAM 2017 May release to Dynatrace NAM 2018 release:

DC RUM 2017 May release Dynatrace NAM 2018 release
RUM Console NAM Console
Central Analysis Server (CAS) NAM Server
Advanced Diagnostic Server (ADS) Advanced Diagnostics on Demand feature of NAM Server
Agentless Monitoring Device (AMD) NAM Probe

Upgrade the AMD software using the upgrade packages provided by Dynatrace.

Warning
Red Hat Enterprise Linux 5 and 6 are not supported in DC RUM 2017 or NAM. Migrate to a supported release before performing this procedure. See:

Log on to the probe machine as the root user.

Get the latest probe installer.

Test the target machine for system readiness.
Go to the directory with the upgrade program and run it with the --test-system parameter. Review Installation and upgrade options - File options for testing for other upgrade.bin testing parameters.
For example:

[root@AMD ~]# ./upgrade-amd-17-00-00-1971-b001.bin --test-system
  • If no system readiness issues are found, you will see a summary message that finishes with a line such as
    "No missing dependencies, it is OK to install the probe software."

  • If system readiness issues are found, follow the instructions on the screen. You may be prompted to install missing software or disable services that affect probe performance. For more information, see Installing Linux without kickstart or AMD software dependencies and conflicts.

Important
An updated Linux kernel may be installed as an effect of a software compatibility check. If this happens, a system restart is necessary so that the proper kernel version is in use. For more information, see Resolving Linux kernel-related compatibility issues.

Run the selected upgrade file in the installation directory.
At the command line prompt, type: ./file_name   with the Mandatory parameters for installation where file_name is the name of the upgrade file.
For example:

[root@AMD ~]# ./upgrade-amd-17-00-00-1971-b001.bin --automatic --licenses-type eservices
  • The probe installation and upgrade does not recognize symbolic links. The install script will leave a custom folder installation, ignore the symbolic links, and install a new version in the following folders:

  • /usr/adlex
    /var/spool/adlex
    /var/log/adlex
    To use a custom installation location, you need to use mounting points on separate partitions.

  • If the installation script warns after setup that the available disk space is below the minimum space required, you must make a suitable amount of free disk space available before continuing.

Optional: Select the correct SSL engine (applies to nCipher support only).
The installation procedure performed by the upgrade file may not be able to detect the exact type of the nCipher accelerator card (nShield or nFast), in which case it configures the probe for nShield. If the card installed is not nShield, you must manually modify the appropriate configuration property after the upgrade file is executed. To do this, open the /usr/adlex/config/rtm.config configuration file and find the ssl.engine property, which defaults to

 ssl.engine=nshield

If the installed card is nFast, change the setting from nShield to nfast .

Reboot the probe to complete the installation.