Defining the Project Template
Typically, the following steps must be completed in order to define your Project Template:
- Define the following two aggregate subnets for your project:
Parameter Description lan_summary A subnet summarizing all the corporate (internal) prefixes in the project
lo_summary A subnet summarizing all the SD-WAN device loopbacks in the project
In the BGP per overlay design method, lo_summary is replaced by tunnel_summary, summarizing all the tunnel subnets in the project.
- Define the regions of the project. For each region, define the following parameters:
Parameter Description as Autonomous System number for the region
lan_summary A subnet summarizing all the corporate (internal) prefixes in the region
lo_summary
A subnet summarizing all the SD-WAN device loopbacks in the region
hubs
List of the Hubs serving the region
In the BGP per overlay design method, lo_summary is not required.
- Define the device profiles for the project. Each profile must list the interfaces and describe their roles and settings. Define the following parameters for each interface:
Parameter Description name Interface name, as it appears on the FortiGate device
role
Interface role (such as LAN-facing or WAN-facing) ol_type Overlay to be established over this interface
ip IP address (including mask) or
dhcp
keyword for DHCP client - Define the Hubs serving the project. All the Hubs referenced in the regions definition must be described here. For each Hub, define the following parameters:
Parameter Description lo_bgp Hub loopback IP, used for BGP termination
overlays Dictionary describing the overlays served by this Hub
All the overlays referenced in the device profiles using
ol_type
parameter must be described here. For each overlay, define the following parameters:Parameter Description wan_ip Hub underlay IP used to build this overlay
network_id Network ID used to connect to this overlay
This overlay information will be used by the Edge devices to establish IPsec tunnels to the Hubs.
In the BGP per overlay design method,
tunnel_net
parameter is required in addition to defining the tunnel subnet for each overlay. See External resources.It is a good idea to start from one of the Project Template examples provided in our GitHub repository.