There is no need to buy physical firewall hardware when you host multiple customers requiring individual secure access to their FW. You just create virtual domains (VDOMs).
You can create multiple Virtual Domains (VDOMs), which are treated as separate firewall instances. The reporting you receive out of this appliance is excellent. You will not need an external management system.
1. sFlow and NetFlow
I could not configure sFlow from the FortiGate graphical user interface. I realized that the sFlow configuration is available only from the CLI, and discovered that sFlow is not supported on virtual interfaces, such as VDOM links, IPsec, or GRE.
NetFlow is a network protocol developed by Cisco for collecting IP traffic information and monitoring network traffic. It is not supported on FortiGate for those who have a NetFlow analyzer/collector already setup in their network.
2. Policies
To control traffic in a firewall, you need to create and apply policies to the FW interfaces. By default, policies are sorted by FW interfaces and this makes FW interfaces an integral part of the policies. Zones provide the option to logically group multiple virtual and physical FortiGate firewall interfaces. Then, you apply security policies to those zones (logical groups of interfaces) to control traffic flow on those interfaces.
In a FortiGate unit with a lot of interfaces (including virtual interfaces), there is a high probability of having duplication of policies.
Three to five years.
These devices are very stable.
They are easily scalable with multiple built-in interfaces. It supports a minimum of 10 VDOMs. VDOM supports all dynamic routing protocols like RIP, OSPF, BGP, and IS-IS. You do not need to reboot after enabling the VDOMs.
Area for improvement - there is one big configuration file with no separations for the unique VDOMs. Maybe they could separate individual VDOM configuration files with the root VDOM configuration file referencing the individual VDOM config files.
Customer Service:
Customer service is great, an eight out 10.
Technical Support:
I will give technical support an eight out 10.
We previously used different solutions as well. We did not switch, we have different requirements for different customers.
The user interface is relatively easy. The devices are easy to deploy and figure out if you have experience with other security appliances.
It was an in-house installation.
The ROI is great. These boxes are not that expensive compared to what they can do, their functionality, and the reporting you receive.
Fortinet licensing is straightforward and less confusing compared to Cisco. Fortinet has one or two license types, and the VPN numbers are only limited by the hardware chassis make.
I already have experience with Cisco ASA, so it was simply a customer preference and well within the budget.
Great appliances, and it is affordable.
The easy way to migrate from one model to another is taking the config file and modify it manually, say rename port WAN to port-1 ( sometimes you need to modify the syntax of commands when moving between different versions) and upload the config back. Another method is to divided the config file to multiple sections say interfaces , NAT policies , Firewall ACLS / objects / object groups , then modify every part as required and upload them one-by-one.