Skip to main content

Service Connection

Service connections define how branch offices and remote locations connect to Prisma SASE, enabling secure connectivity through IPsec tunnels with optional BGP routing and QoS configurations. The scm CLI provides commands to create, update, delete, bulk load, and back up service connection configurations.

Overview

The service-connection commands allow you to:

  • Create service connections with IPsec tunnels and subnet configurations
  • Configure BGP routing for dynamic route exchange
  • Enable QoS profiles for traffic prioritization and source NAT
  • Bulk import service connection configurations from YAML files
  • Export service connection configurations for backup or migration

Set Service Connection

Create or update a service connection configuration.

Syntax

scm set sase service-connection NAME [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEName of the service connectionYes

Options

OptionDescriptionRequired
--ipsec-tunnel TEXTIPsec tunnel for the service connectionYes
--region TEXTRegion for the service connectionYes
--onboarding-type TEXTOnboarding type (default: classic)No
--backup-sc TEXTBackup service connection nameNo
--nat-pool TEXTNAT pool for the service connectionNo
--source-natEnable source NATNo
--subnets TEXTSubnets (repeat for multiple)No
--bgp-enableEnable BGPNo
--bgp-peer-as TEXTBGP peer AS numberNo
--bgp-peer-ip TEXTBGP peer IP addressNo
--bgp-local-ip TEXTBGP local IP addressNo
--bgp-secret TEXTBGP authentication secretNo
--qos-enableEnable QoSNo
--qos-profile TEXTQoS profile nameNo

Examples

Create a Basic Service Connection

$ scm set sase service-connection branch-office-1 \
--ipsec-tunnel ipsec-tunnel-branch-1 \
--region us-east-1 \
--subnets 10.1.0.0/24 --subnets 10.1.1.0/24
---> 100%
Created service connection: branch-office-1

Create a Service Connection with BGP

$ scm set sase service-connection hq-connection \
--ipsec-tunnel ipsec-tunnel-hq \
--region us-west-2 \
--subnets 172.16.0.0/16 \
--bgp-enable \
--bgp-peer-as "65001" \
--bgp-peer-ip "192.168.1.1" \
--bgp-local-ip "192.168.1.2" \
--bgp-secret "mysecret123"
---> 100%
Created service connection: hq-connection

Create a Service Connection with High Availability

$ scm set sase service-connection critical-site \
--ipsec-tunnel ipsec-tunnel-primary \
--region eu-central-1 \
--backup-sc backup-connection \
--subnets 10.10.0.0/16 \
--source-nat \
--qos-enable \
--qos-profile business-critical
---> 100%
Created service connection: critical-site

Delete Service Connection

Delete a service connection configuration from SCM.

Syntax

scm delete sase service-connection NAME [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEName of the service connection to deleteYes

Options

OptionDescriptionRequired
--forceSkip confirmation promptNo

Example

$ scm delete sase service-connection branch-office-1 --force
---> 100%
Deleted service connection: branch-office-1

Load Service Connections

Load multiple service connection configurations from a YAML file.

Syntax

scm load sase service-connection [OPTIONS]

Options

OptionDescriptionRequired
--file TEXTPath to YAML file containing service connection definitionsYes
--dry-runSimulate execution without applying changesNo

YAML File Format

---
service_connections:
- name: branch-office-east
ipsec_tunnel: ipsec-tunnel-east
region: us-east-1
onboarding_type: classic
subnets:
- 10.1.0.0/24
- 10.1.1.0/24
bgp_enable: true
bgp_peer_as: "65001"
bgp_peer_ip_address: 192.168.1.1
bgp_local_ip_address: 192.168.1.2
bgp_secret: bgp-secret-east

- name: branch-office-west
ipsec_tunnel: ipsec-tunnel-west
region: us-west-2
backup_SC: branch-office-west-backup
subnets:
- 10.2.0.0/24
- 10.2.1.0/24
source_nat: true
nat_pool: nat-pool-west
qos_enable: true
qos_profile: standard-qos

Examples

Load Service Connections

$ scm load sase service-connection --file service-connections.yml
---> 100%
✓ Loaded service connection: branch-office-east
✓ Loaded service connection: branch-office-west

Successfully loaded 2 out of 2 service connections from 'service-connections.yml'

Dry Run to Validate Configuration

$ scm load sase service-connection --file service-connections.yml --dry-run
---> 100%
[DRY RUN] Would load service connection: branch-office-east
[DRY RUN] Would load service connection: branch-office-west

Dry run complete. 2 service connections would be loaded.

Show Service Connection

Display service connection configurations.

Syntax

scm show sase service-connection [NAME] [OPTIONS]

Arguments

ArgumentDescriptionRequired
NAMEName of the service connection to show; omit to list allNo

Options

OptionDescriptionRequired
--output, -o [table|json|yaml]Output format (default: table)No
--max-results INTEGERMaximum number of results to displayNo
note

When no NAME is specified, all items are listed by default.

Examples

Show Specific Service Connection

$ scm show sase service-connection branch-office-east
---> 100%
Service Connection: branch-office-east
IPsec Tunnel: ipsec-tunnel-east
Region: us-east-1
Onboarding Type: classic
Subnets: 10.1.0.0/24, 10.1.1.0/24
BGP Settings:
Enabled: true
Peer AS: 65001
Peer IP: 192.168.1.1
Local IP: 192.168.1.2

List All Service Connections (Default Behavior)

$ scm show sase service-connection
---> 100%
Service Connections:
------------------------------------------------------------
Name: branch-office-east
IPsec Tunnel: ipsec-tunnel-east
Region: us-east-1
Subnets: 10.1.0.0/24, 10.1.1.0/24
BGP: Enabled (AS 65001)
------------------------------------------------------------
Name: branch-office-west
IPsec Tunnel: ipsec-tunnel-west
Region: us-west-2
Subnets: 10.2.0.0/24, 10.2.1.0/24
QoS: Enabled
------------------------------------------------------------

Backup Service Connections

Backup all service connection configurations to a YAML file.

Syntax

scm backup sase service-connection [OPTIONS]

Options

OptionDescriptionRequired
--file TEXTCustom output filenameNo

Examples

Backup with Default Filename

$ scm backup sase service-connection
---> 100%
Successfully backed up 3 service connections to service_connection_20240115_120530.yaml

Backup with Custom Filename

$ scm backup sase service-connection --file sc-backup.yaml
---> 100%
Successfully backed up 3 service connections to sc-backup.yaml

Best Practices

  1. Use Descriptive Names: Name service connections to clearly identify the location or purpose (e.g., "branch-office-nyc", "retail-store-001").
  2. Configure Backup Connections: Set up backup service connections for critical sites to ensure continuous connectivity during primary tunnel failures.
  3. Enable BGP for Complex Networks: Use BGP dynamic routing when connecting sites with multiple subnets or complex routing requirements.
  4. Secure BGP Secrets: Store BGP authentication secrets securely and rotate them regularly to maintain routing security.
  5. Apply QoS Profiles: Assign appropriate QoS profiles to prioritize business-critical traffic over less important flows.
  6. Plan Subnets Carefully: Document subnet allocations across all service connections to avoid overlaps and ensure proper routing.