Re: (ASCEND) Problem with connecting Solaris Box.

["Oliver J. Albrecht" <oj@nexus.flensbone.net>]

In article <19980408185523.40527@ibh-dd.de> Andre Beck wrote:

[...]
>it is still up. Ascend Support has visited the Max closely and took a lot
>of data. One thing we found out immediately is that 6.0.x up to .2 has a
>leak in the filter code, causing filterEntry to grow without bounds. Just
>have a look into the debug mode, command "pools". We assume that the
>problem could be cause by filters, we have one one practically every profile.

That would confirm the memory leak we were seeing with 6.0.0. on our Max 4000. 
Pools -v dropped below 700K after two days and we went back to 5.0Ap4X.
We're using filters for a high percentage of our users as well. FWIW, the 
Max 2000 appears to be immune, we installed 6.0.0 the day it was released 
and there are no signs of a memory leak whatsoever (same filters). There are 
no other obvious problems either, like broken routing and/or RIPv2 problems...

-- 
Oliver J. Albrecht <oj@nexus.flensbone.net>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

Follow-Ups:

• Re: (ASCEND) Problem with connecting Solaris Box.
• From: Andre Beck <beck@ibh.de>

---

• Prev by Date: Re: (ASCEND) V.90 Status?
• Next by Date: Re: (ASCEND) V.90 Status?
• Prev by thread: Re: (ASCEND) Problem with connecting Solaris Box.
• Next by thread: Re: (ASCEND) Problem with connecting Solaris Box.
• Index(es):
  • Main
  • Thread