cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2372
Views
0
Helpful
3
Replies

SNMP error %SNMP-3-INPUT_QFULL_ERR

dear

I m receiving the following error

%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full

%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full

%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full

%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full

%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full

 

how can I debug the cause of this error > and did any one face this and have a solution for it ?

 

regards

 

3 Replies 3

InayathUlla Sharieff
Cisco Employee
Cisco Employee

%SNMP-3-INPUT_QFULL_ERR will occur when snmp input queue is full. This happens when there are lot of snmp requests to the switch or when the SNMP process is not able to dequeue the packets from snmp input queue because of busy in processing the previous requests. This messages tells the user that there are bust of SNMP requests (device is polling very frequently) coming to the switch which SNMP process can't handle. User need to stop any SNMP queries to the device till it is recovered. We can avoid this by sending the packets with some duration between the requests (-t option in snmpwalk request)

You can see packet drops using the CLI "show snmp".

 

If there are bust of SNMP requests to the device, and device need to perform some lengthy operation on the request, then there are chances that queue can get full.

 

Can you please get the information on what are the SNMP operations are performing on this switch, like how frequently switch is poling using SNMP and which MIBs. 

 

HTH

Regards

Inayath

polling is happing each 120 sec , for mibs ... I think all mibs , no restriction is defined !!!

 

 

Please provide me with the following information:

-Show version
-Show snmp
-Show log

Also run:
-Show process show proc cpu sort | inc CPU|PID|SNMP ENG, for example:

CR-NMS-6500#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

285       79984    306358        261  1.03%  0.12%  0.07%   0 SNMP ENGINE

425           0         2          0  0.00%  0.00%  0.00%   0 SLB Main CPU pro

508         452    793494          0  0.00%  0.00%  0.00%   0 Max CPU utilizat

-Show stacks 285

I use 285 because it corresponds to the PID snmp engine of my device, when you run the "show stack" command and send me all the commands outputs.  We need a stack with more than 4 lines, four lines means that it is idle and we wont get the information that we require.

 

Claudio