Guys, is it possible to configure NAV to:
1 - ignore a single or a range of devices to be ignored from the polling process? I think this will be possible when we put it in maintenance mode. I'm right?
2 - apply per device ipdevpool's plugins intervals? According to docs, its is possible to set intervals for all devices but I hope that exists some other "hide" config to do that :)
On Wed, 3 Apr 2013 17:59:36 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
Guys, is it possible to configure NAV to:
1 - ignore a single or a range of devices to be ignored from the polling process? I think this will be possible when we put it in maintenance mode. I'm right?
Maybe, depending on what you are hoping to achieve. NAV has a maintenance scheduling tool. You can schedule maintenance tasks for entire locations, rooms or ranges of devices.
Scheduling a maintenance task for a device will, however, not stop NAV from polling it. It will only stop alerts from being sent when NAV detects a problem with the a device (any "problems" will be logged, though).
2 - apply per device ipdevpool's plugins intervals? According to docs, its is possible to set intervals for all devices but I hope that exists some other "hide" config to do that :)
No. We've thought about it, but nobody has expressed any wishes for such functionality, so it has never been implemented.
No. We've thought about it, but nobody has expressed any wishes for such functionality, so it has never been implemented.
hmm ok. Is there a workarround to make this work without remove the device from NAV? Can I open a blueprint for it?
2013/4/4 Morten Brekkevold morten.brekkevold@uninett.no
On Wed, 3 Apr 2013 17:59:36 -0300 Bruno Galindro da Costa < bruno.galindro@gmail.com> wrote:
Guys, is it possible to configure NAV to:
1 - ignore a single or a range of devices to be ignored from the polling process? I think this will be possible when we put it in maintenance
mode.
I'm right?
Maybe, depending on what you are hoping to achieve. NAV has a maintenance scheduling tool. You can schedule maintenance tasks for entire locations, rooms or ranges of devices.
Scheduling a maintenance task for a device will, however, not stop NAV from polling it. It will only stop alerts from being sent when NAV detects a problem with the a device (any "problems" will be logged, though).
2 - apply per device ipdevpool's plugins intervals? According to docs,
its
is possible to set intervals for all devices but I hope that exists some other "hide" config to do that :)
No. We've thought about it, but nobody has expressed any wishes for such functionality, so it has never been implemented.
-- Morten Brekkevold UNINETT
On Fri, 5 Apr 2013 21:50:07 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
No. We've thought about it, but nobody has expressed any wishes for such functionality, so it has never been implemented.
hmm ok. Is there a workarround to make this work without remove the device from NAV?
If your objective is to stop NAV from talking SNMP to a device entirely, you could change its category to something that doesn't require SNMP, such as `OTHER`.
Can I open a blueprint for it?
As I said in some off-list email, I'd rather you open a bugreport which we would classify as wishlist priority.
If your objective is to stop NAV from talking SNMP to a device entirely, you could change its category to something that doesn't require SNMP, such as `OTHER`.
Good idea.
As I said in some off-list email, I'd rather you open a bugreport which
we would classify as wishlist priority.
Ok. When is the case to open a blueprint? Or you always prefers open a bug report to classify it as wishlist priority?
2013/4/10 Morten Brekkevold morten.brekkevold@uninett.no
On Fri, 5 Apr 2013 21:50:07 -0300 Bruno Galindro da Costa < bruno.galindro@gmail.com> wrote:
No. We've thought about it, but nobody has expressed any wishes for such functionality, so it has never been implemented.
hmm ok. Is there a workarround to make this work without remove the
device
from NAV?
If your objective is to stop NAV from talking SNMP to a device entirely, you could change its category to something that doesn't require SNMP, such as `OTHER`.
Can I open a blueprint for it?
As I said in some off-list email, I'd rather you open a bugreport which we would classify as wishlist priority.
-- Morten Brekkevold UNINETT
On Wed, 10 Apr 2013 09:31:01 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
As I said in some off-list email, I'd rather you open a bugreport which we would classify as wishlist priority.
Ok. When is the case to open a blueprint? Or you always prefers open a bug report to classify it as wishlist priority?
We always prefer that users use the bug tracker.
Blueprints are mostly for planning and writing specifications for new features. Blueprints can be linked to bug reports, which means we will create them and attach them to wishlist reports if deemed useful.
ok!
2013/4/15 Morten Brekkevold morten.brekkevold@uninett.no
On Wed, 10 Apr 2013 09:31:01 -0300 Bruno Galindro da Costa < bruno.galindro@gmail.com> wrote:
As I said in some off-list email, I'd rather you open a bugreport which we would classify as wishlist priority.
Ok. When is the case to open a blueprint? Or you always prefers open a
bug
report to classify it as wishlist priority?
We always prefer that users use the bug tracker.
Blueprints are mostly for planning and writing specifications for new features. Blueprints can be linked to bug reports, which means we will create them and attach them to wishlist reports if deemed useful.
-- Morten Brekkevold UNINETT
-
Bruno Galindro da Costa -
Morten Brekkevold