The pping and ipdevpoll daemons have gained support for device filtering options. Using these options can limit the set of devices a pping or ipdevpoll instance will work with, based on your already configured device groups.
This enables a form of distributed monitoring that wasn’t previously possible: If you have a group of devices that are only accesible from the inside of some VLAN or secure zone, you can install NAV inside this zone and configure pping and ipdevpoll there to only monitor the devices within that zone, while telling other pping/ipdevpoll instances to ignore those device groups.
This can also be used for low-level and manual horizontal scaling of NAV’s monitoring functions.
The new options are documented in the daemons’ example config files, ipdevpoll.conf and pping.conf, respectively.
From NAV 5.1 release notes: