The following redundancy and high availability options are available through the Avaya Aura® network.

The Avaya Aura® network uses System Platform high availability. When deploying Avaya Aura® System Manager, you must also install and configure System Platform. For more information about System Platform high availability, see Installing System Platform in Implementing Avaya Aura® System Manager.

The IP Office Branch solution supports Avaya Aura® Session Manager geographic redundancy when a back-up Session Manager is deployed in the secondary data center. If for any reason the IP Office system's primary Session Manager goes out of service, the system will automatically attempt to use the secondary Session Manager. Prioritization of the Session Manager is determined by the line number configured for a particular Session Manager. For example, if the first Session Manager is configured with line number 17 and the second Session Manager is configured with line number 18, then line number 17 has the higher priority and is considered the primary Session Manager. If for some reason you want to designate the secondary Session Manager as the primary line, you must change one or both of the line numbers associated with the Session Manager so that the secondary Session Manager number is lower than the primary line number.

In deployments with Avaya Aura® System Manager geographic redundancy set up, the IP Office devices added in the primary System Manager are also visible in the secondary System Manager. To use Avaya Aura® System Manager geographic redundancy in the IP Office Branch solution, make sure:

• The initial interactions through the SCEP protocol are done between the IP Office and the primary System Manager to establish trust.
• The IP address for the primary and secondary System Manager are configured as trap destinations in the IP Office. This way, IP Office sends alarms and traps to both System Manager servers. When the primary System Manager server is down, the secondary System Manager server still receives this information.

If the IP Office is using Avaya WebLM centralized licensing and the connection between the IP Office and the Avaya WebLM server on the primary System Manager is down, then the IP Office goes into WebLM Error Mode. In this mode, all functionality is available for a grace period of 30 days. No action is required if the Avaya WebLM server on the primary System Manager is active and reachable in less than 30 days. If there is a risk of the System Manager server not being available for 30 days, you must modify the IP Office configuration to use the Avaya WebLM server on the secondary System Manager as soon as possible.