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
| Argument | Description | Required |
|---|---|---|
NAME | Name of the service connection | Yes |
Options
| Option | Description | Required |
|---|---|---|
--ipsec-tunnel TEXT | IPsec tunnel for the service connection | Yes |
--region TEXT | Region for the service connection | Yes |
--onboarding-type TEXT | Onboarding type (default: classic) | No |
--backup-sc TEXT | Backup service connection name | No |
--nat-pool TEXT | NAT pool for the service connection | No |
--source-nat | Enable source NAT | No |
--subnets TEXT | Subnets (repeat for multiple) | No |
--bgp-enable | Enable BGP | No |
--bgp-peer-as TEXT | BGP peer AS number | No |
--bgp-peer-ip TEXT | BGP peer IP address | No |
--bgp-local-ip TEXT | BGP local IP address | No |
--bgp-secret TEXT | BGP authentication secret | No |
--qos-enable | Enable QoS | No |
--qos-profile TEXT | QoS profile name | No |
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
| Argument | Description | Required |
|---|---|---|
NAME | Name of the service connection to delete | Yes |
Options
| Option | Description | Required |
|---|---|---|
--force | Skip confirmation prompt | No |
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
| Option | Description | Required |
|---|---|---|
--file TEXT | Path to YAML file containing service connection definitions | Yes |
--dry-run | Simulate execution without applying changes | No |
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
| Argument | Description | Required |
|---|---|---|
NAME | Name of the service connection to show; omit to list all | No |
Options
| Option | Description | Required |
|---|---|---|
--output, -o [table|json|yaml] | Output format (default: table) | No |
--max-results INTEGER | Maximum number of results to display | No |
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
| Option | Description | Required |
|---|---|---|
--file TEXT | Custom output filename | No |
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
- Use Descriptive Names: Name service connections to clearly identify the location or purpose (e.g., "branch-office-nyc", "retail-store-001").
- Configure Backup Connections: Set up backup service connections for critical sites to ensure continuous connectivity during primary tunnel failures.
- Enable BGP for Complex Networks: Use BGP dynamic routing when connecting sites with multiple subnets or complex routing requirements.
- Secure BGP Secrets: Store BGP authentication secrets securely and rotate them regularly to maintain routing security.
- Apply QoS Profiles: Assign appropriate QoS profiles to prioritize business-critical traffic over less important flows.
- Plan Subnets Carefully: Document subnet allocations across all service connections to avoid overlaps and ensure proper routing.