Add Standalone WildFire Appliances to Manage with Panorama
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
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy 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 Hyper-V
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
- Mount the Panorama ESXi Server to an NFS Datastore
-
- 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 Hyper-V
- Increase CPUs and Memory for Panorama on KVM
- Increase 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
-
- Panorama, Log Collector, Firewall, and WildFire Version Compatibility
- Install Updates for Panorama in an HA Configuration
- Install Updates for Panorama with an Internet Connection
- Install Updates for Panorama When Not Internet-Connected
- Install Updates Automatically for Panorama without an Internet Connection
- Migrate Panorama Logs to the New Log Format
-
- 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-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 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
-
- Add a Firewall as a Managed Device
-
- Add a 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
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute Data to Managed Firewalls
-
- 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
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- 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 Commit Failures
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Downgrade from Panorama 10.0
End-of-Life (EoL)
Add Standalone WildFire Appliances to Manage with Panorama
You can manage up to 200 WildFire appliances
with a Panorama M-Series or virtual appliance. The 200 WildFire
appliance limit is the combined total of standalone appliances and
WildFire appliance cluster nodes (if you also Configure
a Cluster and Add Nodes on Panorama).
Ensure that Panorama
runs at least version 8.0.1, and that any WildFire appliance you
add to Panorama also runs at least version 8.0.1.
- Using the local CLI, verify that each WildFire appliance that you want to manage with Panorama runs PAN-OS 8.0.1 or later.admin@qa16>show system info | match versionsw-version: 8.0.1-c45 wf-content-version: 702-283 logdb-version: 8.0.15
- On each Panorama appliance you want to use to manage WildFire appliances, verify that Panorama runs version 8.0.1 or later:displays the running software version.DashboardGeneral InformationSoftware Version
- If you aren’t sure if a WildFire appliance belongs to a WildFire appliance cluster or is a standalone appliance on the local WildFire appliance CLI, check theNode modeto ensure that the status isstand_aloneand check theApplication statusto ensure that theglobal-db-serviceandglobal-queue-serviceindicateReadyStandalone.admin@WF-500>show cluster membershipService Summary: wfpc signature Cluster name: Address: 10.10.10.100 Host name: WF-500 Node name: wfpc-012345678901-internal Serial number: 012345678901Node mode: stand_aloneServer role: True HA priority: Last changed: Mon, 06 Mar 2017 16:34:25 -0800 Services: wfcore signature wfpc infra Monitor status: Serf Health Status: passing Agent alive and reachable Application status:global-db-service: ReadyStandaloneglobal-queue-service: ReadyStandalone
- If the WildFire appliances you want to manage with Panorama are new, check Get Started with WildFire to ensure that you complete basic steps such as confirming your WildFire license is active, enabling logging, connecting firewalls to WildFire appliances, and configuring basic WildFire features.
- On the local CLI of each WildFire appliance the Panorama server will manage, configure the IP address of the Panorama server.Before you register standalone WildFire appliances to a Panorama appliance, you must first configure the Panorama IP address or FQDN on each WildFire appliance. This is how each WildFire appliance knows which Panorama appliance manages it.
- Configure the IP address or FQDN of the primary Panorama appliance’s management interface:admin@WF-500#set deviceconfig system panorama-server <ip-address | FQDN>
- If you use a backup Panorama appliance for high availability (recommended), configure the IP address or FQDN of the backup Panorama appliance’s management interface:admin@WF-500#set deviceconfig system panorama-server-2 <ip-address | FQDN>
- Register WildFire appliances on the primary Panorama appliance.
- From the Panorama web interface,andPanoramaManaged WildFire AppliancesAdd Appliance.
- Enter the serial number of each WildFire appliance on a separate line. If you do not have a list of serial numbers, on each WildFire appliance, run:admin@WF-500>show system info | match serialserial: 012345678901Several local CLI commands display the WildFire appliance serial number, includingshow cluster membership.
- ClickOK.If it is available, information about configuration that is already committed on the WildFire appliances displays, such as IP address and software version.
- (Optional) Import WildFire appliance configurations into the Panorama appliance.
- Select the appliances that have configurations you want to import from the list of managed WildFire appliances.
- Import Config.
- SelectYes.Importing configurations updates the displayed information and makes the imported configurations part of the Panorama appliance candidate configuration.
- Commit to Panoramato make the imported WildFire appliance configurations part of the Panorama running configuration.
- Configure or confirm the configuration of the WildFire appliance interfaces.Each WildFire appliance has four interfaces:Management(Ethernet0),Analysis Network Environment(Ethernet1),Ethernet2, andEthernet3.
- Selectand select a WildFire appliance.PanoramaManaged WildFire Appliances
- SelectInterfaces.
- Select an interface to configure or edit it. You can enable the interface, set the speed and duplex, the IP address and netmask, the default gateway, the MTU, the DNS server, the link state, and theManagement Servicesfor each interface. You can alsoAddpermitted IP addresses so that an interface accepts traffic only from specified addresses.TheAnalysis Network Environment,Ethernet2, andEthernet3interfaces support onlyPingas aManagement Servicesoption.TheManagementinterface supportsPing,SSH, andSNMPasManagement Servicesoptions. In addition, theManagementinterface supports proxy server configuration in case a direct connection to the internet is not possible.
- ClickOKafter you configure or confirm the settings.
- Commit the configuration on the Panorama appliance and push it to the appliance or to multiple appliances.
- Commit and Push.
- If there are configurations on the Panorama appliance that you do not want to push,Edit Selectionsto choose the appliances to which you push configurations. The pushed configuration overwrites the running configuration on the WildFire appliance.
- Verify the configuration.
- Select.PanoramaManaged WildFire Appliances
- Check the following fields:
- Connected—State isConnected.
- Role—Each WildFire appliance’s role isStandalone.
- Config Status—Status isIn Sync.
- Last Commit State—Commit succeeded.