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

New Firmware Version concludes in a very slow web ui

Hi everybody! I have recently updated the firmware of our Fortigate 310B Cluster to the latest version MR1 Patch 3. I now experience a very slow performance of the web interface, also the CLI via SSH is much slower than usual. Does anyone share the same experience with this release? Kind regards, Oliver
6 REPLIES 6
laf
New Contributor II

I ve hit this problem with v4.0 first releases. Now I m using v4.0 MR1 patch 1. Works fine.

The most expensive and scarce resource for man is time, paradoxically, it' s infinite.

The most expensive and scarce resource for man is time, paradoxically, it' s infinite.
ddskier
Contributor

I' ve noticed that as well when using IE. If I connect using Firefox the UI is very snappy.

-DDSkier FCNSA, FCNSP FortiGate 400D, (2) 200D, (12) 100D, (2) 60D

-DDSkier FCNSA, FCNSP FortiGate 400D, (2) 200D, (12) 100D, (2) 60D
oheigl
Contributor II

I usually use Firefox for the WebUI, I know recognized that the performance isn' t that slow all the time. It' s only sometimes, strange.
Victor
New Contributor III

I am running ver. 4 MR1 Patch 2. I can confirm that the web interface can be woefully slow. I only allow access via https. I cannot say that I have found any performance issue with ssh. I have a call ticket on this issue with Fortinet but as of yet we have not come up with a definitive answer to this problem. I will say from experimentation that in my case, an Active-Active HA, that when I turn off one of the units gui admin access improves dramatically even when the CPU is pegged over 80%. Given the amount of traffic we have, I cannot maintain this solo operation for very long. I had assumed, due to certificate issues with banking sites and IE7 & IE8 in the version 4 code (these versions are using a rare 128-bit certificate), that my problems were caused by some strange anomaly with https & HA, but from your comments, it would seem that some of you are simply using http. Can you confirm as it will be helpful. I will certainly alert my support engineer to this thread. I would also encourage you, if you have not done so, to open a call ticket with Fortinet. Victor
oheigl
Contributor II

Hello Victor, we are only using the web gui via https, but I can' t confirm that this issue didn' t happen with ssh. Sometimes the CLI is slow via SSH too. Also the CLI via the web gui is very very slow the most times. Traffic which is going through the FortiGate is not affected, at least we are not experiencing any performance problems in that way. Kind regards, Oliver
Victor
New Contributor III

Oliver: Thanks for the input. My experience as well concerning user traffic, but with one exception. If you are inspecting https traffic, ie. for webfiltering, you will find that bank sites may not work if the client is using ie7 or ie8 (the latter, only on XP). These server/client combos use a rare 128-bit encryption technology that the version 4 code does not like. Users end up with blank pages. I put the sites in a special policy that does not inspect https. I can also concur that management gui performance with any browser can be inconsistent. Sometimes the pages are displayed normally & others you are waiting 30 seconds or more for the page to show up. There is no rhyme or reason to it either. I could have slow management pages with traffic at 5Mbits and then again, pages could appear normally while my Fortigate cluster is handling 500Mbits of traffic. From the comments it looks like we have a wide range of platforms that span different asic chipsets. Again, have all who are experiencing this placed a call ticket with Fortinet. Victor
Labels
Top Kudoed Authors