Impacts of installing a policy with a changed name that is managed by SMS

[TSOL]

Hello Team

Currently, there is a R81.20's GW that is managed by R81.20's SMS for policies.

Please inform me of any impacts of applying a policy with the following changes to this GW

(there are no changes to the content of communication):

• Change of the policy name
• Change of policy assignment from all gateways to a specific gateway.

Thank you for the advice.

[cem82]

From what I've found when changing policy name, to avoid impact you need to make sure under the GW properties > Other > Connection Persistence is set to "Rematch connections" to keep any traffic flowing otherwise is an outage.  Pretty sure that's the default anyway but there has been times I've needed to modify it.  Other than that pushing a policy with different name shouldn't be a problem

[AkosBakos]

Hi @TSOL

The Remach connection is a gateway/cluster specifiy setting, If you change the policy, this sennting won't change.

If you push the new policy (same content, but different name) the SmartConsole will notify you about that, there is a policy installed, but different name.

Overall: change the name, push the policy, ant nothing will happen. 🙂

Akos

[G_W_Albrecht]

Both will not make any impact.

[cem82]

Good to know,there was a time I had to do similar and it did drop all connections which was a clone policy just different name  😞  When we changed that connection persistance for the second round it kept them all so maybe something weird was going on for the first GW

[Lesley]

No impact, as long you copy the current policy. If you make new policy and do everything manually then a mistake there could cause impact.