>
    Integrate Prisma Access with Riverbed SteelConnect SD-WAN
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma Access
    3. Integrate Third-Party SD-WANs with Prisma Access
    4. Riverbed SteelConnect SD-WAN Solution Guide
    5. Integrate Prisma Access with Riverbed SteelConnect SD-WAN
    Download PDF
    Prisma Access

    Integrate Prisma Access with Riverbed SteelConnect SD-WAN

    Table of Contents

    Integrate Prisma Access with Riverbed SteelConnect SD-WAN

    Where Can I Use This?What Do I Need?
    • Prisma Access (Managed by Panorama)
    Use this workflow to configure three sites to use a ClassicVPN tunnel to establish VPN connectivity with Prisma Access. Match the configuration in SCM with the configuration in Prisma Access. Each management interface has its own default settings, so we recommend that you confirm each setting between SCM and Panorama.
    This workflow assumes that you have already configured the remote network tunnel for the tunnels you want to create. You need the IP address of the Prisma Access side of the tunnel to complete this configuration. To find this address in Panorama, select PanoramaCloud ServicesStatusNetwork Details and find the Service IP Address in the Remote Networks area.
    The following figure shows a total of six RouteVPN tunnels. They are identified by solid orange lines. SteelConnect automatically forms these tunnels over the internet WAN between SteelConnect appliances. Three of these tunnels use the internet between sites, and the other three use the MPLS cloud between sites. These tunnels form the overlay network. This term is an abstraction of the internet and WAN in which the gateways communicate with each other. The communication for the overlay network takes place on an underlay network. The underlay network is the series of network devices owned by a provider or customer making up a network infrastructure.
    The organizational networking defaults you set in SCM determine how the SD-WAN processes traffic. For traffic going to the internet breakout, the traffic uses the internet uplink. For traffic between sites, the SD-WAN prefers the RouteVPN over the internet uplink over the RouteVPN over the MPLS WAN. Based on organizational defaults, SCM automates the creation of a full-mesh RouteVPN over the internet uplink and establishes encrypted tunnels over the MPLS network.
    The following figure shows the internet breakout preferences as defined in SCM.
    The following diagram illustrates the logical traffic flow. The traffic between ThousandOaks and New York, HQ and New York, and HQ and ThousandOaks takes the RouteVPN over the MPLS overlay by default, while traffic from each branch to the internet takes the internet uplink by default. The workflow in this section configures ClassicVPN tunnels and defines traffic rules in SCM so that traffic from the SD-WAN to the internet takes the ClassicVPN tunnels to Prisma Access.
    You can override organizational defaults by Traffic Path rules. The following figure shows an SCM configuration that directs traffic between the New York site 172.16.3.0/24 subnet to the HQ 172.16.1.0/24 subnet or the ThousandOaks 172.16.2.0/24 subnet to use the RouteVPN tunnel instead of the ClassicVPN tunnels used for internet traffic. The settings in SCM specify these tunnels to use the MPLS WAN.
    Internet traffic uses the ClassicVPN tunnel at each site. Traffic from the New York LAN to the internet uses the ClassicVPN tunnel in New York. Traffic from ThousandOaks to the internet uses the ClassicVPN tunnel in ThousandOaks, and traffic from HQ to the internet uses the ClassicVPN tunnel in HQ.
    This workflow creates and configures ClassicVPN tunnels between the SteelConnect SD-WAN and Prisma Access.
    1. In SCM, select Network DesignClassicVPN.
    2. Create the ClassicVPN connection by completing the following steps:
      1. Click New ClassicVPN connection.
      2. Enter a Name for the connection.
      3. Enter the Remote Gateway address.
        The remote gateway address is the Service IP Address for the remote network in Prisma Access. To find this IP address in Panorama, select PanoramaCloud ServicesStatusNetwork Details and note the Service IP Address for the remote network. You must create a remote network tunnel in Prisma Access before you complete this workflow.
      4. Enter the Remote IPv4 network.
        In this case, the remote network is 0.0.0.0/0, because SCM should route all traffic that does not have a more specific route (that is, internet-bound traffic) over the ClassicVPN.
      5. Select the source Site.
      6. Select the source Zones.
        In this example, traffic from LAN1 at HQ is sent over the ClassicVPN connection if a more specific route does not exist in the routing table of the gateway. For additional details on how packets are processed by the SteelConnect network, see How a Packet Traverses a SteelConnect Network in the SteelConnect SD-WAN Deployment Guide.
        There is an additional zone listed in the following figure: NY-LAN2. In the workflow in Configure Internet Breakout from a Single Site to Prisma Access, internet traffic from the New York office is backhauled through the HQ site. Create this zone to establish the VPN tunnel. If you remove the NY-LAN2 zone from the configuration, the tunnel will go down.
        In addition, you must match any zones you create here, including any subnets, on the Prisma Access side. For example, this tunnel includes the 172.16.1.0/24 subnet (for the HQ site) and the 172.16.4.0/24 subnet (for the NY-LAN2 site). You also specified these subnets in Prisma Access for each remote network you created. To view these subnets in Panorama, select PanoramaCloud ServicesConfigurationRemote Networks and view the information in the Branch IP Subnets field.
        There are default values that SCM creates for you when you deploy a ClassicVPN. If you use the default values in SCM, you will need to edit the configuration in Panorama. If you use the defaults in Panorama, you will need to edit the configuration in SCM. Both sides must match. Our HQ configuration will match the Panorama configuration.
    3. Adjust the configuration in SCM by completing the following steps:
      1. Select the Authentication tab.
      2. Enter the Pre-shared Key to match what is configured in Panorama.
      3. Click Submit.
    4. Configure advanced tunnel settings by completing the following steps:
      1. Click the Advanced tab.
      2. Enter the Local ID.
        The Local-ID is the proxy-ID seen in the IPSec tunnel negotiation. If the Proxy-ID isn't known on both ends, the tunnel will fail. This configuration was tested using the IP address as the endpoint ID instead of FQDN.
      3. Enter the Remote ID.
        The remote ID is the tunnel endpoint IP address in Prisma Access.
      4. Click Submit.
    5. Configure IKE settings (Phase 1) and IPSec (Phase 2) encryption settings by completing the following steps.
      IPSec VPNs establish in two phases, IKE phase 1 and IPSec phase 2. Phase 1 is used to create a secure channel in which parameters that apply to the data being encrypted are negotiated. In SCM, the IKE settings are for the phase 1 tunnel. The phase 2 tunnel negotiation defines how the user traffic is encrypted from the SteelConnect gateway to Prisma Access.
      The example used in this workflow creates an IKE tunnel with AES128 encryption, SHA1 hashing, and a lifetime of 28,800 seconds (8 hours).
      1. Scroll down in the Advanced tab and select IKEv1.
        IKEv1 uses the phase 1 and phase 2 method of negotiation, while IKEv2 creates parent and child security associations.
      2. Select AES128.
      3. Select SHA1.
      4. Enter 28800 in the IKE lifetime field.
        This setting specifies the length of time that the IKE phase 1 tunnel remains up before it renegotiates.
      5. Select AES256 as the IPSec encryption cipher
      6. . Select SHA1 in the IPSec has algorithm field.
      7. Select DH Group 2 (1024 bit) in the IPSec DH Group field.
      8. Enter an IPSec lifetime of 2600 seconds.
      9. Click Submit.
      After submitting this configuration, the tunnel begins to establish. Once the tunnel establishes, you receive an event notification in SCM and the tunnel status displays as Online, as seen in the following figure.
    6. Repeat the steps in this workflow to add additional sites.

    Configure the SteelConnect Tunnels

    Since the configuration steps are the same for additional branches, this workflow does not document the workflow for all tunnels. However, you must complete the following tasks after you add the two branch sites:
    • If you use the SCM default values to create the tunnel in SCM, the Local ID is set as the FQDN. If the remote end supports FQDN (as Prisma Access does), you don't need to change this setting. If the remote end does not support FQDN, you must change this setting.
    • SteelConnect creates a randomly generated pre-shared key. If you choose to use this key, you need to copy it and enter it in Prisma Access.
    1. Copy the autogenerated pre-shared key by completing the following steps:
      1. In SCM, click Authentication.
      2. Click Reveal to the right of the Preshared Key field.
      3. Copy the pre-shared key.
    2. (Optional) Modify the Local ID, if required, by completing the following steps:
      1. Click Advanced.
      2. Enter the Local ID.
      3. Enter the Remote ID.
      4. Click Submit.
        There are now three established ClassicVPN sessions from each site to Prisma Access.
    3. Either modify the default rule, or disable it and add a new rule.
      The default outbound rule allows user traffic on the ClassicVPN. Since a 0.0.0.0/0 remote network is defined in the ClassicVPN configuration, the SD-WAN sends all traffic that does not have a more specific route in the routing table over the ClassicVPN to Prisma Access.
      The following SCM output shows the default outbound rules using internet Access as the target.
    4. Modify the default outbound rule, or add a new one as shown in the following figure, to allow sites to communicate over the RouteVPN.
    5. (Optional) Add traffic rules to direct specific traffic over selected links.

    Configure the Tunnel in Prisma Access

    After you configure the tunnel in SCM, configure the tunnel settings in Prisma Access to match the SCM settings.
    1. Select NetworkRemote_Network_TemplateNetwork ProfilesIPSec Crypto.
    2. Click Add and create an IPSec cryptographic profile with settings that match the settings you made for the ClassicVPN tunnel in SCM.
      These settings are for the Phase 2 tunnel establishment.
    3. Select NetworkRemote_Network_TemplateNetwork ProfilesIKE Crypto.
    4. Click Add and create an IKE cryptographic profile with settings that match the settings you made for the ClassicVPN tunnel in SCM.
      These settings are for the Phase 1 tunnel establishment.
      The encryption, authentication, and timer policy rules don't need to be identical between the IPSec and IKE crypto policy rules; however, whatever policy rules you configure must be identical on the SteelConnect gateways and Prisma Access. If the IKE Profile uses AES-128-CBC on the gateway, then you must configure the IKE Crypto profile in Prisma Access to match. If the IPSec settings on the gateway are set to use AES-256, then you must configure the IPSec Crypto Profile in Prisma Access to match.

    Configure Internet Breakout from a Single Site to Prisma Access

    This workflow configures SCM to backhaul internet traffic from the NY office over the RouteVPN and then send it to the internet over the ClassicVPN by way of Prisma Access, as shown in the following figure.
    Complete the following to set up a backhauled internet configuration.
    1. Create a traffic rule that forces traffic between sites to use RouteVPN tunnels.
    2. Edit the traffic rule so that the tunnel the NY-LAN2 and HQ-LAN1 uses the MPLS tunnel by default.
      This configuration ensures that traffic from the NY site to the internet is first backhauled to HQ using the MPLS connection.

    Troubleshoot the Riverbed SteelConnect Remote Network

    Prisma Access provides logs that provide you with the status of remote tunnels and the status of each tunnel. To view these logs in Panorama, select MonitorLogsSystem.
    To debug tunnel issues, you can filter for tunnel-specific logs by using the object identifier corresponding to that tunnel. The following figures show errors related to tunnel misconfiguration and negotiation issues.

    © 2024 Palo Alto Networks, Inc. All rights reserved.