...
A prompt asking to create a configuration backup will appear. Click Ok to create the backup.
Once the backup is successful, another prompt will appear to generate the access key. Click Ok to generate the access key.
Copy the encoded Access Key text from the text box into Clipboard or Notepad or TextEditor
Adding a Peer on the Primary Server
...
A prompt asking to create a configuration backup will appear. Click Create to create the backup.
Once the backup is successful, another prompt will appear to copy the access key generated by the Secondary Server. Write a meaningful name
that best describes the Secondary Server as the other node and then paste the encoded Access Key text obtained from the Secondary Server.
The system will be registered locally and show on the Peer nodes list - its configuration can be viewed or modified by clicking Modify on the right side of the row.
...
For instance, if eth4 is used as a Dedicated Network / Interface and is also a direct cable connection between the Primary and Secondary servers then it must be removed from the Failover triggers table. If the Failover triggers is not removed, in the instance when the Slave Node goes down due to a reboot for instance, it will cause the Master node to temporarily lost NSC service until the Slave node's Cluster service is started.
Floating IP Assignment in SIP Profiles on Primary SBC Server
...
Configuration | Signaling | SIP Profiles
Create SIP Profile
...
There may be many SIP Profiles with each there own unique Floating IP Address.
You may Apply the Configuration as this point, knowing that there is plenty of configuration remaining to correct operation.
Complete the Configuration
Network Configuration, Media Interfaces, and SIP Profile configuration are not enough to complete the configuration of a SBC. The following sections of configuration are required at a minimum to complete the configuration of the SBC.
...
Once completed the configuration of the SBC, Apply the Configuration.
Apply the Configuration
...
Copy configuration from the Primary to the Secondary Server
...
Clicking on Copy configuration to Peer button will start copying the configuration from the Primary to the Secondary server, where all configuration will be copied over, including all the user interface settings and service startup information. This process may take a few minutes, please be patient.
After both servers are configured and the configuration has been copied over, the cluster is now fully configured and ready to start operation.
...
Clicking on Start All Nodes button will start the process joining the HA. When complete, there will be a Master Node and a Slave Node. The Master Node is the SBC unit that is actively processing calls, whereas the Slave Node is monitoring the Master Node.
...
After pressing Start All Nodes, the required Application Services are started. Services managed directly by the cluster are called Cluster Resources, and will be shown on the Control Panel as soon as the cluster services are initialized.
...
Stop both the nodes before modifying hostname.
Update the host name and Apply configuration.
Important to copy the configuration to Peer before restarting.
Restart the system.
...
HA Upgrade Guide
Please refer to the HA Upgrade Guide, to upgrade a pair of SBC servers in High Availability setup
...