Installing Avaya Analytics offline

Last Updated : Jun 27, 2022 |

About this task

You must upload the Avaya Analytics™ files from the Windows PC or laptop to Cluster Control Manager (CCM).

Use the Screen utility while installing Avaya Analytics™. Screen is a Linux command with which you can detach from an SSH session and reattach later. Using the Screen utility 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 macros-enabled Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm file to suit your deployment type.

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

  • Confirm that the local CCM Docker registry and ChartMuseum are running.

  • 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 solution configuration spreadsheet. Cluster node VMs must be running with the vCPU memory and disk allocation as stated in the solution 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. Log in to the Cluster Control Manager (CCM) console as the customer user.
  2. From the directory on CCM that contains the excel file, enter the following command:

    screen

    The Screen utility runs the install in the background.

    Warning:

    Do not skip this step.

  3. Run the following command:

    ccm install Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm

  4. At the prompt, do the following:
    1. Enter your Avaya SSO credentials.

      You must enter the CCM local registry username and password configured with the agn-ctl setup command earlier.

    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 installs the following downloads:

    • The base cluster software

    • The common services platform software

    • The Avaya Analytics™ software

    Note:

    The installation takes several hours to complete.

  5. Run the following command in a seperate window to monitor the progress of the install:

    tail -f /var/log/avaya/ccm/ccm-main.log

    During the installation, the software creates folders and virtual machines on the host machines that are visible in the vCenter of the host.

  6. If you want to disconnect from the SSH session and want the install to continue in the background, do the following:
    1. Disconnect from the SSH session
    2. When you want to reconnect to the SSH session, start a new SSH session to CCM and connect using the customer account
    3. To retrieve the Screen ID of the session that is running the installation, type screen -ls
    4. To reattach to the installation Screen session, type screen -dr <screen id>
      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
  7. 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™.

  8. 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.

  9. Stop the local CCM Docker registry and ChartMuseum. See section Stopping ChartMuseum and Docker registry on ClusterControl Manager in this section.