First of all I wanted to take a moment to explain what this message means as it is one of the comman issue's with 6500s: This message just means that the SNMP queue is full and hence some packets are being dropped. Depending on the amount of data being polled, this is completely expected since SNMP is very low priority as it is just a monitoring tool. If too much SNMP traffic is building up, the device will drop these packets over any other more important data such as routing-switching traffic. Here are some basic steps to troubleshoot this issue: 1. There are known issues reported on 6500s. I have seen a lot of issue with 6500s and the CISCO-FLASH-MIB. A common workaround is to do a view to exclude this MIB. This is easy to do, the commands are the following: snmp-server view public-view ciscoFlashMIB excluded snmp-server view public-view ciscoSwitchEngineMIB excluded Now you have to remove your current community and have update them as per the view (change the <removed> with the community string configured) no snmp-server community <removed> view public-view RO no snmp-server community <removed> RO snmp-server community <removed> view public-view RO snmp-server community <removed> view public-view RO 2. Besides the common issues with the CISCO-FLASH-MIB is saw bugs such as CSCte66495 . You can access the bug details at the link below: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCte66495 Even though the bug description does not directly mentions the "%SNMP-3-INPUT_QFULL_ERR" message, but the issue is related to the error message. So, in many cases it is been observed that after upgrading to a fixed version, or implemented the workaround the "%SNMP-3-INPUT_QFULL_ERR” disappeared. 3. Another bug that seems to be related to this message is CSCtn19200 . Bug details can be seen below: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn19200 4. To be more certain of what exactly is the problem, we would have to collect a 'show stacks <snmp-engine pid>' output, but based on the evidence I believe the best course of action is to either upgrade to the IOS versions that contains the fix for the bugs I mentioned or implement the workaround.
... View more
How does the OID of RSSI : cDot11ClientSignalStrength (188.8.131.52.184.108.40.206.2220.127.116.11.1.3) CISCO-DOT11-ASSOCIATION-MIB creates an output like : 18.104.22.168.22.214.171.124.2126.96.36.199.188.8.131.52.184.108.40.206.220.127.116.11.0.23.224.9.109.224 The way to read the whole OID: The OID cDot11ClientSignalStrength is defined under the cDot11ClientStatisticTable. If you look at the table's description, you will find that the table has a 1 to 1 relationship with the cDot11ClientConfigInfoTable. The cDot11ClientConfigInfoTable (.18.104.22.168.22.214.171.124.2126.96.36.199), uses 3 indexes: -ifIndex (Integer) -cd11IfAuxSsid (Octet String (0..32)) -cDot11ClientAddress (OCTET STRING (6) - MAC Address) So now, you need to start trimming the OID values to find each index's value: -ifIndex = One value -cd11IfAuxSsid = Up to 32 values (On Octet Strings, the first value tells the length of the data) -cDot11ClientAddress = 6 values (MAC Address) Note for example the OID that you were trying to translate is something like: 188.8.131.52.184.108.40.206.2220.127.116.11.18.104.22.168.22.214.171.124.126.96.36.199.0.23.224.9.109.224 The first 188.8.131.52.184.108.40.206.2220.127.116.11.1.3, we already know that pertain to the OID cDot11ClientSignalStrength. After that we have a 1 that means that ifIndex equals 1. cd11IfAuxSsid: -Since the following number is 8, that means we need 8 additional values to get the actual value. - Number of positions = 8 - Values = 18.104.22.168.22.214.171.124 Since the "values" are Octet String, you need to translate each value to the character it represents in the ASCII table (in the following link you will find a very useful tool to do this: http://encodertool.com/octal You can just copy the whole number and paste it on the "Enter decimal ASCII here. Any non-numerical characters will be ignored" box. Once you translate it, the value obtained for the cd11IfAuxSsid is "hpbridge". And finally, you need to translate the remaining numbers from decimal to hexadecimal like in the following: cDot11ClientAddress = 0.23.224.9.109.224 (00-17-E0-09-6D-E0) Is better if you translate those numbers one by one. After doing that, you will be able to tell that the entry corresponds to Interface with ifIndex 1, using SSID "hpbridge" and a device with MAC address 00-17-E0-09-6D-E0 is connected to it.
... View more