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