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

SNMP-SW1-3-INPUT_QFULL_ERR

Hi all ,

I,m getting a error

==========================================

1760896: Nov  2 2015 11:34:21.231 UTC: %SNMP-SW1-3-INPUT_QFULL_ERR: Packet dropped due to input

queue full

1760897: Nov  2 2015 11:34:27.183 UTC: %SNMP-SW1-3-INPUT_QFULL_ERR: Packet dropped due to input

queue full

=============================================

and this impatc my production so can any tell me how to check which snmp mibs are in queue. 

3 REPLIES
Community Member

Hi 

Hi 

In order to verify waht is the problem with Q Full errors, please send me the show version of the device. 

you can check the OIDs being polled with the command : show snmp stats oid 

Best regards, 

Claudio Gonzalez 

Community Member

hi ,

hi ,

thanks for you reply , can you tell me how to trobleshoot such issue.

Issues

1.logs are generating 

==========================================

1760896: Nov  2 2015 11:34:21.231 UTC: %SNMP-SW1-3-INPUT_QFULL_ERR: Packet dropped due to input

queue full

1760897: Nov  2 2015 11:34:27.183 UTC: %SNMP-SW1-3-INPUT_QFULL_ERR: Packet dropped due to input

queue full

=============================================

2. Production get impacted 

I want to know which NMS tools are generating snmp reqest so that i can take necessary steps.

Community Member

Hi, 

Hi, 

In order to determine what exactly might be causing the clog in the SNMP engine, we need to gather an SNMP stack output while the issue is occurring. To gather this stack you need to do issue the below command:

CR-NMS-2811#show proc cpu sort | inc CPU|PID|SNMP ENG
CPU utilization for five seconds: 2%/0%; one minute: 1%; five minutes: 1%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
303 137304 51825 2649 0.00% 0.01% 0.00% 0 SNMP ENGINE

Then, using the PID you get in return (in my case 303) get an SNMP stack this way:

gin-pv0-har1# show stack 303
Process 153: SNMP ENGINE
Stack segment 0x4A0A9CCC - 0x4A0ACBAC
FP: 0x4A0ACAB8, RA: 0x41473078
FP: 0x4A0ACAF8, RA: 0x4127C8D8
FP: 0x4A0ACB70, RA: 0x4142AA74
FP: 0x4A0ACB88, RA: 0x4142AA60

The above stack with only 4 RA's means the engine is idle. You want to get several of these over 2 or 3 second intervals until you see a longer list of RA's and the list is repeating itself. This means it is stuck there.

I can decode that stack and check exactly where the problem is. You might just want to log a putty with all the outputs you get. I also need the full "show version" of this device to decode.

Looking forward to your reply, 

Claudio Gonzalez S

777
Views
5
Helpful
3
Replies
CreatePlease to create content