I just update from NAV 4.3 to 4.4.3.
All seems works but I get in the WatchDog the error message
"ARP records have not been collected in the last 2 days, 13 hours"
All services are ruungin (see below) and I can't find any documentation about this error.
Any suggestin will be appreciated.
Davide.
# sudo nav info activeip (cron): Collect active ip-adresses for all prefixes alertengine (daemon): Dispatches alerts according to individual alert profiles. eventengine (daemon): Reacts and creates alerts from events on the event queue. ipdevpoll (daemon): Collects SNMP inventory data from IP devices. logengine (cron): Regularly check the syslog for network messages and update the logger database mactrace (cron): Checks NAV's cam log for watched MAC addresses maintengine (cron): Regularly check the maintenance-queue and send events to eventq netbiostracker (cron): Regularly fetch netbiosnames from active computers pping (daemon): Pings all IP devices for status monitoring. psuwatch (cron): Monitors the state of redundant PSUs and fans servicemon (daemon): Monitors configured services. smsd (daemon): Dispatches queued SMS alerts. snmptrapd (daemon): Receives and processes SNMP traps and notifications. thresholdmon (cron): Monitors your Graphite metrics for exceeded thresholds topology (cron): Detects the topology of your network. # sudo nav status Up: activeip alertengine eventengine ipdevpoll logengine mactrace maintengine netbiostracker pping psuwatch servicemon smsd snmptrapd thresholdmon topology
On Wed, 4 May 2016 13:11:25 +0000 Davide Miccone davide@wpweb.com wrote:
"ARP records have not been collected in the last 2 days, 13 hours"
All services are ruungin (see below) and I can't find any documentation about this error.
Any suggestin will be appreciated.
This is more of a warning than an error. It means that WatchDog cannot see any ARP records having been modified in the last 2 days and 13 hours. In a normally dynamic network, this would be strange, and could indicate that the collection of ARP and ND records by the ip2mac ipdevpoll job is not working properly.
If you have no routers monitored in NAV, or all your monitored routers are unreachable, you might see the same thing.