Prisma Access Integrations
  • Prisma Access Integrations
  • Prisma Access Documentation
  • All Documentation
>
Integrate Prisma Access with Nuage SD-WAN (Strata Cloud Manager)
Focus
Download PDF
Focus
  1. Home
  2. Prisma Access
  3. Integrate Third-Party SD-WANs with Prisma Access
  4. Nuage Networks SD-WAN Solution Guide
  5. Integrate Prisma Access with Nuage SD-WAN
  6. Integrate Prisma Access with Nuage SD-WAN (Strata Cloud Manager)
Download PDF
Prisma Access

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

Table of Contents

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

Complete the following task to configure the remote network connection as a site-to-site IPSec tunnel.
  1. Follow the steps to Connect a remote network to Prisma Access.
    1. Enter a Site Name and select a Prisma Access Location that is close to the remote network location that you want to onboard.
    2. Select the IPSec Termination Node to use for the remote network.
  2. Configure the primary tunnel.
    1. Set Up the primary tunnel.
      When configuring the tunnel, use the validated settings.
    2. Specify a name for the IPSec Tunnel and click Create New.
    3. Enter a Tunnel Name.
    4. Set the Branch Device Type to Other Devices.
    5. Set the Authentication type to Pre-Shared Key and then enter Pre-Shared Key and Confirm Pre-Shared Key.
    6. Specify how the peers will identify each other.
      • Set the IKE Local Identification and IKE Peer Identification to User FQDN (email address).
        Make note of the value that you use for the Peer Identification and the Pre-Shared key you use; you must match these settings for the Nuage Networks side of the connection in step
        6
        when you
        Set Up the Remote Network Tunnel in Nuage Networks
        .
    7. Enable IKE Passive Mode.
  3. In the Proxy ID section and Add a default route for all local and remote prefixes.
    Creating this route ensures that all prefixes in the VPN use this IPSec tunnel.
  4. Select IPSec Advanced Options and Create New to create a new IPSec crypto profile for the remote network tunnel using the recommended settings.
    Make sure you use IPSec crypto settings that are supported with Prisma Access and Nuage Networks SD-WAN
  5. Select IKE Advanced Options and Create New to create a new IKE cryptographic profile for the remote network tunnel.
    Make sure you enable IKE NAT Traversal. The Nuage Network Services Gateway (NSG) initiates the IKE negotiation, and allows the negotiation to occur even if Nuage Networks side is behind NAT. Refer to the IKE crypto settings that are supported with Nuage for the rest of the settings and make a note of the values you use.
  6. Save the tunnel configuration.
  7. Push your configuration changes.
    1. Return to ManageService SetupRemote Networks and select Push ConfigPush.
    2. Select Remote Networks.
    3. Push your changes.
  8. Find the IP address used on the Prisma Access side of the IPSec tunnel.
    1. Go to ManageService SetupRemote Networks and make a note of the Service IP address.
      You use this IP address as the peer address when you set up the IPSec tunnel on the Meraki SD-WAN.

Set Up the Remote Network Tunnel in Nuage Networks

After you configure the remote network tunnel in Prisma Access, configure the tunnel in Nuage Networks by completing the following task.
Note that Dead Peer Detection (DPD) is only configured in Nuage Networks. No DPD configuration is required in Prisma Access because the NSG is the DPD initiator and Prisma Access can only reply to requests.
  1. In your organization, create the Gateway using the Nuage Networks IKE gateway object.
    In the IP Address field, enter the Service IP address that you retrieved after you completed the setup of the remote network tunnel in Prisma Access.
  2. Define the remote subnet for which traffic will be sent to the gateway.
    The IKE gateway connection uses the underlay breakout mechanism as shown in the following diagram:
    All traffic to Prisma Access is through the underlay. If you enable underlay, and if the remote subnet associated with Prisma Access matches the destination IP in the customer packet, then the Nuage Networks SD-WAN sends the packet to Prisma Access. If the destination IP does not match, the SD-WAN sends the packet to internet breakout using underlay breakout and port address translation (PAT) rules.
  3. Specify a default route to the gateway so that the network sends all internet traffic to Prisma Access.
  4. Create an IKE encryption profile.
    This profile must match the values that you specified in the Prisma Access IPSec configuration.
  5. Create an IKE gateway profile.
    1. Enter a Name for the gateway profile.
    2. Select Check anti-replay.
    3. Select the Service class.
    4. Select the Gateway and Encryption Profile, using the settings you created for Prisma Access.
    The example in the following screenshot uses one pre-shared key per connection, which means that the IKE Gateway profile won't use a pre-shared key object, and the Authentication Method field is empty.
  6. Associate the remote network connection with the NSG uplink port.
    You associate the remote network connection with the Nuage Networks NSG at the uplink VLAN level. This association contains an NSG identifier in RFC 822 format and includes the pre-shared key that is used for the connection.
  7. Check the status of the tunnel connection by entering the following command.
    A status of UP indicates that the connection is successful. 
    A:vsc1# tools vswitch 86.229.176.112 command "nuage-nsg-ike-cli show tunnel-status-summary"
-------------------------------------------------------------------------------
Gateway Name       Local IP          Remote IP       Phase1  Phase2
-------------------------------------------------------------------------------
paloalto           192.168.0.103     3.121.193.101   up      up
-------------------------------------------------------------------------------
  8. Next steps: Learn how Nuage Networks monitors the remote network, and troubleshoot the Nuage Networks remote network connection to Prisma Access, if required.

Nuage Networks Dead Peer Detection and Internet Probing

To detect issues with an IKE gateway for the remote network connection, Nuage Networks VNS uses the Dead Peer Detection (DPD) mechanism, in addition to using a probing mechanism to probe internet services.
The probes are divided into two hierarchical levels: Tier1 and Tier2. Nuage Networks initiates the probe. The Tier 1 probe tests the connectivity of the remote network connection to Prisma Access and the Tier 2 probe tests the connectivity to the internet.
Each connection is composed of an Active IPSec tunnel (priority 100) and a backup IPSec tunnel (priority 200). The HTTP probes run on both connections.
  • Tier 1 Probe—Each Tier1 probe is associated to a weight (between 1 and 100%). For Tier1 to fail, the sum of the Tier1 probes that fail must be equal to or greater than 100%. If the Tier1 probe goes down, Tier 2 probe monitoring also goes down.
  • Tier 2 Probe—The Tier 2 probe uses round-robin monitoring across a set of internet FQDNs. Consecutive probe tests must fail for the Tier2 probe to fail.

Create an HTTP Probe Object

To create an HTTP probe object, complete the following task.
  1. In the Nuage Networks UI, select Performance Monitors.
  2. Create a performance monitor with the following values:
    • Specify a Hold Down Timer value that defines how long the VSD waits for a response before it determines that the performance monitor is unsuccessful and switches to the backup tunnel. The default is 1000 ms.
    • Specify a Probe Type of HTTP.
    After you click Create, the Nuage VNS creates two tiers: Tier 1 and Tier 2. There is no option to add or Remove tiers.
  3. Create Tier 1 URLs, specifying the following values:
    • Down Threshold Count—Defines the number of consecutive failed probes before the VSD declares a state change and raises an alarm.
    • HTTP Request Type—Specifies the HTTP request method used for the HTTP ping.
    • URL Weight—Defines the percent weight for the URL within Tier 1. The sum of the URL weights in Tier 1 cannot exceed 100.
    • URL—Defines the HTTP or HTTPS target. Specify one URL up to 2000 characters long.
    • Rate—Defines the rate at which the probe sends probe packets to the destination target.
    • Timeout (ms)—Defines how long the VSD waits for a response before considering a probe unsuccessful.
  4. Edit Tier 2 options to change the interval and timeout values of the Tier 2 probe by specifying the following values:
    • Interval (s)—Defines the rate at which the probe sends packets to the destination target.
    • Probe Timeout (ms)—This parameter defines how long the VSD waits for a response before it determines a probe to be unsuccessful.
    • Down Threshold Count—This parameter defines the number of consecutive failed probes before the VSD declares a state change and raises an alarm.
  5. Create Tier 2 URLs with the following values:
    • HTTP Request Type—Specifies the HTTP request method that is used for the HTTP ping.
    • URL—Defines the HTTP or HTTPS target. Specify one URL up to 2000 characters long.
  6. After you create the HTTP probe object with Tier 1 and Tier 2 information, associate the probe to the active and backup IPSec tunnel.
    The following condition must apply to associate a probe with an IKE gateway connection:
    • The remote subnet associated with IKE gateway must be 0.0.0.0/0.
    • You must associate all local subnets with the uplink IPSec connection.
    If you do not meet the preceding conditions, tunnel association fails.

Troubleshoot the Remote Network

Prisma Access provides logs and widgets that provide you with the status of remote tunnels and the status of each tunnel.
  • Go to ManageService SetupRemote Networks and check the Status of the tunnel.
  • Go to ActivityLog Viewer and check the Common/System logs for IPSec- and IKE-related messages.
    To view VPN-relates messages, set the filter to sub_type.value = vpn.
    The message ignoring unauthenticated notify payload indicates that the route has not been added in the crypto map on the other side of the IPSec tunnel after the IPSec negotiation has already occurred.
  • Check the Firewall/Traffic logs and view the messages that are coming from the zone that has the same name as the remote network.
    In the logs, the remote network name is used as the source zone.

Technical Documentation

Company

Legal Notices

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