On 6/15/07, Marc Irlandez <[EMAIL PROTECTED]> wrote:
If you select multiple networks, it should be processing the checked networks in the list. It processes each network serially; not in parallel. So you'll have to wait until the first one in the list is finished before getting to the rest of the networks. Depending on the number of pingable IPs and devices on a network it could take some time before one network is finished processing its discovery. If you are still seeing that only one network is being processed, make sure that the page has finished loading completely and send me the output.
Thanks for the reply. I think that what I'm seeing is the result of a totally different root issue. It seems that my scans never finish due to apparent lack of resources. I'm scanning class-C networks (up to 255 nodes). What I see happen in the monitor is that the IPs are emumerated and pinged pretty quickly, then one device or sometimes more are scanned, and then the process seems to hang. I'm watching my memory and it will go as high as I let it (I keep adding RAM to the VM). I'm going to start looking at logs and see if I can determine where the problem is coming from. Troubleshooting tips appreciated. Note: this is a brand new install. All I have to do to make it hang is install Zenoss, add a class-C network, then attempt to scan it. Restarting will temporarily resolve the perf issues but it keeps coming back. -- Psi webmaster (http://psi-im.org) im:[EMAIL PROTECTED] http://halr9000.com _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
