>
    Fields in Remote Networks Table
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma
    3. Prisma Access
    4. Use Remote Networks to Secure Branches
    5. Onboard Remote Networks with Configuration Import
    6. Fields in Remote Networks Table
    Download PDF

    Fields in Remote Networks Table

    Table of Contents

    Fields in 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
    bandwidth
    (Deployments that allocate bandwidth by location only) 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
    regionThe remote network’s location. 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
    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 Prisma Access peer device.N
    local_id_typeThe 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_valueThe 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_typeThe 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_valueThe 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_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 Prisma Access peer device for the secondary IPSec tunnel. N
    sec_local_id_typeThe 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_valueThe 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_typeThe 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_valueThe 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_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_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
    ecmp_link_1_tunnel_name(ECMP deployments only) The name of the IPSec tunnel configuration for ECMP tunnel 1. A unique value is required.
    ecmp_link_1_gateway_name(ECMP deployments only) The name of the IKE Gateway configuration for ECMP tunnel 1. A unique value is required.
    ecmp_link_1_peer_ip_address(ECMP deployments only) The IP address of the Prisma Access peer device for ECMP tunnel 1.
    ecmp_link_1_local_id_type(ECMP deployments only) The type of IKE ID that Prisma Access presents to the peer device for ECMP tunnel 1. 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.
    ecmp_link_1_local_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 1. 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.
    ecmp_link_1_peer_id_type(ECMP deployments only) The value of the IKE ID that the peer presents to Prisma Access for ECMP tunnel 1. 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.
    ecmp_link_1_peer_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 1. 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.
    ecmp_link_1_monitor_ip(ECMP deployments only) The tunnel monitoring IP address the cloud will use to determine that the IPSec tunnel is up and the peer network is reachable for ECMP tunnel 1.
    You cannot export a proxy-ID value for the tunnel monitor.
    ecmp_link_1_proxy_ids (ECMP deployments only) The proxy IDs that are configured for the peer for ECMP tunnel 1. 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}}}]
    ecmp_link_1_bgp_peer_as(ECMP deployments only) The BGP Autonomous System Number (ASN) of the remote network peer device for ECMP tunnel 1.
    ecmp_link_1_bgp_peer_address(ECMP deployments only) The BGP peer address of the remote network peer device for ECMP tunnel 1.
    ecmp_link_2_tunnel_name(ECMP deployments only) The name of the IPSec tunnel configuration for ECMP tunnel 2. A unique value is required.
    ecmp_link_2_gateway_name(ECMP deployments only) The name of the IKE Gateway configuration for ECMP tunnel 2. A unique value is required.
    ecmp_link_2_peer_ip_address(ECMP deployments only) The IP address of the Prisma Access peer device for ECMP tunnel 2.
    ecmp_link_2_local_id_type(ECMP deployments only) The type of IKE ID that Prisma Access presents to the peer device for ECMP tunnel 2. 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.
    ecmp_link_2_local_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 2. 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.
    ecmp_link_2_peer_id_type(ECMP deployments only) The value of the IKE ID that the peer presents to Prisma Access for ECMP tunnel 2. 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.
    ecmp_link_2_peer_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 2. 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.
    ecmp_link_2_monitor_ip(ECMP deployments only) The tunnel monitoring IP address the cloud will use to determine that the IPSec tunnel is up and the peer network is reachable for ECMP tunnel 2.
    You cannot export a proxy-ID value for the tunnel monitor.
    ecmp_link_2_proxy_ids (ECMP deployments only) The proxy IDs that are configured for the peer for ECMP tunnel 2. 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}}}]
    ecmp_link_2_bgp_peer_as(ECMP deployments only) The BGP Autonomous System Number (ASN) of the remote network peer device for ECMP tunnel 2.
    ecmp_link_2_bgp_peer_address(ECMP deployments only) The BGP peer address of the remote network peer device for ECMP tunnel 2.
    ecmp_link_3_tunnel_name(ECMP deployments only) The name of the IPSec tunnel configuration for ECMP tunnel 3. A unique value is required.
    ecmp_link_3_gateway_name(ECMP deployments only) The name of the IKE Gateway configuration for ECMP tunnel 3. A unique value is required.
    ecmp_link_3_peer_ip_address(ECMP deployments only) The IP address of the Prisma Access peer device for ECMP tunnel 3.
    ecmp_link_3_local_id_type(ECMP deployments only) The type of IKE ID that Prisma Access presents to the peer device for ECMP tunnel 3. 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.
    ecmp_link_3_local_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 3. 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.
    ecmp_link_3_peer_id_type(ECMP deployments only) The value of the IKE ID that the peer presents to Prisma Access for ECMP tunnel 3. 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.
    ecmp_link_3_peer_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 3. 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.
    ecmp_link_3_monitor_ip(ECMP deployments only) The tunnel monitoring IP address the cloud will use to determine that the IPSec tunnel is up and the peer network is reachable for ECMP tunnel 3.
    You cannot export a proxy-ID value for the tunnel monitor.
    ecmp_link_3_proxy_ids (ECMP deployments only) The proxy IDs that are configured for the peer for ECMP tunnel 3. 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}}}]
    ecmp_link_3_bgp_peer_as(ECMP deployments only) The BGP Autonomous System Number (ASN) of the remote network peer device for ECMP tunnel 3.
    ecmp_link_3_bgp_peer_address(ECMP deployments only) The BGP peer address of the remote network peer device for ECMP tunnel 3.
    ecmp_link_4_tunnel_name(ECMP deployments only) The name of the IPSec tunnel configuration for ECMP tunnel 4. A unique value is required.
    ecmp_link_4_gateway_name(ECMP deployments only) The name of the IKE Gateway configuration for ECMP tunnel 4. A unique value is required.
    ecmp_link_4_peer_ip_address(ECMP deployments only) The IP address of the Prisma Access peer device for ECMP tunnel 4.
    ecmp_link_4_local_id_type(ECMP deployments only) The type of IKE ID that Prisma Access presents to the peer device for ECMP tunnel 4. 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.
    ecmp_link_4_local_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 4. 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.
    ecmp_link_4_peer_id_type(ECMP deployments only) The value of the IKE ID that the peer presents to Prisma Access for ECMP tunnel 4. 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.
    ecmp_link_4_peer_id_value(ECMP deployments only) The value of the IKE ID that Prisma Access presents to the peer device for ECMP tunnel 4. 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.
    ecmp_link_4_monitor_ip(ECMP deployments only) The tunnel monitoring IP address the cloud will use to determine that the IPSec tunnel is up and the peer network is reachable for ECMP tunnel 4.
    You cannot export a proxy-ID value for the tunnel monitor.
    ecmp_link_4_proxy_ids (ECMP deployments only) The proxy IDs that are configured for the peer for ECMP tunnel 4. 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}}}]
    ecmp_link_4_bgp_peer_as(ECMP deployments only) The BGP Autonomous System Number (ASN) of the remote network peer device for ECMP tunnel 4.
    ecmp_link_4_bgp_peer_address(ECMP deployments only) The BGP peer address of the remote network peer device for ECMP tunnel 4.
    spn-name(Deployments that allocate bandwidth by compute location only) The name of the IPSec Termination Node. This field is required for deployments that allocate bandwidth by compute location.

    © 2024 Palo Alto Networks, Inc. All rights reserved.