there is a limit in the number of concurrent connections it can handle.
it appears the limit was reached. High numbers of web or X window users
could cause it (as this typically generates more than 1 concurrent
connection per user) A DoS could easly cause it. Donno what the max for
the DMZ is (3000 comes to mind), the XPRS is limited to 6000.... I'v been
messing with one and generated the same message while running some tests
-> 2048, which turned out to be a bug, it really meant 6144 (not that it
mattered). Anyway, Sonic recommended using the idle session timeout to
try and throttle the load. you can also generate, a dump called a
Technical Support Report, from the tools menu. Send it to Sonic
and they'll tell you what your current usage and high water mark was.
On Tue, 18 Jul 2000, Eric Carr wrote:
> Hi all,
>
> For some reason, after about 2 days uptime, my Sonicwall DMZ log starts
> filling up with "The cache is full; over 2048 simultaneous connections; some
> will be dropped" error messages, which ofcourse makes our
> connection-test-scripts flood us with error-report emails.
>
> Has anyone got an idea why "the cache is filled up" ? The load on the
> firewall is minimal at this time, but still..
> I'm running firmware v5.0.0 (most recent)...
>
> Regards,
> Eric
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
