01-13-2003 01:09 AM - edited 03-02-2019 04:07 AM
Hi,
I have a customer with CiscoWorks LMS 2.1 installed on W2K. They have numerous Cat4000's in their network. When CiscoWorks does a discovery on a fully populated Cat4000's it stops halfway and continues to the next switch. In the Cat4000s logs it brings up a message UDP Packet Overflow. Any ideas why this would happen, could it be a problem on the switches or in CiscoWorks.
Thanks,
Maretha
Solved! Go to Solution.
01-14-2003 11:27 AM
This situation is documented in
http://www.cisco.com/warp/public/473/34.shtml#UDP_SOCKET_OVERFLOW
and typically means there is too much snmp polling going on for a CatOS device, and tends to show up more often on those with high port densities.
Also look at CSCdx83292: which is relative to CiscoWorks/CMF 2.1 -
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdx83292
This actually addresses the issue of CiscoWorks causing the messages and drops. It has not been resolved yet.
01-13-2003 10:34 AM
What is the exact message that shows up in the Cat4K log related to UDP?
01-14-2003 12:04 AM
Hi,
I've just received similar syslog message:
2003 Jan 13 19:30:25 CET +01:00 %IP-3-UDP_SOCKOVFL:UDP socket overflow from Source IP: 10.2.1.61, Destination port: 161
The source is my HP OV NNM machine.
So it seems to be a general SNMP management problem, not just a CiscoWorks one.
Regards,
Milan
01-14-2003 11:32 AM
You can use the CCO Error Message Decoder Tool:
http://www.cisco.com/cgi-bin/Support/Errordecoder/home.pl for this.
01-15-2003 06:56 AM
Hi,
The message is: Nov 08 03:27:17 GMT+2 +02:00 %IP-6-UDP_SOCKOVFL:UDP socket overflow from Source IP: 10.100.3.33, Destination port: 161
Maretha
01-14-2003 11:27 AM
This situation is documented in
http://www.cisco.com/warp/public/473/34.shtml#UDP_SOCKET_OVERFLOW
and typically means there is too much snmp polling going on for a CatOS device, and tends to show up more often on those with high port densities.
Also look at CSCdx83292: which is relative to CiscoWorks/CMF 2.1 -
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdx83292
This actually addresses the issue of CiscoWorks causing the messages and drops. It has not been resolved yet.
01-15-2003 04:24 AM
I'm having a similiar situation with Aironet 350 access points. They stop responding to our NMS (ping, http, and telnet checks) during discovery. When we reduce ANI Server Discovery CPU allocation, the number of AP's not responding is reduced, but still a problem for a few.
Is there something in CW2k that can be adjusted other than the CPU Usage Allocation?
01-16-2003 10:48 AM
HI the documentation helped thanks, they had another server sending SNMP traps on thier network - this was causing the problem.
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