Policy installation on two different cluster

[max71]

Hello teams, 

I run in this strange situation.

Scenario:

I have a single MGM Gaia version 81.10 JH 87 that control two different cluster located in two different sites

Every cluster has two members.

The 1° cluster has many change daily with install policy frequently but the second is very uncommon.

Yesterday i did a chenge into the second and in the policy i have seen more or less 118 change, in detail i have seen that the chenge are included all change made in 1° cluster... but why this happen is confusing because i understand theat the change should be related only at the cluster where i wish to apply the change.

Any help is appreciated.

Max

[G_W_Albrecht]

I think that all changes done adds to this value. In the compiled policy for the cluster these changes could not appear / be relevant at all, it is only that a number of changed have been done since last policy install.

[max71]

Ok sorry for my understand, seems that the policy installation is a sum of all policy (cluster1 + cluster2) and if i install a policy in cluster 2 show me the number of change made from last installation made in this cluster(cluster2). 

Example from 1 sept is made 80 change but in reality 76 are made in cluster 1 and only 6 in cluster 2, but the installation show me the sum of change.

When i apply the installation policy in cluster 2 will be only 6 right ?

Max

[G_W_Albrecht]

Compiled policy for each cluster contains all config relevant for it. Number of changes is the sum for this policy package, you can e.g. add objects that are not used at the moment, they will add to changes, but they will not go into any policy, only be kept in the policy package.

[PhoneBoy · Accepted solution]

Even if the policies in use for the different clusters are different, they share the same object database.
Which means any changes to an object...even if not in use in the policy by the gateway...will ultimately get pushed to the gateway.
I'm fairly certain this is reflected in the change count and is expected behavior.