Peerlink fails for PBX's in AWS

Installing HAAst, prerequisites, getting HAAst started, and troubleshooting performance and technical issues. As well, upgrades to HAAst and any underlying software.
Post Reply
User avatar
CRM User
Posts: 135
Joined: Sun Nov 27, 2016 3:41 pm

Peerlink fails for PBX's in AWS

Post by CRM User » Wed Jan 18, 2017 1:20 am

We have created our cluster completely in the AWS cloud. Both peers are setup correctly, but there are errors in the log regarding peerlink failing. What is going wrong?
Account for questions transferred from CRM system
User avatar
Telium Support
Posts: 179
Joined: Sun Nov 27, 2016 3:27 pm

Re: Peerlink fails for PBX's in AWS

Post by Telium Support » Wed Jan 18, 2017 1:24 am

The peerlink error means that the two peers are unable to talk to one another. This is most likely due to Security Group misconfiguration within AWS. As a simple test, try to telnet from one peer to the other peer on port 3002; for example:

Code: Select all

telnet 10.1.2.3 3002
This command will likely fail/timeout, which confirms the Security Group misconfiguration. To resolve this, and assuming both peers are in the same Security Group, and iptables/firewalld is disabled, set that Security Group to allow "itself" traffic on all ports (in AWS). After doing so the peers should quickly find each other and the Peerlink indicators in the GUI will turn green.

If you decide you want the highest level of security possible, only enable destination port 3002 TCP access between the peers (plus ports needed for file/directory/database sync as optionally defined in your haast.conf). But if the peers are in the same Security Group you should be fine allowing all traffic.
Post Reply