Panorama import devices with simi lar config

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Panorama import devices with simi lar config

L4 Transporter

Hi,

 

I have to import several FWs (branches) in Panorama. All the FW has similar config/object related to interfaces IP, objects, etc.

It could be any issue in the device groups or templated if all branches have same same internal IP interface. I thought to create a template and Device Group unique for each branch.

 

Thanks

1 accepted solution

Accepted Solutions

Community Team Member

Hi @BigPalo ,

 

Having the same internal IP ranges/interfaces on different firewalls won’t break Panorama. Each fw keeps its own runtime config, but Panorama will flag conflicts if you try to push overlapping IPs within the same template.

 

A good approach is to use template stacks:

  • Site-specific templates for branch settings like interface IPs, VRs, and zones.

  • A global template for shared items such as server profiles, log forwarding, network profiles, interface management, zone protection (think any config that might be shared across sites)

For Device Groups, you can mirror this model:

  • A shared device group for common objects and policies.

  • Branch-specific device groups for rules or NAT configs unique to each site.

This way you keep consistency where it makes sense while still isolating site-specific configs. The biggest lift is upfront planning, but once you understand the nuances of your sites, Panorama management becomes much easier.

 

Good luck!

LIVEcommunity team member
Stay Secure,
Jay
Don't forget to Like items if a post is helpful to you!

Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

1 REPLY 1

Community Team Member

Hi @BigPalo ,

 

Having the same internal IP ranges/interfaces on different firewalls won’t break Panorama. Each fw keeps its own runtime config, but Panorama will flag conflicts if you try to push overlapping IPs within the same template.

 

A good approach is to use template stacks:

  • Site-specific templates for branch settings like interface IPs, VRs, and zones.

  • A global template for shared items such as server profiles, log forwarding, network profiles, interface management, zone protection (think any config that might be shared across sites)

For Device Groups, you can mirror this model:

  • A shared device group for common objects and policies.

  • Branch-specific device groups for rules or NAT configs unique to each site.

This way you keep consistency where it makes sense while still isolating site-specific configs. The biggest lift is upfront planning, but once you understand the nuances of your sites, Panorama management becomes much easier.

 

Good luck!

LIVEcommunity team member
Stay Secure,
Jay
Don't forget to Like items if a post is helpful to you!

Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.
  • 1 accepted solution
  • 106 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!