idnits 2.17.1 draft-ietf-manet-olsrv2-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 25, 2013) is 3987 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 6779 (Obsoleted by RFC 7939) == Outdated reference: A later version (-04) exists of draft-ietf-manet-report-mib-03 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force U. Herberg 3 Internet-Draft Fujitsu Laboratories of America 4 Intended status: Standards Track R. Cole 5 Expires: November 26, 2013 US Army CERDEC 6 T. Clausen 7 LIX, Ecole Polytechnique 8 May 25, 2013 10 Definition of Managed Objects for the Optimized Link State Routing 11 Protocol version 2 12 draft-ietf-manet-olsrv2-mib-09 14 Abstract 16 This document defines the Management Information Base (MIB) module 17 for configuring and managing the Optimized Link State Routing 18 protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured 19 into configuration information, state information, performance 20 information, and notifications. This additional state and 21 performance information is useful to troubleshoot problems and 22 performance issues of the routing protocol. Two levels of compliance 23 allow this MIB module to be deployed on constrained routers. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on November 26, 2013. 42 Copyright Notice 44 Copyright (c) 2013 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. The Internet-Standard Management Framework . . . . . . . . . . 3 61 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 65 5.1. The Configuration Group . . . . . . . . . . . . . . . . . 5 66 5.2. The State Group . . . . . . . . . . . . . . . . . . . . . 5 67 5.3. The Performance Group . . . . . . . . . . . . . . . . . . 5 68 5.4. The Notifications Group . . . . . . . . . . . . . . . . . 6 69 5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 6 70 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 71 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 72 6.2. Relationship to the NHDP-MIB . . . . . . . . . . . . . . . 8 73 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 74 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . 75 76 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 78 77 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 79 78 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 79 79 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 80 80 12.1. Normative References . . . . . . . . . . . . . . . . . . . 80 81 12.2. Informative References . . . . . . . . . . . . . . . . . . 81 82 Appendix A. Note to the RFC Editor . . . . . . . . . . . . . . . 82 84 1. Introduction 86 This document defines the Management Information Base (MIB) module 87 for configuring and managing the Optimized Link State Routing 88 protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured 89 into configuration information, state information, performance 90 information, and notifications. In addition to configuration, this 91 additional state and performance information is useful to 92 troubleshoot problems and performance issues of the routing protocol. 93 Different levels of compliance allow implementers to use smaller 94 subsets of all defined objects, allowing for this MIB module to be 95 deployed on more constrained routers. 97 2. The Internet-Standard Management Framework 99 For a detailed overview of the documents that describe the current 100 Internet-Standard Management Framework, please refer to Section 7 of 101 [RFC3410]. 103 Managed objects are accessed via a virtual information store, termed 104 the Management Information Base or MIB. MIB objects are generally 105 accessed through the Simple Network Management Protocol (SNMP). 106 Objects in the MIB module are defined using the mechanisms defined in 107 the Structure of Management Information (SMI). This document 108 specifies a MIB module that is compliant to the SMIv2, which is 109 described in [RFC2578], [RFC2579], and [RFC2580]. 111 3. Conventions 113 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 114 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 115 "OPTIONAL" in this document are to be interpreted as described in 116 [RFC2119]. 118 4. Overview 120 The Optimized Link State Routing Protocol version 2 (OLSRv2) [OLSRv2] 121 is a table driven, proactive routing protocol, i.e., it exchanges 122 topology information with other routers in the network periodically. 123 OLSRv2 is an optimization of the classical link state routing 124 protocol. Its key concept is that of MultiPoint Relays (MPRs). Each 125 router selects a set of its neighbor routers (which "cover" all of 126 its symmetrically connected 2-hop neighbor routers) as MPRs. MPRs 127 are then used to achieve both flooding reduction and topology 128 reduction. 130 This document provides management and control capabilities of an 131 OLSRv2 instance, allowing to monitor the state and performance of an 132 OLSRV2 router, as well as to change settings of the OLSRv2 instance 133 (e.g., router or interface parameters such as message intervals 134 etc.). 136 As OLSRv2 relies on the neighborhood information discovered by the 137 "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol 138 (NHDP)" [RFC6130], the OLSRv2-MIB module is aligned with the NHDP-MIB 139 [RFC6779] module and augments several of the tables and objects in 140 the NHDP-MIB. In particular, common indexes for router interfaces 141 and discovered neighbors are used, as described in Section 5.2. 143 4.1. Terms 145 The following definitions apply throughout this document: 147 o Configuration Objects - switches, tables, objects which are 148 initialized to default settings or set through the management 149 interface defined by this MIB module. 151 o State Objects - automatically generated values which define the 152 current operating state of the OLSRv2 protocol process in the 153 router. 155 o Performance Objects - automatically generated values which help an 156 administrator or automated tool to assess the performance of the 157 OLSRv2 routing process on the router. 159 o Notification Objects - define triggers and associated notification 160 messages allowing for asynchronous tracking of pre-defined events 161 on the managed router. 163 5. Structure of the MIB Module 165 This section presents the structure of the OLSRv2-MIB module. The 166 objects are arranged into the following structure: 168 o olsrv2MIBObjects - defines objects forming the basis for the 169 OLSRv2-MIB module. These objects are divided up by function into 170 the following groups: 172 * Configuration Group - defining objects related to the 173 configuration of the OLSRv2 instance on the router. 175 * State Group - defining objects which reflect the current state 176 of the OLSRv2 instance running on the router. 178 * Performance Group -defining objects which are useful to a 179 management station when characterizing the performance of 180 OLSRv2 on the router and in the MANET. 182 o olsrv2MIBNotifications - objects defining OLSRv2-MIB module 183 notifications. 185 o olsrv2MIBConformance - defining the minimal and maximal 186 conformance requirements for implementations of this MIB module. 188 5.1. The Configuration Group 190 The OLSRv2 router is configured with a set of controls. The 191 authoritative list of configuration controls within the OLSRv2-MIB 192 module are found within the MIB module itself. Generally, an attempt 193 was made in developing the OLSRv2-MIB module to support all 194 configuration objects defined in [OLSRv2]. For all of the 195 configuration parameters, the same constraints and default values of 196 these parameters as defined in [OLSRv2] are followed. 198 5.2. The State Group 200 The State Group reports current state information of a router running 201 [OLSRv2]. The OLSRv2-MIB module State Group tables were designed to 202 contain the complete set of state information defined within the 203 information bases in [OLSRv2]. 205 The OLSRv2-MIB module State Group tables are constructed as 206 extensions to the corresponding tables within the State Group of the 207 NHDP-MIB [RFC6779] module. Use of the AUGMENTS clause is made, when 208 possible, to accomplish these table extensions. Further, the State 209 Group tables defined in this MIB module are aligned with the 210 according tables in the NHDP-MIB [RFC6779] module, as described in 211 Section 6.2. 213 5.3. The Performance Group 215 The Performance Group reports values relevant to system performance. 216 Frequent changes of sets or frequent recalculation of the routing set 217 or the MPRs can have a negative influence on the performance of 218 OLSRv2. This MIB module defines several objects that can be polled 219 in order to, e.g., calculate histories or monitor frequencies of 220 changes. This may help the network administrator to determine 221 unusual topology changes or other changes that affect stability and 222 reliability of the MANET. One such framework is specified in REPORT- 223 MIB [REPORT-MIB]. 225 5.4. The Notifications Group 227 The Notifications Group contains Control 228 (olsrv2NotificationsControl), Objects (olsrv2NotificationsObjects) 229 and States (olsrv2NotificationsStates), where the Control contains 230 definitions of objects to control the frequency of notifications 231 being generated. The Objects define the supported notifications and 232 the State is used to define additional information to be carried 233 within the notifications. 235 The olsrv2NotificationsObjects sub-tree contains the list of 236 notifications supported within the OLSRv2-MIB module and their 237 intended purpose or utility. 239 The same mechanisms for improving the network performance by reducing 240 the number of notifications apply as defined in Section 5.1 of 241 [RFC6779]. The following objects are used to define the thresholds 242 and time windows for specific notifications defined in the NHDP-MIB 243 module: olsrv2RoutingSetRecalculationCountThreshold, 244 olsrv2RoutingSetRecalculationCountWindow, 245 olsrv2MPRSetRecalculationCountThreshold, and 246 olsrv2MPRSetRecalculationCountWindow. 248 5.5. Tables and Indexing 250 The OLSRv2-MIB module's tables are indexed by the following 251 constructs: 253 o nhdpIfIndex - the ifIndex of the local router on which NHDP is 254 configured. This is defined in the NHDP-MIB. 256 o nhdpDiscIfIndex - a locally managed index representing a known 257 interface on a neighboring router. This is defined in the NHDP- 258 MIB. 260 o nhdpDiscRouterIndex - a locally managed index representing an ID 261 of a known neighboring router. This is defined in the NHDP-MIB. 263 o olsrv2LibOrigSetIndex - an incrementing number representing a 264 distinct index for the olsrv2LibOrigSetTable. 266 o olsrv2LibLocAttNetSetIndex - an incrementing number representing a 267 distinct index for the olsrv2LibLocAttNetSetTable. 269 o olsrv2TibAdRemoteRouterSetRouterId - this is an additional index 270 for each Remote Router's interface address associated with the 271 olsrv2TibAdRemoteRouterSetIpAddr. 273 o olsrv2TibRouterTopologySetIndex - an incrementing number 274 representing a distinct index for the 275 olsrv2TibRouterTopologySetTable. 277 o olsrv2TibAttNetworksSetIndex - an incrementing number representing 278 a distinct index for the olsrv2TibAttNetworksSetTable. 280 o olsrv2TibRoutingSetDestIpAddrType, olsrv2TibRoutingSetDestIpAddr 281 and olsrv2TibRoutingSetDestIpAddrPrefixLen - this is the address 282 of the destination, either the address of an interface of a 283 destination router, or the network address of an attached network. 285 These tables and their indexing are: 287 o olsrv2InterfaceTable - describes the OLSRv2 status on the NHDP 288 interfaces of this router. This table augments nhdpInterfaceEntry 289 and as such it is indexed by the nhdpIfIndex from the NHDP-MIB. 291 o olsrv2IibLinkSetTable - records all links from other routers which 292 are, or recently were, 1-hop neighbors. This table augments 293 nhdpIibLinkSetEntry and as such it is indexed by nhdpIfIndex and 294 nhdpDiscIfIndex. 296 o olsrv2Iib2HopSetTable - records network addresses of symmetric 297 2-hop neighbors and the links to the associated 1-hop neighbors. 298 This table augments nhdpIib2HopSetEntry and as such it is indexed 299 by nhdpIfIndex, nhdpDiscIfIndex, nhdpIib2HopSetIpAddressType and 300 nhdpIib2HopSetIpAddress. 302 o olsrv2LibOrigSetTable - records addresses that were recently used 303 as originator addresses by this router. This table is indexed by 304 olsrv2LibOrigSetIndex. 306 o olsrv2LibLocAttNetSetTable - records its local non-OLSRv2 307 interfaces via which it can act as gateways to other networks. 308 This table is indexed by olsrv2LibLocAttNetSetIndex. 310 o olsrv2NibNeighborSetTable - records all network addresses of each 311 1-hop neighbor. This table augments nhdpNibNeighborSetEntry and 312 as such it is indexed by the nhdpDiscRouterIndex. 314 o olsrv2TibAdRemoteRouterSetTable - records information describing 315 each remote router in the network that transmits TC messages. 316 This table is indexed by olsrv2TibAdRemoteRouterSetRouterId. 318 o olsrv2TibRouterTopologySetTable - records topology information 319 about the network. This table is indexed by 320 olsrv2TibRouterTopologySetIndex. 322 o olsrv2TibRoutableAddressTopologySetTable - records topology 323 information about the routable addresses within the MANET, and via 324 which routers they may be reached. This table is indexed by 325 olsrv2TibRoutableAddressTopologySetIndex. 327 o olsrv2TibAttNetworksSetTable - records information about networks 328 (which may be outside the MANET) attached to other routers and 329 their routable addresses. This table is indexed by 330 olsrv2TibAttNetworksSetIndex. 332 o olsrv2TibRoutingSetTable - records the first hop along a selected 333 path to each destination for which any such path is known. This 334 table is indexed by olsrv2TibRoutingSetDestIpAddrType, 335 olsrv2TibRoutingSetDestIpAddr, and 336 olsrv2TibRoutingSetDestIpAddrPrefixLen. 338 o olsrv2InterfacePerfTable - records performance counters for each 339 active OLSRv2 interface on this device. This table augments 340 nhdpInterfacePerfEntry and as such it is indexed by nhdpIfIndex 341 from the NHDP-MIB. 343 6. Relationship to Other MIB Modules 345 This section specifies the relationship of the MIB modules contained 346 in this document to other standards, particularly to standards 347 containing other MIB modules. MIB modules and specific definitions 348 imported from MIB modules that SHOULD be implemented in conjunction 349 with the MIB module contained within this document are identified in 350 this section. 352 6.1. Relationship to the SNMPv2-MIB 354 The System group in the SNMPv2-MIB [RFC3418] module is defined as 355 being mandatory for all systems, and the objects apply to the entity 356 as a whole. The System group provides identification of the 357 management entity and certain other system-wide data. The OLSRv2-MIB 358 module does not duplicate those objects. 360 6.2. Relationship to the NHDP-MIB 362 OLSRv2 depends on the neighborhood information that is discovered by 363 [RFC6130]. In order to access the Objects relating to discovered 364 neighbors, the State Group tables of the NHDP-MIB [RFC6779] module 365 are aligned with this MIB module. This is accomplished through the 366 use of the AUGMENTS capability of SMIv2 and the definition of 367 TEXTUAL-CONVENTIONS in the NHDP-MIB module: specifically the 368 NeighborRouterIndex. These object types are used to develop indexes 369 into common NHDP-MIB module and routing protocol State Group tables. 371 The values of these objects and the semantics of each individual 372 value SHOULD be identical for the two MIB modules within a given SNMP 373 context. This will allow for improved cross referencing of 374 information across the two MIB modules within a given SNMP context. 376 6.3. MIB modules required for IMPORTS 378 The following OLSRv2-MIB module IMPORTS objects from NHDP-MIB 379 [RFC6779], SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF 380 [RFC2580], IF-MIB [RFC2863] and INET-ADDRESS-MIB [RFC4001]. 382 7. Definitions 384 This section contains the OLSRv2-MIB module defined by the 385 specification. 387 OLSRv2-MIB DEFINITIONS ::= BEGIN 389 IMPORTS 391 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64, 392 Integer32, Unsigned32, mib-2, TimeTicks, 393 NOTIFICATION-TYPE 394 FROM SNMPv2-SMI -- RFC 2578 396 TEXTUAL-CONVENTION, TimeStamp, TruthValue 397 FROM SNMPv2-TC -- RFC 2579 399 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 400 FROM SNMPv2-CONF -- STD 58 402 InetAddressType, InetAddress, 403 InetAddressPrefixLength 404 FROM INET-ADDRESS-MIB -- RFC 3291 406 NeighborRouterIndex, nhdpInterfaceEntry, 407 nhdpIibLinkSetEntry, nhdpIib2HopSetEntry, 408 nhdpNibNeighborSetEntry, nhdpInterfacePerfEntry 409 FROM NHDP-MIB -- RFC 6779 410 ; 412 manetOlsrv2MIB MODULE-IDENTITY 413 LAST-UPDATED "201305251800Z" --25 May 2013 414 ORGANIZATION "IETF MANET Working Group" 415 CONTACT-INFO 416 "WG E-Mail: manet@ietf.org 417 WG Chairs: sratliff@cisco.com 418 jmacker@nrl.navy.mil 420 Editors: Ulrich Herberg 421 Fujitsu Laboratories of America 422 1240 East Arques Avenue 423 Sunnyvale, CA 94085 424 USA 425 ulrich@herberg.name 426 http://www.herberg.name/ 428 Thomas Heide Clausen 429 Ecole Polytechnique 430 LIX 431 91128 Palaiseau Cedex 432 France 433 http://www.thomasclausen.org/ 434 T.Clausen@computer.org 436 Robert G. Cole 437 US Army CERDEC 438 Space and Terrestrial Communications 439 6010 Frankford Street 440 Bldg 6010, Room 453H 441 Aberdeen Proving Ground, MD 21005 442 USA 443 +1 443 395-8744 444 robert.g.cole@us.army.mil 445 http://www.cs.jhu.edu/~rgcole/" 447 DESCRIPTION 448 "This OLSRv2-MIB module is applicable to routers 449 implementing the Optimized Link State Routing Protocol 450 version 2 (OLSRv2) defined in RFC XXXX. 452 Copyright (c) 2013 IETF Trust and the persons 453 identified as authors of the code. All rights reserved. 455 Redistribution and use in source and binary forms, with 456 or without modification, is permitted pursuant to, and 457 subject to the license terms contained in, the Simplified 458 BSD License set forth in Section 4.c of the IETF Trust's 459 Legal Provisions Relating to IETF Documents 460 (http://trustee.ietf.org/license-info). 462 This version of this MIB module is part of RFC YYYY; see 463 the RFC itself for full legal notices." 465 -- Revision History 466 REVISION "201305251800Z" -- 25 May 2013 467 DESCRIPTION 468 "Initial version of this MIB module, 469 published as RFC YYYY." 471 -- RFC-Editor assigns ZZZZ (this comment can be removed) 472 ::= { mib-2 ZZZZ } 474 -- 475 -- TEXTUAL CONVENTIONS 476 -- 478 Olsrv2MetricCompressedFormTC ::= TEXTUAL-CONVENTION 479 DISPLAY-HINT "x" 480 STATUS current 481 DESCRIPTION 482 "OLSRv2 Mertics are expressed in terms of a Link Metric 483 Compressed Form. This textual convention defines 484 the syntax of the metric objects consistent with 485 the definitions of the OLSRv2 Link Metric Compressed Form. 487 The 12-bit compressed form of a link metric uses a modified 488 form of a representation with an 8-bit mantissa (denoted a) 489 and a 4-bit exponent (denoted b). Note that if represented 490 as the 12 bit value 256b+a then the ordering of those 12 bit 491 values is identical to the ordering of the represented values. 493 The value so represented is (257+a)2^b - 256, where ^ denotes 494 exponentiation. This has a minimum value 495 (when a = 0 and b = 0) of MINIMUM_METRIC = 1 and a maximum 496 value (when a = 255 and b = 15) of MAXIMUM_METRIC = 2^24 - 256. 498 Hence the compressed form metric values range from 1 to 499 16776960. The special value of 0 is reserved for the 500 UNKNOWN_METRIC value." 501 SYNTAX Unsigned32 (0..16776960) 503 Olsrv2StatusTC ::= TEXTUAL-CONVENTION 504 STATUS current 505 DESCRIPTION 506 "Controls the operation of the OLSRv2 507 protocol on the device or a specific interface. 508 For example, for an interface: 'enabled' indicates 509 that OLSRv2 is permitted to operate, 510 and 'disabled' indicates that it is not." 511 SYNTAX INTEGER { 512 enabled (1), 513 disabled (2) 514 } 516 WillingnessTC ::= TEXTUAL-CONVENTION 517 DISPLAY-HINT "x" 518 STATUS current 519 DESCRIPTION 520 "A willingness value which evaluates to the 521 device's interest in participating in 522 a particular function, process or behavior. 524 The williness ranges from a low value of 525 WILL_NEVER(0) to a high value of 526 WILL_ALWAYS(15). For each parameter x, 527 there is an associated willingness value 528 W(x) such that WILL_NEVER < W(x) <= WILL_ALWAYS." 529 SYNTAX Unsigned32 (0..15) 531 -- 532 -- Top-Level Object Identifier Assignments 533 -- 535 olsrv2MIBNotifications OBJECT IDENTIFIER ::= { manetOlsrv2MIB 0 } 536 olsrv2MIBObjects OBJECT IDENTIFIER ::= { manetOlsrv2MIB 1 } 537 olsrv2MIBConformance OBJECT IDENTIFIER ::= { manetOlsrv2MIB 2 } 539 -- 540 -- olsrv2ConfigurationGroup 541 -- 543 -- Contains the OLSRv2 objects that configure specific 544 -- options that determine the overall performance and operation 545 -- of the OLSRv2 routing process. 547 olsrv2ConfigurationGroup OBJECT IDENTIFIER ::= {olsrv2MIBObjects 1} 549 olsrv2AdminStatus OBJECT-TYPE 550 SYNTAX Olsrv2StatusTC 551 MAX-ACCESS read-write 552 STATUS current 553 DESCRIPTION 554 "The configured status of the OLSRv2 process 555 on this device. 'enabled(1)' means that 556 OLSRv2 is configured to run on this device. 557 'disabled(2)' mean that the OLSRv2 process 558 is configured off. 560 Operation of the OLSRv2 routing protocol 561 requires the operation of the Neighborhood 562 Discovery Protocol (RFC 6130). Hence, this 563 object cannot have a status of 'enabled' 564 unless at least one interface on the device 565 is a MANET interface with NHDP enabled on that 566 interface. If a network manager attempts to 567 set this object to 'enabled' when no interfaces 568 on this device have HNDP enabled, the device 569 MUST fail the set with inconsistentValue. 570 If all device interfaces running NHDP become 571 disabled or removed, then the 572 olsrv2AdminStatus MUST be 'disabled'. 574 If the network manager, or other means, sets 575 this object to 'disabled', then the associated 576 interface specific objects, i.e., the 577 olsrv2InterfaceAdminStatus objects MUST all 578 be 'disabled'. 580 This object is persistent and when written 581 the entity SHOULD save the change to 582 non-volatile storage." 583 DEFVAL { 2 } 584 ::= { olsrv2ConfigurationGroup 1 } 586 olsrv2InterfaceTable OBJECT-TYPE 587 SYNTAX SEQUENCE OF Olsrv2InterfaceEntry 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "The olsrv2InterfaceTable describes the OLSRv2 592 status on the NHDP interfaces of this router. 593 As such, this table augments the nhdpInterfaceTable 594 defined in the NHDP-MIB (RFC 6779). NHDP interfaces 595 are explicitly defined by network management, CLI, 596 or other means for interfaces on the device that are 597 intended to run MANET protocols. The 598 olsrv2InterfaceTable contains a single object, the 599 olsrv2InterfaceAdminStatus object. This 600 object is set either by network management, or by 601 other means, e.g., CLI. 603 A conceptual row in this table exists if and only 604 if a corresponding entry in the nhdpInterfaceTable 605 exists. If the corresponding entry with nhdpIfIndex 606 value is deleted from the nhdpInterfaceTable, then 607 the entry in this table is automatically deleted and 608 OLSRv2 is disabled on this interface, 609 and all configuration and state information 610 related to this interface is to be removed 611 from memory. 613 The olsrv2InterfaceAdminStatus can only be 614 'enabled' if the corresponding olsrv2AdminStatus 615 object is also set to 'enabled'." 616 REFERENCE 617 "RFC XXXX - The Optimized Link State Routing Protocol 618 version 2, Clausen, T., Dearlove, C., Jacquet, P. 619 and U. Herberg, March 2013." 620 ::= { olsrv2ConfigurationGroup 2 } 622 olsrv2InterfaceEntry OBJECT-TYPE 623 SYNTAX Olsrv2InterfaceEntry 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "The olsrv2InterfaceEntry describes one OLSRv2 628 local interface configuration as indexed by 629 its nhdpIfIndex as defined in the 630 NHDP-MIB (RFC 6779). 632 The objects in this table are persistent and when 633 written the device SHOULD save the change to 634 non-volatile storage. For further information 635 on the storage behavior for these objects, refer 636 to the description for the nhdpIfRowStatus 637 object in the NHDP-MIB (RFC6779)." 638 REFERENCE 639 "RFC 6779 - The Neighborhood Discovery Protocol MIB, 640 Herberg, U., Cole, R.G. and I. Chakeres, 641 October 2012" 642 AUGMENTS { nhdpInterfaceEntry } 643 ::= { olsrv2InterfaceTable 1 } 645 Olsrv2InterfaceEntry ::= 646 SEQUENCE { 647 olsrv2InterfaceAdminStatus 648 Olsrv2StatusTC 649 } 651 olsrv2InterfaceAdminStatus OBJECT-TYPE 652 SYNTAX Olsrv2StatusTC 653 MAX-ACCESS read-create 654 STATUS current 655 DESCRIPTION 656 "The OLSRv2 interface's administrative status. 657 The value 'enabled(1)' denotes that the interface 658 is permitted to participate in the OLSRv2 routing 659 process. The value 'disabled(2)' denotes that 660 the interface is not permitted to participate 661 in the OLSRv2 routing process. 663 The configuration objects for the OLSRv2 routing 664 process, other than the administrative status objects, 665 are common to all interfaces on this device. 666 As such, the OLSRv2 configuration objects are globally 667 defined for the device and are not contained within 668 the olsrv2InterfaceTable." 669 DEFVAL { 2 } 670 ::= { olsrv2InterfaceEntry 1 } 672 olsrv2OrigIpAddrType OBJECT-TYPE 673 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 674 MAX-ACCESS read-write 675 STATUS current 676 DESCRIPTION 677 "The type of the olsrv2OrigIpAddr, as defined 678 in the InetAddress MIB module (RFC 4001). 680 Only the values 'ipv4(1)' and 681 'ipv6(2)' are supported." 682 REFERENCE 683 "RFC XXXX - The Optimized Link State Routing Protocol 684 version 2, Clausen, T., Dearlove, C., Jacquet, P. 685 and U. Herberg, March 2013." 686 ::= { olsrv2ConfigurationGroup 3 } 688 olsrv2OrigIpAddr OBJECT-TYPE 689 SYNTAX InetAddress (SIZE(4|16)) 690 MAX-ACCESS read-write 691 STATUS current 692 DESCRIPTION 693 "The router's originator address. An address that 694 is unique (within the MANET) to this router. 696 This object is persistent and when written 697 the entity SHOULD save the change to 698 non-volatile storage." 699 REFERENCE 700 "RFC XXXX - The Optimized Link State Routing Protocol 701 version 2, Clausen, T., Dearlove, C., Jacquet, P. 703 and U. Herberg, March 2013." 704 ::= { olsrv2ConfigurationGroup 4 } 706 -- 707 -- Local History Times 708 -- 710 olsrv2OHoldTime OBJECT-TYPE 711 SYNTAX Unsigned32 712 UNITS "milliseconds" 713 MAX-ACCESS read-write 714 STATUS current 715 DESCRIPTION 716 "olsrv2OHoldTime corresponds to 717 O_HOLD_TIME of OLSRv2 and represents the 718 time for which a recently used and replaced 719 originator address is used to recognize the router's 720 own messages. 722 Guidance for setting this object may be found 723 in Section 5 of the OLSRv2 specification (RFC XXXX), 724 which indicates that: 725 o olsrv2OHoldTime > 0 727 This object is persistent and when written 728 the entity SHOULD save the change to 729 non-volatile storage." 730 REFERENCE 731 "Section 5 on Protocol Parameters. 732 RFC XXXX - The Optimized Link State Routing Protocol 733 version 2, Clausen, T., Dearlove, C., Jacquet, P. 734 and U. Herberg, March 2013." 735 DEFVAL { 30000 } 736 ::= { olsrv2ConfigurationGroup 5 } 738 -- 739 -- Message intervals 740 -- 742 olsrv2TcInterval OBJECT-TYPE 743 SYNTAX Unsigned32 744 UNITS "centiseconds" 745 MAX-ACCESS read-write 746 STATUS current 747 DESCRIPTION 748 "olsrv2TcInterval corresponds to 749 TC_INTERVAL of OLSRv2 and represents the 750 maximum time between the transmission of 751 two successive TC messages by this router. 753 Guidance for setting this object may be found 754 in Section 5 of the OLSRv2 specification (RFC XXXX), 755 which indicates that: 757 o olsrv2TcInterval > 0 758 o olsrv2TcInterval >= olsrv2TcMinInterval 760 This object is persistent and when written 761 the entity SHOULD save the change to 762 non-volatile storage." 763 REFERENCE 764 "Section 5 on Protocol Parameters. 765 RFC XXXX - The Optimized Link State Routing Protocol 766 version 2, Clausen, T., Dearlove, C., Jacquet, P. 767 and U. Herberg, March 2013." 768 DEFVAL { 5000 } 769 ::= { olsrv2ConfigurationGroup 6 } 771 olsrv2TcMinInterval OBJECT-TYPE 772 SYNTAX Unsigned32 773 UNITS "centiseconds" 774 MAX-ACCESS read-write 775 STATUS current 776 DESCRIPTION 777 "olsrv2TcMinInterval corresponds to 778 TC_MIN_INTERVAL of OLSRv2 and represents 779 the minimum interval between transmission of 780 two successive TC messages by this router. 782 Guidance for setting this object may be found 783 in Section 5 of the OLSRv2 specification (RFC XXXX), 784 which indicates that: 785 o olsrv2TcInterval >= olsrv2TcMinInterval 787 This object is persistent and when written 788 the entity SHOULD save the change to 789 non-volatile storage." 790 REFERENCE 791 "Section 5 on Protocol Parameters. 792 RFC XXXX - The Optimized Link State Routing Protocol 793 version 2, Clausen, T., Dearlove, C., Jacquet, P. 794 and U. Herberg, March 2013." 795 DEFVAL { 1250 } 796 ::= { olsrv2ConfigurationGroup 7 } 797 -- 798 -- Advertised information validity times 799 -- 801 olsrv2THoldTime OBJECT-TYPE 802 SYNTAX Unsigned32 803 UNITS "milliseconds" 804 MAX-ACCESS read-write 805 STATUS current 806 DESCRIPTION 807 "olsrv2THoldTime corresponds to 808 T_HOLD_TIME of OLSRv2 and is used as the 809 minimum value in the TLV with 810 Type = VALIDITY_TIME included in all 811 TC messages sent by this router. 813 Guidance for setting this object may be found 814 in Section 5 of the OLSRv2 specification (RFC XXXX), 815 which indicates that: 816 o olsrv2THoldTime >= olsrv2TcInterval 817 o If TC messages can be lost, then 818 olsrv2THoldTime SHOULD be 819 significantly greater than olsrv2TcInterval; 820 a value >= 3 x olsrv2TcInterval is RECOMMENDED. 822 olsrv2THoldTime MUST be representable by way of the 823 exponent-mantissa notation as described in RFC 5497. 825 This object is persistent and when written 826 the entity SHOULD save the change to 827 non-volatile storage." 828 REFERENCE 829 "Section 5 on Protocol Parameters. 830 RFC XXXX - The Optimized Link State Routing Protocol 831 version 2, Clausen, T., Dearlove, C., Jacquet, P. 832 and U. Herberg, March 2013." 833 DEFVAL { 15000 } 834 ::= { olsrv2ConfigurationGroup 8 } 836 olsrv2AHoldTime OBJECT-TYPE 837 SYNTAX Unsigned32 838 UNITS "milliseconds" 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION 842 "olsrv2AHoldTime corresponds to 843 A_HOLD_TIME of OLSRv2 and represents 844 the period during which TC messages are sent 845 after they no longer have any advertised 846 information to report, but are sent in order 847 to accelerate outdated information removal by other routers. 849 Guidance for setting this object may be found 850 in Section 5 of the OLSRv2 specification (RFC XXXX), 851 which indicates that: 852 o If TC messages can be lost, then 853 olsrv2AHoldTime SHOULD be 854 significantly greater than olsrv2TcInterval; 855 a value >= 3 x olsrv2TcInterval is 856 RECOMMENDED. 858 olsrv2AHoldTime MUST be representable by way 859 of the exponent-mantissa notation as 860 described in RFC 5497. 862 This object is persistent and when written 863 the entity SHOULD save the change to 864 non-volatile storage." 865 REFERENCE 866 "Section 5 on Protocol Parameters. 867 RFC XXXX - The Optimized Link State Routing Protocol 868 version 2, Clausen, T., Dearlove, C., Jacquet, P. 869 and U. Herberg, March 2013." 870 DEFVAL { 15000 } 871 ::= { olsrv2ConfigurationGroup 9 } 873 -- 874 -- Received message validity times 875 -- 877 olsrv2RxHoldTime OBJECT-TYPE 878 SYNTAX Unsigned32 879 UNITS "milliseconds" 880 MAX-ACCESS read-write 881 STATUS current 882 DESCRIPTION 883 "olsrv2RxHoldTime corresponds to 884 RX_HOLD_TIME of OLSRv2 and represents the period 885 after receipt of a message by the appropriate OLSRv2 886 interface of this router for which that information 887 is recorded, in order that the message is recognized 888 as having been previously received on this OLSRv2 889 interface. 891 Guidance for setting this object may be found 892 in Section 5 of the OLSRv2 specification (RFC XXXX), 893 which indicates that: 894 o olsrv2RxHoldTime > 0 895 o This parameter SHOULD be greater 896 than the maximum difference in time that a 897 message may take to traverse the MANET, 898 taking into account any message forwarding 899 jitter as well as propagation, queuing, 900 and processing delays. 902 This object is persistent and when written 903 the entity SHOULD save the change to 904 non-volatile storage." 905 REFERENCE 906 "Section 5 on Protocol Parameters. 907 RFC XXXX - The Optimized Link State Routing Protocol 908 version 2, Clausen, T., Dearlove, C., Jacquet, P. 909 and U. Herberg, March 2013." 910 DEFVAL { 30000 } 911 ::= { olsrv2ConfigurationGroup 10 } 913 olsrv2PHoldTime OBJECT-TYPE 914 SYNTAX Unsigned32 915 UNITS "milliseconds" 916 MAX-ACCESS read-write 917 STATUS current 918 DESCRIPTION 919 "olsrv2PHoldTime corresponds to 920 P_HOLD_TIME of OLSRv2 and represents the period 921 after receipt of a message that is processed by 922 this router for which that information is recorded, 923 in order that the message is not processed again 924 if received again. 926 Guidance for setting this object may be found 927 in Section 5 of the OLSRv2 specification (RFC XXXX), 928 which indicates that: 929 o olsrv2PHoldTime > 0 930 o This parameter SHOULD be greater 931 than the maximum difference in time that a 932 message may take to traverse the MANET, 933 taking into account any message forwarding 934 jitter as well as propagation, queuing, 935 and processing delays. 937 This object is persistent and when written 938 the entity SHOULD save the change to 939 non-volatile storage." 940 REFERENCE 941 "Section 5 on Protocol Parameters. 942 RFC XXXX - The Optimized Link State Routing Protocol 943 version 2, Clausen, T., Dearlove, C., Jacquet, P. 944 and U. Herberg, March 2013." 945 DEFVAL { 30000 } 946 ::= { olsrv2ConfigurationGroup 11 } 948 olsrv2FHoldTime OBJECT-TYPE 949 SYNTAX Unsigned32 950 UNITS "milliseconds" 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 "olsrv2FHoldTime corresponds to 955 F_HOLD_TIME of OLSRv2 and represents the period 956 after receipt of a message that is forwarded by this 957 router for which that information is recorded, in order 958 that the message is not forwarded again if received again. 960 Guidance for setting this object may be found 961 in Section 5 of the OLSRv2 specification (RFC XXXX), 962 which indicates that: 963 o olsrv2FHoldTime > 0 964 o This parameter SHOULD be greater 965 than the maximum difference in time that a 966 message may take to traverse the MANET, 967 taking into account any message forwarding 968 jitter as well as propagation, queuing, 969 and processing delays. 971 This parameter SHOULD be greater 972 than the maximum difference in time that a 973 message may take to traverse the MANET, 974 taking into account any message forwarding 975 jitter as well as propagation, queuing, 976 and processing delays. 978 This object is persistent and when written 979 the entity SHOULD save the change to 980 non-volatile storage." 981 REFERENCE 982 "Section 5 on Protocol Parameters. 983 RFC XXXX - The Optimized Link State Routing Protocol 984 version 2, Clausen, T., Dearlove, C., Jacquet, P. 985 and U. Herberg, March 2013." 986 DEFVAL { 30000 } 987 ::= { olsrv2ConfigurationGroup 12 } 988 -- 989 -- Jitter times 990 -- 992 olsrv2TpMaxJitter OBJECT-TYPE 993 SYNTAX Unsigned32 994 UNITS "centiseconds" 995 MAX-ACCESS read-write 996 STATUS current 997 DESCRIPTION 998 "olsrv2TpMaxJitter corresponds to 999 TP_MAXJITTER of OLSRv2 and represents the value 1000 of MAXJITTER used in RFC5148 for periodically 1001 generated TC messages sent by this router. 1003 For constraints on these parameters see RFC 5148. 1005 This object is persistent and when written 1006 the entity SHOULD save the change to 1007 non-volatile storage." 1008 REFERENCE 1009 "Section 5 on Protocol Parameters. 1010 RFC XXXX - The Optimized Link State Routing Protocol 1011 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1012 and U. Herberg, March 2013." 1013 DEFVAL { 500 } 1014 ::= { olsrv2ConfigurationGroup 13 } 1016 olsrv2TtMaxJitter OBJECT-TYPE 1017 SYNTAX Unsigned32 1018 UNITS "centiseconds" 1019 MAX-ACCESS read-write 1020 STATUS current 1021 DESCRIPTION 1022 "olsrv2TtMaxJitter corresponds to 1023 TT_MAXJITTER of OLSRv2 and represents the value 1024 of MAXJITTER used in RFC5148 for externally 1025 triggered TC messages sent by this router. 1027 For constraints on these parameters see RFC 5148. 1029 This object is persistent and when written 1030 the entity SHOULD save the change to 1031 non-volatile storage." 1032 REFERENCE 1033 "Section 5 on Protocol Parameters. 1034 RFC XXXX - The Optimized Link State Routing Protocol 1035 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1037 and U. Herberg, March 2013." 1038 DEFVAL { 500 } 1039 ::= { olsrv2ConfigurationGroup 14 } 1041 olsrv2FMaxJitter OBJECT-TYPE 1042 SYNTAX Unsigned32 1043 UNITS "centiseconds" 1044 MAX-ACCESS read-write 1045 STATUS current 1046 DESCRIPTION 1047 "olsrv2FMaxJitter corresponds to 1048 F_MAXJITTER of OLSRv2 and represents the 1049 default value of MAXJITTER used in RFC 5148 for 1050 messages forwarded by this router. 1052 For constraints on these parameters see RFC 5148. 1054 This object is persistent and when written 1055 the entity SHOULD save the change to 1056 non-volatile storage." 1057 REFERENCE 1058 "Section 5 on Protocol Parameters. 1059 RFC XXXX - The Optimized Link State Routing Protocol 1060 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1061 and U. Herberg, March 2013." 1062 DEFVAL { 500 } 1063 ::= { olsrv2ConfigurationGroup 15 } 1065 -- 1066 -- Hop limits 1067 -- 1069 olsrv2TcHopLimit OBJECT-TYPE 1070 SYNTAX Unsigned32 (0..255) 1071 UNITS "hops" 1072 MAX-ACCESS read-write 1073 STATUS current 1074 DESCRIPTION 1075 "olsrv2TcHopLimit corresponds to 1076 TC_HOP_LIMIT of OLSRv2. 1078 Guidance for setting this object may be found 1079 in Section 5 of the OLSRv2 specification (RFC XXXX), 1080 which indicates that: 1081 o The maximum value of 1082 olsrv2TcHopLimit >= the network diameter 1084 in hops, a value of 255 is RECOMMENDED. 1085 o All values of olsrv2TcHopLimit >= 2. 1087 This object is persistent and when written 1088 the entity SHOULD save the change to 1089 non-volatile storage." 1090 REFERENCE 1091 "Section 5 on Protocol Parameters. 1092 RFC XXXX - The Optimized Link State Routing Protocol 1093 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1094 and U. Herberg, March 2013." 1095 DEFVAL { 255 } 1096 ::= { olsrv2ConfigurationGroup 16 } 1098 -- 1099 -- Willingness 1100 -- 1102 olsrv2WillRouting OBJECT-TYPE 1103 SYNTAX WillingnessTC 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 "olsrv2WillRouting corresponds to 1108 WILL_ROUTING of OLSRv2. 1110 Guidance for setting this object may be found 1111 in Section 5 of the OLSRv2 specification (RFC XXXX), 1112 which indicates that: 1113 o WILL_NEVER (0) <= olsrv2WillRouting <= 1114 WILL_ALWAYS (15) 1116 This object is persistent and when written 1117 the entity SHOULD save the change to 1118 non-volatile storage." 1119 REFERENCE 1120 "Section 5 on Protocol Parameters. 1121 RFC XXXX - The Optimized Link State Routing Protocol 1122 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1123 and U. Herberg, March 2013." 1124 DEFVAL { 7 } 1125 ::= { olsrv2ConfigurationGroup 17 } 1127 olsrv2WillFlooding OBJECT-TYPE 1128 SYNTAX WillingnessTC 1129 MAX-ACCESS read-write 1130 STATUS current 1131 DESCRIPTION 1132 "olsrv2WillFlooding corresponds to 1133 WILL_FLOODING of OLSRv2. 1135 Guidance for setting this object may be found 1136 in Section 5 of the OLSRv2 specification (RFC XXXX), 1137 which indicates that: 1138 o WILL_NEVER (0) <= olsrv2WillFlooding <= 1139 WILL_ALWAYS (15) 1141 This object is persistent and when written 1142 the entity SHOULD save the change to 1143 non-volatile storage." 1144 REFERENCE 1145 "Section 5 on Protocol Parameters. 1146 RFC XXXX - The Optimized Link State Routing Protocol 1147 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1148 and U. Herberg, March 2013." 1149 DEFVAL { 7 } 1150 ::= { olsrv2ConfigurationGroup 18 } 1152 olsrv2LinkMetricType OBJECT-TYPE 1153 SYNTAX Unsigned32 (0..255) 1154 MAX-ACCESS read-write 1155 STATUS current 1156 DESCRIPTION 1157 "olsrv2LinkMetricType corresponds to 1158 LINK_METRIC_TYPE of OLSRv2. 1160 This object is persistent and when written 1161 the entity SHOULD save the change to 1162 non-volatile storage." 1163 REFERENCE 1164 "Section 5 on Protocol Parameters. 1165 RFC XXXX - The Optimized Link State Routing Protocol 1166 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1167 and U. Herberg, March 2013." 1168 DEFVAL { 0 } 1169 ::= { olsrv2ConfigurationGroup 19 } 1171 -- 1172 -- olsrv2StateGroup 1173 -- 1174 -- 1175 -- Contains information describing the current state of 1176 -- the OLSRv2 process. 1177 -- 1179 olsrv2StateGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 2 } 1181 -- 1182 -- Interface Information Base (IIB) 1183 -- 1185 -- 1186 -- Link Set from RFC 6130, extended by L_in_metric, 1187 -- L_out_metric, and L_mpr_selector entries for each tuple 1188 -- 1190 olsrv2IibLinkSetTable OBJECT-TYPE 1191 SYNTAX SEQUENCE OF Olsrv2IibLinkSetEntry 1192 MAX-ACCESS not-accessible 1193 STATUS current 1194 DESCRIPTION 1195 "A Link Set of an interface records all links 1196 from other routers which are, or recently 1197 were, 1-hop neighbors." 1198 REFERENCE 1199 "RFC XXXX - The Optimized Link State Routing Protocol 1200 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1201 and U. Herberg, March 2013." 1202 ::= { olsrv2StateGroup 1 } 1204 olsrv2IibLinkSetEntry OBJECT-TYPE 1205 SYNTAX Olsrv2IibLinkSetEntry 1206 MAX-ACCESS not-accessible 1207 STATUS current 1208 DESCRIPTION 1209 "A Link Set consists of Link Tuples, each 1210 representing a single link indexed by the 1211 local and remote interface pair. Each Link Set 1212 from NHDP is extended by OLSRv2 by the following 1213 fields: 1215 (L_in_metric, L_out_metric, L_mpr_selector)" 1216 REFERENCE 1217 "RFC XXXX - The Optimized Link State Routing Protocol 1218 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1219 and U. Herberg, March 2013." 1220 AUGMENTS { nhdpIibLinkSetEntry } 1221 ::= { olsrv2IibLinkSetTable 1 } 1222 Olsrv2IibLinkSetEntry ::= 1223 SEQUENCE { 1224 olsrv2IibLinkSetInMetric 1225 Olsrv2MetricCompressedFormTC, 1226 olsrv2IibLinkSetOutMetric 1227 Olsrv2MetricCompressedFormTC, 1228 olsrv2IibLinkSetMprSelector 1229 TruthValue 1230 } 1232 olsrv2IibLinkSetInMetric OBJECT-TYPE 1233 SYNTAX Olsrv2MetricCompressedFormTC 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "olsrv2IibLinkSetInMetric is the metric of the link 1238 from the OLSRv2 interface with addresses 1239 L_neighbor_iface_addr_list to this OLSRv2 interface." 1240 REFERENCE 1241 "RFC XXXX - The Optimized Link State Routing Protocol 1242 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1243 and U. Herberg, March 2013." 1244 ::= { olsrv2IibLinkSetEntry 1 } 1246 olsrv2IibLinkSetOutMetric OBJECT-TYPE 1247 SYNTAX Olsrv2MetricCompressedFormTC 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "olsrv2IibLinkSetOutMetric is the metric of the 1252 link to the OLSRv2 interface with addresses 1253 L_neighbor_iface_addr_list from this OLSRv2 interface." 1254 REFERENCE 1255 "RFC XXXX - The Optimized Link State Routing Protocol 1256 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1257 and U. Herberg, March 2013." 1258 ::= { olsrv2IibLinkSetEntry 2 } 1260 olsrv2IibLinkSetMprSelector OBJECT-TYPE 1261 SYNTAX TruthValue 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "olsrv2IibLinkSetMprSelector is a boolean flag, 1266 recording whether this neighbor has selected this router 1267 as a flooding MPR, i.e., is a flooding MPR selector 1268 of this router." 1269 REFERENCE 1270 "RFC XXXX - The Optimized Link State Routing Protocol 1271 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1272 and U. Herberg, March 2013." 1273 ::= { olsrv2IibLinkSetEntry 3 } 1275 -- 1276 -- 2-Hop Set; from RFC 6130, extended by OLSRv2 by the 1277 -- following fields: N2_in_metric, N2_out_metric 1278 -- 1280 olsrv2Iib2HopSetTable OBJECT-TYPE 1281 SYNTAX SEQUENCE OF Olsrv2Iib2HopSetEntry 1282 MAX-ACCESS not-accessible 1283 STATUS current 1284 DESCRIPTION 1285 "A 2-Hop Set of an interface records network 1286 addresses of symmetric 2-hop neighbors, and 1287 the symmetric links to symmetric 1-hop neighbors 1288 through which these symmetric 2-hop neighbors 1289 can be reached. It consists of 2-Hop Tuples." 1290 REFERENCE 1291 "RFC XXXX - The Optimized Link State Routing Protocol 1292 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1293 and U. Herberg, March 2013." 1294 ::= { olsrv2StateGroup 2 } 1296 olsrv2Iib2HopSetEntry OBJECT-TYPE 1297 SYNTAX Olsrv2Iib2HopSetEntry 1298 MAX-ACCESS not-accessible 1299 STATUS current 1300 DESCRIPTION 1301 "olsrv2Iib2HopSetTable consists of 2-Hop Tuples, 1302 each representing a single network address of 1303 a symmetric 2-hop neighbor, and a single MANET 1304 interface of a symmetric 1-hop neighbor. 1305 Each 2-Hop Set from NHDP is extended by 1306 OLSRv2 by the following fields: 1308 (N2_in_metric, N2_out_metric)" 1309 REFERENCE 1310 "RFC XXXX - The Optimized Link State Routing Protocol 1311 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1312 and U. Herberg, March 2013." 1313 AUGMENTS { nhdpIib2HopSetEntry } 1314 ::= { olsrv2Iib2HopSetTable 1 } 1316 Olsrv2Iib2HopSetEntry ::= 1317 SEQUENCE { 1318 olsrv2Iib2HopSetInMetric 1319 Olsrv2MetricCompressedFormTC, 1320 olsrv2Iib2HopSetOutMetric 1321 Olsrv2MetricCompressedFormTC 1322 } 1324 olsrv2Iib2HopSetInMetric OBJECT-TYPE 1325 SYNTAX Olsrv2MetricCompressedFormTC 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "olsrv2Iib2HopSetInMetric is the neighbor metric 1330 from the router with address N2_2hop_iface_addr 1331 to the router with OLSRv2 interface addresses 1332 N2_neighbor_iface_addr_list." 1333 REFERENCE 1334 "RFC XXXX - The Optimized Link State Routing Protocol 1335 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1336 and U. Herberg, March 2013." 1337 ::= { olsrv2Iib2HopSetEntry 1 } 1339 olsrv2Iib2HopSetOutMetric OBJECT-TYPE 1340 SYNTAX Olsrv2MetricCompressedFormTC 1341 MAX-ACCESS read-only 1342 STATUS current 1343 DESCRIPTION 1344 "olsrv2Iib2HopSetOutMetric is the neighbor metric 1345 to the router with address N2_2hop_iface_addr 1346 from the router with OLSRv2 interface addresses 1347 N2_neighbor_iface_addr_list." 1348 REFERENCE 1349 "RFC XXXX - The Optimized Link State Routing Protocol 1350 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1351 and U. Herberg, March 2013." 1352 ::= { olsrv2Iib2HopSetEntry 2 } 1354 -- 1355 -- Local Information Base - as defined in RFC 6130, 1356 -- extended by the addition of an Originator Set, 1357 -- defined in Section 6.1 and a Local Attached 1358 -- Network Set, defined in Section 6.2. 1359 -- 1361 -- 1362 -- Originator Set 1363 -- 1364 olsrv2LibOrigSetTable OBJECT-TYPE 1365 SYNTAX SEQUENCE OF Olsrv2LibOrigSetEntry 1366 MAX-ACCESS not-accessible 1367 STATUS current 1368 DESCRIPTION 1369 "A router's Originator Set records addresses 1370 that were recently used as originator addresses 1371 by this router." 1372 REFERENCE 1373 "RFC XXXX - The Optimized Link State Routing Protocol 1374 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1375 and U. Herberg, March 2013." 1376 ::= { olsrv2StateGroup 3 } 1378 olsrv2LibOrigSetEntry OBJECT-TYPE 1379 SYNTAX Olsrv2LibOrigSetEntry 1380 MAX-ACCESS not-accessible 1381 STATUS current 1382 DESCRIPTION 1383 "A router's Originator Set consists of 1384 Originator Tuples: 1386 (O_orig_addr, O_time)" 1387 REFERENCE 1388 "RFC XXXX - The Optimized Link State Routing Protocol 1389 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1390 and U. Herberg, March 2013." 1391 INDEX { olsrv2LibOrigSetIndex } 1392 ::= { olsrv2LibOrigSetTable 1 } 1394 Olsrv2LibOrigSetEntry ::= 1395 SEQUENCE { 1396 olsrv2LibOrigSetIndex 1397 Unsigned32, 1398 olsrv2LibOrigSetIpAddrType 1399 InetAddressType, 1400 olsrv2LibOrigSetIpAddr 1401 InetAddress, 1402 olsrv2LibOrigSetExpireTime 1403 TimeStamp 1404 } 1406 olsrv2LibOrigSetIndex OBJECT-TYPE 1407 SYNTAX Unsigned32 (1..65535) 1408 MAX-ACCESS not-accessible 1409 STATUS current 1410 DESCRIPTION 1411 "The index for this table. The entries in this 1412 table expire according to the value of the 1413 olsrv2LibOrigSetExpireTime object. Further, 1414 the lifetime of each entry within this table 1415 is set by the O_HOLD_TIME parameter of the 1416 OLSRv2 protocol. So they timeout in the 1417 order that they are added to this table. 1419 The maximum value of this index is set to allow 1420 for the possibility of an extremely large number 1421 or addresses to be assigned to this OLSRv2 1422 router. This should not be an issue for MANET 1423 router deployments and configurations in the 1424 forseeable future. 1426 The index values assigned to new entries SHOULD 1427 be assigned in numerical order, beginning from 1428 1. New entries should be assigned the next 1429 available value, until the maximum value is 1430 assigned. Following this, the next assigned value 1431 SHOULD go back to 1 and begin incrementing again. 1432 If the table is full, then the next entry SHOULD 1433 be assigned an index value in sequence, replacing 1434 an existing entry (expiring this entry 1435 pre-maturely). 1437 OLSRv2 (RFC XXXX) defines the rules for managing 1438 entries within this table, e.g., populating 1439 and purging entries." 1440 REFERENCE 1441 "RFC XXXX - The Optimized Link State Routing Protocol 1442 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1443 and U. Herberg, March 2013." 1444 ::= { olsrv2LibOrigSetEntry 1 } 1446 olsrv2LibOrigSetIpAddrType OBJECT-TYPE 1447 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "The type of the olsrv2LibOrigSetIpAddr, 1452 as defined in the InetAddress MIB (RFC4001). 1454 Only the values 'ipv4(1)' and 1455 'ipv6(2)' are supported." 1456 REFERENCE 1457 "RFC XXXX - The Optimized Link State Routing Protocol 1458 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1459 and U. Herberg, March 2013." 1461 ::= { olsrv2LibOrigSetEntry 2 } 1463 olsrv2LibOrigSetIpAddr OBJECT-TYPE 1464 SYNTAX InetAddress (SIZE(4|16)) 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "An originator address recently employed 1469 by this router." 1470 REFERENCE 1471 "RFC XXXX - The Optimized Link State Routing Protocol 1472 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1473 and U. Herberg, March 2013." 1474 ::= { olsrv2LibOrigSetEntry 3 } 1476 olsrv2LibOrigSetExpireTime OBJECT-TYPE 1477 SYNTAX TimeStamp 1478 UNITS "centiseconds" 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "olsrv2LibOrigSetExpireTime specifies the value 1483 of sysUptime when this entry SHOULD expire and be 1484 removed from the olsrv2LibOrigSetTable. This time 1485 is determined at the time the entry is added, 1486 derived from the following expression: 1488 O_time := current time + O_HOLD_TIME 1490 where O_time is olsrv2LibOrigSetExpireTime, 1491 current_time is current sysUpTime and 1492 O_HOLD_TIME is a parameter of the OLSRv2 1493 protocol. In the event that the 1494 O_HOLD_TIME is changed, then the 1495 olsrv2LibOrigSetExpireTime needs to be 1496 recomputed for each of the entries in this Table." 1497 REFERENCE 1498 "RFC XXXX - The Optimized Link State Routing Protocol 1499 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1500 and U. Herberg, March 2013." 1501 ::= { olsrv2LibOrigSetEntry 4 } 1503 -- 1504 -- Local Attached Network Set 1505 -- 1507 olsrv2LibLocAttNetSetTable OBJECT-TYPE 1508 SYNTAX SEQUENCE OF Olsrv2LibLocAttNetSetEntry 1509 MAX-ACCESS not-accessible 1510 STATUS current 1511 DESCRIPTION 1512 "A router's Local Attached Network Set records 1513 its local non-OLSRv2 interfaces via which it 1514 can act as gateways to other networks." 1515 REFERENCE 1516 "RFC XXXX - The Optimized Link State Routing Protocol 1517 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1518 and U. Herberg, March 2013." 1519 ::= { olsrv2StateGroup 4 } 1521 olsrv2LibLocAttNetSetEntry OBJECT-TYPE 1522 SYNTAX Olsrv2LibLocAttNetSetEntry 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 "The entries include the Local Attached 1527 Network Tuples: 1529 (AL_net_addr, AL_dist, AL_metric) 1531 where: 1533 AL_net_addr is the network address 1534 of an attached network which can 1535 be reached via this router. 1537 AL_dist is the number of hops to 1538 the network with address AL_net_addr 1539 from this router. 1541 AL_metric is the metric of the link to 1542 the attached network with address 1543 AL_net_addr from this router. 1545 OLSRv2 (RFC XXXX) defines the rules for managing 1546 entries within this table, e.g., populating 1547 and purging entries. Specific instructions for the 1548 olsrv2LibLocAttNetSetEntry(s) are found in 1549 Section 7.2 and Section 17 of OLSRv2 (RFC XXXX)." 1550 REFERENCE 1551 "RFC XXXX - The Optimized Link State Routing Protocol 1552 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1553 and U. Herberg, March 2013." 1554 INDEX { olsrv2LibLocAttNetSetIndex } 1555 ::= { olsrv2LibLocAttNetSetTable 1 } 1556 Olsrv2LibLocAttNetSetEntry ::= 1557 SEQUENCE { 1558 olsrv2LibLocAttNetSetIndex 1559 Unsigned32, 1560 olsrv2LibLocAttNetSetIpAddrType 1561 InetAddressType, 1562 olsrv2LibLocAttNetSetIpAddr 1563 InetAddress, 1564 olsrv2LibLocAttNetSetIpAddrPrefixLen 1565 InetAddressPrefixLength, 1566 olsrv2LibLocAttNetSetDistance 1567 Unsigned32, 1568 olsrv2LibLocAttNetSetMetric 1569 Olsrv2MetricCompressedFormTC 1570 } 1572 olsrv2LibLocAttNetSetIndex OBJECT-TYPE 1573 SYNTAX Unsigned32 (1..65535) 1574 MAX-ACCESS not-accessible 1575 STATUS current 1576 DESCRIPTION 1577 "The index for this table. 1579 The maximum value of this index is set to allow 1580 for the possibility of an extremely large number 1581 interfaces acting as gateways to non-OLSRv2 1582 networks. This should allow for anticipated MANET 1583 router deployments and configurations in the 1584 forseeable future. 1586 The index values assigned to new entries should 1587 be assigned to the lowest available, un-assigned 1588 index value. This will keep the assigned index 1589 set tightly packed near the lowest available 1590 index value of 1. 1592 OLSRv2 (RFC XXXX) defines the rules for managing 1593 entries within this table, e.g., populating 1594 and purging entries." 1595 REFERENCE 1596 "RFC XXXX - The Optimized Link State Routing Protocol 1597 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1598 and U. Herberg, March 2013." 1599 ::= { olsrv2LibLocAttNetSetEntry 1 } 1601 olsrv2LibLocAttNetSetIpAddrType OBJECT-TYPE 1602 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "The type of the olsrv2LibLocAttNetSetIpAddr, as defined 1607 in the InetAddress MIB (RFC 4001). 1609 Only the values 'ipv4(1)' and 1610 'ipv6(2)' are supported." 1611 REFERENCE 1612 "RFC XXXX - The Optimized Link State Routing Protocol 1613 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1614 and U. Herberg, March 2013." 1615 ::= { olsrv2LibLocAttNetSetEntry 2 } 1617 olsrv2LibLocAttNetSetIpAddr OBJECT-TYPE 1618 SYNTAX InetAddress (SIZE(4|16)) 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "This is the network address of an attached 1623 network which can be reached via this router." 1624 REFERENCE 1625 "RFC XXXX - The Optimized Link State Routing Protocol 1626 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1627 and U. Herberg, March 2013." 1628 ::= { olsrv2LibLocAttNetSetEntry 3 } 1630 olsrv2LibLocAttNetSetIpAddrPrefixLen OBJECT-TYPE 1631 SYNTAX InetAddressPrefixLength 1632 UNITS "bits" 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "Indicates the number of leading one bits that form the 1637 mask to be logically ANDed with the destination address 1638 before being compared to the value in the 1639 olsrv2LibLocAttNetSetIpAddr field." 1640 REFERENCE 1641 "RFC XXXX - The Optimized Link State Routing Protocol 1642 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1643 and U. Herberg, March 2013." 1644 ::= { olsrv2LibLocAttNetSetEntry 4 } 1646 olsrv2LibLocAttNetSetDistance OBJECT-TYPE 1647 SYNTAX Unsigned32 (1..255) 1648 UNITS "hops" 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "This object specifies the number of hops 1653 to the network with address 1654 olsrv2LibLocAttNetSetIpAddr from this router." 1655 REFERENCE 1656 "RFC XXXX - The Optimized Link State Routing Protocol 1657 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1658 and U. Herberg, March 2013." 1659 ::= { olsrv2LibLocAttNetSetEntry 5 } 1661 olsrv2LibLocAttNetSetMetric OBJECT-TYPE 1662 SYNTAX Olsrv2MetricCompressedFormTC 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "This object specifies the metric of the 1667 link to the attached network with 1668 address AL_net_addr from this router." 1669 REFERENCE 1670 "RFC XXXX - The Optimized Link State Routing Protocol 1671 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1672 and U. Herberg, March 2013." 1673 ::= { olsrv2LibLocAttNetSetEntry 6 } 1675 -- 1676 -- Neighbor Information Base - as defined in RFC 6130, 1677 -- extended by OLSRv2 by the addition of the following 1678 -- elements to each Neighbor Tuple 1679 -- 1681 -- 1682 -- Neighbor Set 1683 -- 1685 olsrv2NibNeighborSetTable OBJECT-TYPE 1686 SYNTAX SEQUENCE OF Olsrv2NibNeighborSetEntry 1687 MAX-ACCESS not-accessible 1688 STATUS current 1689 DESCRIPTION 1690 "A router's Neighbor Set records all network 1691 addresses of each 1-hop neighbor. It consists 1692 of Neighbor Tuples, each representing a single 1693 1-hop neighbor. " 1694 REFERENCE 1695 "RFC XXXX - The Optimized Link State Routing Protocol 1696 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1697 and U. Herberg, March 2013." 1698 ::= { olsrv2StateGroup 5 } 1699 olsrv2NibNeighborSetEntry OBJECT-TYPE 1700 SYNTAX Olsrv2NibNeighborSetEntry 1701 MAX-ACCESS not-accessible 1702 STATUS current 1703 DESCRIPTION 1704 "Each Neighbor Tuple in the Neighbor Set, defined 1705 in RFC 6130, has these additional elements: 1706 N_orig_addr 1707 N_in_metric 1708 N_out_metric 1709 N_will_flooding 1710 N_will_routing 1711 N_flooding_mpr 1712 N_routing_mpr 1713 N_mpr_selector 1714 N_advertised 1715 defined here as extensions." 1716 REFERENCE 1717 "RFC XXXX - The Optimized Link State Routing Protocol 1718 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1719 and U. Herberg, March 2013." 1720 AUGMENTS { nhdpNibNeighborSetEntry } 1721 ::= { olsrv2NibNeighborSetTable 1 } 1723 Olsrv2NibNeighborSetEntry ::= 1724 SEQUENCE { 1725 olsrv2NibNeighborSetNOrigIpAddrType 1726 InetAddressType, 1727 olsrv2NibNeighborSetNOrigIpAddr 1728 InetAddress, 1729 olsrv2NibNeighborSetNInMetric 1730 Olsrv2MetricCompressedFormTC, 1731 olsrv2NibNeighborSetNOutMetric 1732 Olsrv2MetricCompressedFormTC, 1733 olsrv2NibNeighborSetNWillFlooding 1734 WillingnessTC, 1735 olsrv2NibNeighborSetNWillRouting 1736 WillingnessTC, 1737 olsrv2NibNeighborSetNFloodingMpr 1738 TruthValue, 1739 olsrv2NibNeighborSetNRoutingMpr 1740 TruthValue, 1741 olsrv2NibNeighborSetNMprSelector 1742 TruthValue, 1743 olsrv2NibNeighborSetNAdvertised 1744 TruthValue 1745 } 1747 olsrv2NibNeighborSetNOrigIpAddrType OBJECT-TYPE 1748 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "The type of the olsrv2NibNeighborSetNOrigIpAddr, as defined 1753 in the InetAddress MIB module (RFC4001). 1755 Only the values 'ipv4(1)' and 1756 'ipv6(2)' are supported." 1757 REFERENCE 1758 "RFC XXXX - The Optimized Link State Routing Protocol 1759 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1760 and U. Herberg, March 2013." 1761 ::= { olsrv2NibNeighborSetEntry 1 } 1763 olsrv2NibNeighborSetNOrigIpAddr OBJECT-TYPE 1764 SYNTAX InetAddress (SIZE(4|16)) 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "This is the originator IP address of the neighbor 1769 represented by this table entry." 1770 REFERENCE 1771 "RFC XXXX - The Optimized Link State Routing Protocol 1772 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1773 and U. Herberg, March 2013." 1774 ::= { olsrv2NibNeighborSetEntry 2 } 1776 olsrv2NibNeighborSetNInMetric OBJECT-TYPE 1777 SYNTAX Olsrv2MetricCompressedFormTC 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "This object is the neighbor metric of any 1782 link from this neighbor to an OLSRv2 interface 1783 of this router, i.e., the minimum of all corresponding 1784 L_in_metric with L_status = SYMMETRIC and 1785 L_in_metric != UNKNOWN_METRIC, UNKNOWN_METRIC 1786 if there are no such Link Tuples. UNKNOWN_METRIC 1787 has a value of 0." 1788 REFERENCE 1789 "RFC XXXX - The Optimized Link State Routing Protocol 1790 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1791 and U. Herberg, March 2013." 1792 ::= { olsrv2NibNeighborSetEntry 3 } 1794 olsrv2NibNeighborSetNOutMetric OBJECT-TYPE 1795 SYNTAX Olsrv2MetricCompressedFormTC 1796 MAX-ACCESS read-only 1797 STATUS current 1798 DESCRIPTION 1799 "This object is is the neighbor metric of any 1800 link from an OLSRv2 interface of this router 1801 to this neighbor, i.e., the minimum of 1802 all corresponding L_out_metric with 1803 L_status = SYMMETRIC and 1804 L_out_metric != UNKNOWN_METRIC, UNKNOWN_METRIC 1805 if there are no such Link Tuples. UNKNOWN_METRIC 1806 has a value of 0." 1807 REFERENCE 1808 "RFC XXXX - The Optimized Link State Routing Protocol 1809 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1810 and U. Herberg, March 2013." 1811 ::= { olsrv2NibNeighborSetEntry 4 } 1813 olsrv2NibNeighborSetNWillFlooding OBJECT-TYPE 1814 SYNTAX WillingnessTC 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "This object is the neighbor's willingness to be 1819 selected as a flooding MPR, in the range from 1820 WILL_NEVER to WILL_ALWAYS, both inclusive, taking 1821 the value WILL_NEVER if no OLSRv2 specific 1822 information is received from this neighbor." 1823 REFERENCE 1824 "RFC XXXX - The Optimized Link State Routing Protocol 1825 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1826 and U. Herberg, March 2013." 1827 ::= { olsrv2NibNeighborSetEntry 5 } 1829 olsrv2NibNeighborSetNWillRouting OBJECT-TYPE 1830 SYNTAX WillingnessTC 1831 MAX-ACCESS read-only 1832 STATUS current 1833 DESCRIPTION 1834 "This object is the neighbor's willingness to be 1835 selected as a routing MPR, in the range from 1836 WILL_NEVER to WILL_ALWAYS, both inclusive, taking 1837 the value WILL_NEVER if no OLSRv2 specific 1838 information is received from this neighbor." 1839 REFERENCE 1840 "RFC XXXX - The Optimized Link State Routing Protocol 1841 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1842 and U. Herberg, March 2013." 1844 ::= { olsrv2NibNeighborSetEntry 6 } 1846 olsrv2NibNeighborSetNFloodingMpr OBJECT-TYPE 1847 SYNTAX TruthValue 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "This object is a boolean flag, recording whether 1852 this neighbor is selected as a flooding MPR 1853 by this router." 1854 REFERENCE 1855 "RFC XXXX - The Optimized Link State Routing Protocol 1856 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1857 and U. Herberg, March 2013." 1858 ::= { olsrv2NibNeighborSetEntry 7 } 1860 olsrv2NibNeighborSetNRoutingMpr OBJECT-TYPE 1861 SYNTAX TruthValue 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "This object is a boolean flag, recording whether 1866 this neighbor is selected as a routing MPR 1867 by this router." 1868 REFERENCE 1869 "RFC XXXX - The Optimized Link State Routing Protocol 1870 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1871 and U. Herberg, March 2013." 1872 ::= { olsrv2NibNeighborSetEntry 8 } 1874 olsrv2NibNeighborSetNMprSelector OBJECT-TYPE 1875 SYNTAX TruthValue 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "This object is a boolean flag, 1880 recording whether this neighbor has selected this router 1881 as a routing MPR, i.e., is a routing MPR 1882 selector of this router. 1884 When set to 'true', then this router is selected as 1885 a routing MPR by the neighbor router. 1886 When set to 'false', 1887 then this router is not selected by the neighbor 1888 as a routing MPR." 1889 REFERENCE 1890 "RFC XXXX - The Optimized Link State Routing Protocol 1891 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1893 and U. Herberg, March 2013." 1894 ::= { olsrv2NibNeighborSetEntry 9 } 1896 olsrv2NibNeighborSetNAdvertised OBJECT-TYPE 1897 SYNTAX TruthValue 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION 1901 "This object, N_mpr_selector, is a boolean flag, 1902 recording whether this router has elected to 1903 advertise a link to this neighbor in its TC messages." 1904 REFERENCE 1905 "RFC XXXX - The Optimized Link State Routing Protocol 1906 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1907 and U. Herberg, March 2013." 1908 ::= { olsrv2NibNeighborSetEntry 10 } 1910 olsrv2NibNeighborSetTableAnsn OBJECT-TYPE 1911 SYNTAX Unsigned32 (0..65535) 1912 MAX-ACCESS read-only 1913 STATUS current 1914 DESCRIPTION 1915 "Advertised Neighbor Sequence Number (ANSN), is 1916 a variable, whose value is included in TC messages to 1917 indicate the freshness of the information transmitted." 1918 REFERENCE 1919 "RFC XXXX - The Optimized Link State Routing Protocol 1920 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1921 and U. Herberg, March 2013." 1922 ::= { olsrv2StateGroup 6 } 1924 -- 1925 -- Topology Information Base - this Information 1926 -- Base is specific to OLSRv2, and is defined in 1927 -- Section 10 of RFC XXXX. 1928 -- 1930 -- 1931 -- Advertising Remote Router Set 1932 -- 1934 olsrv2TibAdRemoteRouterSetTable OBJECT-TYPE 1935 SYNTAX SEQUENCE OF Olsrv2TibAdRemoteRouterSetEntry 1936 MAX-ACCESS not-accessible 1937 STATUS current 1938 DESCRIPTION 1939 "A router's Advertising Remote Router Set records 1940 information describing each remote router in the 1941 network that transmits TC messages." 1942 REFERENCE 1943 "RFC XXXX - The Optimized Link State Routing Protocol 1944 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1945 and U. Herberg, March 2013." 1946 ::= { olsrv2StateGroup 7 } 1948 olsrv2TibAdRemoteRouterSetEntry OBJECT-TYPE 1949 SYNTAX Olsrv2TibAdRemoteRouterSetEntry 1950 MAX-ACCESS not-accessible 1951 STATUS current 1952 DESCRIPTION 1953 "A router's Advertised Neighbor Set Table entry 1954 consists of Advertising Remote Router Tuples: 1956 (AR_orig_addr, AR_seq_number, AR_time) 1958 Addresses associated with this router are 1959 found in the NHDP-MIB module's nhdpDiscIfSetTable. 1961 OLSRv2 (RFC XXXX) defines the rules for managing 1962 entries within this table, e.g., populating 1963 and purging entries. Specific instructions for the 1964 olsrv2TibAdRemoteRouterSetEntry(s) are found in 1965 Section 10.1 and Section 17 of OLSRv2 (RFC XXXX)." 1966 REFERENCE 1967 "RFC XXXX - The Optimized Link State Routing Protocol 1968 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1969 and U. Herberg, March 2013." 1970 INDEX { olsrv2TibAdRemoteRouterSetRouterId } 1971 ::= { olsrv2TibAdRemoteRouterSetTable 1 } 1973 Olsrv2TibAdRemoteRouterSetEntry ::= 1974 SEQUENCE { 1975 olsrv2TibAdRemoteRouterSetIpAddrType 1976 InetAddressType, 1977 olsrv2TibAdRemoteRouterSetIpAddr 1978 InetAddress, 1979 olsrv2TibAdRemoteRouterSetRouterId 1980 NeighborRouterIndex, 1981 olsrv2TibAdRemoteRouterSetMaxSeqNo 1982 Unsigned32, 1983 olsrv2TibAdRemoteRouterSetExpireTime 1984 TimeStamp 1985 } 1987 olsrv2TibAdRemoteRouterSetIpAddrType OBJECT-TYPE 1988 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1989 MAX-ACCESS read-only 1990 STATUS current 1991 DESCRIPTION 1992 "The type of the olsrv2TibAdRemoteRouterSetIpAddr, 1993 as defined in the InetAddress MIB module (RFC4001). 1995 Only the values 'ipv4(1)' and 1996 'ipv6(2)' are supported." 1997 REFERENCE 1998 "RFC XXXX - The Optimized Link State Routing Protocol 1999 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2000 and U. Herberg, March 2013." 2001 ::= { olsrv2TibAdRemoteRouterSetEntry 1 } 2003 olsrv2TibAdRemoteRouterSetIpAddr OBJECT-TYPE 2004 SYNTAX InetAddress (SIZE(4|16)) 2005 MAX-ACCESS read-only 2006 STATUS current 2007 DESCRIPTION 2008 "This is the originator address of a received 2009 TC message." 2010 REFERENCE 2011 "RFC XXXX - The Optimized Link State Routing Protocol 2012 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2013 and U. Herberg, March 2013." 2014 ::= { olsrv2TibAdRemoteRouterSetEntry 2 } 2016 olsrv2TibAdRemoteRouterSetRouterId OBJECT-TYPE 2017 SYNTAX NeighborRouterIndex 2018 MAX-ACCESS not-accessible 2019 STATUS current 2020 DESCRIPTION 2021 "This object is an index for each remote router's 2022 interface address associated with the 2023 olsrv2TibAdRemoteRouterSetIpAddr. 2025 The NeighborRouterIndex should be assigned in 2026 sequence beginning at a value of 1. The value 2027 for each discovered remote router's index MUST 2028 remain constant at least from one re-initialization 2029 of the entity's network management agent to the next 2030 re-initialization, except if an application is 2031 deleted and re-created. 2033 OLSRv2 (RFC XXXX) defines the rules for managing 2034 entries within this table, e.g., populating 2035 and purging entries." 2036 REFERENCE 2037 "RFC XXXX - The Optimized Link State Routing Protocol 2038 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2039 and U. Herberg, March 2013." 2040 ::= { olsrv2TibAdRemoteRouterSetEntry 3 } 2042 olsrv2TibAdRemoteRouterSetMaxSeqNo OBJECT-TYPE 2043 SYNTAX Unsigned32 (0..65535) 2044 MAX-ACCESS read-only 2045 STATUS current 2046 DESCRIPTION 2047 "This is the greatest ANSN in any TC message 2048 received which originated from the router 2049 with originator address 2050 olsrv2TibAdRemoteRouterSetIpAddr." 2051 REFERENCE 2052 "RFC XXXX - The Optimized Link State Routing Protocol 2053 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2054 and U. Herberg, March 2013." 2055 ::= { olsrv2TibAdRemoteRouterSetEntry 4 } 2057 olsrv2TibAdRemoteRouterSetExpireTime OBJECT-TYPE 2058 SYNTAX TimeStamp 2059 UNITS "centiseconds" 2060 MAX-ACCESS not-accessible 2061 STATUS current 2062 DESCRIPTION 2063 "olsrv2TibAdRemoteRouterSetExpireTime specifies the value 2064 of sysUptime when this entry SHOULD expire and be 2065 removed from the olsrv2TibAdRemoteRouterSetTable." 2066 REFERENCE 2067 "RFC XXXX - The Optimized Link State Routing Protocol 2068 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2069 and U. Herberg, March 2013." 2070 ::= { olsrv2TibAdRemoteRouterSetEntry 5 } 2072 -- 2073 -- Router Topology Set 2074 -- 2076 olsrv2TibRouterTopologySetTable OBJECT-TYPE 2077 SYNTAX SEQUENCE OF Olsrv2TibTopologySetEntry 2078 MAX-ACCESS not-accessible 2079 STATUS current 2080 DESCRIPTION 2081 "A router's Router Topology Set records topology 2082 information about the network." 2083 REFERENCE 2084 "RFC XXXX - The Optimized Link State Routing Protocol 2085 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2086 and U. Herberg, March 2013." 2087 ::= { olsrv2StateGroup 8 } 2089 olsrv2TibRouterTopologySetEntry OBJECT-TYPE 2090 SYNTAX Olsrv2TibTopologySetEntry 2091 MAX-ACCESS not-accessible 2092 STATUS current 2093 DESCRIPTION 2094 "It consists of Router Topology Tuples: 2096 (TR_from_orig_addr, TR_to_orig_addr, 2097 TR_seq_number, TR_metric, TR_time). 2099 OLSRv2 (RFC XXXX) defines the rules for managing 2100 entries within this table, e.g., populating 2101 and purging entries. Specific instructions for the 2102 olsrv2TibRouterTopologySetEntry(s) are found in 2103 Section 10.2 and Section 17 of OLSRv2 (RFC XXXX)." 2104 REFERENCE 2105 "RFC XXXX - The Optimized Link State Routing Protocol 2106 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2107 and U. Herberg, March 2013." 2108 INDEX { olsrv2TibRouterTopologySetIndex } 2109 ::= { olsrv2TibRouterTopologySetTable 1 } 2111 Olsrv2TibTopologySetEntry ::= 2112 SEQUENCE { 2113 olsrv2TibRouterTopologySetIndex 2114 Unsigned32, 2115 olsrv2TibRouterTopologySetFromOrigIpAddrType 2116 InetAddressType, 2117 olsrv2TibRouterTopologySetFromOrigIpAddr 2118 InetAddress, 2119 olsrv2TibRouterTopologySetToOrigIpAddrType 2120 InetAddressType, 2121 olsrv2TibRouterTopologySetToOrigIpAddr 2122 InetAddress, 2123 olsrv2TibRouterTopologySetSeqNo 2124 Unsigned32, 2125 olsrv2TibRouterTopologySetMetric 2126 Olsrv2MetricCompressedFormTC, 2127 olsrv2TibRouterTopologySetExpireTime 2128 TimeStamp 2130 } 2132 olsrv2TibRouterTopologySetIndex OBJECT-TYPE 2133 SYNTAX Unsigned32 (1..16777215) 2134 MAX-ACCESS not-accessible 2135 STATUS current 2136 DESCRIPTION 2137 "The index for this table. The entries in this 2138 table expire according to the value of the 2139 olsrv2TibRouterTopologySetExpireTime object. 2140 Further, the lifetime of each entry within this 2141 table is set by the validity time in the 2142 OLSRv2 TC message. As such, they are expected 2143 to timeout roughly in the order that they are 2144 added to this table. 2146 The maximum value of this index is set to allow 2147 for the possibility of an extremely large number 2148 Topology Set tuples to be added to this OLSRv2 2149 router. This should not be an issue for MANET 2150 router deployments and configurations in the 2151 forseeable future. 2153 The index values assigned to new entries SHOULD 2154 be assigned in numerical order, beginning from 2155 1. New entries should be assigned the next 2156 available value, until the maximum value is 2157 assigned. Following this, the next assigned value 2158 SHOULD go back to 1 and begin incrementing again. 2159 If the table is full, then the next entry SHOULD 2160 be assigned an index value in sequence, replacing 2161 an existing entry (expiring this entry 2162 pre-maturely). 2164 OLSRv2 (RFC XXXX) defines the rules for managing 2165 entries within this table, e.g., populating 2166 and purging entries." 2167 REFERENCE 2168 "RFC XXXX - The Optimized Link State Routing Protocol 2169 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2170 and U. Herberg, March 2013." 2171 ::= { olsrv2TibRouterTopologySetEntry 1 } 2173 olsrv2TibRouterTopologySetFromOrigIpAddrType OBJECT-TYPE 2174 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2175 MAX-ACCESS read-only 2176 STATUS current 2177 DESCRIPTION 2178 "The type of the olsrv2TibRouterTopologySetFromOrigIpAddr, 2179 as defined in the InetAddress MIB module (RFC4001). 2181 Only the values 'ipv4(1)' and 2182 'ipv6(2)' are supported." 2183 REFERENCE 2184 "RFC XXXX - The Optimized Link State Routing Protocol 2185 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2186 and U. Herberg, March 2013." 2187 ::= { olsrv2TibRouterTopologySetEntry 2 } 2189 olsrv2TibRouterTopologySetFromOrigIpAddr OBJECT-TYPE 2190 SYNTAX InetAddress (SIZE(4|16)) 2191 MAX-ACCESS read-only 2192 STATUS current 2193 DESCRIPTION 2194 "This is the originator address of a router which can 2195 reach the router with originator address TR_to_orig_addr 2196 in one hop." 2197 REFERENCE 2198 "RFC XXXX - The Optimized Link State Routing Protocol 2199 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2200 and U. Herberg, March 2013." 2201 ::= { olsrv2TibRouterTopologySetEntry 3 } 2203 olsrv2TibRouterTopologySetToOrigIpAddrType OBJECT-TYPE 2204 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "The type of the olsrv2TibRouterTopologySetToOrigIpAddr, 2209 as defined in the InetAddress MIB module (RFC4001). 2211 Only the values 'ipv4(1)' and 2212 'ipv6(2)' are supported." 2213 REFERENCE 2214 "RFC XXXX - The Optimized Link State Routing Protocol 2215 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2216 and U. Herberg, March 2013." 2217 ::= { olsrv2TibRouterTopologySetEntry 4 } 2219 olsrv2TibRouterTopologySetToOrigIpAddr OBJECT-TYPE 2220 SYNTAX InetAddress (SIZE(4|16)) 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "This is the originator address of a router which can be 2225 reached by the router with originator address 2226 TR_to_orig_addr in one hop." 2227 REFERENCE 2228 "RFC XXXX - The Optimized Link State Routing Protocol 2229 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2230 and U. Herberg, March 2013." 2231 ::= { olsrv2TibRouterTopologySetEntry 5 } 2233 olsrv2TibRouterTopologySetSeqNo OBJECT-TYPE 2234 SYNTAX Unsigned32 (0..65535) 2235 MAX-ACCESS read-only 2236 STATUS current 2237 DESCRIPTION 2238 "This is the greatest Assigned Neighbor Sequence 2239 Number (ANSN) in any TC message 2240 received which originated from the router 2241 with originator address TR_from_orig_addr 2242 (i.e., which contributed to the information 2243 contained in this Tuple). 2245 Sequence numbers are used in the OLSRv2 protocol 2246 for the purpose of discarding 'old' information, 2247 i.e., messages received out of order. However 2248 with a limited number of bits for representing 2249 sequence numbers, wrap-around (that the sequence 2250 number is incremented from the maximum possible 2251 value to zero) will occur. To prevent this from 2252 interfering with the operation of this protocol, 2253 the following MUST be observed when determining 2254 the ordering of sequence numbers. 2256 The term MAXVALUE designates in the following one 2257 more than the largest possible value for a sequence 2258 number. For a 16 bit sequence number (as are those 2259 defined in this specification) MAXVALUE is 65536. 2261 The sequence number S1 is said to be 'greater than' 2262 the sequence number S2 if: 2264 o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR 2266 o S2 > S1 AND S2 - S1 > MAXVALUE/2 2268 When sequence numbers S1 and S2 differ by MAXVALUE/2 2269 their ordering cannot be determined. In this case, 2270 which should not occur, either ordering may be 2271 assumed. 2273 Thus when comparing two messages, it is possible 2274 - even in the presence of wrap-around - to determine 2275 which message contains the most recent information." 2276 REFERENCE 2277 "RFC XXXX - The Optimized Link State Routing Protocol 2278 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2279 and U. Herberg, March 2013." 2280 ::= { olsrv2TibRouterTopologySetEntry 6 } 2282 olsrv2TibRouterTopologySetMetric OBJECT-TYPE 2283 SYNTAX Olsrv2MetricCompressedFormTC 2284 MAX-ACCESS read-only 2285 STATUS current 2286 DESCRIPTION 2287 "This is the neighbor metric from the router 2288 with originator address TR_from_orig_addr to 2289 the router with originator address 2290 TR_to_orig_addr." 2291 REFERENCE 2292 "RFC XXXX - The Optimized Link State Routing Protocol 2293 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2294 and U. Herberg, March 2013." 2295 ::= { olsrv2TibRouterTopologySetEntry 7 } 2297 olsrv2TibRouterTopologySetExpireTime OBJECT-TYPE 2298 SYNTAX TimeStamp 2299 UNITS "centiseconds" 2300 MAX-ACCESS not-accessible 2301 STATUS current 2302 DESCRIPTION 2303 "olsrv2TibRouterTopologySetExpireTime specifies the value 2304 of sysUptime when this entry SHOULD expire and be 2305 removed from the olsrv2TibRouterTopologySetTable." 2306 REFERENCE 2307 "RFC XXXX - The Optimized Link State Routing Protocol 2308 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2309 and U. Herberg, March 2013." 2310 ::= { olsrv2TibRouterTopologySetEntry 8 } 2312 -- 2313 -- Routable Address Topology Set 2314 -- 2316 olsrv2TibRoutableAddressTopologySetTable OBJECT-TYPE 2317 SYNTAX SEQUENCE OF Olsrv2TibRoutableAddressTopologySetEntry 2318 MAX-ACCESS not-accessible 2319 STATUS current 2320 DESCRIPTION 2321 "A router's Routable Address Topology Set records topology 2322 information about the routable addresses within the MANET, 2323 and via which routers they may be reached." 2324 REFERENCE 2325 "RFC XXXX - The Optimized Link State Routing Protocol 2326 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2327 and U. Herberg, March 2013." 2328 ::= { olsrv2StateGroup 9 } 2330 olsrv2TibRoutableAddressTopologySetEntry OBJECT-TYPE 2331 SYNTAX Olsrv2TibRoutableAddressTopologySetEntry 2332 MAX-ACCESS not-accessible 2333 STATUS current 2334 DESCRIPTION 2335 "It consists of Router Topology Tuples: 2337 (TA_from_orig_addr, TA_dest_addr, 2338 TA_seq_number, TA_metric, TA_time) 2340 OLSRv2 (RFC XXXX) defines the rules for managing 2341 entries within this table, e.g., populating 2342 and purging entries. Specific instructions for the 2343 olsrv2TibRoutableAddressTopologySetEntry(s) are found 2344 in Section 10.3 and Section 17 of OLSRv2 (RFC XXXX)." 2345 REFERENCE 2346 "RFC XXXX - The Optimized Link State Routing Protocol 2347 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2348 and U. Herberg, March 2013." 2349 INDEX { olsrv2TibRoutableAddressTopologySetIndex } 2350 ::= { olsrv2TibRoutableAddressTopologySetTable 1 } 2352 Olsrv2TibRoutableAddressTopologySetEntry ::= 2353 SEQUENCE { 2354 olsrv2TibRoutableAddressTopologySetIndex 2355 Unsigned32, 2356 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType 2357 InetAddressType, 2358 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr 2359 InetAddress, 2360 olsrv2TibRoutableAddressTopologySetDestIpAddrType 2361 InetAddressType, 2362 olsrv2TibRoutableAddressTopologySetDestIpAddr 2363 InetAddress, 2364 olsrv2TibRoutableAddressTopologySetSeqNo 2365 Unsigned32, 2366 olsrv2TibRoutableAddressTopologySetMetric 2367 Olsrv2MetricCompressedFormTC, 2368 olsrv2TibRoutableAddressTopologySetExpireTime 2369 TimeStamp 2370 } 2372 olsrv2TibRoutableAddressTopologySetIndex OBJECT-TYPE 2373 SYNTAX Unsigned32 (1..16777215) 2374 MAX-ACCESS not-accessible 2375 STATUS current 2376 DESCRIPTION 2377 "The index for this table. The entries in this 2378 table expire according to the value of the 2379 olsrv2TibRoutableAddressTopologySetExpireTime object. 2380 Further, the lifetime of each entry within this 2381 table is set by the validity time in the 2382 OLSRv2 TC message. As such, they are expected 2383 to timeout roughly in the order that they are 2384 added to this table. 2386 The maximum value of this index is set to allow 2387 for the possibility of an extremely large number 2388 Routable Address Topology Set tuples to be 2389 added to this OLSRv2 router. This should not be 2390 an issue for MANET router deployments and 2391 configurations in the foreseeable future. 2393 The index values assigned to new entries SHOULD 2394 be assigned in numerical order, beginning from 2395 1. New entries should be assigned the next 2396 available value, until the maximum value is 2397 assigned. Following this, the next assigned value 2398 SHOULD go back to 1 and begin incrementing again. 2399 If the table is full, then the next entry SHOULD 2400 be assigned an index value in sequence, replacing 2401 an existing entry (expiring this entry 2402 pre-maturely). 2404 OLSRv2 (RFC XXXX) defines the rules for managing 2405 entries within this table, e.g., populating 2406 and purging entries." 2407 REFERENCE 2408 "RFC XXXX - The Optimized Link State Routing Protocol 2409 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2410 and U. Herberg, March 2013." 2411 ::= { olsrv2TibRoutableAddressTopologySetEntry 1 } 2413 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType OBJECT-TYPE 2414 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2415 MAX-ACCESS read-only 2416 STATUS current 2417 DESCRIPTION 2418 "The type of the 2419 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, 2420 as defined in the InetAddress MIB module (RFC 4001). 2422 Only the values 'ipv4(1)' and 2423 'ipv6(2)' are supported." 2424 REFERENCE 2425 "RFC XXXX - The Optimized Link State Routing Protocol 2426 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2427 and U. Herberg, March 2013." 2428 ::= { olsrv2TibRoutableAddressTopologySetEntry 2 } 2430 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr OBJECT-TYPE 2431 SYNTAX InetAddress (SIZE(4|16)) 2432 MAX-ACCESS read-only 2433 STATUS current 2434 DESCRIPTION 2435 "This is the originator address of a router which can 2436 reach the router with routable address TA_dest_addr 2437 in one hop." 2438 REFERENCE 2439 "RFC XXXX - The Optimized Link State Routing Protocol 2440 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2441 and U. Herberg, March 2013." 2442 ::= { olsrv2TibRoutableAddressTopologySetEntry 3 } 2444 olsrv2TibRoutableAddressTopologySetDestIpAddrType OBJECT-TYPE 2445 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2446 MAX-ACCESS read-only 2447 STATUS current 2448 DESCRIPTION 2449 "The type of the olsrv2TibRouterTopologySetToOrigIpAddr, 2450 as defined in the InetAddress MIB module (RFC 4001). 2452 Only the values 'ipv4(1)' and 2453 'ipv6(2)' are supported." 2454 REFERENCE 2455 "RFC XXXX - The Optimized Link State Routing Protocol 2456 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2457 and U. Herberg, March 2013." 2458 ::= { olsrv2TibRoutableAddressTopologySetEntry 4 } 2460 olsrv2TibRoutableAddressTopologySetDestIpAddr OBJECT-TYPE 2461 SYNTAX InetAddress (SIZE(4|16)) 2462 MAX-ACCESS read-only 2463 STATUS current 2464 DESCRIPTION 2465 "This is a routable address of a router which can be 2466 reached by the router with originator address 2467 TA_from_orig_addr in one hop." 2468 REFERENCE 2469 "RFC XXXX - The Optimized Link State Routing Protocol 2470 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2471 and U. Herberg, March 2013." 2472 ::= { olsrv2TibRoutableAddressTopologySetEntry 5 } 2474 olsrv2TibRoutableAddressTopologySetSeqNo OBJECT-TYPE 2475 SYNTAX Unsigned32 (0..65535) 2476 MAX-ACCESS read-only 2477 STATUS current 2478 DESCRIPTION 2479 "This is the greatest ANSN in any TC message 2480 received which originated from the router 2481 with originator address TA_from_orig_addr 2482 (i.e., which contributed to the information 2483 contained in this Tuple)." 2484 REFERENCE 2485 "RFC XXXX - The Optimized Link State Routing Protocol 2486 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2487 and U. Herberg, March 2013." 2488 ::= { olsrv2TibRoutableAddressTopologySetEntry 6 } 2490 olsrv2TibRoutableAddressTopologySetMetric OBJECT-TYPE 2491 SYNTAX Olsrv2MetricCompressedFormTC 2492 MAX-ACCESS read-only 2493 STATUS current 2494 DESCRIPTION 2495 "This is the neighbor metric from the router 2496 with originator address TA_from_orig_addr to the 2497 router with OLSRv2 interface address TA_dest_addr." 2498 REFERENCE 2499 "RFC XXXX - The Optimized Link State Routing Protocol 2500 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2501 and U. Herberg, March 2013." 2502 ::= { olsrv2TibRoutableAddressTopologySetEntry 7 } 2504 olsrv2TibRoutableAddressTopologySetExpireTime OBJECT-TYPE 2505 SYNTAX TimeStamp 2506 UNITS "centiseconds" 2507 MAX-ACCESS read-only 2508 STATUS current 2509 DESCRIPTION 2510 "olsrv2TibRoutableAddressTopologySetExpireTime 2511 specifies the value of sysUptime when this entry 2512 SHOULD expire and be removed from the 2513 olsrv2TibRoutableAddressTopologySetTable." 2514 REFERENCE 2515 "RFC XXXX - The Optimized Link State Routing Protocol 2516 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2517 and U. Herberg, March 2013." 2518 ::= { olsrv2TibRoutableAddressTopologySetEntry 8 } 2520 -- 2521 -- Attached Network Set 2522 -- 2524 olsrv2TibAttNetworksSetTable OBJECT-TYPE 2525 SYNTAX SEQUENCE OF Olsrv2TibAttNetworksSetEntry 2526 MAX-ACCESS not-accessible 2527 STATUS current 2528 DESCRIPTION 2529 "A router's Attached Network Set records information 2530 about networks (which may be outside the MANET) 2531 attached to other routers and their routable addresses." 2532 REFERENCE 2533 "RFC XXXX - The Optimized Link State Routing Protocol 2534 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2535 and U. Herberg, March 2013." 2536 ::= { olsrv2StateGroup 10 } 2538 olsrv2TibAttNetworksSetEntry OBJECT-TYPE 2539 SYNTAX Olsrv2TibAttNetworksSetEntry 2540 MAX-ACCESS not-accessible 2541 STATUS current 2542 DESCRIPTION 2543 "It consists of Attached Network Tuples: 2545 (AN_orig_addr, AN_net_addr, AN_seq_number, 2546 AN_dist, AN_metric, AN_time). 2548 OLSRv2 (RFC XXXX) defines the rules for managing 2549 entries within this table, e.g., populating 2550 and purging entries. Specific instructions for the 2551 olsrv2TibRoutableAddressTopologySetEntry(s) are found 2552 in Section 10.4 and Section 17 of OLSRv2 (RFC XXXX)." 2553 REFERENCE 2554 "RFC XXXX - The Optimized Link State Routing Protocol 2555 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2556 and U. Herberg, March 2013." 2557 INDEX { olsrv2TibAttNetworksSetIndex } 2558 ::= { olsrv2TibAttNetworksSetTable 1 } 2559 Olsrv2TibAttNetworksSetEntry ::= 2560 SEQUENCE { 2561 olsrv2TibAttNetworksSetIndex 2562 Unsigned32, 2563 olsrv2TibAttNetworksSetOrigIpAddrType 2564 InetAddressType, 2565 olsrv2TibAttNetworksSetOrigIpAddr 2566 InetAddress, 2567 olsrv2TibAttNetworksSetNetIpAddrType 2568 InetAddressType, 2569 olsrv2TibAttNetworksSetNetIpAddr 2570 InetAddress, 2571 olsrv2TibAttNetworksSetNetIpAddrPrefixLen 2572 InetAddressPrefixLength, 2573 olsrv2TibAttNetworksSetSeqNo 2574 Unsigned32, 2575 olsrv2TibAttNetworksSetDist 2576 Unsigned32, 2577 olsrv2TibAttNetworksSetMetric 2578 Olsrv2MetricCompressedFormTC, 2579 olsrv2TibAttNetworksSetExpireTime 2580 TimeStamp 2581 } 2583 olsrv2TibAttNetworksSetIndex OBJECT-TYPE 2584 SYNTAX Unsigned32 (1..16777215) 2585 MAX-ACCESS not-accessible 2586 STATUS current 2587 DESCRIPTION 2588 "The index for this table. The entries in this 2589 table expire according to the value of the 2590 olsrv2TibAttNetworksSetExpireTime object. 2591 Further, the lifetime of each entry within this 2592 table is set by the validity time in the 2593 OLSRv2 TC message. As such, they are expected 2594 to timeout roughly in the order that they are 2595 added to this table. 2597 The maximum value of this index is set to allow 2598 for the possibility of an extremely large number 2599 Attached Networks Set tuples to be 2600 added to this OLSRv2 router. This should not be 2601 an issue for MANET router deployments and 2602 configurations in the foreseeable future. 2604 The index values assigned to new entries SHOULD 2605 be assigned in numerical order, beginning from 2606 1. New entries should be assigned the next 2607 available value, until the maximum value is 2608 assigned. Following this, the next assigned value 2609 SHOULD go back to 1 and begin incrementing again. 2610 If the table is full, then the next entry SHOULD 2611 be assigned an index value in sequence, replacing 2612 an existing entry (expiring this entry 2613 pre-maturely). 2615 OLSRv2 (RFC XXXX) defines the rules for managing 2616 entries within this table, e.g., populating 2617 and purging entries." 2618 REFERENCE 2619 "RFC XXXX - The Optimized Link State Routing Protocol 2620 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2621 and U. Herberg, March 2013." 2622 ::= { olsrv2TibAttNetworksSetEntry 1 } 2624 olsrv2TibAttNetworksSetOrigIpAddrType OBJECT-TYPE 2625 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2626 MAX-ACCESS read-only 2627 STATUS current 2628 DESCRIPTION 2629 "The type of the olsrv2TibAttNetworksSetOrigIpAddr, 2630 as defined in the InetAddress MIB module (RFC4001). 2632 Only the values 'ipv4(1)' and 2633 'ipv6(2)' are supported." 2634 REFERENCE 2635 "RFC XXXX - The Optimized Link State Routing Protocol 2636 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2637 and U. Herberg, March 2013." 2638 ::= { olsrv2TibAttNetworksSetEntry 2 } 2640 olsrv2TibAttNetworksSetOrigIpAddr OBJECT-TYPE 2641 SYNTAX InetAddress (SIZE(4|16)) 2642 MAX-ACCESS read-only 2643 STATUS current 2644 DESCRIPTION 2645 "This is the originator address, of type 2646 olsrv2TibAttNetworksSetOrigIpAddrType, of a 2647 router which can act as gateway to the 2648 network with address AN_net_addr." 2649 REFERENCE 2650 "RFC XXXX - The Optimized Link State Routing Protocol 2651 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2652 and U. Herberg, March 2013." 2653 ::= { olsrv2TibAttNetworksSetEntry 3 } 2654 olsrv2TibAttNetworksSetNetIpAddrType OBJECT-TYPE 2655 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2656 MAX-ACCESS read-only 2657 STATUS current 2658 DESCRIPTION 2659 "The type of the olsrv2TibAttNetworksSetNetIpAddr, 2660 as defined in the InetAddress MIB module (RFC 4001). 2662 Only the values 'ipv4(1)' and 2663 'ipv6(2)' are supported." 2664 REFERENCE 2665 "RFC XXXX - The Optimized Link State Routing Protocol 2666 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2667 and U. Herberg, March 2013." 2668 ::= { olsrv2TibAttNetworksSetEntry 4 } 2670 olsrv2TibAttNetworksSetNetIpAddr OBJECT-TYPE 2671 SYNTAX InetAddress (SIZE(4|16)) 2672 MAX-ACCESS read-only 2673 STATUS current 2674 DESCRIPTION 2675 "This is is the network address,of type 2676 olsrv2TibAttNetworksSetNetIpAddrType, of an 2677 attached network, which may be reached via 2678 the router with originator address AN_orig_addr." 2679 REFERENCE 2680 "RFC XXXX - The Optimized Link State Routing Protocol 2681 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2682 and U. Herberg, March 2013." 2683 ::= { olsrv2TibAttNetworksSetEntry 5 } 2685 olsrv2TibAttNetworksSetNetIpAddrPrefixLen OBJECT-TYPE 2686 SYNTAX InetAddressPrefixLength 2687 UNITS "bits" 2688 MAX-ACCESS read-only 2689 STATUS current 2690 DESCRIPTION 2691 "Indicates the number of leading one bits that form the 2692 mask to be logically ANDed with the destination address 2693 before being compared to the value in the 2694 olsrv2TibAttNetworksSetNetIpAddr field." 2695 REFERENCE 2696 "RFC XXXX - The Optimized Link State Routing Protocol 2697 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2698 and U. Herberg, March 2013." 2699 ::= { olsrv2TibAttNetworksSetEntry 6 } 2701 olsrv2TibAttNetworksSetSeqNo OBJECT-TYPE 2702 SYNTAX Unsigned32 (0..65535) 2703 MAX-ACCESS read-only 2704 STATUS current 2705 DESCRIPTION 2706 "The greatest ANSN in any TC 2707 message received which originated from the 2708 router with originator address AN_orig_addr 2709 (i.e., which contributed to the information 2710 contained in this Tuple)." 2711 REFERENCE 2712 "RFC XXXX - The Optimized Link State Routing Protocol 2713 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2714 and U. Herberg, March 2013." 2715 ::= { olsrv2TibAttNetworksSetEntry 7 } 2717 olsrv2TibAttNetworksSetDist OBJECT-TYPE 2718 SYNTAX Unsigned32 (0..255) 2719 UNITS "hops" 2720 MAX-ACCESS read-only 2721 STATUS current 2722 DESCRIPTION 2723 "The number of hops to the network 2724 with address AN_net_addr from the router with 2725 originator address AN_orig_addr." 2726 REFERENCE 2727 "RFC XXXX - The Optimized Link State Routing Protocol 2728 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2729 and U. Herberg, March 2013." 2730 ::= { olsrv2TibAttNetworksSetEntry 8 } 2732 olsrv2TibAttNetworksSetMetric OBJECT-TYPE 2733 SYNTAX Olsrv2MetricCompressedFormTC 2734 MAX-ACCESS read-only 2735 STATUS current 2736 DESCRIPTION 2737 "The metric of the link from the router with 2738 originator address AN_orig_addr to the attached 2739 network with address AN_net_addr." 2740 REFERENCE 2741 "RFC XXXX - The Optimized Link State Routing Protocol 2742 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2743 and U. Herberg, March 2013." 2744 ::= { olsrv2TibAttNetworksSetEntry 9 } 2746 olsrv2TibAttNetworksSetExpireTime OBJECT-TYPE 2747 SYNTAX TimeStamp 2748 UNITS "centiseconds" 2749 MAX-ACCESS read-only 2750 STATUS current 2751 DESCRIPTION 2752 "olsrv2TibAttNetworksSetExpireTime 2753 specifies the value of sysUptime when this 2754 entry SHOULD expire and be removed from the 2755 olsrv2TibAttNetworksSetTable." 2756 REFERENCE 2757 "RFC XXXX - The Optimized Link State Routing Protocol 2758 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2759 and U. Herberg, March 2013." 2760 ::= { olsrv2TibAttNetworksSetEntry 10 } 2762 -- 2763 -- Routing Set 2764 -- 2766 olsrv2TibRoutingSetTable OBJECT-TYPE 2767 SYNTAX SEQUENCE OF Olsrv2TibRoutingSetEntry 2768 MAX-ACCESS not-accessible 2769 STATUS current 2770 DESCRIPTION 2771 "A router's Routing Set records the first hop along a 2772 selected path to each destination for which any such 2773 path is known." 2774 REFERENCE 2775 "RFC XXXX - The Optimized Link State Routing Protocol 2776 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2777 and U. Herberg, March 2013." 2778 ::= { olsrv2StateGroup 11 } 2780 olsrv2TibRoutingSetEntry OBJECT-TYPE 2781 SYNTAX Olsrv2TibRoutingSetEntry 2782 MAX-ACCESS not-accessible 2783 STATUS current 2784 DESCRIPTION 2785 "It consists of Routing Tuples: 2787 (R_dest_addr, R_next_iface_addr, 2788 R_local_iface_addr, R_dist, R_metric)" 2789 REFERENCE 2790 "RFC XXXX - The Optimized Link State Routing Protocol 2791 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2792 and U. Herberg, March 2013." 2793 INDEX { olsrv2TibRoutingSetDestIpAddrType, 2794 olsrv2TibRoutingSetDestIpAddr, 2795 olsrv2TibRoutingSetDestIpAddrPrefixLen } 2797 ::= { olsrv2TibRoutingSetTable 1 } 2799 Olsrv2TibRoutingSetEntry ::= 2800 SEQUENCE { 2801 olsrv2TibRoutingSetDestIpAddrType 2802 InetAddressType, 2803 olsrv2TibRoutingSetDestIpAddr 2804 InetAddress, 2805 olsrv2TibRoutingSetDestIpAddrPrefixLen 2806 InetAddressPrefixLength, 2807 olsrv2TibRoutingSetNextIfIpAddrType 2808 InetAddressType, 2809 olsrv2TibRoutingSetNextIfIpAddr 2810 InetAddress, 2811 olsrv2TibRoutingSetLocalIfIpAddrType 2812 InetAddressType, 2813 olsrv2TibRoutingSetLocalIfIpAddr 2814 InetAddress, 2815 olsrv2TibRoutingSetDist 2816 Unsigned32, 2817 olsrv2TibRoutingSetMetric 2818 Olsrv2MetricCompressedFormTC 2819 } 2821 olsrv2TibRoutingSetDestIpAddrType OBJECT-TYPE 2822 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2823 MAX-ACCESS not-accessible 2824 STATUS current 2825 DESCRIPTION 2826 "The type of the olsrv2TibRoutingSetDestIpAddr, 2827 as defined in the InetAddress MIB module (RFC 4001). 2829 Only the values 'ipv4(1)' and 'ipv6(2)' are 2830 supported." 2831 REFERENCE 2832 "RFC XXXX - The Optimized Link State Routing Protocol 2833 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2834 and U. Herberg, March 2013." 2835 ::= { olsrv2TibRoutingSetEntry 1 } 2837 olsrv2TibRoutingSetDestIpAddr OBJECT-TYPE 2838 SYNTAX InetAddress (SIZE(4|16)) 2839 MAX-ACCESS not-accessible 2840 STATUS current 2841 DESCRIPTION 2842 "This is the address of the destination, 2843 either the address of an interface of 2844 a destination router, or the network 2845 address of an attached network." 2846 REFERENCE 2847 "RFC XXXX - The Optimized Link State Routing Protocol 2848 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2849 and U. Herberg, March 2013." 2850 ::= { olsrv2TibRoutingSetEntry 2 } 2852 olsrv2TibRoutingSetDestIpAddrPrefixLen OBJECT-TYPE 2853 SYNTAX InetAddressPrefixLength 2854 UNITS "bits" 2855 MAX-ACCESS not-accessible 2856 STATUS current 2857 DESCRIPTION 2858 "Indicates the number of leading one bits that form the 2859 mask to be logically ANDed with the destination address 2860 before being compared to the value in the 2861 olsrv2TibRoutingSetDestIpAddr field. 2863 Note: This definition needs to be consistent 2864 with the current forwarding table MIB module description. 2865 Specifically, it SHOULD allow for longest prefix 2866 matching of network addresses." 2867 REFERENCE 2868 "RFC XXXX - The Optimized Link State Routing Protocol 2869 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2870 and U. Herberg, March 2013." 2871 ::= { olsrv2TibRoutingSetEntry 3 } 2873 olsrv2TibRoutingSetNextIfIpAddrType OBJECT-TYPE 2874 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2875 MAX-ACCESS read-only 2876 STATUS current 2877 DESCRIPTION 2878 "The type of the olsrv2TibRoutingSetNextIfIpAddr, 2879 as defined in the InetAddress MIB module (RFC 4001). 2881 Only the values 'ipv4(1)' and 2882 'ipv6(2)' are supported." 2883 REFERENCE 2884 "RFC XXXX - The Optimized Link State Routing Protocol 2885 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2886 and U. Herberg, March 2013." 2887 ::= { olsrv2TibRoutingSetEntry 4 } 2889 olsrv2TibRoutingSetNextIfIpAddr OBJECT-TYPE 2890 SYNTAX InetAddress (SIZE(4|16)) 2891 MAX-ACCESS read-only 2892 STATUS current 2893 DESCRIPTION 2894 "This object is the OLSRv2 interface address of the 2895 next hop on the selected path to the 2896 destination." 2897 REFERENCE 2898 "RFC XXXX - The Optimized Link State Routing Protocol 2899 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2900 and U. Herberg, March 2013." 2901 ::= { olsrv2TibRoutingSetEntry 5 } 2903 olsrv2TibRoutingSetLocalIfIpAddrType OBJECT-TYPE 2904 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2905 MAX-ACCESS read-only 2906 STATUS current 2907 DESCRIPTION 2908 "The type of the olsrv2TibRoutingSetLocalIfIpAddr 2909 and olsrv2TibRoutingSetNextIfIpAddr, 2910 as defined in the InetAddress MIB module (RFC 4001). 2912 Only the values 'ipv4(1)' and 2913 'ipv6(2)' are supported." 2914 REFERENCE 2915 "RFC XXXX - The Optimized Link State Routing Protocol 2916 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2917 and U. Herberg, March 2013." 2918 ::= { olsrv2TibRoutingSetEntry 6 } 2920 olsrv2TibRoutingSetLocalIfIpAddr OBJECT-TYPE 2921 SYNTAX InetAddress (SIZE(4|16)) 2922 MAX-ACCESS read-only 2923 STATUS current 2924 DESCRIPTION 2925 "This object is the address of the local OLSRv2 2926 interface over which a packet must be 2927 sent to reach the destination by the 2928 selected path." 2929 REFERENCE 2930 "RFC XXXX - The Optimized Link State Routing Protocol 2931 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2932 and U. Herberg, March 2013." 2933 ::= { olsrv2TibRoutingSetEntry 7 } 2935 olsrv2TibRoutingSetDist OBJECT-TYPE 2936 SYNTAX Unsigned32 (0..255) 2937 UNITS "hops" 2938 MAX-ACCESS read-only 2939 STATUS current 2940 DESCRIPTION 2941 "This object is the number of hops on the selected 2942 path to the destination." 2943 REFERENCE 2944 "RFC XXXX - The Optimized Link State Routing Protocol 2945 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2946 and U. Herberg, March 2013." 2947 ::= { olsrv2TibRoutingSetEntry 8 } 2949 olsrv2TibRoutingSetMetric OBJECT-TYPE 2950 SYNTAX Olsrv2MetricCompressedFormTC 2951 MAX-ACCESS read-only 2952 STATUS current 2953 DESCRIPTION 2954 "This object is the metric of the route 2955 to the destination with address R_dest_addr." 2956 REFERENCE 2957 "RFC XXXX - The Optimized Link State Routing Protocol 2958 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2959 and U. Herberg, March 2013." 2960 ::= { olsrv2TibRoutingSetEntry 9 } 2962 -- 2963 -- OLSRv2 Performance Group 2964 -- 2966 -- 2967 -- Contains objects which help to characterize the 2968 -- performance of the OLSRv2 routing process. 2969 -- 2971 olsrv2PerformanceObjGrp OBJECT IDENTIFIER ::= {olsrv2MIBObjects 3} 2973 -- 2974 -- Objects per local interface 2975 -- 2977 olsrv2InterfacePerfTable OBJECT-TYPE 2978 SYNTAX SEQUENCE OF Olsrv2InterfacePerfEntry 2979 MAX-ACCESS not-accessible 2980 STATUS current 2981 DESCRIPTION 2982 "This table summarizes performance objects that are 2983 measured per each active local OLSRv2 interface. 2984 If the olsrv2InterfaceAdminStatus of the interface 2985 changes to 'disabled' then the row associated with this 2986 interface SHOULD be removed from this table." 2987 REFERENCE 2988 "RFC XXXX - The Optimized Link State Routing Protocol 2989 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2990 and U. Herberg, March 2013." 2991 ::= { olsrv2PerformanceObjGrp 1 } 2993 olsrv2InterfacePerfEntry OBJECT-TYPE 2994 SYNTAX Olsrv2InterfacePerfEntry 2995 MAX-ACCESS not-accessible 2996 STATUS current 2997 DESCRIPTION 2998 "A single entry contains performance counters for 2999 each active local OLSRv2 interface." 3000 AUGMENTS { nhdpInterfacePerfEntry } 3001 ::= { olsrv2InterfacePerfTable 1 } 3003 Olsrv2InterfacePerfEntry ::= 3004 SEQUENCE { 3005 olsrv2IfTcMessageXmits 3006 Counter32, 3007 olsrv2IfTcMessageRecvd 3008 Counter32, 3009 olsrv2IfTcMessageXmitAccumulatedSize 3010 Counter64, 3011 olsrv2IfTcMessageRecvdAccumulatedSize 3012 Counter64, 3013 olsrv2IfTcMessageTriggeredXmits 3014 Counter32, 3015 olsrv2IfTcMessagePeriodicXmits 3016 Counter32, 3017 olsrv2IfTcMessageForwardedXmits 3018 Counter32, 3019 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount 3020 Counter32 3021 } 3023 olsrv2IfTcMessageXmits OBJECT-TYPE 3024 SYNTAX Counter32 3025 UNITS "messages" 3026 MAX-ACCESS read-only 3027 STATUS current 3028 DESCRIPTION 3029 "A counter is incremented each time a TC 3030 message has been transmitted on that interface." 3031 ::= { olsrv2InterfacePerfEntry 1 } 3032 olsrv2IfTcMessageRecvd OBJECT-TYPE 3033 SYNTAX Counter32 3034 UNITS "messages" 3035 MAX-ACCESS read-only 3036 STATUS current 3037 DESCRIPTION 3038 "A counter is incremented each time a 3039 TC message has been received on that interface. 3040 This excludes all messages that are ignored due to 3041 OLSRv2 protocol procedures." 3042 ::= { olsrv2InterfacePerfEntry 2 } 3044 olsrv2IfTcMessageXmitAccumulatedSize OBJECT-TYPE 3045 SYNTAX Counter64 3046 UNITS "octets" 3047 MAX-ACCESS read-only 3048 STATUS current 3049 DESCRIPTION 3050 "A counter is incremented by the number of octets in 3051 a TC message each time a TC message has been sent." 3052 ::= { olsrv2InterfacePerfEntry 3 } 3054 olsrv2IfTcMessageRecvdAccumulatedSize OBJECT-TYPE 3055 SYNTAX Counter64 3056 UNITS "octets" 3057 MAX-ACCESS read-only 3058 STATUS current 3059 DESCRIPTION 3060 "A counter is incremented by the number of octets in 3061 a TC message each time a TC message has been received. 3062 This excludes all messages that are ignored due to 3063 OLSRv2 protocol procedures." 3064 ::= { olsrv2InterfacePerfEntry 4 } 3066 olsrv2IfTcMessageTriggeredXmits OBJECT-TYPE 3067 SYNTAX Counter32 3068 UNITS "messages" 3069 MAX-ACCESS read-only 3070 STATUS current 3071 DESCRIPTION 3072 "A counter is incremented each time a triggered 3073 TC message has been sent." 3074 ::= { olsrv2InterfacePerfEntry 5 } 3076 olsrv2IfTcMessagePeriodicXmits OBJECT-TYPE 3077 SYNTAX Counter32 3078 UNITS "messages" 3079 MAX-ACCESS read-only 3080 STATUS current 3081 DESCRIPTION 3082 "A counter is incremented each time a periodic 3083 TC message has been sent." 3084 ::= { olsrv2InterfacePerfEntry 6 } 3086 olsrv2IfTcMessageForwardedXmits OBJECT-TYPE 3087 SYNTAX Counter32 3088 UNITS "messages" 3089 MAX-ACCESS read-only 3090 STATUS current 3091 DESCRIPTION 3092 "A counter is incremented each time a 3093 TC message has been forwarded." 3094 ::= { olsrv2InterfacePerfEntry 7 } 3096 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount OBJECT-TYPE 3097 SYNTAX Counter32 3098 UNITS "advertised MPR selectors" 3099 MAX-ACCESS read-only 3100 STATUS current 3101 DESCRIPTION 3102 "A counter is incremented by the number of advertised 3103 MPR selectors in a TC each time a TC 3104 message has been sent." 3105 ::= { olsrv2InterfacePerfEntry 8 } 3107 -- 3108 -- Objects concerning the Routing set 3109 -- 3111 olsrv2RoutingSetRecalculationCount OBJECT-TYPE 3112 SYNTAX Counter32 3113 UNITS "recalculations" 3114 MAX-ACCESS read-only 3115 STATUS current 3116 DESCRIPTION 3117 "This counter increments each time the Routing Set has 3118 been recalculated." 3119 ::= { olsrv2PerformanceObjGrp 2 } 3121 -- 3122 -- Objects concerning the MPR set 3123 -- 3125 olsrv2MPRSetRecalculationCount OBJECT-TYPE 3126 SYNTAX Counter32 3127 UNITS "recalculations" 3128 MAX-ACCESS read-only 3129 STATUS current 3130 DESCRIPTION 3131 "This counter increments each time the MPRs 3132 of this router have been recalculated for 3133 any of its interfaces." 3134 ::= { olsrv2PerformanceObjGrp 3 } 3136 -- 3137 -- Notifications 3138 -- 3140 olsrv2NotificationsObjects OBJECT IDENTIFIER ::= 3141 { olsrv2MIBNotifications 0 } 3142 olsrv2NotificationsControl OBJECT IDENTIFIER ::= 3143 { olsrv2MIBNotifications 1 } 3144 olsrv2NotificationsStates OBJECT IDENTIFIER ::= 3145 { olsrv2MIBNotifications 2 } 3147 -- olsrv2NotificationsObjects 3149 olsrv2RouterStatusChange NOTIFICATION-TYPE 3150 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3151 -- the originator of 3152 -- the notification. 3153 olsrv2OrigIpAddr, -- The originator of 3154 -- the notification. 3155 olsrv2AdminStatus -- The new state. 3156 } 3157 STATUS current 3158 DESCRIPTION 3159 "olsrv2RouterStatusChange is a notification generated 3160 when the OLSRv2 router changes it status. 3161 The router status is maintained in the 3162 olsrv2AdminStatus object." 3163 ::= { olsrv2NotificationsObjects 1 } 3165 olsrv2OrigIpAddrChange NOTIFICATION-TYPE 3166 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3167 -- the originator of 3168 -- the notification. 3170 olsrv2OrigIpAddr, -- The originator of 3171 -- the notification. 3172 olsrv2PreviousOrigIpAddrType, -- The address 3173 -- type of previous 3174 -- address of 3175 -- the originator of 3176 -- the notification. 3177 olsrv2PreviousOrigIpAddr -- The previous 3178 -- address of the 3179 -- originator of 3180 -- the notification. 3181 } 3182 STATUS current 3183 DESCRIPTION 3184 "olsrv2OrigIpAddrChange is a notification generated when 3185 the OLSRv2 router changes it originator IP address. 3186 The notification includes the new and the previous 3187 originator IP address of the OLSRv2 router." 3188 ::= { olsrv2NotificationsObjects 2 } 3190 olsrv2RoutingSetRecalculationCountChange NOTIFICATION-TYPE 3191 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3192 -- the originator of 3193 -- the notification. 3194 olsrv2OrigIpAddr, -- The originator of 3195 -- the notification. 3196 olsrv2RoutingSetRecalculationCount -- Number 3197 -- of the 3198 -- routing set 3199 -- recalculations. 3200 } 3201 STATUS current 3202 DESCRIPTION 3203 "The olsrv2RoutingSetRecalculationCountChange 3204 notification is generated when a significant number of 3205 routing set recalculations have occurred in a short time. 3206 This notification SHOULD be generated no more than once 3207 per olsrv2RoutingSetRecalculationCountWindow. 3208 The network administrator SHOULD select 3209 appropriate values for 'significant number of 3210 routing set recalculations' and 'short time' through 3211 the settings of the 3212 olsrv2RoutingSetRecalculationCountThreshold 3213 and olsrv2RoutingSetRecalculationCountWindow objects." 3214 ::= { olsrv2NotificationsObjects 3 } 3216 olsrv2MPRSetRecalculationCountChange NOTIFICATION-TYPE 3217 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3218 -- the originator of 3219 -- the notification. 3220 olsrv2OrigIpAddr, -- The originator of 3221 -- the notification. 3222 olsrv2MPRSetRecalculationCount -- Number of 3223 -- MPR set 3224 -- recalculations. 3225 } 3226 STATUS current 3227 DESCRIPTION 3228 "The olsrv2MPRSetRecalculationCountChange 3229 notification is generated when a significant 3230 number of MPR set recalculations occur in 3231 a short period of time. This notification 3232 SHOULD be generated no more than once 3233 per olsrv2MPRSetRecalculationCountWindow. 3234 The network administrator SHOULD select 3235 appropriate values for 'significant number of 3236 MPR set recalculations' and 'short period of 3237 time' through the settings of the 3238 olsrv2MPRSetRecalculationCountThreshold and 3239 olsrv2MPRSetRecalculationCountWindow objects." 3240 ::= { olsrv2NotificationsObjects 4 } 3242 -- olsrv2NotificationsControl 3244 olsrv2RoutingSetRecalculationCountThreshold OBJECT-TYPE 3245 SYNTAX Integer32 (0..255) 3246 UNITS "recalculations" 3247 MAX-ACCESS read-write 3248 STATUS current 3249 DESCRIPTION 3250 "A threshold value for the 3251 olsrv2RoutingSetRecalculationCount object. 3252 If the number of occurrences exceeds this 3253 threshold within the previous 3254 olsrv2RoutingSetRecalculationCountWindow, 3255 then the olsrv2RoutingSetRecalculationCountChange 3256 notification is to be generated. 3258 It is RECOMMENDED that the value of this 3259 threshold be set to at least 20 and higher 3260 in dense topologies with frequent expected 3261 topology changes." 3262 ::= { olsrv2NotificationsControl 1 } 3264 olsrv2RoutingSetRecalculationCountWindow OBJECT-TYPE 3265 SYNTAX TimeTicks 3266 MAX-ACCESS read-write 3267 STATUS current 3268 DESCRIPTION 3269 "This object is used to determine whether to generate 3270 an olsrv2RoutingSetRecalculationCountChange notification. 3271 This object represents an interval from the present moment, 3272 extending into the past, expressed in hundredths of 3273 a second. If the change in the value of the 3274 olsrv2RoutingSetRecalculationCount object during 3275 this interval has exceeded the value of 3276 olsrv2RoutingSetRecalculationCountThreshold, then 3277 an olsrv2RoutingSetRecalculationCountChange notification 3278 is generated. 3280 It is RECOMMENDED that the value for this 3281 window be set to at least 5 times the 3282 nhdpHelloInterval." 3283 ::= { olsrv2NotificationsControl 2 } 3285 olsrv2MPRSetRecalculationCountThreshold OBJECT-TYPE 3286 SYNTAX Integer32 (0..255) 3287 UNITS "recalculations" 3288 MAX-ACCESS read-write 3289 STATUS current 3290 DESCRIPTION 3291 "A threshold value for the 3292 olsrv2MPRSetRecalculationCount object. 3293 If the number of occurrences exceeds this 3294 threshold within the previous 3295 olsrv2MPRSetRecalculationCountWindow, 3296 then the 3297 olsrv2MPRSetRecalculationCountChange 3298 notification is to be generated. 3300 It is RECOMMENDED that the value of this 3301 threshold be set to at least 20 and higher 3302 in dense topologies with frequent expected 3303 topology changes." 3304 ::= { olsrv2NotificationsControl 3 } 3306 olsrv2MPRSetRecalculationCountWindow OBJECT-TYPE 3307 SYNTAX TimeTicks 3308 MAX-ACCESS read-write 3309 STATUS current 3310 DESCRIPTION 3311 "This object is used to determine whether to generate 3312 an olsrv2MPRSetRecalculationCountChange notification. 3314 This object represents an interval from the present moment, 3315 extending into the past, expressed in hundredths of 3316 a second. If the change in the value of the 3317 olsrv2MPRSetRecalculationCount object during 3318 that interval has exceeded the value of 3319 olsrv2MPRSetRecalculationCountThreshold, then the 3320 an olsrv2MPRSetRecalculationCountChange notification 3321 is generated. 3323 It is RECOMMENDED that the value for this 3324 window be set to at least 5 times the 3325 nhdpHelloInterval." 3326 ::= { olsrv2NotificationsControl 4 } 3328 olsrv2PreviousOrigIpAddrType OBJECT-TYPE 3329 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 3330 MAX-ACCESS read-only 3331 STATUS current 3332 DESCRIPTION 3333 "The type of the olsrv2PreviousOrigIpAddr, 3334 as defined in the InetAddress MIB module (RFC 4001). 3336 Only the values 'ipv4(1)' and 3337 'ipv6(2)' are supported. 3339 This object MUST have the same persistence 3340 characteristics as olsrv2PreviousOrigIpAddr." 3341 REFERENCE 3342 "RFC XXXX - The Optimized Link State Routing Protocol 3343 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3344 and U. Herberg, March 2013." 3345 ::= { olsrv2NotificationsStates 1 } 3347 olsrv2PreviousOrigIpAddr OBJECT-TYPE 3348 SYNTAX InetAddress (SIZE(4|16)) 3349 MAX-ACCESS read-only 3350 STATUS current 3351 DESCRIPTION 3352 "The previous origination IP address 3353 of this OLSRv2 router. 3355 This object SHOULD be updated each time 3356 the olsrv2OrigIpAddr is modified. 3358 This object is persistent and when written 3359 the entity SHOULD save the change to 3360 non-volatile storage." 3362 REFERENCE 3363 "RFC XXXX - The Optimized Link State Routing Protocol 3364 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3365 and U. Herberg, March 2013." 3366 ::= { olsrv2NotificationsStates 2 } 3368 -- 3369 -- Compliance Statements 3370 -- 3372 olsrv2Compliances OBJECT IDENTIFIER ::= { olsrv2MIBConformance 1 } 3373 olsrv2MIBGroups OBJECT IDENTIFIER ::= { olsrv2MIBConformance 2 } 3375 olsrv2BasicCompliance MODULE-COMPLIANCE 3376 STATUS current 3377 DESCRIPTION 3378 "The basic implementation requirements for 3379 managed network entities that implement 3380 the OLSRv2 routing process." 3381 MODULE -- this module 3382 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup } 3383 ::= { olsrv2Compliances 1 } 3385 olsrv2FullCompliance MODULE-COMPLIANCE 3386 STATUS current 3387 DESCRIPTION 3388 "The full implementation requirements for 3389 managed network entities that implement 3390 the OLSRv2 routing process." 3391 MODULE -- this module 3392 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup, 3393 olsrv2StateObjectsGroup, 3394 olsrv2PerfObjectsGroup, 3395 olsrv2NotificationsObjectsGroup, 3396 olsrv2NotificationsGroup } 3397 ::= { olsrv2Compliances 2 } 3399 -- 3400 -- Units of Conformance 3401 -- 3403 olsrv2ConfigObjectsGroup OBJECT-GROUP 3404 OBJECTS { 3405 olsrv2AdminStatus, 3406 olsrv2InterfaceAdminStatus, 3407 olsrv2OrigIpAddrType, 3408 olsrv2OrigIpAddr, 3409 olsrv2OHoldTime, 3410 olsrv2TcInterval, 3411 olsrv2TcMinInterval, 3412 olsrv2THoldTime, 3413 olsrv2AHoldTime, 3414 olsrv2RxHoldTime, 3415 olsrv2PHoldTime, 3416 olsrv2FHoldTime, 3417 olsrv2TpMaxJitter, 3418 olsrv2TtMaxJitter, 3419 olsrv2FMaxJitter, 3420 olsrv2TcHopLimit, 3421 olsrv2WillFlooding, 3422 olsrv2WillRouting, 3423 olsrv2LinkMetricType 3424 } 3425 STATUS current 3426 DESCRIPTION 3427 "Objects to permit configuration of OLSRv2. 3428 All of these SHOULD be backed by non-volatile 3429 storage." 3430 ::= { olsrv2MIBGroups 1 } 3432 olsrv2StateObjectsGroup OBJECT-GROUP 3433 OBJECTS { 3434 olsrv2LibOrigSetIpAddrType, 3435 olsrv2LibOrigSetIpAddr, 3436 olsrv2LibOrigSetExpireTime, 3437 olsrv2LibLocAttNetSetIpAddrType, 3438 olsrv2LibLocAttNetSetIpAddr, 3439 olsrv2LibLocAttNetSetIpAddrPrefixLen, 3440 olsrv2LibLocAttNetSetDistance, 3441 olsrv2LibLocAttNetSetMetric, 3442 olsrv2IibLinkSetInMetric, 3443 olsrv2IibLinkSetOutMetric, 3444 olsrv2IibLinkSetMprSelector, 3445 olsrv2Iib2HopSetInMetric, 3446 olsrv2Iib2HopSetOutMetric, 3447 olsrv2NibNeighborSetNOrigIpAddrType, 3448 olsrv2NibNeighborSetNOrigIpAddr, 3449 olsrv2NibNeighborSetNInMetric, 3450 olsrv2NibNeighborSetNOutMetric, 3451 olsrv2NibNeighborSetNWillFlooding, 3452 olsrv2NibNeighborSetNWillRouting, 3453 olsrv2NibNeighborSetNFloodingMpr, 3454 olsrv2NibNeighborSetNRoutingMpr, 3455 olsrv2NibNeighborSetNMprSelector, 3456 olsrv2NibNeighborSetNAdvertised, 3457 olsrv2NibNeighborSetTableAnsn, 3458 olsrv2TibAdRemoteRouterSetIpAddrType, 3459 olsrv2TibAdRemoteRouterSetIpAddr, 3460 olsrv2TibAdRemoteRouterSetMaxSeqNo, 3461 olsrv2TibRouterTopologySetFromOrigIpAddrType, 3462 olsrv2TibRouterTopologySetFromOrigIpAddr, 3463 olsrv2TibRouterTopologySetToOrigIpAddrType, 3464 olsrv2TibRouterTopologySetToOrigIpAddr, 3465 olsrv2TibRouterTopologySetSeqNo, 3466 olsrv2TibRouterTopologySetMetric, 3467 olsrv2TibRoutableAddressTopologySetExpireTime, 3468 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType, 3469 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, 3470 olsrv2TibRoutableAddressTopologySetDestIpAddrType, 3471 olsrv2TibRoutableAddressTopologySetDestIpAddr, 3472 olsrv2TibRoutableAddressTopologySetSeqNo, 3473 olsrv2TibRoutableAddressTopologySetMetric, 3474 olsrv2TibAttNetworksSetOrigIpAddrType, 3475 olsrv2TibAttNetworksSetOrigIpAddr, 3476 olsrv2TibAttNetworksSetNetIpAddrType, 3477 olsrv2TibAttNetworksSetNetIpAddr, 3478 olsrv2TibAttNetworksSetNetIpAddrPrefixLen, 3479 olsrv2TibAttNetworksSetSeqNo, 3480 olsrv2TibAttNetworksSetDist, 3481 olsrv2TibAttNetworksSetMetric, 3482 olsrv2TibAttNetworksSetExpireTime, 3483 olsrv2TibRoutingSetNextIfIpAddrType, 3484 olsrv2TibRoutingSetNextIfIpAddr, 3485 olsrv2TibRoutingSetLocalIfIpAddrType, 3486 olsrv2TibRoutingSetLocalIfIpAddr, 3487 olsrv2TibRoutingSetDist, 3488 olsrv2TibRoutingSetMetric 3489 } 3490 STATUS current 3491 DESCRIPTION 3492 "Objects to permit monitoring of OLSRv2 state." 3493 ::= { olsrv2MIBGroups 2 } 3495 olsrv2PerfObjectsGroup OBJECT-GROUP 3496 OBJECTS { 3497 olsrv2IfTcMessageXmits, 3498 olsrv2IfTcMessageRecvd, 3499 olsrv2IfTcMessageXmitAccumulatedSize, 3500 olsrv2IfTcMessageRecvdAccumulatedSize, 3501 olsrv2IfTcMessageTriggeredXmits, 3502 olsrv2IfTcMessagePeriodicXmits, 3503 olsrv2IfTcMessageForwardedXmits, 3504 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount, 3505 olsrv2RoutingSetRecalculationCount, 3506 olsrv2MPRSetRecalculationCount 3507 } 3508 STATUS current 3509 DESCRIPTION 3510 "Objects to support monitoring of OLSRv2 performance." 3511 ::= { olsrv2MIBGroups 3 } 3513 olsrv2NotificationsObjectsGroup OBJECT-GROUP 3514 OBJECTS { 3515 olsrv2RoutingSetRecalculationCountThreshold, 3516 olsrv2RoutingSetRecalculationCountWindow, 3517 olsrv2MPRSetRecalculationCountThreshold, 3518 olsrv2MPRSetRecalculationCountWindow, 3519 olsrv2PreviousOrigIpAddrType, 3520 olsrv2PreviousOrigIpAddr 3521 } 3522 STATUS current 3523 DESCRIPTION 3524 "Objects to support the notification types in the 3525 olsrv2NotificationsGroup. Some of these appear in 3526 notification payloads, others serve to control 3527 notification generation." 3528 ::= { olsrv2MIBGroups 4 } 3530 olsrv2NotificationsGroup NOTIFICATION-GROUP 3531 NOTIFICATIONS { 3532 olsrv2RouterStatusChange, 3533 olsrv2OrigIpAddrChange, 3534 olsrv2RoutingSetRecalculationCountChange, 3535 olsrv2MPRSetRecalculationCountChange 3536 } 3537 STATUS current 3538 DESCRIPTION 3539 "Notification types to support management of OLSRv2." 3540 ::= { olsrv2MIBGroups 5 } 3542 END 3544 8. Security Considerations 3546 This MIB module defines objects for the configuration, monitoring and 3547 notification of the Optimized Link State Routing protocol version 2 3548 [OLSRv2]. OLSRv2 allows routers to acquire topological information 3549 of the routing domain by virtue of exchanging TC message, to 3550 calculate shortest paths to each destination router in the routing 3551 domain, to select relays for network-wide transmissions etc. 3553 There are a number of management objects defined in this MIB module 3554 with a MAX-ACCESS clause of read-write and/or read-create. Such 3555 objects may be considered sensitive or vulnerable in some network 3556 environments. The support for SET operations in a non-secure 3557 environment without proper protection can have a negative effect on 3558 network operations. These are the tables and objects and their 3559 sensitivity/vulnerability: 3561 o olsrv2TcInterval, olsrv2TcMinInterval - these writable objects 3562 control the rate at which TC messages are sent. If set at too 3563 high a rate, this could represent a form of DOS attack by 3564 overloading interface resources. If set low, OLSRv2 may not 3565 converge fast enough to provide accurate routes to all 3566 destinations in the routing domain. 3568 o olsrv2TcHopLimit - defines the hop limit for TC messages. If set 3569 too low, messages will not be forwarded beyond the defined scope, 3570 and thus routers further away from the message originator will not 3571 be able to construct appropriate topology graphs. 3573 o olsrv2OHoldTime, olsrv2THoldTime, olsrv2AHoldTime, 3574 olsrv2RxHoldTime, olsrv2PHoldTime, olsrv2FHoldTime - define hold 3575 times for tuples of different Information Bases of OLSRv2. If set 3576 too low, information will expire quickly, and may this harm a 3577 correct operation of the routing protocol. 3579 o olsrv2WillFlooding and olsrv2WillRouting - define the willingness 3580 of this router to become MPR. If this is set to WILL_NEVER (0), 3581 the managed router will not forward any TC messages, nor accept a 3582 selection to become MPR by neighboring routers. If set to 3583 WILL_ALWAYS (15), the router will be preferred by neighbors during 3584 MPR selection, and may thus attract more traffic. 3586 o olsrv2TpMaxJitter, olsrv2TtMaxJitter, olsrv2FMaxJitter - define 3587 jitter values for TC message transmission and forwarding. If set 3588 too low, control traffic may get lost if the channel is lossy. 3590 o olsrv2LinkMetricType - defines the type of the link metric that a 3591 router uses (e.g., ETX or hop-count). Whenever this value 3592 changes, all link metric information recorded by the router is 3593 invalid, causing a reset of information acquired from other 3594 routers in the MANET. Moreover, if olsrv2LinkMetricType on a 3595 router is set to a value that is not known to other routers in the 3596 MANET, these routers will not be able to establish routes to that 3597 router or transiting that router. Existing routes to the router 3598 with a olsrv2LinkMetricType unknown to other routers in the MANET 3599 will be removed. 3601 Some of the readable objects in this MIB module (i.e., objects with a 3602 MAX-ACCESS other than not-accessible) may be considered sensitive or 3603 vulnerable in some network environments. It is thus important to 3604 control even GET and/or NOTIFY access to these objects and possibly 3605 to even encrypt the values of these objects when sending them over 3606 the network via SNMP. These are the tables and objects and their 3607 sensitivity/vulnerability: 3609 o olsrv2TibRouterTopologySetTable - The contains information on the 3610 topology of the MANET, specifically the IP address of the routers 3611 in the MANET (as identified by 3612 olsrv2TibRouterTopologySetFromOrigIpAddr and 3613 olsrv2TibRouterTopologySetToOrigIpAddr objects). This information 3614 provides an adversary broad information on the members of the 3615 MANET, located within this single table. This information can be 3616 used to expedite attacks on the other members of the MANET without 3617 having to go through a laborious discovery process on their own. 3619 Some of the Tables in this MIB AUGMENT Tables defined in NHDP-MIB 3620 [RFC6779]. Hence, care must be taken in configuring access control 3621 here in order make sure that the permitted permissions granted for 3622 the AUGMENT-ing Tables here are consistent with the access controls 3623 permitted within the NHDP-MIB. The below list identifies the 3624 AUGMENT-ing Tables and their NHDP-MIB counterparts. It is recommend 3625 that access control policies for these Table pairs are consistently 3626 set. 3628 o The olsrv2InterfaceTable AUGMENTs the nhdpInterfaceTable. 3630 o The olsrv2IibLinkSetTable AUGMENTs the nhdpIibLinkSetTable. 3632 o The olsrv2Iib2HopSetTable AUGMENTs the nhdpIib2HopSetTable. 3634 o The olsrv2NibNeighborSetTable AUGMENTs the 3635 nhdpNibNeighborSetTable. 3637 o The olsrv2InterfacePerfTable AUGMENTs the nhdpInterfacePerfTable. 3639 MANET technology is often deployed to support communications of 3640 emergency services or military tactical applications. In these 3641 applications, it is imperative to maintain the proper operation of 3642 the communications network and to protect sensitive information 3643 related to its operation. Therefore, when implementing these 3644 capabilities, the full use of SNMPv3 cryptographic mechanisms for 3645 authentication and privacy is RECOMMENDED. 3647 SNMP versions prior to SNMPv3 did not include adequate security. 3648 Even if the network itself is secure (for example by using IPsec), 3649 there is no control as to who on the secure network is allowed to 3650 access and GET/SET (read/change/create/delete) the objects in this 3651 MIB module. 3653 Implementations SHOULD provide the security features described by the 3654 SNMPv3 framework (see [RFC3410]), and implementations claiming 3655 compliance to the SNMPv3 standard MUST include full support for 3656 authentication and privacy via the User-based Security Model (USM) 3657 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 3658 MAY also provide support for the Transport Security Model (TSM) 3659 [RFC5591] in combination with a secure transport such as SSH 3660 [RFC5592] or TLS/DTLS [RFC6353]. 3662 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3663 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3664 enable cryptographic security. It is then a customer/operator 3665 responsibility to ensure that the SNMP entity giving access to an 3666 instance of this MIB module is properly configured to give access to 3667 the objects only to those principals (users) that have legitimate 3668 rights to indeed GET or SET (change/create/delete) them. 3670 9. Applicability Statement 3672 This document describes objects for configuring parameters of the 3673 Optimized Link State Routing version 2 (OLSRv2) Protocol [OLSRv2] 3674 process on a router. This MIB module, denoted OLSRv2-MIB, also 3675 reports state, performance information and notifications. The OLSRv2 3676 protocol relies upon information gathered via the Neighborhood 3677 Discovery Protocol [RFC6130] in order to perform its operations. The 3678 NHDP protocol is managed via the NHDP-MIB [RFC6779]. 3680 MANET deployments can greatly differ in aspects of dynamics of the 3681 topology, capacity and loss rates of underlying channels, traffic 3682 flow directions, memory and CPU capacity of routers etc. SNMP and 3683 therefore this MIB module are only applicable for a subset of MANET 3684 deployments, in particular deployments: 3686 o In which routers have enough memory and CPU resources to run SNMP 3687 and expose the MIB module. 3689 o Where a network management station (NMS) is defined to which 3690 notifications are generated, and from which routers can be 3691 managed. 3693 o Where this NMS is reachable from routers in the MANET most of the 3694 time (as notifications to the NMS and management information from 3695 the NMS to the router will be lost when connectivity is 3696 temporarily lost). This requires that the topology of the MANET 3697 is only moderately dynamic. 3699 o Where the underlying wireless channel supports enough bandwidth to 3700 run SNMP, and where loss rates of the channel are not exhaustive. 3702 Certain MANET deployments, such as community networks with non-mobile 3703 routers, dynamic topology because of changing link quality, and a 3704 pre-defined gateway (that could also serve as NMS), are examples of 3705 networks applicable for this MIB module. Other, more constrained 3706 deployments of MANETs may not be able to run SNMP and require 3707 different management protocols. 3709 Some level of configuration, i.e., read-write objects, is desirable 3710 for OLSRv2 deployments. Topology related configuration such as the 3711 ability to enable OLSRv2 on new interfaces or initially configure 3712 OLSRv2 on a router's interfaces through the 3713 olsrv2InterfaceAdminStatus object is critical to initial system 3714 startup. The OLSRv2 protocol allows for some level of performance 3715 tuning through various protocol parameters and this MIB module allows 3716 for configuration of those protocol parameters through read-write 3717 objects such as the olsrv2TcHopLimit or the olsrv2FMaxJitter. Other 3718 read-write objects allow for the control of Notification behavior 3719 through this MIB module, e.g., the 3720 olsrv2RoutingSetRecalculationCountThreshold object. A fuller 3721 discussion of MANET network management applicability is to be 3722 provided elsewhere [USE-CASES]. 3724 10. IANA Considerations 3726 The MIB module in this document uses the following IANA-assigned 3727 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 3729 Descriptor OBJECT IDENTIFIER value 3730 ---------- ----------------------- 3731 OLSRv2-MIB { mib-2 ZZZZ } 3732 IANA EDITOR NOTE: please assign ZZZZ 3734 11. Acknowledgements 3736 The authors would like to thank Randy Presuhn, Benoit Claise, Adrian 3737 Farrel, as well as the entire MANET WG for reviews of this document. 3739 This MIB document uses the template authored by D. Harrington which 3740 is based on contributions from the MIB Doctors, especially Juergen 3741 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 3743 12. References 3745 12.1. Normative References 3747 [OLSRv2] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg, 3748 "The Optimized Link State Routing Protocol version 2", 3749 draft-ietf-manet-olsrv2-19 (work in progress), 3750 March 2013. 3752 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3753 Requirement Levels", BCP 14, RFC 2119, March 1997. 3755 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3756 Schoenwaelder, Ed., "Structure of Management 3757 Information Version 2 (SMIv2)", STD 58, RFC 2578, 3758 April 1999. 3760 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3761 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3762 STD 58, RFC 2579, April 1999. 3764 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3765 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3766 April 1999. 3768 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3769 MIB", RFC 2863, June 2000. 3771 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 3772 Model (USM) for version 3 of the Simple Network 3773 Management Protocol (SNMPv3)", December 2002. 3775 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3776 Simple Network Management Protocol (SNMP)", STD 62, 3777 RFC 3418, December 2002. 3779 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 3780 Advanced Encryption Standard (AES) Cipher Algorithm in 3781 the SNMP User-based Security Model", June 2004. 3783 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 3784 Schoenwaelder, "Textual Conventions for Internet 3785 Network Addresses", RFC 4001, February 2005. 3787 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security 3788 Model for the Simple Network Management Protocol 3789 (SNMP)", June 2009. 3791 [RFC5592] Harrington, D., Saloway, J., and W. Hardaker, "Secure 3792 Shell Transport Model for the Simple Network 3793 Management Protocol (SNMP)", June 2009. 3795 [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc 3796 Network (MANET) Neighborhood Discovery Protocol 3797 (NHDP)", RFC 6130, April 2011. 3799 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 3800 Model for the Simple Network Management Protocol 3801 (SNMP)", July 2011. 3803 [RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of 3804 Managed Objects for the Neighborhood Discovery 3805 Protocol", RFC 6779, May 2012. 3807 12.2. Informative References 3809 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3810 "Introduction and Applicability Statements for 3811 Internet-Standard Management Framework", RFC 3410, 3812 December 2002. 3814 [REPORT-MIB] Cole, R., Macker, J., and A. Bierman, "Definition of 3815 Managed Objects for Performance Reporting", 3816 draft-ietf-manet-report-mib-03 (work in progress), 3817 November 2012. 3819 [USE-CASES] Nguyen, J., Cole, R., Herberg, U., Yi, J., and J. Dean, 3820 "Network Management of Mobile Ad hoc Networks (MANET): 3821 Architecture, Use Cases, and Applicability", 3822 draft-nguyen-manet-management-00 (work in progress), 3823 February 2013. 3825 Appendix A. Note to the RFC Editor 3827 *************************************************************** 3828 * Note to the RFC Editor (to be removed prior to publication) * 3829 * * 3830 * 1) The reference to RFCYYYY within the DESCRIPTION clauses * 3831 * of the MIB module point to this draft and are to be * 3832 * assigned by the RFC Editor. * 3833 * * 3834 * 2) The reference to RFCXXXX throughout this document point * 3835 * to the current draft-ietf-manet-olsrv2-xx.txt. This * 3836 * needs to be replaced with the XXXX RFC number for the * 3837 * OLSRv2 publication. * 3838 * * 3839 *************************************************************** 3841 Authors' Addresses 3843 Ulrich Herberg 3844 Fujitsu Laboratories of America 3845 1240 East Arques Avenue 3846 Sunnyvale, CA 94085 3847 USA 3849 EMail: ulrich@herberg.name 3850 URI: http://www.herberg.name/ 3852 Robert G. Cole 3853 US Army CERDEC 3854 6010 Frankford Road, Bldg 6010 3855 Aberdeen Proving Ground, Maryland 21005 3856 USA 3858 Phone: +1 443 395 8744 3859 EMail: robert.g.cole@us.army.mil 3860 URI: http://www.cs.jhu.edu/~rgcole/ 3861 Thomas Heide Clausen 3862 LIX, Ecole Polytechnique 3863 Palaiseau Cedex, 91128 3864 France 3866 Phone: +33 6 6058 9349 3867 EMail: T.Clausen@computer.org 3868 URI: http://www.ThomasClausen.org/