Prerequisites - Avaya Aura System Platform Installing And Configuring

System Platform High Availability Failover
are running on the standby node includes graceful shutdown of all resources and start of all
the resources:
• stop of resources - up to 5 minutes
• start of resources - up to 5 minutes
• resulting longest switchover time - up to 10 minutes
In case of failover due to total failure of the active node, the total time between the start of the
outage and time when all resources are running on the standby node includes detection interval
timeout and start of all the resources:
• detect active node failure - 30 seconds
• start of resources - up to 5 minutes
• resulting longest switchover time - up to 5.5 minutes
Note:
Switchover time will vary depending on hardware in use and the specific template installed
on the system. Templates with more virtual machines will take slightly longer to switch over
due to multiple virtual machines booting simultaneously.
See How System Platform High Availability Failover works for more information.

Prerequisites

The prerequisites for configuring System Platform High Availability Failover are as follows:
• Two servers with exactly the same configuration.
• Hardware supported by System Platform.
• The servers must have a spare Gigabit network interface to be used as a crossover
connection dedicated exclusively to High Availability Failover services (heartbeat health
checks and DRBD (Distributed Replicated Block Device) sync propagation)
• Both the servers must be in the same subnet.
• Both the servers in close proximity, approximately 10 meters.
• The same version of System Platform installed on both the active and standby nodes.
• Both the servers must be connected with a gigabit-crossover cable on the ports detected
as eth2 on operating system.
• If you want to install a template on a preferred node, you must do it before starting HA.
• The standby server cannot have less memory, number of processors, and total or free
disk space than the primary server.
84 Installing and Configuring Avaya Aura
™
System Platform April 2010