multiple central manger

[TCAM]

Q1 - Let say I have 200 sites and divided them into 5 sections, so each section has 40 sites. To share the load, I want to deploy one central manager for each section, so there will be a total of 5 central managers for 200 sites.  Will that be a valid solution?

Q2 - now, I have 5 central managers in the network, do they need to talk to each other? and how?

Thanks in advance for you help.

[patrick.preuss]

Hi Joe

depends on what you want to have :-)

You can manage a lot of devices per CM, with a 512 with 2 gb  ram you can manage 750 Engines.

Then you can setup a second as Secondary for backup.

You have to manage the policies on all CMs.

Load is not so high.

But depends ....

HTH

[TCAM]

Patrick, thanks for taking time to answer this, I appreciated.

So, central manager can be deployed as a "centralized" model like one CM with 750 WAEs as mentioned in your post

Or, it can also be deployed as a "distributed" model like putting 40 sites in one group and assign a dedicated CM for this group.  In my case, I have 200 sites and I want to do "distributed" model, so, I will have 5 groups (5 x 40 sites) and 5 CMs.  Is this a valid solution?

BTW, what are the advantages and dis-advantages of choosing "centralized" over the "distributed" model?

Thanks

Joe

[patrick.preuss]

Hi Joe

as far as i know the Policy and Reporting stuff is not syncronized. Have you a link for a multi central manager setup?

What you can have is a primary and a secondary.

Yes you can setup more cm's i had one in our test lab and policys and reporting are not syned to prod enviroment. We had a link between them.

We migrated to one CM and a secondary....

Cheers

Patrick

[Ryan Posey]

You can have two CMs.  The primary unit manages all policies.  The secondary unit is inaccessable via the GUI and can only be accessed via the CLI.  The browser on the secondary is only available if the primary is offline.  The secondary CM pulls the entire database from the primary CM.  Hence you only need to manage one box.  If the primary died, the secondary will have all policies and traffic history.

I recently converted from a 574 Primary to a vWAAS.

The vWAAS-CM was added as a secondary, once everything replicated, we turned off the primary 574 and promoted the vWAAS to primary.  I have all policies, configurations, and historical reports from the past year intact.  Very impressed with it.