multi vsys security policy with ANY zone

Reply
L2 Linker

multi vsys security policy with ANY zone

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?

Tags (1)
L7 Applicator

Re: multi vsys security policy with ANY zone

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

L2 Linker

Re: multi vsys security policy with ANY zone

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.

L2 Linker

Re: multi vsys security policy with ANY zone

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!