Integrate Prisma Access with Aruba SD-WAN (Strata Cloud Manager)

1. Connect a remote network to Prisma Access.

   When configuring the remote network, use the validated settings.

   Choose a Prisma Access Location that is close to the remote network location that you want to onboard.

2. Select IPSec Advanced Options and Create New to create a new IPSec Crypto profile for the remote network tunnel using the recommended settings.
3. Select IKE Advanced Options and Create New to create a new IKE cryptographic profile for the remote network tunnel.

   Be sure to use the crypto values that are supported with Aruba and make a note of the values you use.

4. Set up routing for the remote network.

   Set Up Routing and Add the IP subnets for Static Routing.

5. Push your configuration changes.

   1. Return to ConfigurationNGFW and Prisma AccessConfiguration ScopePrisma AccessRemote Networks and select Push ConfigPush.

   2. Select Remote Networks.

   3. Push your changes.
6. Make a note of the Service IP of the Prisma Access side of the tunnel. To find this address in Prisma Access (Managed by Strata Cloud Manager), select ConfigurationNGFW and Prisma AccessConfiguration ScopePrisma AccessRemote Networks, click the Remote Networks. Look for the Service IP field corresponding to the remote network configuration you created.
7. In the Aruba Branch Gateway, set up the tunnel to Prisma Access.

   1. Select VPNCloud SecurityPalo Alto Networks - GPCS.
   2. Enter values in the fields.

      • Name—Enter an administrative name for the tunnel. The system will append _gpcs at the end.
      • Priority—Enter a numeric identifier for the tunnel.
      • Transform—Select default-aes, which uses AES256 encryption with SHA1 Hash.
      • Source FQDN—Enter the user ID created in Prisma Access (santaclara.branch in the following screenshot).
      • Tunnel destination IP—Enter the Service IP Address from the remote network connection that you got when you configured the remote network connection in Prisma Access
      • Uplink VLAN—Select the Uplink VLAN to be used to bring up tunnels to Prisma Access (in the case of BGWs) or the source VLAN in the case of VPNCs.
      • IKE Shared Secret—Set the same value created in the Prisma Access configuration.

      The solution can set up multiple tunnels and determine which traffic is sent through each one using PBR policy rules; therefore, you can configure active-active and active-backup redundancy.

      Even though the source FQDN has to be unique on a per-branch basis, you should configure the remaining parts of the tunnel configuration at the group level whenever possible. This hierarchical configuration model greatly streamlines configuration efforts. The following screenshot shows a specific Source FQDN configured for the local configuration and a generic Source FQDN specified for the group-level configuration.

8. Create one or more next-hop lists with the tunnels.

   After you create the tunnels, next-hop lists group them together to be used inside PBR policy rules.

   1. Select NextHop ConfigurationRouting.
   2. Create a NextHop.
   3. Add Site-to-Site IPSec maps.
   4. Enter different priorities for the different tunnels.

      Prisma Access does not support load-balancing.
   5. Select Preemptive-failover.

9. Add the next hop to a routing policy by selecting RoutingPolicy-Based Routing.

   In the following example, the policy is sending all the traffic to private subnets (an alias representing 10.0.0.0/8 and 172.16.0.0/12) through the regular path, and it’s sending the rest of the traffic through the Prisma Access nodes.

10. Apply policy rules to the roles or VLANs.

    After you create the routing policy, the last step you perform is to apply it to the role or VLAN that you want to send through Prisma Access.

    If there is a conflict between PBR policy rules applied to a role and VLAN, policy rules applied to the role take precedence.

    The following screen shows a PBR policy being applied to a VLAN.

    The following screen shows a PBR policy being applied to a role.

11. (Optional) Verify the status of the remote network tunnel and troubleshoot when needed.