I sent this to Cambium Support, but maybe someone here has seen the same? The more I try to use WM the more I dislike it.
I am trying to troubleshoot why a new network range is not being discovered in Wireless Manager. I figured out that I had the wrong version of SNMP selected, but now it doesn’t appear to be rescanning the subnet at the specified interval (900 seconds).
I had 3 PMP 320 SMs that have been stuck in a “Discovering” state for weeks, they seem to be working fine and I have no idea what this state means or what the problem is. I had an idea to “unmanage” these devices so that no more nodes will be in a discovering state, so maybe the subnet scan can continue… but no success:
[02 Aug 2012 12:16:25:025] DISCOVERY_TIMEOUT_QUEUE(146): Deep Discovery is still running for 4 devices. This loop skipping.
[02 Aug 2012 12:16:44:446] STATE MANAGEMENT: 172.20.21.21:637: Management state changed to Unmanaged state.
[02 Aug 2012 12:16:46:990] STATE MANAGEMENT: 172.20.21.24:641: Management state changed to Unmanaged state.
[02 Aug 2012 12:16:50:870] STATE MANAGEMENT: 172.20.21.7:643: Management state changed to Unmanaged state.
[02 Aug 2012 12:17:25:037] DISCOVERY_TIMEOUT_QUEUE(146): Deep Discovery is still running for 4 devices. This loop skipping.
[02 Aug 2012 12:18:25:050] DISCOVERY_TIMEOUT_QUEUE(146): Deep Discovery is still running for 4 devices. This loop skipping.
[02 Aug 2012 12:19:25:062] DISCOVERY_TIMEOUT_QUEUE(146): Deep Discovery is still running for 4 devices. This loop skipping.
[02 Aug 2012 12:20:25:072] DISCOVERY_TIMEOUT_QUEUE(146): Deep Discovery is still running for 4 devices. This loop skipping.
What is Deep Discovery? How do I found out what devices it’s running on? Why is it still running after a week? What does this message even mean?
we had the same Problem,1500 sm are always discovering…they cannot resolve it… we had contact with india and they can´t resolve the Problem.
I’ve spent the last few months waiting on their India support team, finally the guy’s applied a patch and I got him remote access to the server, no response yet…
Apparently the patch that debugs this behaviour also stops it?
Try not service Pack for WM4 it will fix the Problem
Nice, that looks to be brand new. Actually one of the developers installed a patch on our system and it has been fine since. I assume that this patch is the same fix in SP2, but I will be applying it nonetheless
Cheers