Rule UUIDs Always Change

[iaingthompson]

Greetings Community! 

Apologies if this has been answered in a previous thread- I couldn't find anything... 

When exporting configuration files from PA-3220 I have noticed that sometimes the rule UUIDs are different than the previous config dump and sometimes they are the same. 

Can someone please explain why this is? What causes the rule UUID to change between config dumps when the rule itself has not changed? 

TIA, 

Iain

[PavelK]

Hello @iaingthompson

thanks for posting.

I spent some time going through documentation. Based on documentation: Track Rules Within a Rulebase the UUID never changes unless you regenerate UUID from CLI. Is it possible that some of the rules that you identified with a new UUID were actually cloned and later renamed to match name of original policy?

Kind Regards

Pavel 

[iaingthompson]

Hi Pavel, 

Thank you for your assistance. I took two firewalls and made the exact same change on them both- Cloned a rule and renamed the cloned rule. I would have expected this to regenerate UUIDs on both devices however it only did so on device 1. The changed UUIDs don't seem to affect anything and the configuration can be successfully uploaded, so I'm happy to essentially ignore it. However I was more so curious as to why this happens. In the case of device 1, I did not regenerate the UUIDs from the device CLI. 

Regards,

Iain