This procedure describes how to install Linux on the NAM Probe platform.
To create a complete NAM Probe installation, you need to:
The NAM Probe platform must run a supported version of Linux.
- Instructions generally apply equally to Red Hat Enterprise Linux and CentOS Linux.
- This procedure uses the kickstart installation method and the installation script provided on installation media to install Linux. If you want to use an existing Linux installation, or you are unable to use the kickstart in your work environment, see Installing Linux without kickstart.
- If the target machine is already running a supported Linux, you may not need to repeat the OS installation procedure. However, you still need to walk through the installation procedures to verify system readiness for NAM Probe software installation.
Before you begin
Have the official Linux distribution ISO handy. See Supported OS and SQL versions to make sure you are using a supported version.
Set the BIOS to boot from either DVD/CD-ROM or USB.
- For DVD/CD-ROM installations, burn the downloaded ISO image onto a DVD/CD-ROM media.
- For USB installations, follow the Red Hat instructions (external link) on how to create a bootable USB drive with a Linux installation. Add the Dynatrace provided kickstart file to the root of the Linux installation USB drive or stick.
Optional: Access to the internet is not required to install Linux, but it is necessary to register Red Hat Enterprise Linux and update or install additional repositories.Note
Red Hat Enterprise Linux is sold on a per-socket-pair basis so that the prices in the vendor's directory affect every two populated sockets in the server. Choose a subscription based on the target hardware architecture for your NAM Probe. For more information on operating system licensing, refer to http://www.redhat.com/).
Except where noted, the NAM Probe has the same functionality and performance on all supported versions of Linux.
Insert the Linux disk or the USB stick.
Reboot the machine and allow the boot menu to appear.
If your system uses the UEFI firmware:
Select the Install Red Hat Enterprise Linux 7.x option.
[TAB] to edit the selected option.
Append the location of the kickstart file to the linuxefi command.
For kickstarts located on a DVD/CD-ROM use:
For kickstarts located on a USB :
[ENTER] to start installing Linux with the modified option.
Skip to step 5 of the installation procedure.
[Esc] to exit the boot menu.
boot: prompt, type the command to use the kickstart script located on the Dynatrace DVD 2 in the
AMD folder or the root of the USB stick.
DVD/CD-ROM installation paths assume that the system hardware contains a physical DVD/CD-ROM drive. External DVD/CD-ROM devices on the USB port may require the use of the USB installation paths even if a CD-ROM media is used.
At the boot command type:
If you intend to install the NAM Probe with support for SSL acceleration cards, you can use the CD kit with appropriate installation files (for example, “Agentless Monitoring Device 12.04.00 with nCipher Support” CD kit) to submit the kickstart installation script to the installer. In this case you must indicate that the kickstart file is in the root of the CD:
At the boot command type:
You can always use the script located on the DVD 2 as the CD kit contains the
amdrhel7.cfg file to limit the number of discs used during installation.
Replace the Red Hat Enterprise Linux distribution media with the CD kit containing the kickstart installation script and press
Allow the kickstart script to load, re-insert the Linux installation media, and press
This example assumes that you have used a LiveUSB Creator which labels the USB as LIVE. If you have used a different tool to create bootable USB, the label may differ.
At the boot command type:
When the installation process finishes, press
[Enter] to reboot the system.
Confirm the installed version of Linux.
Log in as a
root user with a default password
Check the version numbers by using the
uname -snrv command.
[root@AMD ~]# uname -snrv Linux amdprobe 3.10.0-229.el7.x86_64 #1 SMP Thu Jan 29 18:37:38 EST 2015
Inspect the installation logs to find out if everything is installed correctly.
/root/install.log to verify that all software packages were installed successfully. Errors logged here may indicate that the NAM Probe software will not work properly due to failed dependencies. Errors recorded in
/root/install.log may be caused by faulty installation medium; if this occurs, either reinstall the failed packages manually or install the entire system again using another medium.
Check for any installation packages that are not available on the installation media.
NAM Probe software depends on the packages that might not be included with any of the installation disks. To display the list of packages that are required by the NAM Probe software but not installed in the system, run the installation script with
[root@AMD ~]# ./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin --list-missing-deps
Any missing packages can be installed manually or using an Internet connection. You can use the NAM Probe software installation script as an aid for installing the missing packages.
(Optional) Register your system with Red Hat Network.
If your machine is connected to the Internet, we recommend using Red Hat Network to install the NAM Probe dependencies and apply security updates to your Linux. To register the system and enable subscriptions, use the
Register your Linux in Red Hat Network.
subscription-manager register at the command prompt and enter the subscription username and password.
[root@AMD ~]# subscription-manager register Username: Password:
Attach the subscription to the registered system.
subscription-manager attach --auto at the command prompt.
[root@AMD ~]# subscription-manager attach --auto
What to do next
The kickstart script cannot configure some settings automatically, so you need to make these changes after the operating system installation.
If you are running a custom installation of Linux, you may not need to adjust most of the settings.
Change the password for the
Log in as the
root user with password
greenmouse and then issue the
passwd operating system command to modify the
root user password to a password of your choice.
The rest of this procedure should be performed as the
Set the time zone.
- To display supported time zones, type
timedatectl list-timezonesat the command prompt.
Once the list is displayed, write down the time zone that you wish to set.
[root@AMD ~]# timedatectl list-timezones Africa/Abidjan ... Pacific/Wallis
You can use
grep command to display only specific time zones. For example:
[root@AMD ~]# timedatectl list-timezones | grep America/N America/Nassau America/New_York America/Nipigon America/Nome America/Noronha America/North_Dakota/Beulah America/North_Dakota/Center America/North_Dakota/New_Salem
- To change the time zone, type
timedatectl set-timezone time_zoneat the command prompt.
In the command listed above, replace the
time_zonevariable with any of the values displayed in the supported time zones list.
[root@AMD ~]# timedatectl set-timezone Europe/Warsaw
Set the time and date.
Set the current time and date using the command:
[root@AMD ~]# timedatectl set-time 'YYYY-MM-DD HH:MM:SS'
Replace YYYY with a four-digit year, MM with a two-digit month, DD with a two-digit day of the month for the date, and for the time, HH with an hour, MM with a minute, and SS with a second, in two-digit form.
Note that the quotes as shown in the example above are required in this command to hide the special characters from the shell.
timedatectl command to view the current settings.
[root@AMD ~]# timedatectl Local time: Thu 2015-05-21 10:51:11 CEST Universal time: Thu 2015-05-21 08:51:11 UTC RTC time: Thu 2015-05-21 08:51:11 Timezone: Europe/Warsaw (CEST, +0200) NTP enabled: no NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at Sun 2015-03-29 01:59:59 CET Sun 2015-03-29 03:00:00 CEST Next Dst change: DST ends (the clock jumps one hour backwards) at Sun 2015-10-25 02:59:59 CEST Sun 2015-10-25 02:00:00 CET
Optional: Change the keyboard layout.
You can override the default keyboard map, which is “us” (“QWERTY”, LATIN-1). For the convenience of users logging in to the NAM Probe locally, the changes can be made either persistent from session to session or valid for only the current session. Note that a persistent change will affect other users, perhaps including users for whom a different layout is needed. In such cases, a temporary (session-only) change may be preferable.
- To change the keyboard layout temporarily, use the
This affects only the user who executes the command and remains in effect only until the end of the session or until the command is revoked.
To use, for example, the “AZERTY” PC keyboard layout, issue the
loadkeys azerty command.
To return to the default settings, issue the
loadkeys --default command.
To make a persistent change, edit the keyboard configuration file:
To find the names of available keyboard layouts, execute the
[root@AMD ~]# localectl list-keymaps ANSI-dvorak ... windowkeys
You can use
grep command to display only specific keymaps. For example:
[root@AMD ~]# localectl list-keymaps | grep pl-dvorak pl-dvorak pl-dvorak_altquotes pl-dvorak_quotes
- To change the currently used keyboard layout, type
localectl set-keymap layoutat the command prompt.
This change is global. The key map is loaded by startup scripts and requires that you restart your system for the changes to go into effect. When you enter your password, remember that the new key mapping will be active at the time of login.
[root@AMD ~]# localectl set-keymap pl-dvorak