Hello everyone.
We have a dual site setup with R81.10 JHF Take 172.
We noticed that when we make a change on SmartProvisioning and install the policy, only the active chassis receives the policy and updates the policy singature.
For example,
[Global] clish > asg policy verify -a
+----------------------------------------------------------------------+
|Policy Verification |
+-------+-------------------+---------------+-----------------+--------+
|SGM |Policy Name |Policy Date |Policy Signature |Status |
+-------+-------------------+---------------+-----------------+--------+
|1_01 |Standard |14Apr25 09:44 |49c54a3e2 |Failed |
|2_01 |Standard |14Apr25 09:44 |e96b2c0b7 |Failed |
+-------+-------------------+---------------+-----------------+--------+
But when we install a policy without making any changes on SmartProvisioning, everything works, all gateways receive policy, same policy signatures. Example,
+----------------------------------------------------------------------+
|Policy Verification |
+-------+-------------------+---------------+-----------------+--------+
|SGM |Policy Name |Policy Date |Policy Signature |Status |
+-------+-------------------+---------------+-----------------+--------+
|1_01 |Standard |17Apr25 01:17 |fde3508f3 |Success |
|2_01 |Standard |17Apr25 01:17 |fde3508f3 |Success |
+-------+-------------------+---------------+-----------------+--------+
We have been consistently able to replicate this. We thought it may be some sync problems, but policy installation without SP works perfectly fine, so it doesn't look like a sync issue. At leasst not when a normal policy is pushed.
asg diag verify only shows "Policy signature doesn't match on all SGMs" error and everything else is just "Passed". And we see that only after a policy push that contains a change in SP.
I'm not experienced in SmartProvisioning, maybe it has its own policy push mechanism besides SmartConsole or SmartUpdate. But I stand corrected here.
As always, any ideas are deeply appreciated.
Cheers!
.png "Wolfgang"){kind=avatar}
