Zone Rename effects on Panorama and Managed Devices

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

Zone Rename effects on Panorama and Managed Devices

L1 Bithead

Hello Everyone

 

I have simple but very important questions about an eventual Zone Renaming in a Template commited and pushed from Panorama to a Managed devices:

 

1. Changing Zone names inevitably will have an impact on an active sessions ?   

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

 

2. In PAN-OS 9.0 could I ignore the possibility of taking issues renaming zones when I"ll push them from Panorama? 

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

 

3. After renaming zones successfully the Historical Logs on Monitor (traffic, threat, url) will update the Zone Fields on the Panorama (Log Collector) and the Managed Devices?  

 

Thanks for your help 

1 accepted solution

Accepted Solutions

L4 Transporter

Hello @egarantiva 

 

The zones are defined in "Templates", and used in "Device Groups". The config push is not a one-shot (if I see it right), meaning panorama is pushing in part after the other.

We had a similar need, followed the following procedure:

- create new zones, but don't assign it to interfaces

- push the templates

- append new zones to policies (you might need to clone NAT policies) -- I did this using a script, making use of the API

- push the device groups

- adjust the interfaces (use the new zones)

- push the templates

- remove the no longer required zones

 

I would not expect the historic logs will change if you change the zones.

 

Best Regards

  Joerg

View solution in original post

1 REPLY 1

L4 Transporter

Hello @egarantiva 

 

The zones are defined in "Templates", and used in "Device Groups". The config push is not a one-shot (if I see it right), meaning panorama is pushing in part after the other.

We had a similar need, followed the following procedure:

- create new zones, but don't assign it to interfaces

- push the templates

- append new zones to policies (you might need to clone NAT policies) -- I did this using a script, making use of the API

- push the device groups

- adjust the interfaces (use the new zones)

- push the templates

- remove the no longer required zones

 

I would not expect the historic logs will change if you change the zones.

 

Best Regards

  Joerg

  • 1 accepted solution
  • 5388 Views
  • 1 replies
  • 0 Likes
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!