Debian Codegraph @

rfc7184.html

raw
1 <pre>Internet Engineering Task Force (IETF) U. Herberg
2 Request for Comments: 7184 Fujitsu Laboratories of America
3 Category: Standards Track R. Cole
4 ISSN: 2070-1721 US Army CERDEC
5 T. Clausen
6 LIX, Ecole Polytechnique
7 April 2014
8
9
10 <span class="h1">Definition of Managed Objects for</span>
11 <span class="h1">the Optimized Link State Routing Protocol Version 2</span>
12
13 Abstract
14
15 This document defines the Management Information Base (MIB) module
16 for configuring and managing the Optimized Link State Routing
17 Protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured
18 into configuration information, state information, performance
19 information, and notifications. This additional state and
20 performance information is useful for troubleshooting problems and
21 performance issues of the routing protocol. Two levels of compliance
22 allow this MIB module to be deployed on constrained routers.
23
24 Status of This Memo
25
26 This is an Internet Standards Track document.
27
28 This document is a product of the Internet Engineering Task Force
29 (IETF). It represents the consensus of the IETF community. It has
30 received public review and has been approved for publication by the
31 Internet Engineering Steering Group (IESG). Further information on
32 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
33
34 Information about the current status of this document, any errata,
35 and how to provide feedback on it may be obtained at
36 <a href="http://www.rfc-editor.org/info/rfc7184">http://www.rfc-editor.org/info/rfc7184</a>.
37
38 Copyright Notice
39
40 Copyright (c) 2014 IETF Trust and the persons identified as the
41 document authors. All rights reserved.
42
43 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
44 Provisions Relating to IETF Documents
45 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
46 publication of this document. Please review these documents
47 carefully, as they describe your rights and restrictions with respect
48 to this document. Code Components extracted from this document must
49
50
51
52 <span class="grey">Herberg, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
55
56
57 include Simplified BSD License text as described in Section 4.e of
58 the Trust Legal Provisions and are provided without warranty as
59 described in the Simplified BSD License.
60
61 Table of Contents
62
63 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
64 <a href="#section-2">2</a>. The Internet-Standard Management Framework ......................<a href="#page-3">3</a>
65 <a href="#section-3">3</a>. Conventions .....................................................<a href="#page-3">3</a>
66 <a href="#section-4">4</a>. Overview ........................................................<a href="#page-3">3</a>
67 <a href="#section-4.1">4.1</a>. Terms ......................................................<a href="#page-4">4</a>
68 <a href="#section-5">5</a>. Structure of the MIB Module .....................................<a href="#page-4">4</a>
69 <a href="#section-5.1">5.1</a>. The Configuration Group ....................................<a href="#page-5">5</a>
70 <a href="#section-5.2">5.2</a>. The State Group ............................................<a href="#page-5">5</a>
71 <a href="#section-5.3">5.3</a>. The Performance Group ......................................<a href="#page-5">5</a>
72 <a href="#section-5.4">5.4</a>. The Notifications Group ....................................<a href="#page-5">5</a>
73 <a href="#section-5.5">5.5</a>. Tables and Indexing ........................................<a href="#page-6">6</a>
74 <a href="#section-6">6</a>. Relationship to Other MIB Modules ...............................<a href="#page-9">9</a>
75 <a href="#section-6.1">6.1</a>. Relationship to the SNMPv2-MIB .............................<a href="#page-9">9</a>
76 <a href="#section-6.2">6.2</a>. Relationship to the NHDP-MIB ...............................<a href="#page-9">9</a>
77 <a href="#section-6.3">6.3</a>. MIB Modules Required for IMPORTS ...........................<a href="#page-9">9</a>
78 <a href="#section-7">7</a>. Definitions ....................................................<a href="#page-10">10</a>
79 <a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-77">77</a>
80 <a href="#section-9">9</a>. Applicability Statement ........................................<a href="#page-80">80</a>
81 <a href="#section-10">10</a>. IANA Considerations ...........................................<a href="#page-81">81</a>
82 <a href="#section-11">11</a>. Acknowledgements ..............................................<a href="#page-81">81</a>
83 <a href="#section-12">12</a>. References ....................................................<a href="#page-82">82</a>
84 <a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-82">82</a>
85 <a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-83">83</a>
86 <a href="#appendix-A">Appendix A</a>. IANAolsrv2LinkMetricType-MIB ..........................<a href="#page-84">84</a>
87
88 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
89
90 This document defines the Management Information Base (MIB) module
91 for configuring and managing the Optimized Link State Routing
92 Protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured
93 into configuration information, state information, performance
94 information, and notifications. In addition to configuration, this
95 additional state and performance information is useful for
96 troubleshooting problems and performance issues of the routing
97 protocol. Different levels of compliance allow implementers to use
98 smaller subsets of all defined objects, allowing for this MIB module
99 to be deployed on more constrained routers.
100
101
102
103
104
105
106
107
108 <span class="grey">Herberg, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Internet-Standard Management Framework</span>
114
115 For a detailed overview of the documents that describe the current
116 Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">Section&nbsp;7 of
117 [RFC3410]</a>.
118
119 Managed objects are accessed via a virtual information store, termed
120 the Management Information Base or MIB. MIB objects are generally
121 accessed through the Simple Network Management Protocol (SNMP).
122 Objects in the MIB module are defined using the mechanisms defined in
123 the Structure of Management Information (SMI). This document
124 specifies a MIB module that is compliant to the SMIv2, which is
125 described in STD 58, [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], STD 58, [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>] and STD 58
126 [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>].
127
128 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Conventions</span>
129
130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
132 "OPTIONAL" in this document are to be interpreted as described in
133 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
134
135 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span>
136
137 The Optimized Link State Routing Protocol version 2 (OLSRv2)
138 [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>] is a table-driven, proactive routing protocol, i.e., it
139 exchanges topology information with other routers in the network
140 periodically. OLSRv2 is an optimization of the classical link state
141 routing protocol. Its key concept is that of multipoint relays
142 (MPRs). Each router selects a set of its neighbor routers (which
143 "cover" all of its symmetrically connected 2-hop neighbor routers) as
144 MPRs. MPRs are then used to achieve both flooding reduction and
145 topology reduction.
146
147 This document provides management and control capabilities of an
148 OLSRv2 instance, allowing management applications to monitor the
149 state and performance of an OLSRv2 router, as well as to change
150 settings of the OLSRv2 instance (e.g., router or interface parameters
151 such as message intervals, etc.).
152
153 As OLSRv2 relies on the neighborhood information discovered by the
154 "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol
155 (NHDP)" [<a href="./rfc6130" title="&quot;Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)&quot;">RFC6130</a>], the OLSRv2-MIB module is aligned with the NHDP-MIB
156 module [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>] and augments several of the tables and objects in
157 the NHDP-MIB. In particular, common indexes for router interfaces
158 and discovered neighbors are used, as described in <a href="#section-5.2">Section 5.2</a>.
159
160
161
162
163
164 <span class="grey">Herberg, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
167
168
169 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Terms</span>
170
171 The following definitions apply throughout this document:
172
173 o Configuration Objects - switches, tables, and objects that are
174 initialized to default settings or set through the management
175 interface defined by this MIB module.
176
177 o State Objects - automatically generated values that define the
178 current operating state of the OLSRv2 protocol instance in the
179 router.
180
181 o Performance Objects - automatically generated values that help an
182 administrator or automated tool to assess the performance of the
183 OLSRv2 process on the router.
184
185 o Notification Objects - objects that define triggers and associated
186 notification messages allowing for asynchronous tracking of
187 predefined events on the managed router.
188
189 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Structure of the MIB Module</span>
190
191 This section presents the structure of the OLSRv2-MIB module. The
192 objects are arranged into the following structure:
193
194 o olsrv2MIBObjects - defines objects forming the basis for the
195 OLSRv2-MIB module. These objects are divided up by function into
196 the following groups:
197
198 * Configuration Group - defining objects related to the
199 configuration of the OLSRv2 instance on the router.
200
201 * State Group - defining objects that reflect the current state
202 of the OLSRv2 instance running on the router.
203
204 * Performance Group - defining objects that are useful to a
205 management system when characterizing the performance of OLSRv2
206 on the router and in the MANET.
207
208 o olsrv2MIBNotifications - objects defining OLSRv2-MIB module
209 notifications.
210
211 o olsrv2MIBConformance - defining the minimal and maximal
212 conformance requirements for implementations of this MIB module.
213
214
215
216
217
218
219
220 <span class="grey">Herberg, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
223
224
225 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. The Configuration Group</span>
226
227 The OLSRv2 router is configured with a set of controls. The
228 authoritative list of configuration controls within the OLSRv2-MIB
229 module is found within the MIB module itself. Generally, an attempt
230 was made in developing the OLSRv2-MIB module to support all
231 configuration objects defined in [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>]. For all of the
232 configuration parameters, the same constraints and default values of
233 these parameters as defined in [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>] are followed.
234
235 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. The State Group</span>
236
237 The State Group reports current state information of a router running
238 [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>]. The OLSRv2-MIB module State Group tables were designed to
239 contain the complete set of state information defined within the
240 Information Bases in [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>].
241
242 The OLSRv2-MIB module State Group tables are constructed as
243 extensions to the corresponding tables within the State Group of the
244 NHDP-MIB module [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>]. Use of the AUGMENTS clause is made, when
245 possible, to accomplish these table extensions. Further, the State
246 Group tables defined in this MIB module are aligned with the
247 corresponding tables in the NHDP-MIB module [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>], as described
248 in <a href="#section-6.2">Section 6.2</a>.
249
250 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. The Performance Group</span>
251
252 The Performance Group reports values relevant to system performance.
253 Frequent changes of sets or frequent recalculation of the Routing Set
254 or the MPRs can have a negative influence on the performance of
255 OLSRv2. This MIB module defines several objects that can be polled,
256 e.g., in order to calculate histories or monitor frequencies of
257 changes. This may help the network administrator to determine
258 unusual topology changes or other changes that affect stability and
259 reliability of the MANET. One such framework is specified in REPORT-
260 MIB [<a href="#ref-REPORT-MIB" title="&quot;Definition of Managed Objects for Performance Reporting&quot;">REPORT-MIB</a>].
261
262 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. The Notifications Group</span>
263
264 The Notifications Group contains Control
265 (olsrv2NotificationsControl), Objects (olsrv2NotificationsObjects),
266 and States (olsrv2NotificationsStates), where the Control contains
267 definitions of objects to control the frequency of notifications
268 being generated. The Objects define the supported notifications, and
269 the State is used to define additional information to be carried
270 within the notifications.
271
272
273
274
275
276 <span class="grey">Herberg, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
279
280
281 The olsrv2NotificationsObjects sub-tree contains the list of
282 notifications supported within the OLSRv2-MIB module and their
283 intended purpose or utility.
284
285 The same mechanisms for improving the network performance by reducing
286 the number of notifications apply as defined in <a href="./rfc6779#section-5.1">Section&nbsp;5.1 of
287 [RFC6779]</a>. The following objects are used to define the thresholds
288 and time windows for specific notifications defined in the NHDP-MIB
289 module: olsrv2RoutingSetRecalculationCountThreshold,
290 olsrv2RoutingSetRecalculationCountWindow,
291 olsrv2MPRSetRecalculationCountThreshold, and
292 olsrv2MPRSetRecalculationCountWindow.
293
294 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Tables and Indexing</span>
295
296 The OLSRv2-MIB module's tables are indexed by the following
297 constructs:
298
299 o nhdpIfIndex - the ifIndex of the local router on which NHDP is
300 configured. This is defined in the NHDP-MIB.
301
302 o nhdpDiscIfIndex - a locally managed index representing a known
303 interface on a neighboring router. This is defined in the NHDP-
304 MIB.
305
306 o nhdpDiscRouterIndex - a locally managed index representing an ID
307 of a known neighboring router. This is defined in the NHDP-MIB.
308
309 o {olsrv2LibOrigSetIpAddrType, olsrv2LibOrigSetIpAddr} - this index
310 (pair) uniquely identifies recently used originator addresses
311 found within the olsrv2LibOrigSetTable.
312
313 o {olsrv2LibLocAttNetSetIpAddrType, olsrv2LibLocAttNetSetIpAddr,
314 olsrv2LibLocAttNetSetIpAddrPrefixLen} - this index (triplet)
315 uniquely identifies local attached networks reachable through
316 local (non-OLSRv2) interfaces on this router. These are recorded
317 in the olsrv2LibLocAttNetSetTable.
318
319 o {olsrv2TibAdRemoteRouterSetIpAddrType,
320 olsrv2TibAdRemoteRouterSetIpAddr} - this index (pair) uniquely
321 identifies each router in the network that transmits Topology
322 Control (TC) messages received by this router. These records are
323 recorded in the olsrv2TibAdRemoteRouterSetIpAddr.
324
325 o {olsrv2TibRouterTopologySetFromOrigIpAddrType,
326 olsrv2TibRouterTopologySetFromOrigIpAddr,
327 olsrv2TibRouterTopologySetToOrigIpAddrType,
328 olsrv2TibRouterTopologySetToOrigIpAddr} - this index (quadruplet)
329
330
331
332 <span class="grey">Herberg, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
335
336
337 uniquely identifies discovered links within the network recorded
338 by this router. Information associated with each link is stored
339 in the olsrv2TibRouterTopologySetTable.
340
341 o {olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType,
342 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr,
343 olsrv2TibRoutableAddressTopologySetFromDestIpAddrType,
344 olsrv2TibRoutableAddressTopologySetFromDestIpAddr} - this index
345 (quadruplet) uniquely identifies reachable addresses within the
346 network and the router's advertising of these addresses. This
347 information is stored in the
348 olsrv2TibRoutableAddressTopologySetTable.
349
350 o {olsrv2TibAttNetworksSetOrigIpAddrType,
351 olsrv2TibAttNetworksSetOrigIpAddr,
352 olsrv2TibAttNetworksSetNetIpAddrType,
353 olsrv2TibAttNetworksSetNetIpAddr,
354 olsrv2TibAttNetworksSetNetIpAddrPrefixLen} - this index
355 (quintuplet) uniquely identifies the networks (which may be
356 outside the MANET) and the routers through which these networks
357 can be reached. This information is stored in the
358 olsrv2TibAttNetworksSetTable.
359
360 o {olsrv2TibRoutingSetDestIpAddrType, olsrv2TibRoutingSetDestIpAddr,
361 olsrv2TibRoutingSetDestIpAddrPrefixLen} - this index (triplet)
362 uniquely identifies the address of a reachable destination in the
363 network. This indexes the olsrv2TibRoutingSetTable, which
364 contains the next-hop information to reach the indexed addresses.
365
366 These tables and their indexing are:
367
368 o olsrv2InterfaceTable - describes the OLSRv2 status on the NHDP
369 interfaces of this router. This table augments nhdpInterfaceEntry
370 and, as such, it is indexed by the {nhdpIfIndex} from the NHDP-
371 MIB.
372
373 o olsrv2IibLinkSetTable - records all links from other routers that
374 are, or recently were, 1-hop neighbors. This table augments
375 nhdpIibLinkSetEntry and, as such, it is indexed by nhdpIfIndex and
376 nhdpDiscIfIndex.
377
378 o olsrv2Iib2HopSetTable - records network addresses of symmetric
379 2-hop neighbors and the links to the associated 1-hop neighbors.
380 This table augments nhdpIib2HopSetEntry and, as such, it is
381 indexed by {nhdpIfIndex, nhdpDiscIfIndex,
382 nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress}.
383
384
385
386
387
388 <span class="grey">Herberg, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
391
392
393 o olsrv2LibOrigSetTable - records addresses that were recently used
394 as originator addresses by this router. This table is indexed by
395 {olsrv2LibOrigSetIpAddrType, olsrv2LibOrigSetIpAddr}.
396
397 o olsrv2LibLocAttNetSetTable - records its local non-OLSRv2
398 interfaces via which it can act as a gateway to other networks.
399 This table is indexed by {olsrv2LibLocAttNetSetIpAddrType,
400 olsrv2LibLocAttNetSetIpAddr,
401 olsrv2LibLocAttNetSetIpAddrPrefixLen}.
402
403 o olsrv2NibNeighborSetTable - records all network addresses of each
404 1-hop neighbor. This table augments nhdpNibNeighborSetEntry and,
405 as such, it is indexed by the {nhdpDiscRouterIndex}.
406
407 o olsrv2TibAdRemoteRouterSetTable - records information describing
408 each remote router in the network that transmits TC messages.
409 This table is indexed by {olsrv2TibAdRemoteRouterSetIpAddrType,
410 olsrv2TibAdRemoteRouterSetIpAddr}.
411
412 o olsrv2TibRouterTopologySetTable - records topology information
413 about the network. This table is indexed by
414 {olsrv2TibRouterTopologySetFromOrigIpAddrType,
415 olsrv2TibRouterTopologySetFromOrigIpAddr,
416 olsrv2TibRouterTopologySetToOrigIpAddrType,
417 olsrv2TibRouterTopologySetToOrigIpAddr}.
418
419 o olsrv2TibRoutableAddressTopologySetTable - records topology
420 information about the routable addresses within the MANET and via
421 which routers they may be reached. This table is indexed by
422 {olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType,
423 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr,
424 olsrv2TibRoutableAddressTopologySetFromDestIpAddrType,
425 olsrv2TibRoutableAddressTopologySetFromDestIpAddr}.
426
427 o olsrv2TibAttNetworksSetTable - records information about networks
428 (which may be outside the MANET) attached to other routers and
429 their routable addresses. This table is indexed by
430 {olsrv2TibAttNetworksSetOrigIpAddrType,
431 olsrv2TibAttNetworksSetOrigIpAddr,
432 olsrv2TibAttNetworksSetNetIpAddrType,
433 olsrv2TibAttNetworksSetNetIpAddr,
434 olsrv2TibAttNetworksSetNetIpAddrPrefixLen}.
435
436 o olsrv2TibRoutingSetTable - records the first hop along a selected
437 path to each destination for which any such path is known. This
438 table is indexed by {olsrv2TibRoutingSetDestIpAddrType,
439 olsrv2TibRoutingSetDestIpAddr,
440 olsrv2TibRoutingSetDestIpAddrPrefixLen}.
441
442
443
444 <span class="grey">Herberg, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
447
448
449 o olsrv2InterfacePerfTable - records performance counters for each
450 active OLSRv2 interface on this device. This table augments
451 nhdpInterfacePerfEntry and, as such, it is indexed by
452 {nhdpIfIndex} from the NHDP-MIB.
453
454 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Relationship to Other MIB Modules</span>
455
456 This section specifies the relationship of the MIB modules contained
457 in this document to other standards, particularly to standards
458 containing other MIB modules. MIB modules and specific definitions
459 imported from MIB modules that SHOULD be implemented in conjunction
460 with the MIB module contained within this document are identified in
461 this section.
462
463 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Relationship to the SNMPv2-MIB</span>
464
465 The System group in the SNMPv2-MIB module [<a href="./rfc3418" title="&quot;Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)&quot;">RFC3418</a>] is defined as
466 being mandatory for all systems, and the objects apply to the entity
467 as a whole. The System group provides identification of the
468 management entity and certain other system-wide data. The OLSRv2-MIB
469 module does not duplicate those objects.
470
471 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Relationship to the NHDP-MIB</span>
472
473 OLSRv2 depends on the neighborhood information that is discovered by
474 [<a href="./rfc6130" title="&quot;Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)&quot;">RFC6130</a>]. An instance of OLSRv2 MUST have an associated instance of
475 NHDP running on the same device for proper operations of the
476 discovery and routing system. In order for the OLSRv2-MIB module to
477 correctly populate the objects relating to discovered neighbors, the
478 State Group tables of the NHDP-MIB module [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>] are aligned with
479 the State Group tables of this MIB module. This is accomplished
480 through the use of the AUGMENTS capability of SMIv2 (where
481 appropriate). This will allow for cross referencing of information
482 between the two MIB modules within a given SNMP context.
483
484 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. MIB Modules Required for IMPORTS</span>
485
486 The following OLSRv2-MIB module IMPORTS objects from NHDP-MIB
487 [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>], SNMPv2-SMI [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], SNMPv2-TC [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>], SNMPv2-CONF
488 [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>], IF-MIB [<a href="./rfc2863" title="&quot;The Interfaces Group MIB&quot;">RFC2863</a>], and INET-ADDRESS-MIB [<a href="./rfc4001" title="&quot;Textual Conventions for Internet Network Addresses&quot;">RFC4001</a>]. The
489 OLSRv2-MIB module also IMPORTS objects from the
490 IANAolsrv2LinkMetricType-MIB, which is available at &lt;<a href="http://www.iana.org/assignments/ianaolsrv2linkmetrictype-mib">http://</a>
491 <a href="http://www.iana.org/assignments/ianaolsrv2linkmetrictype-mib">www.iana.org/assignments/ianaolsrv2linkmetrictype-mib</a>&gt;.
492
493
494
495
496
497
498
499
500 <span class="grey">Herberg, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
503
504
505 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Definitions</span>
506
507 This section contains the OLSRv2-MIB module defined by the
508 specification.
509
510 OLSRv2-MIB DEFINITIONS ::= BEGIN
511
512 IMPORTS
513
514 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64,
515 Integer32, Unsigned32, mib-2, TimeTicks,
516 NOTIFICATION-TYPE
517 FROM SNMPv2-SMI -- <a href="./rfc2578">RFC 2578</a>
518
519 TEXTUAL-CONVENTION, TimeStamp, TruthValue
520 FROM SNMPv2-TC -- <a href="./rfc2579">RFC 2579</a>
521
522 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
523 FROM SNMPv2-CONF -- STD 58
524
525 InetAddressType, InetAddress,
526 InetAddressPrefixLength
527 FROM INET-ADDRESS-MIB -- <a href="./rfc4001">RFC 4001</a>
528
529 nhdpInterfaceEntry,
530 nhdpIibLinkSetEntry, nhdpIib2HopSetEntry,
531 nhdpNibNeighborSetEntry, nhdpInterfacePerfEntry
532 FROM NHDP-MIB -- <a href="./rfc6779">RFC 6779</a>
533
534 IANAolsrv2LinkMetricTypeTC
535 FROM IANA-OLSRv2-LINK-METRIC-TYPE-MIB
536 ;
537
538 manetOlsrv2MIB MODULE-IDENTITY
539 LAST-UPDATED "201404090000Z" -- 09 April 2014
540 ORGANIZATION "IETF MANET Working Group"
541 CONTACT-INFO
542 "WG E-Mail: [email protected]
543
544 WG Chairs: [email protected]
545 [email protected]
546
547 Editors: Ulrich Herberg
548 Fujitsu Laboratories of America
549 1240 East Arques Avenue
550 Sunnyvale, CA 94085
551 USA
552
553
554
555
556 <span class="grey">Herberg, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
559
560
561 Email: [email protected]
562 URI: <a href="http://www.herberg.name/">http://www.herberg.name/</a>
563
564 Thomas Heide Clausen
565 Ecole Polytechnique
566 LIX
567 91128 Palaiseau Cedex
568 France
569 Email: [email protected]
570 URI: <a href="http://www.thomasclausen.org/">http://www.thomasclausen.org/</a>
571
572 Robert G. Cole
573 US Army CERDEC
574 Space and Terrestrial Communications
575 6010 Frankford Street
576 Bldg 6010, Room 453H
577 Aberdeen Proving Ground, MD 21005
578 USA
579 Phone: +1 443 395-8744
580 Email: [email protected]
581 URI: <a href="http://www.cs.jhu.edu/~rgcole">http://www.cs.jhu.edu/~rgcole</a>"
582
583 DESCRIPTION
584 "This OLSRv2-MIB module is applicable to routers
585 implementing the Optimized Link State Routing
586 Protocol version 2 (OLSRv2) defined in <a href="./rfc7181">RFC 7181</a>.
587
588 Copyright (c) 2014 IETF Trust and the persons
589 identified as authors of the code. All rights reserved.
590
591 Redistribution and use in source and binary forms, with
592 or without modification, is permitted pursuant to, and
593 subject to the license terms contained in, the Simplified
594 BSD License set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's
595 Legal Provisions Relating to IETF Documents
596 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
597
598 This version of this MIB module is part of <a href="./rfc7184">RFC 7184</a>; see
599 the RFC itself for full legal notices."
600
601 -- Revision History
602 REVISION "201404090000Z" -- 09 April 2014
603 DESCRIPTION
604 "Initial version of this MIB module,
605 published as <a href="./rfc7184">RFC 7184</a>."
606
607 ::= { mib-2 219 }
608
609
610
611
612 <span class="grey">Herberg, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
615
616
617 --
618 -- TEXTUAL CONVENTIONS
619 --
620
621 Olsrv2MetricValueCompressedFormTC ::= TEXTUAL-CONVENTION
622 DISPLAY-HINT "d"
623 STATUS current
624 DESCRIPTION
625 "OLSRv2 Metrics are expressed in terms of a Link Metric
626 Compressed Form within the OLSRv2 protocol. This textual
627 convention defines the syntax of the metric objects
628 consistent with the definitions of the OLSRv2 Link
629 Metric Compressed Form in <a href="./rfc7181#section-6.2">Section&nbsp;6.2 of RFC 7181</a>.
630
631 The 12-bit compressed form of a link metric uses a modified
632 form of a representation with an 8-bit mantissa (denoted a)
633 and a 4-bit exponent (denoted b). Note that if represented
634 as the 12-bit value 256b+a, then the ordering of those 12-bit
635 values is identical to the ordering of the represented values.
636
637 The value so represented is (257+a)2^b - 256, where ^ denotes
638 exponentiation. This has a minimum value
639 (when a = 0 and b = 0) of MINIMUM_METRIC = 1 and a maximum
640 value (when a = 255 and b = 15) of MAXIMUM_METRIC = 2^24 - 256.
641
642 Hence, the metric values so represented range from 1 to
643 16776960. The special value of 0 is reserved for the
644 UNKNOWN_METRIC value.
645
646 If a network manager sets the metric value 'm' through the
647 MIB module, then the OLSRv2 code can both use this value
648 and derive a compressed representation of 'm' (as used in
649 messages) as specified in <a href="./rfc7181#section-6.2">Section&nbsp;6.2 of RFC7181</a>.
650 The value 'm' is persistently stored by the MIB module.
651 If the MIB module is pulling this metric's value from some other
652 source, e.g., the protocol instance, then this value is stored
653 as is."
654 SYNTAX Unsigned32 (0..16776960)
655
656 Olsrv2TimeValueCompressedForm32TC ::= TEXTUAL-CONVENTION
657 DISPLAY-HINT "x"
658 STATUS current
659 DESCRIPTION
660 "OLSRv2 time values may be expressed in terms of a compressed
661 form within the OLSRv2 protocol. This textual convention
662 defines the syntax of the time objects defined in terms of
663 an integer number of milliseconds, consistent with the
664 definitions of the 8-bit exponent-mantissa compressed form
665
666
667
668 <span class="grey">Herberg, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
671
672
673 defined in <a href="./rfc5497#section-5">Section&nbsp;5 of RFC 5497</a>. Time values with this
674 representation are defined in terms of a constant C, which
675 is represented in terms of seconds. The constant C
676 (time granularity) is used as specified in <a href="./rfc5497">RFC 5497</a>.
677 It MUST be the same as is used by NHDP (<a href="./rfc6130">RFC 6130</a>).
678
679 The 8-bit compressed form of a time value uses a modified
680 form of a representation with a 3-bit mantissa (denoted a)
681 and a 5-bit exponent (denoted b). Note that if represented
682 as the 8-bit value 8b+a, then the ordering of those 8-bit
683 values is identical to the ordering of the represented values.
684
685 The minimum time value that can be represented in this manner
686 is C. The maximum time value that can be represented in
687 this manner is 15 * 2^28 * C, 15*268,435,456 * C,
688 4,026,531,840 * C, or about 45 days if, for example,
689 C = 1/1024 second.
690
691 This TEXTUAL-CONVENTION limits the maximum value of the
692 time granularity constant C to be no greater than 1/1024
693 seconds due to its use of the Unsigned32 syntax limiting
694 the maximum number of milliseconds to no more than
695 3932160000.
696
697 When OLSRv2 uses this 8-bit exponent-mantissa compressed
698 form, this object value MUST be translated from the
699 integer form represented in this MIB module into the
700 exponent-mantissa form for the OLSRv2 protocol to use
701 according to the algorithm defined in <a href="./rfc5497#section-5">Section&nbsp;5 of
702 RFC 5497</a> for finding the next larger time value within
703 the exponent-mantissa format.
704
705 If a network manager sets the time value 't' through the
706 MIB module, then the OLSRv2 code can derive
707 'compressed_t' = T(a,b) according to the algorithm
708 in <a href="./rfc5497">RFC 5497</a> and 'compressed_t' is the value represented
709 in the OLSRv2 messages. But, the value 't' is persistently
710 stored by the MIB module. If the MIB module is pulling
711 this time parameter from some other source that is using
712 the compressed form, i.e., the protocol instance, then
713 this value is stored as is, after converting from
714 number of time constants C into number of milliseconds."
715 SYNTAX Unsigned32 (1..3932160000)
716
717 Olsrv2StatusTC ::= TEXTUAL-CONVENTION
718 STATUS current
719 DESCRIPTION
720 "Controls the operation of the OLSRv2
721
722
723
724 <span class="grey">Herberg, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
727
728
729 protocol on the device or a specific interface.
730 For example, for an interface, 'enabled' indicates
731 that OLSRv2 is permitted to operate,
732 and 'disabled' indicates that it is not."
733 SYNTAX INTEGER {
734 enabled (1),
735 disabled (2)
736 }
737
738 WillingnessTC ::= TEXTUAL-CONVENTION
739 DISPLAY-HINT "x"
740 STATUS current
741 DESCRIPTION
742 "A willingness value that evaluates to the
743 device's interest in participating in
744 a particular function, process, or behavior.
745
746 The willingness ranges from a low value of
747 WILL_NEVER(0) to a high value of
748 WILL_ALWAYS(15). For each parameter x,
749 there is an associated willingness value
750 W(x) such that WILL_NEVER &lt; W(x) &lt;= WILL_ALWAYS."
751 SYNTAX Unsigned32 (0..15)
752
753
754 --
755 -- Top-Level Object Identifier Assignments
756 --
757
758 olsrv2MIBNotifications OBJECT IDENTIFIER ::= { manetOlsrv2MIB 0 }
759 olsrv2MIBObjects OBJECT IDENTIFIER ::= { manetOlsrv2MIB 1 }
760 olsrv2MIBConformance OBJECT IDENTIFIER ::= { manetOlsrv2MIB 2 }
761
762 --
763 -- olsrv2ConfigurationGroup
764 --
765
766 -- Contains the OLSRv2 objects that configure specific
767 -- options that determine the overall performance and operation
768 -- of the OLSRv2 routing process.
769
770 olsrv2ConfigurationGroup OBJECT IDENTIFIER ::= {olsrv2MIBObjects 1}
771
772
773 olsrv2AdminStatus OBJECT-TYPE
774 SYNTAX Olsrv2StatusTC
775 MAX-ACCESS read-write
776 STATUS current
777
778
779
780 <span class="grey">Herberg, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
783
784
785 DESCRIPTION
786 "The configured status of the OLSRv2 process
787 on this device. 'enabled(1)' means that
788 OLSRv2 is configured to run on this device.
789 'disabled(2)' mean that the OLSRv2 process
790 is configured off.
791
792 Operation of the OLSRv2 protocol
793 requires the operation of the Neighborhood
794 Discovery Protocol (<a href="./rfc6130">RFC 6130</a>). Hence, this
795 object cannot have a status of 'enabled'
796 unless at least one interface on the device
797 is a MANET interface with NHDP enabled on that
798 interface. If a network manager attempts to
799 set this object to 'enabled' when no interfaces
800 on this device have NHDP enabled, the device
801 MUST fail the set with inconsistentValue.
802 If all device interfaces running NHDP become
803 disabled or removed, then the
804 olsrv2AdminStatus MUST be 'disabled'.
805
806 If the network manager, or other means, sets
807 this object to 'disabled', then the associated
808 interface specific objects, i.e., the
809 olsrv2InterfaceAdminStatus objects MUST all
810 be 'disabled'.
811
812 This object is persistent, and when written,
813 the entity SHOULD save the change to
814 non-volatile storage."
815 DEFVAL { disabled }
816 ::= { olsrv2ConfigurationGroup 1 }
817
818 olsrv2InterfaceTable OBJECT-TYPE
819 SYNTAX SEQUENCE OF Olsrv2InterfaceEntry
820 MAX-ACCESS not-accessible
821 STATUS current
822 DESCRIPTION
823 "The olsrv2InterfaceTable describes the OLSRv2
824 status on the NHDP interfaces of this router.
825 As such, this table augments the nhdpInterfaceTable
826 defined in the NHDP-MIB (<a href="./rfc6779">RFC 6779</a>). NHDP interfaces
827 are explicitly defined by network management, command
828 line interface (CLI) or other means for interfaces on
829 the device that are intended to run MANET protocols.
830 The olsrv2InterfaceTable contains a single object: the
831 olsrv2InterfaceAdminStatus object. This
832 object is set by network management, or by
833
834
835
836 <span class="grey">Herberg, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
839
840
841 other means, e.g., CLI.
842
843 A conceptual row in this table exists if and only
844 if a corresponding entry in the nhdpInterfaceTable
845 exists. If the corresponding entry with nhdpIfIndex
846 value is deleted from the nhdpInterfaceTable, then
847 the entry in this table is automatically deleted and
848 OLSRv2 is disabled on this interface,
849 and all configuration and state information
850 related to this interface is to be removed
851 from memory.
852
853 The olsrv2InterfaceAdminStatus can only be
854 'enabled' if the corresponding olsrv2AdminStatus
855 object is also set to 'enabled'."
856 REFERENCE
857 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
858 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
859 and U. Herberg, April 2014."
860 ::= { olsrv2ConfigurationGroup 2 }
861
862 olsrv2InterfaceEntry OBJECT-TYPE
863 SYNTAX Olsrv2InterfaceEntry
864 MAX-ACCESS not-accessible
865 STATUS current
866 DESCRIPTION
867 "The olsrv2InterfaceEntry describes one OLSRv2
868 local interface configuration as indexed by
869 its nhdpIfIndex, as defined in the
870 NHDP-MIB (<a href="./rfc6779">RFC 6779</a>).
871
872 The objects in this table are persistent, and when
873 written, the device SHOULD save the change to
874 non-volatile storage. For further information
875 on the storage behavior for these objects, refer
876 to the description for the nhdpIfRowStatus
877 object in the NHDP-MIB (<a href="./rfc6779">RFC6779</a>)."
878 REFERENCE
879 "<a href="./rfc6779">RFC 6779</a> - Definition of Managed Objects for
880 the Neighborhood Discovery Protocol,
881 Herberg, U., Cole, R.G., and I. Chakeres,
882 October 2012"
883 AUGMENTS { nhdpInterfaceEntry }
884 ::= { olsrv2InterfaceTable 1 }
885
886 Olsrv2InterfaceEntry ::=
887 SEQUENCE {
888 olsrv2InterfaceAdminStatus
889
890
891
892 <span class="grey">Herberg, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
895
896
897 Olsrv2StatusTC
898 }
899
900 olsrv2InterfaceAdminStatus OBJECT-TYPE
901 SYNTAX Olsrv2StatusTC
902 MAX-ACCESS read-create
903 STATUS current
904 DESCRIPTION
905 "The OLSRv2 interface's administrative status.
906 The value 'enabled(1)' denotes that the interface
907 is permitted to participate in the OLSRv2 routing
908 process. The value 'disabled(2)' denotes that
909 the interface is not permitted to participate
910 in the OLSRv2 routing process.
911
912 The configuration objects for the OLSRv2 routing
913 process, other than the administrative status objects,
914 are common to all interfaces on this device.
915 As such, the OLSRv2 configuration objects are globally
916 defined for the device and are not contained within
917 the olsrv2InterfaceTable."
918 DEFVAL { disabled }
919 ::= { olsrv2InterfaceEntry 1 }
920
921 olsrv2OrigIpAddrType OBJECT-TYPE
922 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
923 MAX-ACCESS read-write
924 STATUS current
925 DESCRIPTION
926 "The type of the olsrv2OrigIpAddr, as defined
927 in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
928
929 Only the values 'ipv4(1)' and
930 'ipv6(2)' are supported."
931 REFERENCE
932 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
933 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
934 and U. Herberg, April 2014."
935 ::= { olsrv2ConfigurationGroup 3 }
936
937 olsrv2OrigIpAddr OBJECT-TYPE
938 SYNTAX InetAddress (SIZE(4|16))
939 MAX-ACCESS read-write
940 STATUS current
941 DESCRIPTION
942 "The router's originator address. An address that
943 is unique (within the MANET) to this router.
944
945
946
947
948 <span class="grey">Herberg, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
951
952
953 This object is persistent, and when written,
954 the entity SHOULD save the change to
955 non-volatile storage."
956 REFERENCE
957 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
958 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
959 and U. Herberg, April 2014."
960 ::= { olsrv2ConfigurationGroup 4 }
961
962 --
963 -- Local History Times
964 --
965
966 olsrv2OHoldTime OBJECT-TYPE
967 SYNTAX Unsigned32
968 UNITS "milliseconds"
969 MAX-ACCESS read-write
970 STATUS current
971 DESCRIPTION
972 "olsrv2OHoldTime corresponds to
973 O_HOLD_TIME of OLSRv2, and represents the
974 time for which a recently used and replaced
975 originator address is used to recognize the router's
976 own messages.
977
978 Guidance for setting this object may be found
979 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
980 which indicates that:
981 o olsrv2OHoldTime &gt; 0
982
983 This object is persistent, and when written,
984 the entity SHOULD save the change to
985 non-volatile storage."
986 REFERENCE
987 "<a href="#section-5">Section 5</a> on Protocol Parameters.
988 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
989 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
990 and U. Herberg, April 2014."
991 DEFVAL { 30000 }
992 ::= { olsrv2ConfigurationGroup 5 }
993
994
995 --
996 -- Message intervals
997 --
998
999 olsrv2TcInterval OBJECT-TYPE
1000 SYNTAX Olsrv2TimeValueCompressedForm32TC
1001
1002
1003
1004 <span class="grey">Herberg, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1007
1008
1009 UNITS "milliseconds"
1010 MAX-ACCESS read-write
1011 STATUS current
1012 DESCRIPTION
1013 "olsrv2TcInterval corresponds to
1014 TC_INTERVAL of OLSRv2 and represents the
1015 maximum time between the transmission of
1016 two successive TC messages by this router.
1017
1018 Guidance for setting this object may be found
1019 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1020 which indicates that:
1021
1022 o olsrv2TcInterval &gt; 0
1023 o olsrv2TcInterval &gt;= olsrv2TcMinInterval
1024
1025 This object is persistent, and when written,
1026 the entity SHOULD save the change to
1027 non-volatile storage."
1028 REFERENCE
1029 "<a href="#section-5">Section 5</a> on Representing Time.
1030 <a href="./rfc5497">RFC 5497</a> - Representing Multi-Value Time in
1031 Mobile Ad Hoc Networks (MANETs),
1032 Clausen, T. and C. Dearlove, March 2009.
1033
1034 and
1035
1036 <a href="#section-5">Section 5</a> on Protocol Parameters.
1037 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1038 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1039 and U. Herberg, April 2014."
1040 DEFVAL { 5000 }
1041 ::= { olsrv2ConfigurationGroup 6 }
1042
1043 olsrv2TcMinInterval OBJECT-TYPE
1044 SYNTAX Olsrv2TimeValueCompressedForm32TC
1045 UNITS "milliseconds"
1046 MAX-ACCESS read-write
1047 STATUS current
1048 DESCRIPTION
1049 "olsrv2TcMinInterval corresponds to
1050 TC_MIN_INTERVAL of OLSRv2 and represents
1051 the minimum interval between transmission of
1052 two successive TC messages by this router.
1053
1054 Guidance for setting this object may be found
1055 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1056 which indicates that:
1057
1058
1059
1060 <span class="grey">Herberg, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1063
1064
1065 o olsrv2TcInterval &gt;= olsrv2TcMinInterval
1066
1067 The OLSRv2 protocol may choose to represent this
1068 time interval in terms of the 8-bit exponent-mantissa
1069 form defined in <a href="./rfc5497#section-5">Section&nbsp;5 of RFC 5497</a>. When this
1070 is the case, this object value MUST be translated
1071 from the integer form represented in this
1072 MIB module into the exponent-mantissa form for the
1073 OLSRv2 protocol to use according to the algorithm
1074 defined in <a href="./rfc5497#section-5">Section&nbsp;5 of RFC 5497</a> for finding the
1075 next larger time value within the exponent-mantissa
1076 format.
1077
1078 This object is persistent, and when written,
1079 the entity SHOULD save the change to
1080 non-volatile storage."
1081 REFERENCE
1082 "<a href="#section-5">Section 5</a> on Representing Time.
1083 <a href="./rfc5497">RFC 5497</a> - Representing Multi-Value Time in
1084 Mobile Ad Hoc Networks (MANETs),
1085 Clausen, T. and C. Dearlove, March 2009.
1086
1087 and
1088
1089 <a href="#section-5">Section 5</a> on Protocol Parameters.
1090 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1091 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1092 and U. Herberg, April 2014."
1093 DEFVAL { 1250 }
1094 ::= { olsrv2ConfigurationGroup 7 }
1095
1096
1097 --
1098 -- Advertised information validity times
1099 --
1100
1101 olsrv2THoldTime OBJECT-TYPE
1102 SYNTAX Olsrv2TimeValueCompressedForm32TC
1103 UNITS "milliseconds"
1104 MAX-ACCESS read-write
1105 STATUS current
1106 DESCRIPTION
1107 "olsrv2THoldTime corresponds to
1108 T_HOLD_TIME of OLSRv2 and is used as the
1109 minimum value in the TLV with
1110 Type = VALIDITY_TIME included in all
1111 TC messages sent by this router.
1112
1113
1114
1115
1116 <span class="grey">Herberg, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1119
1120
1121 Guidance for setting this object may be found
1122 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1123 which indicates that:
1124 o olsrv2THoldTime &gt;= olsrv2TcInterval
1125 o If TC messages can be lost, then
1126 olsrv2THoldTime SHOULD be
1127 significantly greater than olsrv2TcInterval;
1128 a value &gt;= 3 x olsrv2TcInterval is RECOMMENDED.
1129
1130 This object is persistent, and when written,
1131 the entity SHOULD save the change to
1132 non-volatile storage."
1133 REFERENCE
1134 "<a href="#section-5">Section 5</a> on Representing Time.
1135 <a href="./rfc5497">RFC 5497</a> - Representing Multi-Value Time in
1136 Mobile Ad Hoc Networks (MANETs),
1137 Clausen, T. and C. Dearlove, March 2009.
1138
1139 and
1140
1141 <a href="#section-5">Section 5</a> on Protocol Parameters.
1142 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1143 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1144 and U. Herberg, April 2014."
1145 DEFVAL { 15000 }
1146 ::= { olsrv2ConfigurationGroup 8 }
1147
1148 olsrv2AHoldTime OBJECT-TYPE
1149 SYNTAX Olsrv2TimeValueCompressedForm32TC
1150 UNITS "milliseconds"
1151 MAX-ACCESS read-write
1152 STATUS current
1153 DESCRIPTION
1154 "olsrv2AHoldTime corresponds to
1155 A_HOLD_TIME of OLSRv2 and represents
1156 the period during which TC messages are sent
1157 after they no longer have any advertised
1158 information to report, but are sent in order
1159 to accelerate outdated information removal by other
1160 routers.
1161
1162 Guidance for setting this object may be found
1163 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1164 which indicates that:
1165 o If TC messages can be lost, then
1166 olsrv2AHoldTime SHOULD be
1167 significantly greater than olsrv2TcInterval;
1168 a value &gt;= 3 x olsrv2TcInterval is
1169
1170
1171
1172 <span class="grey">Herberg, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1175
1176
1177 RECOMMENDED.
1178
1179 This object is persistent, and when written,
1180 the entity SHOULD save the change to
1181 non-volatile storage."
1182 REFERENCE
1183 "<a href="#section-5">Section 5</a> on Representing Time.
1184 <a href="./rfc5497">RFC 5497</a> - Representing Multi-Value Time in
1185 Mobile Ad Hoc Networks (MANETs),
1186 Clausen, T. and C. Dearlove, March 2009.
1187
1188 and
1189
1190 <a href="#section-5">Section 5</a> on Protocol Parameters.
1191 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1192 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1193 and U. Herberg, April 2014."
1194 DEFVAL { 15000 }
1195 ::= { olsrv2ConfigurationGroup 9 }
1196
1197 --
1198 -- Received message validity times
1199 --
1200
1201 olsrv2RxHoldTime OBJECT-TYPE
1202 SYNTAX Unsigned32
1203 UNITS "milliseconds"
1204 MAX-ACCESS read-write
1205 STATUS current
1206 DESCRIPTION
1207 "olsrv2RxHoldTime corresponds to
1208 RX_HOLD_TIME of OLSRv2 and represents the period
1209 after receipt of a message by the appropriate OLSRv2
1210 interface of this router for which that information
1211 is recorded, in order that the message is recognized
1212 as having been previously received on this OLSRv2
1213 interface.
1214
1215 Guidance for setting this object may be found
1216 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1217 which indicates that:
1218 o olsrv2RxHoldTime &gt; 0
1219 o This parameter SHOULD be greater
1220 than the maximum difference in time that a
1221 message may take to traverse the MANET,
1222 taking into account any message forwarding
1223 jitter as well as propagation, queuing,
1224 and processing delays.
1225
1226
1227
1228 <span class="grey">Herberg, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1231
1232
1233 This object is persistent, and when written,
1234 the entity SHOULD save the change to
1235 non-volatile storage."
1236 REFERENCE
1237 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1238 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1239 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1240 and U. Herberg, April 2014."
1241 DEFVAL { 30000 }
1242 ::= { olsrv2ConfigurationGroup 10 }
1243
1244 olsrv2PHoldTime OBJECT-TYPE
1245 SYNTAX Unsigned32
1246 UNITS "milliseconds"
1247 MAX-ACCESS read-write
1248 STATUS current
1249 DESCRIPTION
1250 "olsrv2PHoldTime corresponds to
1251 P_HOLD_TIME of OLSRv2 and represents the period
1252 after receipt of a message that is processed by
1253 this router for which that information is recorded,
1254 in order that the message is not processed again
1255 if received again.
1256
1257 Guidance for setting this object may be found
1258 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1259 which indicates that:
1260 o olsrv2PHoldTime &gt; 0
1261 o This parameter SHOULD be greater
1262 than the maximum difference in time that a
1263 message may take to traverse the MANET,
1264 taking into account any message forwarding
1265 jitter as well as propagation, queuing,
1266 and processing delays.
1267
1268 This object is persistent, and when written,
1269 the entity SHOULD save the change to
1270 non-volatile storage."
1271 REFERENCE
1272 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1273 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1274 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1275 and U. Herberg, April 2014."
1276 DEFVAL { 30000 }
1277 ::= { olsrv2ConfigurationGroup 11 }
1278
1279 olsrv2FHoldTime OBJECT-TYPE
1280 SYNTAX Unsigned32
1281
1282
1283
1284 <span class="grey">Herberg, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1287
1288
1289 UNITS "milliseconds"
1290 MAX-ACCESS read-write
1291 STATUS current
1292 DESCRIPTION
1293 "olsrv2FHoldTime corresponds to
1294 F_HOLD_TIME of OLSRv2 and represents the period
1295 after receipt of a message that is forwarded by this
1296 router for which that information is recorded, in order
1297 that the message is not forwarded again if received again.
1298
1299 Guidance for setting this object may be found
1300 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1301 which indicates that:
1302 o olsrv2FHoldTime &gt; 0
1303 o This parameter SHOULD be greater
1304 than the maximum difference in time that a
1305 message may take to traverse the MANET,
1306 taking into account any message forwarding
1307 jitter as well as propagation, queuing,
1308 and processing delays.
1309
1310 This object is persistent, and when written,
1311 the entity SHOULD save the change to
1312 non-volatile storage."
1313 REFERENCE
1314 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1315 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1316 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1317 and U. Herberg, April 2014."
1318 DEFVAL { 30000 }
1319 ::= { olsrv2ConfigurationGroup 12 }
1320
1321 --
1322 -- Jitter times
1323 --
1324
1325 olsrv2TpMaxJitter OBJECT-TYPE
1326 SYNTAX Unsigned32
1327 UNITS "milliseconds"
1328 MAX-ACCESS read-write
1329 STATUS current
1330 DESCRIPTION
1331 "olsrv2TpMaxJitter corresponds to
1332 TP_MAXJITTER of OLSRv2 and represents the value
1333 of MAXJITTER used in <a href="./rfc5148">RFC 5148</a> for periodically
1334 generated TC messages sent by this router.
1335
1336 For constraints on these parameters, see <a href="./rfc5148">RFC 5148</a>.
1337
1338
1339
1340 <span class="grey">Herberg, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1343
1344
1345 This object is persistent, and when written,
1346 the entity SHOULD save the change to
1347 non-volatile storage."
1348 REFERENCE
1349 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1350 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1351 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1352 and U. Herberg, April 2014."
1353 DEFVAL { 500 }
1354 ::= { olsrv2ConfigurationGroup 13 }
1355
1356 olsrv2TtMaxJitter OBJECT-TYPE
1357 SYNTAX Unsigned32
1358 UNITS "milliseconds"
1359 MAX-ACCESS read-write
1360 STATUS current
1361 DESCRIPTION
1362 "olsrv2TtMaxJitter corresponds to
1363 TT_MAXJITTER of OLSRv2 and represents the value
1364 of MAXJITTER used in <a href="./rfc5148">RFC 5148</a> for externally
1365 triggered TC messages sent by this router.
1366
1367 For constraints on these parameters, see <a href="./rfc5148">RFC 5148</a>.
1368
1369 This object is persistent, and when written,
1370 the entity SHOULD save the change to
1371 non-volatile storage."
1372 REFERENCE
1373 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1374 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1375 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1376 and U. Herberg, April 2014."
1377 DEFVAL { 500 }
1378 ::= { olsrv2ConfigurationGroup 14 }
1379
1380 olsrv2FMaxJitter OBJECT-TYPE
1381 SYNTAX Unsigned32
1382 UNITS "milliseconds"
1383 MAX-ACCESS read-write
1384 STATUS current
1385 DESCRIPTION
1386 "olsrv2FMaxJitter corresponds to
1387 F_MAXJITTER of OLSRv2 and represents the
1388 default value of MAXJITTER used in <a href="./rfc5148">RFC 5148</a> for
1389 messages forwarded by this router.
1390
1391 For constraints on these parameters, see <a href="./rfc5148">RFC 5148</a>.
1392
1393
1394
1395
1396 <span class="grey">Herberg, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1399
1400
1401 This object is persistent, and when written,
1402 the entity SHOULD save the change to
1403 non-volatile storage."
1404 REFERENCE
1405 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1406 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1407 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1408 and U. Herberg, April 2014."
1409 DEFVAL { 500 }
1410 ::= { olsrv2ConfigurationGroup 15 }
1411
1412 --
1413 -- Hop limits
1414 --
1415
1416 olsrv2TcHopLimit OBJECT-TYPE
1417 SYNTAX Unsigned32 (0..255)
1418 UNITS "hops"
1419 MAX-ACCESS read-write
1420 STATUS current
1421 DESCRIPTION
1422 "olsrv2TcHopLimit corresponds to
1423 TC_HOP_LIMIT of OLSRv2.
1424
1425 Guidance for setting this object may be found
1426 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1427 which indicates that:
1428 o The maximum value of
1429 olsrv2TcHopLimit &gt;= the network diameter
1430 in hops, a value of 255 is RECOMMENDED.
1431 o olsrv2TcHopLimit &gt;= 2.
1432
1433 This object is persistent, and when written,
1434 the entity SHOULD save the change to
1435 non-volatile storage."
1436 REFERENCE
1437 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1438 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1439 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1440 and U. Herberg, April 2014."
1441 DEFVAL { 255 }
1442 ::= { olsrv2ConfigurationGroup 16 }
1443
1444 --
1445 -- Willingness
1446 --
1447
1448 olsrv2WillRouting OBJECT-TYPE
1449
1450
1451
1452 <span class="grey">Herberg, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1455
1456
1457 SYNTAX WillingnessTC
1458 MAX-ACCESS read-write
1459 STATUS current
1460 DESCRIPTION
1461 "olsrv2WillRouting corresponds to
1462 WILL_ROUTING of OLSRv2.
1463
1464 Guidance for setting this object may be found
1465 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1466 which indicates that:
1467 o WILL_NEVER (0) &lt;= olsrv2WillRouting &lt;=
1468 WILL_ALWAYS (15)
1469
1470 This object is persistent, and when written,
1471 the entity SHOULD save the change to
1472 non-volatile storage."
1473 REFERENCE
1474 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1475 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1476 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1477 and U. Herberg, April 2014."
1478 DEFVAL { 7 }
1479 ::= { olsrv2ConfigurationGroup 17 }
1480
1481 olsrv2WillFlooding OBJECT-TYPE
1482 SYNTAX WillingnessTC
1483 MAX-ACCESS read-write
1484 STATUS current
1485 DESCRIPTION
1486 "olsrv2WillFlooding corresponds to
1487 WILL_FLOODING of OLSRv2.
1488
1489 Guidance for setting this object may be found
1490 in <a href="#section-5">Section 5</a> of the OLSRv2 specification (<a href="./rfc7181">RFC 7181</a>),
1491 which indicates that:
1492 o WILL_NEVER (0) &lt;= olsrv2WillFlooding &lt;=
1493 WILL_ALWAYS (15)
1494
1495 This object is persistent, and when written,
1496 the entity SHOULD save the change to
1497 non-volatile storage."
1498 REFERENCE
1499 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1500 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1501 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1502 and U. Herberg, April 2014."
1503 DEFVAL { 7 }
1504 ::= { olsrv2ConfigurationGroup 18 }
1505
1506
1507
1508 <span class="grey">Herberg, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1511
1512
1513 olsrv2LinkMetricType OBJECT-TYPE
1514 SYNTAX IANAolsrv2LinkMetricTypeTC
1515 MAX-ACCESS read-write
1516 STATUS current
1517 DESCRIPTION
1518 "olsrv2LinkMetricType corresponds to
1519 LINK_METRIC_TYPE of OLSRv2.
1520
1521 If olsrv2LinkMetricType changes, then all
1522 link metric information recorded by this router
1523 is invalid. The router MUST take the
1524 actions described in <a href="#section-5.5">Section 5.5</a>.
1525 'Parameter Change Constraints' and
1526 <a href="#section-17">Section 17</a> 'Information Base Changes'
1527 in <a href="./rfc7181">RFC 7181</a>.
1528
1529 This object is persistent, and when written,
1530 the entity SHOULD save the change to
1531 non-volatile storage."
1532 REFERENCE
1533 "<a href="#section-5">Section 5</a> on Protocol Parameters.
1534 <a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1535 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1536 and U. Herberg, April 2014."
1537 DEFVAL { unknown }
1538 ::= { olsrv2ConfigurationGroup 19 }
1539
1540 --
1541 -- olsrv2StateGroup
1542 --
1543
1544 --
1545 -- Contains information describing the current state of
1546 -- the OLSRv2 process.
1547 --
1548
1549 olsrv2StateGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 2 }
1550
1551 --
1552 -- Interface Information Base (IIB)
1553 --
1554
1555 --
1556 -- Link Set from <a href="./rfc6130">RFC 6130</a>, extended by L_in_metric,
1557 -- L_out_metric, and L_mpr_selector entries for each tuple
1558 --
1559
1560 olsrv2IibLinkSetTable OBJECT-TYPE
1561
1562
1563
1564 <span class="grey">Herberg, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1567
1568
1569 SYNTAX SEQUENCE OF Olsrv2IibLinkSetEntry
1570 MAX-ACCESS not-accessible
1571 STATUS current
1572 DESCRIPTION
1573 "A Link Set of an interface records all links
1574 from other routers that are, or recently
1575 were, 1-hop neighbors."
1576 REFERENCE
1577 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1578 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1579 and U. Herberg, April 2014."
1580 ::= { olsrv2StateGroup 1 }
1581
1582 olsrv2IibLinkSetEntry OBJECT-TYPE
1583 SYNTAX Olsrv2IibLinkSetEntry
1584 MAX-ACCESS not-accessible
1585 STATUS current
1586 DESCRIPTION
1587 "A Link Set consists of Link Tuples, each
1588 representing a single link indexed by the
1589 local and remote interface pair. Each Link Set
1590 from NHDP is extended by OLSRv2 by the following
1591 fields:
1592
1593 (L_in_metric (olsrv2IibLinkSetInMetricValue),
1594 L_out_metric (olsrv2IibLinkSetOutMetricValue),
1595 L_mpr_selector (olsrv2IibLinkSetMprSelector))"
1596 REFERENCE
1597 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1598 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1599 and U. Herberg, April 2014."
1600 AUGMENTS { nhdpIibLinkSetEntry }
1601 ::= { olsrv2IibLinkSetTable 1 }
1602
1603 Olsrv2IibLinkSetEntry ::=
1604 SEQUENCE {
1605 olsrv2IibLinkSetInMetricValue
1606 Olsrv2MetricValueCompressedFormTC,
1607 olsrv2IibLinkSetOutMetricValue
1608 Olsrv2MetricValueCompressedFormTC,
1609 olsrv2IibLinkSetMprSelector
1610 TruthValue
1611 }
1612
1613 olsrv2IibLinkSetInMetricValue OBJECT-TYPE
1614 SYNTAX Olsrv2MetricValueCompressedFormTC
1615 MAX-ACCESS read-only
1616 STATUS current
1617
1618
1619
1620 <span class="grey">Herberg, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1623
1624
1625 DESCRIPTION
1626 "olsrv2IibLinkSetInMetricValue is the metric of the link
1627 from the OLSRv2 interface with addresses
1628 L_neighbor_iface_addr_list to this OLSRv2 interface.
1629 The L_neighbor_iface_addr_list is identified by
1630 the nhdpDiscIfIndex, which is an index to the
1631 nhdpIibLinkSetTable, which this table augments."
1632 REFERENCE
1633 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1634 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1635 and U. Herberg, April 2014."
1636 ::= { olsrv2IibLinkSetEntry 1 }
1637
1638 olsrv2IibLinkSetOutMetricValue OBJECT-TYPE
1639 SYNTAX Olsrv2MetricValueCompressedFormTC
1640 MAX-ACCESS read-write
1641 STATUS current
1642 DESCRIPTION
1643 "olsrv2IibLinkSetOutMetricValue is the metric of the
1644 link to the OLSRv2 interface with addresses
1645 L_neighbor_iface_addr_list from this OLSRv2 interface.
1646 The L_neighbor_iface_addr_list is identified by
1647 the nhdpDiscIfIndex, which is an index to the
1648 nhdpIibLinkSetTable, which this table augments."
1649 REFERENCE
1650 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1651 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1652 and U. Herberg, April 2014."
1653 ::= { olsrv2IibLinkSetEntry 2 }
1654
1655 olsrv2IibLinkSetMprSelector OBJECT-TYPE
1656 SYNTAX TruthValue
1657 MAX-ACCESS read-only
1658 STATUS current
1659 DESCRIPTION
1660 "olsrv2IibLinkSetMprSelector is a boolean flag,
1661 recording whether this neighbor has selected this router
1662 as a flooding MPR, i.e., is a flooding MPR selector
1663 of this router."
1664 REFERENCE
1665 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1666 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1667 and U. Herberg, April 2014."
1668 ::= { olsrv2IibLinkSetEntry 3 }
1669
1670 --
1671 -- 2-Hop Set; from <a href="./rfc6130">RFC 6130</a>, extended by OLSRv2 by the
1672 -- following fields: N2_in_metric, N2_out_metric
1673
1674
1675
1676 <span class="grey">Herberg, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1679
1680
1681 --
1682
1683 olsrv2Iib2HopSetTable OBJECT-TYPE
1684 SYNTAX SEQUENCE OF Olsrv2Iib2HopSetEntry
1685 MAX-ACCESS not-accessible
1686 STATUS current
1687 DESCRIPTION
1688 "A 2-Hop Set of an interface records network
1689 addresses of symmetric 2-hop neighbors, and
1690 the symmetric links to symmetric 1-hop neighbors
1691 through which these symmetric 2-hop neighbors
1692 can be reached. It consists of 2-Hop Tuples."
1693 REFERENCE
1694 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1695 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1696 and U. Herberg, April 2014."
1697 ::= { olsrv2StateGroup 2 }
1698
1699 olsrv2Iib2HopSetEntry OBJECT-TYPE
1700 SYNTAX Olsrv2Iib2HopSetEntry
1701 MAX-ACCESS not-accessible
1702 STATUS current
1703 DESCRIPTION
1704 "olsrv2Iib2HopSetTable consists of 2-Hop Tuples,
1705 each representing a single network address of
1706 a symmetric 2-hop neighbor and a single MANET
1707 interface of a symmetric 1-hop neighbor.
1708 Each 2-Hop Set from NHDP is extended by
1709 OLSRv2 by the following fields:
1710
1711 (N2_in_metric (olsrv2Iib2HopSetInMetricValue),
1712 N2_out_metric (olsrv2Iib2HopSetOutMetricValue))"
1713 REFERENCE
1714 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1715 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1716 and U. Herberg, April 2014."
1717 AUGMENTS { nhdpIib2HopSetEntry }
1718 ::= { olsrv2Iib2HopSetTable 1 }
1719
1720 Olsrv2Iib2HopSetEntry ::=
1721 SEQUENCE {
1722 olsrv2Iib2HopSetInMetricValue
1723 Olsrv2MetricValueCompressedFormTC,
1724 olsrv2Iib2HopSetOutMetricValue
1725 Olsrv2MetricValueCompressedFormTC
1726 }
1727
1728 olsrv2Iib2HopSetInMetricValue OBJECT-TYPE
1729
1730
1731
1732 <span class="grey">Herberg, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1735
1736
1737 SYNTAX Olsrv2MetricValueCompressedFormTC
1738 MAX-ACCESS read-only
1739 STATUS current
1740 DESCRIPTION
1741 "olsrv2Iib2HopSetInMetricValue is the neighbor
1742 metric from the router with address
1743 N2_2hop_iface_addr to the router
1744 with OLSRv2 interface addresses
1745 N2_neighbor_iface_addr_list.
1746
1747 The N2_2hop_iface_addr is identified by the
1748 (nhdpIib2HopSetIpAddressType,
1749 nhdpIib2HopSetIpAddress) pair from the
1750 nhdpIibLinkSetTable, which this table augments.
1751
1752 The N2_neighbor_iface_addr_list is defined by
1753 the nhdpDiscIfIndex, which is an index of the
1754 nhdpIibLinkSetTable, which this table augments."
1755 REFERENCE
1756 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1757 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1758 and U. Herberg, April 2014.
1759
1760 and
1761
1762 <a href="./rfc6779">RFC 6779</a> - Definition of Managed Objects for the
1763 Neighborhood Discovery Process, Herberg, U.,
1764 Cole, R., and I. Chakeres, October 2012."
1765 ::= { olsrv2Iib2HopSetEntry 1 }
1766
1767 olsrv2Iib2HopSetOutMetricValue OBJECT-TYPE
1768 SYNTAX Olsrv2MetricValueCompressedFormTC
1769 MAX-ACCESS read-only
1770 STATUS current
1771 DESCRIPTION
1772 "olsrv2Iib2HopSetOutMetricValue is the neighbor metric
1773 to the router with address N2_2hop_iface_addr
1774 from the router with OLSRv2 interface addresses
1775 N2_neighbor_iface_addr_list.
1776
1777 The N2_2hop_iface_addr is identified by the
1778 (nhdpIib2HopSetIpAddressType,
1779 nhdpIib2HopSetIpAddress) pair from the
1780 nhdpIibLinkSetTable, which this table augments.
1781
1782 The N2_neighbor_iface_addr_list is defined by
1783 the nhdpDiscIfIndex, which is an index of the
1784 nhdpIibLinkSetTable, which this table augments."
1785
1786
1787
1788 <span class="grey">Herberg, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1791
1792
1793 REFERENCE
1794 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1795 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1796 and U. Herberg, April 2014.
1797
1798 and
1799
1800 <a href="./rfc6779">RFC 6779</a> - Definition of Managed Objects for the
1801 Neighborhood Discovery Process, Herberg, U.,
1802 Cole, R., and I. Chakeres, October 2012."
1803 ::= { olsrv2Iib2HopSetEntry 2 }
1804
1805 --
1806 -- Local Information Base - as defined in <a href="./rfc6130">RFC 6130</a>,
1807 -- extended by the addition of an Originator Set,
1808 -- defined in <a href="#section-6.1">Section 6.1</a> and a Local Attached
1809 -- Network Set, defined in <a href="#section-6.2">Section 6.2</a>.
1810 --
1811
1812 --
1813 -- Originator Set
1814 --
1815
1816 olsrv2LibOrigSetTable OBJECT-TYPE
1817 SYNTAX SEQUENCE OF Olsrv2LibOrigSetEntry
1818 MAX-ACCESS not-accessible
1819 STATUS current
1820 DESCRIPTION
1821 "A router's Originator Set records addresses
1822 that were recently used as originator addresses
1823 by this router."
1824 REFERENCE
1825 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1826 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1827 and U. Herberg, April 2014."
1828 ::= { olsrv2StateGroup 3 }
1829
1830 olsrv2LibOrigSetEntry OBJECT-TYPE
1831 SYNTAX Olsrv2LibOrigSetEntry
1832 MAX-ACCESS not-accessible
1833 STATUS current
1834 DESCRIPTION
1835 "A router's Originator Set consists of
1836 Originator Tuples:
1837
1838 (O_orig_addr (olsrv2LibOrigSetIpAddrType
1839 and olsrv2LibOrigSetIpAddr),
1840 O_time (olsrv2LibOrigSetExpireTime))."
1841
1842
1843
1844 <span class="grey">Herberg, et al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1847
1848
1849 REFERENCE
1850 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1851 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1852 and U. Herberg, April 2014."
1853 INDEX { olsrv2LibOrigSetIpAddrType,
1854 olsrv2LibOrigSetIpAddr }
1855 ::= { olsrv2LibOrigSetTable 1 }
1856
1857 Olsrv2LibOrigSetEntry ::=
1858 SEQUENCE {
1859 olsrv2LibOrigSetIpAddrType
1860 InetAddressType,
1861 olsrv2LibOrigSetIpAddr
1862 InetAddress,
1863 olsrv2LibOrigSetExpireTime
1864 TimeStamp
1865 }
1866
1867 olsrv2LibOrigSetIpAddrType OBJECT-TYPE
1868 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
1869 MAX-ACCESS not-accessible
1870 STATUS current
1871 DESCRIPTION
1872 "The type of the olsrv2LibOrigSetIpAddr,
1873 as defined in the InetAddress MIB (<a href="./rfc4001">RFC4001</a>).
1874
1875 Only the values 'ipv4(1)' and
1876 'ipv6(2)' are supported."
1877 REFERENCE
1878 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1879 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1880 and U. Herberg, April 2014."
1881 ::= { olsrv2LibOrigSetEntry 1 }
1882
1883 olsrv2LibOrigSetIpAddr OBJECT-TYPE
1884 SYNTAX InetAddress (SIZE(4|16))
1885 MAX-ACCESS not-accessible
1886 STATUS current
1887 DESCRIPTION
1888 "An originator address recently employed
1889 by this router."
1890 REFERENCE
1891 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1892 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1893 and U. Herberg, April 2014."
1894 ::= { olsrv2LibOrigSetEntry 2 }
1895
1896 olsrv2LibOrigSetExpireTime OBJECT-TYPE
1897
1898
1899
1900 <span class="grey">Herberg, et al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1903
1904
1905 SYNTAX TimeStamp
1906 UNITS "centiseconds"
1907 MAX-ACCESS read-only
1908 STATUS current
1909 DESCRIPTION
1910 "olsrv2LibOrigSetExpireTime specifies the value
1911 of sysUptime when this entry SHOULD expire and be
1912 removed from the olsrv2LibOrigSetTable. This time
1913 is determined at the time the entry is added,
1914 derived from the following expression:
1915
1916 O_time := current time + O_HOLD_TIME
1917
1918 where O_time is olsrv2LibOrigSetExpireTime,
1919 current_time is current sysUptime, and
1920 O_HOLD_TIME is a parameter of the OLSRv2
1921 protocol. In the event that the
1922 O_HOLD_TIME is changed, the
1923 olsrv2LibOrigSetExpireTime needs to be
1924 recomputed for each of the entries in this table."
1925 REFERENCE
1926 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1927 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1928 and U. Herberg, April 2014."
1929 ::= { olsrv2LibOrigSetEntry 3 }
1930
1931 --
1932 -- Local Attached Network Set
1933 --
1934
1935 olsrv2LibLocAttNetSetTable OBJECT-TYPE
1936 SYNTAX SEQUENCE OF Olsrv2LibLocAttNetSetEntry
1937 MAX-ACCESS not-accessible
1938 STATUS current
1939 DESCRIPTION
1940 "A router's Local Attached Network Set records
1941 its local non-OLSRv2 interfaces via which it
1942 can act as a gateway to other networks."
1943 REFERENCE
1944 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
1945 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
1946 and U. Herberg, April 2014."
1947 ::= { olsrv2StateGroup 4 }
1948
1949 olsrv2LibLocAttNetSetEntry OBJECT-TYPE
1950 SYNTAX Olsrv2LibLocAttNetSetEntry
1951 MAX-ACCESS not-accessible
1952 STATUS current
1953
1954
1955
1956 <span class="grey">Herberg, et al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
1959
1960
1961 DESCRIPTION
1962 "The entries include the Local Attached
1963 Network Tuples:
1964
1965 (AL_net_addr (olsrv2LibLocAttNetSetIpAddr),
1966 AL_dist (olsrv2LibLocAttNetSetDistance),
1967 AL_metric (olsrv2LibLocAttNetSetMetricValue)
1968 )
1969
1970 where:
1971
1972 AL_net_addr is the network address
1973 of an attached network that can
1974 be reached via this router. The
1975 AL_net_addr is defined in this MIB
1976 module by the tuple
1977 (olsrv2LibLocAttNetSetIpAddrType,
1978 olsrv2LibLocAttNetSetIpAddr,
1979 olsrv2LibLocAttNetSetIpAddrPrefixLen).
1980
1981 AL_dist is the number of hops to
1982 the network with address AL_net_addr
1983 from this router. The AL_dist is
1984 defined in this MIB module by the
1985 olsrv2LibLocAttNetSetDistance object.
1986
1987 AL_metric is the metric of the link to
1988 the attached network with address
1989 AL_net_addr from this router. The
1990 AL_metric is defined in this MIB module
1991 by the olsrv2LibLocAttNetSetMetricValue
1992 object.
1993
1994 OLSRv2 (<a href="./rfc7181">RFC 7181</a>) defines the rules for managing
1995 entries within this table, e.g., populating
1996 and purging entries. Specific instructions for the
1997 olsrv2LibLocAttNetSetEntry(s) are found in
1998 Sections <a href="#section-7.2">7.2</a> and <a href="#section-17">17</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
1999 REFERENCE
2000 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2001 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2002 and U. Herberg, April 2014."
2003 INDEX { olsrv2LibLocAttNetSetIpAddrType,
2004 olsrv2LibLocAttNetSetIpAddr,
2005 olsrv2LibLocAttNetSetIpAddrPrefixLen }
2006 ::= { olsrv2LibLocAttNetSetTable 1 }
2007
2008 Olsrv2LibLocAttNetSetEntry ::=
2009
2010
2011
2012 <span class="grey">Herberg, et al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2015
2016
2017 SEQUENCE {
2018 olsrv2LibLocAttNetSetIpAddrType
2019 InetAddressType,
2020 olsrv2LibLocAttNetSetIpAddr
2021 InetAddress,
2022 olsrv2LibLocAttNetSetIpAddrPrefixLen
2023 InetAddressPrefixLength,
2024 olsrv2LibLocAttNetSetDistance
2025 Unsigned32,
2026 olsrv2LibLocAttNetSetMetricValue
2027 Olsrv2MetricValueCompressedFormTC
2028 }
2029
2030 olsrv2LibLocAttNetSetIpAddrType OBJECT-TYPE
2031 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2032 MAX-ACCESS not-accessible
2033 STATUS current
2034 DESCRIPTION
2035 "The type of the olsrv2LibLocAttNetSetIpAddr, as defined
2036 in the InetAddress MIB (<a href="./rfc4001">RFC 4001</a>).
2037
2038 Only the values 'ipv4(1)' and
2039 'ipv6(2)' are supported."
2040 REFERENCE
2041 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2042 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2043 and U. Herberg, April 2014."
2044 ::= { olsrv2LibLocAttNetSetEntry 1 }
2045
2046 olsrv2LibLocAttNetSetIpAddr OBJECT-TYPE
2047 SYNTAX InetAddress (SIZE(4|16))
2048 MAX-ACCESS not-accessible
2049 STATUS current
2050 DESCRIPTION
2051 "This is the network address of an attached
2052 network that can be reached via this router."
2053 REFERENCE
2054 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2055 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2056 and U. Herberg, April 2014."
2057 ::= { olsrv2LibLocAttNetSetEntry 2 }
2058
2059 olsrv2LibLocAttNetSetIpAddrPrefixLen OBJECT-TYPE
2060 SYNTAX InetAddressPrefixLength
2061 UNITS "bits"
2062 MAX-ACCESS not-accessible
2063 STATUS current
2064 DESCRIPTION
2065
2066
2067
2068 <span class="grey">Herberg, et al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2071
2072
2073 "Indicates the number of leading one bits that form the
2074 mask to be logically ANDed with the destination address
2075 before being compared to the value in the
2076 olsrv2LibLocAttNetSetIpAddr field."
2077 REFERENCE
2078 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2079 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2080 and U. Herberg, April 2014."
2081 ::= { olsrv2LibLocAttNetSetEntry 3 }
2082
2083 olsrv2LibLocAttNetSetDistance OBJECT-TYPE
2084 SYNTAX Unsigned32 (1..255)
2085 UNITS "hops"
2086 MAX-ACCESS read-only
2087 STATUS current
2088 DESCRIPTION
2089 "This object specifies the number of hops
2090 to the network with address
2091 olsrv2LibLocAttNetSetIpAddr from this router."
2092 REFERENCE
2093 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2094 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2095 and U. Herberg, April 2014."
2096 ::= { olsrv2LibLocAttNetSetEntry 4 }
2097
2098 olsrv2LibLocAttNetSetMetricValue OBJECT-TYPE
2099 SYNTAX Olsrv2MetricValueCompressedFormTC
2100 MAX-ACCESS read-only
2101 STATUS current
2102 DESCRIPTION
2103 "This object specifies the metric of the
2104 link to the attached network with
2105 address AL_net_addr from this router. The
2106 AL_net_addr is defined by the tuple
2107 (olsrv2LibLocAttNetSetIpAddrType,
2108 olsrv2LibLocAttNetSetIpAddr,
2109 olsrv2LibLocAttNetSetIpAddrPrefixLen)."
2110 REFERENCE
2111 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2112 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2113 and U. Herberg, April 2014."
2114 ::= { olsrv2LibLocAttNetSetEntry 5 }
2115
2116 --
2117 -- Neighbor Information Base
2118 --
2119
2120 --
2121
2122
2123
2124 <span class="grey">Herberg, et al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2127
2128
2129 -- Neighbor Set - as defined in <a href="./rfc6130">RFC 6130</a>,
2130 -- extended by OLSRv2 by the addition of the following
2131 -- elements to each Neighbor Tuple:
2132 -- N_orig_addr (olsrv2NibNeighborSetNOrigIpAddrType,
2133 -- olsrv2NibNeighborSetNOrigIpAddr)
2134 -- N_in_metric (olsrv2NibNeighborSetNInMetricValue)
2135 -- N_out_metric (olsrv2NibNeighborSetNOutMetricValue)
2136 -- N_will_flooding (olsrv2NibNeighborSetNWillFlooding)
2137 -- N_will_routing (olsrv2NibNeighborSetNWillRouting)
2138 -- N_flooding_mpr (olsrv2NibNeighborSetNFloodingMpr)
2139 -- N_routing_mpr (olsrv2NibNeighborSetNRoutingMpr)
2140 -- N_mpr_selector (olsrv2NibNeighborSetNMprSelector)
2141 -- N_advertised (olsrv2NibNeighborSetNAdvertised)
2142 --
2143
2144 olsrv2NibNeighborSetTable OBJECT-TYPE
2145 SYNTAX SEQUENCE OF Olsrv2NibNeighborSetEntry
2146 MAX-ACCESS not-accessible
2147 STATUS current
2148 DESCRIPTION
2149 "A router's Neighbor Set records all network
2150 addresses of each 1-hop neighbor. It consists
2151 of Neighbor Tuples, each representing a single
2152 1-hop neighbor."
2153 REFERENCE
2154 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2155 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2156 and U. Herberg, April 2014."
2157 ::= { olsrv2StateGroup 5 }
2158
2159 olsrv2NibNeighborSetEntry OBJECT-TYPE
2160 SYNTAX Olsrv2NibNeighborSetEntry
2161 MAX-ACCESS not-accessible
2162 STATUS current
2163 DESCRIPTION
2164 "Each Neighbor Tuple in the Neighbor Set, defined
2165 in <a href="./rfc6130">RFC 6130</a>, has these additional elements:
2166 N_orig_addr (olsrv2NibNeighborSetNOrigIpAddrType,
2167 olsrv2NibNeighborSetNOrigIpAddr)
2168 N_in_metric (olsrv2NibNeighborSetNInMetricValue)
2169 N_out_metric (olsrv2NibNeighborSetNOutMetricValue)
2170 N_will_flooding (olsrv2NibNeighborSetNWillFlooding)
2171 N_will_routing (olsrv2NibNeighborSetNWillRouting)
2172 N_flooding_mpr (olsrv2NibNeighborSetNFloodingMpr)
2173 N_routing_mpr (olsrv2NibNeighborSetNRoutingMpr)
2174 N_mpr_selector (olsrv2NibNeighborSetNMprSelector)
2175 N_advertised (olsrv2NibNeighborSetNAdvertised)
2176 defined here as extensions."
2177
2178
2179
2180 <span class="grey">Herberg, et al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2183
2184
2185 REFERENCE
2186 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2187 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2188 and U. Herberg, April 2014."
2189 AUGMENTS { nhdpNibNeighborSetEntry }
2190 ::= { olsrv2NibNeighborSetTable 1 }
2191
2192 Olsrv2NibNeighborSetEntry ::=
2193 SEQUENCE {
2194 olsrv2NibNeighborSetNOrigIpAddrType
2195 InetAddressType,
2196 olsrv2NibNeighborSetNOrigIpAddr
2197 InetAddress,
2198 olsrv2NibNeighborSetNInMetricValue
2199 Olsrv2MetricValueCompressedFormTC,
2200 olsrv2NibNeighborSetNOutMetricValue
2201 Olsrv2MetricValueCompressedFormTC,
2202 olsrv2NibNeighborSetNWillFlooding
2203 WillingnessTC,
2204 olsrv2NibNeighborSetNWillRouting
2205 WillingnessTC,
2206 olsrv2NibNeighborSetNFloodingMpr
2207 TruthValue,
2208 olsrv2NibNeighborSetNRoutingMpr
2209 TruthValue,
2210 olsrv2NibNeighborSetNMprSelector
2211 TruthValue,
2212 olsrv2NibNeighborSetNAdvertised
2213 TruthValue
2214 }
2215
2216 olsrv2NibNeighborSetNOrigIpAddrType OBJECT-TYPE
2217 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2218 MAX-ACCESS read-only
2219 STATUS current
2220 DESCRIPTION
2221 "The type of the olsrv2NibNeighborSetNOrigIpAddr, as defined
2222 in the InetAddress MIB module (<a href="./rfc4001">RFC4001</a>).
2223
2224 Only the values 'ipv4(1)' and
2225 'ipv6(2)' are supported."
2226 REFERENCE
2227 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2228 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2229 and U. Herberg, April 2014."
2230 ::= { olsrv2NibNeighborSetEntry 1 }
2231
2232 olsrv2NibNeighborSetNOrigIpAddr OBJECT-TYPE
2233
2234
2235
2236 <span class="grey">Herberg, et al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2239
2240
2241 SYNTAX InetAddress (SIZE(4|16))
2242 MAX-ACCESS read-only
2243 STATUS current
2244 DESCRIPTION
2245 "This is the originator IP address of the neighbor
2246 represented by this table entry."
2247 REFERENCE
2248 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2249 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2250 and U. Herberg, April 2014."
2251 ::= { olsrv2NibNeighborSetEntry 2 }
2252
2253 olsrv2NibNeighborSetNInMetricValue OBJECT-TYPE
2254 SYNTAX Olsrv2MetricValueCompressedFormTC
2255 MAX-ACCESS read-only
2256 STATUS current
2257 DESCRIPTION
2258 "This object is the neighbor metric of any
2259 link from this neighbor to an OLSRv2 interface
2260 of this router, i.e., the minimum of all corresponding
2261 L_in_metric (olsrv2IibLinkSetInMetricValue)
2262 with L_status = SYMMETRIC and
2263 L_in_metric (olsrv2IibLinkSetInMetricValue) != UNKNOWN_METRIC,
2264 UNKNOWN_METRIC if there are no such Link Tuples.
2265 UNKNOWN_METRIC has a value of 0."
2266 REFERENCE
2267 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2268 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2269 and U. Herberg, April 2014."
2270 ::= { olsrv2NibNeighborSetEntry 3 }
2271
2272 olsrv2NibNeighborSetNOutMetricValue OBJECT-TYPE
2273 SYNTAX Olsrv2MetricValueCompressedFormTC
2274 MAX-ACCESS read-only
2275 STATUS current
2276 DESCRIPTION
2277 "This object is the neighbor metric of any
2278 link from an OLSRv2 interface of this router
2279 to this neighbor, i.e., the minimum of all
2280 corresponding L_out_metric
2281 (olsrv2IibLinkSetOutMetricValue) with L_status =
2282 SYMMETRIC and L_out_metric
2283 (olsrv2IibLinkSetOutMetricValue) != UNKNOWN_METRIC,
2284 UNKNOWN_METRIC if there are no such Link Tuples.
2285 UNKNOWN_METRIC has a value of 0."
2286 REFERENCE
2287 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2288 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2289
2290
2291
2292 <span class="grey">Herberg, et al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2295
2296
2297 and U. Herberg, April 2014."
2298 ::= { olsrv2NibNeighborSetEntry 4 }
2299
2300 olsrv2NibNeighborSetNWillFlooding OBJECT-TYPE
2301 SYNTAX WillingnessTC
2302 MAX-ACCESS read-only
2303 STATUS current
2304 DESCRIPTION
2305 "This object is the neighbor's willingness to be
2306 selected as a flooding MPR, in the range from
2307 WILL_NEVER to WILL_ALWAYS, both inclusive, taking
2308 the value WILL_NEVER if no OLSRv2 specific
2309 information is received from this neighbor."
2310 REFERENCE
2311 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2312 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2313 and U. Herberg, April 2014."
2314 ::= { olsrv2NibNeighborSetEntry 5 }
2315
2316 olsrv2NibNeighborSetNWillRouting OBJECT-TYPE
2317 SYNTAX WillingnessTC
2318 MAX-ACCESS read-only
2319 STATUS current
2320 DESCRIPTION
2321 "This object is the neighbor's willingness to be
2322 selected as a routing MPR, in the range from
2323 WILL_NEVER to WILL_ALWAYS, both inclusive, taking
2324 the value WILL_NEVER if no OLSRv2 specific
2325 information is received from this neighbor."
2326 REFERENCE
2327 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2328 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2329 and U. Herberg, April 2014."
2330 ::= { olsrv2NibNeighborSetEntry 6 }
2331
2332 olsrv2NibNeighborSetNFloodingMpr OBJECT-TYPE
2333 SYNTAX TruthValue
2334 MAX-ACCESS read-only
2335 STATUS current
2336 DESCRIPTION
2337 "This object is a boolean flag, recording whether
2338 this neighbor is selected as a flooding MPR
2339 by this router."
2340 REFERENCE
2341 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2342 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2343 and U. Herberg, April 2014."
2344 ::= { olsrv2NibNeighborSetEntry 7 }
2345
2346
2347
2348 <span class="grey">Herberg, et al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2351
2352
2353 olsrv2NibNeighborSetNRoutingMpr OBJECT-TYPE
2354 SYNTAX TruthValue
2355 MAX-ACCESS read-only
2356 STATUS current
2357 DESCRIPTION
2358 "This object is a boolean flag, recording whether
2359 this neighbor is selected as a routing MPR
2360 by this router."
2361 REFERENCE
2362 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2363 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2364 and U. Herberg, April 2014."
2365 ::= { olsrv2NibNeighborSetEntry 8 }
2366
2367 olsrv2NibNeighborSetNMprSelector OBJECT-TYPE
2368 SYNTAX TruthValue
2369 MAX-ACCESS read-only
2370 STATUS current
2371 DESCRIPTION
2372 "This object is a boolean flag,
2373 recording whether this neighbor has selected this router
2374 as a routing MPR, i.e., is a routing MPR
2375 selector of this router.
2376
2377 When set to 'true', then this router is selected as
2378 a routing MPR by the neighbor router.
2379 When set to 'false',
2380 then this router is not selected by the neighbor
2381 as a routing MPR."
2382 REFERENCE
2383 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2384 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2385 and U. Herberg, April 2014."
2386 ::= { olsrv2NibNeighborSetEntry 9 }
2387
2388 olsrv2NibNeighborSetNAdvertised OBJECT-TYPE
2389 SYNTAX TruthValue
2390 MAX-ACCESS read-only
2391 STATUS current
2392 DESCRIPTION
2393 "This object, N_mpr_selector
2394 (olsrv2NibNeighborSetNMprSelector), is a boolean flag,
2395 recording whether this router has elected to
2396 advertise a link to this neighbor in its TC messages."
2397 REFERENCE
2398 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2399 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2400 and U. Herberg, April 2014."
2401
2402
2403
2404 <span class="grey">Herberg, et al. Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2407
2408
2409 ::= { olsrv2NibNeighborSetEntry 10 }
2410
2411 olsrv2NibNeighborSetTableAnsn OBJECT-TYPE
2412 SYNTAX Unsigned32 (0..65535)
2413 MAX-ACCESS read-only
2414 STATUS current
2415 DESCRIPTION
2416 "Advertised Neighbor Sequence Number (ANSN), is
2417 a variable, whose value is included in TC messages to
2418 indicate the freshness of the information transmitted."
2419 REFERENCE
2420 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2421 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2422 and U. Herberg, April 2014."
2423 ::= { olsrv2StateGroup 6 }
2424
2425 --
2426 -- Topology Information Base - this Information
2427 -- Base is specific to OLSRv2 and is defined in
2428 -- <a href="./rfc7181#section-10">Section&nbsp;10 of RFC 7181</a>.
2429 --
2430
2431 --
2432 -- Advertising Remote Router Set
2433 --
2434
2435 olsrv2TibAdRemoteRouterSetTable OBJECT-TYPE
2436 SYNTAX SEQUENCE OF Olsrv2TibAdRemoteRouterSetEntry
2437 MAX-ACCESS not-accessible
2438 STATUS current
2439 DESCRIPTION
2440 "A router's Advertising Remote Router Set records
2441 information describing each remote router in the
2442 network that transmits TC messages."
2443 REFERENCE
2444 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2445 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2446 and U. Herberg, April 2014."
2447 ::= { olsrv2StateGroup 7 }
2448
2449 olsrv2TibAdRemoteRouterSetEntry OBJECT-TYPE
2450 SYNTAX Olsrv2TibAdRemoteRouterSetEntry
2451 MAX-ACCESS not-accessible
2452 STATUS current
2453 DESCRIPTION
2454 "A router's Advertised Neighbor Set Table entry
2455 consists of Advertising Remote Router Tuples:
2456
2457
2458
2459
2460 <span class="grey">Herberg, et al. Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2463
2464
2465 (AR_orig_addr (olsrv2TibAdRemoteRouterSetIpAddrType,
2466 olsrv2TibAdRemoteRouterSetIpAddr),
2467 AR_seq_number (olsrv2TibAdRemoteRouterSetMaxSeqNo),
2468 AR_time (olsrv2TibAdRemoteRouterSetExpireTime).
2469
2470 Addresses associated with this router are
2471 found in the NHDP-MIB module's nhdpDiscIfSetTable.
2472
2473 OLSRv2 (<a href="./rfc7181">RFC 7181</a>) defines the rules for managing
2474 entries within this table, e.g., populating
2475 and purging entries. Specific instructions for the
2476 olsrv2TibAdRemoteRouterSetEntry(s) are found in
2477 <a href="#section-10.1">Section 10.1</a> and <a href="#section-17">Section 17</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
2478 REFERENCE
2479 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2480 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2481 and U. Herberg, April 2014."
2482 INDEX { olsrv2TibAdRemoteRouterSetIpAddrType,
2483 olsrv2TibAdRemoteRouterSetIpAddr }
2484 ::= { olsrv2TibAdRemoteRouterSetTable 1 }
2485
2486 Olsrv2TibAdRemoteRouterSetEntry ::=
2487 SEQUENCE {
2488 olsrv2TibAdRemoteRouterSetIpAddrType
2489 InetAddressType,
2490 olsrv2TibAdRemoteRouterSetIpAddr
2491 InetAddress,
2492 olsrv2TibAdRemoteRouterSetMaxSeqNo
2493 Unsigned32,
2494 olsrv2TibAdRemoteRouterSetExpireTime
2495 TimeStamp
2496 }
2497
2498 olsrv2TibAdRemoteRouterSetIpAddrType OBJECT-TYPE
2499 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2500 MAX-ACCESS not-accessible
2501 STATUS current
2502 DESCRIPTION
2503 "The type of the olsrv2TibAdRemoteRouterSetIpAddr,
2504 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC4001</a>).
2505
2506 Only the values 'ipv4(1)' and
2507 'ipv6(2)' are supported."
2508 REFERENCE
2509 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2510 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2511 and U. Herberg, April 2014."
2512 ::= { olsrv2TibAdRemoteRouterSetEntry 1 }
2513
2514
2515
2516 <span class="grey">Herberg, et al. Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2519
2520
2521 olsrv2TibAdRemoteRouterSetIpAddr OBJECT-TYPE
2522 SYNTAX InetAddress (SIZE(4|16))
2523 MAX-ACCESS not-accessible
2524 STATUS current
2525 DESCRIPTION
2526 "This is the originator address of a received
2527 TC message."
2528 REFERENCE
2529 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2530 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2531 and U. Herberg, April 2014."
2532 ::= { olsrv2TibAdRemoteRouterSetEntry 2 }
2533
2534 olsrv2TibAdRemoteRouterSetMaxSeqNo OBJECT-TYPE
2535 SYNTAX Unsigned32 (0..65535)
2536 MAX-ACCESS read-only
2537 STATUS current
2538 DESCRIPTION
2539 "This is the greatest Advertised Neighbor Sequence
2540 Number (ANSN) in any TC message
2541 received that originated from the router
2542 with originator address
2543 olsrv2TibAdRemoteRouterSetIpAddr.
2544
2545 Sequence numbers are used in the OLSRv2 protocol
2546 for the purpose of discarding 'old' information,
2547 i.e., messages received out of order. However,
2548 with a limited number of bits for representing
2549 sequence numbers, wraparound (that the sequence
2550 number is incremented from the maximum possible
2551 value to zero) will occur. To prevent this from
2552 interfering with the operation of this protocol,
2553 OLSRv2 implementations observe the following when
2554 determining the ordering of sequence numbers.
2555
2556 In OLSRv2, MAXVALUE designates one more than the
2557 largest possible value for a sequence number.
2558 For a 16-bit sequence number, MAXVALUE is 65536.
2559
2560 The sequence number S1 is said to be 'greater than'
2561 the sequence number S2 if:
2562
2563 o S1 &gt; S2 AND S1 - S2 &lt; MAXVALUE/2 OR
2564
2565 o S2 &gt; S1 AND S2 - S1 &gt; MAXVALUE/2
2566
2567 When sequence numbers S1 and S2 differ by MAXVALUE/2,
2568 their ordering cannot be determined. In this case,
2569
2570
2571
2572 <span class="grey">Herberg, et al. Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2575
2576
2577 which should not occur, either ordering may be
2578 assumed.
2579
2580 Thus, when comparing two messages, it is possible
2581 - even in the presence of wraparound - to determine
2582 which message contains the most recent information."
2583 REFERENCE
2584 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2585 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2586 and U. Herberg, April 2014."
2587 ::= { olsrv2TibAdRemoteRouterSetEntry 3 }
2588
2589 olsrv2TibAdRemoteRouterSetExpireTime OBJECT-TYPE
2590 SYNTAX TimeStamp
2591 UNITS "centiseconds"
2592 MAX-ACCESS read-only
2593 STATUS current
2594 DESCRIPTION
2595 "olsrv2TibAdRemoteRouterSetExpireTime specifies the value
2596 of sysUptime when this entry SHOULD expire and be
2597 removed from the olsrv2TibAdRemoteRouterSetTable."
2598 REFERENCE
2599 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2600 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2601 and U. Herberg, April 2014."
2602 ::= { olsrv2TibAdRemoteRouterSetEntry 4 }
2603
2604 --
2605 -- Router Topology Set
2606 --
2607
2608 olsrv2TibRouterTopologySetTable OBJECT-TYPE
2609 SYNTAX SEQUENCE OF Olsrv2TibRouterTopologySetEntry
2610 MAX-ACCESS not-accessible
2611 STATUS current
2612 DESCRIPTION
2613 "A router's Router Topology Set records topology
2614 information about the network."
2615 REFERENCE
2616 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2617 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2618 and U. Herberg, April 2014."
2619 ::= { olsrv2StateGroup 8 }
2620
2621 olsrv2TibRouterTopologySetEntry OBJECT-TYPE
2622 SYNTAX Olsrv2TibRouterTopologySetEntry
2623 MAX-ACCESS not-accessible
2624 STATUS current
2625
2626
2627
2628 <span class="grey">Herberg, et al. Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2631
2632
2633 DESCRIPTION
2634 "It consists of Router Topology Tuples:
2635
2636 (TR_from_orig_addr
2637 (olsrv2TibRouterTopologySetFromOrigIpAddrType,
2638 olsrv2TibRouterTopologySetFromOrigIpAddr),
2639 TR_to_orig_addr
2640 (olsrv2TibRouterTopologySetToOrigIpAddrType,
2641 olsrv2TibRouterTopologySetToOrigIpAddr),
2642 TR_seq_number (olsrv2TibRouterTopologySetSeqNo),
2643 TR_metric (olsrv2TibRouterTopologySetMetricValue),
2644 TR_time (olsrv2TibRouterTopologySetExpireTime)).
2645
2646 OLSRv2 (<a href="./rfc7181">RFC 7181</a>) defines the rules for managing
2647 entries within this table, e.g., populating
2648 and purging entries. Specific instructions for the
2649 olsrv2TibRouterTopologySetEntry(s) are found in
2650 <a href="#section-10.2">Section 10.2</a> and <a href="#section-17">Section 17</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
2651 REFERENCE
2652 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2653 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2654 and U. Herberg, April 2014."
2655 INDEX { olsrv2TibRouterTopologySetFromOrigIpAddrType,
2656 olsrv2TibRouterTopologySetFromOrigIpAddr,
2657 olsrv2TibRouterTopologySetToOrigIpAddrType,
2658 olsrv2TibRouterTopologySetToOrigIpAddr }
2659 ::= { olsrv2TibRouterTopologySetTable 1 }
2660
2661 Olsrv2TibRouterTopologySetEntry ::=
2662 SEQUENCE {
2663 olsrv2TibRouterTopologySetFromOrigIpAddrType
2664 InetAddressType,
2665 olsrv2TibRouterTopologySetFromOrigIpAddr
2666 InetAddress,
2667 olsrv2TibRouterTopologySetToOrigIpAddrType
2668 InetAddressType,
2669 olsrv2TibRouterTopologySetToOrigIpAddr
2670 InetAddress,
2671 olsrv2TibRouterTopologySetSeqNo
2672 Unsigned32,
2673 olsrv2TibRouterTopologySetMetricValue
2674 Olsrv2MetricValueCompressedFormTC,
2675 olsrv2TibRouterTopologySetExpireTime
2676 TimeStamp
2677 }
2678
2679 olsrv2TibRouterTopologySetFromOrigIpAddrType OBJECT-TYPE
2680 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2681
2682
2683
2684 <span class="grey">Herberg, et al. Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2687
2688
2689 MAX-ACCESS not-accessible
2690 STATUS current
2691 DESCRIPTION
2692 "The type of the olsrv2TibRouterTopologySetFromOrigIpAddr,
2693 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC4001</a>).
2694
2695 Only the values 'ipv4(1)' and
2696 'ipv6(2)' are supported."
2697 REFERENCE
2698 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2699 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2700 and U. Herberg, April 2014."
2701 ::= { olsrv2TibRouterTopologySetEntry 1 }
2702
2703 olsrv2TibRouterTopologySetFromOrigIpAddr OBJECT-TYPE
2704 SYNTAX InetAddress (SIZE(4|16))
2705 MAX-ACCESS not-accessible
2706 STATUS current
2707 DESCRIPTION
2708 "This is the originator address of a router that can
2709 reach the router with originator address TR_to_orig_addr
2710 in one hop."
2711 REFERENCE
2712 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2713 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2714 and U. Herberg, April 2014."
2715 ::= { olsrv2TibRouterTopologySetEntry 2 }
2716
2717 olsrv2TibRouterTopologySetToOrigIpAddrType OBJECT-TYPE
2718 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2719 MAX-ACCESS not-accessible
2720 STATUS current
2721 DESCRIPTION
2722 "The type of the olsrv2TibRouterTopologySetToOrigIpAddr,
2723 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC4001</a>).
2724
2725 Only the values 'ipv4(1)' and
2726 'ipv6(2)' are supported."
2727 REFERENCE
2728 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2729 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2730 and U. Herberg, April 2014."
2731 ::= { olsrv2TibRouterTopologySetEntry 3 }
2732
2733 olsrv2TibRouterTopologySetToOrigIpAddr OBJECT-TYPE
2734 SYNTAX InetAddress (SIZE(4|16))
2735 MAX-ACCESS not-accessible
2736 STATUS current
2737
2738
2739
2740 <span class="grey">Herberg, et al. Standards Track [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2743
2744
2745 DESCRIPTION
2746 "This is the originator address of a router that can be
2747 reached by the router with originator address
2748 TR_to_orig_addr in one hop."
2749 REFERENCE
2750 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2751 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2752 and U. Herberg, April 2014."
2753 ::= { olsrv2TibRouterTopologySetEntry 4 }
2754
2755 olsrv2TibRouterTopologySetSeqNo OBJECT-TYPE
2756 SYNTAX Unsigned32 (0..65535)
2757 MAX-ACCESS read-only
2758 STATUS current
2759 DESCRIPTION
2760 "This is the greatest Advertised Neighbor Sequence
2761 Number (ANSN) in any TC message
2762 received that originated from the router
2763 with originator address TR_from_orig_addr,
2764 i.e., that contributed to the information
2765 contained in this Tuple and that is defined by the
2766 objects:
2767 (olsrv2TibRouterTopologySetFromOrigIpAddrType,
2768 olsrv2TibRouterTopologySetFromOrigIpAddr).
2769
2770 Sequence numbers are used in the OLSRv2 protocol
2771 for the purpose of discarding 'old' information,
2772 i.e., messages received out of order. However,
2773 with a limited number of bits for representing
2774 sequence numbers, wraparound (that the sequence
2775 number is incremented from the maximum possible
2776 value to zero) will occur. To prevent this from
2777 interfering with the operation of this protocol,
2778 OLSRv2 implementations observe the following when
2779 determining the ordering of sequence numbers.
2780
2781 In OLSRv2, MAXVALUE designates one more than the
2782 largest possible value for a sequence number.
2783 For a 16-bit sequence number, MAXVALUE is 65536.
2784
2785 The sequence number S1 is said to be 'greater than'
2786 the sequence number S2 if:
2787
2788 o S1 &gt; S2 AND S1 - S2 &lt; MAXVALUE/2 OR
2789
2790 o S2 &gt; S1 AND S2 - S1 &gt; MAXVALUE/2
2791
2792 When sequence numbers S1 and S2 differ by MAXVALUE/2,
2793
2794
2795
2796 <span class="grey">Herberg, et al. Standards Track [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2799
2800
2801 their ordering cannot be determined. In this case,
2802 which should not occur, either ordering may be
2803 assumed.
2804
2805 Thus, when comparing two messages, it is possible
2806 - even in the presence of wraparound - to determine
2807 which message contains the most recent information."
2808 REFERENCE
2809 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2810 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2811 and U. Herberg, April 2014."
2812 ::= { olsrv2TibRouterTopologySetEntry 5 }
2813
2814 olsrv2TibRouterTopologySetMetricValue OBJECT-TYPE
2815 SYNTAX Olsrv2MetricValueCompressedFormTC
2816 MAX-ACCESS read-only
2817 STATUS current
2818 DESCRIPTION
2819 "This is the neighbor metric from the router
2820 with originator address TR_from_orig_addr
2821 (olsrv2TibRouterTopologySetFromOrigIpAddrType,
2822 olsrv2TibRouterTopologySetFromOrigIpAddr) to
2823 the router with originator address TR_to_orig_addr
2824 (olsrv2TibRouterTopologySetToOrigIpAddrType,
2825 olsrv2TibRouterTopologySetToOrigIpAddr)."
2826 REFERENCE
2827 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2828 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2829 and U. Herberg, April 2014."
2830 ::= { olsrv2TibRouterTopologySetEntry 6 }
2831
2832 olsrv2TibRouterTopologySetExpireTime OBJECT-TYPE
2833 SYNTAX TimeStamp
2834 UNITS "centiseconds"
2835 MAX-ACCESS read-only
2836 STATUS current
2837 DESCRIPTION
2838 "olsrv2TibRouterTopologySetExpireTime specifies the value
2839 of sysUptime when this entry SHOULD expire and be
2840 removed from the olsrv2TibRouterTopologySetTable."
2841 REFERENCE
2842 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2843 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2844 and U. Herberg, April 2014."
2845 ::= { olsrv2TibRouterTopologySetEntry 7 }
2846
2847 --
2848 -- Routable Address Topology Set
2849
2850
2851
2852 <span class="grey">Herberg, et al. Standards Track [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2855
2856
2857 --
2858
2859 olsrv2TibRoutableAddressTopologySetTable OBJECT-TYPE
2860 SYNTAX SEQUENCE OF Olsrv2TibRoutableAddressTopologySetEntry
2861 MAX-ACCESS not-accessible
2862 STATUS current
2863 DESCRIPTION
2864 "A router's Routable Address Topology Set records topology
2865 information about the routable addresses within the MANET,
2866 including via which routers they may be reached."
2867 REFERENCE
2868 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2869 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2870 and U. Herberg, April 2014."
2871 ::= { olsrv2StateGroup 9 }
2872
2873 olsrv2TibRoutableAddressTopologySetEntry OBJECT-TYPE
2874 SYNTAX Olsrv2TibRoutableAddressTopologySetEntry
2875 MAX-ACCESS not-accessible
2876 STATUS current
2877 DESCRIPTION
2878 "It consists of Router Topology Tuples:
2879
2880 (TA_from_orig_addr
2881 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType
2882 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr),
2883 TA_dest_addr
2884 (olsrv2TibRoutableAddressTopologySetFromDestIpAddrType
2885 olsrv2TibRoutableAddressTopologySetFromDestIpAddr),
2886 TA_seq_number (olsrv2TibRoutableAddressTopologySetSeqNo)
2887 TA_metric (olsrv2TibRoutableAddressTopologySetMetricValue)
2888 TA_time (olsrv2TibRoutableAddressTopologySetExpireTime)
2889 )
2890
2891 OLSRv2 (<a href="./rfc7181">RFC 7181</a>) defines the rules for managing
2892 entries within this table, e.g., populating
2893 and purging entries. Specific instructions for the
2894 olsrv2TibRoutableAddressTopologySetEntry(s) are found
2895 in <a href="#section-10.3">Section 10.3</a> and <a href="#section-17">Section 17</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
2896 REFERENCE
2897 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2898 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2899 and U. Herberg, April 2014."
2900 INDEX { olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType,
2901 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr,
2902 olsrv2TibRoutableAddressTopologySetDestIpAddrType,
2903 olsrv2TibRoutableAddressTopologySetDestIpAddr }
2904 ::= { olsrv2TibRoutableAddressTopologySetTable 1 }
2905
2906
2907
2908 <span class="grey">Herberg, et al. Standards Track [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2911
2912
2913 Olsrv2TibRoutableAddressTopologySetEntry ::=
2914 SEQUENCE {
2915 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType
2916 InetAddressType,
2917 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr
2918 InetAddress,
2919 olsrv2TibRoutableAddressTopologySetDestIpAddrType
2920 InetAddressType,
2921 olsrv2TibRoutableAddressTopologySetDestIpAddr
2922 InetAddress,
2923 olsrv2TibRoutableAddressTopologySetSeqNo
2924 Unsigned32,
2925 olsrv2TibRoutableAddressTopologySetMetricValue
2926 Olsrv2MetricValueCompressedFormTC,
2927 olsrv2TibRoutableAddressTopologySetExpireTime
2928 TimeStamp
2929 }
2930
2931 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType OBJECT-TYPE
2932 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2933 MAX-ACCESS not-accessible
2934 STATUS current
2935 DESCRIPTION
2936 "The type of the
2937 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr,
2938 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
2939
2940 Only the values 'ipv4(1)' and
2941 'ipv6(2)' are supported."
2942 REFERENCE
2943 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2944 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2945 and U. Herberg, April 2014."
2946 ::= { olsrv2TibRoutableAddressTopologySetEntry 1 }
2947
2948 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr OBJECT-TYPE
2949 SYNTAX InetAddress (SIZE(4|16))
2950 MAX-ACCESS not-accessible
2951 STATUS current
2952 DESCRIPTION
2953 "This is the originator address of a router that can
2954 reach the router with routable address TA_dest_addr
2955 in one hop."
2956 REFERENCE
2957 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2958 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2959 and U. Herberg, April 2014."
2960 ::= { olsrv2TibRoutableAddressTopologySetEntry 2 }
2961
2962
2963
2964 <span class="grey">Herberg, et al. Standards Track [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
2967
2968
2969 olsrv2TibRoutableAddressTopologySetDestIpAddrType OBJECT-TYPE
2970 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
2971 MAX-ACCESS not-accessible
2972 STATUS current
2973 DESCRIPTION
2974 "The type of the olsrv2TibRouterTopologySetToOrigIpAddr,
2975 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
2976
2977 Only the values 'ipv4(1)' and
2978 'ipv6(2)' are supported."
2979 REFERENCE
2980 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2981 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2982 and U. Herberg, April 2014."
2983 ::= { olsrv2TibRoutableAddressTopologySetEntry 3 }
2984
2985 olsrv2TibRoutableAddressTopologySetDestIpAddr OBJECT-TYPE
2986 SYNTAX InetAddress (SIZE(4|16))
2987 MAX-ACCESS not-accessible
2988 STATUS current
2989 DESCRIPTION
2990 "This is a routable address of a router that can be
2991 reached by the router with originator address
2992 TA_from_orig_addr in one hop. The TA_from_orig_addr
2993 is defined by the tuple
2994 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType
2995 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr)."
2996 REFERENCE
2997 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
2998 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
2999 and U. Herberg, April 2014."
3000 ::= { olsrv2TibRoutableAddressTopologySetEntry 4 }
3001
3002 olsrv2TibRoutableAddressTopologySetSeqNo OBJECT-TYPE
3003 SYNTAX Unsigned32 (0..65535)
3004 MAX-ACCESS read-only
3005 STATUS current
3006 DESCRIPTION
3007 "This is the greatest Advertised Neighbor Sequence
3008 Number (ANSN) in any TC message
3009 received that originated from the router
3010 with originator address TA_from_orig_addr,
3011 i.e., that contributed to the information
3012 contained in this Tuple. The TA_from_orig_addr
3013 is defined by the tuple
3014 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType
3015 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr)."
3016 REFERENCE
3017
3018
3019
3020 <span class="grey">Herberg, et al. Standards Track [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3023
3024
3025 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3026 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3027 and U. Herberg, April 2014."
3028 ::= { olsrv2TibRoutableAddressTopologySetEntry 5 }
3029
3030 olsrv2TibRoutableAddressTopologySetMetricValue OBJECT-TYPE
3031 SYNTAX Olsrv2MetricValueCompressedFormTC
3032 MAX-ACCESS read-only
3033 STATUS current
3034 DESCRIPTION
3035 "This is the neighbor metric from the router
3036 with originator address TA_from_orig_addr (defined
3037 by the tuple
3038 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType
3039 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr))
3040 to the router with OLSRv2 interface address TA_dest_addr
3041 (defined by the tuple
3042 (olsrv2TibRoutableAddressTopologySetFromDestIpAddrType
3043 olsrv2TibRoutableAddressTopologySetFromDestIpAddr))."
3044 REFERENCE
3045 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3046 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3047 and U. Herberg, April 2014."
3048 ::= { olsrv2TibRoutableAddressTopologySetEntry 6 }
3049
3050 olsrv2TibRoutableAddressTopologySetExpireTime OBJECT-TYPE
3051 SYNTAX TimeStamp
3052 UNITS "centiseconds"
3053 MAX-ACCESS read-only
3054 STATUS current
3055 DESCRIPTION
3056 "olsrv2TibRoutableAddressTopologySetExpireTime
3057 specifies the value of sysUptime when this entry
3058 SHOULD expire and be removed from the
3059 olsrv2TibRoutableAddressTopologySetTable."
3060 REFERENCE
3061 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3062 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3063 and U. Herberg, April 2014."
3064 ::= { olsrv2TibRoutableAddressTopologySetEntry 7 }
3065
3066 --
3067 -- Attached Network Set
3068 --
3069
3070 olsrv2TibAttNetworksSetTable OBJECT-TYPE
3071 SYNTAX SEQUENCE OF Olsrv2TibAttNetworksSetEntry
3072 MAX-ACCESS not-accessible
3073
3074
3075
3076 <span class="grey">Herberg, et al. Standards Track [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3079
3080
3081 STATUS current
3082 DESCRIPTION
3083 "A router's Attached Network Set records information
3084 about networks (which may be outside the MANET)
3085 attached to other routers and their routable addresses."
3086 REFERENCE
3087 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3088 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3089 and U. Herberg, April 2014."
3090 ::= { olsrv2StateGroup 10 }
3091
3092 olsrv2TibAttNetworksSetEntry OBJECT-TYPE
3093 SYNTAX Olsrv2TibAttNetworksSetEntry
3094 MAX-ACCESS not-accessible
3095 STATUS current
3096 DESCRIPTION
3097 "It consists of Attached Network Tuples:
3098
3099 (AN_orig_addr
3100 (olsrv2TibAttNetworksSetOrigIpAddrType,
3101 olsrv2TibAttNetworksSetOrigIpAddr),
3102 AN_net_addr
3103 (olsrv2TibAttNetworksSetNetIpAddrType,
3104 olsrv2TibAttNetworksSetNetIpAddr,
3105 olsrv2TibAttNetworksSetNetIpAddrPrefixLen),
3106 AN_seq_number (olsrv2TibAttNetworksSetSeqNo),
3107 AN_dist (olsrv2TibAttNetworksSetDist),
3108 AN_metric (olsrv2TibAttNetworksSetMetricValue),
3109 AN_time (olsrv2TibAttNetworksSetExpireTime)
3110 )
3111
3112 OLSRv2 (<a href="./rfc7181">RFC 7181</a>) defines the rules for managing
3113 entries within this table, e.g., populating
3114 and purging entries. Specific instructions for the
3115 olsrv2TibRoutableAddressTopologySetEntry(s) are found
3116 in <a href="#section-10.4">Section 10.4</a> and <a href="#section-17">Section 17</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
3117 REFERENCE
3118 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3119 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3120 and U. Herberg, April 2014."
3121 INDEX { olsrv2TibAttNetworksSetOrigIpAddrType,
3122 olsrv2TibAttNetworksSetOrigIpAddr,
3123 olsrv2TibAttNetworksSetNetIpAddrType,
3124 olsrv2TibAttNetworksSetNetIpAddr,
3125 olsrv2TibAttNetworksSetNetIpAddrPrefixLen }
3126 ::= { olsrv2TibAttNetworksSetTable 1 }
3127
3128 Olsrv2TibAttNetworksSetEntry ::=
3129
3130
3131
3132 <span class="grey">Herberg, et al. Standards Track [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3135
3136
3137 SEQUENCE {
3138 olsrv2TibAttNetworksSetOrigIpAddrType
3139 InetAddressType,
3140 olsrv2TibAttNetworksSetOrigIpAddr
3141 InetAddress,
3142 olsrv2TibAttNetworksSetNetIpAddrType
3143 InetAddressType,
3144 olsrv2TibAttNetworksSetNetIpAddr
3145 InetAddress,
3146 olsrv2TibAttNetworksSetNetIpAddrPrefixLen
3147 InetAddressPrefixLength,
3148 olsrv2TibAttNetworksSetSeqNo
3149 Unsigned32,
3150 olsrv2TibAttNetworksSetDist
3151 Unsigned32,
3152 olsrv2TibAttNetworksSetMetricValue
3153 Olsrv2MetricValueCompressedFormTC,
3154 olsrv2TibAttNetworksSetExpireTime
3155 TimeStamp
3156 }
3157
3158 olsrv2TibAttNetworksSetOrigIpAddrType OBJECT-TYPE
3159 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
3160 MAX-ACCESS not-accessible
3161 STATUS current
3162 DESCRIPTION
3163 "The type of the olsrv2TibAttNetworksSetOrigIpAddr,
3164 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC4001</a>).
3165
3166 Only the values 'ipv4(1)' and
3167 'ipv6(2)' are supported."
3168 REFERENCE
3169 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3170 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3171 and U. Herberg, April 2014."
3172 ::= { olsrv2TibAttNetworksSetEntry 1 }
3173
3174 olsrv2TibAttNetworksSetOrigIpAddr OBJECT-TYPE
3175 SYNTAX InetAddress (SIZE(4|16))
3176 MAX-ACCESS not-accessible
3177 STATUS current
3178 DESCRIPTION
3179 "This is the originator address, of type
3180 olsrv2TibAttNetworksSetOrigIpAddrType, of a
3181 router that can act as gateway to the
3182 network with address AN_net_addr. The
3183 AN_net_addr is defined by the tuple
3184 (olsrv2TibAttNetworksSetNetIpAddrType,
3185
3186
3187
3188 <span class="grey">Herberg, et al. Standards Track [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3191
3192
3193 olsrv2TibAttNetworksSetNetIpAddr,
3194 olsrv2TibAttNetworksSetNetIpAddrPrefixLen)."
3195 REFERENCE
3196 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3197 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3198 and U. Herberg, April 2014."
3199 ::= { olsrv2TibAttNetworksSetEntry 2 }
3200
3201 olsrv2TibAttNetworksSetNetIpAddrType OBJECT-TYPE
3202 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
3203 MAX-ACCESS not-accessible
3204 STATUS current
3205 DESCRIPTION
3206 "The type of the olsrv2TibAttNetworksSetNetIpAddr,
3207 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
3208
3209 Only the values 'ipv4(1)' and
3210 'ipv6(2)' are supported."
3211 REFERENCE
3212 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3213 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3214 and U. Herberg, April 2014."
3215 ::= { olsrv2TibAttNetworksSetEntry 3 }
3216
3217 olsrv2TibAttNetworksSetNetIpAddr OBJECT-TYPE
3218 SYNTAX InetAddress (SIZE(4|16))
3219 MAX-ACCESS not-accessible
3220 STATUS current
3221 DESCRIPTION
3222 "This is the network address, of type
3223 olsrv2TibAttNetworksSetNetIpAddrType, of an
3224 attached network, that may be reached via
3225 the router with originator address AN_orig_addr.
3226 The AN_orig_addr is defined by the tuple
3227 (olsrv2TibAttNetworksSetOrigIpAddrType,
3228 olsrv2TibAttNetworksSetOrigIpAddr)."
3229 REFERENCE
3230 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3231 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3232 and U. Herberg, April 2014."
3233 ::= { olsrv2TibAttNetworksSetEntry 4 }
3234
3235 olsrv2TibAttNetworksSetNetIpAddrPrefixLen OBJECT-TYPE
3236 SYNTAX InetAddressPrefixLength
3237 UNITS "bits"
3238 MAX-ACCESS not-accessible
3239 STATUS current
3240 DESCRIPTION
3241
3242
3243
3244 <span class="grey">Herberg, et al. Standards Track [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3247
3248
3249 "Indicates the number of leading one bits that form the
3250 mask to be logically ANDed with the destination address
3251 before being compared to the value in the
3252 olsrv2TibAttNetworksSetNetIpAddr field."
3253 REFERENCE
3254 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3255 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3256 and U. Herberg, April 2014."
3257 ::= { olsrv2TibAttNetworksSetEntry 5 }
3258
3259 olsrv2TibAttNetworksSetSeqNo OBJECT-TYPE
3260 SYNTAX Unsigned32 (0..65535)
3261 MAX-ACCESS read-only
3262 STATUS current
3263 DESCRIPTION
3264 "This is the greatest Advertised Neighbor Sequence
3265 Number (ANSN) in any TC message received
3266 that originated from the router
3267 with originator address AN_orig_addr
3268 (i.e., that contributed to the information
3269 contained in this Tuple). The AN_orig_addr
3270 is defined by the tuple
3271 (olsrv2TibAttNetworksSetOrigIpAddrType,
3272 olsrv2TibAttNetworksSetOrigIpAddr).
3273
3274 Sequence numbers are used in the OLSRv2 protocol
3275 for the purpose of discarding 'old' information,
3276 i.e., messages received out of order. However,
3277 with a limited number of bits for representing
3278 sequence numbers, wraparound (that the sequence
3279 number is incremented from the maximum possible
3280 value to zero) will occur. To prevent this from
3281 interfering with the operation of this protocol,
3282 the following MUST be observed when determining
3283 the ordering of sequence numbers.
3284
3285 The term MAXVALUE designates in the following one
3286 more than the largest possible value for a sequence
3287 number. For a 16-bit sequence number (as are those
3288 defined in this specification), MAXVALUE is 65536.
3289
3290 The sequence number S1 is said to be 'greater than'
3291 the sequence number S2 if:
3292
3293 o S1 &gt; S2 AND S1 - S2 &lt; MAXVALUE/2 OR
3294
3295 o S2 &gt; S1 AND S2 - S1 &gt; MAXVALUE/2
3296
3297
3298
3299
3300 <span class="grey">Herberg, et al. Standards Track [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3303
3304
3305 When sequence numbers S1 and S2 differ by MAXVALUE/2,
3306 their ordering cannot be determined. In this case,
3307 which should not occur, either ordering may be
3308 assumed.
3309
3310 Thus, when comparing two messages, it is possible
3311 - even in the presence of wraparound - to determine
3312 which message contains the most recent information."
3313 REFERENCE
3314 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3315 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3316 and U. Herberg, April 2014."
3317 ::= { olsrv2TibAttNetworksSetEntry 6 }
3318
3319 olsrv2TibAttNetworksSetDist OBJECT-TYPE
3320 SYNTAX Unsigned32 (0..255)
3321 UNITS "hops"
3322 MAX-ACCESS read-only
3323 STATUS current
3324 DESCRIPTION
3325 "The number of hops to the network
3326 with address AN_net_addr from the router with
3327 originator address AN_orig_addr.
3328 The AN_orig_addr is defined by the tuple
3329 (olsrv2TibAttNetworksSetOrigIpAddrType,
3330 olsrv2TibAttNetworksSetOrigIpAddr)."
3331 REFERENCE
3332 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3333 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3334 and U. Herberg, April 2014."
3335 ::= { olsrv2TibAttNetworksSetEntry 7 }
3336
3337 olsrv2TibAttNetworksSetMetricValue OBJECT-TYPE
3338 SYNTAX Olsrv2MetricValueCompressedFormTC
3339 MAX-ACCESS read-only
3340 STATUS current
3341 DESCRIPTION
3342 "The metric of the link from the router with
3343 originator address AN_orig_addr to the attached
3344 network with address AN_net_addr.
3345 The AN_net_addr is defined by the tuple
3346 (olsrv2TibAttNetworksSetNetIpAddrType,
3347 olsrv2TibAttNetworksSetNetIpAddr,
3348 olsrv2TibAttNetworksSetNetIpAddrPrefixLen)."
3349 REFERENCE
3350 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3351 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3352 and U. Herberg, April 2014."
3353
3354
3355
3356 <span class="grey">Herberg, et al. Standards Track [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3359
3360
3361 ::= { olsrv2TibAttNetworksSetEntry 9 }
3362
3363 olsrv2TibAttNetworksSetExpireTime OBJECT-TYPE
3364 SYNTAX TimeStamp
3365 UNITS "centiseconds"
3366 MAX-ACCESS read-only
3367 STATUS current
3368 DESCRIPTION
3369 "olsrv2TibAttNetworksSetExpireTime
3370 specifies the value of sysUptime when this
3371 entry SHOULD expire and be removed from the
3372 olsrv2TibAttNetworksSetTable."
3373 REFERENCE
3374 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3375 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3376 and U. Herberg, April 2014."
3377 ::= { olsrv2TibAttNetworksSetEntry 10 }
3378
3379 --
3380 -- Routing Set
3381 --
3382
3383 olsrv2TibRoutingSetTable OBJECT-TYPE
3384 SYNTAX SEQUENCE OF Olsrv2TibRoutingSetEntry
3385 MAX-ACCESS not-accessible
3386 STATUS current
3387 DESCRIPTION
3388 "A router's Routing Set records the first hop along a
3389 selected path to each destination for which any such
3390 path is known."
3391 REFERENCE
3392 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3393 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3394 and U. Herberg, April 2014."
3395 ::= { olsrv2StateGroup 11 }
3396
3397 olsrv2TibRoutingSetEntry OBJECT-TYPE
3398 SYNTAX Olsrv2TibRoutingSetEntry
3399 MAX-ACCESS not-accessible
3400 STATUS current
3401 DESCRIPTION
3402 "It consists of Routing Tuples:
3403
3404 (R_dest_addr, R_next_iface_addr,
3405 R_local_iface_addr, R_dist, R_metric)"
3406 REFERENCE
3407 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3408 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3409
3410
3411
3412 <span class="grey">Herberg, et al. Standards Track [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3415
3416
3417 and U. Herberg, April 2014."
3418 INDEX { olsrv2TibRoutingSetDestIpAddrType,
3419 olsrv2TibRoutingSetDestIpAddr,
3420 olsrv2TibRoutingSetDestIpAddrPrefixLen }
3421 ::= { olsrv2TibRoutingSetTable 1 }
3422
3423 Olsrv2TibRoutingSetEntry ::=
3424 SEQUENCE {
3425 olsrv2TibRoutingSetDestIpAddrType
3426 InetAddressType,
3427 olsrv2TibRoutingSetDestIpAddr
3428 InetAddress,
3429 olsrv2TibRoutingSetDestIpAddrPrefixLen
3430 InetAddressPrefixLength,
3431 olsrv2TibRoutingSetNextIfIpAddrType
3432 InetAddressType,
3433 olsrv2TibRoutingSetNextIfIpAddr
3434 InetAddress,
3435 olsrv2TibRoutingSetLocalIfIpAddrType
3436 InetAddressType,
3437 olsrv2TibRoutingSetLocalIfIpAddr
3438 InetAddress,
3439 olsrv2TibRoutingSetDist
3440 Unsigned32,
3441 olsrv2TibRoutingSetMetricValue
3442 Unsigned32
3443 }
3444
3445 olsrv2TibRoutingSetDestIpAddrType OBJECT-TYPE
3446 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
3447 MAX-ACCESS not-accessible
3448 STATUS current
3449 DESCRIPTION
3450 "The type of the olsrv2TibRoutingSetDestIpAddr,
3451 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
3452
3453 Only the values 'ipv4(1)' and 'ipv6(2)' are
3454 supported."
3455 REFERENCE
3456 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3457 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3458 and U. Herberg, April 2014."
3459 ::= { olsrv2TibRoutingSetEntry 1 }
3460
3461 olsrv2TibRoutingSetDestIpAddr OBJECT-TYPE
3462 SYNTAX InetAddress (SIZE(4|16))
3463 MAX-ACCESS not-accessible
3464 STATUS current
3465
3466
3467
3468 <span class="grey">Herberg, et al. Standards Track [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3471
3472
3473 DESCRIPTION
3474 "This is the address of the destination,
3475 either the address of an interface of
3476 a destination router or the network
3477 address of an attached network."
3478 REFERENCE
3479 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3480 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3481 and U. Herberg, April 2014."
3482 ::= { olsrv2TibRoutingSetEntry 2 }
3483
3484 olsrv2TibRoutingSetDestIpAddrPrefixLen OBJECT-TYPE
3485 SYNTAX InetAddressPrefixLength
3486 UNITS "bits"
3487 MAX-ACCESS not-accessible
3488 STATUS current
3489 DESCRIPTION
3490 "Indicates the number of leading one bits that form the
3491 mask to be logically ANDed with the destination address
3492 before being compared to the value in the
3493 olsrv2TibRoutingSetDestIpAddr field.
3494
3495 Note: This definition needs to be consistent
3496 with the current forwarding table MIB module description.
3497 Specifically, it SHOULD allow for longest prefix
3498 matching of network addresses."
3499 REFERENCE
3500 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3501 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3502 and U. Herberg, April 2014."
3503 ::= { olsrv2TibRoutingSetEntry 3 }
3504
3505 olsrv2TibRoutingSetNextIfIpAddrType OBJECT-TYPE
3506 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
3507 MAX-ACCESS read-only
3508 STATUS current
3509 DESCRIPTION
3510 "The type of the olsrv2TibRoutingSetNextIfIpAddr,
3511 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
3512
3513 Only the values 'ipv4(1)' and
3514 'ipv6(2)' are supported."
3515 REFERENCE
3516 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3517 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3518 and U. Herberg, April 2014."
3519 ::= { olsrv2TibRoutingSetEntry 4 }
3520
3521
3522
3523
3524 <span class="grey">Herberg, et al. Standards Track [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3527
3528
3529 olsrv2TibRoutingSetNextIfIpAddr OBJECT-TYPE
3530 SYNTAX InetAddress (SIZE(4|16))
3531 MAX-ACCESS read-only
3532 STATUS current
3533 DESCRIPTION
3534 "This object is the OLSRv2 interface address of the
3535 next hop on the selected path to the
3536 destination."
3537 REFERENCE
3538 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3539 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3540 and U. Herberg, April 2014."
3541 ::= { olsrv2TibRoutingSetEntry 5 }
3542
3543 olsrv2TibRoutingSetLocalIfIpAddrType OBJECT-TYPE
3544 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
3545 MAX-ACCESS read-only
3546 STATUS current
3547 DESCRIPTION
3548 "The type of the olsrv2TibRoutingSetLocalIfIpAddr
3549 and olsrv2TibRoutingSetNextIfIpAddr,
3550 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
3551
3552 Only the values 'ipv4(1)' and
3553 'ipv6(2)' are supported."
3554 REFERENCE
3555 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3556 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3557 and U. Herberg, April 2014."
3558 ::= { olsrv2TibRoutingSetEntry 6 }
3559
3560 olsrv2TibRoutingSetLocalIfIpAddr OBJECT-TYPE
3561 SYNTAX InetAddress (SIZE(4|16))
3562 MAX-ACCESS read-only
3563 STATUS current
3564 DESCRIPTION
3565 "This object is the address of the local OLSRv2
3566 interface over which a packet must be
3567 sent to reach the destination by the
3568 selected path."
3569 REFERENCE
3570 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3571 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3572 and U. Herberg, April 2014."
3573 ::= { olsrv2TibRoutingSetEntry 7 }
3574
3575 olsrv2TibRoutingSetDist OBJECT-TYPE
3576 SYNTAX Unsigned32 (0..255)
3577
3578
3579
3580 <span class="grey">Herberg, et al. Standards Track [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3583
3584
3585 UNITS "hops"
3586 MAX-ACCESS read-only
3587 STATUS current
3588 DESCRIPTION
3589 "This object is the number of hops on the selected
3590 path to the destination."
3591 REFERENCE
3592 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3593 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3594 and U. Herberg, April 2014."
3595 ::= { olsrv2TibRoutingSetEntry 8 }
3596
3597 olsrv2TibRoutingSetMetricValue OBJECT-TYPE
3598 SYNTAX Unsigned32(0..4294901760)
3599 MAX-ACCESS read-only
3600 STATUS current
3601 DESCRIPTION
3602 "This object is the metric of the route
3603 to the destination with address R_dest_addr.
3604 The maximum value of this object can be
3605 256 times MAXIMUM_METRIC,
3606 as represented in Olsrv2MetricValueCompressedFormTC, i.e.,
3607 4294901760."
3608 REFERENCE
3609 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3610 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3611 and U. Herberg, April 2014."
3612 ::= { olsrv2TibRoutingSetEntry 9 }
3613
3614 --
3615 -- OLSRv2 Performance Group
3616 --
3617
3618 --
3619 -- Contains objects that help to characterize the
3620 -- performance of the OLSRv2 routing process.
3621 --
3622
3623 olsrv2PerformanceObjGrp OBJECT IDENTIFIER ::= {olsrv2MIBObjects 3}
3624
3625 --
3626 -- Objects per local interface
3627 --
3628
3629 olsrv2InterfacePerfTable OBJECT-TYPE
3630 SYNTAX SEQUENCE OF Olsrv2InterfacePerfEntry
3631 MAX-ACCESS not-accessible
3632 STATUS current
3633
3634
3635
3636 <span class="grey">Herberg, et al. Standards Track [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3639
3640
3641 DESCRIPTION
3642 "This table summarizes performance objects that are
3643 measured per each active local OLSRv2 interface.
3644 If the olsrv2InterfaceAdminStatus of the interface
3645 changes to 'disabled', then the row associated with this
3646 interface SHOULD be removed from this table."
3647 REFERENCE
3648 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3649 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3650 and U. Herberg, April 2014."
3651 ::= { olsrv2PerformanceObjGrp 1 }
3652
3653 olsrv2InterfacePerfEntry OBJECT-TYPE
3654 SYNTAX Olsrv2InterfacePerfEntry
3655 MAX-ACCESS not-accessible
3656 STATUS current
3657 DESCRIPTION
3658 "A single entry contains performance counters for
3659 each active local OLSRv2 interface."
3660 AUGMENTS { nhdpInterfacePerfEntry }
3661 ::= { olsrv2InterfacePerfTable 1 }
3662
3663 Olsrv2InterfacePerfEntry ::=
3664 SEQUENCE {
3665 olsrv2IfTcMessageXmits
3666 Counter32,
3667 olsrv2IfTcMessageRecvd
3668 Counter32,
3669 olsrv2IfTcMessageXmitAccumulatedSize
3670 Counter64,
3671 olsrv2IfTcMessageRecvdAccumulatedSize
3672 Counter64,
3673 olsrv2IfTcMessageTriggeredXmits
3674 Counter32,
3675 olsrv2IfTcMessagePeriodicXmits
3676 Counter32,
3677 olsrv2IfTcMessageForwardedXmits
3678 Counter32,
3679 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount
3680 Counter32
3681 }
3682
3683 olsrv2IfTcMessageXmits OBJECT-TYPE
3684 SYNTAX Counter32
3685 UNITS "messages"
3686 MAX-ACCESS read-only
3687 STATUS current
3688 DESCRIPTION
3689
3690
3691
3692 <span class="grey">Herberg, et al. Standards Track [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3695
3696
3697 "A counter is incremented each time a TC
3698 message has been transmitted on that interface."
3699 ::= { olsrv2InterfacePerfEntry 1 }
3700
3701 olsrv2IfTcMessageRecvd OBJECT-TYPE
3702 SYNTAX Counter32
3703 UNITS "messages"
3704 MAX-ACCESS read-only
3705 STATUS current
3706 DESCRIPTION
3707 "A counter is incremented each time a
3708 TC message has been received on that interface.
3709 This excludes all messages that are ignored due to
3710 OLSRv2 protocol procedures, such as messages
3711 considered invalid for processing by this router,
3712 as defined in <a href="#section-16.3.1">Section 16.3.1</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
3713 REFERENCE
3714 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3715 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3716 and U. Herberg, April 2014."
3717 ::= { olsrv2InterfacePerfEntry 2 }
3718
3719 olsrv2IfTcMessageXmitAccumulatedSize OBJECT-TYPE
3720 SYNTAX Counter64
3721 UNITS "octets"
3722 MAX-ACCESS read-only
3723 STATUS current
3724 DESCRIPTION
3725 "A counter is incremented by the number of octets in
3726 a TC message each time a TC message has been sent."
3727 ::= { olsrv2InterfacePerfEntry 3 }
3728
3729 olsrv2IfTcMessageRecvdAccumulatedSize OBJECT-TYPE
3730 SYNTAX Counter64
3731 UNITS "octets"
3732 MAX-ACCESS read-only
3733 STATUS current
3734 DESCRIPTION
3735 "A counter is incremented by the number of octets in
3736 a TC message each time a TC message has been received.
3737 This excludes all messages that are ignored due to
3738 OLSRv2 protocol procedures, such as messages
3739 considered invalid for processing by this router,
3740 as defined in <a href="#section-16.3.1">Section 16.3.1</a> of OLSRv2 (<a href="./rfc7181">RFC 7181</a>)."
3741 REFERENCE
3742 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
3743 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
3744 and U. Herberg, April 2014."
3745
3746
3747
3748 <span class="grey">Herberg, et al. Standards Track [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3751
3752
3753 ::= { olsrv2InterfacePerfEntry 4 }
3754
3755 olsrv2IfTcMessageTriggeredXmits OBJECT-TYPE
3756 SYNTAX Counter32
3757 UNITS "messages"
3758 MAX-ACCESS read-only
3759 STATUS current
3760 DESCRIPTION
3761 "A counter is incremented each time a triggered
3762 TC message has been sent."
3763 ::= { olsrv2InterfacePerfEntry 5 }
3764
3765 olsrv2IfTcMessagePeriodicXmits OBJECT-TYPE
3766 SYNTAX Counter32
3767 UNITS "messages"
3768 MAX-ACCESS read-only
3769 STATUS current
3770 DESCRIPTION
3771 "A counter is incremented each time a periodic
3772 TC message has been sent."
3773 ::= { olsrv2InterfacePerfEntry 6 }
3774
3775 olsrv2IfTcMessageForwardedXmits OBJECT-TYPE
3776 SYNTAX Counter32
3777 UNITS "messages"
3778 MAX-ACCESS read-only
3779 STATUS current
3780 DESCRIPTION
3781 "A counter is incremented each time a
3782 TC message has been forwarded."
3783 ::= { olsrv2InterfacePerfEntry 7 }
3784
3785 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount OBJECT-TYPE
3786 SYNTAX Counter32
3787 UNITS "advertised MPR selectors"
3788 MAX-ACCESS read-only
3789 STATUS current
3790 DESCRIPTION
3791 "A counter is incremented by the number of advertised
3792 MPR selectors in a TC each time a TC
3793 message has been sent."
3794 ::= { olsrv2InterfacePerfEntry 8 }
3795
3796 --
3797 -- Objects concerning the Routing Set
3798 --
3799
3800 olsrv2RoutingSetRecalculationCount OBJECT-TYPE
3801
3802
3803
3804 <span class="grey">Herberg, et al. Standards Track [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3807
3808
3809 SYNTAX Counter32
3810 UNITS "recalculations"
3811 MAX-ACCESS read-only
3812 STATUS current
3813 DESCRIPTION
3814 "This counter increments each time the Routing Set has
3815 been recalculated."
3816 ::= { olsrv2PerformanceObjGrp 2 }
3817
3818 --
3819 -- Objects concerning the MPR set
3820 --
3821
3822 olsrv2MPRSetRecalculationCount OBJECT-TYPE
3823 SYNTAX Counter32
3824 UNITS "recalculations"
3825 MAX-ACCESS read-only
3826 STATUS current
3827 DESCRIPTION
3828 "This counter increments each time the MPRs
3829 of this router have been recalculated for
3830 any of its interfaces."
3831 ::= { olsrv2PerformanceObjGrp 3 }
3832
3833 --
3834 -- Notifications
3835 --
3836
3837 olsrv2NotificationsObjects OBJECT IDENTIFIER ::=
3838 { olsrv2MIBNotifications 0 }
3839 olsrv2NotificationsControl OBJECT IDENTIFIER ::=
3840 { olsrv2MIBNotifications 1 }
3841 olsrv2NotificationsStates OBJECT IDENTIFIER ::=
3842 { olsrv2MIBNotifications 2 }
3843
3844
3845 -- olsrv2NotificationsObjects
3846
3847 olsrv2RouterStatusChange NOTIFICATION-TYPE
3848 OBJECTS { olsrv2OrigIpAddrType, -- The address type of
3849 -- the originator of
3850 -- the notification.
3851 olsrv2OrigIpAddr, -- The originator of
3852 -- the notification.
3853 olsrv2AdminStatus -- The new state.
3854 }
3855 STATUS current
3856 DESCRIPTION
3857
3858
3859
3860 <span class="grey">Herberg, et al. Standards Track [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3863
3864
3865 "olsrv2RouterStatusChange is a notification generated
3866 when the OLSRv2 router changes it status.
3867 The router status is maintained in the
3868 olsrv2AdminStatus object."
3869 ::= { olsrv2NotificationsObjects 1 }
3870
3871 olsrv2OrigIpAddrChange NOTIFICATION-TYPE
3872 OBJECTS { olsrv2OrigIpAddrType, -- The address type of
3873 -- the originator of
3874 -- the notification.
3875 olsrv2OrigIpAddr, -- The originator of
3876 -- the notification.
3877 olsrv2PreviousOrigIpAddrType, -- The address
3878 -- type of the previous
3879 -- address of
3880 -- the originator of
3881 -- the notification.
3882 olsrv2PreviousOrigIpAddr -- The previous
3883 -- address of the
3884 -- originator of
3885 -- the notification.
3886 }
3887 STATUS current
3888 DESCRIPTION
3889 "olsrv2OrigIpAddrChange is a notification generated when
3890 the OLSRv2 router changes it originator IP address.
3891 The notification includes the new and the previous
3892 originator IP address of the OLSRv2 router."
3893 ::= { olsrv2NotificationsObjects 2 }
3894
3895 olsrv2RoutingSetRecalculationCountChange NOTIFICATION-TYPE
3896 OBJECTS { olsrv2OrigIpAddrType, -- The address type of
3897 -- the originator of
3898 -- the notification.
3899 olsrv2OrigIpAddr, -- The originator of
3900 -- the notification.
3901 olsrv2RoutingSetRecalculationCount -- Number
3902 -- of the
3903 -- Routing Set
3904 -- recalculations.
3905 }
3906 STATUS current
3907 DESCRIPTION
3908 "The olsrv2RoutingSetRecalculationCountChange
3909 notification is generated when a significant number of
3910 Routing Set recalculations have occurred in a short time.
3911 This notification SHOULD be generated no more than once
3912 per olsrv2RoutingSetRecalculationCountWindow.
3913
3914
3915
3916 <span class="grey">Herberg, et al. Standards Track [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3919
3920
3921 The network administrator SHOULD select
3922 appropriate values for 'significant number of
3923 Routing Set recalculations' and 'short time' through
3924 the settings of the
3925 olsrv2RoutingSetRecalculationCountThreshold
3926 and olsrv2RoutingSetRecalculationCountWindow objects."
3927 ::= { olsrv2NotificationsObjects 3 }
3928
3929 olsrv2MPRSetRecalculationCountChange NOTIFICATION-TYPE
3930 OBJECTS { olsrv2OrigIpAddrType, -- The address type of
3931 -- the originator of
3932 -- the notification.
3933 olsrv2OrigIpAddr, -- The originator of
3934 -- the notification.
3935 olsrv2MPRSetRecalculationCount -- Number of
3936 -- MPR set
3937 -- recalculations.
3938 }
3939 STATUS current
3940 DESCRIPTION
3941 "The olsrv2MPRSetRecalculationCountChange
3942 notification is generated when a significant
3943 number of MPR set recalculations occur in
3944 a short period of time. This notification
3945 SHOULD be generated no more than once
3946 per olsrv2MPRSetRecalculationCountWindow.
3947 The network administrator SHOULD select
3948 appropriate values for 'significant number of
3949 MPR set recalculations' and 'short period of
3950 time' through the settings of the
3951 olsrv2MPRSetRecalculationCountThreshold and
3952 olsrv2MPRSetRecalculationCountWindow objects."
3953 ::= { olsrv2NotificationsObjects 4 }
3954
3955 -- olsrv2NotificationsControl
3956
3957 olsrv2RoutingSetRecalculationCountThreshold OBJECT-TYPE
3958 SYNTAX Integer32 (0..255)
3959 UNITS "recalculations"
3960 MAX-ACCESS read-write
3961 STATUS current
3962 DESCRIPTION
3963 "A threshold value for the
3964 olsrv2RoutingSetRecalculationCount object.
3965 If the number of occurrences exceeds this
3966 threshold within the previous
3967 olsrv2RoutingSetRecalculationCountWindow,
3968 then the olsrv2RoutingSetRecalculationCountChange
3969
3970
3971
3972 <span class="grey">Herberg, et al. Standards Track [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
3975
3976
3977 notification is to be generated.
3978
3979 It is RECOMMENDED that the value of this
3980 threshold be set to at least 20 and higher
3981 in dense topologies with frequent expected
3982 topology changes."
3983 DEFVAL { 20 }
3984 ::= { olsrv2NotificationsControl 1 }
3985
3986 olsrv2RoutingSetRecalculationCountWindow OBJECT-TYPE
3987 SYNTAX TimeTicks
3988 MAX-ACCESS read-write
3989 STATUS current
3990 DESCRIPTION
3991 "This object is used to determine whether to generate
3992 an olsrv2RoutingSetRecalculationCountChange notification.
3993 This object represents an interval from the present moment,
3994 extending into the past, expressed in hundredths of
3995 a second. If the change in the value of the
3996 olsrv2RoutingSetRecalculationCount object during
3997 this interval has exceeded the value of
3998 olsrv2RoutingSetRecalculationCountThreshold, then
3999 an olsrv2RoutingSetRecalculationCountChange notification
4000 is generated.
4001
4002 It is RECOMMENDED that the value for this
4003 window be set to at least 5 times the
4004 nhdpHelloInterval (whose default value is
4005 2 seconds."
4006 DEFVAL { 1000 }
4007 ::= { olsrv2NotificationsControl 2 }
4008
4009 olsrv2MPRSetRecalculationCountThreshold OBJECT-TYPE
4010 SYNTAX Integer32 (0..255)
4011 UNITS "recalculations"
4012 MAX-ACCESS read-write
4013 STATUS current
4014 DESCRIPTION
4015 "A threshold value for the
4016 olsrv2MPRSetRecalculationCount object.
4017 If the number of occurrences exceeds this
4018 threshold within the previous
4019 olsrv2MPRSetRecalculationCountWindow,
4020 then the
4021 olsrv2MPRSetRecalculationCountChange
4022 notification is to be generated.
4023
4024 It is RECOMMENDED that the value of this
4025
4026
4027
4028 <span class="grey">Herberg, et al. Standards Track [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4031
4032
4033 threshold be set to at least 20 and higher
4034 in dense topologies with frequent expected
4035 topology changes."
4036 DEFVAL { 20 }
4037 ::= { olsrv2NotificationsControl 3 }
4038
4039 olsrv2MPRSetRecalculationCountWindow OBJECT-TYPE
4040 SYNTAX TimeTicks
4041 MAX-ACCESS read-write
4042 STATUS current
4043 DESCRIPTION
4044 "This object is used to determine whether to generate
4045 an olsrv2MPRSetRecalculationCountChange notification.
4046 This object represents an interval from the present moment,
4047 extending into the past, expressed in hundredths of
4048 a second. If the change in the value of the
4049 olsrv2MPRSetRecalculationCount object during
4050 that interval has exceeded the value of
4051 olsrv2MPRSetRecalculationCountThreshold, then the
4052 an olsrv2MPRSetRecalculationCountChange notification
4053 is generated.
4054
4055 It is RECOMMENDED that the value for this
4056 window be set to at least 5 times the
4057 nhdpHelloInterval."
4058 DEFVAL { 1000 }
4059 ::= { olsrv2NotificationsControl 4 }
4060
4061 olsrv2PreviousOrigIpAddrType OBJECT-TYPE
4062 SYNTAX InetAddressType { ipv4(1) , ipv6(2) }
4063 MAX-ACCESS read-only
4064 STATUS current
4065 DESCRIPTION
4066 "The type of the olsrv2PreviousOrigIpAddr,
4067 as defined in the InetAddress MIB module (<a href="./rfc4001">RFC 4001</a>).
4068
4069 Only the values 'ipv4(1)' and
4070 'ipv6(2)' are supported.
4071
4072 This object MUST have the same persistence
4073 characteristics as olsrv2PreviousOrigIpAddr."
4074 REFERENCE
4075 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
4076 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
4077 and U. Herberg, April 2014."
4078 ::= { olsrv2NotificationsStates 1 }
4079
4080 olsrv2PreviousOrigIpAddr OBJECT-TYPE
4081
4082
4083
4084 <span class="grey">Herberg, et al. Standards Track [Page 73]</span></pre>
4085 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
4086 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4087
4088
4089 SYNTAX InetAddress (SIZE(4|16))
4090 MAX-ACCESS read-only
4091 STATUS current
4092 DESCRIPTION
4093 "The previous origination IP address
4094 of this OLSRv2 router.
4095
4096 This object SHOULD be updated each time
4097 the olsrv2OrigIpAddr is modified.
4098
4099 This object is persistent, and when written,
4100 the entity SHOULD save the change to
4101 non-volatile storage."
4102 REFERENCE
4103 "<a href="./rfc7181">RFC 7181</a> - The Optimized Link State Routing Protocol
4104 Version 2, Clausen, T., Dearlove, C., Jacquet, P.,
4105 and U. Herberg, April 2014."
4106 ::= { olsrv2NotificationsStates 2 }
4107
4108 --
4109 -- Compliance Statements
4110 --
4111
4112 olsrv2Compliances OBJECT IDENTIFIER ::= { olsrv2MIBConformance 1 }
4113 olsrv2MIBGroups OBJECT IDENTIFIER ::= { olsrv2MIBConformance 2 }
4114
4115 olsrv2BasicCompliance MODULE-COMPLIANCE
4116 STATUS current
4117 DESCRIPTION
4118 "The basic implementation requirements for
4119 managed network entities that implement
4120 the OLSRv2 routing process."
4121 MODULE -- this module
4122 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup }
4123 ::= { olsrv2Compliances 1 }
4124
4125 olsrv2FullCompliance MODULE-COMPLIANCE
4126 STATUS current
4127 DESCRIPTION
4128 "The full implementation requirements for
4129 managed network entities that implement
4130 the OLSRv2 routing process."
4131 MODULE -- this module
4132 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup,
4133 olsrv2StateObjectsGroup,
4134 olsrv2PerfObjectsGroup,
4135 olsrv2NotificationsObjectsGroup,
4136 olsrv2NotificationsGroup }
4137
4138
4139
4140 <span class="grey">Herberg, et al. Standards Track [Page 74]</span></pre>
4141 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
4142 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4143
4144
4145 ::= { olsrv2Compliances 2 }
4146
4147 --
4148 -- Units of Conformance
4149 --
4150
4151 olsrv2ConfigObjectsGroup OBJECT-GROUP
4152 OBJECTS {
4153 olsrv2AdminStatus,
4154 olsrv2InterfaceAdminStatus,
4155 olsrv2OrigIpAddrType,
4156 olsrv2OrigIpAddr,
4157 olsrv2OHoldTime,
4158 olsrv2TcInterval,
4159 olsrv2TcMinInterval,
4160 olsrv2THoldTime,
4161 olsrv2AHoldTime,
4162 olsrv2RxHoldTime,
4163 olsrv2PHoldTime,
4164 olsrv2FHoldTime,
4165 olsrv2TpMaxJitter,
4166 olsrv2TtMaxJitter,
4167 olsrv2FMaxJitter,
4168 olsrv2TcHopLimit,
4169 olsrv2WillFlooding,
4170 olsrv2WillRouting,
4171 olsrv2LinkMetricType
4172 }
4173 STATUS current
4174 DESCRIPTION
4175 "Objects to permit configuration of OLSRv2.
4176 All of these SHOULD be backed by non-volatile
4177 storage."
4178 ::= { olsrv2MIBGroups 1 }
4179
4180 olsrv2StateObjectsGroup OBJECT-GROUP
4181 OBJECTS {
4182 olsrv2LibOrigSetExpireTime,
4183 olsrv2LibLocAttNetSetDistance,
4184 olsrv2LibLocAttNetSetMetricValue,
4185 olsrv2IibLinkSetInMetricValue,
4186 olsrv2IibLinkSetOutMetricValue,
4187 olsrv2IibLinkSetMprSelector,
4188 olsrv2Iib2HopSetInMetricValue,
4189 olsrv2Iib2HopSetOutMetricValue,
4190 olsrv2NibNeighborSetNOrigIpAddrType,
4191 olsrv2NibNeighborSetNOrigIpAddr,
4192 olsrv2NibNeighborSetNInMetricValue,
4193
4194
4195
4196 <span class="grey">Herberg, et al. Standards Track [Page 75]</span></pre>
4197 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
4198 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4199
4200
4201 olsrv2NibNeighborSetNOutMetricValue,
4202 olsrv2NibNeighborSetNWillFlooding,
4203 olsrv2NibNeighborSetNWillRouting,
4204 olsrv2NibNeighborSetNFloodingMpr,
4205 olsrv2NibNeighborSetNRoutingMpr,
4206 olsrv2NibNeighborSetNMprSelector,
4207 olsrv2NibNeighborSetNAdvertised,
4208 olsrv2NibNeighborSetTableAnsn,
4209 olsrv2TibAdRemoteRouterSetMaxSeqNo,
4210 olsrv2TibAdRemoteRouterSetExpireTime,
4211 olsrv2TibRouterTopologySetSeqNo,
4212 olsrv2TibRouterTopologySetMetricValue,
4213 olsrv2TibRouterTopologySetExpireTime,
4214 olsrv2TibRoutableAddressTopologySetExpireTime,
4215 olsrv2TibRoutableAddressTopologySetSeqNo,
4216 olsrv2TibRoutableAddressTopologySetMetricValue,
4217 olsrv2TibAttNetworksSetSeqNo,
4218 olsrv2TibAttNetworksSetDist,
4219 olsrv2TibAttNetworksSetMetricValue,
4220 olsrv2TibAttNetworksSetExpireTime,
4221 olsrv2TibRoutingSetNextIfIpAddrType,
4222 olsrv2TibRoutingSetNextIfIpAddr,
4223 olsrv2TibRoutingSetLocalIfIpAddrType,
4224 olsrv2TibRoutingSetLocalIfIpAddr,
4225 olsrv2TibRoutingSetDist,
4226 olsrv2TibRoutingSetMetricValue
4227 }
4228 STATUS current
4229 DESCRIPTION
4230 "Objects to permit monitoring of OLSRv2 state."
4231 ::= { olsrv2MIBGroups 2 }
4232
4233 olsrv2PerfObjectsGroup OBJECT-GROUP
4234 OBJECTS {
4235 olsrv2IfTcMessageXmits,
4236 olsrv2IfTcMessageRecvd,
4237 olsrv2IfTcMessageXmitAccumulatedSize,
4238 olsrv2IfTcMessageRecvdAccumulatedSize,
4239 olsrv2IfTcMessageTriggeredXmits,
4240 olsrv2IfTcMessagePeriodicXmits,
4241 olsrv2IfTcMessageForwardedXmits,
4242 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount,
4243 olsrv2RoutingSetRecalculationCount,
4244 olsrv2MPRSetRecalculationCount
4245 }
4246 STATUS current
4247 DESCRIPTION
4248 "Objects to support monitoring of OLSRv2 performance."
4249
4250
4251
4252 <span class="grey">Herberg, et al. Standards Track [Page 76]</span></pre>
4253 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
4254 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4255
4256
4257 ::= { olsrv2MIBGroups 3 }
4258
4259 olsrv2NotificationsObjectsGroup OBJECT-GROUP
4260 OBJECTS {
4261 olsrv2RoutingSetRecalculationCountThreshold,
4262 olsrv2RoutingSetRecalculationCountWindow,
4263 olsrv2MPRSetRecalculationCountThreshold,
4264 olsrv2MPRSetRecalculationCountWindow,
4265 olsrv2PreviousOrigIpAddrType,
4266 olsrv2PreviousOrigIpAddr
4267 }
4268 STATUS current
4269 DESCRIPTION
4270 "Objects to support the notification types in the
4271 olsrv2NotificationsGroup. Some of these appear in
4272 notification payloads, others serve to control
4273 notification generation."
4274 ::= { olsrv2MIBGroups 4 }
4275
4276
4277 olsrv2NotificationsGroup NOTIFICATION-GROUP
4278 NOTIFICATIONS {
4279 olsrv2RouterStatusChange,
4280 olsrv2OrigIpAddrChange,
4281 olsrv2RoutingSetRecalculationCountChange,
4282 olsrv2MPRSetRecalculationCountChange
4283 }
4284 STATUS current
4285 DESCRIPTION
4286 "Notification types to support management of OLSRv2."
4287 ::= { olsrv2MIBGroups 5 }
4288
4289 END
4290
4291
4292 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
4293
4294 This MIB module defines objects for the configuration, monitoring,
4295 and notification of the Optimized Link State Routing Protocol version
4296 2 (OLSRv2) [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>]. OLSRv2 allows routers to acquire topological
4297 information of the routing domain by exchanging TC messages in order
4298 to calculate shortest paths to each destination router in the routing
4299 domain.
4300
4301 There are a number of management objects defined in this MIB module
4302 with a MAX-ACCESS clause of read-write and/or read-create. Such
4303 objects may be considered sensitive or vulnerable in some network
4304 environments. The support for SET operations in a non-secure
4305
4306
4307
4308 <span class="grey">Herberg, et al. Standards Track [Page 77]</span></pre>
4309 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
4310 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4311
4312
4313 environment without proper protection can have a negative effect on
4314 network operations. These are the tables and objects and their
4315 sensitivity/vulnerability:
4316
4317 o olsrv2TcInterval, olsrv2TcMinInterval - these writable objects
4318 control the rate at which TC messages are sent. If set at too
4319 high a rate, this could represent a form of a DoS attack by
4320 overloading interface resources. If set too low, OLSRv2 may not
4321 converge fast enough to provide accurate routes to all
4322 destinations in the routing domain.
4323
4324 o olsrv2TcHopLimit - defines the hop limit for TC messages. If set
4325 too low, messages will not be forwarded beyond the defined scope;
4326 thus, routers further away from the message originator will not be
4327 able to construct appropriate topology graphs.
4328
4329 o olsrv2OHoldTime, olsrv2THoldTime, olsrv2AHoldTime,
4330 olsrv2RxHoldTime, olsrv2PHoldTime, olsrv2FHoldTime - define hold
4331 times for tuples of different Information Bases of OLSRv2. If set
4332 too low, information will expire quickly, and may this harm a
4333 correct operation of the routing protocol.
4334
4335 o olsrv2WillFlooding and olsrv2WillRouting - define the willingness
4336 of this router to become MPR. If this is set to WILL_NEVER (0),
4337 the managed router will not forward any TC messages, nor accept a
4338 selection to become MPR by neighboring routers. If set to
4339 WILL_ALWAYS (15), the router will be preferred by neighbors during
4340 MPR selection and may thus attract more traffic.
4341
4342 o olsrv2TpMaxJitter, olsrv2TtMaxJitter, olsrv2FMaxJitter - define
4343 jitter values for TC message transmission and forwarding. If set
4344 too low, control traffic may get lost when collisions occur.
4345
4346 o olsrv2LinkMetricType - defines the type of the link metric that a
4347 router uses (e.g., ETX or hop count). Whenever this value
4348 changes, all link metric information recorded by the router is
4349 invalid, causing a reset of information acquired from other
4350 routers in the MANET. Moreover, if olsrv2LinkMetricType on a
4351 router is set to a value that is not known to other routers in the
4352 MANET, these routers will not be able to establish routes to that
4353 router or transiting that router. Existing routes to the router
4354 with an olsrv2LinkMetricType unknown to other routers in the MANET
4355 will be removed.
4356
4357 Some of the readable objects in this MIB module (i.e., objects with a
4358 MAX-ACCESS other than not-accessible) may be considered sensitive or
4359 vulnerable in some network environments. It is thus important to
4360 control even GET and/or NOTIFY access to these objects and possibly
4361
4362
4363
4364 <span class="grey">Herberg, et al. Standards Track [Page 78]</span></pre>
4365 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
4366 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4367
4368
4369 to even encrypt the values of these objects when sending them over
4370 the network via SNMP. These are the tables and objects and their
4371 sensitivity/vulnerability:
4372
4373 o olsrv2TibRouterTopologySetTable - The contains information on the
4374 topology of the MANET, specifically the IP address of the routers
4375 in the MANET (as identified by
4376 olsrv2TibRouterTopologySetFromOrigIpAddr and
4377 olsrv2TibRouterTopologySetToOrigIpAddr objects). This information
4378 provides an adversary broad information on the members of the
4379 MANET, located within this single table. This information can be
4380 used to expedite attacks on the other members of the MANET without
4381 having to go through a laborious discovery process on their own.
4382
4383 Some of the Tables in this MIB module AUGMENT Tables defined in NHDP-
4384 MIB [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>]. Hence, care must be taken in configuring access
4385 control here in order make sure that the permitted permissions
4386 granted for the AUGMENTing Tables here are consistent with the access
4387 controls permitted within the NHDP-MIB. The below list identifies
4388 the AUGMENTing Tables and their NHDP-MIB counterparts. It is
4389 RECOMMENDED that access control policies for these Table pairs are
4390 consistently set.
4391
4392 o The olsrv2InterfaceTable AUGMENTs the nhdpInterfaceTable.
4393
4394 o The olsrv2IibLinkSetTable AUGMENTs the nhdpIibLinkSetTable.
4395
4396 o The olsrv2Iib2HopSetTable AUGMENTs the nhdpIib2HopSetTable.
4397
4398 o The olsrv2NibNeighborSetTable AUGMENTs the
4399 nhdpNibNeighborSetTable.
4400
4401 o The olsrv2InterfacePerfTable AUGMENTs the nhdpInterfacePerfTable.
4402
4403 MANET technology is often deployed to support communications of
4404 emergency services or military tactical applications. In these
4405 applications, it is imperative to maintain the proper operation of
4406 the communications network and to protect sensitive information
4407 related to its operation. Therefore, when implementing these
4408 capabilities, the full use of SNMPv3 cryptographic mechanisms for
4409 authentication and privacy is RECOMMENDED.
4410
4411 SNMP versions prior to SNMPv3 did not include adequate security.
4412 Even if the network itself is secure (for example by using IPsec),
4413 there is no control as to who on the secure network is allowed to
4414 access and GET/SET (read/change/create/delete) the objects in this
4415 MIB module.
4416
4417
4418
4419
4420 <span class="grey">Herberg, et al. Standards Track [Page 79]</span></pre>
4421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
4422 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4423
4424
4425 Implementations SHOULD provide the security features described by the
4426 SNMPv3 framework (see [<a href="./rfc3410" title="&quot;Introduction and Applicability Statements for Internet- Standard Management Framework&quot;">RFC3410</a>]), and implementations claiming
4427 compliance to the SNMPv3 standard MUST include full support for
4428 authentication and privacy via the User-based Security Model (USM)
4429 [<a href="./rfc3414" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">RFC3414</a>] with the AES cipher algorithm [<a href="./rfc3826" title="&quot;The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model&quot;">RFC3826</a>]. Implementations
4430 MAY also provide support for the Transport Security Model (TSM)
4431 [<a href="./rfc5591" title="&quot;Transport Security Model for the Simple Network Management Protocol (SNMP)&quot;">RFC5591</a>] in combination with a secure transport such as SSH
4432 [<a href="./rfc5592" title="&quot;Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)&quot;">RFC5592</a>] or TLS/DTLS [<a href="./rfc6353" title="&quot;Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)&quot;">RFC6353</a>].
4433
4434 Further, deployment of SNMP versions prior to SNMPv3 is NOT
4435 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
4436 enable cryptographic security. It is then a customer/operator
4437 responsibility to ensure that the SNMP entity giving access to an
4438 instance of this MIB module is properly configured to give access to
4439 the objects only to those principals (users) that have legitimate
4440 rights to indeed GET or SET (change/create/delete) them.
4441
4442 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Applicability Statement</span>
4443
4444 This document describes objects for configuring parameters of the
4445 Optimized Link State Routing Protocol version 2 (OLSRv2) [<a href="./rfc7181" title="&quot;The Optimized Link State Routing Protocol Version 2&quot;">RFC7181</a>]
4446 process on a router. This MIB module, denoted OLSRv2-MIB, also
4447 reports state, performance information, and notifications. The
4448 OLSRv2 protocol relies upon information gathered via the Neighborhood
4449 Discovery Protocol [<a href="./rfc6130" title="&quot;Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)&quot;">RFC6130</a>] in order to perform its operations.
4450 NHDP is managed via the NHDP-MIB [<a href="./rfc6779" title="&quot;Definition of Managed Objects for the Neighborhood Discovery Protocol&quot;">RFC6779</a>].
4451
4452 MANET deployments can greatly differ in aspects of dynamics of the
4453 topology, capacity, and loss rates of underlying channels, traffic
4454 flow directions, memory and CPU capacity of routers, etc. SNMP, and
4455 therefore this MIB module, are only applicable for a subset of MANET
4456 deployments, in particular deployments:
4457
4458 o In which routers have enough memory and CPU resources to run SNMP
4459 and expose the MIB module.
4460
4461 o Where a Network Management System (NMS) is defined to which
4462 notifications are generated and from which routers can be managed.
4463
4464 o Where this NMS is reachable from routers in the MANET most of the
4465 time (as notifications to the NMS and management information from
4466 the NMS to the router will be lost when connectivity is
4467 temporarily lost). This requires that the topology of the MANET
4468 is only moderately dynamic.
4469
4470 o Where the underlying wireless channel supports enough bandwidth to
4471 run SNMP, and where loss rates of the channel are not exhaustive.
4472
4473
4474
4475
4476 <span class="grey">Herberg, et al. Standards Track [Page 80]</span></pre>
4477 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
4478 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4479
4480
4481 Certain MANET deployments such as community networks with non-mobile
4482 routers, dynamic topology because of changing link quality, and a
4483 predefined gateway (that could also serve as NMS), are examples of
4484 networks applicable for this MIB module. Other, more constrained
4485 deployments of MANETs may not be able to run SNMP and require
4486 different management protocols.
4487
4488 Some level of configuration, i.e., read-write objects, is desirable
4489 for OLSRv2 deployments. Topology-related configuration, such as the
4490 ability to enable OLSRv2 on new interfaces or initially configure
4491 OLSRv2 on a router's interfaces through the
4492 olsrv2InterfaceAdminStatus object, is critical to initial system
4493 startup. The OLSRv2 protocol allows for some level of performance
4494 tuning through various protocol parameters, and this MIB module
4495 allows for configuration of those protocol parameters through read-
4496 write objects such as the olsrv2TcHopLimit or the olsrv2FMaxJitter.
4497 Other read-write objects allow for the control of Notification
4498 behavior through this MIB module, e.g., the
4499 olsrv2RoutingSetRecalculationCountThreshold object. A fuller
4500 discussion of MANET network management applicability is to be
4501 provided elsewhere: [<a href="#ref-MGMT-SNAP" title="&quot;Snapshot of OLSRv2-Routed MANET Management&quot;">MGMT-SNAP</a>] provides a snapshot of OLSRv2-routed
4502 MANET management as currently deployed, while [<a href="#ref-MANET-MGMT" title="&quot;Network Management of Mobile Ad hoc Networks (MANET): Architecture, Use Cases, and Applicability&quot;">MANET-MGMT</a>] is
4503 intended to provide specific guidelines on MANET network management
4504 considering the various MIB modules that have been written.
4505
4506 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span>
4507
4508 IANA now maintains the IANAolsrv2LinkMetricType-MIB and keeps it
4509 synchronized with the "LINK_METRIC Address Block TLV Type Extensions"
4510 registry at &lt;<a href="http://www.iana.org/assignments/manet-parameters">http://www.iana.org/assignments/manet-parameters</a>&gt;.
4511
4512 The MIB modules in this document use the following IANA-assigned
4513 OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
4514
4515 Descriptor OBJECT IDENTIFIER value
4516 ---------- -----------------------
4517 OLSRv2-MIB { mib-2 219 }
4518 IANA-OLSRv2-LINK-METRIC-TYPE-MIB { mib-2 221 }
4519
4520 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgements</span>
4521
4522 The authors would like to thank Randy Presuhn, Benoit Claise, Adrian
4523 Farrel, as well as the entire MANET WG for reviews of this document.
4524
4525 This MIB document uses the template authored by D. Harrington, which
4526 is based on contributions from the MIB Doctors, especially Juergen
4527 Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn.
4528
4529
4530
4531
4532 <span class="grey">Herberg, et al. Standards Track [Page 81]</span></pre>
4533 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span>
4534 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4535
4536
4537 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
4538
4539 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
4540
4541 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
4542 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
4543
4544 [<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
4545 Schoenwaelder, Ed., "Structure of Management Information
4546 Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
4547
4548 [<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
4549 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
4550 58, <a href="./rfc2579">RFC 2579</a>, April 1999.
4551
4552 [<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
4553 "Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>,
4554 April 1999.
4555
4556 [<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
4557 MIB", <a href="./rfc2863">RFC 2863</a>, June 2000.
4558
4559 [<a id="ref-RFC3414">RFC3414</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model
4560 (USM) for version 3 of the Simple Network Management
4561 Protocol (SNMPv3)", STD 62, <a href="./rfc3414">RFC 3414</a>, December 2002.
4562
4563 [<a id="ref-RFC3418">RFC3418</a>] Presuhn, R., "Management Information Base (MIB) for the
4564 Simple Network Management Protocol (SNMP)", STD 62, <a href="./rfc3418">RFC</a>
4565 <a href="./rfc3418">3418</a>, December 2002.
4566
4567 [<a id="ref-RFC3826">RFC3826</a>] Blumenthal, U., Maino, F., and K. McCloghrie, "The
4568 Advanced Encryption Standard (AES) Cipher Algorithm in
4569 the SNMP User-based Security Model", <a href="./rfc3826">RFC 3826</a>, June
4570 2004.
4571
4572 [<a id="ref-RFC4001">RFC4001</a>] Daniele, M., Haberman, B., Routhier, S., and J.
4573 Schoenwaelder, "Textual Conventions for Internet Network
4574 Addresses", <a href="./rfc4001">RFC 4001</a>, February 2005.
4575
4576 [<a id="ref-RFC5591">RFC5591</a>] Harrington, D. and W. Hardaker, "Transport Security
4577 Model for the Simple Network Management Protocol
4578 (SNMP)", <a href="./rfc5591">RFC 5591</a>, June 2009.
4579
4580 [<a id="ref-RFC5592">RFC5592</a>] Harrington, D., Salowey, J., and W. Hardaker, "Secure
4581 Shell Transport Model for the Simple Network Management
4582 Protocol (SNMP)", <a href="./rfc5592">RFC 5592</a>, June 2009.
4583
4584
4585
4586
4587
4588 <span class="grey">Herberg, et al. Standards Track [Page 82]</span></pre>
4589 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span>
4590 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4591
4592
4593 [<a id="ref-RFC6130">RFC6130</a>] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
4594 Network (MANET) Neighborhood Discovery Protocol (NHDP)",
4595 <a href="./rfc6130">RFC 6130</a>, April 2011.
4596
4597 [<a id="ref-RFC6353">RFC6353</a>] Hardaker, W., "Transport Layer Security (TLS) Transport
4598 Model for the Simple Network Management Protocol
4599 (SNMP)", <a href="./rfc6353">RFC 6353</a>, July 2011.
4600
4601 [<a id="ref-RFC6779">RFC6779</a>] Herberg, U., Cole, R., and I. Chakeres, "Definition of
4602 Managed Objects for the Neighborhood Discovery
4603 Protocol", <a href="./rfc6779">RFC 6779</a>, October 2012.
4604
4605 [<a id="ref-RFC7181">RFC7181</a>] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg,
4606 "The Optimized Link State Routing Protocol Version 2",
4607 <a href="./rfc7181">RFC 7181</a>, April 2014.
4608
4609 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
4610
4611 [<a id="ref-MANET-MGMT">MANET-MGMT</a>] Nguyen, J., Cole, R., Herberg, U., Yi, J., and J. Dean,
4612 "Network Management of Mobile Ad hoc Networks (MANET):
4613 Architecture, Use Cases, and Applicability", Work in
4614 Progress, February 2013.
4615
4616 [<a id="ref-MGMT-SNAP">MGMT-SNAP</a>] Clausen, T. and U. Herberg, "Snapshot of OLSRv2-Routed
4617 MANET Management", Work in Progress, February 2014.
4618
4619 [<a id="ref-REPORT-MIB">REPORT-MIB</a>] Cole, R., Macker, J., and A. Bierman, "Definition of
4620 Managed Objects for Performance Reporting", Work in
4621 Progress, November 2012.
4622
4623 [<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart,
4624 "Introduction and Applicability Statements for Internet-
4625 Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002.
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644 <span class="grey">Herberg, et al. Standards Track [Page 83]</span></pre>
4645 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span>
4646 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4647
4648
4649 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. IANAolsrv2LinkMetricType-MIB</span>
4650
4651 This document has set up the IANAolsrv2LinkMetricType-MIB module.
4652 IANA now maintains the IANAolsrv2LinkMetricType-MIB and keeps it
4653 synchronized with the "LINK_METRIC Address Block TLV Type Extensions"
4654 registry at &lt;<a href="http://www.iana.org/assignments/manet-parameters">http://www.iana.org/assignments/manet-parameters</a>&gt;. The
4655 IANA site is the definitive source for this MIB should there be any
4656 discrepancies (e.g., future updates to the MIB).
4657
4658 IANA-OLSRv2-LINK-METRIC-TYPE-MIB DEFINITIONS ::= BEGIN
4659
4660 IMPORTS
4661 MODULE-IDENTITY, mib-2
4662 FROM SNMPv2-SMI
4663 TEXTUAL-CONVENTION
4664 FROM SNMPv2-TC;
4665
4666 ianaolsrv2LinkMetricType MODULE-IDENTITY
4667 LAST-UPDATED "201404090000Z" -- 09 April 2014
4668 ORGANIZATION "IANA"
4669 CONTACT-INFO "Internet Assigned Numbers Authority
4670
4671 Postal: ICANN
4672 12025 Waterfront Drive, Suite 300
4673 Los Angeles, CA 90094-2536
4674
4675 Tel: +1 310 301 5800
4676 E-Mail: [email protected]"
4677 DESCRIPTION "This MIB module defines the
4678 IANAolsrv2LinkMetricType Textual
4679 Convention, and thus the enumerated values of
4680 the olsrv2LinkMetricType object defined in
4681 the OLSRv2-MIB."
4682 REVISION "201404090000Z" -- 09 April 2014
4683 DESCRIPTION "Initial version of this MIB as published in
4684 <a href="./rfc7184">RFC 7184</a>."
4685
4686 ::= { mib-2 221 }
4687
4688 IANAolsrv2LinkMetricTypeTC ::= TEXTUAL-CONVENTION
4689 STATUS current
4690 DESCRIPTION
4691 "This data type is used as the syntax of the
4692 olsrv2LinkMetricType object in the definition
4693 of the OLSRv2-MIB module.
4694
4695 The olsrv2LinkMetricType corresponds to
4696
4697
4698
4699
4700 <span class="grey">Herberg, et al. Standards Track [Page 84]</span></pre>
4701 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span>
4702 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4703
4704
4705 LINK_METRIC_TYPE of OLSRv2 (<a href="./rfc7181">RFC 7181</a>).
4706 OLSRv2 uses bidirectional additive link metrics
4707 to determine shortest distance routes (i.e.,
4708 routes with smallest total of link metric values).
4709
4710 OLSRv2 has established a registry for the LINK_METRIC_TYPEs
4711 (denoted 'LINK_METRIC Address Block TLV Type Extensions'):
4712 <a href="http://www.iana.org/assignments/manet-parameters/">http://www.iana.org/assignments/manet-parameters/</a>
4713
4714 This is done in <a href="#section-24.5">Section 24.5</a> in OLSRv2 (<a href="./rfc7181">RFC 7181</a>).
4715 The LINK_METRIC_TYPE (which has as corresponding
4716 object in the MIB module olsrv2LinkMetricType)
4717 corresponds to the type extension of
4718 the LINK_METRIC TLV that is set up in the
4719 'LINK_METRIC Address Block TLV Type Extensions' registry.
4720 Whenever new link metric types are added to that registry,
4721 IANA MUST update this textual convention accordingly.
4722
4723 The definition of this textual convention with the
4724 addition of newly assigned values is published
4725 periodically by the IANA, in either the Assigned
4726 Numbers RFC, or some derivative of it specific to
4727 Internet Network Management number assignments. (The
4728 latest arrangements can be obtained by contacting the
4729 IANA.)
4730
4731 Requests for new values should be made to IANA via
4732 email ([email protected])."
4733 SYNTAX INTEGER {
4734 unknown(0) -- Link metric meaning assigned
4735 -- by administrative action
4736 -- 1-223 Unassigned
4737 -- 224-255 Reserved for
4738 -- Experimental Use
4739 }
4740
4741 END
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756 <span class="grey">Herberg, et al. Standards Track [Page 85]</span></pre>
4757 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span>
4758 <span class="grey"><a href="./rfc7184">RFC 7184</a> The OLSRv2-MIB April 2014</span>
4759
4760
4761 Authors' Addresses
4762
4763 Ulrich Herberg
4764 Fujitsu Laboratories of America
4765 1240 East Arques Avenue
4766 Sunnyvale, CA 94085
4767 USA
4768
4769 EMail: [email protected]
4770 URI: <a href="http://www.herberg.name/">http://www.herberg.name/</a>
4771
4772
4773 Robert G. Cole
4774 US Army CERDEC
4775 6010 Frankford Road, Bldg 6010
4776 Aberdeen Proving Ground, Maryland 21005
4777 USA
4778
4779 Phone: +1 443 395 8744
4780 EMail: [email protected]
4781 URI: <a href="http://www.cs.jhu.edu/~rgcole/">http://www.cs.jhu.edu/~rgcole/</a>
4782
4783
4784 Thomas Heide Clausen
4785 LIX, Ecole Polytechnique
4786 Palaiseau Cedex 91128
4787 France
4788
4789 Phone: +33 6 6058 9349
4790 EMail: [email protected]
4791 URI: <a href="http://www.ThomasClausen.org/">http://www.ThomasClausen.org/</a>
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812 Herberg, et al. Standards Track [Page 86]
4813 </pre>