Monitor CloudBlade Events
Table of Contents
3.1.6 Cloud Managed
Expand all | Collapse all
-
- Onboard a Non-ECMP Site
- Set Additional Information Tag
- Configure BGP
- Customize Prisma Access Objects Names using CloudBlade Tag
- Edit Application Policy Network Rules
- Understand Service and Data Center Groups
- Verify Standard VPN Endpoints
- Configure Standard Groups
- Assign Domains to Sites
- Use Groups in Network Policy Rules
- Enable, Pause, Disable, and Uninstall the Integration
Monitor CloudBlade Events
316 FIC
The following are the descriptions and
suggested solutions for events that may appear in the
CloudBlades
Events
tab in the Monitor
screen.
These could be helpful in identifying and troubleshooting various
scenarios. Event | Description | Suggested Solution |
|---|---|---|
internal error occurred | Token generated is not available in the cache.
This may occur while installing a new version of the CloudBlade. | Save the CloudBlade configuration again, or
wait awhile for the error to time out. |
internal error occurred | App is uninstalled or not found. This may occur
while installing a new version of the CloudBlade. | Save the CloudBlade configuration again, or
wait awhile for the error to time out. |
internal error occurred | App version is incorrect. This may occur while
installing a new version of the CloudBlade. | Save the CloudBlade configuration again, or
wait awhile for the error to time out |
internal error occurred | Prisma Access (Cloud managed) API sent missing
infra-asn. | This may occur when the Prisma Access APIs
are down. Try again. |
internal error occurred | Prisma Access (Cloud managed) API sent missing
infra-ip. | This may occur when the Prisma Access APIs
are down. Try again. |
Associated Prisma Access tenant not found | Cannot find the corresponding Prisma Access
Account. | Verify the App association in the Hub portal. |
Incorrect HA configuration | HA configuration for the site is incorrect. | Rectify the HA configuration and tags to onboard
the site successfully. |
ECMP bundle skipped due to multiple SPNs | ECMP tag could not be processed due to incorrect tagging. | Ensure all ports are tagged with one SPN name
or index. |
Status data corrupt | Mongo DB data is corrupted. | Contact the Palo Alto Support Team. |
Insufficient tunnel IP pool | IP pool is insufficient. | Increase the IP range configuration or free
up sites. |
Local authentication failure | Authentication failure | Check if Prisma Access has deployed all resources. |
Authentication failure | Token expired/Controller issue when logging
in. | If the issue persists, contact Contact the
Palo Alto Support Team. |
Site is configured incorrectly | Prisma Access tag applied/configured is incorrect. | Verify all Prisma Access tags. |
Site onboarding failure | API error occurs when saving the SDWAN site. | If the issue persists, contact Contact the
Palo Alto Support Team. |
Configuration of more than two elements is
not supported | More than two Elements are attached to the
site. | Ensure any unused elements are detached from
the site. |
Bandwidth migration is in progress | Bandwidth migration is in progress. | Ensure Bandwidth migration is complete before
execution. |
IP allocation conflict | IP allocation is throwing a conflict. | Contact the Palo Alto Support Team. |
Prisma name xxxx is used in multiple sites | Duplicate name tag used in multiple sites. | Ensure sites have unique name tag. |
Only one tag must be defined on a site | Multiple name tags are defined on a site. | Ensure only one name tag is defined on a site. |
Malformed prisma name tag xxxx | Invalid tag format or colon position. | Ensure tag is in the format: prisma_name:xxxxx |
Prisma name xxxx has disallowed chars on site xxxx | Prisma name does not match the allowed alpha
numeric characters. | Ensure site name contains only allowed alpha
numeric characters. |
Prisma name xxxx must be of length between
xx and xx | Prisma name length is either too short or too
long. | Ensure site name length is between 3 and 11
characters. |