[c-nsp] %IPC-5-WATERMARK: What is this?

[e ninja]

Max,

Ignore my last post. Are there any mallocfails? if yes, this might be as a
result a memory leak in the IPC buffer addressed in CSCek64188 resolved in
12.2(18)SXF8.

-----

CSCek64188

Symptoms: An error message indicating memory leak and pending transmission
for IPC messages is displayed as follows:

*Dec 3 01:31:31.792: %IPC-5-WATERMARK: 25642 messages pending in xmt
for the port
Primary RFS Server Port(10000.C) from source seat 2150000

 *Dec 3 01:32:01.489: %SYS-2-MALLOCFAIL: Memory allocation of 4268
bytes failed from
0x9F32944, alignment 32

 Conditions: This issue is triggered by CSCeb05456 and is applicable only if
your Cisco IOS image has integrated the fix of CSCeb05456.

Workaround: Periodically, reload the router so that the IPC buffer pool will
be reinitialized.
------

Note that your current IOS image has the fix for CSCeb05456 (fixed in
12.2(18)SXF1
- the trigger for this issue


/eninja



On Sun, Mar 2, 2008 at 2:16 PM, e ninja <eninja at gmail.com> wrote:

> Max,
>
> This is a sev 5 notification message. As such, it is nothing to be worried
> about. From cco....
>
> *Error Message   *IPC-5-WATERMARK: [dec] messages pending in [hex] for the
> port [chars] [hex].[hex]
>
>    *Explanation   *This message indicates that a particular IPC port is
>    overused. An application is not draining packets quickly, which suggests
>    that the CPU is very busy. [dec] is the number of messages pending in the
>    IPC to be processed by the application. [chars] is the IPC port name. The
>    first [hex] is the IPC port number, the second [hex] is the IPC seat number,
>    and the third [hex] is the IPC index.
>
>    *Recommended Action   *No action is required.
>
>
> /eninja
>
>
>
> On Fri, Feb 29, 2008 at 9:43 PM, Max Clark <max.clark at gmail.com> wrote:
>
> > %IPC-5-WATERMARK: 1627 messages pending in xmt for the port Primary
> > RFS Server Port(10000.A) seat 10000
> >
> > I have not found a good explaination for what this is, what causes it,
> > and how to resolve it - or if it's even something to be concerned
> > about. Can anyone share some more information for what this is?
> >
> > This is from a 6509 Sup 720 3BXL running
> > s72033-adventerprisek9_wan-mz.122-18.SXF3.bin.
> >
> > Thanks,
> > Max
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
>