Configure and Integrate Prisma Access CloudBlade (Cloud Managed CloudBlade)

1. In Strata Cloud Manager, go to ConfigurationPrisma SD-WANCloudBlades.
2. In CloudBlades, locate the Prisma Access for Networks (Cloud Managed) CloudBlade and click Configure. If this CloudBlade does not appear in the list, contact Palo Alto Networks Support.

3. Enter the following information in the fields shown below. Change where appropriate:

   1. VERSION: Select the version of the CloudBlade to use.
   2. ADMIN STATE: For the admin state, select or retain Enabled.
   3. ION PEERING DEFAULT LOCAL AS NUMBER: The BGP Local AS number is defined to quickly onboard ECMP sites. This can be any 16-bit AS number, but private BGP AS numbers are recommended.
   4. TUNNEL IDENTIFIER, PRISMA ACCESS FOR NETWORKS SIDE: Enter an FQDN IKE identifier in name@domain.com format. This identifier will be used by Prisma Access to identify remote tunnel connections.
   5. TUNNEL IDENTIFIER TEMPLATE, PRISMA SD-WAN SIDE: Enter an FQDN IKE identifier in name@domain.com format. This identifier should be different from the Prisma Access identifier. This identifier will serve as a template for generating a unique ID for each tunnel.
   6. TUNNEL INNER IP POOL: Specify an IP pool, using IP address or Mask notation. This IP Pool should be unused or unique across the entire network and should not be used by the Palo Alto Service Infrastructure subnet.
      If you want to change the IP Prefix specified here, start by disabling the CloudBlade and ensuring all service links are updated. Now, change the IP CIDR to the required value and enable the CloudBlade to allocate Tunnels based on the new IP CIDR.
      The number of tunnels created in the Prisma SD-WAN Fabric to Prisma Access are directly limited by this configuration. Each tunnel will use a /31 subnet from this pool.
   7. TUNNEL PSK SEED: Specify a string of text, which will be used to derive the unique pre-shared keys (PSKs) used per tunnel.
   8. ENFORCE DEFAULT PRISMA SD-WAN LIVELINESS PROBES: For Prisma Access, the default is to leverage an ICMP probe to the last Prisma Access Infrastructure IP address. You can reconfigure this to probe non-default tunnel monitor IP addresses that were configured during Prisma Access integration.
   9. ENABLE DRY RUN EXECUTIONS: When enabled, the CloudBlade logs the changes made on Prisma SD-WAN and the CloudBlade in the Logs and Status Monitor. You can use this option to check the changes required by the CloudBlade.
4. Click Install after configuring the settings.