Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: ND2 remote polling Engine without own database
(Oliver Gorwits)
2. Re: ND2 remote polling Engine without own database
(Oliver Gorwits)
3. Re: ND2 remote polling Engine without own database (Oliver B?hrig)
--- Begin Message ---
Hi Oliver
On 2018-02-22 07:09, Oliver Bührig wrote:
I am looking for a way to poll some network devices (macksuck) with a
differnd polling interval like all other devices.
Is it possible ?
That's a very interesting question! It's not an immediately configurable
setting, but I think the effect can be achieved. You've also not said
whether you mean higher or lower interval than default, and how many
devices are affected. I'll give some options...
We have the macsuck_min_age setting which controls "the minimum amount
of time in seconds which must elapse between any two macsuck jobs for a
device". If you want to *increase* the interval, you could set this to
higher than 3600 (the default schedule interval for macsuck).
To limit this to specific devices, you will need to run a second poller
on another system (well done for working this out!). Configure the
second poller with:
schedule: null # to disable the scheduler
discover_no: 'any'
arpnip_no: 'any'
macsuck_only: 'set-of-devices-with-different-interval'
On your main poller you could have a corresponding:
macsuck_no: 'set-of-devices-with-different-interval'
If instead you want a shorter interval, macsuck_min_age will not work
because it defaults to zero anyway. For that, you invert the behaviour:
set the scheduler on your main poller to lower the re-schedule interval:
schedule:
macsuck:
when: '15,45 * * * *' # twice an hour
and set the main poller to hourly macsuck interval:
macsuck_min_age: 3600
(remove the setting of macsuck_min_age on your secondary poller so it
reverts to "0" which means ASAP).
At the end of the day, your job queue WILL be a mess, but by controlling
the configuration settings above, the pollers will behave intelligently
and you will have the correct effect after all, so don't worry about the
queue too much.
I hope this helps!
regards,
oliver.
Maybe with a 2nd host as remote poller, which use the database from
the 'main' poller ?
Netdisco version is 2.39.7.
I made some tests on a development system, but I saw a lot of jobs in
the job queue which never been configured from my side. When I stopped
netdisco-backend on one host, so only one poller is active, it 's
looks fine. (also from remote polling host). The configured polling
data was send to the database on the 'main' netdisco hosts.
Any ideas or solutions ?
Thanks,
Regards
Oliver Buehrig
--
Deutsches Elektronen-Synchrotron
IT-Kommunikationsnetzwerke
Notkestr. 85
22607 Hamburg
Germany
Tel. : +49 40 8998 2622
Fax : +49 40 8994 2622
E-Mail: oliver.bueh...@desy.de
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Oliver
I realised with a minor patch, Netdisco could make this a bit easier
too:
I have allowed the netdisco-do CLI tool to have an --enqueue option,
which will add the job to the backend queue instead of executing
immediately. If your devices with a different timing are within an IP
prefix this becomes even better. In your crontab:
15,45 * * * /home/netdisco/bin/netdisco-do macsuck -d 192.0.2.0/29
--enqueue --quiet
This will run two times an hour for those devices, and only output
errors. No need for a second backend poller.
(It would be nice if this could be done from the "schedule" config, but
right now you can only have one macsuck setting within schedule.)
Hope this helps!
Oliver.
On 2018-02-22 20:08, Oliver Gorwits wrote:
Hi Oliver
On 2018-02-22 07:09, Oliver Bührig wrote:
I am looking for a way to poll some network devices (macksuck) with a
differnd polling interval like all other devices.
Is it possible ?
That's a very interesting question! It's not an immediately
configurable setting, but I think the effect can be achieved. You've
also not said whether you mean higher or lower interval than default,
and how many devices are affected. I'll give some options...
We have the macsuck_min_age setting which controls "the minimum amount
of time in seconds which must elapse between any two macsuck jobs for
a device". If you want to *increase* the interval, you could set this
to higher than 3600 (the default schedule interval for macsuck).
To limit this to specific devices, you will need to run a second
poller on another system (well done for working this out!). Configure
the second poller with:
schedule: null # to disable the scheduler
discover_no: 'any'
arpnip_no: 'any'
macsuck_only: 'set-of-devices-with-different-interval'
On your main poller you could have a corresponding:
macsuck_no: 'set-of-devices-with-different-interval'
If instead you want a shorter interval, macsuck_min_age will not work
because it defaults to zero anyway. For that, you invert the
behaviour: set the scheduler on your main poller to lower the
re-schedule interval:
schedule:
macsuck:
when: '15,45 * * * *' # twice an hour
and set the main poller to hourly macsuck interval:
macsuck_min_age: 3600
(remove the setting of macsuck_min_age on your secondary poller so it
reverts to "0" which means ASAP).
At the end of the day, your job queue WILL be a mess, but by
controlling the configuration settings above, the pollers will behave
intelligently and you will have the correct effect after all, so don't
worry about the queue too much.
I hope this helps!
regards,
oliver.
Maybe with a 2nd host as remote poller, which use the database from
the 'main' poller ?
Netdisco version is 2.39.7.
I made some tests on a development system, but I saw a lot of jobs in
the job queue which never been configured from my side. When I stopped
netdisco-backend on one host, so only one poller is active, it 's
looks fine. (also from remote polling host). The configured polling
data was send to the database on the 'main' netdisco hosts.
Any ideas or solutions ?
Thanks,
Regards
Oliver Buehrig
--
Deutsches Elektronen-Synchrotron
IT-Kommunikationsnetzwerke
Notkestr. 85
22607 Hamburg
Germany
Tel. : +49 40 8998 2622
Fax : +49 40 8994 2622
E-Mail: oliver.bueh...@desy.de
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Oliver,
many thank for your quick answer. I need a lower polling for a small
group of 13 devices (old Stuff with very low CPU Power). A polling twice
a day is a max rate I can answer for that kind of devices, but is is
okay for this task.
With your hints, I can solve my problem.
Thanks a lot !
The idea with a 2nd, 3th.. poller would be a nice option to poll devices
behind a firewall without exections in the firewall rules for each
device. Only the database port must be opend for remote poller to the
Netdisco 'main' host.
Habe a nice Weekend
Regards,
Oliver
Am 22.02.2018 um 21:08 schrieb Oliver Gorwits:
> Hi Oliver
>
> On 2018-02-22 07:09, Oliver Bührig wrote:
>> I am looking for a way to poll some network devices (macksuck) with a
>> differnd polling interval like all other devices.
>> Is it possible ?
>
> That's a very interesting question! It's not an immediately
> configurable setting, but I think the effect can be achieved. You've
> also not said whether you mean higher or lower interval than default,
> and how many devices are affected. I'll give some options...
>
> We have the macsuck_min_age setting which controls "the minimum amount
> of time in seconds which must elapse between any two macsuck jobs for
> a device". If you want to *increase* the interval, you could set this
> to higher than 3600 (the default schedule interval for macsuck).
>
> To limit this to specific devices, you will need to run a second
> poller on another system (well done for working this out!). Configure
> the second poller with:
>
> schedule: null # to disable the scheduler
> discover_no: 'any'
> arpnip_no: 'any'
> macsuck_only: 'set-of-devices-with-different-interval'
>
> On your main poller you could have a corresponding:
>
> macsuck_no: 'set-of-devices-with-different-interval'
>
> If instead you want a shorter interval, macsuck_min_age will not work
> because it defaults to zero anyway. For that, you invert the
> behaviour: set the scheduler on your main poller to lower the
> re-schedule interval:
>
> schedule:
> macsuck:
> when: '15,45 * * * *' # twice an hour
>
> and set the main poller to hourly macsuck interval:
>
> macsuck_min_age: 3600
>
> (remove the setting of macsuck_min_age on your secondary poller so it
> reverts to "0" which means ASAP).
>
> At the end of the day, your job queue WILL be a mess, but by
> controlling the configuration settings above, the pollers will behave
> intelligently and you will have the correct effect after all, so don't
> worry about the queue too much.
>
> I hope this helps!
>
> regards,
> oliver.
>
>>
>> Maybe with a 2nd host as remote poller, which use the database from
>> the 'main' poller ?
>> Netdisco version is 2.39.7.
>>
>> I made some tests on a development system, but I saw a lot of jobs in
>> the job queue which never been configured from my side. When I stopped
>> netdisco-backend on one host, so only one poller is active, it 's
>> looks fine. (also from remote polling host). The configured polling
>> data was send to the database on the 'main' netdisco hosts.
>>
>> Any ideas or solutions ?
>>
>> Thanks,
>>
>> Regards
>>
>> Oliver Buehrig
>>
>> --
>>
>> Deutsches Elektronen-Synchrotron
>> IT-Kommunikationsnetzwerke
>> Notkestr. 85
>> 22607 Hamburg
>> Germany
>> Tel. : +49 40 8998 2622
>> Fax : +49 40 8994 2622
>>
>> E-Mail: oliver.bueh...@desy.de
>>
>> ------------------------------------------------------------------------------
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
