Template Stacks
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- Objects > Addresses
- Objects > Address Groups
- Objects > Regions
- Objects > Dynamic User Groups
- Objects > Application Groups
- Objects > Application Filters
- Objects > Services
- Objects > Service Groups
- Objects > External Dynamic Lists
- Objects > Custom Objects > Spyware/Vulnerability
- Objects > Custom Objects > URL Category
- Objects > Security Profiles > Antivirus
- Objects > Security Profiles > Anti-Spyware Profile
- Objects > Security Profiles > Vulnerability Protection
- Objects > Security Profiles > File Blocking
- Objects > Security Profiles > WildFire Analysis
- Objects > Security Profiles > Data Filtering
- Objects > Security Profiles > DoS Protection
- Objects > Security Profiles > GTP Protection
- Objects > Security Profiles > SCTP Protection
- Objects > Security Profile Groups
- Objects > Log Forwarding
- Objects > Authentication
- Objects > Decryption > Forwarding Profile
- Objects > Schedules
-
-
- Firewall Interfaces Overview
- Common Building Blocks for Firewall Interfaces
- Common Building Blocks for PA-7000 Series Firewall Interfaces
- Tap Interface
- HA Interface
- Virtual Wire Interface
- Virtual Wire Subinterface
- PA-7000 Series Layer 2 Interface
- PA-7000 Series Layer 2 Subinterface
- PA-7000 Series Layer 3 Interface
- Layer 3 Interface
- Layer 3 Subinterface
- Log Card Interface
- Log Card Subinterface
- Decrypt Mirror Interface
- Aggregate Ethernet (AE) Interface Group
- Aggregate Ethernet (AE) Interface
- Network > Interfaces > VLAN
- Network > Interfaces > Loopback
- Network > Interfaces > Tunnel
- Network > Interfaces > SD-WAN
- Network > VLANs
- Network > Virtual Wires
-
- Network > Network Profiles > GlobalProtect IPSec Crypto
- Network > Network Profiles > IPSec Crypto
- Network > Network Profiles > IKE Crypto
- Network > Network Profiles > Monitor
- Network > Network Profiles > Interface Mgmt
- Network > Network Profiles > QoS
- Network > Network Profiles > LLDP Profile
- Network > Network Profiles > SD-WAN Interface Profile
-
-
- Device > Setup
- Device > Setup > Management
- Device > Setup > Interfaces
- Device > Setup > Telemetry
- Device > Setup > Content-ID
- Device > Setup > WildFire
- Device > Log Forwarding Card
- Device > Config Audit
- Device > Administrators
- Device > Admin Roles
- Device > Access Domain
- Device > Authentication Sequence
-
- Security Policy Match
- QoS Policy Match
- Authentication Policy Match
- Decryption/SSL Policy Match
- NAT Policy Match
- Policy Based Forwarding Policy Match
- DoS Policy Match
- Routing
- Test Wildfire
- Threat Vault
- Ping
- Trace Route
- Log Collector Connectivity
- External Dynamic List
- Update Server
- Test Cloud Logging Service Status
- Test Cloud GP Service Status
- Device > Virtual Systems
- Device > Shared Gateways
- Device > Certificate Management
- Device > Certificate Management > Certificate Profile
- Device > Certificate Management > OCSP Responder
- Device > Certificate Management > SSL/TLS Service Profile
- Device > Certificate Management > SCEP
- Device > Certificate Management > SSL Decryption Exclusion
- Device > Response Pages
- Device > Server Profiles
- Device > Server Profiles > SNMP Trap
- Device > Server Profiles > Syslog
- Device > Server Profiles > Email
- Device > Server Profiles > HTTP
- Device > Server Profiles > NetFlow
- Device > Server Profiles > RADIUS
- Device > Server Profiles > TACACS+
- Device > Server Profiles > LDAP
- Device > Server Profiles > Kerberos
- Device > Server Profiles > SAML Identity Provider
- Device > Server Profiles > DNS
- Device > Server Profiles > Multi Factor Authentication
- Device > Local User Database > Users
- Device > Local User Database > User Groups
- Device > Scheduled Log Export
- Device > Software
- Device > Dynamic Updates
- Device > Licenses
- Device > Support
-
- Network > GlobalProtect > MDM
- Network > GlobalProtect > Device Block List
- Network > GlobalProtect > Clientless Apps
- Network > GlobalProtect > Clientless App Groups
- Objects > GlobalProtect > HIP Profiles
-
- Use the Panorama Web Interface
- Context Switch
- Panorama Commit Operations
- Defining Policies on Panorama
- Log Storage Partitions for a Panorama Virtual Appliance in Legacy Mode
- Panorama > Setup > Interfaces
- Panorama > High Availability
- Panorama > Administrators
- Panorama > Admin Roles
- Panorama > Access Domains
- Panorama > Device Groups
- Panorama > Plugins
- Panorama > Log Ingestion Profile
- Panorama > Log Settings
- Panorama > Scheduled Config Export
End-of-Life (EoL)
Template Stacks
You can configure a template stack or assign templates
to a template stack. Assigning firewalls to a template stack allows you to push
all necessary settings to the firewalls instead of adding every
setting to every template individually. Panorama supports up to
1,024 stacks. You can Add Stack to create
a new template stack and configure the settings as described in
the following table. After you configure a template stack, you must
commit your changes in Panorama (see Panorama
Commit Operations). Additionally, after you configure the
network and device settings of firewalls assigned to the stack,
you must perform a template commit and push the settings to the
firewalls.
Deleting a template stack or removing
a firewall from a template stack does not delete the values that
Panorama previously pushed to that firewall; however, when you remove
a firewall from a template stack, Panorama no longer pushes new
updates to that firewall.
Template Stack Settings | Description |
---|---|
Name | Enter a stack name (up to 31 characters).
The name is case-sensitive, must be unique, must start with a letter,
and can contain only letters, numbers, and underscores. In the Device and Network tabs,
the Template drop-down displays the stack
name and its assigned templates. |
Description | Enter a description for the stack. |
Templates | Add each template
you want to include in the stack (up to 8). If templates have
duplicate settings, Panorama pushes only the settings from the template that
is higher in the list when pushing settings to the assigned firewalls.
For example, if Template_A is above Template_B in the list and both
templates define the ethernet1/1 interface, then Panorama pushes
the ethernet1/1 definition from Template_A and not from Template_B.
To change the order of templates in the list, select a template and Move
Up or Move Down. Panorama doesn’t validate template combinations
in stacks so plan the order of your
templates to avoid invalid relationships. |
Devices | Select each firewall that you want to add
to the stack. If the list of firewalls is long, you can filter the
list by Platforms, Device Groups, Tags,
and HA Status. You can assign
firewalls that have non-matching modes (VPN mode, multiple virtual
systems mode, or operational mode) to the same stack. Panorama pushes
mode-specific settings only to those firewalls that support those
modes. |
Select All | Selects every firewall in the list. |
Deselect All | Deselects every firewall in the list. |
Group HA Peers | Groups firewalls that are high availability
(HA) peers. This enables you to easily identify firewalls that have
an HA configuration. When pushing settings from the template stack,
you can push to the grouped pair instead of to each firewall individually. |
Filter Selected | To display only specific firewalls, select
them and then Filter Selected. |