Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) AP24 Bug [ small ]


 To better track pool leaks, Try the following command:


TNT3#pool addrQ


Pool Name                         size  limit  inUse  hiWat  heapAdrs
addrQueue                          12     0     284    292   103C55E0

Buffers for pool:
count =   284: Stack        0        0        0        0

                      heapAdrs  size  # buffers  # segments
                      103C55E0     1        119         119
TNT3#


If you see the hiwater mark exceed you pool base count, Then you can
easily blame address leaks, (Which by chance we having been seeing
here for some time) We usually have to bounce the boxes once every
4 days. We have been working with Ascend engineering to fix this
for awhile now.


Jason Nealis
Director Internet Operations
Network Access
Erols Internet


On Thu, 22 Jan 1998, Martin Hannigan wrote:

> 
> Don't know if this is a known bug, but it's a bug, apparently.
> 
> admin> ip-p
> 
> Pool#                Base         Count      InUse
>    1                209.6.78.1     254         42
> 
>  Number of remaining allocated addresses:    0 
> 
> 
> I am not seeing the pool server leak issue, but I am seeing a failure
> of the counter to increment/decrement. Not a big issue, but can 
> any confirm this? 
> 
> 
> 
> Regards,
> 
> --
> Martin Hannigan                       hannigan@xcom.net
> Director of Data Networks             V:617.500.0108
> XCOM Technologies, INC.               F:617.500.0002
> The Leading Carrier for ISP's         http://www.xcom.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>
> 

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