cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5873
Views
0
Helpful
2
Replies

exceeds data buffer size discarding this snmp request

Morning

Cisco Prime LMS 4.2.3 is sending SNMP request too big for asa interface buffer.

LMS is running on Windows server

incoming SNMP request (528 bytes) from IP address x.x.x.x  Port  50592  Interface "inside" exceeds data buffer size, discarding this SNMP  request.

212005: incoming SNMP request (%d bytes) from %s exceeds data buffer size, discarding this SNMP request.

It is very much like this error

Error Message    %PIX-3-212005: incoming SNMP request (number bytes) on interface 
interface_name exceeds data buffer size, discarding this SNMP request.

Explanation    This is an SNMP message. This message reports that the length of the incoming SNMP  request, destined for the firewall, exceeds the size of the internal data buffer (512 bytes) used for  storing the request during internal processing; therefore, the firewall is unable to process this request.  This does not affect the SNMP traffic passing through the firewall via any interface.

Recommended Action    Have the SNMP management station resend the request with a shorter length,  for example, instead of querying multiple MIB variables in one request, try querying only one MIB  variable in a request. This may involve modifying the configuration of the SNMP manager software.

how do I change the SNMP request size in LMS?

I can only find the following that might be an option

http://blogs.technet.com/b/mihai/archive/2012/05/14/reducing-the-maximum-number-of-oids-queried-in-a-single-batch-in-om-2012.aspx

any thoughts on the matter would be appreciated

just using default settings with snmpv3

2 Replies 2

Bug in lms 4.2.3

CSCtj88629            Bug Details

SNMP packet size requests from LMS is too large
Symptom:
LMS sends more than 512 SNMP requests to the FWSM, so it rejects the requests.

Conditions:
This occurs with FWSM and ASA's.

Workaround:
None.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtj88629

We have the same issue with Firewalls that are running 9.1.2 or below code. We recently upgraded 2 of our firewalls to 9.2.3 then pushed SNMPv3 on all including these firewalls from Prime 2.2 and only these 2 upgraded firewalls are synced up with Prime without any issues. So this means that this issue has been fixed in version 9.2.3

Thanks,

PK

Review Cisco Networking for a $25 gift card