Prisma Access Administrator’s Guide (Panorama Managed)
  • Prisma Access Administrator’s Guide (Panorama Managed)
  • All Documentation
>
Prisma Access Deployment Progress and Status
Focus
Download PDF
Focus
  1. Home
  2. Prisma
  3. Prisma Access
  4. Prisma Access Overview
  5. Prisma Access Deployment Progress and Status
Download PDF

Prisma Access Deployment Progress and Status

Table of Contents

Prisma Access Deployment Progress and Status

View the deployment and onboarding status of Prisma Access jobs from Panorama.
When you configure and commit and push your changes for a service connection, remote network connection, mobile user deployment, or clean pipe instance, Prisma Access begins a series of events to complete the deployment process. To allow you to view the progress of onboarding and deployment jobs before they complete, and to view the status of completed jobs, Prisma Access provides you with deployment status information that is available on the Prisma Access status page.
Checking the progress of a job is useful if, for example, you need the Service IP Address of a service connection or remote network connection to complete the IPSec tunnel connection to your customer premises equipment (CPE). Since Prisma Access does not create the Service IP Address until onboarding is complete, you can view the status of the onboarding job from the deployment status page, instead of refreshing the Network Details page and waiting for the Service IP Address to display.
To view the status of deployment jobs, select PanoramaCloud ServicesStatusStatus.
The Deployment Status area displays a graphic element (a bubble) showing the status of the deployment, along with the following text:
Deployment Status TextDescription
StartedThe deployment job has started.
In-ProgressThe deployment job is in progress.
SuccessThe deployment job succeeded.
FailedThe deployment job failed.
TimeoutThe deployment job timed out.
WarningThe deployment job was partially successful; some commit operations succeeded and some commit operations failed.
Click details to view the Job ID of the job, its status, and the percentage of its completion. The Job ID field is the Job ID that is associated with the commit operation in Panorama.
To view more details of a specific deployment job, click the left arrow next to Job ID. The following screenshot shows the deployment status of a commit that has the Panorama Job ID of 1555. The overall status is Warning because two of the nodes failed during the commit stage.
The first line of the job status shows the following information:
  • The type of deployment job (either Service Connections, Remote Networks, Clean Pipe), or the type of mobile user onboarding operation (GlobalProtect Gateways, GlobalProtect Portals, or both gateways and portals).
  • The Number of Nodes that are in the job.
    Nodes represent the number of cloud firewalls, gateways, or portals that Prisma Access is configuring for a specific job. The number of nodes do not always correspond to the number of Service Connections, Remote Networks, mobile user locations, or Clean Pipe instances that you deployed; for example, onboarding a location might cause configuration changes to both Prisma Access firewalls and portals.
  • The number of nodes that are still being provisioned (Provisioning in Progress).
  • The number of nodes that failed (Provisioning Failed).
  • The number of nodes that completed provisioning (Provisioning Complete).
The next line in the table provides more granular information about the deployment job. The following screenshot shows three mobile user locations (Australia Southeast, South Africa West, and Brazil East) being successfully onboarded.
FieldDescription
Name (Service Connection, Remote Network, and Clean Pipe deployments only)The name of the service connection, remote network connection, or clean pipe instance.
LocationThe location where the service connection, remote network connection, mobile user, or clean pipe node was onboarded.
Node StatusThe status of the deployment operation.
  • Validation Checks In Progress—The deployment job has started, and preliminary checks are in progress.
  • Validation Checks Succeeded—The deployment job has started, and preliminary checks have succeeded.
  • Validation Checks Failed—The job failed during validation. More information about the failure is available in he Error Details area.
  • Commit In Progress—Validation checks have completed, and the commit job is complete.
  • Commit Succeeded—Validation checks have completed, and the commit job succeeded.
  • Commit Failed—The job failed during the commit stage. More information about the failure is available in he Error Details area.
  • Deployment In Progress—Preliminary checks and commit operations have completed for the job, and deployment is in progress.
  • Deployment Succeeded—The job completed all stages and was successful.
  • Deployment Failed—Preliminary checks and commit operations completed, but the job failed during the deployment stage. More information about the failure is available in he Error Details area.
Action Needed
If a job failed, provides additional information about the steps you can perform to fix the issue (either Commit and push your changes from Panorama again or Open a support case).
Prisma Access does not retain the details of jobs that you onboard and later delete. For example, job 42233 added the Australia Southeast, South Africa West, and Brazil East mobile user locations. If you delete those locations later, clicking the left arrow next to Job ID for job 42233 does not provide any additional details about the job.

Technical Documentation

Company

Legal Notices

© 2025 Palo Alto Networks, Inc. All rights reserved.