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 Configure the GlobalProtect Cloud Service for 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 the GlobalProtect cloud service to deploy the infrastructure for securing these locations.
  1. Select PanoramaCloud ServicesConfigurationRemote 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 your changes.
    1. CommitCommit 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.
FieldDescriptionRequired? (Y/N)
nameThe name of the remote network. Y
bandwidthThe allocated bandwidth of the remote network. Acceptable values are:
  • 2 Mbps
  • 5 Mbps
  • 10 Mbps
  • 25 Mbps
  • 50 Mbps
  • 100 Mbps
  • 300 Mbps
Y
regionThe remote network’s region. Acceptable values are:
  • Asia Pacific (Mumbai)
  • Asia Pacific (Seoul)
  • Asia Pacific (Singapore)
  • Asia Pacific (Sydney)
  • Asia Pacific (Tokyo)
  • Canada (Montreal)
  • EU (Frankfurt)
  • EU (Ireland)
  • EU (London)
  • South America (Sao Paulo)
  • US East (N. Virginia)
  • US East (Ohio)
  • US West (N. California)
  • US West (Oregon)
Y
subnetsStatically routed subnets on the LAN side of the remote network. Separate multiple subnets with commas.N
bgp_peer_asThe BGP Autonomous System Number (ASN) of the remote network peer device.N
bgp_peer_addressThe BGP peer address of the remote network peer device.N
tunnel_nameThe name of the IPSec tunnel configuration. A unique value is required.Y
gateway_nameThe name of the IKE Gateway configuration. A unique value is required.Y
peer_ip_addressThe IP address of the GlobalProtect cloud service peer device. N
local_id_typeThe type of IKE ID that the GlobalProtect cloud service 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_valueThe value of the IKE ID that the GlobalProtect cloud service 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_typeThe value of the IKE ID that the peer presents to the GlobalProtect cloud service. 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_valueThe value of the IKE ID that the GlobalProtect cloud service 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_ipThe 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_idsThe 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_enabledSpecifies whether or not you enable a secondary IPSec tunnel. Acceptable values are yes and no.N
sec_tunnel_nameThe name of the secondary IPSec tunnel configuration. A unique value is required if you specify a secondary tunnel.N
sec_gateway_nameThe name of the secondary IKE Gateway configuration. A unique value is required if you specify a secondary tunnel.N
sec_peer_ip_addressThe IP address of the GlobalProtect cloud service peer device for the secondary IPSec tunnel. N
sec_local_id_typeThe type of IKE ID that the GlobalProtect cloud service 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_valueThe value of the IKE ID that the GlobalProtect cloud service 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_typeThe value of the IKE ID that the peer presents to the GlobalProtect cloud service 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_valueThe value of the IKE ID that the GlobalProtect cloud service 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_ipThe 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_idsThe 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

Related Documentation