Upgrade the AMD software from AMD 2017 to NAM Probe 2018 using the upgrade packages provided by Dynatrace.
To avoid confusion, be aware that primary components are renamed during upgrade from DC RUM 2017 May to NAM 2018:
|DC RUM 2017 and older||NAM 2018, NAM 2019|
|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|
Red Hat Enterprise Linux 5 and 6 are not supported in DC RUM 2017. Migrate to a supported release before performing this procedure. See:
Log on to the AMD as
Mount the latest AMD upgrade disc.
Insert the AMD upgrade disc into your drive and mount the drive with the
mount /dev/cdrom /mnt command.
[root@AMD ~]# mount /dev/cdrom /mnt
If you are working with a different installation, your device mount location may be different - you can skip to Step 4.
Go to the upgrade directory.
Change your current working directory to
AMD on the drive with the
cd /mnt/AMD command.
[root@AMD ~]# cd /mnt/AMD
Select the upgrade file.
For more information, see Installation and upgrade file names.
Test the target machine for system readiness.
Run the selected upgrade file with the
--test-system parameter. Review the File options for testing section for other
upgrade.bin testing parameters.
[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 AMD 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 AMD performance.
For more information, see Preparing the Operating System for AMD Software Installation or AMD software dependencies and conflicts .
Run the selected upgrade file in the installation directory.
At the command line prompt, type:
./file_name with the Mandatory parameters for upgrade where
file_name is the name of the upgrade file.
[root@AMD ~]# ./upgrade-amd-17-00-00-1971-b001.bin --automatic
When using the
--manual parameter, if any auxiliary packages are missing, the process stops and the missing package names are listed. If this occurs, use your Red Hat subscription repository or the system installation media to install the required packages. Note that the AMD 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
For more information, see AMD software dependencies and conflicts .
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 .
If the installation script discovers that, after setup, the available disk space is below the minimum space required, a message is displayed. If this happens, you must make a suitable amount of free disk space available before continuing.
Figure 2. Warning Messages on System with Insufficient Amount of Free Disk Space
Warning: Insufficient free disk space available. /usr/adlex/rtm/bin requires at least 2GB /var/log/adlex requires at least 1GB /var/spool/adlex/rtm requires at least 10GB
Optional: Select the correct SSL engine (applies to nCipher support only).
Because of hardware constraints, 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), and it configures the AMD for nShield. If the card installed is not nShield, you must manually modify the appropriate AMD 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
If the installed card is nFast, change the setting from
Reboot the AMD to complete the upgrade.
After the AMD is restarted, you can use the
ndstat command to view the installed packages and their versions.
Example of ndstat output after an upgrade.
[root@AMD ~]# ndstat === The default Java machine openjdk version "1.8.0_65" OpenJDK Runtime Environment (build 1.8.0_65-b17) OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) === Installed Java packages java-1.8.0-openjdk-headless-184.108.40.206-0.b17.el6_7.x86_64 java-1.7.0-openjdk-220.127.116.11-18.104.22.168.el6_7.x86_64 java-1.8.0-openjdk-22.214.171.124-0.b17.el6_7.x86_64 === Installed packages adlexrtm-ndw.126.96.36.1998-1.el6.x86_64 adlexv2page-12.4.0-20.el6.x86_64 adlexpage2trans-12.4.0-25.el6.x86_64 rtmperf-12.4.0-10.el6.x86_64 tomcat-amd-12.4.0-4.el6.x86_64 cpwrdlm-4.5.0-16.2.el6.x86_64 rtmgate-12.4.0-60.el6.x86_64 cba-12.4.0-1308.el6.x86_64 cba-agent-12.4.0-66.el6.x86_64 nfc-12.4.0-1308.el6.x86_64 Installation type: rtm