Morten Brekkevold

I believe some of this stems from the fact that some of the API endpoints tend to inline too many of the related objects of each response record. E.g., why...

Jan Sigurd@UiO says this is appropriate to put to the NAV reference committee vote, and @hmpf says she wants to have a go at it whenever it comes up on...

> Possible workaraound: If #members in DeviceGroup is larger than N, do not populate Availability columns. I guess there are multiple possible workarounds. Some considerations: ### Front-end fetch vs. back-end...

@johannaengland You might also be able to reproduce the original issue by fuzzing some data into the database. Just having a group of 2500 faked netboxes may still produce the...

This is the exact same problem that has been reported for Cisco ASA through many years. Most stuff works through SNMP, but *not* ARP cache collection.

Tip from HiVolda: https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-device-details-per-mac-address

> If I go to the IP device info section, I can search for devices or IP > addresses. But I do not see and devices that exist already. For...

This is much the same NAV does specifically for collecting **BRIDGE-MIB** on Cisco and Aruba devices. These vendors have multiple instances of this MIB, which are reachable through community indexing....

There is of course this utility class which we definitely will need here: https://github.com/Uninett/nav/blob/770504d0ee400767b746464c330974123f8fc2c6/python/nav/mibs/mibretriever.py#L574-L586

The constant barrage of automated e-mail received from customers has prompted me to rebase this to the 5.4.x branch as a potential hotfix for a 5.4.1 release - I've also...