Thanks
I recommend you add this to the documentation.
Most HA clusters (Firewalls, Controllers ..) require an L2 segment and a dedicated link for sync and the reason why they are in the same Data Center.
The current SSR documentation leaves this for guessing. Please just add a few diagrams with subnetting (one Data Center, Distributed Data Center, Cloud..)
Real redundance require geographical distribution for HA
Best regards
------------------------------
Hannu Rokka
Senior Advisor (DataCom)
------------------------------
Original Message:
Sent: 08-22-2022 09:58
From: Christopher Wilkinson
Subject: Conductor High Availability for Cloud Deployments requirement
Hi Hannu,
For physically deployed conductors, they run as active/active with all the managed routers connecting to both. Unlike HA routers, there's no interface takeover with conductors; each conductor "node" is given a unique IP address that's reachable by everybody. The two HA conductors then communicate with one another to synchronize state, so it doesn't matter which conductor an admin logs into to view metrics, alarms, etc. But, because of that sync, Juniper Networks requires that the network between geographically separated conductors have a latency of no more than 100ms, and packet loss no greater than 1%.
For cloud deployments, we have great documentation, and this guide walks through launching the 2 Session Smart Conductor VMs.
https://docs.128technology.com/docs/intro_initialize_HA_conductor/
Hope this helps!
------------------------------
Christopher Wilkinson
Original Message:
Sent: 08-18-2022 06:24
From: Hannu Rokka
Subject: Conductor High Availability for Cloud Deployments requirement
What are the requirements for a Conductor HA environment? (latency? L2 segment? multi-cloud?)
Best regards
...Hannu
------------------------------
Hannu Rokka
Senior Advisor (DataCom)
------------------------------