Primary System Manager server

The first or the master System Manager server in a Geographic Redundancy setup that serves all system management requests.

Secondary System Manager server

The System Manager server that functions as a backup to the primary System Manager server in a Geographic Redundancy setup. The secondary System Manager server provides the full System Manager functionality when the system fails to connect to the primary System Manager server.

Active System Manager server

The mode of operation of the System Manager server where the server provides the full System Manager functionality.

Standby System Manager server

The mode of operation of the System Manager server where the server serves only authentication and authorization requests. In the standby mode of operation, the system supports limited Geographic Redundancy configuration, the inventory service.

Standalone System Manager server

The single System Manager server deployed in an enterprise that provides full System Manager functionality. The standalone server operates independently and does not contain a backup server.

Element

An element is an instance of an Avaya Aura® network entity that the System Manager manages. For example, a Session Manager server or a Communication Manager server.

In the context of System Manager Geographic Redundancy, the elements can be classified as follows:

• Geographic Redundancy-unaware element: An element that does not support Geographic Redundancy, such as Avaya Aura® Session Manager Release 6.2.x and earlier. If you have a Geographic Redundancy-unaware element that is configured and managed by the primary System Manager server, and if the primary System Manager goes down or a Split brain scenario occurs, then you cannot use the secondary System Manager to manage the element either automatically or with a simple click of a button. If you need to manage a Geographic Redundancy-unaware element, then you need to make the changes manually. The manual changes differ from one Geographic Redundancy-unaware element to another.

• Geographic Redundancy-aware element: An element that supports Geographic Redundancy, such as Avaya Aura® Session Manager Release 6.3 and later. These elements can leverage the services of the primary or the secondary System Manager servers, either automatically or with the simple click of a button. The Geographic Redundancy-aware elements are classified in the following types:

  • Elements capable of automatically switching between the primary and secondary System Manager servers depending on the state of the System Manager servers - If the primary System Manager server goes down or a Split brain scenario occurs and you activated the secondary System Manager server, then the element can detect it and depending on the current state of the System Manager server, the element automatically switches to the appropriate System Manager server, so that the element can be managed by it.

    For example, if you have a System Manager 8.1.x Geographic Redundancy deployment, (Sunny Day) with a few Session Manager 8.1.x servers configured and you activated the secondary System Manager due to a network split, then each Session Manager server detects this. If the primary System Manager is not reachable, then the Session Manager server automatically switches to the active secondary System Manager server. If the primary System Manager server is reachable, then the element does not switch to the secondary System Manager, even though it is active. This does not mean that you cannot manage them. To manage the element through the secondary System Manager server, on secondary System Manager go to the Manage Elements page, select the element, and then click the More Options > Force Manage option.

  • Elements that require manual switch - If the primary System Manager server goes down or a Split brain scenario occurs, and you need to manage the element from the secondary System Manager server, then on secondary System Manager go to the Manage Elements page, select the element, and then click the More Options > Force Manage option. This step is required to manage such elements from the secondary System Manager server.

Geographic Redundancy-aware element

An element that supports Geographic Redundancy, such as Avaya Aura® Session Manager Release 6.3.

Geographic Redundancy-unaware element

An element that does not support Geographic Redundancy, such as Avaya Aura® Session Manager release earlier than 6.3.

Geographic Redundancy operational modes

• The normal operation mode. Also called the Sunny Day scenario. A System Manager Geographic Redundancy scenario where the primary System Manager server runs in the active mode while the secondary System Manager server runs in the standby mode providing limited set of services. In the normal operation mode, the primary System Manager server manages all elements and provides the complete System Manager functionality.

• Primary nonoperational mode. Also called the Rainy Day scenario. The primary System Manager server fails or loses connectivity to all elements that the system manages. The administrator activates the secondary System Manager server to make the secondary System Manager server manage all elements in the system.

• Split network. A System Manager Geographic Redundancy scenario when the primary and secondary System Manager servers run in the active mode but cannot communicate with each other due to a network connectivity outage or when some elements cannot communicate with one System Manager and both primary and secondary System Manager servers can communicate with each other.

Failover

Failover is the process of activating the secondary System Manager server when the primary System Manager server becomes nonoperational due to server outage or loses connectivity to the elements that the server manages.

Failback

Failback is the process of making the primary System Manager server operational by restoring the primary System Manager server by using the primary or secondary System Manager data.