Move a Firewall to a Different Device Group
Table of Contents
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on Alibaba Cloud
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on Alibaba Cloud
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Increase the CPUs and Memory for Panorama on Oracle Cloud Infrastructure (OCI)
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
- Install the Device Certificate for a Dedicated Log Collector
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-500 Appliance to an M-700 Appliance
- Migrate from an M-600 Appliance to an M-700 Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Admin Role Profile for Selective Push to Managed Firewalls
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
- Configure Tracking of Administrator Activity
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Move a Firewall to a Different Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Device Group Push to a Multi-VSYS Firewall
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Schedule a Configuration Push to Managed Firewalls
- Redistribute Data to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Configure a Managed Collector
- Monitor Managed Collector Health Status
- Configure Log Forwarding to Panorama
- Configure Syslog Forwarding to External Destinations
- Forward Logs to Strata Logging Service
- Verify Log Forwarding to Panorama
- Modify Log Forwarding and Buffering Defaults
- Configure Log Forwarding from Panorama to External Destinations
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
-
-
- Preview, Validate, or Commit Configuration Changes
- Commit Selective Configuration Changes for Managed Devices
- Push Selective Configuration Changes to Managed Devices
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- View Log Query Jobs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- View Task Success or Failure Status
- Generate a Stats Dump File for a Managed Firewall
- Recover Managed Device Connectivity to Panorama
- Restore an Expired Device Certificate
Move a Firewall to a Different Device Group
Migrate a managed firewall from one device group to another on Panorama to change its
policy and object inheritance.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
Move a firewall to a different device group when organizational changes require
different security policies and objects. Common scenarios include organizational
restructuring, mergers and acquisitions, role-based policy changes, or migrating
workloads between business units. Each managed firewall or virtual system can belong to
only one device group at a time. Moving a firewall changes which policies and objects it
inherits from Panorama.
Moving a firewall to a new device group removes all policies and objects inherited
from the old group. If the firewall relies on specific security rules, NAT rules,
or objects from the old device group, move or clone them to the new device group (or
a shared parent) before moving the device to prevent traffic drops and avoid
validation errors.
If you do not move required policies and objects first, you may encounter validation
errors including:
- Duplicate object names across rulebases
- Duplicate addresses and address groups
- Duplicate VPN tunnels and NAT rules
- Invalid IP address references
- Configuration conflicts that prevent commits
- (Optional but Recommended) Move or clone required policies and objects to the new device group.If the firewall depends on policies or objects that exist only in the old device group, move or clone them to the new device group before moving the firewall.
- Select PoliciesSecurity (or the relevant policy type).For Device Group, choose the source device group (the group the firewall is currently in).Select the policy rules you want to keep for the firewall.Click Move (to remove from the old group and add to the new group) or Clone (to keep in the old group and add to the new group).Select the destination device group and click OK.Repeat for any required address objects, address groups, service objects, or other policy objects.For more information, see Move or Clone a Policy Rule or Object to a Different Device Group.Move the firewall to the new device group.
- Select PanoramaDevice Groups.In the device group list, select the source device group (the group the firewall is currently in).Click Edit to open the device group configuration.In the Devices section, uncheck the box next to the firewall to remove it from this device group.Click OK.In the device group list, select the destination device group (the group you want to move the firewall to).Click Edit to open the device group configuration.In the Devices section, check the box next to the firewall to add it to this device group.Click OK.Commit the changes to Panorama.
- Click Commit and select Commit to Panorama.Verify the changes and click Commit.This updates Panorama to reflect that the device now belongs to the new device group. The firewall has not yet received the new configuration.Push the configuration to the firewall.
- Click Commit and select Push to Devices (or Commit and Push if you skipped the previous step).Click Edit Selections.In the Device Groups tab, select the destination device group.Ensure the firewall you moved is selected in the device list.(Optional) Select Force Template Values if the new device group or template stack has significantly different network settings you need to enforce.A standard push is usually sufficient for policy and object changes. Use Force Template Values only when you need to override local template settings on the firewall.Click OK and then click Push.Verify the firewall received the configuration from the new device group.
- Select PanoramaManaged DevicesSummary.Verify the Device State shows Connected and the Config column shows In sync.Verify the Device Group column shows the correct destination device group name.Alternative Method: Use Device ReassociationYou can also move a firewall between device groups using the Reassociate function in Panorama. This method allows you to change the device group assignment along with template stack and other associations in a single operation.