Installing Avaya Analytics

Last Updated : Jun 27, 2022 |

About this task

To install Avaya Analytics™ on the Cluster Control Manager (CCM) server, select the required deployment type by selecting the agent footprints in the macro-enabled Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm file.

Before installing Avaya Analytics™, you must complete the fields with the customer details that correspond to each deployment type. Examples of customer details include IP addresses and passwords. The spreadsheet includes descriptions of each configurable field to guide the installer during the configuration process.

Use the screen utility while installing Avaya Analytics™. Screen is a Linux command with which you can detach from an SSH session and reattach at a later time. This avoids issues where the SSH session can disconnect after timing out, thereby interrupting the install.

Important:

Ensure that you are familiar with the screen utility. For detailed information about using screen, enter the man screen command.

Before you begin

  • Configure CCM.

  • Update the Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm file.

  • Copy the Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm file to the CCM server.

  • For high availability, deploy 3 or more cluster nodes by setting values for CPU, memory, and disk. Refer to Deploying Cluster Nodes chapter in this guide.

  • Modify the cluster node VMs running with the vCPU, memory, and disk allocation as stated in the Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm spreadsheet. Cluster node VMs must be running with the vCPU memory and disk allocation as stated in the deployment spreadsheet.

  • If you are deploying with high availability enabled (three master nodes) you must create an anti-affinity rule in your vCenter for your cluster nodes.

    If DRS is enabled, the vCenter administrator must create a DRS anti-affinity rule and include all master cluster node VMs in the rule.

    If DRS is disabled, the vCenter administrator must ensure that the VMs for the master cluster nodes are deployed on separate hosts if HA is required.

Procedure

  1. Connect to the CCM server using the customer account log in.
    Important:

    If this is your first login after deploying CCM, you must change the password.

  2. Copy the excel file to a location on the CCM server.
  3. From the directory on CCM that contains the excel file, enter the following command: screen

    The screen utility allows the install to run in the background.

    Warning:

    Do not skip this step.

  4. Run the following command: ccm install Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm
  5. When prompted:
    1. Enter your Avaya SSO credentials.
    2. Accept the EULA.
    3. When prompted, either enable or do not enable the High Availability Audit feature.

      To enable the feature, respond Y to give the cluster deployment vCenter access.

      Y – Enable the High Availability Audit feature and grant deployment vCenter access for the cluster. The solution configuration spreadsheet must also set high_availability to enabled.

      N – Do not grant deployment vCenter access for the cluster, and do not enable the High Availability Audit feature.

      Example:

      The following features will be enabled if this cluster deployment is allowed vCenter access.
- High Availability Audit

Do you want to allow this cluster deployment vCenter access? (Y/N)
    4. Enter the vCenter user ID and password.
    5. Re-confirm the password.

    The installation starts downloading and installing the following:

    • The base cluster software

    • The common services platform software

    • The Avaya Analytics™ software

    The installation takes several hours to complete.

  6. Run the following command in a separate window to monitor the progress of the install: tail -f /var/log/avaya/ccm/ccm-main.log

    During the installation folders and virtual machines are created on host machines visible in the host’s vCenter.

  7. If you want to disconnect from the SSH session and allow the install to continue in the background, do the following:
    1. Disconnect from the SSH session.
    2. When you want reconnect to the SSH session, start a new SSH session to CCM and connect using the customer account.
    3. Type screen -ls to retrieve the screen id of the session that is running the installation.
    4. Type screen -dr <screen id> to reattach to the installation screen session.
      See the following example command to reattach to the installation screen session: 
      [cust@examplelab ~]$ screen -ls
There is a screen on:
			9069.avaya.examplelab    (Detached)
1 Socket in /var/run/screen/S-cust.
[cust@examplelab ~]$ screen -dr 9069.avaya.examplelab
  8. To check if the installation is successful, run the following command on the CCM console:

    ccm status

    The CCM console displays the status details as follows:

    • If the Status column displays the status as deployed, it indicates that all the components are currently deployed to the cluster.

    • If the Status column displays the status as Staged or '', it indicates that the software is staged on the system, but not deployed.

      The tools-policy and utility-services remain in a staged state.

      Note:

      You might see this status in the older versions of the software after a upgrade.

    • If the Status column displays the status as Error, it indicates that the components failed to install.

    Important:

    If the installation fails, run the ccm install cancel command, resolve the issue causing the failure, and restart the installation procedure. For more information about troubleshooting installation failures, see Maintaining and Troubleshooting Avaya Analytics™.

  9. Delete the spreadsheet from CCM after the deployment is complete. Ensure you keep a copy of the spreadsheet and store it in a secure location.

    This step is important to save the passwords and other configuration details that you entered as plain text for the deployment.