.. _resilience_administration_manual_failover:

**************************************
Administration in Manual Failover Mode
**************************************

In Manual failover mode, there is no heartbeat link between Standby and Main XiVO.
Activation of the Standby XiVO is manual - see :ref:`resilience_architecture_failover_mode`.
This page describes how to trigger the failover and fallback in the different deployment type.

.. contents:: :local:


XiVO Deployment
===============

Failover to Standby
-------------------

On **Standby** XiVO:

* An admin connects to the Web interface in :menuselection:`Services --> IPBX --> Resilience Management`
* And triggers the activation of the Standby node by clicking on :guilabel:`Start services`
* The standby will then activate and start the services

on **Main** XiVO:

* An admin must connects to the Web interface in :menuselection:`Services --> IPBX --> Resilience Management`
* And triggers the deactivation of the Main node by clicking on :guilabel:`Stop services`
* The Main will then deactivate and stop the services


Failback to Main
------------------

On **Standby** XiVO:

* An admin connects to the Web interface in :menuselection:`Services --> IPBX --> Resilience Management`
* And triggers the deactivation of the Standby node by clicking on :guilabel:`Stop services`
* The standby will then deactivate and stop the services

on **Main** XiVO:

* An admin connects to the Web interface in :menuselection:`Services --> IPBX --> Resilience Management`
* And triggers the activation of the Main node by clicking on :guilabel:`Start services`
* The Main will then activate and start the services


CC Deployment
=============

Failover to Standby
-------------------

What happens:

* Standby CC starts needed services when it detects Standby XiVO went to status *Active*
* Main CC stops needed services when it detects Main XiVO went to status *Inactive*

Manual actions:

* The users must reconnect manually to the CC Standby by entering the new CC Standby FQDN in their browser


Failback to Main
------------------

What happens:

* Standby CC stops needed services when it detects Standby XiVO went to status *Inactive*
* Main CC starts needed services when it detects Main XiVO went to status *Active*

Manual actions:

* The users must reconnect manually to the CC Main by entering the new CC Main FQDN in their browser


XDS Deployment
==============

Failover to Standby
-------------------

What happens:

* When the standby takes over the telephony service, it registers to the other MDS

Manual actions: None


Failback to Main
------------------

What happens:

* When the main is back again, it registers to the other MDS

Manual actions: None


Edge Deployment
===============

* A single Edge stack is relaying its services to either the Main or the Standby XiVO machines. 


Failover to Standby
-------------------

What happens:

* Edge detects that Main CC/XiVO are not working and redirects the traffic to Standby CC/XiVO

Manual actions: 

* The users must refresh its Web page to reconnect (no need to change FQDN)


Failback to Main
------------------

What happens:

* Edge detects that Standby CC/XiVO are not working and redirects the traffic to Main CC/XiVO

Manual actions: 

* The users must refresh its Web page to reconnect (no need to change FQDN)