The situation is a seminar session for about 250 users who need access to a BI server through their client in-house application. It's look like this:
Five Servers -> FortiADC -> FortiWLC-> Meru Wireless
The situation is a seminar session for about 250 users who need access to a BI server through their client in-house application. It's look like this:
Five Servers -> FortiADC -> FortiWLC-> Meru Wireless
Even though FortiADC is not completely working for me, overall it helps me provide workload distribution to the servers, as expected.
Of course the troubleshooting tools. I think the troubleshooting command is easy and useful. Because ADC is the intermediary between the servers and the end-user application, it gives thorough information about the traffic, what the problem is.
The L7 Persistent load-balancing algorithm has not worked for me after having tested it many times with my customer's in-house application. I'd like to suggest that the company make sure that all load-balancing algorithms work properly with most applications, even those that are in-house apps, because this is the main requirement of ADC.
After I created a virtual server, the servers are still reachable from the client side by a Ping command. That did not happen with F5. I have to work around it
by setting up a traffic policy.
I did not test the SSL decryption feature but it's an essential point that FortiADC ensure they can support all the newest encryption methods and always be up to date.
No issues with stability.
No issues with scalability.
I have not engaged ADC support.
I think they can make it easier. The company's homework is to redesign those menus to configure with the smallest number of steps.
If FortiADC wants to compete - and having used F5 LTM for a year - in my opinion:
