Maestro Dual Site - From one to two orchestrator per site

[Alex-]

As title says, the plan is to go from a single MHO per site to two. MHO-175 in this case.

Uplinks and downlinks will be spread between the two MHO's.

Is it recommended to use one management port from the first MHO or connect both port and create a aggregation for management?

We're OK to rebuild the SG if needed, but since there are 2 MHO in both sites, each with management uplink for now, there is also the question of whether it's best practice and recommended from experience.

[Nir_Shamir]

When working with two MHO's per site (the recommended deployment) each port , data or management, is bonded with at least two ports from each MHO.

This way you have full HA between them.

Regarding the move from 1 MHO to 2 MHO's . This procedure is a bit complicated and involves a lot of manual changes in configuration files.

I would recommend working with our Professional Services to do such a change.

[Alex-]

Thank you for the quick reply.

We are OK with recreating the SG from scratch, as the project is on the launchpad and the current cluster still manages traffic.

Since there are external parties in charge of the network infrastructure to which we will need to make demands, we'd like to clarify the following points to explore all options:

• Can we work with dual uplinks/downlinks but keep only one Management port (1) on the MHO-175? Current tests show the policy installs and failovers work
• Can we delete the SG, create a MAGG with just one port on the first MHO, recreate the SG and in the future connect the port 1 of the second MHO which will then join the MAGG?

[emmap]

Yes and yes.