Focus

Prisma Access

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration)

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Release Notes
Select a Document
- 6.1 Preferred and Innovation
- 6.0 Preferred and Innovation
- 5.2 Preferred and Innovation
- 5.1 Preferred and Innovation
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
Activation & Onboarding
Administration
Select a Document
- 4.0 & Later
- Prisma Access China
Integrations
Incidents & Alerts

Integrate Prisma Access with Cisco Catalyst SD-WAN

Integrate ServiceNow with Prisma Access

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration)

Configure the remote network between the Cisco Catalyst SD-WAN and Prisma Access by completing the steps in the following workflows.

Where Can I Use This?	What Do I Need?
Prisma Access (Managed by Strata Cloud Manager) Prisma Access (Managed by Panorama)	Prisma Access license IP address of the Cisco Catalyst SD-WAN device that you will be using as the other side of the remote network connection

You can configure the IPSec tunnel in Prisma Access before you perform the IPSec tunnel configuration in Cisco Catalyst SD-WAN, formerly known as Viptela SD-WAN.

Cisco Catalyst SD-WAN supports the following deployment architectures for use with Prisma Access. a dash (—) indicates that the deployment is not supported.

Use Case	Architecture	Supported?
Securing traffic from each branch site with 1 WAN link (Type 1)		Yes
Securing branch and HQ sites with active/backup SD-WAN connections		Yes
Securing branch and HQ sites with active/active SD-WAN connections		Yes
Securing branch and HQ sites with SD-WAN edge devices in HA mode		Yes
Securing SD-WAN deployments with Regional Hub/POP architecture (Type 2)		Yes

Before you start, get the IP address of the Cisco Catalyst SD-WAN device that you will be using as the other side of the remote network connection; you enter this information in your IKE Gateway profile.

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration) (Strata Cloud Manager)

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration).

Connect a remote network site to Prisma Access.
- Choose a Prisma Access Location that is close to the remote network location that you want to onboard.
- When creating the IPSec tunnel, use a Branch Device Type of Other Devices.
Select IPSec Advanced Options and Create New to create a new IPSec crypto profile for the remote network tunnel using the recommended settings.
Select IKE Advanced Options and Create New to create a new IKE cryptographic profile for the remote network tunnel.

Be sure to use crypto values that are supported with Viptela and make a note of the values you use.
Set up routing for the remote network.
Set Up Routing and Add the IP subnets for Static Routing.

Choose Static Routing and Add a subnet. A /30 subnet is sufficient for a Viptela-Prisma Access SD-WAN integration, because you need only two IP addresses for this configuration:
- 10.10.10.1, which you specified as the IP address for the ge0/4 interface.
- 10.10.10.2, for which you specify a default route when you configure the remote network connection in Viptela.
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.
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.
Complete configuration of the IPSec tunnel.
1. Return to the IPSec tunnel configuration.
2. Change Local Identification to IP address and add the Service IP you just retrieved (13.1.1.1 in this example).
  
  Be sure to make a note of the Service IP; you configure this as the peer IP address for the IPSec tunnel between the Viptela SD-WAN device and Prisma Access.

Create a Remote Network Connection in Viptela

Use the following steps to configure the IPSec tunnel in Viptela. The examples in this section use command-line interface (CLI) commands.

This configuration completes the remote network connection between Prisma Access and the Viptela SD-WAN. The following figure shows what you define in the Viptela side:

On the LAN side of the Viptela SD-WAN device, create a ge0/0 interface with an IP address of 10.50.50.1. This matches the IP address you specified when you configured the IKE Gateway in Prisma Access.
The Viptela SD-WAN performs NAT on the source IP address for the LAN (73.146.228.139).
On the remote network tunnel (WAN) side, create an interface named ipsec2 with a type, slot, and port of ge0/4 whose IP address is 10.10.10.1/30.
This address must be within the subnet range you specified for the Branch IP Subnet when you onboarded your remote network in Prisma Access. In this example, the administrator specified a Branch IP Subnet of 10.10.10.0/30 in Prisma Access, and you use the other available IP address (10.10.10.1/30) on the Viptela side of the remote network connection.
Specify a tunnel-destination IP address that matches the Prisma Access Service IP. This example uses 13.1.1.1.
Specify a loopback IP address that Prisma Access can use for tunnel monitoring.
In this example, the administrator configured a loopback100 interface with an IP address of 10.1.50.1/32. This value matches the Tunnel Monitor Destination IP address you specified in the IPSec Tunnel configuration that you configured in Prisma Access.

Open a CLI session with the Viptela SD-WAN device and enter the following commands to define the control plane for the Viptela Overlay Management Protocol (OMP).
The following commands enable a graceful restart for the OMP and advertise static and connected routes.
```
omp
 no shutdown
 graceful-restart
 advertise connected
 advertise static
```
Define the security types for the IPSec tunnel.
The following commands enable the AH-SHA1 HMAC and ESP HMAC-SHA1 authentication types.
```
security
 ipsec
  authentication-type sha1-hmac ah-sha1-hmac
```

Configure VPNs to segment the Viptela overlay network.

The following commands create a VPN VPN 0 named Transport VPN and associates the ge0/4 interface with this VPN. You use this interface and VPN for the Viptela SD-WAN side of the remote network tunnel (IPSec tunnel) between Viptela and Prisma Access.

vpn 0
 name "Transport VPN"
 interface ge0/4
  ip dhcp-client
  tunnel-interface
   encapsulation ipsec
   color biz-internet
   allow-service all
   no allow-service bgp
   allow-service dhcp
   allow-service dns
   allow-service icmp
   no allow-service sshd
   no allow-service netconf
   no allow-service ntp
   no allow-service ospf
   no allow-service stun

Enter the no shutdown command to enable the ge0/4 interface.
Create another VPN named VPN 1, associate the ge0/0 interface with this VPN, then define parameters for it.
The following example defines the parameters to allow the Viptela SD-WAN to route traffic from the LAN to its ge0/0 interface.
```
vpn 1
 interface ge0/0
  ip address 10.50.50.1/24
  no shutdown
  dhcp-server
   address-pool 10.50.50.0/24
   exclude      10.50.50.1
   offer-time   600
   lease-time   86400
   admin-state  up
   options
    default-gateway 10.50.50.1
    dns-servers     8.8.8.8 8.8.4.4
```
Create an interface named ipsec2 and apply it to the ge0/4 interface. These commands define the parameters for the remote network tunnel between the Viptela SD-WAN and Prisma Access.
Enter the following values:
- Enter an ip address to allow the Viptela SD-WAN to route traffic to Prisma Access.
  This address must be within the subnet range you specified for the Branch Subnet when you onboarded your remote network in Prisma Access. A /30 address is sufficient to allow routing to Prisma Access.
- Specify the same tunnel-source-interface that you used for VPN 0 (ge0/4 in this example).
- Specify a tunnel-destination using the Service IP from Prisma Access. This example uses 13.1.1.1 as the Service IP.
- Make sure that the ike and ipsec parameters that you specify match the parameters you specified in Prisma Access.
- Enter a pre-shared-secret that matches the Pre-shared key (PSK) that you entered in Prisma Access. This example uses a PSK of secretkey.
```
 interface ipsec2
  ip address 10.10.10.1/30
  tunnel-source-interface ge0/4
  tunnel-destination      13.1.1.1   
  ike
   version      1
   mode         main
   rekey        14400
   cipher-suite aes128-cbc-sha1
   group        2
   authentication-type
    pre-shared-key
     pre-shared-secret secretkey
    !
   !
  !
  ipsec
   rekey         3600
   replay-window 512
   cipher-suite  aes256-cbc-sha1
```
Enter the no shutdown command on the ipsec2 interface to enable it.

Create a loopback interface to be used for tunnel monitoring.

interface loopback100
  ip address 10.1.50.1/32
  no shutdown

Create a default route for the network.
This route uses the second IP address (10.10.10.2 in this example) of the /30 subnet you used when you onboarded your remote network in Prisma Access. The Viptela side of the network can route to this IP address and uses it as a next hop for routing.
```
ip route 0.0.0.0/0 10.10.10.2
```
Enter a VPN and give it a name.
```
vpn 512 name "Transport VPN"
```
Apply policies for the network.
```
policy
 app-visibility
 flow-visibility
```

Troubleshoot the Viptela Remote Network

To troubleshoot problems related to SD-WAN tunnels in Viptela, refer to the Viptela documentation for configuring IPSec tunnels at the following URL: https://www.cisco.com/c/en/us/support/routers/sd-wan/tsd-products-support-series-home.html.

Prisma Access provides logs and widgets that provide you with the status of remote tunnels and the status of each tunnel.

Go to ConfigurationNGFW and Prisma AccessConfiguration ScopePrisma AccessRemote 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.

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration) (Panorama)

You can configure the IPSec tunnel in Prisma Access before you perform the IPSec tunnel configuration in Cisco Catalyst.

In Panorama, add an IPSec crypto profile, IKE crypto profile, IKE gateway, and IPSec tunnel in the Remote_Network_Template template.
1. Select NetworkNetwork ProfilesIPSec Crypto and Add an IPSec Crypto Profile, specifying supported Encryption and Authentication settings; then click OK.
  
  Be sure that you have selected the Remote_Network_Template in the Templates drop-down at the top of the page.
2. Select Network ProfilesIKE Crypto and Add an IKE Crypto Profile specifying supported DH Group, Encryption, and Authentication settings; then click OK.
3. Select Network ProfilesIKE Gateways and Add an IKE Gateway.
  Specify the following values in the General tab:
  Select a Peer IP Address Type of IP and enter the IP address of the Cisco Catalyst SD-WAN device that you will be using as the other side of the remote network connection as the Peer Address.
  If using a pre-shared key for the IPSec tunnel, specify a Pre-shared Key.
  Leave Local Identification blank, because you do not know what this address is at the time of configuration; you add this later at the end of the procedure in Step 5.
  Specify a Peer Identification of either IP Address or User FQDN.
  Be sure that you match the settings you specify here when you configure the device used to terminate the other side of the Cisco Catalyst IPSec tunnel.
  
  Select the following values in the Advanced Options tab:
  Select Enable NAT Traversal.
  NAT traversal is required because the Cisco Catalyst SD-WAN uses the IP address from the LAN side of the SD-WAN device as the source interface. As a result, all traffic undergoes NAT translation on the interface used for the remote network connection (that is, the WAN side of the Cisco Catalyst SD-WAN).
  With the NAT Traversal option enabled, Prisma Access performs UDP encapsulation on IKE and UDP protocols, enabling them to pass through intermediate NAT devices.
  Select the IKE Crypto Profile you created in Step 1.b.
  
  Click OK when complete.
4. Select IPSec Tunnels and Add an IPSec Tunnel, specifying the IKE Gateway and IPSec Crypto Profile you just created.
5. (Optional) Select Tunnel Monitor and specify a Destination IP address that can monitor reachability of the IPSec tunnel between Prisma Access and the Cisco Catalyst SD-WAN.
  
  Make a note of this address; you match this address with the loopback100 interface you assign to the Cisco Catalyst SD-WAN when you configure the remote network connection in Cisco Catalyst.
Make a note of all IKE and IPSec settings you used in the tunnel configuration.
Onboard your remote network connection and enter the following values:
- Specify a Name, Bandwidth, and Region.
- Select the IPSec Tunnel profile you created in Step 1.d.
- Specify a Branch IP Subnet that is significant to Cisco Catalyst.
  A /30 subnet is sufficient for a Cisco Catalyst-Prisma Access SD-WAN integration, because you need only two IP addresses for this configuration:
  - 10.10.10.1, which you specified as the IP address for the ge0/4 interface.
  - 10.10.10.2, for which you specify a default route when you configure the remote network connection in Cisco Catalyst.
Commit the configuration changes to Panorama and push the configuration out to Prisma Access for remote networks.
1. Click CommitCommit to Panorama.
2. Click CommitCommit and Push. Click Edit SelectionsPrisma Access, and select both Prisma Access for remote networks and Prisma Access for service setup to push the configuration out to the service.
3. Click OK and Push.
Complete configuration of the IKE Gateway.
1. Select PanoramaCloud ServicesStatusNetwork Details, click the Remote Networks tab, and make a note of the Service IP Address.
2. Select Network ProfilesIKE Gateways and select the IKE Gateway you specified in Step 1.c.
3. Change Local Identification to IP address and add the Service IP Address you just retrieved (13.1.1.1 in this example).
  
  Be sure to make a note of the Service IP Address; you must configure this as the peer IP address to set up the IPSec tunnel between the Cisco Catalyst SD-WAN device and Prisma Access.

Create a Remote Network Connection in Cisco Catalyst

Use the following steps to configure the IPSec tunnel in Cisco Catalyst. The examples in this section use command-line interface (CLI) commands.

This configuration completes the remote network connection between Prisma Access and the Cisco Catalyst SD-WAN. The following figure shows what you define in the Cisco Catalyst side:

On the LAN side of the Cisco Catalyst SD-WAN device, create a ge0/0 interface with an IP address of 10.50.50.1. This matches the IP address you specified when you configured the IKE Gateway in Prisma Access.
The Cisco Catalyst SD-WAN performs NAT on the source IP address for the LAN (73.146.228.139).
On the remote network tunnel (WAN) side, create an interface named ipsec2 with a type, slot, and port of ge0/4 whose IP address is 10.10.10.1/30.
This address must be within the subnet range you specified for the Branch IP Subnet when you onboarded your remote network in Prisma Access. In this example, the administrator specified a Branch IP Subnet of 10.10.10.0/30 in Prisma Access, and you use the other available IP address (10.10.10.1/30) on the Cisco Catalyst side of the remote network connection.
Specify a tunnel-destination IP address that matches the Prisma Access Service IP Address. This example uses 13.1.1.1.
Specify a loopback IP address that Prisma Access can use for tunnel monitoring.
In this example, the administrator configured a loopback100 interface with an IP address of 10.1.50.1/32. This value matches the Tunnel Monitor Destination IP address you specified in the IPSec Tunnel configuration that you configured in Prisma Access.

Open a CLI session with the Cisco Catalyst SD-WAN device and enter the following commands to define the control plane for the Cisco Catalyst Overlay Management Protocol (OMP).
The following commands enable a graceful restart for the OMP and advertise static and connected routes.
```
omp
 no shutdown
 graceful-restart
 advertise connected
 advertise static
```
Define the security types for the IPSec tunnel.
The following commands enable the AH-SHA1 HMAC and ESP HMAC-SHA1 authentication types.
```
security
 ipsec
  authentication-type sha1-hmac ah-sha1-hmac
```
Configure VPNs to segment the Cisco Catalyst overlay network.
The following commands create a VPN VPN 0 named Transport VPN and associates the ge0/4 interface with this VPN. You use this interface and VPN for the Cisco Catalyst SD-WAN side of the remote network tunnel (IPSec tunnel) between Cisco Catalyst and Prisma Access.
```
vpn 0
 name "Transport VPN"
 interface ge0/4
  ip dhcp-client
  tunnel-interface
   encapsulation ipsec
   color biz-internet
   allow-service all
   no allow-service bgp
   allow-service dhcp
   allow-service dns
   allow-service icmp
   no allow-service sshd
   no allow-service netconf
   no allow-service ntp
   no allow-service ospf
   no allow-service stun
```
Enter the no shutdown command to enable the ge0/4 interface.
Create another VPN named VPN 1, associate the ge0/0 interface with this VPN, then define parameters for it.
The following example defines the parameters to allow the Cisco Catalyst SD-WAN to route traffic from the LAN to its ge0/0 interface.
```
vpn 1
 interface ge0/0
  ip address 10.50.50.1/24
  no shutdown
  dhcp-server
   address-pool 10.50.50.0/24
   exclude      10.50.50.1
   offer-time   600
   lease-time   86400
   admin-state  up
   options
    default-gateway 10.50.50.1
    dns-servers     8.8.8.8 8.8.4.4
```
Create an interface named ipsec2 and apply it to the ge0/4 interface. These commands define the parameters for the remote network tunnel between the Cisco Catalyst SD-WAN and Prisma Access.
Enter the following values:
- Enter an ip address to allow the Cisco Catalyst SD-WAN to route traffic to Prisma Access.
  This address must be within the subnet range you specified for the Branch Subnet when you onboarded your remote network in Prisma Access. A /30 address is sufficient to allow routing to Prisma Access.
- Specify the same tunnel-source-interface that you used for VPN 0 (ge0/4 in this example).
- Specify a tunnel-destination using the Service IP Address from Prisma Access. This example uses 13.1.1.1 as the Service IP Address.
- Make sure that the ike and ipsec parameters that you specify match the parameters you specified in Prisma Access.
- Enter a pre-shared-secret that matches the Pre-shared key (PSK) that you entered in Prisma Access. This example uses a PSK of secretkey.
```
 interface ipsec2
  ip address 10.10.10.1/30
  tunnel-source-interface ge0/4
  tunnel-destination      13.1.1.1   
  ike
   version      1
   mode         main
   rekey        14400
   cipher-suite aes128-cbc-sha1
   group        2
   authentication-type
    pre-shared-key
     pre-shared-secret secretkey
    !
   !
  !
  ipsec
   rekey         3600
   replay-window 512
   cipher-suite  aes256-cbc-sha1
```
Enter the no shutdown command on the ipsec2 interface to enable it.

Create a loopback interface to be used for tunnel monitoring.

interface loopback100
  ip address 10.1.50.1/32
  no shutdown

Create a default route for the network.
This route uses the second IP address (10.10.10.2 in this example) of the /30 subnet you used when you onboarded your remote network in Prisma Access. The Cisco Catalyst side of the network can route to this IP address and uses it as a next hop for routing.
```
ip route 0.0.0.0/0 10.10.10.2
```
Enter a VPN and give it a name.
```
vpn 512 name "Transport VPN"
```
Apply policies for the network.
```
policy
 app-visibility
 flow-visibility
```

Troubleshoot the Cisco Catalyst Remote Network

To troubleshoot problems related to SD-WAN tunnels in Cisco Catalyst, refer to the Cisco Catalyst documentation for configuring IPSec tunnels at the following URL: https://www.cisco.com/c/en/us/support/routers/sd-wan/tsd-products-support-series-home.html.

To troubleshoot issues in Prisma Access, we provide 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.

Integrate Prisma Access with Cisco Catalyst SD-WAN

Integrate ServiceNow with Prisma Access

Prisma Access Docs

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration)

Prisma Access Docs

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration)

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration) (Strata Cloud Manager)

Create a Remote Network Connection in Viptela

Troubleshoot the Viptela Remote Network

Integrate Prisma Access with Cisco Catalyst SD-WAN (Manual Integration) (Panorama)

Create a Remote Network Connection in Cisco Catalyst

Troubleshoot the Cisco Catalyst Remote Network

Activation and Onboarding

Next-Generation Firewalls

SASE

Cloud-Delivered Security Services

Network Security

Endpoints

Visibility & Monitoring

FedRAMP

Hardware Reference

Hardware Quick Start Guides

Virtual ION Deployment

3rd Party Integrations

Best Practices

Experts Corner