Creating Avaya Oceana Cluster 2

Last Updated : Apr 04, 2024 |

About this task

Use this procedure to create Avaya Oceana® Cluster 2.

Note:

  • For an Avaya Oceana® deployment that supports up to 100 active agents, do not create Avaya Oceana® Cluster 2 and install the SVARs of Avaya Oceana® Cluster 2 on Avaya Oceana® Cluster 1.

  • Do not add nodes to the cluster while creating the cluster.

Procedure

  1. On the System Manager web console, click Elements > Avaya Breeze® > Cluster Administration.
  2. On the Cluster Administration page, click New.
  3. On the Cluster Editor page, select the General tab.
  4. In the Basic section, perform the following steps:
    1. In the Cluster Profile field, select Customer Engagement.
    2. In the Cluster Name field, enter a unique cluster name.

      The name must be a string of Alphanumeric characters. For example, AvayaOceanaCluster2.

    3. In the Cluster Group field, select a cluster group.
      Important:

      Select the same cluster group for all clusters of Avaya Oceana® and ensure that you do not use the selected cluster group for any non-Avaya Oceana® cluster.

    4. In the Cluster IP field, enter the IP address of the cluster.

      The IP address of the cluster must be on the same subnet as the Security Module IP address of the Avaya Breeze® platform nodes that you plan to add to the cluster.

      Ensure that you do not specify the IP address of any of the Avaya Breeze® platform nodes that you plan to add to the cluster.

      The system uses the IP address of the cluster as the load balancer. The system does not provide an option to select Avaya Breeze® platform instances within the cluster for load balancing.

    5. In the Cluster Fully Qualified Domain Name field, enter the FQDN of the cluster.
    6. Select the Enable Cluster Database check box.
    7. In the Description field, enter a description for the cluster.
  5. In the Cluster Attributes section, perform the following steps:
    1. If the AuthorizationService snap-in is installed on Avaya Oceana® Cluster 2, then in the Authorization Services Address field, enter the FQDN of Avaya Oceana® Cluster 2.
    2. Increase the value of the attribute Http or Https limit on connections per client from the default value of 100, so that the cluster supports more connections simultaneously.

      The suggested value is 6000.

    3. In the HTTP or HTTPS traffic rate limit in bytes/sec per client field, set the value to 5000000.
    4. In the HTTP Load Balancer backend server max failure response timeout period (seconds) field, type 60.
    5. In the Max number of failure responses from HTTP Load Balancer backend server field, type 10.
    6. In the Network connection timeout to HTTP Load Balancer backend server (seconds) field, type 3.
    7. Select or clear the Only allow secure web communications check box based on your requirement.
    8. Clear the Is load balancer enabled check box.
      Important:

      After adding Avaya Breeze® platform nodes to the cluster, you must edit the cluster and select this check box.

    9. Clear the Is session affinity enabled check box.

    For a description of Cluster Attributes, see Administering Avaya Breeze® platform.

  6. On the Cluster Editor page, select the Services tab.

    The system automatically adds the CallEventControl and EventingConnector SVARs to the Assigned Services list.

  7. In the Available Services list, click the plus sign (+) on the following SVARs to add the SVARs to Avaya Oceana® Cluster 2:

    • AuthorizationService

    • AvayaMobileCommunications

    • BotConnector

    • MetricbeatService

      This is an optional SVAR, which is used for Centralized Logging. If you do not need Centralized Logging, do not install this SVAR and free up some CPU cycles for contact processing.

    • OceanaMonitorService

    • PacketbeatService

      This is an optional SVAR, which is used for Centralized Logging. If you do not need Centralized Logging, do not install this SVAR and free up some CPU cycles for contact processing.

    • UnifiedAgentContextService

    • UnifiedAgentController

  8. Click Commit.

    The system prompts you to ensure that you restart all Avaya Breeze® platform nodes before placing the cluster into the Accept New Service state.

  9. Click OK.