Onboard Remote Networks with Configuration Import

Use the bulk import capability to speed up the process of onboarding remote networks
To streamline the process to Onboard and Configure Remote Networks, you have the option to onboard at least one remote network and then export those settings to a Comma Separated Value (CSV) text file. The CSV file includes the values of IPSec tunnel and IKE gateway settings for the network you selected for export, and you can then edit these settings and make them unique for each new network you may want to onboard. You can modify the CSV file to include 1000 new remote networks and then import the CSV file back to speed up the process of onboarding new remote network locations.
The CSV file does not include keys or passwords, such as the BGP shared secret, the IKE preshared key, Proxy ID, IKE crypto profile, IPSec crypto profile. Therefore, any keys and passwords required for the IPSec tunnel and IKE gateway settings are inherited from the network you select when you initiate the CSV file import.
When using this bulk import process, you must wait for Prisma Access to deploy the infrastructure for securing these locations.
  1. Select
    Panorama
    Cloud Services
    Configuration
    Remote Networks
    (in the Onboarding section).
  2. Select a region, then
    Export
    the configuration of a remote network that you have previously onboarded.
    You must select a remote network and click
    Export
    . A CSV file that includes the settings is downloaded to your computer.
  3. Modify the CSV file to add configuration for remote networks.
    See Fields in the Remote Networks Table for a description of the fields and the possible values in this file.
    You must rename the network(s) listed in the exported file. If the file has duplicate names the import will fail.
  4. Import
    the CSV file.
    The configuration from the file are displayed on screen. The remote network you selected to import the file will serve as a model configuration, and the remote networks listed in the file will inherit the keys and any missing values that do not have to be unique from there.
  5. Commit and push your changes.
    1. Commit
      Commit and Push
      your changes.
    2. Click
      OK
      and
      Push
      .

Fields in the Remote Networks Table

The following table provides a description of the fields in the remote networks table. Fields marked as
Y
in the
Required
row are required fields and fields marked as
N
are optional.
Field
Description
Required? (Y/N)
name
The name of the remote network.
Y
bandwidth
The allocated bandwidth of the remote network. Acceptable values are:
  • 2 Mbps
  • 5 Mbps
  • 10 Mbps
  • 20 Mbps
  • 25 Mbps
  • 50 Mbps
  • 100 Mbps
  • 150 Mbps
  • 300 Mbps
  • 500 Mbps
  • 1000 Mbps
The 1000 Mbps bandwidth option is in preview mode. The throughput during preview is delivered on a best-effort basis and the actual performance will vary depending upon the traffic mix.
Y
region
The remote network’s region. See the list of Prisma Access locations for the values to enter.
Enter the locations exactly as they are in this document (for example,
US West
, or
Japan South
).
Y
subnets
Statically routed subnets on the LAN side of the remote network. Separate multiple subnets with commas.
N
bgp_peer_as
The BGP Autonomous System Number (ASN) of the remote network peer device.
N
bgp_peer_address
The BGP peer address of the remote network peer device.
N
tunnel_name
The name of the IPSec tunnel configuration. A unique value is required.
Y
gateway_name
The name of the IKE Gateway configuration. A unique value is required.
Y
peer_ip_address
The IP address of the Prisma Access peer device.
N
local_id_type
The type of IKE ID that Prisma Access presents to the peer device. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Configured Certificate values.
N
local_id_value
The value of the IKE ID that Prisma Access presents to the peer device. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Configured Certificate values.
N
peer_id_type
The value of the IKE ID that the peer presents to Prisma Access. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Peer Certificate values.
N
peer_id_value
The value of the IKE ID that Prisma Access presents to the peer device. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Peer Certificate values.
N
monitor_ip
The tunnel monitoring IP address the cloud will use to determine that the IPSec tunnel is up and the peer network is reachable.
You cannot export a proxy-ID value for the tunnel monitor.
N
proxy_ids
The proxy IDs that are configured for the peer. For route-based VPNs, leave this field blank. Specify the Proxy ID in the following CSV configuration format:
[{"
name
":"
proxyidname
", "
local
":"
1.2.3.4/32
", "
remote
":"
4.3.2.1/32
", "
protocol
":{"
udp
": {"
local-port
":
123
, "
remote-port
":
234
}}}, {"
name
":"
proxyidname2
", "
local
":"
2.3.4.5/32
", "
remote
":"
3.4.5.6/32
", "
protocol
":{"
tcp
": {"
local-port
":
234
,"
remote-port
":
345
}}}]
N
sec_wan_enabled
Specifies whether or not you enable a secondary IPSec tunnel. Acceptable values are
yes
and
no
.
N
sec_tunnel_name
The name of the secondary IPSec tunnel configuration. A unique value is required if you specify a secondary tunnel.
N
sec_gateway_name
The name of the secondary IKE Gateway configuration. A unique value is required if you specify a secondary tunnel.
N
sec_peer_ip_address
The IP address of the Prisma Access peer device for the secondary IPSec tunnel.
N
sec_local_id_type
The type of IKE ID that Prisma Access presents to the peer device for the secondary IPSec tunnel. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Configured Certificate values.
N
sec_local_id_value
The value of the IKE ID that Prisma Access presents to the peer device for the secondary IPSec tunnel. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Configured Certificate values.
N
sec_peer_id_type
The value of the IKE ID that the peer presents to Prisma Access for the secondary IPSec tunnel. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Peer Certificate values.
N
sec_peer_id_value
The value of the IKE ID that Prisma Access presents to the peer device for the secondary IPSec tunnel. If you use certificates in the remote network to which you import this file, all imported types specified will refer to the Peer Certificate values.
N
sec_monitor_ip
The tunnel monitoring IP address the cloud will use for the secondary IPSec tunnel to determine that the IPSec tunnel is up and the peer network is reachable.
You cannot export a proxy-ID value for the tunnel monitor.
N
sec_proxy_ids
The proxy IDs that are configured for the peer for the secondary IPSec tunnel. For route-based VPNs, leave this field blank. Specify the Proxy ID in the following CSV configuration format:
[{"
name
":"
proxyidname
", "
local
":"
1.2.3.4/32
", "
remote
":"
4.3.2.1/32
", "
protocol
":{"
udp
": {"
local-port
":
123
, "
remote-port
":
234
}}}, {"
name
":"
proxyidname2
", "
local
":"
2.3.4.5/32
", "
remote
":"
3.4.5.6/32
", "
protocol
":{"
tcp
": {"
local-port
":
234
,"
remote-port
":
345
}}}]
N

Recommended For You