1.       Log-in to the Production FatPipe via Live IP Address

a.       Verify the Unit Failover Settings (System>Unit Failover

                                                               i.      By setting them exact from the old HA pair to the new replacement pair creates the same virtualized MAC address where you can avoid any ARP Cache Issues

2.       Apply the same Group ID and Access IP + /Mask

3.       Set the Peer Unit Access IP - what you plan to use for the Backup Device

a.        (if using Eth0 as Heartbeat interface, you will not be able to edit the multicast IP: 224.0.0.18)

4.       Choose Eth0 or Eth4 for Heartbeat Interface

a.       By choosing Eth4 – the heartbeat packets are isolated to their own interface (Recommended)

                                                               i.      Locate the corresponding NIC in the PCI section labeled: UF Only

5.       When Unit Failover is enabled the device requires a reboot (the FatPipe receives a Virtual MAC address for every Interface (Eth0-3). Be aware of the New virtualized MAC Address (may require ARP tables to be cleared on adjacent devices)

a.       ***WARNING: once unit failover is enabled, it will be in a Standby mode, where you cannot access the UI unless the FatPipe detects Power on a WAN side interface and a LAN side interface (if you're plugged into the LAN port with a Laptop, that is perfect, just connect a basic straight-through or crossover from WAN1 to WAN2 [loopback style] so that the WAN side detects power and the unit will come out of the Standby State)

6.       Now that Unit Failover is enabled on the Primary Device Role, rebooted, and verified...go to System>Maintenance>and click Shutdown (leave powered off until its racked, settled, and cabled up)

7.       Follow the same procedure for the Backup Role device

a.       Restore the Configuration (Tar.gz) file

                                                               i.      System>General>Restore

                                                             ii.      Reboot Required

b.      Re-Access the Unit with your original IPs

                                                               i.      Enable Unit Failover with its Group ID and Access IP/Mask

                                                             ii.      Ensure this is a different IP to avoid IP Conflict

                                                            iii.      Set the Peer Unit Access IP (if using Eth0 as Heartbeat interface, you will not be able to edit the multicast IP: 224.0.0.18)

                                                           iv.      Choose the Corresponding Eth0 or Eth4 Heartbeat Interface (same as what was chosen for the Primary Role Device)

                                                             v.      Click Save, and the Unit will reboot

c.       ***WARNING: once unit failover is enabled, it will be in a Standby mode, where you cannot access the UI unless the FatPipe detects Power on a WAN side interface and a LAN side interface (if you're plugged into the LAN port with a Laptop, that is perfect, just connect a basic straight-through or crossover from WAN1 to WAN2 [loopback style] so that the WAN side detects power and the unit will come out of the Standby State)

8.       When ready to introduce the HA pair Primary with the Backup FatPipe:

a.       Shutdown the Backup "Secondary FatPipe"

                                                               i.      Where both Fatpipe’s have HA Enabled, and both are Shutdown

b.      Replicate the Physical connections to the Primary & Secondary FatPipe if not yet completed (WANs, LAN, etc.)

c.       Power-On the Primary FatPipe, Once Booted up it will show “Login:” at the Console if you have a VGA Monitor connected

d.      Power-On the Backup Fatpipe

                                                               i.      FYI: The Active/Standby "Status Designation" is determined on Bootup (for example: the backup unit, upon bootup will detect that the Primary Unit is up/active, and it will go into standby mode, ready for failover)

e.      You should now see a “Peer Unit” in the Unit Failover Section of the System Menu