Page Comparison

Ensure you have at least one network card installed and configured with full access to network services, such as DNS and NTP (the same as your Gateways). Some configurations, such as the Cell environment, require 2 network cards. See Network Preparation for more details.

Root access

Installation The installation must be performed by a root user. You cannot use sudo instead. However, you may run it after running the command: su -
The installation will add entries to the PATH variable using .bash_profile. Make sure these entries are maintained during the login sequence (do not override with a fixed PATH).
Do not use script command during the login sequence to make typescript of the terminal session for audit, as this will cause various scripts to hang.

Disks, mount points / file systems and logical volumes

Once configured, you may verify there are at least 3 disks using the following command:

Tip: to create the mount points / file systems during RHEL installation:

The Store service requires a dedicated OS user and group to run. Consider executing the following command:

groupadd storeadms && useradd -g storeadms -md /home/storeadm -s /bin/bash storeadm

The supported OS locale is en_US.UTF-8. Check the OS Locale Configuration and change it if necessary.

Setup DNS

Setup DNS - your network admin may need to assist you with this action. Make sure you can ping to your LDAP, Mail/SMTP Server, NTP Server.

For RedHat only: Your system might need to be registered and subscribed to the Red Hat Customer Portal to be able to install all prerequisites using yum.
Registration and subscription may differ between organizations, so use the following commands just as a demonstration:

subscription-manager register
subscription-manager attach --auto
subscription-manager repos --enable=rhel-7-server-rh-common-rpms
subscription-manager repos --enable=rhel-7-server-optional-rpms


Setup NTP - it has to be the same one configured in your IBM DataPower Gateways.

• Consult your Linux and network admin about the proper way to configure this service.
• For RHEL 7.x

  • Ensure the NTP RPM is installed. Consider executing the following commands:
    

    yum install ntp
ntpdate <ntp server hostname>
systemctl enable ntpd.service
systemctl start ntpd.service

• For RHEL 8.x
  

  • Ensure the Chrony RPM is installed. Consider executing the following commands:
    

    yum install chrony
chronyd -q 'server {ntp_server_name} iburst'
systemctl enable chronyd.service
systemctl start chronyd.service



Verify that the /etc/hosts file includes an entry with your server name mapped to your external server IP.

To find your server name, you may execute the command:

hostname

Required RPMs

Verify the existence of the following RPMs from the official RedHat/CentOS yum repositories:

• httpd version 2.4.6-67 and above (together with the following dependencies: mailcap, apr, httpd_tools)
• mod_ssl
• mod_proxy_html
• curl
• wget
• unzip
• iptables
• iptables-services
• bc
• fontconfig

The installation is usually performed by executing yum:

yum install -y httpd
yum install -y mod_ssl
yum install -y mod_proxy_html
yum install -y curl
yum install -y wget unzip iptables iptables-services bc
yum install -y unzip
yum install -y iptables
yum install -y iptables-services
yum install -y bc
yum install -y fontconfig

If this command fails to find the packages, you should manually download the RPM files and install them.

Ensure the httpd service is enabled and started by executing the command:

systemctl enable httpd.service && systemctl start httpd.service

• This RPM is not always accessible from existing repositories. Try first to install it by executing the command: yum install mod_proxy_html
  If you get the error "No package mod_proxy_html available. Error: Nothing to do", you will need to download the RPM yourself, using one of the following methods:
  • Method 1 - download the RPM
    • Find your httpd version by executing the command: rpm -qa | grep httpd
    • The system will print something resembling httpd-2.4.6-67.el7_2.4.x86_64. This is the mod_proxy version you need to download.
    • For RedHat only - Download the mod_proxy with the correct version from the following url:
      https://access.redhat.com/downloads/content/mod_proxy_html/2.4.6-45.el7/x86_64/f21541eb/package (change the version part of the URL to match the httpd version you found above). Use wget or any other mechanism to download, and ensure to place the RPM inside the /tmp directory of the pre-installed OS server.
    • Install the RPM by executing the command:  rpm -Uvh mod_proxy_html-2.4.6-67.el7_2.4.x86_64.rpm (Note: your version may vary, as described above)
  • Method 2 - add a repository and install it from the repository using the commands (For RedHat only)
    subscription-manager repos --enable=rhel-7-server-optional-rpms
yum install mod_proxy_html

service && systemctl status httpd.service

In case you are using yum, it is recommended to clean its cache to make sure there is enough space in /var (yum cache can take a lot of the space there). To clean yum cache, execute the command:

yum clean all

Installation file and environment

Ensure your /tmp directory has at least 1GB of free space.

Installation from a different directory is possible. If you opt to run the install from a directory other than /tmp, ensure that this directory:

• • Has at least 1GB of free space.
  • Is NOT one of these folders: /app, /logs, /data, /shared, /installs.

Download the CEF file and transfer it to the installation directory (e.g. /tmp) on the pre-installed OS server.

Execute the following command from the pre-installed OS server terminal:

chmod 755 ./<File Name>

It is recommended to let DPOD optimize the Operating System parameters to ensure performance.

Please review the script before executing it and make sure the OS parameters values match your organization's policy.

/app/scripts/tune-os-parameters.sh

When DPOD is later installed, it will check the OS parameters. Critical compatibility checks must be satisfied in order to install the system, while other informational compatibility checks will make sure the operating system is optimized and will notify if changes are recommended to be made. Please take time to review the results of these checks after installation, and perform all applicable optimizations. The compatibility checks report can be found in /installs/logs/appliance_checks-<date time>.log.