Preparing for software-only deployments

Last Updated : May 27, 2024 |

About this task

Use this procedure to prepare the setup for software-only deployments.

Before you begin

  1. Create an RHEL instance with required resources and do the following:

    1. Ensure that the system is configured with RHEL 8 yum repository.

      For information about configuring the yum repository, see Red Hat documentation.

    2. Important:

      Avaya recommends installing only required RPMs to the system for security and stability. Do not install complete Red Hat system.

      In a software-only installation, the customer installs the Red Hat provided RPM updates. To avoid possible issues or incompatibilities with new RPMs, check the list of tested RPMs and follow the instructions in the PSN020617u that Avaya publishes periodically on the Avaya Support website.

    3. Create the required disk partitions.

      You must have the following partitions:

      • /var/lib/pgsql/data

      • /emdata

      • /perfdata

      • /swlibrary

      For information about the partitions, see System Manager disk partitioning.

    4. Ensure that the /etc/cron.deny file is available on the System Manager system. Do the following:

      1. If the /etc/cron.allow file is available, then delete it.

      2. If the /etc/cron.deny is not available, then create the /etc/cron.deny file on the System Manager system.

    5. Ensure that the network interface naming convention is configured to old network scheme names.

      System Manager requires old network scheme eth0 and eth1.

      Note:

      If you do not configure the old network scheme names, the deployment fails.

      For more information about creating RHEL instance, see the Red Hat documentation.

      For more information about supported Red Hat Enterprise Linux operating system versions, see Supported Red Hat Enterprise Linux operating system versions for Software-only Environment.

      For more information about the required resources, see Supported footprints information for respective environments.

Procedure

  1. For deploying System Manager 10.2 ISO, run the following command to install the openjdk libraries before installing the actual System Manager dependencies RPM to be consistent with 10.2.0.0 OVA patch.

    yum install java-1.8.0-openjdk-1.8.0.342.b07-2.el8_6.x86_64 java-1.8.0-openjdk-headless-1.8.0.342.b07-2.el8_6.x86_64 java-1.8.0-openjdk-devel-1.8.0.342.b07-2.el8_6.x86_64

  2. Log in to the RHEL instance as a default user and switch to the root account. To create a directory, run the following command: 
    mkdir /swlibrary/installer
  3. Download the Avaya Aura® application ISO to the RHEL instance.
  4. To mount the ISO, run the following command: 
    mount -o loop AvayaAuraSystemManager-10.2.x.0.xxxxxx_vxx.iso /mnt
  5. To copy the ISO content to the directory, run the following command: 
    cp -rvf /mnt/* /swlibrary/installer
  6. Run the following command to unmount the /mnt directory: 
    umount /mnt
  7. Delete the downloaded ISO file.
  8. To install dependencies, run the following command: 
    yum install SMGR-Dependencies-0.1-1.noarch.rpm -y
  9. Set the umask to 0022.
  10. Ensure that the Defaults requiretty setting is not available in the /etc/sudoers file.
  11. Ensure that the log_group permission is set to admin in the /etc/audit/auditd.conf file.
  12. To configure the python to version 3 in RHEL 8, run the following command: 
    alternatives --set python /usr/bin/python3

    The default python is python3.

    If the alternatives command fails, then use the following commands to set the python3 link:

    1. unlink /usr/bin/python

    2. ln -s /usr/bin/python3 /usr/bin/python

  13. Set the system-wide crypto policy to LEGACY on the RHEL 8.x and later operating system by running the following command.

    update-crypto-policies --set LEGACY

    For details, see System-wide crypto policy.

  14. Disable SELinux, if already enabled.

    For disabling SELinux, see the Red Hat documentation.

  15. To remove cloud-init package for AWS, run the following command: 
    systemctl stop cloud-init
systemctl disable cloud-init
yum remove cloud-init -y
  16. Reboot the system.

Next Steps

Check the environment.

Related information
Checking the environment