[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-buglist
Subject:    [Buglist] [Bug 2075] unexpected behavior on ip-management policy for capsd
From:       bugzilla () opennms ! org (bugzilla at opennms ! org)
Date:       2008-06-26 15:29:28
Message-ID: 20080626152928.1F7CB7884DD () nen ! opennms ! org
[Download RAW message or body]

http://bugzilla.opennms.org/show_bug.cgi?id=2075


michael.seibold at gek.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael.seibold at gek.de




------- Comment #4 from michael.seibold at gek.de  2008-06-26 11:29 -------
If you have a large network and there are a lot of ip addresses which can't be
reached due to routing or firewall policies (provider address ranges p.e.) most
service scans will wait till timeout and this can take a while...

I think there sould be the possibility to define "do not scan" like you can
define "unmanaged".

Probably it's possible to do both, e.g. you can mark ranges for
"manage and scan"

"unmanage but scan" Just to know what the hell they put in your network
(always? Doesn't make sense only on initial scan or forced scan if you have the
last possibility)

"unmanaged don't scan"

Another idea is to create packages where you can use filters or "containers" so
you can define packages where only some services are scanned (infrastructure
ranges) and other packages where more services are scanned (server ranges) etc.

This will not only speed up discovery but also rescans etc.


-- 
Configure bugmail: http://bugzilla.opennms.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[prev in list] [next in list] [prev in thread] [next in thread]