Elastic XL - management

[Mikula83]

Can you clarify me something related to ElasticXL design and configuration. During the "First time wizzard" I have to put Management connection parameters and that IP address become a IP address of bonded MAGG1 interface (subordinate Mgmt interface).

After adding SMO gateway (member 1) to smart console, I have to put ip address of MAGG1 interface or I can put any other configured interface IP address?

Lets assume that on SITE B I have ElasticXL cluster, SMS (Security Management Server) and PC with smart console application installed (attached picture). SMS is on private IP address. Is it a possible to add ElasticXL cluster which is on SITE A. SITE A and SITE B have different public IP addresses.

I have done similar scenario a few years ago but on SITE A I used ClusterXL. I have NATed my SMS to public IP and added public IPs of gateways on SITE A. My question is, is it possible in ElasticXL cluster design and on which way? All gateways are 9100 Quantum Force models.

Best regards,
Milan Babic

[Bob_Zimmerman]

magg1 is just a bond like any other. It happens to contain the interface named Mgmt by default, and it's used for provisioning new members, but it's in the same routing table as all your other interfaces. You don't have to use it to manage the box.

[Alex-]

What do you mean by provisioning new members?

We have some Elastic where the magg is disconnected and new members are seen and provisioned via the built-in sync.

[Bob_Zimmerman]

Huh! I could have sworn the new member talked via the interface named Mgmt first, then it starts the rsync over the interface named Sync once the join is approved. If the interface named Mgmt isn't needed for that, then magg1 is just like any other bond.

[Alex-]

That might be the case, hence my question.

I can't say with certainty if those few sites moved away from the magg after or before finishing the cluster.