devel:database
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devel:database [2010/06/18 13:27] faltin |
devel:database [2012/05/07 11:22] (current) morten fix url |
||
|---|---|---|---|
| Line 243: | Line 243: | ||
| This [[http://domen.uninett.no/~faltin/nav/navdb/netbox_related.png|diagram]] shows OID database (and more). | 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 replaces getDeviceData) does not depend | ||
| + | on the OID database. Cricket still does and getBoksMacs still uses the oid database to figure out device | ||
| + | capabilities. | ||
| ==== snmpoid ==== | ==== snmpoid ==== | ||
| Line 334: | Line 338: | ||
| rrd_fileid the rrd file the data source is within | rrd_fileid the rrd file the data source is within | ||
| name name of the source (ds0,ds1,RESPONSE TIME etc) | 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) | dstype type (DERIVE / GAUGE) | ||
| units units used on y-axis (seconds, bytes, etc) | units units used on y-axis (seconds, bytes, etc) | ||
| Line 428: | Line 432: | ||
| <code> | <code> | ||
| - | gwportid router port in question | + | interfaceid interface (router port) in question |
| prefixid prefix in question | prefixid prefix in question | ||
| gwip ip address defines on the router port | gwip ip address defines on the router port | ||
| Line 543: | Line 547: | ||
| <code> | <code> | ||
| swportvlanid table primary key | swportvlanid table primary key | ||
| - | swportid switch port id (foreign key ref to swport table) | + | interfaceid interface id (foreign key ref to interface table, i.e. which switch port is this) |
| vlanid vlan id (foreign key ref to vlan table, not an actual vlan number) | 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). | 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> | </code> | ||
| Line 561: | Line 565: | ||
| <code> | <code> | ||
| - | swportid switch trunk port in question | + | interfaceid switch trunk port in question (foreign key to the interface table) |
| hexstring hexstring that defines the allowed vlans for the trunk | hexstring hexstring that defines the allowed vlans for the trunk | ||
| </code> | </code> | ||
| Line 570: | Line 574: | ||
| <code> | <code> | ||
| - | swportid switch port in question | + | interfaceid switch port in question (foreign key to interface table) |
| vlan vlan value | vlan vlan value | ||
| </code> | </code> | ||
| Line 585: | Line 589: | ||
| ifindex ifindex on the switch | ifindex ifindex on the switch | ||
| to_netboxid candidate next hop netbox | to_netboxid candidate next hop netbox | ||
| - | to_swportid candidate next hop switch port | + | to_interfaceid candidate next hop switch port (foreign key to interface table) |
| misscnt see misscnt in the cam table below. Same thing. | misscnt see misscnt in the cam table below. Same thing. | ||
| </code> | </code> | ||
| Line 647: | Line 651: | ||
| <code> | <code> | ||
| patchid primary key | patchid primary key | ||
| - | swportid reference to the swport the cross connect is connected to | + | interfaceid reference to the swport the cross connect is connected to (foreign key to interface table) |
| cablingid reference to the jakc the cross connect is connected to | cablingid reference to the jakc the cross connect is connected to | ||
| split If a split cable is used in the jack end, specify type and leaf. | split If a split cable is used in the jack end, specify type and leaf. | ||
| Line 665: | Line 669: | ||
| Different subsystem (specified in source) post events on the event queue. | 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 | 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> | <code> | ||
| Line 754: | Line 758: | ||
| </code> | </code> | ||
| - | ==== alertmsg ==== | + | ==== alertqmsg ==== |
| Event engine will, based on alertmsg.conf, preformat the alarm messages, | Event engine will, based on alertmsg.conf, preformat the alarm messages, | ||
| one message for each configured alert channel (email, sms), one message for | one message for each configured alert channel (email, sms), one message for | ||
| - | each configured language. The data are stored in the alertmsg table. | + | each configured language. The data are stored in the alertqmsg table. |
| <code> | <code> | ||
| Line 824: | Line 828: | ||
| </code> | </code> | ||
| - | ==== alertengine ==== | ||
| - | Used by alert engine to keep track of processed alerts. | ||
| - | |||
| - | <code> | ||
| - | lastalertqid value of the last alertqid that alert engine has processed. | ||
| - | </code> | ||
| ===== Messages ===== | ===== Messages ===== | ||
| Line 923: | Line 921: | ||
| - | ===== Traffic map ===== | ||
| - | |||
| - | The traffic map (vlanplot) uses three tables to store values on positioning of | ||
| - | routers in the graph and on the use of containers. | ||
| - | This [[http://domen.uninett.no/~faltin/nav/navdb/trafficmap.png|diagram]] shows the releations between the | ||
| - | traffic map tables. | ||
| - | |||
| - | Also, see more documentation on the TrafficMap. | ||
| - | |||
| - | ==== vp_netbox_xy ==== | ||
| - | |||
| - | The table is used for positioning nodes (routers) on the traffic map. | ||
| - | A netbox may be positioned in more than one container (because we show the | ||
| - | other side of the link, the netboxes themself always only belong to one container). | ||
| - | |||
| - | <code> | ||
| - | vp_netbox_xyid primary key | ||
| - | pnetboxid the netboxid of this box (router) | ||
| - | x the X coordinate | ||
| - | y the Y coordinate | ||
| - | vp_netbox_grp_infoid reference to the container this node belongs to. | ||
| - | </code> | ||
| - | |||
| - | ==== vp_netbox_grp_info ==== | ||
| - | |||
| - | The table keeps information on all containers used by the traffic map. | ||
| - | Editing containers is done in Edit Database. | ||
| - | |||
| - | <code> | ||
| - | vp_netbox_grp_infoid primary key | ||
| - | name name of the container. The top container is named _Top. | ||
| - | hideicons boolean. The value has different meanings, see the TrafficMap wiki page. | ||
| - | iconname if a name is given and an equivalent icon is placed in the vlanPlot/icons | ||
| - | directory this will be used. | ||
| - | x the X coordinate of the container placement on _Top. | ||
| - | y the Y coordinate of the container placement on _Top. | ||
| - | </code> | ||
| - | |||
| - | ==== vp_netbox_grp ==== | ||
| - | |||
| - | The table maps netboxes to containers. This information is maintained by Edit Database. | ||
| - | |||
| - | <code> | ||
| - | vp_netbox_grp_infoid the container | ||
| - | pnetboxid the netboxid of this box (router) | ||
| - | </code> | ||
| Line 1011: | Line 963: | ||
| ==== identity ==== | ==== identity ==== | ||
| + | |||
| + | :!: Not up to date! | ||
| <code> | <code> | ||
| Line 1017: | Line 971: | ||
| blocked_status boolean | blocked_status boolean | ||
| blocked_reasonid reason of the block, reference to the blocked_reason table | blocked_reasonid reason of the block, reference to the blocked_reason table | ||
| - | swportid reference to the switch port found in the manage.swport table. | + | swportid reference to the switch port found in the interface table. |
| We find sysname,ip,module and port from this | We find sysname,ip,module and port from this | ||
| swsysname current sysname of switch, kept for consistency check | swsysname current sysname of switch, kept for consistency check | ||
| Line 1088: | Line 1042: | ||
| version...). | 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]]. | 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]]. | ||
devel/database.1276867622.txt.gz ยท Last modified: 2010/06/18 13:27 by faltin
Page Tools
