Advanced WildFire Powered by Precision AI™
WildFire Application States
Table of Contents
Expand All
|
Collapse All
Advanced WildFire
-
-
- Forward Files for Advanced WildFire Analysis
- Manually Upload Files to the WildFire Portal
- Forward Decrypted SSL Traffic for Advanced WildFire Analysis
- Enable Advanced WildFire Inline Cloud Analysis
- Enable Advanced WildFire Inline ML
- Enable Hold Mode for Real-Time Signature Lookup
- Configure the Content Cloud FQDN Settings
- Sample Removal Request
- Firewall File-Forwarding Capacity by Model
-
-
-
- set deviceconfig cluster
- set deviceconfig high-availability
- set deviceconfig setting management
- set deviceconfig setting wildfire
- set deviceconfig system eth2
- set deviceconfig system eth3
- set deviceconfig system panorama local-panorama panorama-server
- set deviceconfig system panorama local-panorama panorama-server-2
- set deviceconfig system update-schedule
- set deviceconfig system vm-interface
-
- clear high-availability
- create wildfire api-key
- delete high-availability-key
- delete wildfire api-key
- delete wildfire-metadata
- disable wildfire
- edit wildfire api-key
- load wildfire api-key
- request cluster decommission
- request cluster reboot-local-node
- request high-availability state
- request high-availability sync-to-remote
- request system raid
- request wildfire sample redistribution
- request system wildfire-vm-image
- request wf-content
- save wildfire api-key
- set wildfire portal-admin
- show cluster all-peers
- show cluster controller
- show cluster data migration status
- show cluster membership
- show cluster task
- show high-availability all
- show high-availability control-link
- show high-availability state
- show high-availability transitions
- show system raid
- submit wildfire local-verdict-change
- show wildfire
- show wildfire global
- show wildfire local
- test wildfire registration
WildFire Application States
Where Can I Use This? | What Do I Need? |
---|---|
|
|
The WildFire appliance operates a series of
internal applications to manage and coordinate processing of sample
data. These applications and their requisite statuses are shown
when viewing the status of a WildFire appliance cluster.
The
following list shows the cluster components, purpose, and status
conditions:
Name | Description | Possible Status Conditions | Definition |
---|---|---|---|
global-db-service | This application database
is used to store WildFire analysis data. | AcquiringSessionSpinLock | Waiting for the session spin lock until acquiring
the lock or timeout. |
Bootstrapping | The sample database application is currently
in a bootstrapping state. | ||
BootstrappingNoMeet | The local sample database service started without
forming a cluster with other WildFire appliances. | ||
FailedToBecomeWorker | Failed to join the cluster as a worker node. | ||
FailedToBootstrap | The bootstrapping process has failed. | ||
FailedToJoinCluster | Failed to join the cluster. | ||
FailedToStartServices | Internal database services failed to start. | ||
MaintenanceDecommission | Starting decommission process for database
services. | ||
MaintenanceDecommissionDone | Database service has been decommissioned. | ||
MaintenanceFailover | Starting the process to demote local service
and failover backup replica. | ||
MaintenanceFailed | Service failover has failed. | ||
MaintenanceFailoverDone | Service failover is done. | ||
MaintenanceRecoverFromSplitbrain | If the WildFire appliance is currently in split-brain
mode, the database service state will be set to MaintenanceRecoverFromSplitbrain
upon the start of the service. | ||
MaintenanceSuspend | The database service is in the process of
being suspended as a result of the user issuing one of the following
commands: debug cluster suspend or request cluster decommission. | ||
MaintenanceSuspendDone | The database service has completed the suspension
process. | ||
DataMigration | The contents of the local database is being merged
with the primary database. This occurs when a WildFire appliance
joins a cluster. | ||
DataMigrationDone | The data migration process is complete. | ||
DataMigrationFailed | The data migration process has failed. | ||
JoinedCluster | The local database service has joined the cluster. | ||
Ready | The database service is in a ready state. | ||
ReadyLeader | The database service is in a ready state
and the appliance is set as the leader. | ||
ReadyStandalone | The database service is in a ready state
and the appliance is operating as a standalone appliance. | ||
Splitbrain | A split-brain condition has been detected
and the database services has entered split-brain mode. The service
will transition to ReadyStandalone shortly. | ||
StandbyAsWorker | The worker node database service is in a standby
state. | ||
WaitingforLeaderReady | The local node is waiting to join the leader node. |
Name | Description | Possible Status Conditions | Definition |
---|---|---|---|
global-queue-service | Handles the management and prioritization
of samples sent for WildFire analysis. | Bootstrapping | Queuing service application is currently
in a bootstrapping state. |
FailedToBecomeWorker | Failed to join the cluster as a worker node. | ||
FailedToBootstrap | The bootstrapping process has failed. | ||
FailedToJoinCluster | Failed to join the cluster. | ||
FailedToStartServices | Internal queuing services failed to start. | ||
MaintenanceDecommission | Starting decommission process for queuing
services. | ||
MaintenanceDecommissionDone | Queuing service has been decommissioned. | ||
MaintenanceFailover | Starting the process to demote local service
and failover backup replica. | ||
MaintenanceFailed | Service failover has failed. | ||
MaintenanceFailoverDone | Service failover is done. | ||
MaintenanceRecoverFromSplitbrain | If the WildFire appliance is currently in split-brain
mode, the queuing service state will be set to | ||
MaintenanceSuspend | The queuing service is in the process of
being suspended as a result of the user issuing one of the following
commands: debug cluster suspend or request cluster decommission. | ||
MaintenanceSuspendDone | The queuing service has completed the suspension
process. | ||
JoinedCluster | The queuing service has joined the cluster. | ||
Ready | The queuing service is in a ready state. | ||
ReadyLeader | The queuing service is in a ready state
and the appliance is set as the leader. | ||
ReadyStandalone | The queuing service is in a ready state
and the appliance is operating as a standalone appliance. | ||
Splitbrain | A split-brain condition has been detected
and the queuing services has entered split-brain mode. The service
will transition to ReadyStandalone shortly. | ||
StandbyAsWorker | The worker node queuing service is in a standby
state. |
Name | Description | Possible Status Conditions | Definition |
---|---|---|---|
siggen-db | Generates WildFire private signatures
and analysis samples. | DatabaseFailover | When HA failover occurs, the passive controller
becomes the active controller. The signature service in the passive
controller becomes the primary and the state is set to DatabaseFailover. |
DatabaseFailoverFaild | The signature database failover has failed. | ||
DataMigration | The contents of the local signature database
is being merged with the primary database. This occurs when a WildFire appliance
joins a cluster. | ||
DataMigrationDone | The data migration process is complete. | ||
DataMigrationFailed | The data migration process has failed. | ||
Deregistered | Signature database service has been deregistered. | ||
MaintenanceDecommission | Starting decommission process for signature
database services. | ||
MaintenanceDecommissionDone | Queuing service has been decommissioned. | ||
MaintenanceFailover | Starting the process to demote local service
and failover backup replica. | ||
MaintenanceFailoverDone | Service failover is done. | ||
MaintenanceSuspend | The signature database service is in the process
of being suspended as a result of the user issuing one of the following commands:
debug cluster suspend or request cluster decommission. | ||
MaintenanceSuspendDone | The signature database service has completed
the suspension process. | ||
MigrateMalwareDatabase | When upgrading PAN-OS from
version 7.1 to 8.0, the sample data is converted to a different format.
These states indicate the progress of the data migration process. | ||
MigrateSiggenDatabaseStage1 | |||
MigrateSiggenDatabaseStage2 | |||
MigrateSiggenDatabaseStage3 | |||
Ready | The signature database service is in a ready
state. | ||
ReadyMaster | The signature database service is in primary
mode and is operating on the active controller. | ||
ReadySlave | The signature database service is in backup
mode and is operating on the passive controller. | ||
ReadyStandalone | The signature database service is in a ready
state and the appliance is operating as a standalone appliance. | ||
Splitbrain | A split-brain condition has been detected
and the signature database service has entered split-brain mode.
The service will transition to ReadyStandalone shortly. | ||
Stopped | The signature database service has stopped
on the appliance. |
Name | Description | Possible Status Conditions | Definition |
---|---|---|---|
wildfire-management-service | WildFire work mode management service. | Running | The WildFire management service is in an operational state. |
Done | The WildFire management service has finished running. |
Name | Description | Possible Status Conditions | Definition |
---|---|---|---|
wildfire-apps-service | WildFire infrastructure applications. | Deregistered | The WildFire applications service has been
deregistered. |
Ready | The WildFire applications service is in
a ready state. | ||
Restored | The WildFire applications service has finished
maintenance procedures. | ||
Scheduling | The WildFire applications service is in
a scheduling state. | ||
SetupSampleStorage | This WildFire applications service operates
when WildFire is being upgraded from 7.1 to 8.0. | ||
Stopped | The WildFire applications service has stopped
on the appliance. | ||
Suspended | The WildFire applications service has been
suspended due to maintenance. |