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: ReadyStandalonewildfire-apps-service: Readyglobal-queue-service: ReadyStandalonewildfire-management-service: Done siggen-db: ReadyMaster Diag report: 10.10.10.100: reported leader '10.10.10.100', age 0. 10.10.10.100: local node passed sanity check.
- 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
- 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.
Recommended For You
Recommended videos not found.