Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available in FrFab FreeQ pool# 3

Hi All,

i see this message on my router(cisco 12410) Could you tell me what the meaning in this message ?

thank you.

SLOT 0:Oct 23 19:59:43 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:00:34 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(531) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:00:44 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(417) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:00:54 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:01:04 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(849) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:01:14 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(753) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:01:44 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1600) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:02:04 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1242) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:02:14 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1313) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:02:34 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1104) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:02:44 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(885) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:02:54 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1542) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:03:04 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1462) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:03:14 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(1230) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:03:24 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(369) are available in FrFab FreeQ pool# 3

SLOT 0:Oct 23 20:03:34 GMT+7: %EE48-3-QM_SANITY_WARNING: Few free buffers(511) are available in FrFab FreeQ pool# 3

5 REPLIES
Cisco Employee

EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available i


Hello,

Ususally this can be caused by oversubsription of particular link which trigger the buffer memory deplition. You need to see if particular interface getting High Rate of traffic and if pause frames grow there. Then sort that out understandbing why other side sending to much. Once it sorted route should be able to recover memory by itself.

Nik

Community Member

EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available i

Hello,

What the effect ? packet can transmit or drop.

and could your explain about interface forwarding algorithm ???

Thank you.

Cisco Employee

EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available i

So far some buffers are available - so no drops. Actually each port has it's own buffer and there is also sgared buffer for all ports. Whenever port buffer is full of packets waiting transmission it may request for more buffer space in that pool if available. And then stored waiting ofr its queue to go further or dropped if no buffer available or it is rate limited. I explain this in gerneral not specific to 12000 router and espicially to any of it's line cards. The particular realization for each LC, SIP, SPA can be different.

Nik

Community Member

EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available i

1. in this case i have many gigabit port for inbound traffic and only one pos interface for outbound traffic

    why when pos interface had been full buffer outbound traffic forward in gigabit port can not see input drop ?

2. in this case i have config CBWFQ outbound POS interface also it can help or not ?

Cisco Employee

EE48-3-QM_SANITY_WARNING: Few free buffers(1098) are available i

Hello,

1. Many interfaces for inbound and single interface for outbound can mean oversubscription. Each particular Gig interface can carry not much traffic to drop itself. But they total combined cause buffer starvation on POS. This is why POS can have problem and Gig can'not. Again it is just a guess traffic analysis should be done to be sure in it.

2. CBWFQ can help you to make sure - priority traffic will be sent first and will not be dependent of buffer starvation. Non-priority can be dropped if finally POS run out of buffers. I guess this is fine. However no buffer misses reported so far - only warning of few left.

Q: When did it start, can you correlate it to any event in your network (config change, HW/SW change, new application rollout)?

- Is it consistent  - I mean this error continue to appear regularly or now gone?

Nik

2361
Views
0
Helpful
5
Replies
CreatePlease to create content