cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3136
Views
0
Helpful
10
Replies
simon.allen
Beginner

bgp_cpu2timeout message

Can anyone explain this message:

Mar 9 11:49:17.608 GMT: bgp_cpu2timeout: seconds: 7500, slot: 1 for 5: 11% and

1: 13%

I'm seeing it on a 2811 running 12.4(23) SP services. It suggests a CPU problem but a "show proc cpu history" shows the cpu util is ok.

I can't find any reference to it on the error message decoder or the output interpreter.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Harold Ritter
Cisco Employee

Simon,

This is a cosmetic bug and it should be fixed in the next 12.4 main line release.

Regards

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

View solution in original post

10 REPLIES 10
Giuseppe Larosa
Hall of Fame Master

Hello Simon,

how many prefixes are on the BGP table?

have you configured some specific route filters ?

the message hasn't the IOS message format so this is a message that comes from an IOS routine/code

Is it appearing many times and have you seen impacts on routing ?

Hope to help

Giuseppe

Harold Ritter
Cisco Employee

Simon,

This is a cosmetic bug and it should be fixed in the next 12.4 main line release.

Regards

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Ok, thanks for your help

Still showing up in 12.4(25) running on an NPE-400 (512MB RAM) in a 7204VXR.

Not even taking a full BGP table on this router. Just the 1 to 2 hop routes and some peering. 2 x 30K routes from the border routers.

Shows up every couple of minutes.

May 24 17:42:22: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 17% and 1: 17%

May 24 17:46:22: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 16%

May 24 17:46:53: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 14%

May 24 17:47:47: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 17:48:17: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 17:50:46: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 17:51:16: bgp_cpu2timeout: seconds: 7500, slot: 1 for 5: 15% and 1: 16%

May 24 17:51:48: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 17:52:36: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 17:54:11: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 17:54:42: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 13%

May 24 17:55:12: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 14%

May 24 17:56:57: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 18:00:01: bgp_cpu2timeout: seconds: 7500, slot: 1 for 5: 15% and 1: 16%

May 24 18:00:10: bgp_cpu2timeout: seconds: 7500, slot: 1 for 5: 15% and 1: 16%

May 24 18:03:07: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 16%

May 24 18:03:37: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 16%

May 24 18:04:16: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 16%

May 24 18:04:46: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 16%

May 24 18:19:34: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 17% and 1: 16%

May 24 18:20:05: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 17% and 1: 15%

May 24 18:21:21: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 17% and 1: 14%

May 24 18:21:52: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 14%

May 24 18:22:29: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 15%

May 24 18:23:38: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 15%

May 24 18:24:08: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 14%

May 24 18:24:39: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 15%

May 24 18:32:47: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 15% and 1: 15%

May 24 18:33:20: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 13%

May 24 18:33:50: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 14%

May 24 18:34:20: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 14%

May 24 18:35:39: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 14%

May 24 18:36:09: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 14%

May 24 18:36:41: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 14%

May 24 18:37:20: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 13%

May 24 18:37:51: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 14% and 1: 14%

May 24 18:40:01: bgp_cpu2timeout: seconds: 7500, slot: 1 for 5: 15% and 1: 17%

May 24 18:42:11: bgp_cpu2timeout: seconds: 7500, slot: 1 for 5: 16% and 1: 17%

May 24 18:42:20: bgp_cpu2timeout: seconds: 30000, slot: 3 for 5: 16% and 1: 16%

Strange that there isn't anything in bugtoolkit (at least not anything that's viewable by non internal...)

j.samanta
Beginner

I am also seeing the same message on 12.4(23) when I enable aggregate route on this router. Anybody can explain this? I am not seeing any reference to this in Cisco website.

So if its a cosmetic bug can we safely ignore it and say there is no impact to router/routing becoz of this?

I raised a TAC case as well as posting a the original question here , and the TAC confirmed that it is a cosmetic issue. An internal debug message was left enabled in the code.

They were expecting it to be fixed in the next main release which would have been 12.4(25) but I've seen it again in 12.4(25). I'll re-open the case and see what the response is.

Simon,

From what I can see, this fix will be part of 12.4(23a), which is targeted before the end of the month.

Regards

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

It looks like it's fixed in 12.4(25a) for the 7200 and others, but they forgot to do an RSP/7500 release of that code (again)... May be they will upload it later if someone inside cisco remembers.

Hello Simon,

What was the TAC response ? And what is the Bug Id associated with this issue ?

Thanks.

Regards,

Antonio Soares

Hi Antonio,

This is what the TAC engineer told me:

"The one you observed is a cosmetic issue, since it was an internal debug message that remained enabled even without any specific debugs activated.

Nothing to worry about then, as confirmed by the developers. It will be fixed in the next releases, though there's no official bug id for this yet"

We upgraded our 2811s to 12.4(25a) and the bug is fixed in that version, although this may not be the case for all platforms.

Regards, Simon Allen