10-06-2013 01:21 AM - edited 03-07-2019 03:51 PM
HI,
I am getting error message on my 6509 switch console when i try to add the device in my cisco LMS server
%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
Below is snmp config
snmp-server view public-view iso included
snmp-server view public-view ciscoMemoryPoolMIB excluded
snmp-server community xxxxx RW
snmp-server host 172.16.1.100 version 2c xxxxx
snmp-server enable trap
Below is debug snmp output
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 172.16.1.100 on Vlan2
Oct 6 07:57:25: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 309, errstat 0, erridx 0
sysUpTime.0 = 378818380
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189825 = SNMP
clogHistoryEntry.3.189825 = 4
clogHistoryEntry.4.189825 = INPUT_QFULL_ERR
clogHistoryEntry.5.189825 = Packet dropped due to input
clogHistoryEntry.6.189825 = 378818380
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 172.16.1.100 on Vlan2
Oct 6 07:57:35: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 310, errstat 0, erridx 0
sysUpTime.0 = 378819380
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189826 = SNMP
clogHistoryEntry.3.189826 = 4
clogHistoryEntry.4.189826 = INPUT_QFULL_ERR
clogHistoryEntry.5.189826 = Packet dropped due to input
clogHistoryEntry.6.189826 = 378819380
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 127.0.0.91 on EOBC0/0
Oct 6 07:57:51: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 311, errstat 0, erridx 0
sysUpTime.0 = 378820925
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189827 = SNMP
clogHistoryEntry.3.189827 = 4
clogHistoryEntry.4.189827 = INPUT_QFULL_ERR
clogHistoryEntry.5.189827 = Packet dropped due to input
clogHistoryEntry.6.189827 = 378820924
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 127.0.0.91 on EOBC0/0
Oct 6 07:57:53: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 312, errstat 0, erridx 0
sysUpTime.0 = 378821125
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189828 = SNMP
clogHistoryEntry.3.189828 = 4
clogHistoryEntry.4.189828 = INPUT_QFULL_ERR
clogHistoryEntry.5.189828 = Packet dropped due to input
clogHistoryEntry.6.189828 = 378821124
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 172.16.1.100 on Vlan2
Oct 6 07:57:55: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 313, errstat 0, erridx 0
sysUpTime.0 = 378821381
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189829 = SNMP
clogHistoryEntry.3.189829 = 4
clogHistoryEntry.4.189829 = INPUT_QFULL_ERR
clogHistoryEntry.5.189829 = Packet dropped due to input
clogHistoryEntry.6.189829 = 378821380
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 127.0.0.91 on EOBC0/0
Oct 6 07:58:51: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 314, errstat 0, erridx 0
sysUpTime.0 = 378826924
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189830 = SNMP
clogHistoryEntry.3.189830 = 4
clogHistoryEntry.4.189830 = INPUT_QFULL_ERR
clogHistoryEntry.5.189830 = Packet dropped due to input
clogHistoryEntry.6.189830 = 378826924
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
KFH-DR-CORE-SW1#
6w1d: SNMP: Packet received via UDP from 127.0.0.91 on EOBC0/0
Oct 6 07:58:53: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input
queue full
KFH-DR-CORE-SW1#
6w1d: SNMP: Queuing packet to 172.16.1.100
6w1d: SNMP: V2 Trap, reqid 315, errstat 0, erridx 0
sysUpTime.0 = 378827124
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.189831 = SNMP
clogHistoryEntry.3.189831 = 4
clogHistoryEntry.4.189831 = INPUT_QFULL_ERR
clogHistoryEntry.5.189831 = Packet dropped due to input
clogHistoryEntry.6.189831 = 378827124
6w1d: SNMP: Packet sent via UDP to 172.16.1.100
10-06-2013 02:37 AM
Hi,
snmp-server view public-view iso included
snmp-server view public-view ciscoMemoryPoolMIB excluded
this looks like the workaround described in CSCsk27147.
Should be resolved in 12.2(33)SXI.
What IOS are you using?
Regards
Rolf
10-06-2013 04:00 AM
HI,
I am using
122-33.SXH8b
10-06-2013 09:04 AM
Salam Asim,
Few bugs and it is recorded on csc thread;
CSCsm80154 SNMP stops responding due to %SNMP-3-INPUT_QFULL_ERR
CSCto74586 SNMP - SNMP-3-INPUT_QFULL_ERR when using CISCO-ENERGYWISE-MIB
CSCti48279 %SNMP-3-INPUT_QFULL_ERR needs improvement
CSCth71681 SNMP-3-INPUT_QFULL_ERR, IPCTXERR, and/or CLC unresponsive in SCB
CSCsg60274 Snmp Engine stops responding - Error %SNMP-3-INPUT_QFULL_ERR
CSCtq48275 %SNMP-3-INPUT_QFULL_ERR generated after OIR operations
CSCtn19200 Catalyst6500 generate SNMP-3-INPUT_QFULL_ERR when receive IF-MIB.
What i mean from a genuine issue is when this error in syslog is just a symptom of other issue, like high CPU, device polled extensively or snmp engine not responding at all, etc.
The first thing to try to t/s this is to stop and start snmp engine:
To stop:
no snmp-server
To start:
Any snmp related command which was already configured before stopping snmp engine. You can see snmp configuration using show run | incl snmp-server.
If that does not fix the issue, next step is to take the traceback for SNMP ENGINE PID which i mentioned on last post. traceback can reveal any issue with snmp process.
Ref:https://supportforums.cisco.com/thread/2166321
HTH
Regards
Inayath
*Plz dont forget to rate the usefull posts.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide