Hi!
Earlier this week I built a H/A conductor pair:
- I followed this document: Conductor High Availability for Cloud Deployments | SSN Docs
- Software version 5.5.4
- Built from the AWS marketplace AMI image
- Two conductor nodes in AWS, in different availability zones
- Both nodes reaching each other on internal addressing via VPC peering with firewall exceptions for all ports
- Both nodes reachable on their public IPs on the correct ports with the suggested firewalling
Everything seemed fine (apart from the subtle error in the second conductor's node name). "show system connectivity" showed connected and each node reported the status of the other.
admin@XXXX-128T-CON-AWS1.XXXX-128T-CON-AWS1-NODE# show system connectivity
Tue 2022-10-04 16:05:54 UTC
✔ Retrieving system connectivity...
============================================ ======================= ==============
Local Node Remote Node State
============================================ ======================= ==============
XXXX-128T-CON-AWS1.XXXX-128T-CON-AWS1-NODE XXXX-128T-CON- connected
AWS2.XXXX-128T-CON-
AWS1-NODE
However after configuring my first router and running validate, I noticed this warning:
admin@XXXX-128T-CON-AWS1.XXXX-128T-CON-AWS1-NODE# validate
⚠ Validating: [5/5]...
% Warning:
1. Node is missing a non-forwarding fabric or shared interface. The node may not have
inter node connectivity to its peer node unless the interfaces were set up manually.
config
authority
router XXXX-128T-CON-AWS1-NODE
node XXXX-128T-CON-AWS1
name
2. Node is missing a non-forwarding fabric or shared interface. The node may not have
inter node connectivity to its peer node unless the interfaces were set up manually.
config
authority
router XXXX-128T-CON-AWS1-NODE
node XXXX-128T-CON-AWS2
name
Candidate configuration is valid
I have also seen intermittent NGINX 500 errors and "red circle exclamation mark" errors from the conductor GUI.
A search led me to this document: Transitioning a Conductor from Standalone to HA | SSN Docs
It suggests that I need to configure two non-forwarding interfaces so connectivity can be established between both Conductor nodes.
I'm unclear. Any tips would be gratefully received:
- Do I really need additional interfaces for a public cloud H/A conductor pair?
- If so, how should they be setup?
- Are both documents up-to-date and accurate?
Thanks, Chris
------------------------------
Chris Tomkins
------------------------------