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
The Deployment Status area displays a graphic element (a bubble) showing the status of the deployment, along with the following text:
Deployment Status Text
The deployment job has started.
The deployment job is in progress.
The deployment job succeeded.
The deployment job failed.
The deployment job timed out.
The deployment job was partially successful; some commit operations succeeded and some commit operations failed.
detailsto view the Job ID of the job, its status, and the percentage of its completion. The
Job IDfield 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
Warningbecause 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 (eitherService Connections,Remote Networks,Clean Pipe), or the type of mobile user onboarding operation (GlobalProtect Gateways,GlobalProtect Portals, or both gateways and portals).
- TheNumber of Nodesthat 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.
Service Connection, Remote Network, and Clean Pipe deployments only)
The name of the service connection, remote network connection, or clean pipe instance.
The location where the service connection, remote network connection, mobile user, or clean pipe node was onboarded.
The status of the deployment operation.
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 againor
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 IDfor job 42233 does not provide any additional details about the job.
Recommended For You
Recommended videos not found.