I have seen the same messages recently on several slots after TE tunnels flap, but they caused a lot of issues (FIA errors, CEF disable and so on).
%EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in ToFab FreeQ pool# 3 %EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in ToFab FreeQ pool# 1 %EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in ToFab FreeQ pool# 1 ToFAB BMA information Number of FreeQs carved 3 Pool 1: Carve Size 94155: Current Size 0 Pool 2: Carve Size 57539: Current Size 0 Pool 3: Carve Size 109848: Current Size 0 IPC FreeQ: Carve Size 600: Current Size 599 Number of LOQs enabled 2048 LOQ/OQ 1408: Current Size 261540 Q 0x580: Head 135076, tail 124292, length 261540 %EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in ToFab FreeQ pool# 1 %EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in ToFab FreeQ pool# 1 %EE48-3-QM_SANITY_WARNING: Few free buffers(0) are available in ToFab FreeQ pool# 1 Dumping the head 135076 34908 0x3299EE80 364 Dumping the tail 124292 149241 0x327F9A80 52 %EE48-3-QM_SANITY_WARNING: ToFab FreeQ buffers depleted. Recarving the ToFab buffers %EE192-3-BM_QUIESCE: Rx FIM/LIM failed to go idle. Value: 0x50000000 -Traceback= 400312FC 4063DD24 4063DE50 40648B48 40648BAC 40636B08 40B13274 403CAC4C 40107ED4 400AF4A0 400DB2F4 400DB2E0 The version is 12.0(33)S6 and the modules are Engine 5... It seems a bug. What would cause this? -----Mensagem original----- De: [email protected] [mailto:[email protected]] Em nome de Oliver Boehmer (oboehmer) Enviada em: terça-feira, 3 de agosto de 2010 02:51 Para: Drew Weaver; [email protected] Assunto: Re: [c-nsp] Odd error after Interface flap [GSR/Engine 5] Hi, > One of our upstream providers had an interface flap for about 10 seconds. > > After the Interface came back up and before the BGP session came up this > message was logged: > > SLOT 5:Aug 2 14:43:36 EDT: %EE48-3-QM_SANITY_WARNING: Few free buffers(10) > are available in ToFab FreeQ pool# 1 > ... > Has anyone seen this error before/know what it could indicate? > > Everything seems to be back to normal now, just making sure that isn't cause > for high alarm. this is a relatively new msg for E5 (via CSCsr99615, was around for E3 a bit longer), which reports low buffer conditions in LC buffer pools. As long as it doesn't pop up more often, it only reports a transient condition and can be ignored. The check can be adapted/disabled via "[no] hw-module slot <n> qm-sanity ..." command.. oli _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
