Solved: %SYS-2-INPUTQ in 2811 running 12.4(24)T2

alfredos · ‎02-17-2010

Hi,

I have a 2811 running 12.4(24)T2 full of these:

Feb 17 16:03:01.240: %SYS-2-INPUTQ: INPUTQ set, but no IDB, ptr=47255574, -Traceback= 0x4038B480z 0x43874C80z 0x43875A54z 0x41C633DCz 0x41C78890z 0x421D16A8z 0x4325C194z 0x4325AE1Cz 0x431A3D84z 0x41C77874z 0x41C78890z 0x43873F08z 0x40046B18z 0x4000FD88z 0x40011570z

They happen at irregular intervals, sometimes minutes, sometimes seconds, but only during business hours, i.e., it seems to depend at least partially on traffic.

Perhaps related, because no issues have happened to justify it, unexpected VRRP transitions:

Feb 17 15:57:53.074: %VRRP-6-STATECHANGE: Fa0/0.915 Grp 2 state Backup -> Master

Feb 17 15:58:02.854: %VRRP-6-STATECHANGE: Fa0/0.915 Grp 2 state Master -> Backup

This one happened not right after one of the %SYS-2-INPUTQ but 15 minutes later.

Should I worry much?

Is 12.4(24)T2 too broken? it's still the latest release out and, although it's ED, it's 3 months old and hasn't been deferred.

Giuseppe Larosa · ‎02-17-2010

Hello Alfredo,

error mesage decoder provides the following feedaback:

%SYS-2-INPUTQ:

INPUTQ set, but no IDB, ptr=[hex]

This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted.

Recommended Action: When reporting this condition, copy the message exactly as it appears, include the associated stack trace, on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.

after 15 minutes it is difficult to see a correlation

it is a SW bug

CSCtd75189 Bug Details

Error message %SYS-2-INPUTQ: INPUTQ set, but no IDB, ptr= on voice GW

Symptom:
Continuous error message similar to the one below are recorded on Voice GW with 12.4(24)T2

%SYS-2-INPUTQ: INPUTQ set, but no IDB, ptr=6818DA34, -Traceback=

Conditions:
Voice GW running 12.4(24)T2.

Workaround:
None currently. The fix will need to be integrated into the next 12.4(24)T release.

comment:

if you don't see any real issue you should be fine.

Hope to help

Giuseppe

View solution in original post

Giuseppe Larosa · ‎02-17-2010

Hello Alfredo,

error mesage decoder provides the following feedaback:

%SYS-2-INPUTQ:

INPUTQ set, but no IDB, ptr=[hex]

This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted.

Recommended Action: When reporting this condition, copy the message exactly as it appears, include the associated stack trace, on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.

after 15 minutes it is difficult to see a correlation

it is a SW bug

CSCtd75189 Bug Details

Error message %SYS-2-INPUTQ: INPUTQ set, but no IDB, ptr= on voice GW

Symptom:
Continuous error message similar to the one below are recorded on Voice GW with 12.4(24)T2

%SYS-2-INPUTQ: INPUTQ set, but no IDB, ptr=6818DA34, -Traceback=

Conditions:
Voice GW running 12.4(24)T2.

Workaround:
None currently. The fix will need to be integrated into the next 12.4(24)T release.

comment:

if you don't see any real issue you should be fine.

Hope to help

Giuseppe

alfredos · ‎02-17-2010

Thanks, that's the kind of feedback I was hoping for (especially the comment ).