It's probably related to either ARP or FDB tables.
You can run discovery by hand as Tom suggests and then disable the module causing the issues.
Next time you might think twice of buying shitty 3750s. (and using the pointless "stacking" crap, which basically has resulted in your 300 ports having a single, massively underpowered control plane cpu) :)
adam.
On Mon, 4 Mar 2013 10:02:04 -0500, Patrick Zaloum pzaloum@gmail.com wrote:
Hello I are testing Observium in a new environment after previous success
stories
elsewhere. We have noted that when we run device discovery on a stack of 5 Cat3750 (12.2-50-SE1) the "device" becomes unresponsive to any other queries / pings / ssh for approximately 5-6 minutes (during the discovery cycle).
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.
Total ports on the stack are 278 (no argument that it is a large number
of
ports to poll from a single device).
Regular polling of the device does not appear to have any consequences,
it
is specific to the discovery module.
Does anyone have any insight into this?
Thanks Patrick