Good Day Carlos,
CMM instances can be deployed in a resilience design but they infarct act independently from each other as each instance gets its information directly from the connected Call Bridges and from TMS. (See Cisco Notes below)
You do not require a Load Balancer for a resilience design.
CMM Resilience
To add resilience to your Meeting Management deployment, you can connect up to 2 instances of Meeting Management to the same Meeting Server deployments.
Decide if you want to set up 1 or 2 instances of Meeting Management. They must be configured independently; each instance gets its information directly from the connected Call Bridges and from TMS. No information is exchanged between them. We recommend that the 2 instances of Meeting Management are placed in different locations so for example power outages or connection issues will not affect both instances at the same time.
Also, decide how you want to direct users to the appropriate instance of Meeting Management.
The options are:
a. Users manually sign in to a specific instance. Define an address (FQDN) for each instance
and ask users to sign in to one. If they experience issues, they should sign in to the other
instance and inform their administrator.
b. User traffic is redirected. On top of defining an address (FQDN) for each instance, create a
third, user facing address which redirects to one instance. Ask users to always sign in to
the user facing address. If there are issues, the administrator should change the redirect.
