Following on from this, i would suggest trying to remove 'nightly inventory job' from this device if you have this set up or removing the node from NCM if its configured with this modul. I would remove the device from NCM then check back tomorrow
Hi and thanks for the quick reply.
I will check it out and send a reply.
Btw: Our Core Switch is a VSS system with 2 6500 devices. We read about the FW Bug, and we are planning to perform a FW update on our Cores soon.
Relating to this bug, in my opinion the messages should appear every time the Core Switch is being polled, not only every 24 hrs and 15 Minutes?
So Your idea with the nightly job sounds good to me.
Let´s see if it leads to success ;-)
I will spend a coffee then!
Well... no success. The traps messages are back, exactly 24hrs and 15 minutes after the last messages from yesterday.
Maybe there´s a general problem with Solarwinds Orion NPM and Cisco VSS?
Done a quick browse been abit tided up today
check this link out the Second one seems more legit
i actually think this is the solution at the moment for you seems to meet everything you've mentioned
Thanks, we tested everything, SNMPv1, all pollers off...Nothing was helpful.
The Solarwinds support told us to ask Cisco because it is a Cisco problem. Cisco told us to ask Solarwinds...
Well, we will perform the Cisco FW upgrade and then we´ll see if the problem disappears or not.
Thanks for your help!!!
This is what I through would happen, if the firmware resolves your issue post back just incase someone else gets the same issue:)
Good work dude
Yes, i will check back and post the results.
It is a known snmp response issue.
We are seeing it on our 3850, Sup2's on the 4500's..
It may be to the size of the response packets.
It does not appear that a fix is coming, putting the snmp filter in place will help clean up syslog, and also require us to reconsider our strategy how we use UDT and NCM jobs for inventory.
As I believe both hit these MIBs every poll cycle.
%SNMP-3-INPUT_QFULL_ERR when polling the CISCO-SWITCH-ENGINE-MIB
A Cisco 6500 generates the error message when polling the CISCO-SWITCH-ENGINE-MIB:
"%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full".
A supervisor 2t engine running 15.1(1)SY1 on cisco 6500 generates the error message " SNMP-3-INPUT_QFULL_ERR Packet dropped due to input queue full".
This issue has been found when the switch is added to Ciscoworks LMS and an inventory collection job runs. The job queries CISCO-SWITCH-ENGINE-MIB and the switch stops responding to the snmp and we can see SNMP-3-INPUT_QFULL_ERR Packet dropped due to input queue full in the logs of device.
Do a warm restart of SNMP ENGINE to get device respond to snmp request.
Create a snmp-server view blocking this portion of the mib tree or the CISCO-SWITCH-ENGINE-MIB.
snmp-server view cutdown iso included
snmp-server view cutdown 22.214.171.124.126.96.36.199.97 excluded
snmp-server community < your string here> view cutdown ROCustomer VisibleWas the description about this Bug Helpful?
Product:(1)Cisco Catalyst 6000 Series SwitchesSupport Cases:
Known Affected Releases:(2)15.1(1)SY1
Known Fixed Releases:(0)No release planned to fix this bug