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

Traffic statistics wrong

Hi All, Anyone else having issues with the traffic counters on FortOS 5.0.7? Counters in the " traffic history" widgets are all completely wrong except one interface. also when polling interface statistics using SNMP i get wrong values.

- MBR -

NSE1, NSE2, NSE3

FGT60D/E, FWF60D/E, FGT200D

- MBR - NSE1, NSE2, NSE3 FGT60D/E, FWF60D/E, FGT200D
12 REPLIES 12
ede_pfau
SuperUser
SuperUser

Not with me. But von 5.2.0 there seems to be similar displays: https://forum.fortinet.com/FindPost/111762

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Brady_R__Houser
New Contributor

I' m also running 5.0.7. My Interface History shows bytes being transmitted. I know that my 100+ users aren' t using the Internet. I' m only monitoring for security alerts, do you think this could be the cause?
MBR
New Contributor III

Support told me the problem should be fixed in 5.0 patch 9 so you could try it. I hope to schedule the upgrade anytime soon.

- MBR -

NSE1, NSE2, NSE3

FGT60D/E, FWF60D/E, FGT200D

- MBR - NSE1, NSE2, NSE3 FGT60D/E, FWF60D/E, FGT200D
Istvan_Takacs_FTNT

That is strange MBR if they told you that.... 5.0.9 only has 1 patch for a completely different issue. What actually you have to do after the installation of 5.0.9 is to reset all your reports which might fixes the issue if the DB got corrupted. But it' s not really a fix, only a workaround and you will lose all your statistics, too. Here' s the section from the release notes; Reports Before you run a report after upgrading to v5.0 Patch Release 9, you must enter the following CLI commands: execute report-config reset This will reset report templates to the factory default. All changes to the default report will be lost! Do you want to continue? (y/n)y Report configuration was reset to the factory default. execute report recreate-db This will recreate the report database from the log database. Do you want to continue? (y/n)y Request to recreate report database is successfully sent.
Brady_R__Houser

Do you know if doing a reset with 5.0.7 will resolve the issues? Upgrading the firmware of our production environment is going to be a hard sell when all it does is fix reporting.
Istvan_Takacs_FTNT

It not only fixes the reporting (actually the fixes for reporting have nothing to do with this particular issue), but applies many patches in 5.0.8 on the firewall and on 5.0.9 only a single security patch made it into the release. I would highly recommend to update the production, public-facing server and don' t keep running on 5.0.7 due to the number of open issues you have with fixes already available. You can upgrade straight to 5.0.9 from 5.0.6 or later, you don' t have to go through each patches one by one. But since it can be problematic to organise a maintenance window for the upgrade and reboot, the suggested DB rebuild might have a chance to fix the reporting issue. Bear in mind though that you will most likely lose all your collected stats and will start from scratch again.
Brady_R__Houser
New Contributor

I' ll have to plan doing the upgrade. The reset of the db and stats didn' t fix it.
Brady_R__Houser
New Contributor

I can confirm that after we performed the upgrade to .09, the web traffic reporting started to work correctly.
MBR
New Contributor III

Hi Brady, Thanks for sharing! I' ll hope to schedule the update soon

- MBR -

NSE1, NSE2, NSE3

FGT60D/E, FWF60D/E, FGT200D

- MBR - NSE1, NSE2, NSE3 FGT60D/E, FWF60D/E, FGT200D
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors