I see a big discrepency between 7.2/7.4 and 7.6 for maximum values.
On a 1500D, 1100E, 2200E, and 3301E the maximum number of server-load-balance is 2048 when running 7.2 and 7.4
For 7.6 these values drop to 64. Why is there such a big discrepency?
firewall.vip type=server-load-balance (virtual server)
Solved! Go to Solution.
The helpdesk rep has verified with the devs. The 64 value in the maximum values table website is is populated by documentation and the source docs had the wrong value.
Hard value for the maximum number of type=server-load-balance is 2048 for the 7.6 train.
I guess because 7.6 needs more RAM for other features.
I am hoping it is just a typo and that value reflects the other global limit of real servers per load balancer and the real value matches max vips of 32768
There would be no way I would be able to upgrade some of my fortigates to 7.6.2. I would lose hundreds or 1000+ load balancers on some of my firewalls.
Maybe NGINX in k8s, possibly using k8s SDN connectors with dynamic address objects but that has a low limit of 256.
I have a ticket in. the rep said he had zero problem adding in over 500 load balancers, with my sample configuration I gave him, to an 1100E.
He doesn't think it is a table size restriction. He has reached out to the development team to see what that value actually means since it doesn't even show up in "print tablesize".
The helpdesk rep has verified with the devs. The 64 value in the maximum values table website is is populated by documentation and the source docs had the wrong value.
Hard value for the maximum number of type=server-load-balance is 2048 for the 7.6 train.
Thanks for sharing, Guerriero.
User | Count |
---|---|
2548 | |
1354 | |
795 | |
646 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.