<div dir="ltr">Hi all and many thanks for all the replies.<div><br></div><div>Jeremy: I did the tcpdump as per the thread and found that the R= value was significantly less than the maximum 32 bit integer on some of the switches but negative on others. Censored, truncated output follows. How do we deal with the negative numbers?</div><div>---</div><div><div>06:35:54.584298 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 72)</div><div> 172.22.106.11.60150 > 192.168.78.254.snmp: { SNMPv2c C=public { GetRequest(28) R=-2032073048 .1.3.6.1.2.1.1.1.0 } }</div><div>06:35:55.153728 IP (tos 0x0, ttl 254, id 47570, offset 0, flags [none], proto UDP (17), length 335)</div><div> 192.168.78.254.snmp > 172.22.106.11.60150: { SNMPv2c C=public { GetResponse(287) R=-2032073048 .1.3.6.1.2.1.1.1.0="Cisco IOS Software, CGS2520 Software (CGS2520-IPSERVICESK9-M), Version censored, RELEASE SOFTWARE (fc1)^M^JTechnical Support: <a href="http://www.cisco.com/techsupport">http://www.cisco.com/techsupport</a>^M^JCopyright (c) 1986-2011 by Cisco Systems, Inc.^M^JCompiled sometime by prod_rel_team" } }</div><div>06:35:55.157010 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 78)</div><div> 172.22.106.11.60150 > 192.168.78.254.snmp: { SNMPv2c C=public { GetRequest(34) R=-2032073047 .1.3.6.1.4.1.9.9.109.1.1.1.1.5.1 } }</div><div>06:35:55.731062 IP (tos 0x0, ttl 254, id 47571, offset 0, flags [none], proto UDP (17), length 79)</div><div> 192.168.78.254.snmp > 172.22.106.11.60150: { SNMPv2c C=public { GetResponse(35) R=-2032073047 .1.3.6.1.4.1.9.9.109.1.1.1.1.5.1=5 } }</div><div>06:35:55.732084 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 74)</div><div> 172.22.106.11.60150 > 192.168.78.254.snmp: { SNMPv2c C=public { GetRequest(30) R=-2032073046 .1.3.6.1.4.1.9.2.1.2.0 } }</div><div>06:35:56.316063 IP (tos 0x0, ttl 254, id 47572, offset 0, flags [none], proto UDP (17), length 82)</div><div> 192.168.78.254.snmp > 172.22.106.11.60150: { SNMPv2c C=public { GetResponse(38) R=-2032073046 .1.3.6.1.4.1.9.2.1.2.0="power-on" } }</div></div><div>---<br></div><div><br><div>Nikolai: I'm a bit hesitant to apply patches like this so I'll exhaust all other avenues before looking at this.</div><div><br></div><div>Paul: Double checked Devmon's hosts.db and I can confirm the details are correct.</div><div><br></div><div>Thanks</div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 26, 2016 at 9:38 PM, Root, Paul T <span dir="ltr"><<a href="mailto:Paul.Root@centurylink.com" target="_blank">Paul.Root@centurylink.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Look in your hosts.db file, and see if the switches are identified as the proper template and that the community string is correct. The newer NX type switches
do not work with the old template.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Use snmpwalk/snmpget to pull some of the OIDs of the template.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Xymon [mailto:<a href="mailto:xymon-bounces@xymon.com" target="_blank">xymon-bounces@xymon.com</a>]
<b>On Behalf Of </b>Colin Coe<br>
<b>Sent:</b> Thursday, May 26, 2016 7:21 AM<br>
<b>To:</b> <a href="mailto:xymon@xymon.com" target="_blank">xymon@xymon.com</a><br>
<b>Subject:</b> [Xymon] Devmon tests clear but snmpwalk works<u></u><u></u></span></p>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi all<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I know this is the Xymon list not Devmon but I think I'll have most luck on this list so apologies in advance.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I have a few of Cisco switches that I've just started monitoring at a couple of remote sites. snmpwalk works from the Xymon server but the Devmon tests are all clear (Devmon runs on the Xymon server).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">When I look at the devmon.log I just see lots of <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">--- <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">[16-05-26@20:19:09] No SNMP data found for ifName on swi02<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">[16-05-26@20:19:09] No SNMP data found for ifOutPktsSec on swi02<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">[16-05-26@20:19:09] No SNMP data found for ifOutCollisions on swi02<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">--- <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Any ideas on tracking this down?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We have many if these switches at other sites and they display correctly in Xymon.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">CC<u></u><u></u></p>
</div>
</div>
</div></div></div>
<center>This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately
notify the sender by reply e-mail and destroy all copies of the communication and any attachments.</center>
</div>
</blockquote></div><br></div>