Vsys name and Zone name commit fail

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Vsys name and Zone name commit fail

L1 Bithead

I wanted to share this experience and maybe see if this is a bug or simply a condition of how PAN works.


I am migrating multiple ASA contexts into a multi-vsys PAN environment. I was doing a partial load config/xpath sequence from the CLI and I got errors on moving the vsys over.




After much testing the solution was to make sure the name of the vsys and the name of a security zone were NOT an identical match. In our case, changing the name of the vsys is much easier than a security zone where the subsequent rules did not automatically change the referenced zone name. Again, not sure if this is a bug or if this has to be this way as a result of how PAN processes things.


L6 Presenter

@micharr  You are correct, PAN-OS does not allow to have same name on vsys and zone , I just tried to create a new zone called "vsys1" and it is showing error message said vsys 1 already exist. So this is not a bug from Expedition. 


Screen Shot 2023-03-27 at 7.30.54 PM.png



  • 1 replies
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!