15
SonicWALL Scrutinizer 9.0.1 Release Notes
P/N 232-000861-00 Rev A
Known Issues
This section contains a list of known issues in the Scrutinizer 9.0.1 release.
Symptom
Condition / Workaround
MFSN report for some sFlow devices will occur
even though no flows are being lost. This can
happen if multiple subagents exist on a single
sFlow exporter
Fix coming in a future release.
Flow Analytics can cause the server to page
memory to disk and slow down the user
interface. Generally, occurs on underpowered
machines.
Disable the following algorithms:
• Top Countries
• Internet Threats Monitor
• DDOS Violations
• Nefarious activity
When initially evaluating SonicWALL Scrutinizer
the interface is slow and many interfaces don’t
immediately appear.
If installing Scrutinizer on a machine that is
already receiving flows from > 50 devices,
Scrutinizer will need an extra 5 minutes to crunch
the data and display all that it is receiving.
The interface of SonicWALL Scrutinizer is very
sluggish and / or the collector may fail and need
to be restarted.
The performance of Scrutinizer is dependent on
processing power of the machine it is installed on.
NOTES:
• VMware is often not a good platform
• SAN storage can be slow
• Turn Anti-virus off or exclude the
Scrutinizer directory
Multiple CPUs mislabeled in Vitals Summary
Fix coming in a future release.
Loading a single report in Scrutinizer consumes
roughly 90MB-95MB of memory.
Solution being considered. Possibly addressed in
future release. Currently functioning as designed.
Issues displaying SonicWALL Scrutinizer in
Internet Explorer v6
Internet Explorer v6 is no longer supported.
Please use Internet Explorer v7 or newer. The
latest version of any browser is highly
recommended.
Bad formatting in report type when no data is
available.
Fix coming in a future release.
Pie Charts error with "Graphing Error: No data
for selected period" when results are zero.
Fix coming in a future release.