As far as I understand TME NetView is NOT applying ping sweep mechanisms for 
node
discoveries, neither for :
        1. Automatic new node discoveries nor for
        2. Seed file discoveries (address ranges or wildcards are used as 
filters).

So network components having an IP address but not using it for communication 
will
not be discovered unless implicitely defined in the seed file. So what to do in 
the
following (theoretical) cases:

        1. Bridges operate on Layer 2, some of them have an IP address such that
they can be managed using SNMP. However if the SNMP agent has nothing to report 
for
e.g. a time longer then the ARP flush time of its communication partners, 
NetView
will not be able to discover such a bridge unless its IP address is implicitely
listed in a seed file. But I don't like the issue that I have to update my seed 
when
I add such a bridge for example.

        2. A hot standby system which is not supposed to communicate unless its
detects an outage of the main system for which it acts as standby.

So I guess to solve such a kind of problems I have two possibilities:
        1. Use the seed file.
        2. Use a script file (or whatever) performing a (limited) ping sweep (= 
just
trying IP addresses in a certain range) at regular intervals from the management
station. I know this is quite constly in terms of band-width and execution time.

--
-----------------------------------------------
- Marco Mommers                               -
-       Eurocontrol Maastricht UAC            -
-       Engineering division                  -
-       Horsterweg 11                         -
-       NL-6191RX Beek (l)a                   -
- Work : Phone : +31 (0)43 3661 376           -
-        Fax   : +31 (0)43 3661 300           -
-        email : marco.mommers AT eurocontrol DOT be -
- Home : Phone : +31 (0)43 3540 080           -
-        PC    : +31 (0)43 3540 041           -
-        email : mommers AT cobweb DOT nl            -
-----------------------------------------------