Known Issues Specific to the WF-500 Appliance

Known issues specific to the WF-500 Appliance
The following list includes known issues specific to WildFire® 8.1 releases running on the WF-500 appliance. See also the specific and general Known Issues Related to PAN-OS 8.1 Releases.
Issue ID
A Panorama™ management server running PAN-OS® 8.1 does not currently support management of appliances running WildFire 7.1 or earlier releases. Even though these management options are visible on the Panorama 8.1 web interface (PanoramaManaged WildFire Clusters and PanoramaManaged WildFire Appliances), making changes to these settings for appliances running WildFire 7.1 or an earlier release has no effect.
This issue is now resolved. SeePAN-OS 8.1.6 Addressed Issues.
(RADIUS server profile configurations only) You cannot send a commit from a Panorama appliance running a PAN-OS 8.1 release to a WF-500 appliance running a PAN-OS 8.0 release because the RADIUS authentication protocol is incorrectly changed to CHAP authentication.
This issue is now resolved. SeePAN-OS 8.1.6 Addressed Issues.
In rare cases when you upgrade a WF-500 appliance from a PAN-OS 7.1 release to a PAN-OS 8.0 release, the disk partition becomes full due to the amount of data on the drive. When you try deleting the backup database to free up space, the debug wildfire reset backup-database-for-old-samples CLI command fails and displays the following error: Servererror : Client wf_devsrvr not ready.
The Create Date shown when using the show wildfire global sample-status sha256 equal<hash> and show wildfire global sample-analysis CLI commands is two hours behind the actual time for WF-500 appliance samples.
WildFire appliances build and release all untested signatures to the connected firewalls every five minutes, which is the maximum time that a signature remains untested (not released to firewalls). When a WildFire appliance joins a cluster, if any untested (unreleased) signatures are on the appliance, they may be lost instead of migrating to the cluster, depending on when the last build of untested signatures occurred.

Related Documentation