Installing the MPP software interactively

Last Updated : Jun 05, 2026 |

Before you begin

  • Make sure you have installed the EPM software on the primary EPM server as described in Installing the EPM software on the primary EPM server.

  • Complete the MPP server installation worksheet and have it available to help answer the questions raised during the installation.

  • Download any patches for Avaya Experience Portal Release 8.1 from the Avaya Support website at http://support.avaya.com.

  • Ensure that you download the Avaya Experience Portal ISO file from the Avaya Support website and burn it to a DVD.

  • Check if default umask is set to 027. If it is not set to 027, the installer asks if you want to set it to 027. If you select 'yes', the installer applies this setting to the OS. If you select 'no', the installer exits.

Procedure

  1. Log into the server on which you want to install the primary EPM software.

    • Log on to the local Linux console as root.

    • Or log on remotely as a non-root user and then change the user to root by entering the su - root command.

    Note:

    By default, the craft and sroot users are disabled in Avaya Experience Portal 8.1 Avaya Enterprise Linux fresh installations. Avaya Service Login accounts can only access the Avaya Experience Portal system if they are EASG protected.

  2. Insert the Avaya Experience Portal 8.1 software installation DVD into the DVD drive of the server.
    Tip:

    These instructions assume that you are going to access the Experience Portal installation DVD by mounting the appropriate DVD drive on the target system. If you want to access the installation DVD files from a shared network directory or a local directory, you can copy the files from the Experience Portal installation DVD to that directory. However, that directory needs to be readable by all users on the system because the Experience Portal installation script changes users during execution. If the directory is only readable by the root user, the installation script will encounter errors and will not complete successfully. You also need to ensure the directory name does not contain spaces. If there are spaces in the directory name, the installation script will encounter errors and will not complete successfully.

  3. Mount the Avaya Experience Portal 8.1 software installation DVD. The mount command depends on the server's hardware and operating system.

    • If you are working with Avaya Enterprise Linux, mount the DVD by entering the mount /mnt/cdrom command, where /mnt/cdrom is the mount point typically associated with the DVD drive in the fstab file.

    • If you are working with a supported version of Red Hat Enterprise Linux Server, to mount the DVD:

      • Run the mkdir -p /media/cdrom command.

        Note:

        This command is required only if the /media/cdrom mount point does not exist.

      • Run the mount -o ro /dev/cdrom /media/cdrom command.

      Warning:

      When Red Hat Enterprise Linux Server automatically mounts the DVD, the files on the DVD are not executable. You must manually mount the Experience Portal installation DVD using the commands shown above.

  4. Change to the mount point directory.
  5. Enter the bash aepinstall.sh command and press Enter to start the installation script.

    The bash aepinstall.sh script checks to make sure the calling user has root privileges.

  6. Press Enter to continue.
  7. Read through the end user license agreement and select Y to accept the terms of the license agreement.

    Experience Portal automatically starts the PVI checker, which analyzes your system’s hardware and operating system configuration. The PVI checker does the following:

    • Checks to ensure that a non-root user account has been created.

    • Asks the user to confirm that one of these accounts is the non-root account the user has configured, and to set the password.

    • Checks for any missing pre-requisite RPMs and installs any if missing.

    • Creates a log file in /opt/Avaya/InstallLogs/pvicheck.log.

    • Checks if default umask is set to 027. If it is not set to 027, the installer asks if you want to set it to 027. If you select 'yes', the installer applies this setting to the OS. If you select 'no', the installer exits.

  8. After the configuration analysis is complete, the PVI checker displays a message stating whether all prerequisite checks passed followed by the first Prerequisite Status page.
  9. From the installation options, enter 3 to select Standalone MPP and confirm.
  10. Verify that the Primary EPM is online as the next step requires Primary EPM to be contactable.
  11. On the Primary EPM Server Location section, enter the Primary EPM hostname or IP address and confirm.

    This checks the connection to the Primary EPM. If the Primary EPM is not contactable, then this will fail and you will be again asked to enter the Primary EPM Location.

    Note:

    During the MPP software installation, if the MPP server does not have an EASG state, it will set the EASG state as the same EASG state of the Primary EPM. If the MPP server is set to disable EASG, ensure that you have access to the system without the Avaya Service Logins, and that you can get root access without using sroot.

  12. Experience Portal begins installing the software. During the install, it displays messages indicating its progress.

    The installation process can appear completed or stopped even though it is still processing and installing the software.

    Please wait until the aepinstall.sh script completes installing and displays the message:

    
20210402-17:15:15 Finished Installation

    The aepinstall.sh script creates a log file at /opt/Avaya/InstallLogs/ aepinstall.log

  13. To unmount and eject the DVD:
    1. Change the directory to a location that is outside the mount point. For example, enter the cd / command to change to the root directory.
    2. Unmount the DVD as described in the server documentation.
    3. To eject the Experience Portal installation DVD, press the button on the DVD drive or enter the eject command.
  14. To verify that chronyd is operating properly, enter the chronyc tracking command.

    The system displays a status message similar to the following:

    Reference ID    : 0A868E42 (10.134.142.66)
Stratum         : 4
Ref time (UTC)  : Thu Sep 17 12:47:44 2020
System time     : 0.000000488 seconds fast of NTP time
Last offset     : +0.000008485 seconds
RMS offset      : 0.000039525 seconds
Frequency       : 24.108 ppm slow
Residual freq   : +0.001 ppm
Skew            : 0.030 ppm
Root delay      : 0.147401720 seconds
Root dispersion : 0.003942181 seconds
Update interval : 1037.7 seconds
Leap status     : Normal

    Verify that the Reference ID points to the Primary EPM server.

Next Steps