idnits 2.17.1 draft-ietf-manet-olsrv2-mib-12.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 (June 24, 2013) is 3959 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: December 26, 2013 US Army CERDEC 6 T. Clausen 7 LIX, Ecole Polytechnique 8 June 24, 2013 10 Definition of Managed Objects for the Optimized Link State Routing 11 Protocol version 2 12 draft-ietf-manet-olsrv2-mib-12 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 December 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 . . . . . . . . . . . . . . 9 71 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 72 6.2. Relationship to the NHDP-MIB . . . . . . . . . . . . . . . 9 73 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 74 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . 78 76 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 80 77 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 81 78 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 82 79 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 82 80 12.1. Normative References . . . . . . . . . . . . . . . . . . . 82 81 12.2. Informative References . . . . . . . . . . . . . . . . . . 83 82 Appendix A. Appendix A: . . . . . . . . . . . . . . . . . . . . . 84 83 Appendix B. Note to the RFC Editor . . . . . . . . . . . . . . . 86 85 1. Introduction 87 This document defines the Management Information Base (MIB) module 88 for configuring and managing the Optimized Link State Routing 89 protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured 90 into configuration information, state information, performance 91 information, and notifications. In addition to configuration, this 92 additional state and performance information is useful to 93 troubleshoot problems and performance issues of the routing protocol. 94 Different levels of compliance allow implementers to use smaller 95 subsets of all defined objects, allowing for this MIB module to be 96 deployed on more constrained routers. 98 2. The Internet-Standard Management Framework 100 For a detailed overview of the documents that describe the current 101 Internet-Standard Management Framework, please refer to Section 7 of 102 [RFC3410]. 104 Managed objects are accessed via a virtual information store, termed 105 the Management Information Base or MIB. MIB objects are generally 106 accessed through the Simple Network Management Protocol (SNMP). 107 Objects in the MIB module are defined using the mechanisms defined in 108 the Structure of Management Information (SMI). This document 109 specifies a MIB module that is compliant to the SMIv2, which is 110 described in [RFC2578], [RFC2579], and [RFC2580]. 112 3. Conventions 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 116 "OPTIONAL" in this document are to be interpreted as described in 117 [RFC2119]. 119 4. Overview 121 The Optimized Link State Routing Protocol version 2 (OLSRv2) [OLSRv2] 122 is a table driven, proactive routing protocol, i.e., it exchanges 123 topology information with other routers in the network periodically. 124 OLSRv2 is an optimization of the classical link state routing 125 protocol. Its key concept is that of MultiPoint Relays (MPRs). Each 126 router selects a set of its neighbor routers (which "cover" all of 127 its symmetrically connected 2-hop neighbor routers) as MPRs. MPRs 128 are then used to achieve both flooding reduction and topology 129 reduction. 131 This document provides management and control capabilities of an 132 OLSRv2 instance, allowing management applications to monitor the 133 state and performance of an OLSRv2 router, as well as to change 134 settings of the OLSRv2 instance (e.g., router or interface parameters 135 such as message intervals, etc.). 137 As OLSRv2 relies on the neighborhood information discovered by the 138 "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol 139 (NHDP)" [RFC6130], the OLSRv2-MIB module is aligned with the NHDP-MIB 140 [RFC6779] module and augments several of the tables and objects in 141 the NHDP-MIB. In particular, common indexes for router interfaces 142 and discovered neighbors are used, as described in Section 5.2. 144 4.1. Terms 146 The following definitions apply throughout this document: 148 o Configuration Objects - switches, tables, objects which are 149 initialized to default settings or set through the management 150 interface defined by this MIB module. 152 o State Objects - automatically generated values which define the 153 current operating state of the OLSRv2 protocol instance in the 154 router. 156 o Performance Objects - automatically generated values which help an 157 administrator or automated tool to assess the performance of the 158 OLSRv2 routing process on the router. 160 o Notification Objects - define triggers and associated notification 161 messages allowing for asynchronous tracking of pre-defined events 162 on the managed router. 164 5. Structure of the MIB Module 166 This section presents the structure of the OLSRv2-MIB module. The 167 objects are arranged into the following structure: 169 o olsrv2MIBObjects - defines objects forming the basis for the 170 OLSRv2-MIB module. These objects are divided up by function into 171 the following groups: 173 * Configuration Group - defining objects related to the 174 configuration of the OLSRv2 instance on the router. 176 * State Group - defining objects which reflect the current state 177 of the OLSRv2 instance running on the router. 179 * Performance Group -defining objects which are useful to a 180 management station when characterizing the performance of 181 OLSRv2 on the router and in the MANET. 183 o olsrv2MIBNotifications - objects defining OLSRv2-MIB module 184 notifications. 186 o olsrv2MIBConformance - defining the minimal and maximal 187 conformance requirements for implementations of this MIB module. 189 5.1. The Configuration Group 191 The OLSRv2 router is configured with a set of controls. The 192 authoritative list of configuration controls within the OLSRv2-MIB 193 module is found within the MIB module itself. Generally, an attempt 194 was made in developing the OLSRv2-MIB module to support all 195 configuration objects defined in [OLSRv2]. For all of the 196 configuration parameters, the same constraints and default values of 197 these parameters as defined in [OLSRv2] are followed. 199 5.2. The State Group 201 The State Group reports current state information of a router running 202 [OLSRv2]. The OLSRv2-MIB module State Group tables were designed to 203 contain the complete set of state information defined within the 204 information bases in [OLSRv2]. 206 The OLSRv2-MIB module State Group tables are constructed as 207 extensions to the corresponding tables within the State Group of the 208 NHDP-MIB [RFC6779] module. Use of the AUGMENTS clause is made, when 209 possible, to accomplish these table extensions. Further, the State 210 Group tables defined in this MIB module are aligned with the 211 according tables in the NHDP-MIB [RFC6779] module, as described in 212 Section 6.2. 214 5.3. The Performance Group 216 The Performance Group reports values relevant to system performance. 217 Frequent changes of sets or frequent recalculation of the routing set 218 or the MPRs can have a negative influence on the performance of 219 OLSRv2. This MIB module defines several objects that can be polled 220 in order to, e.g., calculate histories or monitor frequencies of 221 changes. This may help the network administrator to determine 222 unusual topology changes or other changes that affect stability and 223 reliability of the MANET. One such framework is specified in REPORT- 224 MIB [REPORT-MIB]. 226 5.4. The Notifications Group 228 The Notifications Group contains Control 229 (olsrv2NotificationsControl), Objects (olsrv2NotificationsObjects) 230 and States (olsrv2NotificationsStates), where the Control contains 231 definitions of objects to control the frequency of notifications 232 being generated. The Objects define the supported notifications and 233 the State is used to define additional information to be carried 234 within the notifications. 236 The olsrv2NotificationsObjects sub-tree contains the list of 237 notifications supported within the OLSRv2-MIB module and their 238 intended purpose or utility. 240 The same mechanisms for improving the network performance by reducing 241 the number of notifications apply as defined in Section 5.1 of 242 [RFC6779]. The following objects are used to define the thresholds 243 and time windows for specific notifications defined in the NHDP-MIB 244 module: olsrv2RoutingSetRecalculationCountThreshold, 245 olsrv2RoutingSetRecalculationCountWindow, 246 olsrv2MPRSetRecalculationCountThreshold, and 247 olsrv2MPRSetRecalculationCountWindow. 249 5.5. Tables and Indexing 251 The OLSRv2-MIB module's tables are indexed by the following 252 constructs: 254 o nhdpIfIndex - the ifIndex of the local router on which NHDP is 255 configured. This is defined in the NHDP-MIB. 257 o nhdpDiscIfIndex - a locally managed index representing a known 258 interface on a neighboring router. This is defined in the NHDP- 259 MIB. 261 o nhdpDiscRouterIndex - a locally managed index representing an ID 262 of a known neighboring router. This is defined in the NHDP-MIB. 264 o {olsrv2LibOrigSetIpAddrType, olsrv2LibOrigSetIpAddr} - this index 265 (pair) uniquely identifies recently used originator addresses 266 found within the olsrv2LibOrigSetTable. 268 o {olsrv2LibLocAttNetSetIpAddrType, olsrv2LibLocAttNetSetIpAddr, 269 olsrv2LibLocAttNetSetIpAddrPerfixLen} - this index (triplet) 270 uniquely identifies local attached networks reachable through 271 local (non-OLSRv2) interfaces on this router. These are recorded 272 in the olsrv2LibLocAttNetSetTable. 274 o {olsrv2TibAdRemoteRouterSetIpAddrType, 275 olsrv2TibAdRemoteRouterSetIpAddr} - this index (pair) uniquely 276 identifies each router in the network that transmits TC messages 277 received by this router. These records are recorded in the 278 olsrv2TibAdRemoteRouterSetIpAddr. 280 o {olsrv2TibRouterTopologySetFromOrigIpAddrType, 281 olsrv2TibRouterTopologySetFromOrigIpAddr, 282 olsrv2TibRouterTopologySetToOrigIpAddrType, 283 olsrv2TibRouterTopologySetToOrigIpAddr} - this index (quadruplet) 284 uniquely identifies discovered links within the network recorded 285 by this router. Information associated with each link is stored 286 in the olsrv2TibRouterTopologySetTable. 288 o {olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType, 289 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, 290 olsrv2TibRoutableAddressTopologySetFromDestIpAddrType, 291 olsrv2TibRoutableAddressTopologySetFromDestIpAddr} - this index 292 (quadruplet) uniquely identifies reachable addresses within the 293 network and the router's advertising these addresses. This 294 information is stored in the 295 olsrv2TibRoutableAddressTopologySetTable. 297 o {olsrv2TibAttNetworksSetOrigIpAddrType, 298 olsrv2TibAttNetworksSetOrigIpAddr, 299 olsrv2TibAttNetworksSetNetIpAddrType, 300 olsrv2TibAttNetworksSetNetIpAddr, 301 olsrv2TibAttNetworksSetNetIpAddrPrefixLen} - this index 302 (quintuplet) uniquely identifies the networks (which may be 303 outside the MANET) and the routers through which these networks 304 can be reached. This information is stored in the 305 olsrv2TibAttNetworksSetTable. 307 o {olsrv2TibRoutingSetDestIpAddrType, olsrv2TibRoutingSetDestIpAddr, 308 olsrv2TibRoutingSetDestIpAddrPrefixLen} - this index (triplet) 309 uniquely identifies the address of a reachable destination in the 310 network. This indexes the olsrv2TibRoutingSetTable which contains 311 the next hop information to reach the indexed addresses. 313 These tables and their indexing are: 315 o olsrv2InterfaceTable - describes the OLSRv2 status on the NHDP 316 interfaces of this router. This table augments nhdpInterfaceEntry 317 and as such it is indexed by the {nhdpIfIndex} from the NHDP-MIB. 319 o olsrv2IibLinkSetTable - records all links from other routers which 320 are, or recently were, 1-hop neighbors. This table augments 321 nhdpIibLinkSetEntry and as such it is indexed by nhdpIfIndex and 322 nhdpDiscIfIndex. 324 o olsrv2Iib2HopSetTable - records network addresses of symmetric 325 2-hop neighbors and the links to the associated 1-hop neighbors. 326 This table augments nhdpIib2HopSetEntry and as such it is indexed 327 by {nhdpIfIndex, nhdpDiscIfIndex, nhdpIib2HopSetIpAddressType, 328 nhdpIib2HopSetIpAddress}. 330 o olsrv2LibOrigSetTable - records addresses that were recently used 331 as originator addresses by this router. This table is indexed by 332 {olsrv2LibOrigSetIpAddrType, olsrv2LibOrigSetIpAddr}. 334 o olsrv2LibLocAttNetSetTable - records its local non-OLSRv2 335 interfaces via which it can act as gateways to other networks. 336 This table is indexed by {olsrv2LibLocAttNetSetIpAddrType, 337 olsrv2LibLocAttNetSetIpAddr, 338 olsrv2LibLocAttNetSetIpAddrPerfixLen}. 340 o olsrv2NibNeighborSetTable - records all network addresses of each 341 1-hop neighbor. This table augments nhdpNibNeighborSetEntry and 342 as such it is indexed by the {nhdpDiscRouterIndex}. 344 o olsrv2TibAdRemoteRouterSetTable - records information describing 345 each remote router in the network that transmits TC messages. 346 This table is indexed by {olsrv2TibAdRemoteRouterSetIpAddrType, 347 olsrv2TibAdRemoteRouterSetIpAddr}. 349 o olsrv2TibRouterTopologySetTable - records topology information 350 about the network. This table is indexed by 351 {olsrv2TibRouterTopologySetFromOrigIpAddrType, 352 olsrv2TibRouterTopologySetFromOrigIpAddr, 353 olsrv2TibRouterTopologySetToOrigIpAddrType, 354 olsrv2TibRouterTopologySetToOrigIpAddr}. 356 o olsrv2TibRoutableAddressTopologySetTable - records topology 357 information about the routable addresses within the MANET, and via 358 which routers they may be reached. This table is indexed by 359 {olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType, 360 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, 361 olsrv2TibRoutableAddressTopologySetFromDestIpAddrType, 362 olsrv2TibRoutableAddressTopologySetFromDestIpAddr}. 364 o olsrv2TibAttNetworksSetTable - records information about networks 365 (which may be outside the MANET) attached to other routers and 366 their routable addresses. This table is indexed by 367 {olsrv2TibAttNetworksSetOrigIpAddrType, 368 olsrv2TibAttNetworksSetOrigIpAddr, 369 olsrv2TibAttNetworksSetNetIpAddrType, 370 olsrv2TibAttNetworksSetNetIpAddr, 371 olsrv2TibAttNetworksSetNetIpAddrPrefixLen}. 373 o olsrv2TibRoutingSetTable - records the first hop along a selected 374 path to each destination for which any such path is known. This 375 table is indexed by {olsrv2TibRoutingSetDestIpAddrType, 376 olsrv2TibRoutingSetDestIpAddr, 377 olsrv2TibRoutingSetDestIpAddrPrefixLen}. 379 o olsrv2InterfacePerfTable - records performance counters for each 380 active OLSRv2 interface on this device. This table augments 381 nhdpInterfacePerfEntry and as such it is indexed by {nhdpIfIndex} 382 from the NHDP-MIB. 384 6. Relationship to Other MIB Modules 386 This section specifies the relationship of the MIB modules contained 387 in this document to other standards, particularly to standards 388 containing other MIB modules. MIB modules and specific definitions 389 imported from MIB modules that SHOULD be implemented in conjunction 390 with the MIB module contained within this document are identified in 391 this section. 393 6.1. Relationship to the SNMPv2-MIB 395 The System group in the SNMPv2-MIB [RFC3418] module is defined as 396 being mandatory for all systems, and the objects apply to the entity 397 as a whole. The System group provides identification of the 398 management entity and certain other system-wide data. The OLSRv2-MIB 399 module does not duplicate those objects. 401 6.2. Relationship to the NHDP-MIB 403 OLSRv2 depends on the neighborhood information that is discovered by 404 [RFC6130]. An instance of OLSRv2 MUST have an associated instance of 405 NHDP running on the same device for proper operations of the 406 discovery and routing system. In order for the OLSRv2-MIB module to 407 correctly populate the objects relating to discovered neighbors, the 408 State Group tables of the NHDP-MIB [RFC6779] module are aligned with 409 the State Group tables of this MIB module. This is accomplished 410 through the use of the AUGMENTS capability of SMIv2 (where 411 appropriate). This will allow for cross referencing of information 412 between the two MIB modules within a given SNMP context. 414 6.3. MIB modules required for IMPORTS 416 The following OLSRv2-MIB module IMPORTS objects from NHDP-MIB 417 [RFC6779], SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF 419 [RFC2580], IF-MIB [RFC2863] and INET-ADDRESS-MIB [RFC4001]. The 420 OLSRv2-MIB module also IMPORTS objects from the 421 IANAolsrv2LinkMetricType-MIB which is defined in Appendix A of this 422 document. 424 7. Definitions 426 This section contains the OLSRv2-MIB module defined by the 427 specification. 429 OLSRv2-MIB DEFINITIONS ::= BEGIN 431 IMPORTS 433 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64, 434 Integer32, Unsigned32, mib-2, TimeTicks, 435 NOTIFICATION-TYPE 436 FROM SNMPv2-SMI -- RFC 2578 438 TEXTUAL-CONVENTION, TimeStamp, TruthValue 439 FROM SNMPv2-TC -- RFC 2579 441 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 442 FROM SNMPv2-CONF -- STD 58 444 InetAddressType, InetAddress, 445 InetAddressPrefixLength 446 FROM INET-ADDRESS-MIB -- RFC 3291 448 nhdpInterfaceEntry, 449 nhdpIibLinkSetEntry, nhdpIib2HopSetEntry, 450 nhdpNibNeighborSetEntry, nhdpInterfacePerfEntry 451 FROM NHDP-MIB -- RFC 6779 453 IANAolsrv2LinkMetricTypeTC 454 FROM IANAolsrv2LinkMetricType-MIB 455 ; 457 manetOlsrv2MIB MODULE-IDENTITY 458 LAST-UPDATED "201306240000Z" --24 June 2013 459 ORGANIZATION "IETF MANET Working Group" 460 CONTACT-INFO 461 "WG E-Mail: manet@ietf.org 463 WG Chairs: sratliff@cisco.com 464 jmacker@nrl.navy.mil 466 Editors: Ulrich Herberg 467 Fujitsu Laboratories of America 468 1240 East Arques Avenue 469 Sunnyvale, CA 94085 470 USA 471 ulrich@herberg.name 472 http://www.herberg.name/ 474 Thomas Heide Clausen 475 Ecole Polytechnique 476 LIX 477 91128 Palaiseau Cedex 478 France 479 http://www.thomasclausen.org/ 480 T.Clausen@computer.org 482 Robert G. Cole 483 US Army CERDEC 484 Space and Terrestrial Communications 485 6010 Frankford Street 486 Bldg 6010, Room 453H 487 Aberdeen Proving Ground, MD 21005 488 USA 489 +1 443 395-8744 490 robert.g.cole@us.army.mil 491 http://www.cs.jhu.edu/~rgcole/" 493 DESCRIPTION 494 "This OLSRv2-MIB module is applicable to routers 495 implementing the Optimized Link State Routing Protocol 496 version 2 (OLSRv2) defined in RFC XXXX. 498 Copyright (c) 2013 IETF Trust and the persons 499 identified as authors of the code. All rights reserved. 501 Redistribution and use in source and binary forms, with 502 or without modification, is permitted pursuant to, and 503 subject to the license terms contained in, the Simplified 504 BSD License set forth in Section 4.c of the IETF Trust's 505 Legal Provisions Relating to IETF Documents 506 (http://trustee.ietf.org/license-info). 508 This version of this MIB module is part of RFC YYYY; see 509 the RFC itself for full legal notices." 511 -- Revision History 512 REVISION "201306240000Z" -- 24 June 2013 513 DESCRIPTION 514 "Initial version of this MIB module, 515 published as RFC YYYY." 517 -- RFC-Editor assigns ZZZZ (this comment can be removed) 518 ::= { mib-2 ZZZZ } 520 -- 521 -- TEXTUAL CONVENTIONS 522 -- 524 Olsrv2MetricValueCompressedFormTC ::= TEXTUAL-CONVENTION 525 DISPLAY-HINT "d" 526 STATUS current 527 DESCRIPTION 528 "OLSRv2 Metrics are expressed in terms of a Link Metric 529 Compressed Form within the OLSRv2 protocol. This textual 530 convention defines the syntax of the metric objects 531 consistent with the definitions of the OLSRv2 Link 532 Metric Compressed Form in Section 6.2 of RFC XXXX. 534 The 12-bit compressed form of a link metric uses a modified 535 form of a representation with an 8-bit mantissa (denoted a) 536 and a 4-bit exponent (denoted b). Note that if represented 537 as the 12 bit value 256b+a then the ordering of those 12 bit 538 values is identical to the ordering of the represented values. 540 The value so represented is (257+a)2^b - 256, where ^ denotes 541 exponentiation. This has a minimum value 542 (when a = 0 and b = 0) of MINIMUM_METRIC = 1 and a maximum 543 value (when a = 255 and b = 15) of MAXIMUM_METRIC = 2^24 - 256. 545 Hence the compressed form metric values range from 1 to 546 16776960. The special value of 0 is reserved for the 547 UNKNOWN_METRIC value. 549 If a network manager sets the metric value 'm' through the 550 MIB-module, then the OLSRv2 code can derive 'compressed_m' 551 = M(a,b) according to the algorithm in RFC 5497 and 552 'compressed_m' is the value represented in the OLSRv2 messages. 553 But the value 'm' is persistently stored by the MIB-module. 554 If the MIB-module is pulling this time parameter from some other 555 source, i.e., the protocol instance, then this value is stored 556 as is." 557 SYNTAX Unsigned32 (0..16776960) 559 Olsrv2TimeValueCompressedForm32TC ::= TEXTUAL-CONVENTION 560 DISPLAY-HINT "x" 561 STATUS current 562 DESCRIPTION 563 "OLSRv2 time values may be expressed in terms of a compressed 564 form within the OLSRv2 protocol. This textual convention 565 defines the syntax of the time objects defined in terms of 566 an interger number of millisceonds, consistent with the 567 definitions of the 8-bit exponent-mantissa compressed form 568 defined in Section 5 of RFC 5497. Time values with this 569 representation are defined in terms of a constant C which 570 is represented in terms of seconds. The constant C 571 (time granularity) is used as specified in RFC 5497. 572 It MUST be the same as is used by the NHDP protocol 573 RFC 6130. 575 The 8-bit compressed form of a time value uses a modified 576 form of a representation with an 3-bit mantissa (denoted a) 577 and a 5-bit exponent (denoted b). Note that if represented 578 as the 8 bit value 8b+a then the ordering of those 8 bit 579 values is identical to the ordering of the represented values. 581 The minimum time-value that can be represented in this manner 582 is C. The maximum time-value that can be represented in 583 this manner is 15 * 2^28 * C, 15*268,435,456 * C, 584 4,026,531,840 * C or about 45 days if, for example, 585 C = 1/1024 second. 587 This TEXTUAL-CONVENTION limits the maximum value of the 588 time granularity constant C to be no greater than 1/1024 589 seconds due to its use of the Unsigned32 syntax limiting 590 the maximum number of milliseconds to no more than 591 3932160000. 593 When OLSRv2 uses this 8-bit exponent-mantissa compressed 594 form, this object value MUST be translated from the 595 integer form represented in this MIB-module into the 596 exponent-mantissa form for the OLSRv2 protocol to use 597 according to the algorithm defined in Section 5 of 598 RFC 5497 for finding the next larger time value within 599 the exponent-mantissa format. 601 If a network manager sets the time value 't' through the 602 MIB-module, then the OLSRv2 code can derive 603 'compressed_t' = T(a,b) according to the algorithm 604 in RFC 5497 and 'compressed_t' is the value represented 605 in the OLSRv2 messages. But the value 't' is persistently 606 stored by the MIB-module. If the MIB-module is pulling 607 this time parameter from some other source which is using 608 the compressed form, i.e., the protocol instance, then 609 this value is stored as is, after converting from 610 number of time constants C into number of milliseconds." 611 SYNTAX Unsigned32 (1..3932160000) 613 Olsrv2StatusTC ::= TEXTUAL-CONVENTION 614 STATUS current 615 DESCRIPTION 616 "Controls the operation of the OLSRv2 617 protocol on the device or a specific interface. 618 For example, for an interface: 'enabled' indicates 619 that OLSRv2 is permitted to operate, 620 and 'disabled' indicates that it is not." 621 SYNTAX INTEGER { 622 enabled (1), 623 disabled (2) 624 } 626 WillingnessTC ::= TEXTUAL-CONVENTION 627 DISPLAY-HINT "x" 628 STATUS current 629 DESCRIPTION 630 "A willingness value which evaluates to the 631 device's interest in participating in 632 a particular function, process or behavior. 634 The williness ranges from a low value of 635 WILL_NEVER(0) to a high value of 636 WILL_ALWAYS(15). For each parameter x, 637 there is an associated willingness value 638 W(x) such that WILL_NEVER < W(x) <= WILL_ALWAYS." 639 SYNTAX Unsigned32 (0..15) 641 -- 642 -- Top-Level Object Identifier Assignments 643 -- 645 olsrv2MIBNotifications OBJECT IDENTIFIER ::= { manetOlsrv2MIB 0 } 646 olsrv2MIBObjects OBJECT IDENTIFIER ::= { manetOlsrv2MIB 1 } 647 olsrv2MIBConformance OBJECT IDENTIFIER ::= { manetOlsrv2MIB 2 } 649 -- 650 -- olsrv2ConfigurationGroup 651 -- 653 -- Contains the OLSRv2 objects that configure specific 654 -- options that determine the overall performance and operation 655 -- of the OLSRv2 routing process. 657 olsrv2ConfigurationGroup OBJECT IDENTIFIER ::= {olsrv2MIBObjects 1} 659 olsrv2AdminStatus OBJECT-TYPE 660 SYNTAX Olsrv2StatusTC 661 MAX-ACCESS read-write 662 STATUS current 663 DESCRIPTION 664 "The configured status of the OLSRv2 process 665 on this device. 'enabled(1)' means that 666 OLSRv2 is configured to run on this device. 667 'disabled(2)' mean that the OLSRv2 process 668 is configured off. 670 Operation of the OLSRv2 routing protocol 671 requires the operation of the Neighborhood 672 Discovery Protocol (RFC 6130). Hence, this 673 object cannot have a status of 'enabled' 674 unless at least one interface on the device 675 is a MANET interface with NHDP enabled on that 676 interface. If a network manager attempts to 677 set this object to 'enabled' when no interfaces 678 on this device have HNDP enabled, the device 679 MUST fail the set with inconsistentValue. 680 If all device interfaces running NHDP become 681 disabled or removed, then the 682 olsrv2AdminStatus MUST be 'disabled'. 684 If the network manager, or other means, sets 685 this object to 'disabled', then the associated 686 interface specific objects, i.e., the 687 olsrv2InterfaceAdminStatus objects MUST all 688 be 'disabled'. 690 This object is persistent and when written 691 the entity SHOULD save the change to 692 non-volatile storage." 693 DEFVAL { 2 } 694 ::= { olsrv2ConfigurationGroup 1 } 696 olsrv2InterfaceTable OBJECT-TYPE 697 SYNTAX SEQUENCE OF Olsrv2InterfaceEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "The olsrv2InterfaceTable describes the OLSRv2 702 status on the NHDP interfaces of this router. 703 As such, this table augments the nhdpInterfaceTable 704 defined in the NHDP-MIB (RFC 6779). NHDP interfaces 705 are explicitly defined by network management, CLI, 706 or other means for interfaces on the device that are 707 intended to run MANET protocols. The 708 olsrv2InterfaceTable contains a single object, the 709 olsrv2InterfaceAdminStatus object. This 710 object is set by network management, or by 711 other means, e.g., CLI. 713 A conceptual row in this table exists if and only 714 if a corresponding entry in the nhdpInterfaceTable 715 exists. If the corresponding entry with nhdpIfIndex 716 value is deleted from the nhdpInterfaceTable, then 717 the entry in this table is automatically deleted and 718 OLSRv2 is disabled on this interface, 719 and all configuration and state information 720 related to this interface is to be removed 721 from memory. 723 The olsrv2InterfaceAdminStatus can only be 724 'enabled' if the corresponding olsrv2AdminStatus 725 object is also set to 'enabled'." 726 REFERENCE 727 "RFC XXXX - The Optimized Link State Routing Protocol 728 version 2, Clausen, T., Dearlove, C., Jacquet, P. 729 and U. Herberg, March 2013." 730 ::= { olsrv2ConfigurationGroup 2 } 732 olsrv2InterfaceEntry OBJECT-TYPE 733 SYNTAX Olsrv2InterfaceEntry 734 MAX-ACCESS not-accessible 735 STATUS current 736 DESCRIPTION 737 "The olsrv2InterfaceEntry describes one OLSRv2 738 local interface configuration as indexed by 739 its nhdpIfIndex as defined in the 740 NHDP-MIB (RFC 6779). 742 The objects in this table are persistent and when 743 written the device SHOULD save the change to 744 non-volatile storage. For further information 745 on the storage behavior for these objects, refer 746 to the description for the nhdpIfRowStatus 747 object in the NHDP-MIB (RFC6779)." 748 REFERENCE 749 "RFC 6779 - The Neighborhood Discovery Protocol MIB, 750 Herberg, U., Cole, R.G. and I. Chakeres, 751 October 2012" 753 AUGMENTS { nhdpInterfaceEntry } 754 ::= { olsrv2InterfaceTable 1 } 756 Olsrv2InterfaceEntry ::= 757 SEQUENCE { 758 olsrv2InterfaceAdminStatus 759 Olsrv2StatusTC 760 } 762 olsrv2InterfaceAdminStatus OBJECT-TYPE 763 SYNTAX Olsrv2StatusTC 764 MAX-ACCESS read-create 765 STATUS current 766 DESCRIPTION 767 "The OLSRv2 interface's administrative status. 768 The value 'enabled(1)' denotes that the interface 769 is permitted to participate in the OLSRv2 routing 770 process. The value 'disabled(2)' denotes that 771 the interface is not permitted to participate 772 in the OLSRv2 routing process. 774 The configuration objects for the OLSRv2 routing 775 process, other than the administrative status objects, 776 are common to all interfaces on this device. 777 As such, the OLSRv2 configuration objects are globally 778 defined for the device and are not contained within 779 the olsrv2InterfaceTable." 780 DEFVAL { 2 } 781 ::= { olsrv2InterfaceEntry 1 } 783 olsrv2OrigIpAddrType OBJECT-TYPE 784 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 785 MAX-ACCESS read-write 786 STATUS current 787 DESCRIPTION 788 "The type of the olsrv2OrigIpAddr, as defined 789 in the InetAddress MIB module (RFC 4001). 791 Only the values 'ipv4(1)' and 792 'ipv6(2)' are supported." 793 REFERENCE 794 "RFC XXXX - The Optimized Link State Routing Protocol 795 version 2, Clausen, T., Dearlove, C., Jacquet, P. 796 and U. Herberg, March 2013." 797 ::= { olsrv2ConfigurationGroup 3 } 799 olsrv2OrigIpAddr OBJECT-TYPE 800 SYNTAX InetAddress (SIZE(4|16)) 801 MAX-ACCESS read-write 802 STATUS current 803 DESCRIPTION 804 "The router's originator address. An address that 805 is unique (within the MANET) to this router. 807 This object is persistent and when written 808 the entity SHOULD save the change to 809 non-volatile storage." 810 REFERENCE 811 "RFC XXXX - The Optimized Link State Routing Protocol 812 version 2, Clausen, T., Dearlove, C., Jacquet, P. 813 and U. Herberg, March 2013." 814 ::= { olsrv2ConfigurationGroup 4 } 816 -- 817 -- Local History Times 818 -- 820 olsrv2OHoldTime OBJECT-TYPE 821 SYNTAX Unsigned32 822 UNITS "milliseconds" 823 MAX-ACCESS read-write 824 STATUS current 825 DESCRIPTION 826 "olsrv2OHoldTime corresponds to 827 O_HOLD_TIME of OLSRv2 and represents the 828 time for which a recently used and replaced 829 originator address is used to recognize the router's 830 own messages. 832 Guidance for setting this object may be found 833 in Section 5 of the OLSRv2 specification (RFC XXXX), 834 which indicates that: 835 o olsrv2OHoldTime > 0 837 This object is persistent and when written 838 the entity SHOULD save the change to 839 non-volatile storage." 840 REFERENCE 841 "Section 5 on Protocol Parameters. 842 RFC XXXX - The Optimized Link State Routing Protocol 843 version 2, Clausen, T., Dearlove, C., Jacquet, P. 844 and U. Herberg, March 2013." 845 DEFVAL { 30000 } 846 ::= { olsrv2ConfigurationGroup 5 } 847 -- 848 -- Message intervals 849 -- 851 olsrv2TcInterval OBJECT-TYPE 852 SYNTAX Olsrv2TimeValueCompressedForm32TC 853 UNITS "milliseconds" 854 MAX-ACCESS read-write 855 STATUS current 856 DESCRIPTION 857 "olsrv2TcInterval corresponds to 858 TC_INTERVAL of OLSRv2 and represents the 859 maximum time between the transmission of 860 two successive TC messages by this router. 862 Guidance for setting this object may be found 863 in Section 5 of the OLSRv2 specification (RFC XXXX), 864 which indicates that: 866 o olsrv2TcInterval > 0 867 o olsrv2TcInterval >= olsrv2TcMinInterval 869 This object is persistent and when written 870 the entity SHOULD save the change to 871 non-volatile storage." 872 REFERENCE 873 "Section 5 on Representing Time. 874 RFC 5497 - Representing Multi-Value Time in 875 Mobile Ad Hoc Networks (MANETs), 876 Clausen, T. and C. Dearlove, March 2009. 878 and 880 Section 5 on Protocol Parameters. 881 RFC XXXX - The Optimized Link State Routing Protocol 882 version 2, Clausen, T., Dearlove, C., Jacquet, P. 883 and U. Herberg, March 2013." 884 DEFVAL { 5000 } 885 ::= { olsrv2ConfigurationGroup 6 } 887 olsrv2TcMinInterval OBJECT-TYPE 888 SYNTAX Olsrv2TimeValueCompressedForm32TC 889 UNITS "milliseconds" 890 MAX-ACCESS read-write 891 STATUS current 892 DESCRIPTION 893 "olsrv2TcMinInterval corresponds to 894 TC_MIN_INTERVAL of OLSRv2 and represents 895 the minimum interval between transmission of 896 two successive TC messages by this router. 898 Guidance for setting this object may be found 899 in Section 5 of the OLSRv2 specification (RFC XXXX), 900 which indicates that: 901 o olsrv2TcInterval >= olsrv2TcMinInterval 903 The OLSRv2 protocol may choose to represent this 904 time interval in terms of the 8-bit exponent-mantissa 905 form defined in Section 5 of RFC 5497. When this 906 is the case, this object value MUST be translated 907 from the integer form represented in this 908 MIB-module into the exponent-mantissa form for the 909 OLSRv2 protocol to use according to the algorithm 910 defined in Section 5 of RFC 5497 for finding the 911 next larger time value within the exponent-mantissa 912 format. 914 This object is persistent and when written 915 the entity SHOULD save the change to 916 non-volatile storage." 917 REFERENCE 918 "Section 5 on Representing Time. 919 RFC 5497 - Representing Multi-Value Time in 920 Mobile Ad Hoc Networks (MANETs), 921 Clausen, T. and C. Dearlove, March 2009. 923 and 925 Section 5 on Protocol Parameters. 926 RFC XXXX - The Optimized Link State Routing Protocol 927 version 2, Clausen, T., Dearlove, C., Jacquet, P. 928 and U. Herberg, March 2013." 929 DEFVAL { 1250 } 930 ::= { olsrv2ConfigurationGroup 7 } 932 -- 933 -- Advertised information validity times 934 -- 936 olsrv2THoldTime OBJECT-TYPE 937 SYNTAX Olsrv2TimeValueCompressedForm32TC 938 UNITS "milliseconds" 939 MAX-ACCESS read-write 940 STATUS current 941 DESCRIPTION 942 "olsrv2THoldTime corresponds to 943 T_HOLD_TIME of OLSRv2 and is used as the 944 minimum value in the TLV with 945 Type = VALIDITY_TIME included in all 946 TC messages sent by this router. 948 Guidance for setting this object may be found 949 in Section 5 of the OLSRv2 specification (RFC XXXX), 950 which indicates that: 951 o olsrv2THoldTime >= olsrv2TcInterval 952 o If TC messages can be lost, then 953 olsrv2THoldTime SHOULD be 954 significantly greater than olsrv2TcInterval; 955 a value >= 3 x olsrv2TcInterval is RECOMMENDED. 957 This object is persistent and when written 958 the entity SHOULD save the change to 959 non-volatile storage." 960 REFERENCE 961 "Section 5 on Representing Time. 962 RFC 5497 - Representing Multi-Value Time in 963 Mobile Ad Hoc Networks (MANETs), 964 Clausen, T. and C. Dearlove, March 2009. 966 and 968 Section 5 on Protocol Parameters. 969 RFC XXXX - The Optimized Link State Routing Protocol 970 version 2, Clausen, T., Dearlove, C., Jacquet, P. 971 and U. Herberg, March 2013." 972 DEFVAL { 15000 } 973 ::= { olsrv2ConfigurationGroup 8 } 975 olsrv2AHoldTime OBJECT-TYPE 976 SYNTAX Olsrv2TimeValueCompressedForm32TC 977 UNITS "milliseconds" 978 MAX-ACCESS read-write 979 STATUS current 980 DESCRIPTION 981 "olsrv2AHoldTime corresponds to 982 A_HOLD_TIME of OLSRv2 and represents 983 the period during which TC messages are sent 984 after they no longer have any advertised 985 information to report, but are sent in order 986 to accelerate outdated information removal by other 987 routers. 989 Guidance for setting this object may be found 990 in Section 5 of the OLSRv2 specification (RFC XXXX), 991 which indicates that: 992 o If TC messages can be lost, then 993 olsrv2AHoldTime SHOULD be 994 significantly greater than olsrv2TcInterval; 995 a value >= 3 x olsrv2TcInterval is 996 RECOMMENDED. 998 This object is persistent and when written 999 the entity SHOULD save the change to 1000 non-volatile storage." 1001 REFERENCE 1002 "Section 5 on Representing Time. 1003 RFC 5497 - Representing Multi-Value Time in 1004 Mobile Ad Hoc Networks (MANETs), 1005 Clausen, T. and C. Dearlove, March 2009. 1007 and 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 { 15000 } 1014 ::= { olsrv2ConfigurationGroup 9 } 1016 -- 1017 -- Received message validity times 1018 -- 1020 olsrv2RxHoldTime OBJECT-TYPE 1021 SYNTAX Unsigned32 1022 UNITS "milliseconds" 1023 MAX-ACCESS read-write 1024 STATUS current 1025 DESCRIPTION 1026 "olsrv2RxHoldTime corresponds to 1027 RX_HOLD_TIME of OLSRv2 and represents the period 1028 after receipt of a message by the appropriate OLSRv2 1029 interface of this router for which that information 1030 is recorded, in order that the message is recognized 1031 as having been previously received on this OLSRv2 1032 interface. 1034 Guidance for setting this object may be found 1035 in Section 5 of the OLSRv2 specification (RFC XXXX), 1036 which indicates that: 1037 o olsrv2RxHoldTime > 0 1038 o This parameter SHOULD be greater 1039 than the maximum difference in time that a 1040 message may take to traverse the MANET, 1041 taking into account any message forwarding 1042 jitter as well as propagation, queuing, 1043 and processing delays. 1045 This object is persistent and when written 1046 the entity SHOULD save the change to 1047 non-volatile storage." 1048 REFERENCE 1049 "Section 5 on Protocol Parameters. 1050 RFC XXXX - The Optimized Link State Routing Protocol 1051 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1052 and U. Herberg, March 2013." 1053 DEFVAL { 30000 } 1054 ::= { olsrv2ConfigurationGroup 10 } 1056 olsrv2PHoldTime OBJECT-TYPE 1057 SYNTAX Unsigned32 1058 UNITS "milliseconds" 1059 MAX-ACCESS read-write 1060 STATUS current 1061 DESCRIPTION 1062 "olsrv2PHoldTime corresponds to 1063 P_HOLD_TIME of OLSRv2 and represents the period 1064 after receipt of a message that is processed by 1065 this router for which that information is recorded, 1066 in order that the message is not processed again 1067 if received again. 1069 Guidance for setting this object may be found 1070 in Section 5 of the OLSRv2 specification (RFC XXXX), 1071 which indicates that: 1072 o olsrv2PHoldTime > 0 1073 o This parameter SHOULD be greater 1074 than the maximum difference in time that a 1075 message may take to traverse the MANET, 1076 taking into account any message forwarding 1077 jitter as well as propagation, queuing, 1078 and processing delays. 1080 This object is persistent and when written 1081 the entity SHOULD save the change to 1082 non-volatile storage." 1083 REFERENCE 1084 "Section 5 on Protocol Parameters. 1085 RFC XXXX - The Optimized Link State Routing Protocol 1086 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1087 and U. Herberg, March 2013." 1088 DEFVAL { 30000 } 1089 ::= { olsrv2ConfigurationGroup 11 } 1091 olsrv2FHoldTime OBJECT-TYPE 1092 SYNTAX Unsigned32 1093 UNITS "milliseconds" 1094 MAX-ACCESS read-write 1095 STATUS current 1096 DESCRIPTION 1097 "olsrv2FHoldTime corresponds to 1098 F_HOLD_TIME of OLSRv2 and represents the period 1099 after receipt of a message that is forwarded by this 1100 router for which that information is recorded, in order 1101 that the message is not forwarded again if received again. 1103 Guidance for setting this object may be found 1104 in Section 5 of the OLSRv2 specification (RFC XXXX), 1105 which indicates that: 1106 o olsrv2FHoldTime > 0 1107 o This parameter SHOULD be greater 1108 than the maximum difference in time that a 1109 message may take to traverse the MANET, 1110 taking into account any message forwarding 1111 jitter as well as propagation, queuing, 1112 and processing delays. 1114 This parameter SHOULD be greater 1115 than the maximum difference in time that a 1116 message may take to traverse the MANET, 1117 taking into account any message forwarding 1118 jitter as well as propagation, queuing, 1119 and processing delays. 1121 This object is persistent and when written 1122 the entity SHOULD save the change to 1123 non-volatile storage." 1124 REFERENCE 1125 "Section 5 on Protocol Parameters. 1126 RFC XXXX - The Optimized Link State Routing Protocol 1127 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1128 and U. Herberg, March 2013." 1129 DEFVAL { 30000 } 1130 ::= { olsrv2ConfigurationGroup 12 } 1132 -- 1133 -- Jitter times 1134 -- 1136 olsrv2TpMaxJitter OBJECT-TYPE 1137 SYNTAX Unsigned32 1138 UNITS "milliseconds" 1139 MAX-ACCESS read-write 1140 STATUS current 1141 DESCRIPTION 1142 "olsrv2TpMaxJitter corresponds to 1143 TP_MAXJITTER of OLSRv2 and represents the value 1144 of MAXJITTER used in RFC5148 for periodically 1145 generated TC messages sent by this router. 1147 For constraints on these parameters see RFC 5148. 1149 This object is persistent and when written 1150 the entity SHOULD save the change to 1151 non-volatile storage." 1152 REFERENCE 1153 "Section 5 on Protocol Parameters. 1154 RFC XXXX - The Optimized Link State Routing Protocol 1155 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1156 and U. Herberg, March 2013." 1157 DEFVAL { 500 } 1158 ::= { olsrv2ConfigurationGroup 13 } 1160 olsrv2TtMaxJitter OBJECT-TYPE 1161 SYNTAX Unsigned32 1162 UNITS "milliseconds" 1163 MAX-ACCESS read-write 1164 STATUS current 1165 DESCRIPTION 1166 "olsrv2TtMaxJitter corresponds to 1167 TT_MAXJITTER of OLSRv2 and represents the value 1168 of MAXJITTER used in RFC5148 for externally 1169 triggered TC messages sent by this router. 1171 For constraints on these parameters see RFC 5148. 1173 This object is persistent and when written 1174 the entity SHOULD save the change to 1175 non-volatile storage." 1176 REFERENCE 1177 "Section 5 on Protocol Parameters. 1178 RFC XXXX - The Optimized Link State Routing Protocol 1179 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1180 and U. Herberg, March 2013." 1182 DEFVAL { 500 } 1183 ::= { olsrv2ConfigurationGroup 14 } 1185 olsrv2FMaxJitter OBJECT-TYPE 1186 SYNTAX Unsigned32 1187 UNITS "milliseconds" 1188 MAX-ACCESS read-write 1189 STATUS current 1190 DESCRIPTION 1191 "olsrv2FMaxJitter corresponds to 1192 F_MAXJITTER of OLSRv2 and represents the 1193 default value of MAXJITTER used in RFC 5148 for 1194 messages forwarded by this router. 1196 For constraints on these parameters see RFC 5148. 1198 This object is persistent and when written 1199 the entity SHOULD save the change to 1200 non-volatile storage." 1201 REFERENCE 1202 "Section 5 on Protocol Parameters. 1203 RFC XXXX - The Optimized Link State Routing Protocol 1204 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1205 and U. Herberg, March 2013." 1206 DEFVAL { 500 } 1207 ::= { olsrv2ConfigurationGroup 15 } 1209 -- 1210 -- Hop limits 1211 -- 1213 olsrv2TcHopLimit OBJECT-TYPE 1214 SYNTAX Unsigned32 (0..255) 1215 UNITS "hops" 1216 MAX-ACCESS read-write 1217 STATUS current 1218 DESCRIPTION 1219 "olsrv2TcHopLimit corresponds to 1220 TC_HOP_LIMIT of OLSRv2. 1222 Guidance for setting this object may be found 1223 in Section 5 of the OLSRv2 specification (RFC XXXX), 1224 which indicates that: 1225 o The maximum value of 1226 olsrv2TcHopLimit >= the network diameter 1227 in hops, a value of 255 is RECOMMENDED. 1229 o All values of olsrv2TcHopLimit >= 2. 1231 This object is persistent and when written 1232 the entity SHOULD save the change to 1233 non-volatile storage." 1234 REFERENCE 1235 "Section 5 on Protocol Parameters. 1236 RFC XXXX - The Optimized Link State Routing Protocol 1237 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1238 and U. Herberg, March 2013." 1239 DEFVAL { 255 } 1240 ::= { olsrv2ConfigurationGroup 16 } 1242 -- 1243 -- Willingness 1244 -- 1246 olsrv2WillRouting OBJECT-TYPE 1247 SYNTAX WillingnessTC 1248 MAX-ACCESS read-write 1249 STATUS current 1250 DESCRIPTION 1251 "olsrv2WillRouting corresponds to 1252 WILL_ROUTING of OLSRv2. 1254 Guidance for setting this object may be found 1255 in Section 5 of the OLSRv2 specification (RFC XXXX), 1256 which indicates that: 1257 o WILL_NEVER (0) <= olsrv2WillRouting <= 1258 WILL_ALWAYS (15) 1260 This object is persistent and when written 1261 the entity SHOULD save the change to 1262 non-volatile storage." 1263 REFERENCE 1264 "Section 5 on Protocol Parameters. 1265 RFC XXXX - The Optimized Link State Routing Protocol 1266 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1267 and U. Herberg, March 2013." 1268 DEFVAL { 7 } 1269 ::= { olsrv2ConfigurationGroup 17 } 1271 olsrv2WillFlooding OBJECT-TYPE 1272 SYNTAX WillingnessTC 1273 MAX-ACCESS read-write 1274 STATUS current 1275 DESCRIPTION 1276 "olsrv2WillFlooding corresponds to 1277 WILL_FLOODING of OLSRv2. 1279 Guidance for setting this object may be found 1280 in Section 5 of the OLSRv2 specification (RFC XXXX), 1281 which indicates that: 1282 o WILL_NEVER (0) <= olsrv2WillFlooding <= 1283 WILL_ALWAYS (15) 1285 This object is persistent and when written 1286 the entity SHOULD save the change to 1287 non-volatile storage." 1288 REFERENCE 1289 "Section 5 on Protocol Parameters. 1290 RFC XXXX - The Optimized Link State Routing Protocol 1291 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1292 and U. Herberg, March 2013." 1293 DEFVAL { 7 } 1294 ::= { olsrv2ConfigurationGroup 18 } 1296 olsrv2LinkMetricType OBJECT-TYPE 1297 SYNTAX IANAolsrv2LinkMetricTypeTC 1298 MAX-ACCESS read-write 1299 STATUS current 1300 DESCRIPTION 1301 "olsrv2LinkMetricType corresponds to 1302 LINK_METRIC_TYPE of OLSRv2. 1304 If olsrv2LinkMetricType changes, then all 1305 link metric information recorded by this router 1306 is invalid. The router MUST take the 1307 actions described in Section 5.5. 1308 'Parameter Change Constraints' and 1309 Section 17 'Information Base Changes' 1310 in RFC XXXX. 1312 This object is persistent and when written 1313 the entity SHOULD save the change to 1314 non-volatile storage." 1315 REFERENCE 1316 "Section 5 on Protocol Parameters. 1317 RFC XXXX - The Optimized Link State Routing Protocol 1318 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1319 and U. Herberg, March 2013." 1320 DEFVAL { 0 } 1321 ::= { olsrv2ConfigurationGroup 19 } 1323 -- 1324 -- olsrv2StateGroup 1325 -- 1327 -- 1328 -- Contains information describing the current state of 1329 -- the OLSRv2 process. 1330 -- 1332 olsrv2StateGroup OBJECT IDENTIFIER ::= { olsrv2MIBObjects 2 } 1334 -- 1335 -- Interface Information Base (IIB) 1336 -- 1338 -- 1339 -- Link Set from RFC 6130, extended by L_in_metric, 1340 -- L_out_metric, and L_mpr_selector entries for each tuple 1341 -- 1343 olsrv2IibLinkSetTable OBJECT-TYPE 1344 SYNTAX SEQUENCE OF Olsrv2IibLinkSetEntry 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "A Link Set of an interface records all links 1349 from other routers which are, or recently 1350 were, 1-hop neighbors." 1351 REFERENCE 1352 "RFC XXXX - The Optimized Link State Routing Protocol 1353 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1354 and U. Herberg, March 2013." 1355 ::= { olsrv2StateGroup 1 } 1357 olsrv2IibLinkSetEntry OBJECT-TYPE 1358 SYNTAX Olsrv2IibLinkSetEntry 1359 MAX-ACCESS not-accessible 1360 STATUS current 1361 DESCRIPTION 1362 "A Link Set consists of Link Tuples, each 1363 representing a single link indexed by the 1364 local and remote interface pair. Each Link Set 1365 from NHDP is extended by OLSRv2 by the following 1366 fields: 1368 (L_in_metric (olsrv2IibLinkSetInMetricValue), 1369 L_out_metric (olsrv2IibLinkSetOutMetricValue), 1370 L_mpr_selector (olsrv2IibLinkSetMprSelector))" 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 AUGMENTS { nhdpIibLinkSetEntry } 1377 ::= { olsrv2IibLinkSetTable 1 } 1379 Olsrv2IibLinkSetEntry ::= 1380 SEQUENCE { 1381 olsrv2IibLinkSetInMetricValue 1382 Olsrv2MetricValueCompressedFormTC, 1383 olsrv2IibLinkSetOutMetricValue 1384 Olsrv2MetricValueCompressedFormTC, 1385 olsrv2IibLinkSetMprSelector 1386 TruthValue 1387 } 1389 olsrv2IibLinkSetInMetricValue OBJECT-TYPE 1390 SYNTAX Olsrv2MetricValueCompressedFormTC 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION 1394 "olsrv2IibLinkSetInMetricValue is the metric of the link 1395 from the OLSRv2 interface with addresses 1396 L_neighbor_iface_addr_list to this OLSRv2 interface. 1397 The L_neighbor_iface_addr_list is identified by 1398 the nhdpDiscIfIndex which is an index to the 1399 nhdpIibLinkSetTable which this table augments." 1400 REFERENCE 1401 "RFC XXXX - The Optimized Link State Routing Protocol 1402 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1403 and U. Herberg, March 2013." 1404 ::= { olsrv2IibLinkSetEntry 1 } 1406 olsrv2IibLinkSetOutMetricValue OBJECT-TYPE 1407 SYNTAX Olsrv2MetricValueCompressedFormTC 1408 MAX-ACCESS read-write 1409 STATUS current 1410 DESCRIPTION 1411 "olsrv2IibLinkSetOutMetricValue is the metric of the 1412 link to the OLSRv2 interface with addresses 1413 L_neighbor_iface_addr_list from this OLSRv2 interface. 1414 The L_neighbor_iface_addr_list is identified by 1415 the nhdpDiscIfIndex which is an index to the 1416 nhdpIibLinkSetTable which this table augments." 1417 REFERENCE 1418 "RFC XXXX - The Optimized Link State Routing Protocol 1419 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1421 and U. Herberg, March 2013." 1422 ::= { olsrv2IibLinkSetEntry 2 } 1424 olsrv2IibLinkSetMprSelector OBJECT-TYPE 1425 SYNTAX TruthValue 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "olsrv2IibLinkSetMprSelector is a boolean flag, 1430 recording whether this neighbor has selected this router 1431 as a flooding MPR, i.e., is a flooding MPR selector 1432 of this router." 1433 REFERENCE 1434 "RFC XXXX - The Optimized Link State Routing Protocol 1435 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1436 and U. Herberg, March 2013." 1437 ::= { olsrv2IibLinkSetEntry 3 } 1439 -- 1440 -- 2-Hop Set; from RFC 6130, extended by OLSRv2 by the 1441 -- following fields: N2_in_metric, N2_out_metric 1442 -- 1444 olsrv2Iib2HopSetTable OBJECT-TYPE 1445 SYNTAX SEQUENCE OF Olsrv2Iib2HopSetEntry 1446 MAX-ACCESS not-accessible 1447 STATUS current 1448 DESCRIPTION 1449 "A 2-Hop Set of an interface records network 1450 addresses of symmetric 2-hop neighbors, and 1451 the symmetric links to symmetric 1-hop neighbors 1452 through which these symmetric 2-hop neighbors 1453 can be reached. It consists of 2-Hop Tuples." 1454 REFERENCE 1455 "RFC XXXX - The Optimized Link State Routing Protocol 1456 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1457 and U. Herberg, March 2013." 1458 ::= { olsrv2StateGroup 2 } 1460 olsrv2Iib2HopSetEntry OBJECT-TYPE 1461 SYNTAX Olsrv2Iib2HopSetEntry 1462 MAX-ACCESS not-accessible 1463 STATUS current 1464 DESCRIPTION 1465 "olsrv2Iib2HopSetTable consists of 2-Hop Tuples, 1466 each representing a single network address of 1467 a symmetric 2-hop neighbor, and a single MANET 1468 interface of a symmetric 1-hop neighbor. 1470 Each 2-Hop Set from NHDP is extended by 1471 OLSRv2 by the following fields: 1473 (N2_in_metric (olsrv2Iib2HopSetInMetricValue), 1474 N2_out_metric (olsrv2Iib2HopSetOutMetricValue))" 1475 REFERENCE 1476 "RFC XXXX - The Optimized Link State Routing Protocol 1477 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1478 and U. Herberg, March 2013." 1479 AUGMENTS { nhdpIib2HopSetEntry } 1480 ::= { olsrv2Iib2HopSetTable 1 } 1482 Olsrv2Iib2HopSetEntry ::= 1483 SEQUENCE { 1484 olsrv2Iib2HopSetInMetricValue 1485 Olsrv2MetricValueCompressedFormTC, 1486 olsrv2Iib2HopSetOutMetricValue 1487 Olsrv2MetricValueCompressedFormTC 1488 } 1490 olsrv2Iib2HopSetInMetricValue OBJECT-TYPE 1491 SYNTAX Olsrv2MetricValueCompressedFormTC 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "olsrv2Iib2HopSetInMetricValue is the neighbor 1496 metric from the router with address 1497 N2_2hop_iface_addr to the router 1498 with OLSRv2 interface addresses 1499 N2_neighbor_iface_addr_list. 1501 The N2_2hop_iface_addr is identified by the 1502 (nhdpIib2HopSetIpAddressType, 1503 nhdpIib2HopSetIpAddress) pair from the 1504 nhdpIibLinkSetTable which this table augments. 1506 The N2_neighbor_iface_addr_list is defined by 1507 the nhdpDiscIfIndex which is an index of the 1508 nhdpIibLinkSetTable which this table augments." 1509 REFERENCE 1510 "RFC XXXX - The Optimized Link State Routing Protocol 1511 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1512 and U. Herberg, March 2013. 1514 and 1516 RFC 6779 - Definition of Managed Objects for the 1517 Neighboorhood Discovery Process, Herberg, U., 1518 Cole, R. and I. Chakeres, October 2012." 1519 ::= { olsrv2Iib2HopSetEntry 1 } 1521 olsrv2Iib2HopSetOutMetricValue OBJECT-TYPE 1522 SYNTAX Olsrv2MetricValueCompressedFormTC 1523 MAX-ACCESS read-only 1524 STATUS current 1525 DESCRIPTION 1526 "olsrv2Iib2HopSetOutMetricValue is the neighbor metric 1527 to the router with address N2_2hop_iface_addr 1528 from the router with OLSRv2 interface addresses 1529 N2_neighbor_iface_addr_list. 1531 The N2_2hop_iface_addr is identified by the 1532 (nhdpIib2HopSetIpAddressType, 1533 nhdpIib2HopSetIpAddress) pair from the 1534 nhdpIibLinkSetTable which this table augments. 1536 The N2_neighbor_iface_addr_list is defined by 1537 the nhdpDiscIfIndex which is an index of the 1538 nhdpIibLinkSetTable which this table augments." 1539 REFERENCE 1540 "RFC XXXX - The Optimized Link State Routing Protocol 1541 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1542 and U. Herberg, March 2013. 1544 and 1546 RFC 6779 - Definition of Managed Objects for the 1547 Neighboorhood Discovery Process, Herberg, U., 1548 Cole, R. and I. Chakeres, October 2012." 1549 ::= { olsrv2Iib2HopSetEntry 2 } 1551 -- 1552 -- Local Information Base - as defined in RFC 6130, 1553 -- extended by the addition of an Originator Set, 1554 -- defined in Section 6.1 and a Local Attached 1555 -- Network Set, defined in Section 6.2. 1556 -- 1558 -- 1559 -- Originator Set 1560 -- 1562 olsrv2LibOrigSetTable OBJECT-TYPE 1563 SYNTAX SEQUENCE OF Olsrv2LibOrigSetEntry 1564 MAX-ACCESS not-accessible 1565 STATUS current 1566 DESCRIPTION 1567 "A router's Originator Set records addresses 1568 that were recently used as originator addresses 1569 by this router." 1570 REFERENCE 1571 "RFC XXXX - The Optimized Link State Routing Protocol 1572 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1573 and U. Herberg, March 2013." 1574 ::= { olsrv2StateGroup 3 } 1576 olsrv2LibOrigSetEntry OBJECT-TYPE 1577 SYNTAX Olsrv2LibOrigSetEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "A router's Originator Set consists of 1582 Originator Tuples: 1584 (O_orig_addr (olsrv2LibOrigSetIpAddrType 1585 and olsrv2LibOrigSetIpAddr), 1586 O_time (olsrv2LibOrigSetExpireTime))." 1587 REFERENCE 1588 "RFC XXXX - The Optimized Link State Routing Protocol 1589 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1590 and U. Herberg, March 2013." 1591 INDEX { olsrv2LibOrigSetIpAddrType, 1592 olsrv2LibOrigSetIpAddr } 1593 ::= { olsrv2LibOrigSetTable 1 } 1595 Olsrv2LibOrigSetEntry ::= 1596 SEQUENCE { 1597 olsrv2LibOrigSetIpAddrType 1598 InetAddressType, 1599 olsrv2LibOrigSetIpAddr 1600 InetAddress, 1601 olsrv2LibOrigSetExpireTime 1602 TimeStamp 1603 } 1605 olsrv2LibOrigSetIpAddrType OBJECT-TYPE 1606 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1607 MAX-ACCESS not-accessible 1608 STATUS current 1609 DESCRIPTION 1610 "The type of the olsrv2LibOrigSetIpAddr, 1611 as defined in the InetAddress MIB (RFC4001). 1613 Only the values 'ipv4(1)' and 1614 'ipv6(2)' are supported." 1615 REFERENCE 1616 "RFC XXXX - The Optimized Link State Routing Protocol 1617 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1618 and U. Herberg, March 2013." 1619 ::= { olsrv2LibOrigSetEntry 1 } 1621 olsrv2LibOrigSetIpAddr OBJECT-TYPE 1622 SYNTAX InetAddress (SIZE(4|16)) 1623 MAX-ACCESS not-accessible 1624 STATUS current 1625 DESCRIPTION 1626 "An originator address recently employed 1627 by this router." 1628 REFERENCE 1629 "RFC XXXX - The Optimized Link State Routing Protocol 1630 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1631 and U. Herberg, March 2013." 1632 ::= { olsrv2LibOrigSetEntry 2 } 1634 olsrv2LibOrigSetExpireTime OBJECT-TYPE 1635 SYNTAX TimeStamp 1636 UNITS "centiseconds" 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "olsrv2LibOrigSetExpireTime specifies the value 1641 of sysUptime when this entry SHOULD expire and be 1642 removed from the olsrv2LibOrigSetTable. This time 1643 is determined at the time the entry is added, 1644 derived from the following expression: 1646 O_time := current time + O_HOLD_TIME 1648 where O_time is olsrv2LibOrigSetExpireTime, 1649 current_time is current sysUpTime and 1650 O_HOLD_TIME is a parameter of the OLSRv2 1651 protocol. In the event that the 1652 O_HOLD_TIME is changed, then the 1653 olsrv2LibOrigSetExpireTime needs to be 1654 recomputed for each of the entries in this Table." 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 ::= { olsrv2LibOrigSetEntry 3 } 1660 -- 1661 -- Local Attached Network Set 1662 -- 1664 olsrv2LibLocAttNetSetTable OBJECT-TYPE 1665 SYNTAX SEQUENCE OF Olsrv2LibLocAttNetSetEntry 1666 MAX-ACCESS not-accessible 1667 STATUS current 1668 DESCRIPTION 1669 "A router's Local Attached Network Set records 1670 its local non-OLSRv2 interfaces via which it 1671 can act as gateways to other networks." 1672 REFERENCE 1673 "RFC XXXX - The Optimized Link State Routing Protocol 1674 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1675 and U. Herberg, March 2013." 1676 ::= { olsrv2StateGroup 4 } 1678 olsrv2LibLocAttNetSetEntry OBJECT-TYPE 1679 SYNTAX Olsrv2LibLocAttNetSetEntry 1680 MAX-ACCESS not-accessible 1681 STATUS current 1682 DESCRIPTION 1683 "The entries include the Local Attached 1684 Network Tuples: 1686 (AL_net_addr (olsrv2LibLocAttNetSetIpAddr), 1687 AL_dist (olsrv2LibLocAttNetSetDistance), 1688 AL_metric (olsrv2LibLocAttNetSetMetricValue) 1689 ) 1691 where: 1693 AL_net_addr is the network address 1694 of an attached network which can 1695 be reached via this router. The 1696 AL_net_addr is defined in this MIB 1697 module by the tuple 1698 (olsrv2LibLocAttNetSetIpAddrType, 1699 olsrv2LibLocAttNetSetIpAddr, 1700 olsrv2LibLocAttNetSetIpAddrPrefixLen). 1702 AL_dist is the number of hops to 1703 the network with address AL_net_addr 1704 from this router. The AL_dist is 1705 defined in this MIB module by the 1706 olsrv2LibLocAttNetSetDistance object. 1708 AL_metric is the metric of the link to 1709 the attached network with address 1710 AL_net_addr from this router. The 1711 AL_metric is defined in this MIB module 1712 by the olsrv2LibLocAttNetSetMetricValue 1713 object. 1715 OLSRv2 (RFC XXXX) defines the rules for managing 1716 entries within this table, e.g., populating 1717 and purging entries. Specific instructions for the 1718 olsrv2LibLocAttNetSetEntry(s) are found in 1719 Section 7.2 and Section 17 of OLSRv2 (RFC XXXX)." 1720 REFERENCE 1721 "RFC XXXX - The Optimized Link State Routing Protocol 1722 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1723 and U. Herberg, March 2013." 1724 INDEX { olsrv2LibLocAttNetSetIpAddrType, 1725 olsrv2LibLocAttNetSetIpAddr, 1726 olsrv2LibLocAttNetSetIpAddrPrefixLen } 1727 ::= { olsrv2LibLocAttNetSetTable 1 } 1729 Olsrv2LibLocAttNetSetEntry ::= 1730 SEQUENCE { 1731 olsrv2LibLocAttNetSetIpAddrType 1732 InetAddressType, 1733 olsrv2LibLocAttNetSetIpAddr 1734 InetAddress, 1735 olsrv2LibLocAttNetSetIpAddrPrefixLen 1736 InetAddressPrefixLength, 1737 olsrv2LibLocAttNetSetDistance 1738 Unsigned32, 1739 olsrv2LibLocAttNetSetMetricValue 1740 Olsrv2MetricValueCompressedFormTC 1741 } 1743 olsrv2LibLocAttNetSetIpAddrType OBJECT-TYPE 1744 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1745 MAX-ACCESS not-accessible 1746 STATUS current 1747 DESCRIPTION 1748 "The type of the olsrv2LibLocAttNetSetIpAddr, as defined 1749 in the InetAddress MIB (RFC 4001). 1751 Only the values 'ipv4(1)' and 1752 'ipv6(2)' are supported." 1753 REFERENCE 1754 "RFC XXXX - The Optimized Link State Routing Protocol 1755 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1757 and U. Herberg, March 2013." 1758 ::= { olsrv2LibLocAttNetSetEntry 1 } 1760 olsrv2LibLocAttNetSetIpAddr OBJECT-TYPE 1761 SYNTAX InetAddress (SIZE(4|16)) 1762 MAX-ACCESS not-accessible 1763 STATUS current 1764 DESCRIPTION 1765 "This is the network address of an attached 1766 network which can be reached via this router." 1767 REFERENCE 1768 "RFC XXXX - The Optimized Link State Routing Protocol 1769 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1770 and U. Herberg, March 2013." 1771 ::= { olsrv2LibLocAttNetSetEntry 2 } 1773 olsrv2LibLocAttNetSetIpAddrPrefixLen OBJECT-TYPE 1774 SYNTAX InetAddressPrefixLength 1775 UNITS "bits" 1776 MAX-ACCESS not-accessible 1777 STATUS current 1778 DESCRIPTION 1779 "Indicates the number of leading one bits that form the 1780 mask to be logically ANDed with the destination address 1781 before being compared to the value in the 1782 olsrv2LibLocAttNetSetIpAddr field." 1783 REFERENCE 1784 "RFC XXXX - The Optimized Link State Routing Protocol 1785 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1786 and U. Herberg, March 2013." 1787 ::= { olsrv2LibLocAttNetSetEntry 3 } 1789 olsrv2LibLocAttNetSetDistance OBJECT-TYPE 1790 SYNTAX Unsigned32 (1..255) 1791 UNITS "hops" 1792 MAX-ACCESS read-only 1793 STATUS current 1794 DESCRIPTION 1795 "This object specifies the number of hops 1796 to the network with address 1797 olsrv2LibLocAttNetSetIpAddr from this router." 1798 REFERENCE 1799 "RFC XXXX - The Optimized Link State Routing Protocol 1800 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1801 and U. Herberg, March 2013." 1802 ::= { olsrv2LibLocAttNetSetEntry 4 } 1804 olsrv2LibLocAttNetSetMetricValue OBJECT-TYPE 1805 SYNTAX Olsrv2MetricValueCompressedFormTC 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "This object specifies the metric of the 1810 link to the attached network with 1811 address AL_net_addr from this router. The 1812 AL_net_addr is defined by the tuple 1813 (olsrv2LibLocAttNetSetIpAddrType, 1814 olsrv2LibLocAttNetSetIpAddr, 1815 olsrv2LibLocAttNetSetIpAddrPrefixLen)." 1816 REFERENCE 1817 "RFC XXXX - The Optimized Link State Routing Protocol 1818 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1819 and U. Herberg, March 2013." 1820 ::= { olsrv2LibLocAttNetSetEntry 5 } 1822 -- 1823 -- Neighbor Information Base - as defined in RFC 6130, 1824 -- extended by OLSRv2 by the addition of the following 1825 -- elements to each Neighbor Tuple 1826 -- 1828 -- 1829 -- Neighbor Set 1830 -- 1832 olsrv2NibNeighborSetTable OBJECT-TYPE 1833 SYNTAX SEQUENCE OF Olsrv2NibNeighborSetEntry 1834 MAX-ACCESS not-accessible 1835 STATUS current 1836 DESCRIPTION 1837 "A router's Neighbor Set records all network 1838 addresses of each 1-hop neighbor. It consists 1839 of Neighbor Tuples, each representing a single 1840 1-hop neighbor. " 1841 REFERENCE 1842 "RFC XXXX - The Optimized Link State Routing Protocol 1843 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1844 and U. Herberg, March 2013." 1845 ::= { olsrv2StateGroup 5 } 1847 olsrv2NibNeighborSetEntry OBJECT-TYPE 1848 SYNTAX Olsrv2NibNeighborSetEntry 1849 MAX-ACCESS not-accessible 1850 STATUS current 1851 DESCRIPTION 1852 "Each Neighbor Tuple in the Neighbor Set, defined 1853 in RFC 6130, has these additional elements: 1854 N_orig_addr (olsrv2NibNeighborSetNOrigIpAddrType, 1855 olsrv2NibNeighborSetNOrigIpAddr) 1856 N_in_metric (olsrv2NibNeighborSetNInMetricValue) 1857 N_out_metric (olsrv2NibNeighborSetNOutMetricValue) 1858 N_will_flooding (olsrv2NibNeighborSetNWillFlooding) 1859 N_will_routing (olsrv2NibNeighborSetNWillRouting) 1860 N_flooding_mpr (olsrv2NibNeighborSetNFloodingMpr) 1861 N_routing_mpr (olsrv2NibNeighborSetNRoutingMpr) 1862 N_mpr_selector (olsrv2NibNeighborSetNMprSelector) 1863 N_advertised (olsrv2NibNeighborSetNAdvertised) 1864 defined here as extensions." 1865 REFERENCE 1866 "RFC XXXX - The Optimized Link State Routing Protocol 1867 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1868 and U. Herberg, March 2013." 1869 AUGMENTS { nhdpNibNeighborSetEntry } 1870 ::= { olsrv2NibNeighborSetTable 1 } 1872 Olsrv2NibNeighborSetEntry ::= 1873 SEQUENCE { 1874 olsrv2NibNeighborSetNOrigIpAddrType 1875 InetAddressType, 1876 olsrv2NibNeighborSetNOrigIpAddr 1877 InetAddress, 1878 olsrv2NibNeighborSetNInMetricValue 1879 Olsrv2MetricValueCompressedFormTC, 1880 olsrv2NibNeighborSetNOutMetricValue 1881 Olsrv2MetricValueCompressedFormTC, 1882 olsrv2NibNeighborSetNWillFlooding 1883 WillingnessTC, 1884 olsrv2NibNeighborSetNWillRouting 1885 WillingnessTC, 1886 olsrv2NibNeighborSetNFloodingMpr 1887 TruthValue, 1888 olsrv2NibNeighborSetNRoutingMpr 1889 TruthValue, 1890 olsrv2NibNeighborSetNMprSelector 1891 TruthValue, 1892 olsrv2NibNeighborSetNAdvertised 1893 TruthValue 1894 } 1896 olsrv2NibNeighborSetNOrigIpAddrType OBJECT-TYPE 1897 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION 1901 "The type of the olsrv2NibNeighborSetNOrigIpAddr, as defined 1902 in the InetAddress MIB module (RFC4001). 1904 Only the values 'ipv4(1)' and 1905 'ipv6(2)' are supported." 1906 REFERENCE 1907 "RFC XXXX - The Optimized Link State Routing Protocol 1908 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1909 and U. Herberg, March 2013." 1910 ::= { olsrv2NibNeighborSetEntry 1 } 1912 olsrv2NibNeighborSetNOrigIpAddr OBJECT-TYPE 1913 SYNTAX InetAddress (SIZE(4|16)) 1914 MAX-ACCESS read-only 1915 STATUS current 1916 DESCRIPTION 1917 "This is the originator IP address of the neighbor 1918 represented by this table entry." 1919 REFERENCE 1920 "RFC XXXX - The Optimized Link State Routing Protocol 1921 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1922 and U. Herberg, March 2013." 1923 ::= { olsrv2NibNeighborSetEntry 2 } 1925 olsrv2NibNeighborSetNInMetricValue OBJECT-TYPE 1926 SYNTAX Olsrv2MetricValueCompressedFormTC 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "This object is the neighbor metric of any 1931 link from this neighbor to an OLSRv2 interface 1932 of this router, i.e., the minimum of all corresponding 1933 L_in_metric (olsrv2IibLinkSetInMetricValue) 1934 with L_status = SYMMETRIC and 1935 L_in_metric (olsrv2IibLinkSetInMetricValue) != UNKNOWN_METRIC, 1936 UNKNOWN_METRIC if there are no such Link Tuples. 1937 UNKNOWN_METRIC has a value of 0." 1938 REFERENCE 1939 "RFC XXXX - The Optimized Link State Routing Protocol 1940 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1941 and U. Herberg, March 2013." 1942 ::= { olsrv2NibNeighborSetEntry 3 } 1944 olsrv2NibNeighborSetNOutMetricValue OBJECT-TYPE 1945 SYNTAX Olsrv2MetricValueCompressedFormTC 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "This object is the neighbor metric of any 1950 link from an OLSRv2 interface of this router 1951 to this neighbor, i.e., the minimum of all 1952 corresponding L_out_metric 1953 (olsrv2IibLinkSetOutMetricValue) with L_status = 1954 SYMMETRIC and L_out_metric 1955 (olsrv2IibLinkSetOutMetricValue) != UNKNOWN_METRIC, 1956 UNKNOWN_METRIC if there are no such Link Tuples. 1957 UNKNOWN_METRIC has a value of 0." 1958 REFERENCE 1959 "RFC XXXX - The Optimized Link State Routing Protocol 1960 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1961 and U. Herberg, March 2013." 1962 ::= { olsrv2NibNeighborSetEntry 4 } 1964 olsrv2NibNeighborSetNWillFlooding OBJECT-TYPE 1965 SYNTAX WillingnessTC 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "This object is the neighbor's willingness to be 1970 selected as a flooding MPR, in the range from 1971 WILL_NEVER to WILL_ALWAYS, both inclusive, taking 1972 the value WILL_NEVER if no OLSRv2 specific 1973 information is received from this neighbor." 1974 REFERENCE 1975 "RFC XXXX - The Optimized Link State Routing Protocol 1976 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1977 and U. Herberg, March 2013." 1978 ::= { olsrv2NibNeighborSetEntry 5 } 1980 olsrv2NibNeighborSetNWillRouting OBJECT-TYPE 1981 SYNTAX WillingnessTC 1982 MAX-ACCESS read-only 1983 STATUS current 1984 DESCRIPTION 1985 "This object is the neighbor's willingness to be 1986 selected as a routing MPR, in the range from 1987 WILL_NEVER to WILL_ALWAYS, both inclusive, taking 1988 the value WILL_NEVER if no OLSRv2 specific 1989 information is received from this neighbor." 1990 REFERENCE 1991 "RFC XXXX - The Optimized Link State Routing Protocol 1992 version 2, Clausen, T., Dearlove, C., Jacquet, P. 1993 and U. Herberg, March 2013." 1994 ::= { olsrv2NibNeighborSetEntry 6 } 1995 olsrv2NibNeighborSetNFloodingMpr OBJECT-TYPE 1996 SYNTAX TruthValue 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "This object is a boolean flag, recording whether 2001 this neighbor is selected as a flooding MPR 2002 by this router." 2003 REFERENCE 2004 "RFC XXXX - The Optimized Link State Routing Protocol 2005 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2006 and U. Herberg, March 2013." 2007 ::= { olsrv2NibNeighborSetEntry 7 } 2009 olsrv2NibNeighborSetNRoutingMpr OBJECT-TYPE 2010 SYNTAX TruthValue 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "This object is a boolean flag, recording whether 2015 this neighbor is selected as a routing MPR 2016 by this router." 2017 REFERENCE 2018 "RFC XXXX - The Optimized Link State Routing Protocol 2019 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2020 and U. Herberg, March 2013." 2021 ::= { olsrv2NibNeighborSetEntry 8 } 2023 olsrv2NibNeighborSetNMprSelector OBJECT-TYPE 2024 SYNTAX TruthValue 2025 MAX-ACCESS read-only 2026 STATUS current 2027 DESCRIPTION 2028 "This object is a boolean flag, 2029 recording whether this neighbor has selected this router 2030 as a routing MPR, i.e., is a routing MPR 2031 selector of this router. 2033 When set to 'true', then this router is selected as 2034 a routing MPR by the neighbor router. 2035 When set to 'false', 2036 then this router is not selected by the neighbor 2037 as a routing MPR." 2038 REFERENCE 2039 "RFC XXXX - The Optimized Link State Routing Protocol 2040 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2041 and U. Herberg, March 2013." 2042 ::= { olsrv2NibNeighborSetEntry 9 } 2043 olsrv2NibNeighborSetNAdvertised OBJECT-TYPE 2044 SYNTAX TruthValue 2045 MAX-ACCESS read-only 2046 STATUS current 2047 DESCRIPTION 2048 "This object, N_mpr_selector 2049 (olsrv2NibNeighborSetNMprSelector), is a boolean flag, 2050 recording whether this router has elected to 2051 advertise a link to this neighbor in its TC messages." 2052 REFERENCE 2053 "RFC XXXX - The Optimized Link State Routing Protocol 2054 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2055 and U. Herberg, March 2013." 2056 ::= { olsrv2NibNeighborSetEntry 10 } 2058 olsrv2NibNeighborSetTableAnsn OBJECT-TYPE 2059 SYNTAX Unsigned32 (0..65535) 2060 MAX-ACCESS read-only 2061 STATUS current 2062 DESCRIPTION 2063 "Advertised Neighbor Sequence Number (ANSN), is 2064 a variable, whose value is included in TC messages to 2065 indicate the freshness of the information transmitted." 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 ::= { olsrv2StateGroup 6 } 2072 -- 2073 -- Topology Information Base - this Information 2074 -- Base is specific to OLSRv2, and is defined in 2075 -- Section 10 of RFC XXXX. 2076 -- 2078 -- 2079 -- Advertising Remote Router Set 2080 -- 2082 olsrv2TibAdRemoteRouterSetTable OBJECT-TYPE 2083 SYNTAX SEQUENCE OF Olsrv2TibAdRemoteRouterSetEntry 2084 MAX-ACCESS not-accessible 2085 STATUS current 2086 DESCRIPTION 2087 "A router's Advertising Remote Router Set records 2088 information describing each remote router in the 2089 network that transmits TC messages." 2090 REFERENCE 2091 "RFC XXXX - The Optimized Link State Routing Protocol 2092 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2093 and U. Herberg, March 2013." 2094 ::= { olsrv2StateGroup 7 } 2096 olsrv2TibAdRemoteRouterSetEntry OBJECT-TYPE 2097 SYNTAX Olsrv2TibAdRemoteRouterSetEntry 2098 MAX-ACCESS not-accessible 2099 STATUS current 2100 DESCRIPTION 2101 "A router's Advertised Neighbor Set Table entry 2102 consists of Advertising Remote Router Tuples: 2104 (AR_orig_addr (olsrv2TibAdRemoteRouterSetIpAddrType, 2105 olsrv2TibAdRemoteRouterSetIpAddr), 2106 AR_seq_number (olsrv2TibAdRemoteRouterSetMaxSeqNo), 2107 AR_time (olsrv2TibAdRemoteRouterSetExpireTime). 2109 Addresses associated with this router are 2110 found in the NHDP-MIB module's nhdpDiscIfSetTable. 2112 OLSRv2 (RFC XXXX) defines the rules for managing 2113 entries within this table, e.g., populating 2114 and purging entries. Specific instructions for the 2115 olsrv2TibAdRemoteRouterSetEntry(s) are found in 2116 Section 10.1 and Section 17 of OLSRv2 (RFC XXXX)." 2117 REFERENCE 2118 "RFC XXXX - The Optimized Link State Routing Protocol 2119 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2120 and U. Herberg, March 2013." 2121 INDEX { olsrv2TibAdRemoteRouterSetIpAddrType, 2122 olsrv2TibAdRemoteRouterSetIpAddr } 2123 ::= { olsrv2TibAdRemoteRouterSetTable 1 } 2125 Olsrv2TibAdRemoteRouterSetEntry ::= 2126 SEQUENCE { 2127 olsrv2TibAdRemoteRouterSetIpAddrType 2128 InetAddressType, 2129 olsrv2TibAdRemoteRouterSetIpAddr 2130 InetAddress, 2131 olsrv2TibAdRemoteRouterSetMaxSeqNo 2132 Unsigned32, 2133 olsrv2TibAdRemoteRouterSetExpireTime 2134 TimeStamp 2135 } 2137 olsrv2TibAdRemoteRouterSetIpAddrType OBJECT-TYPE 2138 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2139 MAX-ACCESS not-accessible 2140 STATUS current 2141 DESCRIPTION 2142 "The type of the olsrv2TibAdRemoteRouterSetIpAddr, 2143 as defined in the InetAddress MIB module (RFC4001). 2145 Only the values 'ipv4(1)' and 2146 'ipv6(2)' are supported." 2147 REFERENCE 2148 "RFC XXXX - The Optimized Link State Routing Protocol 2149 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2150 and U. Herberg, March 2013." 2151 ::= { olsrv2TibAdRemoteRouterSetEntry 1 } 2153 olsrv2TibAdRemoteRouterSetIpAddr OBJECT-TYPE 2154 SYNTAX InetAddress (SIZE(4|16)) 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "This is the originator address of a received 2159 TC message." 2160 REFERENCE 2161 "RFC XXXX - The Optimized Link State Routing Protocol 2162 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2163 and U. Herberg, March 2013." 2164 ::= { olsrv2TibAdRemoteRouterSetEntry 2 } 2166 olsrv2TibAdRemoteRouterSetMaxSeqNo OBJECT-TYPE 2167 SYNTAX Unsigned32 (0..65535) 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "This is the greatest Assigned Neighbor Sequence 2172 Number (ANSN) in any TC message 2173 received which originated from the router 2174 with originator address 2175 olsrv2TibAdRemoteRouterSetIpAddr. 2177 Sequence numbers are used in the OLSRv2 protocol 2178 for the purpose of discarding 'old' information, 2179 i.e., messages received out of order. However 2180 with a limited number of bits for representing 2181 sequence numbers, wrap-around (that the sequence 2182 number is incremented from the maximum possible 2183 value to zero) will occur. To prevent this from 2184 interfering with the operation of this protocol, 2185 OLSRv2 implementations observe the following when 2186 determining the ordering of sequence numbers. 2188 In OLSRv2, MAXVALUE designates one more than the 2189 largest possible value for a sequence number. 2190 For a 16 bit sequence number MAXVALUE is 65536. 2192 The sequence number S1 is said to be 'greater than' 2193 the sequence number S2 if: 2195 o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR 2197 o S2 > S1 AND S2 - S1 > MAXVALUE/2 2199 When sequence numbers S1 and S2 differ by MAXVALUE/2 2200 their ordering cannot be determined. In this case, 2201 which should not occur, either ordering may be 2202 assumed. 2204 Thus when comparing two messages, it is possible 2205 - even in the presence of wrap-around - to determine 2206 which message contains the most recent information." 2207 REFERENCE 2208 "RFC XXXX - The Optimized Link State Routing Protocol 2209 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2210 and U. Herberg, March 2013." 2211 ::= { olsrv2TibAdRemoteRouterSetEntry 3 } 2213 olsrv2TibAdRemoteRouterSetExpireTime OBJECT-TYPE 2214 SYNTAX TimeStamp 2215 UNITS "centiseconds" 2216 MAX-ACCESS not-accessible 2217 STATUS current 2218 DESCRIPTION 2219 "olsrv2TibAdRemoteRouterSetExpireTime specifies the value 2220 of sysUptime when this entry SHOULD expire and be 2221 removed from the olsrv2TibAdRemoteRouterSetTable." 2222 REFERENCE 2223 "RFC XXXX - The Optimized Link State Routing Protocol 2224 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2225 and U. Herberg, March 2013." 2226 ::= { olsrv2TibAdRemoteRouterSetEntry 4 } 2228 -- 2229 -- Router Topology Set 2230 -- 2231 olsrv2TibRouterTopologySetTable OBJECT-TYPE 2232 SYNTAX SEQUENCE OF Olsrv2TibTopologySetEntry 2233 MAX-ACCESS not-accessible 2234 STATUS current 2235 DESCRIPTION 2236 "A router's Router Topology Set records topology 2237 information about the network." 2238 REFERENCE 2239 "RFC XXXX - The Optimized Link State Routing Protocol 2240 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2241 and U. Herberg, March 2013." 2242 ::= { olsrv2StateGroup 8 } 2244 olsrv2TibRouterTopologySetEntry OBJECT-TYPE 2245 SYNTAX Olsrv2TibTopologySetEntry 2246 MAX-ACCESS not-accessible 2247 STATUS current 2248 DESCRIPTION 2249 "It consists of Router Topology Tuples: 2251 (TR_from_orig_addr 2252 (olsrv2TibRouterTopologySetFromOrigIpAddrType, 2253 olsrv2TibRouterTopologySetFromOrigIpAddr), 2254 TR_to_orig_addr 2255 (olsrv2TibRouterTopologySetToOrigIpAddrType, 2256 olsrv2TibRouterTopologySetToOrigIpAddr), 2257 TR_seq_number (olsrv2TibRouterTopologySetSeqNo), 2258 TR_metric (olsrv2TibRouterTopologySetMetricValue), 2259 TR_time (olsrv2TibRouterTopologySetExpireTime)). 2261 OLSRv2 (RFC XXXX) defines the rules for managing 2262 entries within this table, e.g., populating 2263 and purging entries. Specific instructions for the 2264 olsrv2TibRouterTopologySetEntry(s) are found in 2265 Section 10.2 and Section 17 of OLSRv2 (RFC XXXX)." 2266 REFERENCE 2267 "RFC XXXX - The Optimized Link State Routing Protocol 2268 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2269 and U. Herberg, March 2013." 2270 INDEX { olsrv2TibRouterTopologySetFromOrigIpAddrType, 2271 olsrv2TibRouterTopologySetFromOrigIpAddr, 2272 olsrv2TibRouterTopologySetToOrigIpAddrType, 2273 olsrv2TibRouterTopologySetToOrigIpAddr } 2274 ::= { olsrv2TibRouterTopologySetTable 1 } 2276 Olsrv2TibTopologySetEntry ::= 2277 SEQUENCE { 2278 olsrv2TibRouterTopologySetFromOrigIpAddrType 2279 InetAddressType, 2280 olsrv2TibRouterTopologySetFromOrigIpAddr 2281 InetAddress, 2282 olsrv2TibRouterTopologySetToOrigIpAddrType 2283 InetAddressType, 2284 olsrv2TibRouterTopologySetToOrigIpAddr 2285 InetAddress, 2286 olsrv2TibRouterTopologySetSeqNo 2287 Unsigned32, 2288 olsrv2TibRouterTopologySetMetricValue 2289 Olsrv2MetricValueCompressedFormTC, 2290 olsrv2TibRouterTopologySetExpireTime 2291 TimeStamp 2292 } 2294 olsrv2TibRouterTopologySetFromOrigIpAddrType OBJECT-TYPE 2295 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2296 MAX-ACCESS not-accessible 2297 STATUS current 2298 DESCRIPTION 2299 "The type of the olsrv2TibRouterTopologySetFromOrigIpAddr, 2300 as defined in the InetAddress MIB module (RFC4001). 2302 Only the values 'ipv4(1)' and 2303 'ipv6(2)' are supported." 2304 REFERENCE 2305 "RFC XXXX - The Optimized Link State Routing Protocol 2306 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2307 and U. Herberg, March 2013." 2308 ::= { olsrv2TibRouterTopologySetEntry 1 } 2310 olsrv2TibRouterTopologySetFromOrigIpAddr OBJECT-TYPE 2311 SYNTAX InetAddress (SIZE(4|16)) 2312 MAX-ACCESS not-accessible 2313 STATUS current 2314 DESCRIPTION 2315 "This is the originator address of a router which can 2316 reach the router with originator address TR_to_orig_addr 2317 in one hop." 2318 REFERENCE 2319 "RFC XXXX - The Optimized Link State Routing Protocol 2320 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2321 and U. Herberg, March 2013." 2322 ::= { olsrv2TibRouterTopologySetEntry 2 } 2324 olsrv2TibRouterTopologySetToOrigIpAddrType OBJECT-TYPE 2325 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2326 MAX-ACCESS not-accessible 2327 STATUS current 2328 DESCRIPTION 2329 "The type of the olsrv2TibRouterTopologySetToOrigIpAddr, 2330 as defined in the InetAddress MIB module (RFC4001). 2332 Only the values 'ipv4(1)' and 2333 'ipv6(2)' are supported." 2334 REFERENCE 2335 "RFC XXXX - The Optimized Link State Routing Protocol 2336 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2337 and U. Herberg, March 2013." 2338 ::= { olsrv2TibRouterTopologySetEntry 3 } 2340 olsrv2TibRouterTopologySetToOrigIpAddr OBJECT-TYPE 2341 SYNTAX InetAddress (SIZE(4|16)) 2342 MAX-ACCESS not-accessible 2343 STATUS current 2344 DESCRIPTION 2345 "This is the originator address of a router which can be 2346 reached by the router with originator address 2347 TR_to_orig_addr in one hop." 2348 REFERENCE 2349 "RFC XXXX - The Optimized Link State Routing Protocol 2350 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2351 and U. Herberg, March 2013." 2352 ::= { olsrv2TibRouterTopologySetEntry 4 } 2354 olsrv2TibRouterTopologySetSeqNo OBJECT-TYPE 2355 SYNTAX Unsigned32 (0..65535) 2356 MAX-ACCESS read-only 2357 STATUS current 2358 DESCRIPTION 2359 "This is the greatest Assigned Neighbor Sequence 2360 Number (ANSN) in any TC message 2361 received which originated from the router 2362 with originator address TR_from_orig_addr, 2363 i.e., which contributed to the information 2364 contained in this Tuple and is defined by the 2365 objects: 2366 (olsrv2TibRouterTopologySetFromOrigIpAddrType, 2367 olsrv2TibRouterTopologySetFromOrigIpAddr). 2369 Sequence numbers are used in the OLSRv2 protocol 2370 for the purpose of discarding 'old' information, 2371 i.e., messages received out of order. However 2372 with a limited number of bits for representing 2373 sequence numbers, wrap-around (that the sequence 2374 number is incremented from the maximum possible 2375 value to zero) will occur. To prevent this from 2376 interfering with the operation of this protocol, 2377 OLSRv2 implementations observe the following when 2378 determining the ordering of sequence numbers. 2380 In OLSRv2, MAXVALUE designates one more than the 2381 largest possible value for a sequence number. 2382 For a 16 bit sequence number MAXVALUE is 65536. 2384 The sequence number S1 is said to be 'greater than' 2385 the sequence number S2 if: 2387 o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR 2389 o S2 > S1 AND S2 - S1 > MAXVALUE/2 2391 When sequence numbers S1 and S2 differ by MAXVALUE/2 2392 their ordering cannot be determined. In this case, 2393 which should not occur, either ordering may be 2394 assumed. 2396 Thus when comparing two messages, it is possible 2397 - even in the presence of wrap-around - to determine 2398 which message contains the most recent information." 2399 REFERENCE 2400 "RFC XXXX - The Optimized Link State Routing Protocol 2401 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2402 and U. Herberg, March 2013." 2403 ::= { olsrv2TibRouterTopologySetEntry 5 } 2405 olsrv2TibRouterTopologySetMetricValue OBJECT-TYPE 2406 SYNTAX Olsrv2MetricValueCompressedFormTC 2407 MAX-ACCESS read-only 2408 STATUS current 2409 DESCRIPTION 2410 "This is the neighbor metric from the router 2411 with originator address TR_from_orig_addr 2412 (olsrv2TibRouterTopologySetFromOrigIpAddrType, 2413 olsrv2TibRouterTopologySetFromOrigIpAddr) to 2414 the router with originator address TR_to_orig_addr 2415 (olsrv2TibRouterTopologySetToOrigIpAddrType, 2416 olsrv2TibRouterTopologySetToOrigIpAddr)." 2417 REFERENCE 2418 "RFC XXXX - The Optimized Link State Routing Protocol 2419 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2420 and U. Herberg, March 2013." 2421 ::= { olsrv2TibRouterTopologySetEntry 6 } 2422 olsrv2TibRouterTopologySetExpireTime OBJECT-TYPE 2423 SYNTAX TimeStamp 2424 UNITS "centiseconds" 2425 MAX-ACCESS not-accessible 2426 STATUS current 2427 DESCRIPTION 2428 "olsrv2TibRouterTopologySetExpireTime specifies the value 2429 of sysUptime when this entry SHOULD expire and be 2430 removed from the olsrv2TibRouterTopologySetTable." 2431 REFERENCE 2432 "RFC XXXX - The Optimized Link State Routing Protocol 2433 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2434 and U. Herberg, March 2013." 2435 ::= { olsrv2TibRouterTopologySetEntry 7 } 2437 -- 2438 -- Routable Address Topology Set 2439 -- 2441 olsrv2TibRoutableAddressTopologySetTable OBJECT-TYPE 2442 SYNTAX SEQUENCE OF Olsrv2TibRoutableAddressTopologySetEntry 2443 MAX-ACCESS not-accessible 2444 STATUS current 2445 DESCRIPTION 2446 "A router's Routable Address Topology Set records topology 2447 information about the routable addresses within the MANET, 2448 and via which routers they may be reached." 2449 REFERENCE 2450 "RFC XXXX - The Optimized Link State Routing Protocol 2451 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2452 and U. Herberg, March 2013." 2453 ::= { olsrv2StateGroup 9 } 2455 olsrv2TibRoutableAddressTopologySetEntry OBJECT-TYPE 2456 SYNTAX Olsrv2TibRoutableAddressTopologySetEntry 2457 MAX-ACCESS not-accessible 2458 STATUS current 2459 DESCRIPTION 2460 "It consists of Router Topology Tuples: 2462 (TA_from_orig_addr 2463 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType 2464 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr), 2465 TA_dest_addr 2466 (olsrv2TibRoutableAddressTopologySetFromDestIpAddrType 2467 olsrv2TibRoutableAddressTopologySetFromDestIpAddr), 2468 TA_seq_number (olsrv2TibRoutableAddressTopologySetSeqNo) 2469 TA_metric (olsrv2TibRoutableAddressTopologySetMetricValue) 2470 TA_time (olsrv2TibRoutableAddressTopologySetExpireTime) 2471 ) 2473 OLSRv2 (RFC XXXX) defines the rules for managing 2474 entries within this table, e.g., populating 2475 and purging entries. Specific instructions for the 2476 olsrv2TibRoutableAddressTopologySetEntry(s) are found 2477 in Section 10.3 and Section 17 of OLSRv2 (RFC XXXX)." 2478 REFERENCE 2479 "RFC XXXX - The Optimized Link State Routing Protocol 2480 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2481 and U. Herberg, March 2013." 2482 INDEX { olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType, 2483 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, 2484 olsrv2TibRoutableAddressTopologySetDestIpAddrType, 2485 olsrv2TibRoutableAddressTopologySetDestIpAddr } 2486 ::= { olsrv2TibRoutableAddressTopologySetTable 1 } 2488 Olsrv2TibRoutableAddressTopologySetEntry ::= 2489 SEQUENCE { 2490 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType 2491 InetAddressType, 2492 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr 2493 InetAddress, 2494 olsrv2TibRoutableAddressTopologySetDestIpAddrType 2495 InetAddressType, 2496 olsrv2TibRoutableAddressTopologySetDestIpAddr 2497 InetAddress, 2498 olsrv2TibRoutableAddressTopologySetSeqNo 2499 Unsigned32, 2500 olsrv2TibRoutableAddressTopologySetMetricValue 2501 Olsrv2MetricValueCompressedFormTC, 2502 olsrv2TibRoutableAddressTopologySetExpireTime 2503 TimeStamp 2504 } 2506 olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType OBJECT-TYPE 2507 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2508 MAX-ACCESS not-accessible 2509 STATUS current 2510 DESCRIPTION 2511 "The type of the 2512 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, 2513 as defined in the InetAddress MIB module (RFC 4001). 2515 Only the values 'ipv4(1)' and 2516 'ipv6(2)' are supported." 2518 REFERENCE 2519 "RFC XXXX - The Optimized Link State Routing Protocol 2520 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2521 and U. Herberg, March 2013." 2522 ::= { olsrv2TibRoutableAddressTopologySetEntry 1 } 2524 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr OBJECT-TYPE 2525 SYNTAX InetAddress (SIZE(4|16)) 2526 MAX-ACCESS not-accessible 2527 STATUS current 2528 DESCRIPTION 2529 "This is the originator address of a router which can 2530 reach the router with routable address TA_dest_addr 2531 in one hop." 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 ::= { olsrv2TibRoutableAddressTopologySetEntry 2 } 2538 olsrv2TibRoutableAddressTopologySetDestIpAddrType OBJECT-TYPE 2539 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2540 MAX-ACCESS not-accessible 2541 STATUS current 2542 DESCRIPTION 2543 "The type of the olsrv2TibRouterTopologySetToOrigIpAddr, 2544 as defined in the InetAddress MIB module (RFC 4001). 2546 Only the values 'ipv4(1)' and 2547 'ipv6(2)' are supported." 2548 REFERENCE 2549 "RFC XXXX - The Optimized Link State Routing Protocol 2550 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2551 and U. Herberg, March 2013." 2552 ::= { olsrv2TibRoutableAddressTopologySetEntry 3 } 2554 olsrv2TibRoutableAddressTopologySetDestIpAddr OBJECT-TYPE 2555 SYNTAX InetAddress (SIZE(4|16)) 2556 MAX-ACCESS not-accessible 2557 STATUS current 2558 DESCRIPTION 2559 "This is a routable address of a router which can be 2560 reached by the router with originator address 2561 TA_from_orig_addr in one hop. The TA_from_orig_addr 2562 is defined by the tuple 2563 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType 2564 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr)." 2565 REFERENCE 2566 "RFC XXXX - The Optimized Link State Routing Protocol 2567 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2568 and U. Herberg, March 2013." 2569 ::= { olsrv2TibRoutableAddressTopologySetEntry 4 } 2571 olsrv2TibRoutableAddressTopologySetSeqNo OBJECT-TYPE 2572 SYNTAX Unsigned32 (0..65535) 2573 MAX-ACCESS read-only 2574 STATUS current 2575 DESCRIPTION 2576 "This is the greatest ANSN in any TC message 2577 received which originated from the router 2578 with originator address TA_from_orig_addr, 2579 i.e., which contributed to the information 2580 contained in this Tuple. The TA_from_orig_addr 2581 is defined by the tuple 2582 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType 2583 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr)." 2584 REFERENCE 2585 "RFC XXXX - The Optimized Link State Routing Protocol 2586 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2587 and U. Herberg, March 2013." 2588 ::= { olsrv2TibRoutableAddressTopologySetEntry 5 } 2590 olsrv2TibRoutableAddressTopologySetMetricValue OBJECT-TYPE 2591 SYNTAX Olsrv2MetricValueCompressedFormTC 2592 MAX-ACCESS read-only 2593 STATUS current 2594 DESCRIPTION 2595 "This is the neighbor metric from the router 2596 with originator address TA_from_orig_addr (defined 2597 by the tuple 2598 (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType 2599 olsrv2TibRoutableAddressTopologySetFromOrigIpAddr)) 2600 to the router with OLSRv2 interface address TA_dest_addr 2601 (defined by the tuple 2602 (olsrv2TibRoutableAddressTopologySetFromDestIpAddrType 2603 olsrv2TibRoutableAddressTopologySetFromDestIpAddr))." 2604 REFERENCE 2605 "RFC XXXX - The Optimized Link State Routing Protocol 2606 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2607 and U. Herberg, March 2013." 2608 ::= { olsrv2TibRoutableAddressTopologySetEntry 6 } 2610 olsrv2TibRoutableAddressTopologySetExpireTime OBJECT-TYPE 2611 SYNTAX TimeStamp 2612 UNITS "centiseconds" 2613 MAX-ACCESS read-only 2614 STATUS current 2615 DESCRIPTION 2616 "olsrv2TibRoutableAddressTopologySetExpireTime 2617 specifies the value of sysUptime when this entry 2618 SHOULD expire and be removed from the 2619 olsrv2TibRoutableAddressTopologySetTable." 2620 REFERENCE 2621 "RFC XXXX - The Optimized Link State Routing Protocol 2622 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2623 and U. Herberg, March 2013." 2624 ::= { olsrv2TibRoutableAddressTopologySetEntry 7 } 2626 -- 2627 -- Attached Network Set 2628 -- 2630 olsrv2TibAttNetworksSetTable OBJECT-TYPE 2631 SYNTAX SEQUENCE OF Olsrv2TibAttNetworksSetEntry 2632 MAX-ACCESS not-accessible 2633 STATUS current 2634 DESCRIPTION 2635 "A router's Attached Network Set records information 2636 about networks (which may be outside the MANET) 2637 attached to other routers and their routable addresses." 2638 REFERENCE 2639 "RFC XXXX - The Optimized Link State Routing Protocol 2640 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2641 and U. Herberg, March 2013." 2642 ::= { olsrv2StateGroup 10 } 2644 olsrv2TibAttNetworksSetEntry OBJECT-TYPE 2645 SYNTAX Olsrv2TibAttNetworksSetEntry 2646 MAX-ACCESS not-accessible 2647 STATUS current 2648 DESCRIPTION 2649 "It consists of Attached Network Tuples: 2651 (AN_orig_addr 2652 (olsrv2TibAttNetworksSetOrigIpAddrType, 2653 olsrv2TibAttNetworksSetOrigIpAddr), 2654 AN_net_addr 2655 (olsrv2TibAttNetworksSetNetIpAddrType, 2656 olsrv2TibAttNetworksSetNetIpAddr, 2657 olsrv2TibAttNetworksSetNetIpAddrPrefixLen), 2658 AN_seq_number (olsrv2TibAttNetworksSetSeqNo), 2659 AN_dist (olsrv2TibAttNetworksSetDist), 2660 AN_metric (olsrv2TibAttNetworksSetMetricValue), 2661 AN_time (olsrv2TibAttNetworksSetExpireTime) 2662 ) 2664 OLSRv2 (RFC XXXX) defines the rules for managing 2665 entries within this table, e.g., populating 2666 and purging entries. Specific instructions for the 2667 olsrv2TibRoutableAddressTopologySetEntry(s) are found 2668 in Section 10.4 and Section 17 of OLSRv2 (RFC XXXX)." 2669 REFERENCE 2670 "RFC XXXX - The Optimized Link State Routing Protocol 2671 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2672 and U. Herberg, March 2013." 2673 INDEX { olsrv2TibAttNetworksSetOrigIpAddrType, 2674 olsrv2TibAttNetworksSetOrigIpAddr, 2675 olsrv2TibAttNetworksSetNetIpAddrType, 2676 olsrv2TibAttNetworksSetNetIpAddr, 2677 olsrv2TibAttNetworksSetNetIpAddrPrefixLen } 2678 ::= { olsrv2TibAttNetworksSetTable 1 } 2680 Olsrv2TibAttNetworksSetEntry ::= 2681 SEQUENCE { 2682 olsrv2TibAttNetworksSetOrigIpAddrType 2683 InetAddressType, 2684 olsrv2TibAttNetworksSetOrigIpAddr 2685 InetAddress, 2686 olsrv2TibAttNetworksSetNetIpAddrType 2687 InetAddressType, 2688 olsrv2TibAttNetworksSetNetIpAddr 2689 InetAddress, 2690 olsrv2TibAttNetworksSetNetIpAddrPrefixLen 2691 InetAddressPrefixLength, 2692 olsrv2TibAttNetworksSetSeqNo 2693 Unsigned32, 2694 olsrv2TibAttNetworksSetDist 2695 Unsigned32, 2696 olsrv2TibAttNetworksSetMetricValue 2697 Olsrv2MetricValueCompressedFormTC, 2698 olsrv2TibAttNetworksSetExpireTime 2699 TimeStamp 2700 } 2702 olsrv2TibAttNetworksSetOrigIpAddrType OBJECT-TYPE 2703 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2704 MAX-ACCESS not-accessible 2705 STATUS current 2706 DESCRIPTION 2707 "The type of the olsrv2TibAttNetworksSetOrigIpAddr, 2708 as defined in the InetAddress MIB module (RFC4001). 2710 Only the values 'ipv4(1)' and 2711 'ipv6(2)' are supported." 2712 REFERENCE 2713 "RFC XXXX - The Optimized Link State Routing Protocol 2714 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2715 and U. Herberg, March 2013." 2716 ::= { olsrv2TibAttNetworksSetEntry 1 } 2718 olsrv2TibAttNetworksSetOrigIpAddr OBJECT-TYPE 2719 SYNTAX InetAddress (SIZE(4|16)) 2720 MAX-ACCESS not-accessible 2721 STATUS current 2722 DESCRIPTION 2723 "This is the originator address, of type 2724 olsrv2TibAttNetworksSetOrigIpAddrType, of a 2725 router which can act as gateway to the 2726 network with address AN_net_addr. The 2727 AN_net_addr is defined by the tuple 2728 (olsrv2TibAttNetworksSetNetIpAddrType, 2729 olsrv2TibAttNetworksSetNetIpAddr, 2730 olsrv2TibAttNetworksSetNetIpAddrPrefixLen)." 2731 REFERENCE 2732 "RFC XXXX - The Optimized Link State Routing Protocol 2733 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2734 and U. Herberg, March 2013." 2735 ::= { olsrv2TibAttNetworksSetEntry 2 } 2737 olsrv2TibAttNetworksSetNetIpAddrType OBJECT-TYPE 2738 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2739 MAX-ACCESS not-accessible 2740 STATUS current 2741 DESCRIPTION 2742 "The type of the olsrv2TibAttNetworksSetNetIpAddr, 2743 as defined in the InetAddress MIB module (RFC 4001). 2745 Only the values 'ipv4(1)' and 2746 'ipv6(2)' are supported." 2747 REFERENCE 2748 "RFC XXXX - The Optimized Link State Routing Protocol 2749 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2750 and U. Herberg, March 2013." 2751 ::= { olsrv2TibAttNetworksSetEntry 3 } 2753 olsrv2TibAttNetworksSetNetIpAddr OBJECT-TYPE 2754 SYNTAX InetAddress (SIZE(4|16)) 2755 MAX-ACCESS not-accessible 2756 STATUS current 2757 DESCRIPTION 2758 "This is is the network address,of type 2759 olsrv2TibAttNetworksSetNetIpAddrType, of an 2760 attached network, which may be reached via 2761 the router with originator address AN_orig_addr. 2762 The AN_orig_addr is defined by the tuple 2763 (olsrv2TibAttNetworksSetOrigIpAddrType, 2764 olsrv2TibAttNetworksSetOrigIpAddr)." 2765 REFERENCE 2766 "RFC XXXX - The Optimized Link State Routing Protocol 2767 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2768 and U. Herberg, March 2013." 2769 ::= { olsrv2TibAttNetworksSetEntry 4 } 2771 olsrv2TibAttNetworksSetNetIpAddrPrefixLen OBJECT-TYPE 2772 SYNTAX InetAddressPrefixLength 2773 UNITS "bits" 2774 MAX-ACCESS not-accessible 2775 STATUS current 2776 DESCRIPTION 2777 "Indicates the number of leading one bits that form the 2778 mask to be logically ANDed with the destination address 2779 before being compared to the value in the 2780 olsrv2TibAttNetworksSetNetIpAddr field." 2781 REFERENCE 2782 "RFC XXXX - The Optimized Link State Routing Protocol 2783 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2784 and U. Herberg, March 2013." 2785 ::= { olsrv2TibAttNetworksSetEntry 5 } 2787 olsrv2TibAttNetworksSetSeqNo OBJECT-TYPE 2788 SYNTAX Unsigned32 (0..65535) 2789 MAX-ACCESS read-only 2790 STATUS current 2791 DESCRIPTION 2792 "This is the greatest Assigned Neighbor Sequence 2793 Number (ANSN) in any TC message received 2794 which originated from the router 2795 with originator address AN_orig_addr 2796 (i.e., which contributed to the information 2797 contained in this Tuple). The AN_orig_addr 2798 is defined by the tuple 2799 (olsrv2TibAttNetworksSetOrigIpAddrType, 2800 olsrv2TibAttNetworksSetOrigIpAddr). 2802 Sequence numbers are used in the OLSRv2 protocol 2803 for the purpose of discarding 'old' information, 2804 i.e., messages received out of order. However 2805 with a limited number of bits for representing 2806 sequence numbers, wrap-around (that the sequence 2807 number is incremented from the maximum possible 2808 value to zero) will occur. To prevent this from 2809 interfering with the operation of this protocol, 2810 the following MUST be observed when determining 2811 the ordering of sequence numbers. 2813 The term MAXVALUE designates in the following one 2814 more than the largest possible value for a sequence 2815 number. For a 16 bit sequence number (as are those 2816 defined in this specification) MAXVALUE is 65536. 2818 The sequence number S1 is said to be 'greater than' 2819 the sequence number S2 if: 2821 o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR 2823 o S2 > S1 AND S2 - S1 > MAXVALUE/2 2825 When sequence numbers S1 and S2 differ by MAXVALUE/2 2826 their ordering cannot be determined. In this case, 2827 which should not occur, either ordering may be 2828 assumed. 2830 Thus when comparing two messages, it is possible 2831 - even in the presence of wrap-around - to determine 2832 which message contains the most recent information." 2833 REFERENCE 2834 "RFC XXXX - The Optimized Link State Routing Protocol 2835 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2836 and U. Herberg, March 2013." 2837 ::= { olsrv2TibAttNetworksSetEntry 6 } 2839 olsrv2TibAttNetworksSetDist OBJECT-TYPE 2840 SYNTAX Unsigned32 (0..255) 2841 UNITS "hops" 2842 MAX-ACCESS read-only 2843 STATUS current 2844 DESCRIPTION 2845 "The number of hops to the network 2846 with address AN_net_addr from the router with 2847 originator address AN_orig_addr. 2848 The AN_orig_addr is defined by the tuple 2849 (olsrv2TibAttNetworksSetOrigIpAddrType, 2850 olsrv2TibAttNetworksSetOrigIpAddr)." 2851 REFERENCE 2852 "RFC XXXX - The Optimized Link State Routing Protocol 2853 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2854 and U. Herberg, March 2013." 2855 ::= { olsrv2TibAttNetworksSetEntry 7 } 2857 olsrv2TibAttNetworksSetMetricValue OBJECT-TYPE 2858 SYNTAX Olsrv2MetricValueCompressedFormTC 2859 MAX-ACCESS read-only 2860 STATUS current 2861 DESCRIPTION 2862 "The metric of the link from the router with 2863 originator address AN_orig_addr to the attached 2864 network with address AN_net_addr. 2865 The AN_net_addr is defined by the tuple 2866 (olsrv2TibAttNetworksSetNetIpAddrType, 2867 olsrv2TibAttNetworksSetNetIpAddr, 2868 olsrv2TibAttNetworksSetNetIpAddrPrefixLen)." 2869 REFERENCE 2870 "RFC XXXX - The Optimized Link State Routing Protocol 2871 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2872 and U. Herberg, March 2013." 2873 ::= { olsrv2TibAttNetworksSetEntry 9 } 2875 olsrv2TibAttNetworksSetExpireTime OBJECT-TYPE 2876 SYNTAX TimeStamp 2877 UNITS "centiseconds" 2878 MAX-ACCESS read-only 2879 STATUS current 2880 DESCRIPTION 2881 "olsrv2TibAttNetworksSetExpireTime 2882 specifies the value of sysUptime when this 2883 entry SHOULD expire and be removed from the 2884 olsrv2TibAttNetworksSetTable." 2885 REFERENCE 2886 "RFC XXXX - The Optimized Link State Routing Protocol 2887 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2888 and U. Herberg, March 2013." 2889 ::= { olsrv2TibAttNetworksSetEntry 10 } 2891 -- 2892 -- Routing Set 2893 -- 2895 olsrv2TibRoutingSetTable OBJECT-TYPE 2896 SYNTAX SEQUENCE OF Olsrv2TibRoutingSetEntry 2897 MAX-ACCESS not-accessible 2898 STATUS current 2899 DESCRIPTION 2900 "A router's Routing Set records the first hop along a 2901 selected path to each destination for which any such 2902 path is known." 2903 REFERENCE 2904 "RFC XXXX - The Optimized Link State Routing Protocol 2905 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2906 and U. Herberg, March 2013." 2907 ::= { olsrv2StateGroup 11 } 2909 olsrv2TibRoutingSetEntry OBJECT-TYPE 2910 SYNTAX Olsrv2TibRoutingSetEntry 2911 MAX-ACCESS not-accessible 2912 STATUS current 2913 DESCRIPTION 2914 "It consists of Routing Tuples: 2916 (R_dest_addr, R_next_iface_addr, 2917 R_local_iface_addr, R_dist, R_metric)" 2918 REFERENCE 2919 "RFC XXXX - The Optimized Link State Routing Protocol 2920 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2921 and U. Herberg, March 2013." 2922 INDEX { olsrv2TibRoutingSetDestIpAddrType, 2923 olsrv2TibRoutingSetDestIpAddr, 2924 olsrv2TibRoutingSetDestIpAddrPrefixLen } 2925 ::= { olsrv2TibRoutingSetTable 1 } 2927 Olsrv2TibRoutingSetEntry ::= 2928 SEQUENCE { 2929 olsrv2TibRoutingSetDestIpAddrType 2930 InetAddressType, 2931 olsrv2TibRoutingSetDestIpAddr 2932 InetAddress, 2933 olsrv2TibRoutingSetDestIpAddrPrefixLen 2934 InetAddressPrefixLength, 2935 olsrv2TibRoutingSetNextIfIpAddrType 2936 InetAddressType, 2937 olsrv2TibRoutingSetNextIfIpAddr 2938 InetAddress, 2939 olsrv2TibRoutingSetLocalIfIpAddrType 2940 InetAddressType, 2941 olsrv2TibRoutingSetLocalIfIpAddr 2942 InetAddress, 2943 olsrv2TibRoutingSetDist 2944 Unsigned32, 2945 olsrv2TibRoutingSetMetricValue 2946 Olsrv2MetricValueCompressedFormTC 2948 } 2950 olsrv2TibRoutingSetDestIpAddrType OBJECT-TYPE 2951 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 2952 MAX-ACCESS not-accessible 2953 STATUS current 2954 DESCRIPTION 2955 "The type of the olsrv2TibRoutingSetDestIpAddr, 2956 as defined in the InetAddress MIB module (RFC 4001). 2958 Only the values 'ipv4(1)' and 'ipv6(2)' are 2959 supported." 2960 REFERENCE 2961 "RFC XXXX - The Optimized Link State Routing Protocol 2962 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2963 and U. Herberg, March 2013." 2964 ::= { olsrv2TibRoutingSetEntry 1 } 2966 olsrv2TibRoutingSetDestIpAddr OBJECT-TYPE 2967 SYNTAX InetAddress (SIZE(4|16)) 2968 MAX-ACCESS not-accessible 2969 STATUS current 2970 DESCRIPTION 2971 "This is the address of the destination, 2972 either the address of an interface of 2973 a destination router, or the network 2974 address of an attached network." 2975 REFERENCE 2976 "RFC XXXX - The Optimized Link State Routing Protocol 2977 version 2, Clausen, T., Dearlove, C., Jacquet, P. 2978 and U. Herberg, March 2013." 2979 ::= { olsrv2TibRoutingSetEntry 2 } 2981 olsrv2TibRoutingSetDestIpAddrPrefixLen OBJECT-TYPE 2982 SYNTAX InetAddressPrefixLength 2983 UNITS "bits" 2984 MAX-ACCESS not-accessible 2985 STATUS current 2986 DESCRIPTION 2987 "Indicates the number of leading one bits that form the 2988 mask to be logically ANDed with the destination address 2989 before being compared to the value in the 2990 olsrv2TibRoutingSetDestIpAddr field. 2992 Note: This definition needs to be consistent 2993 with the current forwarding table MIB module description. 2994 Specifically, it SHOULD allow for longest prefix 2995 matching of network addresses." 2997 REFERENCE 2998 "RFC XXXX - The Optimized Link State Routing Protocol 2999 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3000 and U. Herberg, March 2013." 3001 ::= { olsrv2TibRoutingSetEntry 3 } 3003 olsrv2TibRoutingSetNextIfIpAddrType OBJECT-TYPE 3004 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 3005 MAX-ACCESS read-only 3006 STATUS current 3007 DESCRIPTION 3008 "The type of the olsrv2TibRoutingSetNextIfIpAddr, 3009 as defined in the InetAddress MIB module (RFC 4001). 3011 Only the values 'ipv4(1)' and 3012 'ipv6(2)' are supported." 3013 REFERENCE 3014 "RFC XXXX - The Optimized Link State Routing Protocol 3015 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3016 and U. Herberg, March 2013." 3017 ::= { olsrv2TibRoutingSetEntry 4 } 3019 olsrv2TibRoutingSetNextIfIpAddr OBJECT-TYPE 3020 SYNTAX InetAddress (SIZE(4|16)) 3021 MAX-ACCESS read-only 3022 STATUS current 3023 DESCRIPTION 3024 "This object is the OLSRv2 interface address of the 3025 next hop on the selected path to the 3026 destination." 3027 REFERENCE 3028 "RFC XXXX - The Optimized Link State Routing Protocol 3029 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3030 and U. Herberg, March 2013." 3031 ::= { olsrv2TibRoutingSetEntry 5 } 3033 olsrv2TibRoutingSetLocalIfIpAddrType OBJECT-TYPE 3034 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 3035 MAX-ACCESS read-only 3036 STATUS current 3037 DESCRIPTION 3038 "The type of the olsrv2TibRoutingSetLocalIfIpAddr 3039 and olsrv2TibRoutingSetNextIfIpAddr, 3040 as defined in the InetAddress MIB module (RFC 4001). 3042 Only the values 'ipv4(1)' and 3043 'ipv6(2)' are supported." 3044 REFERENCE 3045 "RFC XXXX - The Optimized Link State Routing Protocol 3046 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3047 and U. Herberg, March 2013." 3048 ::= { olsrv2TibRoutingSetEntry 6 } 3050 olsrv2TibRoutingSetLocalIfIpAddr OBJECT-TYPE 3051 SYNTAX InetAddress (SIZE(4|16)) 3052 MAX-ACCESS read-only 3053 STATUS current 3054 DESCRIPTION 3055 "This object is the address of the local OLSRv2 3056 interface over which a packet must be 3057 sent to reach the destination by the 3058 selected path." 3059 REFERENCE 3060 "RFC XXXX - The Optimized Link State Routing Protocol 3061 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3062 and U. Herberg, March 2013." 3063 ::= { olsrv2TibRoutingSetEntry 7 } 3065 olsrv2TibRoutingSetDist OBJECT-TYPE 3066 SYNTAX Unsigned32 (0..255) 3067 UNITS "hops" 3068 MAX-ACCESS read-only 3069 STATUS current 3070 DESCRIPTION 3071 "This object is the number of hops on the selected 3072 path to the destination." 3073 REFERENCE 3074 "RFC XXXX - The Optimized Link State Routing Protocol 3075 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3076 and U. Herberg, March 2013." 3077 ::= { olsrv2TibRoutingSetEntry 8 } 3079 olsrv2TibRoutingSetMetricValue OBJECT-TYPE 3080 SYNTAX Olsrv2MetricValueCompressedFormTC 3081 MAX-ACCESS read-only 3082 STATUS current 3083 DESCRIPTION 3084 "This object is the metric of the route 3085 to the destination with address R_dest_addr." 3086 REFERENCE 3087 "RFC XXXX - The Optimized Link State Routing Protocol 3088 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3089 and U. Herberg, March 2013." 3090 ::= { olsrv2TibRoutingSetEntry 9 } 3092 -- 3093 -- OLSRv2 Performance Group 3094 -- 3096 -- 3097 -- Contains objects which help to characterize the 3098 -- performance of the OLSRv2 routing process. 3099 -- 3101 olsrv2PerformanceObjGrp OBJECT IDENTIFIER ::= {olsrv2MIBObjects 3} 3103 -- 3104 -- Objects per local interface 3105 -- 3107 olsrv2InterfacePerfTable OBJECT-TYPE 3108 SYNTAX SEQUENCE OF Olsrv2InterfacePerfEntry 3109 MAX-ACCESS not-accessible 3110 STATUS current 3111 DESCRIPTION 3112 "This table summarizes performance objects that are 3113 measured per each active local OLSRv2 interface. 3114 If the olsrv2InterfaceAdminStatus of the interface 3115 changes to 'disabled' then the row associated with this 3116 interface SHOULD be removed from this table." 3117 REFERENCE 3118 "RFC XXXX - The Optimized Link State Routing Protocol 3119 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3120 and U. Herberg, March 2013." 3121 ::= { olsrv2PerformanceObjGrp 1 } 3123 olsrv2InterfacePerfEntry OBJECT-TYPE 3124 SYNTAX Olsrv2InterfacePerfEntry 3125 MAX-ACCESS not-accessible 3126 STATUS current 3127 DESCRIPTION 3128 "A single entry contains performance counters for 3129 each active local OLSRv2 interface." 3130 AUGMENTS { nhdpInterfacePerfEntry } 3131 ::= { olsrv2InterfacePerfTable 1 } 3133 Olsrv2InterfacePerfEntry ::= 3134 SEQUENCE { 3135 olsrv2IfTcMessageXmits 3136 Counter32, 3137 olsrv2IfTcMessageRecvd 3138 Counter32, 3139 olsrv2IfTcMessageXmitAccumulatedSize 3140 Counter64, 3141 olsrv2IfTcMessageRecvdAccumulatedSize 3142 Counter64, 3143 olsrv2IfTcMessageTriggeredXmits 3144 Counter32, 3145 olsrv2IfTcMessagePeriodicXmits 3146 Counter32, 3147 olsrv2IfTcMessageForwardedXmits 3148 Counter32, 3149 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount 3150 Counter32 3151 } 3153 olsrv2IfTcMessageXmits OBJECT-TYPE 3154 SYNTAX Counter32 3155 UNITS "messages" 3156 MAX-ACCESS read-only 3157 STATUS current 3158 DESCRIPTION 3159 "A counter is incremented each time a TC 3160 message has been transmitted on that interface." 3161 ::= { olsrv2InterfacePerfEntry 1 } 3163 olsrv2IfTcMessageRecvd OBJECT-TYPE 3164 SYNTAX Counter32 3165 UNITS "messages" 3166 MAX-ACCESS read-only 3167 STATUS current 3168 DESCRIPTION 3169 "A counter is incremented each time a 3170 TC message has been received on that interface. 3171 This excludes all messages that are ignored due to 3172 OLSRv2 protocol procedures." 3173 ::= { olsrv2InterfacePerfEntry 2 } 3175 olsrv2IfTcMessageXmitAccumulatedSize OBJECT-TYPE 3176 SYNTAX Counter64 3177 UNITS "octets" 3178 MAX-ACCESS read-only 3179 STATUS current 3180 DESCRIPTION 3181 "A counter is incremented by the number of octets in 3182 a TC message each time a TC message has been sent." 3183 ::= { olsrv2InterfacePerfEntry 3 } 3185 olsrv2IfTcMessageRecvdAccumulatedSize OBJECT-TYPE 3186 SYNTAX Counter64 3187 UNITS "octets" 3188 MAX-ACCESS read-only 3189 STATUS current 3190 DESCRIPTION 3191 "A counter is incremented by the number of octets in 3192 a TC message each time a TC message has been received. 3193 This excludes all messages that are ignored due to 3194 OLSRv2 protocol procedures." 3195 ::= { olsrv2InterfacePerfEntry 4 } 3197 olsrv2IfTcMessageTriggeredXmits OBJECT-TYPE 3198 SYNTAX Counter32 3199 UNITS "messages" 3200 MAX-ACCESS read-only 3201 STATUS current 3202 DESCRIPTION 3203 "A counter is incremented each time a triggered 3204 TC message has been sent." 3205 ::= { olsrv2InterfacePerfEntry 5 } 3207 olsrv2IfTcMessagePeriodicXmits OBJECT-TYPE 3208 SYNTAX Counter32 3209 UNITS "messages" 3210 MAX-ACCESS read-only 3211 STATUS current 3212 DESCRIPTION 3213 "A counter is incremented each time a periodic 3214 TC message has been sent." 3215 ::= { olsrv2InterfacePerfEntry 6 } 3217 olsrv2IfTcMessageForwardedXmits OBJECT-TYPE 3218 SYNTAX Counter32 3219 UNITS "messages" 3220 MAX-ACCESS read-only 3221 STATUS current 3222 DESCRIPTION 3223 "A counter is incremented each time a 3224 TC message has been forwarded." 3225 ::= { olsrv2InterfacePerfEntry 7 } 3227 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount OBJECT-TYPE 3228 SYNTAX Counter32 3229 UNITS "advertised MPR selectors" 3230 MAX-ACCESS read-only 3231 STATUS current 3232 DESCRIPTION 3233 "A counter is incremented by the number of advertised 3234 MPR selectors in a TC each time a TC 3235 message has been sent." 3237 ::= { olsrv2InterfacePerfEntry 8 } 3239 -- 3240 -- Objects concerning the Routing set 3241 -- 3243 olsrv2RoutingSetRecalculationCount OBJECT-TYPE 3244 SYNTAX Counter32 3245 UNITS "recalculations" 3246 MAX-ACCESS read-only 3247 STATUS current 3248 DESCRIPTION 3249 "This counter increments each time the Routing Set has 3250 been recalculated." 3251 ::= { olsrv2PerformanceObjGrp 2 } 3253 -- 3254 -- Objects concerning the MPR set 3255 -- 3257 olsrv2MPRSetRecalculationCount OBJECT-TYPE 3258 SYNTAX Counter32 3259 UNITS "recalculations" 3260 MAX-ACCESS read-only 3261 STATUS current 3262 DESCRIPTION 3263 "This counter increments each time the MPRs 3264 of this router have been recalculated for 3265 any of its interfaces." 3266 ::= { olsrv2PerformanceObjGrp 3 } 3268 -- 3269 -- Notifications 3270 -- 3272 olsrv2NotificationsObjects OBJECT IDENTIFIER ::= 3273 { olsrv2MIBNotifications 0 } 3274 olsrv2NotificationsControl OBJECT IDENTIFIER ::= 3275 { olsrv2MIBNotifications 1 } 3276 olsrv2NotificationsStates OBJECT IDENTIFIER ::= 3277 { olsrv2MIBNotifications 2 } 3279 -- olsrv2NotificationsObjects 3281 olsrv2RouterStatusChange NOTIFICATION-TYPE 3282 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3283 -- the originator of 3284 -- the notification. 3285 olsrv2OrigIpAddr, -- The originator of 3286 -- the notification. 3287 olsrv2AdminStatus -- The new state. 3288 } 3289 STATUS current 3290 DESCRIPTION 3291 "olsrv2RouterStatusChange is a notification generated 3292 when the OLSRv2 router changes it status. 3293 The router status is maintained in the 3294 olsrv2AdminStatus object." 3295 ::= { olsrv2NotificationsObjects 1 } 3297 olsrv2OrigIpAddrChange NOTIFICATION-TYPE 3298 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3299 -- the originator of 3300 -- the notification. 3301 olsrv2OrigIpAddr, -- The originator of 3302 -- the notification. 3303 olsrv2PreviousOrigIpAddrType, -- The address 3304 -- type of previous 3305 -- address of 3306 -- the originator of 3307 -- the notification. 3308 olsrv2PreviousOrigIpAddr -- The previous 3309 -- address of the 3310 -- originator of 3311 -- the notification. 3312 } 3313 STATUS current 3314 DESCRIPTION 3315 "olsrv2OrigIpAddrChange is a notification generated when 3316 the OLSRv2 router changes it originator IP address. 3317 The notification includes the new and the previous 3318 originator IP address of the OLSRv2 router." 3319 ::= { olsrv2NotificationsObjects 2 } 3321 olsrv2RoutingSetRecalculationCountChange NOTIFICATION-TYPE 3322 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3323 -- the originator of 3324 -- the notification. 3325 olsrv2OrigIpAddr, -- The originator of 3326 -- the notification. 3328 olsrv2RoutingSetRecalculationCount -- Number 3329 -- of the 3330 -- routing set 3331 -- recalculations. 3332 } 3333 STATUS current 3334 DESCRIPTION 3335 "The olsrv2RoutingSetRecalculationCountChange 3336 notification is generated when a significant number of 3337 routing set recalculations have occurred in a short time. 3338 This notification SHOULD be generated no more than once 3339 per olsrv2RoutingSetRecalculationCountWindow. 3340 The network administrator SHOULD select 3341 appropriate values for 'significant number of 3342 routing set recalculations' and 'short time' through 3343 the settings of the 3344 olsrv2RoutingSetRecalculationCountThreshold 3345 and olsrv2RoutingSetRecalculationCountWindow objects." 3346 ::= { olsrv2NotificationsObjects 3 } 3348 olsrv2MPRSetRecalculationCountChange NOTIFICATION-TYPE 3349 OBJECTS { olsrv2OrigIpAddrType, -- The address type of 3350 -- the originator of 3351 -- the notification. 3352 olsrv2OrigIpAddr, -- The originator of 3353 -- the notification. 3354 olsrv2MPRSetRecalculationCount -- Number of 3355 -- MPR set 3356 -- recalculations. 3357 } 3358 STATUS current 3359 DESCRIPTION 3360 "The olsrv2MPRSetRecalculationCountChange 3361 notification is generated when a significant 3362 number of MPR set recalculations occur in 3363 a short period of time. This notification 3364 SHOULD be generated no more than once 3365 per olsrv2MPRSetRecalculationCountWindow. 3366 The network administrator SHOULD select 3367 appropriate values for 'significant number of 3368 MPR set recalculations' and 'short period of 3369 time' through the settings of the 3370 olsrv2MPRSetRecalculationCountThreshold and 3371 olsrv2MPRSetRecalculationCountWindow objects." 3372 ::= { olsrv2NotificationsObjects 4 } 3374 -- olsrv2NotificationsControl 3375 olsrv2RoutingSetRecalculationCountThreshold OBJECT-TYPE 3376 SYNTAX Integer32 (0..255) 3377 UNITS "recalculations" 3378 MAX-ACCESS read-write 3379 STATUS current 3380 DESCRIPTION 3381 "A threshold value for the 3382 olsrv2RoutingSetRecalculationCount object. 3383 If the number of occurrences exceeds this 3384 threshold within the previous 3385 olsrv2RoutingSetRecalculationCountWindow, 3386 then the olsrv2RoutingSetRecalculationCountChange 3387 notification is to be generated. 3389 It is RECOMMENDED that the value of this 3390 threshold be set to at least 20 and higher 3391 in dense topologies with frequent expected 3392 topology changes." 3393 DEFVAL { 20 } 3394 ::= { olsrv2NotificationsControl 1 } 3396 olsrv2RoutingSetRecalculationCountWindow OBJECT-TYPE 3397 SYNTAX TimeTicks 3398 MAX-ACCESS read-write 3399 STATUS current 3400 DESCRIPTION 3401 "This object is used to determine whether to generate 3402 an olsrv2RoutingSetRecalculationCountChange notification. 3403 This object represents an interval from the present moment, 3404 extending into the past, expressed in hundredths of 3405 a second. If the change in the value of the 3406 olsrv2RoutingSetRecalculationCount object during 3407 this interval has exceeded the value of 3408 olsrv2RoutingSetRecalculationCountThreshold, then 3409 an olsrv2RoutingSetRecalculationCountChange notification 3410 is generated. 3412 It is RECOMMENDED that the value for this 3413 window be set to at least 5 times the 3414 nhdpHelloInterval (whose default value is 3415 2 seconds." 3416 DEFVAL { 1000 } 3417 ::= { olsrv2NotificationsControl 2 } 3419 olsrv2MPRSetRecalculationCountThreshold OBJECT-TYPE 3420 SYNTAX Integer32 (0..255) 3421 UNITS "recalculations" 3422 MAX-ACCESS read-write 3423 STATUS current 3424 DESCRIPTION 3425 "A threshold value for the 3426 olsrv2MPRSetRecalculationCount object. 3427 If the number of occurrences exceeds this 3428 threshold within the previous 3429 olsrv2MPRSetRecalculationCountWindow, 3430 then the 3431 olsrv2MPRSetRecalculationCountChange 3432 notification is to be generated. 3434 It is RECOMMENDED that the value of this 3435 threshold be set to at least 20 and higher 3436 in dense topologies with frequent expected 3437 topology changes." 3438 DEFVAL { 20 } 3439 ::= { olsrv2NotificationsControl 3 } 3441 olsrv2MPRSetRecalculationCountWindow OBJECT-TYPE 3442 SYNTAX TimeTicks 3443 MAX-ACCESS read-write 3444 STATUS current 3445 DESCRIPTION 3446 "This object is used to determine whether to generate 3447 an olsrv2MPRSetRecalculationCountChange notification. 3448 This object represents an interval from the present moment, 3449 extending into the past, expressed in hundredths of 3450 a second. If the change in the value of the 3451 olsrv2MPRSetRecalculationCount object during 3452 that interval has exceeded the value of 3453 olsrv2MPRSetRecalculationCountThreshold, then the 3454 an olsrv2MPRSetRecalculationCountChange notification 3455 is generated. 3457 It is RECOMMENDED that the value for this 3458 window be set to at least 5 times the 3459 nhdpHelloInterval." 3460 DEFVAL { 1000 } 3461 ::= { olsrv2NotificationsControl 4 } 3463 olsrv2PreviousOrigIpAddrType OBJECT-TYPE 3464 SYNTAX InetAddressType { ipv4(1) , ipv6(2) } 3465 MAX-ACCESS read-only 3466 STATUS current 3467 DESCRIPTION 3468 "The type of the olsrv2PreviousOrigIpAddr, 3469 as defined in the InetAddress MIB module (RFC 4001). 3471 Only the values 'ipv4(1)' and 3472 'ipv6(2)' are supported. 3474 This object MUST have the same persistence 3475 characteristics as olsrv2PreviousOrigIpAddr." 3476 REFERENCE 3477 "RFC XXXX - The Optimized Link State Routing Protocol 3478 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3479 and U. Herberg, March 2013." 3480 ::= { olsrv2NotificationsStates 1 } 3482 olsrv2PreviousOrigIpAddr OBJECT-TYPE 3483 SYNTAX InetAddress (SIZE(4|16)) 3484 MAX-ACCESS read-only 3485 STATUS current 3486 DESCRIPTION 3487 "The previous origination IP address 3488 of this OLSRv2 router. 3490 This object SHOULD be updated each time 3491 the olsrv2OrigIpAddr is modified. 3493 This object is persistent and when written 3494 the entity SHOULD save the change to 3495 non-volatile storage." 3496 REFERENCE 3497 "RFC XXXX - The Optimized Link State Routing Protocol 3498 version 2, Clausen, T., Dearlove, C., Jacquet, P. 3499 and U. Herberg, March 2013." 3500 ::= { olsrv2NotificationsStates 2 } 3502 -- 3503 -- Compliance Statements 3504 -- 3506 olsrv2Compliances OBJECT IDENTIFIER ::= { olsrv2MIBConformance 1 } 3507 olsrv2MIBGroups OBJECT IDENTIFIER ::= { olsrv2MIBConformance 2 } 3509 olsrv2BasicCompliance MODULE-COMPLIANCE 3510 STATUS current 3511 DESCRIPTION 3512 "The basic implementation requirements for 3513 managed network entities that implement 3514 the OLSRv2 routing process." 3515 MODULE -- this module 3516 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup } 3518 ::= { olsrv2Compliances 1 } 3520 olsrv2FullCompliance MODULE-COMPLIANCE 3521 STATUS current 3522 DESCRIPTION 3523 "The full implementation requirements for 3524 managed network entities that implement 3525 the OLSRv2 routing process." 3526 MODULE -- this module 3527 MANDATORY-GROUPS { olsrv2ConfigObjectsGroup, 3528 olsrv2StateObjectsGroup, 3529 olsrv2PerfObjectsGroup, 3530 olsrv2NotificationsObjectsGroup, 3531 olsrv2NotificationsGroup } 3532 ::= { olsrv2Compliances 2 } 3534 -- 3535 -- Units of Conformance 3536 -- 3538 olsrv2ConfigObjectsGroup OBJECT-GROUP 3539 OBJECTS { 3540 olsrv2AdminStatus, 3541 olsrv2InterfaceAdminStatus, 3542 olsrv2OrigIpAddrType, 3543 olsrv2OrigIpAddr, 3544 olsrv2OHoldTime, 3545 olsrv2TcInterval, 3546 olsrv2TcMinInterval, 3547 olsrv2THoldTime, 3548 olsrv2AHoldTime, 3549 olsrv2RxHoldTime, 3550 olsrv2PHoldTime, 3551 olsrv2FHoldTime, 3552 olsrv2TpMaxJitter, 3553 olsrv2TtMaxJitter, 3554 olsrv2FMaxJitter, 3555 olsrv2TcHopLimit, 3556 olsrv2WillFlooding, 3557 olsrv2WillRouting, 3558 olsrv2LinkMetricType 3559 } 3560 STATUS current 3561 DESCRIPTION 3562 "Objects to permit configuration of OLSRv2. 3563 All of these SHOULD be backed by non-volatile 3564 storage." 3565 ::= { olsrv2MIBGroups 1 } 3566 olsrv2StateObjectsGroup OBJECT-GROUP 3567 OBJECTS { 3568 olsrv2LibOrigSetExpireTime, 3569 olsrv2LibLocAttNetSetDistance, 3570 olsrv2LibLocAttNetSetMetricValue, 3571 olsrv2IibLinkSetInMetricValue, 3572 olsrv2IibLinkSetOutMetricValue, 3573 olsrv2IibLinkSetMprSelector, 3574 olsrv2Iib2HopSetInMetricValue, 3575 olsrv2Iib2HopSetOutMetricValue, 3576 olsrv2NibNeighborSetNOrigIpAddrType, 3577 olsrv2NibNeighborSetNOrigIpAddr, 3578 olsrv2NibNeighborSetNInMetricValue, 3579 olsrv2NibNeighborSetNOutMetricValue, 3580 olsrv2NibNeighborSetNWillFlooding, 3581 olsrv2NibNeighborSetNWillRouting, 3582 olsrv2NibNeighborSetNFloodingMpr, 3583 olsrv2NibNeighborSetNRoutingMpr, 3584 olsrv2NibNeighborSetNMprSelector, 3585 olsrv2NibNeighborSetNAdvertised, 3586 olsrv2NibNeighborSetTableAnsn, 3587 olsrv2TibAdRemoteRouterSetMaxSeqNo, 3588 olsrv2TibRouterTopologySetSeqNo, 3589 olsrv2TibRouterTopologySetMetricValue, 3590 olsrv2TibRoutableAddressTopologySetExpireTime, 3591 olsrv2TibRoutableAddressTopologySetSeqNo, 3592 olsrv2TibRoutableAddressTopologySetMetricValue, 3593 olsrv2TibAttNetworksSetSeqNo, 3594 olsrv2TibAttNetworksSetDist, 3595 olsrv2TibAttNetworksSetMetricValue, 3596 olsrv2TibAttNetworksSetExpireTime, 3597 olsrv2TibRoutingSetNextIfIpAddrType, 3598 olsrv2TibRoutingSetNextIfIpAddr, 3599 olsrv2TibRoutingSetLocalIfIpAddrType, 3600 olsrv2TibRoutingSetLocalIfIpAddr, 3601 olsrv2TibRoutingSetDist, 3602 olsrv2TibRoutingSetMetricValue 3603 } 3604 STATUS current 3605 DESCRIPTION 3606 "Objects to permit monitoring of OLSRv2 state." 3607 ::= { olsrv2MIBGroups 2 } 3609 olsrv2PerfObjectsGroup OBJECT-GROUP 3610 OBJECTS { 3611 olsrv2IfTcMessageXmits, 3612 olsrv2IfTcMessageRecvd, 3613 olsrv2IfTcMessageXmitAccumulatedSize, 3614 olsrv2IfTcMessageRecvdAccumulatedSize, 3615 olsrv2IfTcMessageTriggeredXmits, 3616 olsrv2IfTcMessagePeriodicXmits, 3617 olsrv2IfTcMessageForwardedXmits, 3618 olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount, 3619 olsrv2RoutingSetRecalculationCount, 3620 olsrv2MPRSetRecalculationCount 3621 } 3622 STATUS current 3623 DESCRIPTION 3624 "Objects to support monitoring of OLSRv2 performance." 3625 ::= { olsrv2MIBGroups 3 } 3627 olsrv2NotificationsObjectsGroup OBJECT-GROUP 3628 OBJECTS { 3629 olsrv2RoutingSetRecalculationCountThreshold, 3630 olsrv2RoutingSetRecalculationCountWindow, 3631 olsrv2MPRSetRecalculationCountThreshold, 3632 olsrv2MPRSetRecalculationCountWindow, 3633 olsrv2PreviousOrigIpAddrType, 3634 olsrv2PreviousOrigIpAddr 3635 } 3636 STATUS current 3637 DESCRIPTION 3638 "Objects to support the notification types in the 3639 olsrv2NotificationsGroup. Some of these appear in 3640 notification payloads, others serve to control 3641 notification generation." 3642 ::= { olsrv2MIBGroups 4 } 3644 olsrv2NotificationsGroup NOTIFICATION-GROUP 3645 NOTIFICATIONS { 3646 olsrv2RouterStatusChange, 3647 olsrv2OrigIpAddrChange, 3648 olsrv2RoutingSetRecalculationCountChange, 3649 olsrv2MPRSetRecalculationCountChange 3650 } 3651 STATUS current 3652 DESCRIPTION 3653 "Notification types to support management of OLSRv2." 3654 ::= { olsrv2MIBGroups 5 } 3656 END 3657 8. Security Considerations 3659 This MIB module defines objects for the configuration, monitoring and 3660 notification of the Optimized Link State Routing protocol version 2 3661 [OLSRv2]. OLSRv2 allows routers to acquire topological information 3662 of the routing domain by virtue of exchanging TC message, to 3663 calculate shortest paths to each destination router in the routing 3664 domain, to select relays for network-wide transmissions etc. 3666 There are a number of management objects defined in this MIB module 3667 with a MAX-ACCESS clause of read-write and/or read-create. Such 3668 objects may be considered sensitive or vulnerable in some network 3669 environments. The support for SET operations in a non-secure 3670 environment without proper protection can have a negative effect on 3671 network operations. These are the tables and objects and their 3672 sensitivity/vulnerability: 3674 o olsrv2TcInterval, olsrv2TcMinInterval - these writable objects 3675 control the rate at which TC messages are sent. If set at too 3676 high a rate, this could represent a form of DOS attack by 3677 overloading interface resources. If set low, OLSRv2 may not 3678 converge fast enough to provide accurate routes to all 3679 destinations in the routing domain. 3681 o olsrv2TcHopLimit - defines the hop limit for TC messages. If set 3682 too low, messages will not be forwarded beyond the defined scope, 3683 and thus routers further away from the message originator will not 3684 be able to construct appropriate topology graphs. 3686 o olsrv2OHoldTime, olsrv2THoldTime, olsrv2AHoldTime, 3687 olsrv2RxHoldTime, olsrv2PHoldTime, olsrv2FHoldTime - define hold 3688 times for tuples of different Information Bases of OLSRv2. If set 3689 too low, information will expire quickly, and may this harm a 3690 correct operation of the routing protocol. 3692 o olsrv2WillFlooding and olsrv2WillRouting - define the willingness 3693 of this router to become MPR. If this is set to WILL_NEVER (0), 3694 the managed router will not forward any TC messages, nor accept a 3695 selection to become MPR by neighboring routers. If set to 3696 WILL_ALWAYS (15), the router will be preferred by neighbors during 3697 MPR selection, and may thus attract more traffic. 3699 o olsrv2TpMaxJitter, olsrv2TtMaxJitter, olsrv2FMaxJitter - define 3700 jitter values for TC message transmission and forwarding. If set 3701 too low, control traffic may get lost if the channel is lossy. 3703 o olsrv2LinkMetricType - defines the type of the link metric that a 3704 router uses (e.g., ETX or hop-count). Whenever this value 3705 changes, all link metric information recorded by the router is 3706 invalid, causing a reset of information acquired from other 3707 routers in the MANET. Moreover, if olsrv2LinkMetricType on a 3708 router is set to a value that is not known to other routers in the 3709 MANET, these routers will not be able to establish routes to that 3710 router or transiting that router. Existing routes to the router 3711 with a olsrv2LinkMetricType unknown to other routers in the MANET 3712 will be removed. 3714 Some of the readable objects in this MIB module (i.e., objects with a 3715 MAX-ACCESS other than not-accessible) may be considered sensitive or 3716 vulnerable in some network environments. It is thus important to 3717 control even GET and/or NOTIFY access to these objects and possibly 3718 to even encrypt the values of these objects when sending them over 3719 the network via SNMP. These are the tables and objects and their 3720 sensitivity/vulnerability: 3722 o olsrv2TibRouterTopologySetTable - The contains information on the 3723 topology of the MANET, specifically the IP address of the routers 3724 in the MANET (as identified by 3725 olsrv2TibRouterTopologySetFromOrigIpAddr and 3726 olsrv2TibRouterTopologySetToOrigIpAddr objects). This information 3727 provides an adversary broad information on the members of the 3728 MANET, located within this single table. This information can be 3729 used to expedite attacks on the other members of the MANET without 3730 having to go through a laborious discovery process on their own. 3732 Some of the Tables in this MIB AUGMENT Tables defined in NHDP-MIB 3733 [RFC6779]. Hence, care must be taken in configuring access control 3734 here in order make sure that the permitted permissions granted for 3735 the AUGMENT-ing Tables here are consistent with the access controls 3736 permitted within the NHDP-MIB. The below list identifies the 3737 AUGMENT-ing Tables and their NHDP-MIB counterparts. It is recommend 3738 that access control policies for these Table pairs are consistently 3739 set. 3741 o The olsrv2InterfaceTable AUGMENTs the nhdpInterfaceTable. 3743 o The olsrv2IibLinkSetTable AUGMENTs the nhdpIibLinkSetTable. 3745 o The olsrv2Iib2HopSetTable AUGMENTs the nhdpIib2HopSetTable. 3747 o The olsrv2NibNeighborSetTable AUGMENTs the 3748 nhdpNibNeighborSetTable. 3750 o The olsrv2InterfacePerfTable AUGMENTs the nhdpInterfacePerfTable. 3752 MANET technology is often deployed to support communications of 3753 emergency services or military tactical applications. In these 3754 applications, it is imperative to maintain the proper operation of 3755 the communications network and to protect sensitive information 3756 related to its operation. Therefore, when implementing these 3757 capabilities, the full use of SNMPv3 cryptographic mechanisms for 3758 authentication and privacy is RECOMMENDED. 3760 SNMP versions prior to SNMPv3 did not include adequate security. 3761 Even if the network itself is secure (for example by using IPsec), 3762 there is no control as to who on the secure network is allowed to 3763 access and GET/SET (read/change/create/delete) the objects in this 3764 MIB module. 3766 Implementations SHOULD provide the security features described by the 3767 SNMPv3 framework (see [RFC3410]), and implementations claiming 3768 compliance to the SNMPv3 standard MUST include full support for 3769 authentication and privacy via the User-based Security Model (USM) 3770 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 3771 MAY also provide support for the Transport Security Model (TSM) 3772 [RFC5591] in combination with a secure transport such as SSH 3773 [RFC5592] or TLS/DTLS [RFC6353]. 3775 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3776 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3777 enable cryptographic security. It is then a customer/operator 3778 responsibility to ensure that the SNMP entity giving access to an 3779 instance of this MIB module is properly configured to give access to 3780 the objects only to those principals (users) that have legitimate 3781 rights to indeed GET or SET (change/create/delete) them. 3783 9. Applicability Statement 3785 This document describes objects for configuring parameters of the 3786 Optimized Link State Routing version 2 (OLSRv2) Protocol [OLSRv2] 3787 process on a router. This MIB module, denoted OLSRv2-MIB, also 3788 reports state, performance information and notifications. The OLSRv2 3789 protocol relies upon information gathered via the Neighborhood 3790 Discovery Protocol [RFC6130] in order to perform its operations. The 3791 NHDP protocol is managed via the NHDP-MIB [RFC6779]. 3793 MANET deployments can greatly differ in aspects of dynamics of the 3794 topology, capacity and loss rates of underlying channels, traffic 3795 flow directions, memory and CPU capacity of routers etc. SNMP and 3796 therefore this MIB module are only applicable for a subset of MANET 3797 deployments, in particular deployments: 3799 o In which routers have enough memory and CPU resources to run SNMP 3800 and expose the MIB module. 3802 o Where a network management station (NMS) is defined to which 3803 notifications are generated, and from which routers can be 3804 managed. 3806 o Where this NMS is reachable from routers in the MANET most of the 3807 time (as notifications to the NMS and management information from 3808 the NMS to the router will be lost when connectivity is 3809 temporarily lost). This requires that the topology of the MANET 3810 is only moderately dynamic. 3812 o Where the underlying wireless channel supports enough bandwidth to 3813 run SNMP, and where loss rates of the channel are not exhaustive. 3815 Certain MANET deployments, such as community networks with non-mobile 3816 routers, dynamic topology because of changing link quality, and a 3817 pre-defined gateway (that could also serve as NMS), are examples of 3818 networks applicable for this MIB module. Other, more constrained 3819 deployments of MANETs may not be able to run SNMP and require 3820 different management protocols. 3822 Some level of configuration, i.e., read-write objects, is desirable 3823 for OLSRv2 deployments. Topology related configuration such as the 3824 ability to enable OLSRv2 on new interfaces or initially configure 3825 OLSRv2 on a router's interfaces through the 3826 olsrv2InterfaceAdminStatus object is critical to initial system 3827 startup. The OLSRv2 protocol allows for some level of performance 3828 tuning through various protocol parameters and this MIB module allows 3829 for configuration of those protocol parameters through read-write 3830 objects such as the olsrv2TcHopLimit or the olsrv2FMaxJitter. Other 3831 read-write objects allow for the control of Notification behavior 3832 through this MIB module, e.g., the 3833 olsrv2RoutingSetRecalculationCountThreshold object. A fuller 3834 discussion of MANET network management applicability is to be 3835 provided elsewhere [USE-CASES]. 3837 10. IANA Considerations 3839 The RFC editor should remove the specification of the 3840 IANAolsrv2LinkMetricType-MIB found in Appendix A upon publication of 3841 the OLSRv2-MIB. Further, IANA should take over the 3842 IANAolsrv2LinkMetricType-MIB and keep it synchronized with the 3843 registry identified below within the IANAolsrv2LinkMetricType 3844 TEXTUAL-CONVENTION. 3846 The MIB module in this document uses the following IANA-assigned 3847 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 3849 Descriptor OBJECT IDENTIFIER value 3850 ---------- ----------------------- 3851 OLSRv2-MIB { mib-2 ZZZZ } 3852 IANA EDITOR NOTE: please assign ZZZZ 3854 11. Acknowledgements 3856 The authors would like to thank Randy Presuhn, Benoit Claise, Adrian 3857 Farrel, as well as the entire MANET WG for reviews of this document. 3859 This MIB document uses the template authored by D. Harrington which 3860 is based on contributions from the MIB Doctors, especially Juergen 3861 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 3863 12. References 3865 12.1. Normative References 3867 [OLSRv2] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg, 3868 "The Optimized Link State Routing Protocol version 2", 3869 draft-ietf-manet-olsrv2-19 (work in progress), 3870 March 2013. 3872 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3873 Requirement Levels", BCP 14, RFC 2119, March 1997. 3875 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3876 Schoenwaelder, Ed., "Structure of Management 3877 Information Version 2 (SMIv2)", STD 58, RFC 2578, 3878 April 1999. 3880 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3881 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3882 STD 58, RFC 2579, April 1999. 3884 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3885 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3886 April 1999. 3888 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3889 MIB", RFC 2863, June 2000. 3891 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 3892 Model (USM) for version 3 of the Simple Network 3893 Management Protocol (SNMPv3)", December 2002. 3895 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3896 Simple Network Management Protocol (SNMP)", STD 62, 3897 RFC 3418, December 2002. 3899 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 3900 Advanced Encryption Standard (AES) Cipher Algorithm in 3901 the SNMP User-based Security Model", June 2004. 3903 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 3904 Schoenwaelder, "Textual Conventions for Internet 3905 Network Addresses", RFC 4001, February 2005. 3907 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security 3908 Model for the Simple Network Management Protocol 3909 (SNMP)", June 2009. 3911 [RFC5592] Harrington, D., Saloway, J., and W. Hardaker, "Secure 3912 Shell Transport Model for the Simple Network 3913 Management Protocol (SNMP)", June 2009. 3915 [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc 3916 Network (MANET) Neighborhood Discovery Protocol 3917 (NHDP)", RFC 6130, April 2011. 3919 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 3920 Model for the Simple Network Management Protocol 3921 (SNMP)", July 2011. 3923 [RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of 3924 Managed Objects for the Neighborhood Discovery 3925 Protocol", RFC 6779, May 2012. 3927 12.2. Informative References 3929 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3930 "Introduction and Applicability Statements for 3931 Internet-Standard Management Framework", RFC 3410, 3932 December 2002. 3934 [REPORT-MIB] Cole, R., Macker, J., and A. Bierman, "Definition of 3935 Managed Objects for Performance Reporting", 3936 draft-ietf-manet-report-mib-03 (work in progress), 3937 November 2012. 3939 [USE-CASES] Nguyen, J., Cole, R., Herberg, U., Yi, J., and J. Dean, 3940 "Network Management of Mobile Ad hoc Networks (MANET): 3941 Architecture, Use Cases, and Applicability", 3942 draft-nguyen-manet-management-00 (work in progress), 3943 February 2013. 3945 Appendix A. Appendix A: 3947 This appendix contains the IANAolsrv2LinkMetricType-MIB module 3948 defined by this specification below. The RFC editor should remove 3949 this specification of the IANAolsrv2LinkMetricType-MIB upon 3950 publication of the OLSRv2-MIB. Further, IANA should take over the 3951 IANAolsrv2LinkMetricType-MIB and to keep it synchronized with the 3952 registry identified below within the IANAolsrv2LinkMetricType 3953 TEXTUAL-CONVENTION. 3955 IANAolsrv2LinkMetricType-MIB DEFINITIONS ::= BEGIN 3957 IMPORTS 3958 MODULE-IDENTITY, mib-2 3959 FROM SNMPv2-SMI 3960 TEXTUAL-CONVENTION 3961 FROM SNMPv2-TC; 3963 ianaolsrv2LinkMetricType MODULE-IDENTITY 3964 LAST-UPDATED "201306240000Z" -- June 24, 2013 3965 ORGANIZATION "IANA" 3966 CONTACT-INFO "Internet Assigned Numbers Authority 3968 Postal: ICANN 3969 4676 Admiralty Way, Suite 330 3970 Marina del Rey, CA 90292 3972 Tel: +1 310 823 9358 3973 E-Mail: iana@iana.org" 3974 DESCRIPTION "This MIB module defines the 3975 IANAolsrv2LinkMetricType Textual 3976 Convention, and thus the enumerated values of 3977 the olsrv2LinkMetricType object defined in 3978 the OLSRv2-MIB." 3979 REVISION "201306240000Z" -- June 24, 2013 3980 DESCRIPTION "Initial version of this MIB as published in 3981 RFC KKKK." 3983 ::= { mib-2 kkkk } 3985 IANAolsrv2LinkMetricTypeTC ::= TEXTUAL-CONVENTION 3986 STATUS current 3987 DESCRIPTION 3988 "This data type is used as the syntax of the 3989 olsrv2LinkMetricType object in the definition 3990 of the OLSRv2-MIB module. 3992 The olsrv2LinkMetricType corresponds to 3993 LINK_METRIC_TYPE of OLSRv2 (RFC XXXX). 3994 OLSRv2 uses bidirectional additive link metrics 3995 to determine shortest distance routes (i.e., 3996 routes with smallest total of link metric values). 3998 OLSRv2 has established a registry for the LINK_METRIC_TYPEs 3999 (denoted 'LINK_METRIC Address Block TLV Type Extensions'): 4000 http://www.iana.org/assignments/manet-parameters/ 4001 manet-parameters.xml# 4002 link-metric-address-block-tlv-type-extension 4004 This is done in Section 24.5 in OLSRv2 (RFC XXXX). 4005 The LINK_METRIC_TYPE (which has as corresponding 4006 object in the MIB module olsrv2LinkMetricType) 4007 corresponds to the type extension of 4008 the LINK_METRIC TLV that is set up in the 4009 'LINK_METRIC Address Block TLV Type Extensions' registry. 4010 Whenever new link metric types are added to that registry, 4011 IANA MUST update this textual convention accordingly. 4013 The definition of this textual convention with the 4014 addition of newly assigned values is published 4015 periodically by the IANA, in either the Assigned 4016 Numbers RFC, or some derivative of it specific to 4017 Internet Network Management number assignments. (The 4018 latest arrangements can be obtained by contacting the 4019 IANA.) 4021 Requests for new values should be made to IANA via 4022 email (iana@iana.org)." 4023 SYNTAX INTEGER { 4024 unknown(0) -- Link metric meaning assigned 4025 -- by administrative action 4026 -- 1-223 Unassigned 4027 -- 224-255 Reserved for 4028 -- Experimental Use 4029 } 4031 END 4033 Appendix B. Note to the RFC Editor 4035 *************************************************************** 4036 * Note to the RFC Editor (to be removed prior to publication) * 4037 * * 4038 * 1) The reference to RFCYYYY within the DESCRIPTION clauses * 4039 * of the MIB module point to this draft and are to be * 4040 * assigned by the RFC Editor. * 4041 * * 4042 * 2) The reference to RFCXXXX throughout this document point * 4043 * to the current draft-ietf-manet-olsrv2-xx.txt. This * 4044 * needs to be replaced with the XXXX RFC number for the * 4045 * OLSRv2 publication. * 4046 * * 4047 * 3) Appendix A contains the IANAolsrv2LinkMetricType-MIB * 4048 * module which is defined by this specification in the * 4049 * appendix. The RFC editor should remove this specification * 4050 * of the IANAolsrv2LinkMetricType-MIB upon publication of * 4051 * the OLSRv2-MIB. Further, IANA should take over the * 4052 * IANAolsrv2LinkMetricType-MIB and keep it synchronized * 4053 * with the registry identified within the contained * 4054 * IANAolsrv2LinkMetricType TEXTUAL-CONVENTION. * 4055 * * 4056 *************************************************************** 4058 Authors' Addresses 4060 Ulrich Herberg 4061 Fujitsu Laboratories of America 4062 1240 East Arques Avenue 4063 Sunnyvale, CA 94085 4064 USA 4066 EMail: ulrich@herberg.name 4067 URI: http://www.herberg.name/ 4069 Robert G. Cole 4070 US Army CERDEC 4071 6010 Frankford Road, Bldg 6010 4072 Aberdeen Proving Ground, Maryland 21005 4073 USA 4075 Phone: +1 443 395 8744 4076 EMail: robert.g.cole@us.army.mil 4077 URI: http://www.cs.jhu.edu/~rgcole/ 4078 Thomas Heide Clausen 4079 LIX, Ecole Polytechnique 4080 Palaiseau Cedex, 91128 4081 France 4083 Phone: +33 6 6058 9349 4084 EMail: T.Clausen@computer.org 4085 URI: http://www.ThomasClausen.org/