Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
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.
Hope this helps!