Hi again,
Looks like my 3.0.b10 nav installation isn't doing the automated processes like it should. I'm pretty sure I've done the seeding process correctly, and nav isn't showing any error's. The problem is in that nav isn't monitoring new ip devices I add. i.e. if I plug out a router that is in nav's db, it still shows it as UP, hence my alert profile doesn't work. Also nav makes cricket targets only for sysuptime, no interface targets.
I need help in tracking this problem.
This FAQ entry may help you here:
http://metanav.ntnu.no/moin.cgi/NAVFAQ#a-box-is-down-but-it-does-not-show-on...
6.1 A box is down, but it does not show on the status page. Why?
First, check if the box has been registered with Edit database, for instance in netbox report. Second, check with 'nav status' if pping and eventEngine are running. Third, check the log file of pping if it detected the outage. If it did, check the log file of eventEngine if it processed the event. If it did not, check if the event is still present in the eventq: In psql do 'SELECT * FROM eventq;'.
Further look at FAQ 7.1 for alert engine debugging.
To clarify, if confusing, pping will initially detect the outage and report to its log file and on the event queue (eventq). Event engine will in turn process the event and potentially correlate it with other relevant events, i.e. to detect "shadow states". Event engine posts the alarm on the alarm queue (alertq and alerthist), whereas alert engine processes the alarm queue an looks for matches in users active profiles.
Note: I have no switches, cabling and patches entered in the nav db, maybe the problem is there!?
This is no problem. As long as a given ip device is added thru add netbox it will be monitored by pping. Consistant topology information is not a requirement for the status monitor.
Also I don't have a switch that has snmp support, where/how do I enter such equipment in nav's db?
You can't. (I assume the switch has no IP address for management, if it has, but lack snmp support, you can status monitor it using the category OTHER).
On a general basis I would strongly recommend snmp support for all switches. Then NAV will be able to derive the switchports, neighbor information, vlan information, machine tracker information, statistics etc, etc.
- Vidar