Morten Brekkevold

@ingeborgoh It may be that this occurs because of some very inefficient SQL generated by the Django ORM, as used by the QuickSelect widget rendered to let the user select...

A complete and more proper solution for the issues described would be to replace the QuickSelect component with a more dynamic widget that employs the NAV API for component search....

> The force push was because of a rebase onto master Sure, but please refrain from doing that once the review process has begun, unless absolutely necessary - it makes...

> An extra level in the metric path for _location_ may also be needed. This could in reality be any prefix configured into the integration script, something like: > >...

IRL discussion landed us on `nav.dhcp.vlanXXX.netidentYYY` is the preferred prefix for DHCP pool stats. We should probably also support the simple case where no VLAN tags are reused, so dhcp...

Hi, @b2cc . SNMPv3 has been on the backburner for a while now, because we want to prioritize NETCONF et.al. But, any initial support for NETCONF will be mainly for...

> Hello @lunkwill42 Any news on this? I still do not see SNMP v3 in the Management Profile section... Indeed. No news, unfortunately. This is still not a priority for...

The main informative table about POE from the `POWER-ETHERNET-MIB` is the `pethPsePortTable`. See [RFC 3621](https://datatracker.ietf.org/doc/rfc3621/). The `CISCO-POWER-ETHERNET-EXT-MIB` extends/augments this table using the `cpeExtPsePortTable` table. This table provides several columns that...

Feedback from customers indicate that these objects from `CISCO-POWER-ETHERNET-EXT-MIB` are desired for logging: * `cpeExtPsePortPwrMax` * `cpeExtPsePortPwrAllocated` * `cpeExtPsePortPwrConsumption` * `cpeExtPsePortMaxPwrDrawn` These are defined thus: ```asn1 cpeExtPsePortPwrMax OBJECT-TYPE SYNTAX Unsigned32...

This has actually been made redundant/obsolete by #245 - thanks @pboers1988 !