Configuring System Platform High Availability Failover - Avaya Aura System Platform Installing And Configuring

• The standby server cannot have installed template. If present, the failover configuration
will fail with an error. If you are using the bundled System Platform installation (with
solution template), disable template installation on the standby server.
• Default network gateway is the System Platform High Availability Failover heartbeat's ping
target and it is not a configurable parameter. Ensure that your network gateway replies
to ICMP requests coming from the System Platform nodes. Heartbeat sets payload with
node-identifying data and checks that the data in replied packet payload is correct. The
size of these ICMP ping packets is in the range of 132-256 Bytes. If you apply firewall
rules against the ping service (at the gateway), specifically packet size restriction, you
must allow for packet sizes up to 256 bytes.

Configuring System Platform High Availability Failover

Prerequisites
• 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 Redundant Block Device) sync propagation)
• Both the servers in close proximity, approximately 10 meters.
• System Platform installed on both the active and standby nodes.
Note:
There is no need to install template virtual machines on both machines. If any template is
already installed, the system uses all virtual machines from the preferred node; otherwise
you can install a template on a system already running High Availability Failover.
1. Log on to System Platform Management Console on the active server as an
2. Click Configure Failover.
Installing and Configuring Avaya Aura
advanced administrator.
™
System Platform
Configuring System Platform High Availability Failover
April 2010 85