Installation and upgrade options

The NAM Probe is a set of regular applications. This set of applications is installed or upgraded by a single script (upgrade.bin). Each supported hardware platform and operating system requires a dedicated upgrade.bin script to install the NAM Probe software.

A number of software dependencies may need to be resolved before the NAM Probe software installation completes. They can be resolved automatically, using the upgrade.bin script and --automatic parameter, or manually with the --manual parameter and updates referred in NAM Probe software dependencies and conflicts.

Important

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

File name

The target operating system, hardware architecture, and release number can be read from the installation script file name. The following convention is used:

upgrade-[*SSL decryption engine* ]-[*os version* ]-[*hardware architecture* ]-ndw-[*release number* ]-b001.bin

where four pieces of information are encoded:

  • [SSL decryption engine]
    Indicates the SSL support built into this variant of the NAM Probe software:
    • amd = OpenSSL on NAM Probe
    • amd__ncipher_pkcs11 =  nCipher on NAM Probe
    • amd__ncipherXC_pkcs11 =  nShield Connect XC on NAM Probe
  • [os version] Indicates the Linux release. Example: amdos7
  • [hardware architecture] indicates the target architecture. Example: x86_64
  • [release number] indicates the NAM Probe version (major release number, minor release number, and patch number)

Installation software in the community downloads

The installation file is available in several versions depending on the hardware architecture, operating system version, and SSL decryption engine. The Dynatrace Community Downloads page contains the installation files.

The following is an example name of an installation file for Red Hat Enterprise Linux 7:

upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin

Choose a file labeled x86_64 for 64-bit operating system versions. The version number, which is indicated by the digits following the string ndw in the file name, may be different from the number on your distribution disk.

Choose a file labeled amdos7 for installation on Red Hat Enterprise Linux 7.

File options for installing

Specific parameter must be used with the upgrade.bin during an installation. You must indicate whether the installation script should automatically configure your system or attempt to upgrade the system as it is and, you must specify the license type for your installation.

Mandatory parameters for installation:

  • --automatic or--manual
    If you want the installation script to automatically install/upgrade missing dependencies, disable the nonessential service and modify the required services configurations, use the --automatic  parameter.

    If you want the installation script to upgrade without any system changes, use the –manual  parameter. The installation script will attempt to install/upgrade the monitoring software on the existing system, but it will stop and report changes and updates that need to be performed if the system does not meet the requirements. To learn more about the parameters on testing system or resolving software dependencies, see NAM Probe software dependencies and conflicts.

  • --licenses-type <lic-type>
    Specifies the license type (New installations only); values: dlm, eservices
    Use dlm  to install NAM Probe using a classic, DLM based licensing scheme. Use eservices  to install the NAM Probe using eServices based licensing scheme.

    Note

    The --licenses-type values for releases before 12.4.11 use numbers instead of strings. 1 for DLM and 2 for eServices.

    For example, to install NAM Probe, using the DLM based licensing scheme, use the NAM Probe upgrade.bin like this:

    ./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin --licenses-type dlm
    

    To install NAM Probe using the eServices based licensing scheme, use the NAM Probe upgrade.bin like this:

    ./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin --licenses-type eservices
    

Optional parameters for installation:

  • --tmpdir="<directory>"
    Sets a temporary directory with permissions to launch the upgrade.bin script. Some system security policies do not permit scrip execution from the /tmp directory. Use this parameter to specify different temporary directory that has the execution permissions.

    [root@AMD ~]# ./upgrade-amdos7-x86_64-17-00-b1.bin --test-system
    
    Extracting upgrade.bin package to /tmp/upgrade-amdos7-x86_64-17-00-b1.bin..Done
    
    ./upgrade-amdos7-x86_64-17-00-b1.bin: line 221: /tmp/upgrade-amdos7-x86_64-17-00-b1.bin.pl: Permission denied
    
    [root@AMD ~]# ./upgrade-amdos7-x86_64-17-00-b1.bin --tmpdir="/root" --test-system
    
    Extracting upgrade.bin package to /root/upgrade-amdos7-x86_64-17-00-b1.bin.pl..Done
    
    AMD Installation and Upgrade Utility, Copyright
    (C) 2005-2017 Dynatrace LLC.
    
  • --set-user <username[:groupname]>
    The installation file option --set-user can be used to specify an unprivileged NAM Probe user. The --set-user option specifies or creates a user and the group to which this user belongs. A user created with this option has all the necessary permissions to configure and operate the NAM Probe software, but is not permitted to perform system-level operations. The following syntax specifies the user and a group during the installation: --set-useruser:groupFor example, to specify the user “peter” belonging to group “operators` ”, execute a command in the following format:

    [root@AMD ~]# ./upgrade-amd-17-00-00-1971-b001.bin --set-user peter:operators
    

    Since this option is available only in new installations, specifying the user and the group will automatically create, assign, and make use of the created users and groups during the installation process.

    --help

    Use the --help option for a list of parameters available during the installation mode:

File options for upgrading

Specific parameter must be used with the upgrade.bin during an upgrade. During the upgrade, you must indicate whether the installation script should automatically configure your system or attempt to upgrade the system as it is.

Mandatory parameters for upgrade:

  • --automatic or--manual

    Use --automatic if you want the installation script to automatically install/upgrade missing dependencies, disable the nonessential service, and modify the required services configurations.

    Use –manual if you want the installation script to upgrade without making any system changes. The installation script will attempt to install/upgrade the monitoring software on the existing system, but it will stop and report changes and updates that need to be performed if the system does not meet the requirements. To learn more about the parameters on testing system or resolving software dependencies, see NAM Probe software dependencies and conflicts.

Optional parameters for upgrade:

  • --tmpdir="<directory>"
    Sets a temporary directory with permissions to launch the upgrade.bin script. Some system security policies do not permit scrip execution from the /tmp directory. Use this parameter to specify different temporary directory that has the execution permissions.

    [root@AMD ~]# ./upgrade-amdos7-x86_64-17-00-b1.bin --test-system
    
    Extracting upgrade.bin package to /tmp/upgrade-amdos7-x86_64-17-00-b1.bin..Done
    
    ./upgrade-amdos7-x86_64-17-00-b1.bin: line 221: /tmp/upgrade-amdos7-x86_64-17-00-b1.bin.pl: Permission denied
    
    [root@AMD ~]# ./upgrade-amdos7-x86_64-17-00-b1.bin --tmpdir="/root" --test-system
    
    Extracting upgrade.bin package to /root/upgrade-amdos7-x86_64-17-00-b1.bin.pl..Done
    
    AMD Installation and Upgrade Utility, Copyright
    (C) 2005-2017 Dynatrace LLC.
    

File options for testing

Without modifying the system, you can run the script to check whether all software dependencies are resolved.
If this occurs, use your Red Hat subscription repository or the system installation media to install the required packages. 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.

  • --test-system
    Tests the system readiness for the NAM Probe software installation. Lists missing packages, services and features affecting the NAM Probe performance.
  • --list-missing-deps
    Lists missing packages required for NAM Probe installation on this particular system.
  • --install-deps-from-net
    Installs NAM Probe software dependencies from Red Hat Network (if enabled).
  • --install-deps-from-media
    Installs NAM Probe software dependencies from Linux installation disk or pendrive.
  • --install-deps-from-url <url>
    Installs NAM Probe software dependencies from a custom yum repository.
  • --backup-path
    Sets path to the temporary directory used during the installation (default: system temp dir).

Uninstalling the NAM Probe

To remove the NAM Probe software from your machine, run upgrade.bin with the –-erase option. For example:

[root@AMD ~]#./upgrade-amd-17-00-00-1838-b001.bin --erase

To clear the system completely, after you uninstall the software, you may need to remove the NAM Probe specific directories. Use the following commands:

rm -fr /usr/adlex
rm -fr /var/log/adlex
rm -fr /var/spool/adlex

Nonstandard boot loader

Default installations of standard distributions of Red Hat Enterprise Linux use the GRUB 2 boot loader. If the number of CPUs is eight or more, the NAM Probe software installation or upgrade script updates kernel parameters in the boot loader configuration file. The installation script on nonstandard distributions, or installations using a boot loader other than GRUB, generate the following warning:

Warning: Kernel parameters were not processed due to '/boot/grub/grub.conf' file error: No such file or directory

Though the installation or upgrade will complete successfully, you must modify the boot loader configuration file manually and set the kernel parameters. Edit the configuration file of your boot loader, set the following parameters, and reboot the system.

isolcpus=0
rhash_entries=8192