1

Checking for RHEL version

Session Manager requires at least version 8.4 of Red Hat Enterprise Linux. Re-install the virtual machine with a supported version of Linux.

2

Checking virtualization environment

Session Manager supports deployment in a virtualized environment. Session Manager does not support deployment on baremetal. Use a virtual machine to install Session Manager.

3

Checking RPM dependencies

Failure of this test indicates that the RPMs currently installed does not meet Session Manager requirements. 

4

Checking number of processors

If a profile is passed to the installer, the installer checks the number of CPUs versus the required amount by the profile.  If no profile is supplied, the installer uses Session Manager Profile 1 (3 CPUs). Ensure that the number of CPUs assigned to the virtual machine meets the desired profile.

5

Checking memory

If a profile is passed to the installer, the installer checks the amount of memory versus the required amount by the profile.  If no profile is supplied, the installer uses Session Manager Profile 1 (5132 MB). Ensure that the amount of memory assigned to the virtual machine meets the desired profile.

6

Checking available disk space on root partition

Session Manager requires at least 8 GiB of free disk space on the root partition for the installer to run. Clear some space and re-run the installer.

7

Checking available disk space on /var/lib directory (if applicable)

Session Manager needs at least 12 GiB of free disk space in /var/lib for profiles 1 & 2, 15 GiB for profiles 3 & 4, and 22 GiB for profiles 5 & 6. Clear or add some space under /var/lib and re-run the installer.

8

Checking user permissions

You must run the installer as a root user.  Re-run the installer as a root user.

9

Checking IPv6

Session Manager requires IPv6 be enabled even if IPv6 is not used. Make sure that kernel option ipv6.disable=1 is not present and re-run the installer.

10

Checking installed Avaya applications

Do not install other Avaya applications on the virtual machine created for deploying Session Manager.

11

Checking rsyslog status

Enable Syslog service to generate installation logs. Start rsyslog prior to running the installer (systemctl start rsyslog).

12

Checking network interfaces

Session Manager requires two network interfaces:

• Out of Band Management

• Public (SIP/HTTP)

Reconfigure the virtual machine for two network interfaces.

13

Checking network naming

Session Manager requires the network interface names as eth0 and eth1. If this test fails, allow the installer to rename the network interfaces.

14

Checking eth1 configuration

Session Manager takes control of eth1 interface for the SIP networks and overwrites any existing configuration. This is a warning only. If the install continues, then Session Manager overwrites the existing eth1 configuration.

15

Checking Listening ports

Resolve any port conflicts re-run the installer. Refer the port matrix document for the ports necessary for Session Manager's correct operation.

16

Checking /home directory access

The Session Manager installer creates several new users. Many of these users require a home directory. If the /home directory is not accessible (for example, configured with autofs) then the installer will not be able to create the users. If /home is not available for new users, then update /etc/defaults/useradd to a writable home directory.