Hi Patrick.<br><br>That&#39;s surely not supposed to happen. It&#39;s quite a number of ports, but certainly nothing that should be an issue, i poll larger stacks and people poll devices with thousands of interfaces.<br><br>I would try to check with the -d switch and see which queries lock it up, then report this to cisco as that&#39;s simply unacceptable.<br><br>If you know what causes it and you don&#39;t happen to need that info, you could disable that discovery module for those devices. That should help you out while cisco will treat your issue with utmost urgency and does the needful *cough*<br><br>Sent from my mobile, please excuse brevity and spelling errors.<br><br><div id="htc_header" style="">----- Reply message -----<br>From: &quot;Patrick Zaloum&quot; &lt;pzaloum@gmail.com&gt;<br>To: &lt;observium@observium.org&gt;<br>Subject: [Observium] Discovery of large stack causes hardware to become	unresponsive<br>Date: Mon, Mar 4, 2013 16:02<br><br></div><br><div dir="ltr">Hello<div style>I are testing Observium in a new environment after previous success stories elsewhere. </div><div style>We have noted that when we run device discovery on a stack of 5 Cat3750 (12.2-50-SE1) the &quot;device&quot; becomes unresponsive to any other queries / pings / ssh for approximately 5-6 minutes (during the discovery cycle). </div>

<div style><br>Once the discovery is complete, the poller, pings, and other operations return to normal. Note that traffic flow does not appear to be affected across the switch.</div><div style><br></div><div style>Total ports on the stack are 278 (no argument that it is a large number of ports to poll from a single device).</div>

<div style><br></div><div style>Regular polling of the device does not appear to have any consequences, it is specific to the discovery module.</div><div style><br></div><div style>Does anyone have any insight into this?</div>

<div style><br></div><div style>Thanks</div><div style>Patrick</div></div>