Configuring a multiple node Avaya Breeze® platform cluster

Last Updated : Oct 24, 2019 |
Prolog information
Metadata
Keywords:
Use the following procedure to configure a multiple node Avaya Breeze® platform cluster. Multiple node clusters are used to deploy a High Availability (n+1) configuration. For more information about High Availability configurations, see Chapter 9 in the Deploying Avaya Breeze® platform guide.
SIP high availability enables the ability to route users of a service to the cluster rather than a specific Avaya Breeze® platform server. In this deployment scenario, the Cluster IP field of the cluster needs to be populated and the Load Balancer enabled. The users of the Device Adapter service are pointed to the cluster through the Cluster IP.
Note:
For every Avaya Breeze® platform server running Avaya Device Adapter Snap-in, an additional SIP Entity of the Endpoint Concentrator type must be defined. A number of Entity links between the SIP Entity and one or more Avaya Aura® Session Managers must also be defined. The Entity links must have a Connection Policy set to Endpoint Concentrator. An Avaya Aura® Session Manager Communication Profile must also be defined for every user or endpoint.
  1. On System Manager, click ElementsAvaya Breeze®Cluster Administration.
  2. Click New.
  3. Select the Cluster Editor page.
  4. Select the Core Platform cluster profile.
  5. Enter the cluster attributes.
    ADDITIONAL INFORMATION:
    Note:
    The cluster name must be unique.
    Important:
    For multi-node clusters, assign the Cluster IP and enable the Load Balancer.
    Consider using the previous CS 1000 Node IP as the value of the Cluster IP Address field of the cluster. This will enable performing a migration that will move all endpoints in one step. Do not do this if you are performing a phased migration.
  6. Select Enable Cluster Database.
    ADDITIONAL INFORMATION:
    Note:
    Device Adapter cannot be installed if the cluster database is disabled.
  7. Select Should calls be allowed on the cluster.
  8. Select values for the Minimum TLS Version for Non-SIP Traffic and Minimum TLS Version for SIP Call Traffic.
  9. Deselect Use secure signaling for platform initiated SIP calls to allow unsecured calls.
  10. Enter the SIP domain in the Default SIP Domain field.
  11. Select the Servers tab.
  12. Assign servers to the cluster.
    ADDITIONAL INFORMATION:
    Note:
    All servers in a cluster must have the same Avaya Breeze® platform version.
  13. Select the Services tab.
  14. Assign the Device Adapter service.
  15. Click Commit.
    STEP RESULT:
    The Service Install Status field on the Cluster Administration page displays a green tick symbol after all the assigned snap-ins are successfully installed on all the servers in the cluster.
  16. On System Manager, click ElementsAvaya Breeze®Cluster Administration.
  17. Click Show beside the cluster name.
  18. Identify the active and standby database servers in the Cluster Database field.
    ADDITIONAL INFORMATION:
    Note:
    The server marked Active is the primary server. The server marked Standby is the secondary server. All other servers in the cluster should be marked as Idle.
    Important:
    TPS node is active only when one of the two servers: Active and Standby servers are active and running. TPS node is inactive when both Active and Standby servers are not running even if the other servers in cluster are active.