On Mon 30 Sep 2024 at 15:12, Davide Miccone davide@wpweb.com wrote:
the use case is really simple.
One switch fail and needs to be replaced. (Or I need to replace an old with a new one).
I have the old switch configuration backup but NAV's representation is more clear than the script, especially for those who are used to managing the switch through NAV.
So I replace the switch but I wish to leave the old switch inside NAV because some configurations are not immediately migrated to the new switch, so I need to see in NAV the configuration of the old switch.
Continue to see the old switch in NAV is very useful for this reason. But I don't want to see the switch has a failed switch in the home page.
NAV was never designed with this use-case in mind. Rather, the common approach would be to put the dead switch in maintenance mode in NAV. NAV will still attempt to monitor it, but any alarms about it will be suppressed.
You can put a device on maintenance directly from the status tool by checking the checkbox next to the offending alert and selecting "Put on maintenance" from the actions drop-down menu. IIRC, this will create a maintenance task with no set end-time for that device.
This also allows you to add a description/reason for why the device has been placed on maintenance.
Several Network Monitoring Tools (LibreNMS, CheckMK, Zabbix) let disable a device.
You're welcome to post a feature request in our tracker :-)