Fortinet Fortigate Cluster - Create
To create a Fortinet Fortigate Cluster, follow the guided steps in the Evolution Platform console. The portal collects service-level and device-level data in the order below and validates inputs before provisioning.
Step 1 - Select project
Select the project in which you want to deploy your virtual Edge:
Select your project.
Step 2 - Deployment configuration
2.1 Name your Virtual Edge (This name will be displayed on the Virtual Network Edge dashboard)
Set Virtual Edge name.
Select implementation mode.
Virtual device configuration
2.3 Fill the Virtual Device name (This name will be used as hostname for the virtual device).
2.4 Select the Orange POP which correspond to the location of POP.
Fill Virtual Device Name, Region and POP.
For Dual topology, different POP can be chosen for each virtual Device.
For Cluster topology, the Virtual devices must be on the same POP.
Select Internet and MPLS Bandwidth for each Virtual Device.
Select Internet and MPLS bandwidth for the Virtual Device.
Step 3 - Virtual Edge configuration
3.1 Select the Software version.
Available software versions are :
- 7.2.5
- 7.2.6
- 7.4.9
3.2 Select the Virtual Device flavor.
Available flavors are :
| Standard | DPDK | |
|---|---|---|
| Extra-Small | 1 vCPU 2 GB Mem 64 GB Disk | - |
| Small | 2 vCPU 4 GB Mem 64 GB Disk | 2 vCPU 4 GB Mem 64 GB Disk |
| Medium | 4 vCPU 8 GB Mem 64 GB Disk | 4 vCPU 8 GB Mem 64 GB Disk |
| Medium | 4 vCPU 16 GB Mem 64 GB Disk | 4 vCPU 16 GB Mem 64 GB Disk |
| Large | 8 vCPU 16 GB Mem 64 GB Disk | 8 vCPU 16 GB Mem 64 GB Disk |
- For Dual topology, different flavors can be selected for each Virtual device.
- DPDK (Data Plane Development Kit) is a set of libraries and drivers designed to acceler- ate packet processing and optimize performance in network applications. It provides a high-performance framework for managing network traffic at a low level, bypassing the traditional kernel network stack to enhance throughput and reduce latency.
Pay attention the use of an image with DPDK significantly increases energy consumption and therefore the associated carbon footprint.
3.3 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.
Step 4 - Interfaces configuration
Interfaces
Interface configuration uses the exact labels shown in the portal: #1 - Internet Interface, #2 - MPLS-VPN interface, and #3 - HA Interface.
Interface layout used in the provisioning form.
-
#1 - Internet Interface: you may request additional platform public IPv4 addresses by setting Added IP address number (1..8). Allocated public IP addresses are platform-generated and displayed as informational outputs after provisioning.
-
#2 - MPLS-VPN interface: enable the required VLAN sub-interfaces (VLAN 101..108) and for each sub-interface select one or more VPN entries from the VPN list. For each selected VLAN sub-interface you can set the VPN name and the VPN role. BGP configuration is available per VLAN sub-interface and is optional.
-
#3 - HA Interface: present in the topology; no user parameters are required for this interface in the provisioning form.
Virtual device configuration
The provisioning form asks for image and flavor selection for the virtual devices and several VM-level values. Cloud-init is generated by the platform for this VNF; uploading custom cloud-init userdata is not supported for this blueprint.
Virtual device configuration fields in the portal.
Step 5 - Service specific parameters
5.1 Fill in the following service parameters:
- Disk size: Boot volume size (in GiB) for the Fortigate virtual device. The platform asks this value at provisioning time. min: 16, max: 500.
- Disk size: Boot volume size (in GiB) for the second Fortigate virtual device. The platform asks this value at provisioning time. min: 16, max: 500.
- VM AS number: AS number assigned to the virtual machine if required by the service. The platform accepts 2- or 4-byte AS numbers in the documented range. min:1, max:4294967295; description: 'AS 2 and 4 Bytes allowed'..
- Equipment name: Provide a short equipment name (allowed characters: letters, digits, hyphen, underscore) that will identify your Fortigate instance in the platform. pattern: [a-zA-Z0-9-_]*; virtualDeviceNameMaxLength: 22 (see specification)..
- Password: Provide an administrator password for the virtual device. It will be set by the platform during provisioning and is not displayed in plain text afterwards. pattern:.50; maxLength: 50, minLength: 1..
- Fortinet manager IP address: Optionally provide the IP address of your Fortinet manager if you want that information recorded with the service configuration.
- Fortinet manager serial number: Optionally provide the Fortinet manager serial number for record-keeping with the service configuration. pattern: '[a-zA-Z0-9-]*' per specification..
5.2 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.
Step 6 - Validation
After clicking the Continue button, a page summarizing the characteristics of the Virtual Edge will be displayed.
This page is divided into several sections :
- Projects
- Deployment
- Virtual edge configuration
- Interfaces configuration
- Service specific parameters
At this stage, it is still possible to modify the characteristics for these sections.
One section is dedicated to display the Carbon footprint of the Virtual Edge :
Carbon footprint for Virtual Edge.
Click on the Provision button to initiate the provisioning of the Virtual Network Edge.
You can also preserve the Virtual Network Edge configuration by clicking the Save and close button and the following toast is displayed.
In this case, you will find the Virtual Network Edge in designed state on the .
