Configure Custom Liveliness Probe
Table of Contents
Expand all | Collapse all
-
- QoS CIR Support For Aggregate Bandwidth
- Prisma Access for Networks Non-Aggregate Bandwidth Licensing
- IPSec Termination Nodes in Prisma
- IPSec Termination Node Logic (Panorama Managed)
- Determine Region Bandwidth Utilization
- Determine IPSec Termination Nodes Method #1 (Remote Networking On-Boarding)
- Determine IPSec Termination Nodes Method #2 (Panorama API Method)
- IPSec Termination Node Conventions and Tag Nomenclature
-
- Onboard a Non-ECMP Site
- Set Additional Information Tag
- Configure BGP
- Assign Interface-Level Tags for Non-ECMP Sites
- Customize Prisma Access Objects Names using CloudBlade Tag
- Prisma Access for Networks Region List
- Prisma Access CloudBlade Tag Information
- 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 the Prisma Access for Networks (Panorama Managed) CloudBlade
- Understand Prisma SD-WAN and Prisma Access for Networks Integration
- Correlate Objects between Prisma SD-WAN and Panorama
- View Standard VPNs at a Site Level
- View Alerts and Alarms
- View Activity Charts
- Use the Device Toolkit
- Check Tunnel Status on Panorama
- Change Existing Panorama Serial Number Post CloudBlade Integration
Configure Custom Liveliness Probe
316 PIC
Prisma Access
for Networks uses the concept
of an Infrastructure Subnet when creating the Service Setup under
the plugin. The Infrastructure Subnet is required for services within
a given Prisma Access
Tenant.When you create an Infrastructure
Subnet, the last usable IP address provided becomes the following
set of services within
Prisma Access
:- Captive Portal Redirect IP Address
- Remote Network DNS Proxy IP Address
- Tunnel Monitor IP Address
When the CloudBlade creates
a standard VPN to
Prisma Access
, the default is to use the Tunnel
Monitor IP Address within the Prisma Access
Infrastructure, using a
Liveliness probe. There may be times when a probe may need to be
changed from the default, to monitor additional services external
of Prisma Access
for a given business requirement.![](/content/dam/techdocs/en_US/dita/_graphics/uv/prisma/prisma-sd-wan/cloudblades/312-pa-cb-liveliness-probe-new.png)
- Within the CloudBlade, the default is to use the last usable Infrastructure IP address. To utilize a different Liveliness Probe, uncheck the box within the CloudBlade.
- To configure a custom Liveliness Probe, navigate towithin theManageResourcesService & DC GroupsPrisma SD-WANweb interface.
- Within theService & DC Groups, look for and clickEndpoints.The default view withinEndpointswill bePrisma SD-WAN.
- ClickStandard VPNfrom the drop-down.
- For a givenPrisma AccessRegion, find and clickLiveliness Probe.The default probe for Prisma Andorra which was chosen in this section is using the last usable IP address in the Infrastructure Subnet.
- To add another IP address or modify the probe, edit or add an ICMP ping as appropriate.In the following example, an additional ICMP probe is added.
- For this standard VPN toPrisma Access(Prisma Andorra), an additional ICMP probe to 8.8.8.8 is added to the Liveliness Probe.
- Repeat this step for each location that needs to be adjusted for a given business requirement.