Thanks, Ray.
That's what we were afraid of -- netmon only reads the seedfile when it
first starts or updated via the netmon -y/GUI. We want discovery to always
be on, so this is what I'm thinking:
1. Maintain a list of loopback addresses that are in the process of being
put on the network.
2. Write a script that pings these addresses every x minutes.
3. As soon as they are pingable, issue a netmon -y.
4. Rebuild the seedfile nightly to add/delete addresses from the list.
Not perfect, but will hopefully work 95%+ of the time. Thanks again!
Mark
--------------------------------------------------
(Lemire)>>If a device comes online sometime after Netview startup, will
>>netmon always prioritize using a seedfile address to discover
an object,over
>>and above its normal SNMP discovery process?
>Well it depends. First of all you have to have netmon configured to use a
>seedfile. If you have that, then it only reads it when it starts up, or
when
>you tell it to (by typing netmon -y on the command line or choosing
>Backup-Reread seed file (or some such) from the GUI Menu). If you have
>discovery on, and you are managing the network that contains the new
router, it
>will discover it. If you want to control this, turn discovery off, and
either
>use loadhosts to add the new router, or put it in the seedfile and run
netmon
>-y.
|