Deploying Avaya Aura® Session Manager or Branch Session Manager in a software-only environment

Last Updated : Jul 16, 2026 |
Prolog information
Metadata
Keywords:
Note:
The deployment of Avaya Aura® applications as software only is available but a restricted offer for net new deployments and requires Avaya Aura® BU approval before proceeding. If you have a business requirement to deploy Avaya Aura® as software only, please get in touch with your Avaya Sales team. Existing customers using software only deployments continue to be supported.
Before you begin
  • Create a new virtual machine for the software-only installation. For creating a virtual machine, refer to the corresponding third-party documentation.
  • Install Linux on the virtual machine.
  • Ensure that TMOUT variable is not set to read-only.
  • Ensure that yum is configured on the virtual machine. For more information, see Red Hat documentation.
  • Deploy System Manager. For more information, see the specific System Manager deploying guide on Avaya Support website.
  • Download the application ISO file to the virtual machine.
  1. Log in to the system as a root user.
  2. Run the following command to mount the ISO file:
    ADDITIONAL INFORMATION: mount -o loop,ro Session_Manager_10.2.x.x.xxxx.iso /mnt
  3. Run the following command to remove the cloud-init packages:
    ADDITIONAL INFORMATION: yum erase cloud-init google-compute-engine
    Some of these packages are installed only on cloud based installations such as AWS.
  4. Run the following command to install the required RPMs:
    ADDITIONAL INFORMATION: yum install /mnt/avaya-sm-setup-10.2.x.x.xxxx-1.noarch.rpm
    The avaya-sm-setup RPM is an empty RPM that lists the required RPMs for Session Manager.
    For the list of tested Avaya Aura® Software-Only RPMs, see Avaya PSN020361u at PSN020361u.
    Important:
    The PSN PSN020361u provides details of the latest RPMs tested with Avaya applications. These RPM versions should be used when installing and updating the operating system. Using the RPM versions that are not tested might result in an operational impact to the Avaya application.
  5. Run the following command to start the installation:
    ADDITIONAL INFORMATION: /mnt/install-SM
    The installer performs the following checks to verify that the environment is suitable for Session Manager:
    • The version of Red Hat is at least 8.4.
    • The environment is virtual and not baremetal.
    • All the RPM dependencies are installed.
    • The number of processors meets the provided profile. If a profile is not specified, then Profile 1 CPU requirements are used.
    • The amount of memory for the provided profile. If a profile is not specified, then Profile 1 memory requirements are used.
    • The amount of disk space available on the root partition.
    • The amount of disk space available on the /var/lib directory. This check is skipped if the operating system is configured with only one partition.
    • All users can read the /opt directory (755 permissions).
    • Root user is being used to run the installer.
    • IPv6 is enabled in the kernel.
    • No other Avaya applications are installed.
    • Remote syslog is running.
    • Minimum 2 network interfaces exist.
    • The network interfaces are named eth0 and eth1.
    • Network interface eth1 configuration does not exist.
    • Identify any port conflicts.
    • The installer can write in the home directory.
    If any check fails, refer to the troubleshooting section.
  6. Optional: If net.ifnames=0 is not specified during the Linux installation, enter Y to allow the installer to automatically rename the interfaces and repeat Step 2 and Step 5 after reboot.
  7. On the End User License Agreement page, click Accept.
  8. On the System Configuration page, read the warning, and click Accept.
  9. Click Continue to acknowledge system reboot after installation.
  10. On the Please select installation type window, select the required installation type.
    ADDITIONAL INFORMATION:
    Important:
    The installation type must match the profile values used while creating the virtual machine. If the virtual machine is configured with the Session Manager profile, you must select the Core Session Manager. If the virtual machine is configured with the Branch Session Manager profile, you must select the Branch Session Manager as a required installation type.
  11. Enter the IP address of the primary System Manager and click OK.
  12. In the Enrollment password field, type the enrollment password.
  13. In the Confirm Password field, re-enter the enrollment password and click OK.
  14. On the Enhanced Access Security Gateway (EASG) page, read the EASG information, and click OK.
  15. Select one of the following and then click OK:
    • Enable EASG (Recommended)
    • Disable EASG
  16. In the Enter Login ID to use for the customer account field, type a new username to use as a customer account, and click OK.
  17. In the Enter password field, type the customer account password.
  18. In the Confirm Password field, re-enter the customer account password and click OK.
  19. On the Verify Settings page, confirm all the settings and click Continue.
    ADDITIONAL INFORMATION:
    After the installation is completed, reboot the virtual machine.
    Note:
    Session Manager supports running with FIPS enabled. FIPS should be enabled after installing Session Manager. Session Manager provides fips_mode.sh for enabling FIPS. To enable FIPS, run:
    fips_mode.sh enable