mbruck, I just upgrade from firmware v2.80 to v3.00 build 8424,070322, and I am experiencing this right now.
where exactly did you look to re-enable syslog filters?
Before the update, obviously everything was working great, but to be on the safe side I backed up the config, and applied the update.
Should I re-apply my backup config? I didn' t do it because all of my policies and other misc settings were saved.
Thanks for the help, I' m really liking this release so far save for this syslog issue.
err .. EDIT: and 2 minutes later, I realize syslog was set to ALERT, instead of INFORMATION.
Ok, so NOW my question is, what would be the optimal setting? Notification, Information, Alert, Debug etc etc ?
Rick Payton, IT Support
Morikawa & Associates
http://www.mai-hawaii.com/
FortiGate-60 build 726 (retired)
FortiGate-60B v4.0 build 328 MR2 Patch 8
FortiAnalyzer-100B v4.0 build 513 MR3