Deployments with Avaya Aura® and without Avaya Aura®

Last Updated : Jun 08, 2023 |
Prolog information
Metadata
Keywords:
Starting from Release 10.1.1, you can choose whether Avaya Aura® Device Services requires Avaya Aura® components, such as System Manager or Session Manager, to operate. Avaya Aura® Device Services supports the following deployment options:
  • Avaya Aura® deployments, where Avaya Aura® Device Services requires the functionality that Avaya Aura® components provide, such as System Manager or Session Manager. Avaya Aura® Device Services cannot operate if your environment does not include these components.
  • Deployments without Avaya Aura®, where Avaya Aura® Device Services does not require any Avaya Aura® components and operates as an independent server. Your environment can include other Avaya Aura® components, but Avaya Aura® Device Services do not use them by default.
You can choose the deployment type when installing the Avaya Aura® Device Services application on a virtual machine. The initial virtual machine deployment process remains the same for both deployment options.
Important:
You cannot switch the deployment type after installing Avaya Aura® Device Services or when you upgrade Avaya Aura® Device Services to the latest release. To switch to another deployment type, uninstall the Avaya Aura® Device Services application and select the required deployment type when reinstalling Avaya Aura® Device Services.

Considerations and limitations

Avaya Aura® Device Services deployed in an environment without Avaya Aura® cannot use features that System Manager or Session Manager provide. Therefore, certain features work differently in deployments with Avaya Aura® and deployments without Avaya Aura®. For example:
  • Identity certificates for Avaya Aura® Device Services interfaces and internode communication. In Avaya Aura® deployments, Avaya Aura® Device Services by default uses identity certificates signed by the System Manager. In deployments without Avaya Aura®, System Manager is unavailable, so you must obtain and use identity certificates provided by a third-party CA.
  • Dynamic configuration service. In Avaya Aura® deployments, Avaya Aura® Device Services automatically retrieves certain endpoint configuration settings from System Manager. In deployments without Avaya Aura®, you must manually configure and publish these settings on Avaya Aura® Device Services.
  • Alarms. When operating, Avaya Aura® Device Services can trigger various alarms. In Avaya Aura® deployments, you can view these alarms on System Manager. In deployments without Avaya Aura®, you must configure a separate SNMP server to view Avaya Aura® Device Services alarms.
  • LDAP and contact search. In deployments without Avaya Aura®, Avaya Aura® Device Services does not perform contact search on System Manager and does not synchronize LDAP data with System Manager.
Deployments without Avaya Aura® do not support the following Avaya Aura® components and their features:
  • System Manager and all its features, such as data center topology configuration or DRS synchronization.
  • Session Manager and all its features, such as Session Manager Cassandra clustering.
If deployments without Avaya Aura® do not support a particular feature or require a specific setup for a feature, this document mentions it explicitly.