multi vsys security policy with ANY zone

[jasonrakers]

I am testing multi vsys configurations in my lab and noticed that I am unable to use a source/destination zone of "any" in the device group security policy associated with vsys2.  The default vsys1 accepts "any" zone.  When I attempt to commit/validate to the device i get a error like the following attached.  It seems as I can only have defined zones in my security policy when using multi vsys.  This prohibits the use of our global "Shared" rules that are applied across all devices regardless of what zone.

• Details:
• . vsys2 (vsys2)
• . Error: Rulebase 'security'
• . 'any' zone is invalid from rule 'threat'
• . Error: Failed to parse security policy
• . (Module: device)
• . Configuration is invalid

I am using 8.1.10.   Has any one encountered this?

[reaper]

For starters it is not recommended to use "any" (as zones are the pivotal point for zone-based firewalls)

In a multi vats environment, using any could inadvertently allow packets to be passed onto another vats, which is what you are trying to prevent by setting up multi-vsys

[jasonrakers · Accepted solution]

In order to make use of "any" zone, you need to have at least one zone configured for the new vsys.  It does not need to be in use in the Security policy.

[jasonrakers]

Thanks for this one Reaper...

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSVCA0

Good stuff!