Differences

This shows you the differences between two versions of the page.

--- devel:database [2010/06/21 12:30] – faltin
+++ devel:database [2012/05/07 11:22] (current) – fix url morten
@@ Line 244: / Line 244: @@
 This [[http://domen.uninett.no/~faltin/nav/navdb/netbox_related.png|diagram]] shows OID database (and more).
-The role of the OID database has changed with NAV 3.6. ipdevpoll (that replaced getDeviceData) does not depend
+The role of the OID database has changed with NAV 3.6. ipdevpoll (that replaces getDeviceData) does not depend
-on the OID databe. Cricket still does and getBoksMacs still uses the oid database to figure out device
+on the OID database. Cricket still does and getBoksMacs still uses the oid database to figure out device
 capabilities.
@@ Line 338: / Line 338: @@
 rrd_fileid       the rrd file the data source is within
 name             name of the source (ds0,ds1,RESPONSE TIME etc)
-descr            further description
+descr            type of datasource, i.e. ifInOctets, ifInErrors, cpu5min, etc
 dstype           type (DERIVE / GAUGE)
 units            units used on y-axis (seconds, bytes, etc)
@@ Line 550: / Line 550: @@
 vlanid          vlan id (foreign key ref to vlan table, not an actual vlan number)
 direction       Direction of the link, seen from the root of the topology (the vlan's router).
-                'o' = 'Up', 'n' = 'Down', 'x' = ???
+                'o' = 'Up', 'n' = 'Down', 'b' = 'Blocked', 'x' = Unknown
 </code>
@@ Line 669: / Line 669: @@
 Different subsystem (specified in source) post events on the event queue.
 Normally event engine is the target and will take the event off the event
-queue and process it. getDeviceData are in some cases the target.
+queue and process it (getDeviceData was in some cases the target, not anymore).
 <code>
@@ Line 1042: / Line 1042: @@
 version...).
-See [[http://metanav.uninett.no/static/reports/NAVMore.pdf|NAVMore report ch 2.4]] (in Norwegian) for a further explaination of
+See [[http://nav.uninett.no/static/reports/NAVMore.pdf|NAVMore report ch 2.4]] (in Norwegian) for a further explaination of
 the NAV Cisco syslog analyzer tool. The chapter also includes a database figure, almost uptodate; the system table no longer exists and there is a newpriority reference from message to priority. For an explanation of the front-end tool, see [[..sysloganalyzer|here]].