Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
robinct
New Contributor

IPSEC throughput limited?

We are having some throughput problems between two Fortinet devices.

 

We have a 100D connected to a 60E over an IPSEC tunnel. The traffic seems to stagger around ~200Mbps even though we have a direct Gbps fiber connection.

 

Somewhere, it feels like a limitation of sorts. Any setting that could give this behaviour, or could it be that the 100D is simply too old for these speeds?

13 REPLIES 13
heisenberg
New Contributor III

vpn imply an overhead over the "pure" speed of a link. It is normal that a device cannot do a full link speed over vpn channel.

to do a full speed vpn connection you need specific processor/device (more expensive that a 100D)

 

hope this helps.

 

ps. you can see your vpn limit on the forti 100D docs. (consider even the other traffic that pass through the wan you are using...the "tube" is the same and it is shared)

heisenberg
New Contributor III

for example a 110C have a 100Mbit limitation over vpn.

a 100D is granted for 300Mbit over ipsec vpn but you have to consider the slowest link, in this case the 60E that is granted for 150Mbit. You are lucky because you are slightly over performance.

 

my best

 

oheigl

I'm not sure where you got those values, but in the datasheet these are listed:

FortiGate 60E: IPsec VPN Throughput (512 byte) - 2 Gbps

FortiGate 100D: IPsec VPN Throughput (512 byte) - 380 Mbps

heisenberg
New Contributor III

Sorry, you are absolutely right I was reading the ssl vpn not the ipsec. (this can explain the slightly more throughput over 150Mbps that I wrote).

Anyway you should go up to 380 because of the 100D....up to....as you use AES256-SHA256 and other condition over the firewall. May be 200Mbps seems not as lighting fast but, pheraps you should consider the load on the device or for example the geographic (routing) distance

ede_pfau

1- for testing, reduce the IPsec parameters to AES128 and SHA1

these are guaranteed to be handled in hardware (SHA384 for ex. is not)

2- no UTM whatsoever in the tunnel policy (as this will involve the CPU)

 

This should give you fully accelerated IPsec. The weak link is the 100D. Consider buying a second 60E and finance it through the reduced service contract costs.


Ede

"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
robinct

heisenberg wrote:

Sorry, you are absolutely right I was reading the ssl vpn not the ipsec. (this can explain the slightly more throughput over 150Mbps that I wrote).

Anyway you should go up to 380 because of the 100D....up to....as you use AES256-SHA256 and other condition over the firewall. May be 200Mbps seems not as lighting fast but, pheraps you should consider the load on the device or for example the geographic (routing) distance

Well, I need to figure out what might be the cause and make actions against it :) 380 is almost double the speed is absolutely a better number.

 

I see that both 100D and 60E has 200 Mbps "Threat Protection Throughput", but how do I verify if that is enabled or not?

Toshi_Esumi

Since it's not clear in the original post I wanted to point out one thing: VPN throughput is half dictated by the environment/connection between two end devices. If the test is not done with two devices side-by-side over a cable, you need to include that part into consideration. 

robinct

toshiesumi wrote:

Since it's not clear in the original post I wanted to point out one thing: VPN throughput is half dictated by the environment/connection between two end devices. If the test is not done with two devices side-by-side over a cable, you need to include that part into consideration. 

Sorry I wasn't clear enough about it. The connection is a leased fiber connection, going straight from one firewall to the other, not over the internet, etc.

Toshi_Esumi

Then why do you need a VPN over a point-to-point dedicated/private circuit?

Labels
Top Kudoed Authors