Avaya OneCloud Subscription system deployment models

Last Updated : Oct 09, 2020 |

The following are the Avaya OneCloud™ Subscription system deployment models:

Single data center with one Avaya OneCloud™ Subscription system

In this deployment model:

You can install a Usage Metering Collector in a data center and configure a single Avaya OneCloud™ Subscription system in the Usage Metering Collector. You can deploy the applications that are subscribed under this Avaya OneCloud™ Subscription system in the same data center.

In this deployment model:

You can install a Usage Metering Collector in a data center and configure multiple Avaya OneCloud™ Subscription systems in the Usage Metering Collector. You can deploy the applications that are subscribed under these Avaya OneCloud™ Subscription systems in the same data center.
You must deploy a separate WebLM server and Communication Manager system — simplex or duplex — for each Avaya OneCloud™ Subscription system.
You can share the same SAL GW among the Avaya OneCloud™ Subscription systems.

In this deployment model:

You can install a Usage Metering Collector in one data center and configure an Avaya OneCloud™ Subscription system in the Usage Metering Collector. You can deploy the applications that are subscribed under this Avaya OneCloud™ Subscription system in multiple data centers.
You must deploy a separate WebLM server and SAL GW for each data center.

However, some applications do not require license management. For example, licensing for the Communication Manager Survivable Core server is managed by the Communication Manager main server. Hence, if a data center has only those applications that do not require license management, you need not deploy a WebLM server in that data center.

In this deployment model:

You cannot deploy a geo-redundant Usage Metering Collector because concurrently deploying two Usage Metering Collectors that contain the same Avaya OneCloud™ Subscription system causes duplicate usage calculation.

In a geo-redundant environment, if the Usage Metering server fails in the primary data center or if a network outage is detected, you must perform a new installation of the Usage Metering server in the secondary data center. You must then restore the backup of the primary Usage Metering server on the secondary Usage Metering server by using the Usage Metering backup file.

Note that the deployment of the applications that are subscribed under an Avaya OneCloud™ Subscription system in both primary and secondary data centers depends on the High Availability and geo-redundancy models that are supported for these applications.
You must deploy a separate WebLM server and SAL GW for each data center.

For more information, see Usage Metering in a geo-redundant environment.

Consider the following caveats before choosing a deployment model for your data center:

Currently, each Usage Metering Collector supports only one time zone.

For more information, see Setting the time zone.

Hence, ensure that you deploy each on-premise application, both primary and secondary applications, that is part of an Avaya OneCloud™ Subscription system by using the time zone that is set for the Usage Metering Collector in which this Avaya OneCloud™ Subscription system is configured.

For more information, see Adding an application to the Avaya OneCloud Subscription system.
Do not configure the same Avaya OneCloud™ Subscription system in multiple Usage Metering Collectors because it causes duplicate usage calculation.

For more information, see Considerations for configuring Avaya OneCloud Subscription systems of the same subscription offer in multiple Usage Metering Collectors.

Send Feedback