Morten Brekkevold

This is basically what the device history tool is for. I do see a potential for merging the two tools, however - since device history is mostly a superset of...

Yes, I was imprecise: _device history is mostly a superset_ ➜ _device history is mostly **supposed to be** a superset_ :-)

In reality, this is two events: 1. Device was removed from a netbox 2. Device appeared on another netbox

> In reality, this is two events: > > 1. Device was removed from a netbox > > 2. Device appeared on another netbox Changed the wording of this issue....

Feedback from nav-ref indicates that this is not simply a "on/off" choice, but potentially a choice between "off" and several other "on"-type configs: - **Off** is pretty self-explanatory - **Auto**...

@hmpf I believe you want the **JUNIPER-ALARM-MIB**. It simply enumerates the number of present "red" alarms and "yellow" alarms in a device. There's a copy of it here: https://github.com/pgmillon/observium/blob/master/mibs/juniper/JUNIPER-ALARM-MIB You...

> Seems like step one is adding that mib to NAV's own library of mibs then :) Is there a howto for that? Closest thing we have is this: https://nav.readthedocs.io/en/latest/hacking/adding-environment-probe-support.html?highlight=smidump#dumping-the-mib

#2368 adds the necessary documentation for some of the command line utilities that are useful for testing SNMP OID compatibility with NAV...

After a design discussion with @knutvi, we have sort of concluded on a way forward. For the CNaaS team, it's important to know at any one given time what the...

I'm working on an implementation using `JUNIPER-VIRTUALCHASSIS-MIB`, but it seems the Juniper switches we're testing on will actually provide the necessary information in `ENTITY-MIB`. However, the latter implementation reports the...