idnits 2.17.00 (12 Aug 2021) /tmp/idnits7354/draft-ietf-manet-rfc6779bis-07.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (June 2, 2016) is 2172 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) == Unused Reference: 'RFC3411' is defined on line 3263, but no explicit reference was found in the text == Unused Reference: 'RFC4293' is defined on line 3276, but no explicit reference was found in the text == Unused Reference: 'RFC5497' is defined on line 3287, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 6779 (Obsoleted by RFC 7939) Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group U. Herberg 3 Internet-Draft 4 Obsoletes: 6779 (if approved) R. Cole 5 Intended status: Standards Track US Army CERDEC 6 Expires: December 4, 2016 I. Chakeres 7 Delvin 8 T. Clausen 9 Ecole Polytechnique 10 June 2, 2016 12 Definition of Managed Objects for the Neighborhood Discovery Protocol 13 draft-ietf-manet-rfc6779bis-07 15 Abstract 17 This document revises, extends, and replaces RFC 6779. It defines a 18 portion of the Management Information Base (MIB) for use with network 19 management protocols in the Internet community. In particular, it 20 describes objects for configuring parameters of the Neighborhood 21 Discovery Protocol (NHDP) process on a router. The extensions 22 described in this document add objects and values to support the NHDP 23 optimization specified in RFC 7466. The MIB module defined in this 24 document, denoted NHDP-MIB, also reports state, performance 25 information, and notifications about NHDP. This additional state and 26 performance information is useful to troubleshoot problems and 27 performance issues during neighbor discovery. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on December 4, 2016. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 1.1. Difference from RFC 6779 . . . . . . . . . . . . . . . . . 3 65 2. The Internet-Standard Management Framework . . . . . . . . . . 3 66 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 4.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 71 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 5 72 5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5 73 5.1.2. Notification Generation . . . . . . . . . . . . . . . 5 74 5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5 75 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 7 76 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 7 77 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 8 78 5.5. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 79 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 10 80 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 10 81 6.2. Relationship to Routing Protocol MIB Modules Relying 82 on the NHDP-MIB Module . . . . . . . . . . . . . . . . . . 10 83 6.3. Relationship to the If-MIB . . . . . . . . . . . . . . . . 10 84 6.4. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 11 85 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 86 8. Security Considerations . . . . . . . . . . . . . . . . . . . 66 87 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 68 88 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68 89 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 90 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 91 12.1. Normative References . . . . . . . . . . . . . . . . . . . 69 92 12.2. Informative References . . . . . . . . . . . . . . . . . . 70 94 1. Introduction 96 This document defines a portion of the Management Information Base 97 (MIB) for use with network management protocols in the Internet 98 community. In particular, it describes objects for configuring 99 parameters of the Mobile Ad Hoc Network (MANET) Neighborhood 100 Discovery Protocol (NHDP) [RFC6130] process on a router. The MIB 101 module defined in this document, denoted NHDP-MIB, also reports 102 state, performance information, and notifications about NHDP. This 103 additional state and performance information is useful to 104 troubleshoot problems and performance issues during neighbor 105 discovery. 107 1.1. Difference from RFC 6779 109 This document obsoletes [RFC6779], replacing that document as the 110 specification of the MIB module for [RFC6130]. This revision to 111 [RFC6779] is necessitated by the update to [RFC6130] specified in 112 [RFC7466]. 114 The MIB module for [RFC6130], specified in this document, captures 115 the new information and states for each symmetric 2-hop neighbor, 116 recorded in the Neighbor Information Base of a router and to be 117 reflected in the appropriate tables, introduced by [RFC7466], 118 specifically: 120 o Addition of objects nhdpIib2HopSetN2Lost and 121 nhdpIfPerfCounterDiscontinuityTime. 123 o Addition of extra value (notconsidered) to nhdp2HopNbrState. 125 o Revised full compliance state. 127 2. The Internet-Standard Management Framework 129 For a detailed overview of the documents that describe the current 130 Internet-Standard Management Framework, please refer to section 7 of 131 RFC 3410 [RFC3410]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. MIB objects are generally 135 accessed through the Simple Network Management Protocol (SNMP). 136 Objects in the MIB are defined using the mechanisms defined in the 137 Structure of Management Information (SMI). This memo specifies a MIB 138 module that is compliant to the SMIv2, which is described in STD 58, 139 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 140 [RFC2580]. 142 3. Conventions 144 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 145 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 146 OPTIONAL" in this document are to be interpreted as described in 147 [RFC2119]. 149 4. Overview 151 [RFC6130] allows a router to discover and track topological 152 information of routers up to two hops away by virtue of exchanging 153 HELLO messages. This information is useful for routers running 154 various routing and multicast flooding protocols developed within the 155 IETF MANET Working Group. 157 4.1. Terms 159 The following definitions apply throughout this document: 161 o Notification Objects - triggers and associated notification 162 messages allowing for asynchronous tracking of pre-defined events 163 on the managed router. 165 o Configuration Objects - switches, tables, and objects that are 166 initialized to default settings or set through the management 167 interface defined by this MIB module. 169 o State Objects - automatically generated values that define the 170 current operating state of the NHDP instance in the router. 172 o Performance Objects - automatically generated values that help an 173 administrator or automated tool to assess the performance of the 174 NHDP instance on the router and the overall discovery performance 175 within the Mobile Ad Hoc Network (MANET). 177 4.2. Notation 179 The same notations as defined in [RFC6130] are used throughout this 180 document. 182 5. Structure of the MIB Module 184 This section presents the structure of the NHDP-MIB module. The MIB 185 module is arranged into the following structure: 187 o nhdpNotifications - objects defining NHDP-MIB notifications. 189 o nhdpObjects - defining objects within this MIB module. The 190 objects are arranged into the following groups: 192 * Configuration Group - defining objects related to the 193 configuration of the NHDP instance on the router. 195 * State Group - defining objects that reflect the current state 196 of the NHDP instance running on the router. 198 * Performance Group - defining objects that are useful to a 199 management station when characterizing the performance of NHDP 200 on the router and in the MANET. 202 o nhdpConformance - defining the minimal and maximal conformance 203 requirements for implementations of this MIB module. 205 5.1. Notifications 207 This section describes the use of notifications and mechanisms to 208 enhance the ability to manage NHDP routing domains. 210 5.1.1. Introduction 212 Notifications can be emitted by a router running an instance of this 213 specification as a reaction to a specific event. This allows a 214 network manager to efficiently determine the source of problems or 215 significant changes of configuration or topology, instead of polling 216 a possibly large number of routers. 218 5.1.2. Notification Generation 220 When an exception event occurs, the application notifies the local 221 agent, which sends a notification to the appropriate SNMP management 222 stations. The message includes the notification type and may include 223 a list of notification-specific variables. Section 7 contains the 224 notification definitions, which includes the variable lists. At 225 least one IP address of the router that originates the notification 226 is included in the variable list so that the network manager may 227 determine the source of the notification. 229 5.1.3. Limiting Frequency of Notifications 231 To limit the frequency of notifications, the following additional 232 mechanisms are suggested, similar to those in [RFC4750]. 234 5.1.3.1. Ignoring Initial Activity 236 The majority of critical events occur when NHDP is first enabled on a 237 router, at which time the symmetric neighbors and two-hop neighbors 238 of the router are discovered. During this initial period, a 239 potential flood of notifications is unnecessary since the events are 240 expected. To avoid unnecessary notifications, a router SHOULD NOT 241 originate expected notifications until a certain time interval has 242 elapsed, which is to be predefined by the network manager. It is 243 RECOMMENDED that this time interval is at least 3 x 244 nhdpHelloInterval, so that symmetric neighbors are discovered. The 245 suppression window for notifications is started when the nhdpIfStatus 246 transitions from its default value of 'false(2)' to 'true(1)'. 248 5.1.3.2. Throttling Notifications 250 The mechanism for throttling the notifications is the same as in 251 [RFC4750] (i.e., the number of transmitted notifications per time is 252 bounded). 254 Appropriate values for the window time and upper bound are to be 255 selected by the network manager and depend on the deployment of the 256 MANET. If NHDP is deployed on a lossy, wireless medium, sending too 257 many notifications in a short time interval may lead to collisions 258 and dropped packets. In particular, in dense deployments of routers 259 running NHDP (i.e., where each router has many neighbors), a change 260 of the local topology may trigger many notifications at the same 261 time. [RFC4750] recommends "7 traps with a window time of 10 262 seconds" as the upper bound. As NHDP is expected to be deployed in 263 more lossy channels than OSPF, it is RECOMMENDED to choose a lower 264 threshold for the number of notifications per time than that. 265 Specifically, it is RECOMMENDED that the threshold value for the 266 objects reflecting the change be set to a value of '10' and the 267 DEFAULT values for these objects within the Notifications Group be 268 set to this value. Further, a time window for the change objects is 269 defined within this MIB module. It is RECOMMENDED that if the number 270 of occurrences exceeds the change threshold within the previous 271 change window, then the notification is to be sent. Furthermore, it 272 is RECOMMENDED that the value for this window be set to at least 5 273 times the nhdpHelloInterval. 275 The following objects are used to define the thresholds and time 276 windows for specific notifications defined in the NHDP-MIB module: 277 nhdpNbrStateChangeThreshold, nhdpNbrStateChangeWindow, 278 nhdp2HopNbrStateChangeThreshold, and nhdp2HopNbrStateChangeWindow. 280 5.1.3.3. One Notification per Event 282 Similar to the mechanism in [RFC4750], only one notification is sent 283 per event. 285 5.2. The Configuration Group 287 The router running NHDP is configured with a set of controls. The 288 authoritative list of configuration controls within the NHDP-MIB 289 module are found within the MIB module itself. Generally, an attempt 290 was made in developing the NHDP-MIB module to support all 291 configuration objects defined in [RFC6130]. For all of the 292 configuration parameters, the same constraints and default values of 293 these parameters as defined in [RFC6130] are followed. Refer to 294 [RFC5148] for guidance on setting jitter-related parameters, e.g., 295 nhdpMaxJitter. 297 5.3. The State Group 299 The State Group reports current state information of a router running 300 NHDP. The NHDP-MIB State Group tables were designed to contain the 301 complete set of state information defined within the information 302 bases specified in Sections 6, 7, and 8 of [RFC6130]. 304 Two constructs, i.e., TEXTUAL-CONVENTIONs, are defined to support the 305 tables in the State Group. NHDP stores and indexes information 306 through sets of (dynamically defined) addresses, i.e., address sets. 307 Within SMIv2, it is not possible to index tables with variably 308 defined address sets. Hence, these TEXTUAL-CONVENTIONs are defined 309 to provide a local mapping between NHDP-managed address sets and 310 SMIv2 table indexing. These constructs are the NeighborIfIndex and 311 NeighborRouterIndex. These are locally (to the router) defined, 312 unique identifiers of virtual neighbors and neighbor interfaces. Due 313 to the nature of NHDP, the local router may have identified distinct 314 address sets but is not able to associate these as a single 315 interface. Hence, two or more NeighborIfIndexes pointing to multiple 316 distinct address sets may, in fact, be related to a common neighbor 317 interface. This ambiguity may also hold with respect to the 318 assignment of the NeighborRouterIndex. The local MIB agent is 319 responsible for managing, aggregating, and retiring the defined 320 indexes and for updating MIB tables using these indexes as the local 321 router learns more about its neighbors' topologies. These constructs 322 are used to define indexes to the appropriate State Group tables and 323 to correlate table entries to address sets, virtual neighbor 324 interfaces, and virtual neighbors within the MANET. 326 5.4. The Performance Group 328 The Performance Group reports values relevant to system performance. 329 Unstable neighbors or 2-hop neighbors and frequent changes of sets 330 can have a negative influence on the performance of NHDP. This MIB 331 module defines several objects that can be polled in order to, e.g., 332 calculate histories or monitor frequencies of changes. This may help 333 the network administrator to determine unusual topology changes or 334 other changes that affect stability and reliability of the MANET. 336 5.5. Tables and Indexing 338 The NHDP-MIB module contains a number of tables that record data 339 related to: 341 o the local router, 343 o a local MANET interface on the router, 345 o other routers that are 1 hop removed from the local router, 347 o interfaces on other routers that are 1 hop removed from the local 348 router, and 350 o other routers that are 2 hops removed from the local router. 352 The NHDP-MIB module's tables are indexed via the following 353 constructs: 355 o nhdpIfIndex - the IfIndex of the local router on which NHDP is 356 configured. 358 o nhdpDiscIfIndex - a locally managed index representing a known 359 interface on a neighboring router. 361 o nhdpDiscRouterIndex - a locally managed index representing an ID 362 of a known neighboring router. 364 These tables and their indexing are: 366 o nhdpInterfaceTable - describes the configuration of the interfaces 367 of this router. This table has INDEX { nhdpIfIndex }. 369 o nhdpLibLocalIfSetTable - records all network addresses that are 370 defined as local interface network addresses on this router. This 371 table has INDEX { nhdpLibLocalIfSetIndex }. 373 o nhdpLibRemovedIfAddrSetTable - records network addresses that were 374 recently used as local interface network addresses on this router 375 but have been removed. This table has INDEX 376 { nhdpLibRemovedIfAddrSetIndex }. 378 o nhdpInterfaceStateTable - records state information related to 379 specific interfaces of this router. This table has INDEX 380 { nhdpIfIndex }. 382 o nhdpDiscIfSetTable - includes the nhdpDiscRouterIndex of the 383 discovered router, the nhdpDiscIfIndex of the discovered 384 interface, and the current set of addresses associated with this 385 neighbor interface. This table has INDEX { nhdpDiscIfSetIndex }. 387 o nhdpIibLinkSetTable - for each local interface, records all links 388 belonging to other routers that are, or recently were, 1-hop 389 neighbors to this router. This table has INDEX { nhdpIfIndex, 390 nhdpDiscIfIndex }. 392 o nhdpIib2HopSetTable - for each local interface, records network 393 addresses (one at a time) of symmetric 2-hop neighbors and the 394 symmetric links to symmetric 1-hop neighbors of this router 395 through which these symmetric 2-hop neighbors can be reached. 396 This table has INDEX { nhdpIfIndex, nhdpDiscIfIndex, 397 nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress }. 399 o nhdpNibNeighborSetTable - records all network addresses of each 400 1-hop neighbor to this router. This table has INDEX 401 { nhdpDiscRouterIndex }. 403 o nhdpNibLostNeighborSetTable - records network addresses of other 404 routers that were recently symmetric 1-hop neighbors to this 405 router but are now advertised as lost. This table has INDEX 406 { nhdpDiscRouterIndex }. 408 o nhdpInterfacePerfTable - records performance objects that are 409 measured for each local NHDP interface on this router. This table 410 has INDEX { nhdpIfIndex }. 412 o nhdpDiscIfSetPerfTable - records performance objects that are 413 measured for each discovered interface of a neighbor of this 414 router. This table has INDEX { nhdpDiscIfIndex }. 416 o nhdpDiscNeighborSetPerfTable - records performance objects that 417 are measured for discovered neighbors of this router. This table 418 has INDEX { nhdpDiscRouterIndex }. 420 o nhdpIib2HopSetPerfTable - records performance objects that are 421 measured for discovered 2-hop neighbors of this router. This 422 table has INDEX { nhdpDiscRouterIndex }. 424 6. Relationship to Other MIB Modules 426 This section specifies the relationship of the MIB module contained 427 in this document to other standards, particularly to standards 428 containing other MIB modules. MIB modules and specific definitions 429 imported from MIB modules that SHOULD be implemented in conjunction 430 with the MIB module contained within this document are identified in 431 this section. 433 6.1. Relationship to the SNMPv2-MIB 435 The System group in the SNMPv2-MIB module [RFC3418] is defined as 436 being mandatory for all systems, and the objects apply to the entity 437 as a whole. The System group provides identification of the 438 management entity and certain other system-wide data. The NHDP-MIB 439 module does not duplicate those objects. 441 6.2. Relationship to Routing Protocol MIB Modules Relying on the NHDP- 442 MIB Module 444 [RFC6130] allows routing protocols to rely on the neighborhood 445 information that is discovered by means of HELLO message exchange. 446 In order to allow for troubleshooting, fault isolation, and 447 management of such routing protocols through a routing protocol MIB 448 module, it may be desired to align the State Group tables of the 449 NHDP-MIB module and the routing protocol MIB module. This is 450 accomplished through the definition of two TEXTUAL-CONVENTIONs in the 451 NHDP-MIB module: the NeighborIfIndex and the NeighborRouterIndex. 452 These object types are used to develop indexes into common NHDP-MIB 453 module and routing protocol State Group tables. These objects are 454 locally significant but should be locally common to the NHDP-MIB 455 module and the routing protocol MIB module implemented on a common 456 networked router. This will allow for improved cross-referencing of 457 information across the two MIB modules. 459 6.3. Relationship to the If-MIB 461 The nhdpInterfaceTable in this MIB module describes the configuration 462 of the interfaces of this router that are intended to use MANET 463 control protocols. As such, this table 'sparse augments' the ifTable 464 [RFC2863] specifically when NHDP is to be configured to operate over 465 this interface. The interface is identified by the ifIndex from the 466 interfaces group defined in the Interfaces Group MIB module 467 [RFC2863]. 469 A conceptual row in the nhdpInterfaceTable exists if and only if 470 either a manager has explicitly created the row or there is an 471 interface on the managed device that supports and runs NHDP. 473 If the corresponding entry with ifIndex value is deleted from the 474 Interface Table, then the entry in this table is automatically 475 deleted, NHDP is disabled on this interface, and all configuration 476 and state information related to this interface is to be removed from 477 memory. 479 6.4. MIB Modules Required for IMPORTS 481 The following NHDP-MIB module IMPORTS objects from SNMPv2-SMI 482 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 483 [RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340]. 485 7. Definitions 487 This section contains the MIB module defined by the specification. 489 NHDP-MIB DEFINITIONS ::= BEGIN 491 -- This MIB module defines objects for the management of 492 -- NHDP (RFC 6130) - Mobile Ad Hoc Network (MANET) 493 -- Neighborhood Discovery Protocol (NHDP), 494 -- Clausen, T., Dearlove, C., and J. Dean, January 2011. 496 IMPORTS 498 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 499 Counter32, Counter64, Integer32, Unsigned32, mib-2, 500 TimeTicks 501 FROM SNMPv2-SMI -- RFC 2578 503 TEXTUAL-CONVENTION, TruthValue, TimeStamp, 504 RowStatus 505 FROM SNMPv2-TC -- RFC 2579 507 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 508 FROM SNMPv2-CONF -- STD 58 510 SnmpAdminString 511 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 513 InetAddressType, InetAddress, 514 InetAddressPrefixLength 515 FROM INET-ADDRESS-MIB -- RFC 4001 517 InterfaceIndex 518 FROM IF-MIB -- RFC 2863 520 Float32TC 521 FROM FLOAT-TC-MIB -- RFC 6340 522 ; 524 nhdpMIB MODULE-IDENTITY 525 LAST-UPDATED "201606021100Z" -- 02 June 2016 526 ORGANIZATION "IETF MANET Working Group" 527 CONTACT-INFO 528 "WG E-Mail: manet@ietf.org 529 WG web page: https://datatracker.ietf.org/wg/manet 531 Editors: Ulrich Herberg 532 USA 533 ulrich@herberg.name 534 http://www.herberg.name/ 536 Robert G. Cole 537 US Army CERDEC 538 Space and Terrestrial Communications 539 6010 Frankford Street 540 Aberdeen Proving Ground, Maryland 21005 541 USA 542 +1 443 395-8744 543 robert.g.cole@us.army.mil 544 http://www.cs.jhu.edu/~rgcole/ 546 Ian D Chakeres 547 Delvin 548 Ellicott City, Maryland 21042 549 USA 550 ian.chakeres@gmail.com 551 http://www.ianchak.com/ 553 Thomas Heide Clausen 554 Ecole Polytechnique 555 LIX 556 91128 Palaiseau Cedex 557 France 558 Email: T.Clausen@computer.org 559 URI: http://www.thomasclausen.org/" 561 DESCRIPTION 562 "This NHDP-MIB module is applicable to routers 563 implementing the Mobile Ad Hoc Network (MANET) 564 Neighborhood Discovery Protocol (NHDP) 565 defined in RFC 6130. 567 Copyright (c) 2014 IETF Trust and the persons 568 identified as authors of the code. All rights reserved. 570 Redistribution and use in source and binary forms, with 571 or without modification, is permitted pursuant to, and 572 subject to the license terms contained in, the Simplified 573 BSD License set forth in Section 4.c of the IETF Trust's 574 Legal Provisions Relating to IETF Documents 575 (http://trustee.ietf.org/license-info). 577 This version of this MIB module is part of RFC xxxx; see 578 the RFC itself for full legal notices." 580 -- revision 581 REVISION "201606021100Z" -- 02 June 2016 582 DESCRIPTION 583 "Updated version of this MIB module, 584 including updates made to NHDP by 585 RFC 7466, published as RFC xxxx." 586 REVISION "201210221000Z" -- 22 October 2012 587 DESCRIPTION 588 "Initial version of this MIB module, 589 published as RFC 6779." 590 ::= { mib-2 213 } 592 -- 593 -- Top-Level Components of this MIB Module 594 -- 595 nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 } 596 nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 } 597 nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 } 599 -- 600 -- TEXTUAL-CONVENTIONs 601 -- 602 -- Two new TEXTUAL-CONVENTIONs have been defined in 603 -- this MIB module for indexing into the following 604 -- tables and indexing into other tables in other MIB modules. 605 -- This was necessary because NHDP manages and 606 -- indexes based upon dynamic address tuples, i.e., 607 -- address sets, while SMI requires statically 608 -- defined indexes for accessing its table rows. 609 -- The NeighborIfIndex defines a unique (to the local router) 610 -- index referencing a discovered virtual interface on another 611 -- neighbor within the MANET. The NeighborRouterIndex defines a 612 -- unique (to the local router) index referencing a discovered 613 -- virtual neighbor within the MANET. 614 -- 615 -- Due to the nature of NHDP, 616 -- different indexes may be related to common neighbor 617 -- interfaces or common neighbor routers, but the information 618 -- obtained through NHDP has not allowed the local router 619 -- to relate these virtual objects (i.e., interfaces or routers) 620 -- at this point in time. As more topology information 621 -- is gathered by the local router, it may associate 622 -- virtual interfaces or routers and collapse these 623 -- indexes appropriately. 625 -- Multiple addresses can be associated with a 626 -- given NeighborIfIndex. Each NeighborIfIndex is 627 -- associated with a NeighborRouterIndex. Throughout 628 -- the nhdpStateObjGroup, the 629 -- NeighborIfIndex and the NeighborRouterIndex are used 630 -- to define the set of IP Addresses related to a virtual 631 -- neighbor interface or virtual neighbor under discussion. 633 NeighborIfIndex ::= TEXTUAL-CONVENTION 634 DISPLAY-HINT "d" 635 STATUS current 636 DESCRIPTION 637 "An arbitrary, locally unique identifier associated with a 638 virtual interface of a discovered NHDP neighbor. 639 Due to the nature of NHDP, the local router 640 may not know if two distinct addresses belong to the 641 same interface of a neighbor or to two different 642 interfaces. As the local router gains more 643 knowledge of its neighbors, its local view may change, and 644 this table will be updated to reflect the local router's 645 current understanding, associating address sets to neighbor 646 interfaces. The local router identifies a virtual neighbor 647 interface through the receipt of address lists advertised 648 through an NHDP HELLO message. 650 All objects of type NeighborIfIndex are assigned by the agent 651 out of a common number space. 653 The value for each discovered virtual neighbor 654 interface may not remain constant from 655 one re-initialization of the entity's network management 656 agent to the next re-initialization. If the 657 local router gains information associating two virtual 658 interfaces on a neighbor as a common interface, 659 then the agent MUST aggregate the two address sets to 660 a single index chosen from the set of aggregated indexes, 661 and it MUST update all tables in this 662 MIB module that are indexed by indexes 663 of type NeighborIfIndex. It MAY then reuse freed 664 index values following the next agent restart. 666 The specific value is meaningful only within a given SNMP 667 entity." 668 SYNTAX Unsigned32 (1..2147483647) 670 NeighborRouterIndex ::= TEXTUAL-CONVENTION 671 DISPLAY-HINT "d" 672 STATUS current 673 DESCRIPTION 674 "An arbitrary, locally unique identifier associated with a 675 virtual discovered neighbor (one or two hop). Due to the 676 nature of NHDP, the local router may identify 677 multiple virtual neighbors that, in fact, are one and 678 the same. Neighbors that are two hops away with more than 679 one advertised address will exhibit this behavior. As the 680 local router's knowledge of its neighbors' topology 681 increases, the local router will be able to associate 682 multiple virtual neighbor indexes into a single virtual 683 neighbor index chosen from the set of aggregated indexes; 684 it MUST update all tables in this MIB module indexed by these 685 indexes, and it MAY reuse the freed indexes following the 686 next agent re-initialization. 688 All objects of type NeighborRouterIndex are assigned by 689 the agent out of a common number space. 691 The NeighborRouterIndex defines a discovered NHDP peer 692 virtual neighbor of the local router. 693 The value for each discovered virtual neighbor index MUST 694 remain constant at least from one re-initialization of 695 the entity's network management agent to the next 696 re-initialization, except if an application is deleted 697 and re-created. 699 The specific value is meaningful only within a given SNMP 700 entity. A NeighborRouterIndex value MUST NOT be reused 701 until the next agent restart." 702 SYNTAX Unsigned32 (1..2147483647) 704 -- 705 -- nhdpObjects 706 -- 708 -- 1) Configuration Objects Group 709 -- 2) State Objects Group 710 -- 3) Performance Objects Group 712 -- 713 -- nhdpConfigurationObjGrp 714 -- 716 -- Contains the NHDP objects that configure specific options 717 -- that determine the overall performance and operation of 718 -- NHDP. 720 nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } 722 nhdpInterfaceTable OBJECT-TYPE 723 SYNTAX SEQUENCE OF NhdpInterfaceEntry 724 MAX-ACCESS not-accessible 725 STATUS current 726 DESCRIPTION 727 "The nhdpInterfaceTable describes the 728 configuration of the interfaces of this router 729 that are intended to use MANET control protocols. 730 As such, this table 'sparse augments' the ifTable 731 specifically when NHDP is to be configured to 732 operate over this interface. The interface is 733 identified by the ifIndex from the interfaces 734 group defined in the Interfaces Group MIB module. 736 A conceptual row in this table exists if and only 737 if either a manager has explicitly created the row 738 or there is an interface on the managed device 739 that supports and runs NHDP. 741 The manager can create a row by setting 742 rowStatus to 'createAndGo' or 'createAndWait'. 743 Row objects having associated DEFVAL clauses are 744 automatically defined by the agent with these 745 values during row creation, unless the manager 746 explicitly defines these object values during the 747 row creation. 749 If the corresponding entry with ifIndex value 750 is deleted from the Interface Table, then the entry 751 in this table is automatically deleted, 752 NHDP is disabled on this interface, 753 and all configuration and state information 754 related to this interface is to be removed 755 from memory." 756 REFERENCE 757 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 758 K., and F. Kastenholtz, June 2000" 759 ::= { nhdpConfigurationObjGrp 1 } 761 nhdpInterfaceEntry OBJECT-TYPE 762 SYNTAX NhdpInterfaceEntry 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "The nhdpInterfaceEntry describes one NHDP 767 local interface configuration as indexed by 768 its ifIndex as defined in the Standard MIB II 769 Interface Table (RFC 2863). 771 The objects in this table are persistent, and when 772 written, the device SHOULD save the change to 773 non-volatile storage. For further information 774 on the storage behavior for these objects, refer 775 to the description for the nhdpIfRowStatus 776 object." 777 INDEX { nhdpIfIndex } 778 ::= { nhdpInterfaceTable 1 } 780 NhdpInterfaceEntry ::= 781 SEQUENCE { 782 nhdpIfIndex 783 InterfaceIndex, 784 nhdpIfName 785 SnmpAdminString, 786 nhdpIfStatus 787 TruthValue, 788 nhdpHelloInterval 789 Unsigned32, 790 nhdpHelloMinInterval 791 Unsigned32, 792 nhdpRefreshInterval 793 Unsigned32, 794 nhdpLHoldTime 795 Unsigned32, 796 nhdpHHoldTime 797 Unsigned32, 798 nhdpHystAcceptQuality 799 Float32TC, 800 nhdpHystRejectQuality 801 Float32TC, 802 nhdpInitialQuality 803 Float32TC, 804 nhdpInitialPending 805 TruthValue, 806 nhdpHpMaxJitter 807 Unsigned32, 808 nhdpHtMaxJitter 809 Unsigned32, 810 nhdpIfRowStatus 811 RowStatus 812 } 814 nhdpIfIndex OBJECT-TYPE 815 SYNTAX InterfaceIndex 816 MAX-ACCESS not-accessible 817 STATUS current 818 DESCRIPTION 819 "This value MUST correspond to an ifIndex referring 820 to a valid entry in the Interfaces Table." 821 REFERENCE 822 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 823 and F. Kastenholtz, June 2000" 824 ::= { nhdpInterfaceEntry 1 } 826 nhdpIfName OBJECT-TYPE 827 SYNTAX SnmpAdminString 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The textual name of the interface. The value of this 832 object SHOULD be the name of the interface as assigned by 833 the local device. This can be a text-name, such as 'le0' 834 or a simple port number, such as '1', 835 depending on the interface-naming syntax of the device. 837 If there is no local name or this object is otherwise not 838 applicable, then this object contains a zero-length string." 839 ::= { nhdpInterfaceEntry 2 } 841 nhdpIfStatus OBJECT-TYPE 842 SYNTAX TruthValue 843 MAX-ACCESS read-create 844 STATUS current 845 DESCRIPTION 846 "nhdpIfStatus indicates whether this interface is 847 currently running NHDP. A value of 'true(1)' indicates 848 that NHDP is running on this interface. 849 A value of 'false(2)' indicates that NHDP is not 850 currently running on this interface. This corresponds 851 to the I_manet parameter in the Local Interface Set 852 of NHDP." 853 DEFVAL { false } 854 ::= { nhdpInterfaceEntry 3 } 856 -- 857 -- Interface Parameters - Message Intervals 858 -- 860 nhdpHelloInterval OBJECT-TYPE 861 SYNTAX Unsigned32 862 UNITS "milliseconds" 863 MAX-ACCESS read-create 864 STATUS current 865 DESCRIPTION 866 "nhdpHelloInterval corresponds to 867 HELLO_INTERVAL of NHDP and represents the 868 maximum time between the transmission of two 869 successive HELLO messages on this MANET interface. 871 Guidance for setting this object may be found 872 in Section 5 of the NHDP specification (RFC 6130), 873 which indicates that: 874 o nhdpHelloInterval > 0 875 o nhdpHelloInterval >= nhdpHelloMinInterval" 876 REFERENCE 877 "Section 5 on Protocol Parameters and 878 Constraints of RFC 6130 - Mobile Ad Hoc 879 Network (MANET) Neighborhood Discovery 880 Protocol (NHDP), Clausen, T., Dearlove, 881 C., and J. Dean, April 2011" 882 DEFVAL { 2000 } 883 ::= { nhdpInterfaceEntry 4 } 885 nhdpHelloMinInterval OBJECT-TYPE 886 SYNTAX Unsigned32 887 UNITS "milliseconds" 888 MAX-ACCESS read-create 889 STATUS current 890 DESCRIPTION 891 "nhdpHelloMinInterval corresponds to 892 HELLO_MIN_INTERVAL of NHDP and represents 893 the minimum interval between transmission 894 of two successive HELLO messages on this 895 MANET interface. 897 Guidance for setting this object may be found 898 in Section 5 of the NHDP specification (RFC 6130), 899 which indicates that: 900 o nhdpHelloMinInterval <= nhdpHelloInterval" 901 REFERENCE 902 "Section 5 on Protocol Parameters and 903 Constraints of RFC 6130 - Mobile Ad Hoc Network 904 (MANET) Neighborhood Discovery Protocol (NHDP), 905 Clausen, T., Dearlove, C., and J. Dean, April 2011" 906 DEFVAL { 500 } 907 ::= { nhdpInterfaceEntry 5 } 909 nhdpRefreshInterval OBJECT-TYPE 910 SYNTAX Unsigned32 911 UNITS "milliseconds" 912 MAX-ACCESS read-create 913 STATUS current 914 DESCRIPTION 915 "nhdpRefreshInterval corresponds to 916 REFRESH_INTERVAL of NHDP and represents the 917 maximum interval between advertisements of 918 each 1-hop neighbor network address and its 919 status. Each advertisement is in a HELLO 920 message on this MANET interface. 922 Guidance for setting this object may be found 923 in Section 5 of the NHDP specification (RFC 6130), 924 which indicates that: 925 o nhdpRefreshInterval >= nhdpHelloInterval" 926 REFERENCE 927 "Section 5 on Protocol Parameters and 928 Constraints of RFC 6130 - Mobile Ad Hoc Network 929 (MANET) Neighborhood Discovery Protocol (NHDP), 930 Clausen, T., Dearlove, C., and J. Dean, April 2011" 931 DEFVAL { 2000 } 932 ::= { nhdpInterfaceEntry 6 } 934 -- 935 -- Interface Parameters - Information Validity times 936 -- 938 nhdpLHoldTime OBJECT-TYPE 939 SYNTAX Unsigned32 940 UNITS "milliseconds" 941 MAX-ACCESS read-create 942 STATUS current 943 DESCRIPTION 944 "nhdpLHoldTime corresponds to 945 L_HOLD_TIME of NHDP and represents the period 946 of advertisement, on this MANET interface, of 947 former 1-hop neighbor network addresses as lost 948 in HELLO messages, allowing recipients of these 949 HELLO messages to accelerate removal of this 950 information from their Link Sets. 952 Guidance for setting this object may be found 953 in Section 5 of the NHDP specification (RFC 6130), 954 which indicates that it should be assigned a 955 value significantly greater than the refresh 956 interval held by nhdpRefreshInterval." 957 REFERENCE 958 "Section 5 on Protocol Parameters and 959 Constraints of RFC 6130 - Mobile Ad Hoc Network 960 (MANET) Neighborhood Discovery Protocol (NHDP), 961 Clausen, T., Dearlove, C., and J. Dean, April 2011" 962 DEFVAL { 6000 } 963 ::= { nhdpInterfaceEntry 7 } 965 nhdpHHoldTime OBJECT-TYPE 966 SYNTAX Unsigned32 967 UNITS "milliseconds" 968 MAX-ACCESS read-create 969 STATUS current 970 DESCRIPTION 971 "nhdpHHoldTime corresponds to 972 H_HOLD_TIME of NHDP and is used as the value 973 in the VALIDITY_TIME Message TLV included in all 974 HELLO messages on this MANET interface. It is then 975 used by each router receiving such a HELLO message 976 to indicate the validity of the information taken 977 from that HELLO message and recorded in the receiving 978 router's Information Bases. 980 Guidance for setting this object may be found 981 in Section 5 of the NHDP specification (RFC 6130), 982 which indicates that it should be assigned a 983 value significantly greater than the refresh interval 984 held by nhdpRefreshInterval and must be representable 985 as described in RFC 5497." 986 REFERENCE 987 "Section 5 on Protocol Parameters and 988 Constraints of RFC 6130 - Mobile Ad Hoc Network 989 (MANET) Neighborhood Discovery Protocol (NHDP), 990 Clausen, T., Dearlove, C., and J. Dean, April 2011" 991 DEFVAL { 6000 } 992 ::= { nhdpInterfaceEntry 8 } 994 -- 995 -- Interface Parameters - Link Quality 996 -- 998 nhdpHystAcceptQuality OBJECT-TYPE 999 SYNTAX Float32TC 1000 MAX-ACCESS read-create 1001 STATUS current 1002 DESCRIPTION 1003 "nhdpHystAcceptQuality corresponds to 1004 HYST_ACCEPT of NHDP and represents the link 1005 quality threshold at or above which a link becomes 1006 usable, if it was not already so. 1008 Guidance for setting this object may be found 1009 in Section 5 of the NHDP specification (RFC 6130), 1010 which indicates that: 1011 o 0 <= nhdpHystRejectQuality 1012 <= nhdpHystAcceptQuality <= 1.0 1014 The default value for this object is 1.0. According to 1015 RFC 6340: 1016 Since these textual conventions are defined in terms 1017 of the OCTET STRING type, the SMI's mechanism for 1018 formally setting range constraints are not available. 1019 MIB designers using these textual conventions will need 1020 to use DESCRIPTION clauses to spell out any applicable 1021 range constraints beyond those implied by the underlying 1022 IEEE types. 1023 Therefore, this object does not have a DEFVAL clause." 1024 REFERENCE 1025 "Section 5 on Protocol Parameters and 1026 Constraints of RFC 6130 - Mobile Ad Hoc Network 1027 (MANET) Neighborhood Discovery Protocol (NHDP), 1028 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1029 -- DEFVAL { 1.0 } see DESCRIPTION 1030 ::= { nhdpInterfaceEntry 9 } 1032 nhdpHystRejectQuality OBJECT-TYPE 1033 SYNTAX Float32TC 1034 MAX-ACCESS read-create 1035 STATUS current 1036 DESCRIPTION 1037 "nhdpHystRejectQuality corresponds to 1038 HYST_REJECT of NHDP and represents the 1039 link quality threshold below which a 1040 link becomes unusable, if it was not 1041 already so. 1043 Guidance for setting this object may be found 1044 in Section 5 of the NHDP specification (RFC 6130), 1045 which indicates that: 1046 o 0 <= nhdpHystRejectQuality 1047 <= nhdpHystAcceptQuality <= 1.0 1049 The default value for this object is 0.0. According to 1050 RFC 6340: 1051 Since these textual conventions are defined in terms 1052 of the OCTET STRING type, the SMI's mechanism for 1053 formally setting range constraints are not available. 1054 MIB designers using these textual conventions will need 1055 to use DESCRIPTION clauses to spell out any applicable 1056 range constraints beyond those implied by the underlying 1057 IEEE types. 1058 Therefore, this object does not have a DEFVAL clause." 1059 REFERENCE 1060 "Section 5 on Protocol Parameters and 1061 Constraints of RFC 6130 - Mobile Ad Hoc Network 1062 (MANET) Neighborhood Discovery Protocol (NHDP), 1063 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1064 -- DEFVAL { 0.0 } see DESCRIPTION 1065 ::= { nhdpInterfaceEntry 10 } 1067 nhdpInitialQuality OBJECT-TYPE 1068 SYNTAX Float32TC 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION 1072 "nhdpInitialQuality corresponds to 1073 INITIAL_QUALITY of NHDP and represents the 1074 initial quality of a newly identified link. 1076 Guidance for setting this object may be found 1077 in Section 5 of the NHDP specification (RFC 6130), 1078 which indicates that: 1079 o 0 <= nhdpInitialQuality <= 1.0 1081 The default value for this object is 1.0. According to 1082 RFC 6340: 1084 Since these textual conventions are defined in terms 1085 of the OCTET STRING type, the SMI's mechanism for 1086 formally setting range constraints are not available. 1087 MIB designers using these textual conventions will need 1088 to use DESCRIPTION clauses to spell out any applicable 1089 range constraints beyond those implied by the underlying 1090 IEEE types. 1091 Therefore, this object does not have a DEFVAL clause." 1092 REFERENCE 1093 "Section 5 on Protocol Parameters and 1094 Constraints of RFC 6130 - Mobile Ad Hoc Network 1095 (MANET) Neighborhood Discovery Protocol (NHDP), 1096 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1097 -- DEFVAL { 1.0 } see DESCRIPTION 1098 ::= { nhdpInterfaceEntry 11 } 1100 nhdpInitialPending OBJECT-TYPE 1101 SYNTAX TruthValue 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "nhdpInitialPending corresponds to 1106 INITIAL_PENDING of NHDP. If the value of this object 1107 is 'true(1)', then a newly identified link is considered 1108 pending and is not usable until the link quality 1109 has reached or exceeded the nhdpHystAcceptQuality 1110 threshold. 1112 Guidance for setting this object may be found 1113 in Section 5 of the NHDP specification (RFC 6130), 1114 which indicates that: 1115 o If nhdpInitialQuality >= nhdpHystAcceptQuality, 1116 then nhdpInitialPending := false(2). 1117 o If nhdpInitialQuality < nhdpHystRejectQuality, 1118 then nhdpInitialPending := true(1)." 1119 REFERENCE 1120 "Section 5 on Protocol Parameters and 1121 Constraints of RFC 6130 - Mobile Ad Hoc Network 1122 (MANET) Neighborhood Discovery Protocol (NHDP), 1123 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1124 DEFVAL { false } 1125 ::= { nhdpInterfaceEntry 12 } 1127 -- 1128 -- Interface Parameters - Jitter 1129 -- 1130 nhdpHpMaxJitter OBJECT-TYPE 1131 SYNTAX Unsigned32 1132 UNITS "milliseconds" 1133 MAX-ACCESS read-create 1134 STATUS current 1135 DESCRIPTION 1136 "nhdpHpMaxJitter corresponds to 1137 HP_MAXJITTER of NHDP and represents the 1138 value of MAXJITTER used in RFC 5148 for 1139 periodically generated HELLO messages on 1140 this MANET interface. 1142 Guidance for setting this object may be found 1143 in Section 5 of RFC 5148, which indicates that: 1144 o nhdpHpMaxJitter <= nhdpHelloInterval / 2 1145 o nhdpHpMaxJitter should not be greater 1146 than nhdpHelloInterval / 4 1147 o If nhdpMinHelloInterval > 0, then 1148 nhdpHpMaxJitter <= nhdpHelloMinInterval; and 1149 nhdpHpMaxJitter should not be greater than 1150 nhdpHelloMinInterval / 2" 1151 REFERENCE 1152 "Section 5 of RFC 5148 - Jitter Considerations in 1153 Mobile Ad Hoc Networks (MANETs), 1154 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1155 DEFVAL { 500 } 1156 ::= { nhdpInterfaceEntry 13 } 1158 nhdpHtMaxJitter OBJECT-TYPE 1159 SYNTAX Unsigned32 1160 UNITS "milliseconds" 1161 MAX-ACCESS read-create 1162 STATUS current 1163 DESCRIPTION 1164 "nhdpHtMaxJitter corresponds to 1165 HT_MAXJITTER of NHDP and represents the 1166 value of MAXJITTER used in RFC 5148 for 1167 externally triggered HELLO messages on this 1168 MANET interface. 1170 Guidance for setting this object may be found 1171 in Section 5 of RFC 5148, which indicates that: 1172 o nhdpHtMaxJitter <= nhdpHelloInterval / 2 1173 o nhdpHtMaxJitter should not be greater 1174 than nhdpHelloInterval / 4 1175 o If nhdpMinHelloInterval > 0, then 1176 nhdpHtMaxJitter <= nhdpHelloMinInterval; and 1177 nhdpHtMaxJitter should not be greater than 1178 nhdpHelloMinInterval / 2" 1180 REFERENCE 1181 "Section 5 of RFC 5148 - Jitter Considerations in 1182 Mobile Ad Hoc Networks (MANETs), 1183 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1184 DEFVAL { 500 } 1185 ::= { nhdpInterfaceEntry 14 } 1187 nhdpIfRowStatus OBJECT-TYPE 1188 SYNTAX RowStatus 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "This object permits management of the table 1193 by facilitating actions such as row creation, 1194 construction, and destruction. The value of 1195 this object has no effect on whether other 1196 objects in this conceptual row can be 1197 modified. 1199 An entry may not exist in the 'active(1)' state unless all 1200 objects in the entry have a defined appropriate value. For 1201 objects with DEFVAL clauses, the management station 1202 does not need to specify the value of this object in order 1203 for the row to transit to the 'active(1)' state; the default 1204 value for this object is used. For objects that do not 1205 have DEFVAL clauses, then the network manager MUST 1206 specify the value of this object prior to this row 1207 transitioning to the 'active(1)' state. 1209 When this object transitions to 'active(1)', all objects 1210 in this row SHOULD be written to non-volatile (stable) 1211 storage. Read-create objects in this row MAY be modified. 1212 When an object in a row with nhdpIfRowStatus of 'active(1)' 1213 is changed, then the updated value MUST be reflected in NHDP, 1214 and this new object value MUST be written to non-volatile 1215 storage. 1217 If the value of this object is not equal to 'active(1)', 1218 all associated entries in the nhdpLibLocalIfSetTable, 1219 nhdpInterfaceStateTable, nhdpIibLinkSetTable, and 1220 nhdpInterfacePerfTable MUST be deleted." 1221 REFERENCE 1222 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1223 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1224 C., and J. Dean, April 2011" 1225 DEFVAL { active } 1226 ::= { nhdpInterfaceEntry 15 } 1227 -- 1228 -- Router Parameters - Information Validity Time 1229 -- 1230 nhdpNHoldTime OBJECT-TYPE 1231 SYNTAX Unsigned32 1232 UNITS "milliseconds" 1233 MAX-ACCESS read-write 1234 STATUS current 1235 DESCRIPTION 1236 "nhdpNHoldTime corresponds to 1237 N_HOLD_TIME of NHDP and is used as the period 1238 during which former 1-hop neighbor network 1239 addresses are advertised as lost in HELLO 1240 messages, allowing recipients of these HELLO 1241 messages to accelerate removal of this information 1242 from their 2-Hop Sets. 1244 This object is persistent, and when written, 1245 the entity SHOULD save the change to 1246 non-volatile storage." 1247 REFERENCE 1248 "Section 5 on Protocol Parameters and 1249 Constraints of RFC 6130 - Mobile Ad Hoc Network 1250 (MANET) Neighborhood Discovery Protocol (NHDP), 1251 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1252 DEFVAL { 6000 } 1253 ::= { nhdpConfigurationObjGrp 2 } 1255 nhdpIHoldTime OBJECT-TYPE 1256 SYNTAX Unsigned32 1257 UNITS "milliseconds" 1258 MAX-ACCESS read-write 1259 STATUS current 1260 DESCRIPTION 1261 "nhdpIHoldTime corresponds to 1262 I_HOLD_TIME of NHDP and represents the period 1263 for which a recently used local interface network 1264 address is recorded. 1266 This object is persistent, and when written, 1267 the entity SHOULD save the change to 1268 non-volatile storage." 1269 REFERENCE 1270 "Section 5 on Protocol Parameters and 1271 Constraints of RFC 6130 - Mobile Ad Hoc Network 1272 (MANET) Neighborhood Discovery Protocol (NHDP), 1273 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1275 DEFVAL { 6000 } 1276 ::= { nhdpConfigurationObjGrp 3 } 1278 -- A router's Local Information Base (LIB) 1280 -- 1281 -- Local Interface Set Table 1282 -- 1284 nhdpLibLocalIfSetTable OBJECT-TYPE 1285 SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry 1286 MAX-ACCESS not-accessible 1287 STATUS current 1288 DESCRIPTION 1289 "A router's Local Interface Set records all 1290 network addresses that are defined as local 1291 MANET interface network addresses. 1292 As such, this table 'sparse augments' the 1293 nhdpInterfaceTable when network addresses are 1294 being defined for the interfaces existing within 1295 the nhdpInterfaceTable. The local interface 1296 is defined by the nhdpIfIndex. 1298 The Local Interface Set consists of Local Interface 1299 Address Tuples per MANET interface and their prefix 1300 lengths (in order to determine the network addresses 1301 related to the interface). 1303 A conceptual row in this table exists if and only 1304 if a manager has explicitly created the row. The 1305 manager can create a row by setting rowStatus 1306 to 'createAndGo' or 'createAndWait'. 1308 Further guidance on the addition or removal of 1309 local addresses and network addresses is found 1310 in Section 9 of RFC 6130." 1311 REFERENCE 1312 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1313 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1314 C., and J. Dean, April 2011" 1315 ::= { nhdpConfigurationObjGrp 4 } 1317 nhdpLibLocalIfSetEntry OBJECT-TYPE 1318 SYNTAX NhdpLibLocalIfSetEntry 1319 MAX-ACCESS not-accessible 1320 STATUS current 1321 DESCRIPTION 1322 "A router's Local Interface Set consists 1323 of Local Interface Tuples for each network 1324 interface. 1326 The objects in this table are persistent, and when 1327 written, the device SHOULD save the change to 1328 non-volatile storage. For further information 1329 on the storage behavior for these objects, refer 1330 to the description for the nhdpLibLocalIfSetRowStatus 1331 object." 1332 REFERENCE 1333 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1334 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1335 C., and J. Dean, April 2011" 1336 INDEX { nhdpLibLocalIfSetIndex } 1337 ::= { nhdpLibLocalIfSetTable 1 } 1339 NhdpLibLocalIfSetEntry ::= 1340 SEQUENCE { 1341 nhdpLibLocalIfSetIndex 1342 Integer32, 1343 nhdpLibLocalIfSetIfIndex 1344 InterfaceIndex, 1345 nhdpLibLocalIfSetIpAddrType 1346 InetAddressType, 1347 nhdpLibLocalIfSetIpAddr 1348 InetAddress, 1349 nhdpLibLocalIfSetIpAddrPrefixLen 1350 InetAddressPrefixLength, 1351 nhdpLibLocalIfSetRowStatus 1352 RowStatus 1353 } 1355 nhdpLibLocalIfSetIndex OBJECT-TYPE 1356 SYNTAX Integer32 (0..65535) 1357 MAX-ACCESS not-accessible 1358 STATUS current 1359 DESCRIPTION 1360 "The index for this table. Necessary 1361 because multiple addresses may be associated 1362 with a given nhdpIfIndex." 1363 REFERENCE 1364 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1365 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1366 C., and J. Dean, April 2011" 1367 ::= { nhdpLibLocalIfSetEntry 1 } 1369 nhdpLibLocalIfSetIfIndex OBJECT-TYPE 1370 SYNTAX InterfaceIndex 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "Specifies the local nhdpIfIndex for which this 1375 IP address was added." 1376 REFERENCE 1377 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1378 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1379 C., and J. Dean, April 2011" 1380 ::= { nhdpLibLocalIfSetEntry 2 } 1382 nhdpLibLocalIfSetIpAddrType OBJECT-TYPE 1383 SYNTAX InetAddressType 1384 MAX-ACCESS read-create 1385 STATUS current 1386 DESCRIPTION 1387 "The type of the nhdpLibLocalIfSetIpAddr 1388 in the InetAddress MIB (RFC 4001). 1390 Only the values 'ipv4(1)' and 1391 'ipv6(2)' are supported." 1392 REFERENCE 1393 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1394 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1395 C., and J. Dean, April 2011" 1396 ::= { nhdpLibLocalIfSetEntry 3 } 1398 nhdpLibLocalIfSetIpAddr OBJECT-TYPE 1399 SYNTAX InetAddress (SIZE(4|16)) 1400 MAX-ACCESS read-create 1401 STATUS current 1402 DESCRIPTION 1403 "nhdpLibLocalIfSetIpAddr is an 1404 address of an interface of 1405 this router. 1407 This object is interpreted according to 1408 the setting of nhdpLibLocalIfSetIpAddrType." 1409 REFERENCE 1410 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1411 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1412 C., and J. Dean, April 2011" 1413 ::= { nhdpLibLocalIfSetEntry 4 } 1415 nhdpLibLocalIfSetIpAddrPrefixLen OBJECT-TYPE 1416 SYNTAX InetAddressPrefixLength 1417 MAX-ACCESS read-create 1418 STATUS current 1419 DESCRIPTION 1420 "Indicates the number of leading one bits that 1421 form the mask. The mask is logically ANDed 1422 to the nhdpLibLocalIfSetIpAddr to determine 1423 the address prefix. A row match is true 1424 if the address used as an index falls within 1425 the network address range defined by the 1426 address prefix." 1427 REFERENCE 1428 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1429 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1430 C., and J. Dean, April 2011" 1431 ::= { nhdpLibLocalIfSetEntry 5 } 1433 nhdpLibLocalIfSetRowStatus OBJECT-TYPE 1434 SYNTAX RowStatus 1435 MAX-ACCESS read-create 1436 STATUS current 1437 DESCRIPTION 1438 "This object permits management of the table 1439 by facilitating actions such as row creation, 1440 construction, and destruction. The value of 1441 this object has no effect on whether other 1442 objects in this conceptual row can be 1443 modified. 1445 An entry may not exist in the 'active(1)' state unless all 1446 read-create objects in the entry have a defined 1447 appropriate value. As no objects in this table have 1448 DEFVAL clauses, the management station MUST specify 1449 the values of all read-create objects prior to this row 1450 transitioning to the 'active(1)' state. 1452 When this object transitions to 'active(1)', all objects 1453 in this row SHOULD be written to non-volatile (stable) 1454 storage. Read-create objects in this row MAY be modified. 1455 When an object in a row with nhdpIfRowStatus of 'active(1)' 1456 is changed, then the updated value MUST be reflected in NHDP, 1457 and this new object value MUST be written to non-volatile 1458 storage." 1459 REFERENCE 1460 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1461 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1462 C., and J. Dean, April 2011" 1463 DEFVAL { notReady } 1464 ::= { nhdpLibLocalIfSetEntry 6 } 1466 -- 1467 -- Removed Interface Addr Set Table 1468 -- 1470 nhdpLibRemovedIfAddrSetTable OBJECT-TYPE 1471 SYNTAX SEQUENCE OF NhdpLibRemovedIfAddrSetEntry 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "A router's Removed Interface Address Set records 1476 network addresses that were recently used as local 1477 interface network addresses. If a router's interface 1478 network addresses are immutable, then the Removed 1479 Interface Address Set is always empty and may be omitted. 1480 It consists of Removed Interface Address Tuples, one 1481 per network address." 1482 REFERENCE 1483 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1484 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1485 C., and J. Dean, April 2011" 1486 ::= { nhdpConfigurationObjGrp 5 } 1488 nhdpLibRemovedIfAddrSetEntry OBJECT-TYPE 1489 SYNTAX NhdpLibRemovedIfAddrSetEntry 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "A router's Removed Interface Address Set consists 1494 of Removed Interface Address Tuples, one per network 1495 address: 1497 (IR_local_iface_addr, IR_time) 1499 The association between these addresses and the 1500 router's Interface is found in RFC 4293 (ipAddressTable)" 1501 REFERENCE 1502 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1503 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1504 C., and J. Dean, April 2011" 1505 INDEX { nhdpLibRemovedIfAddrSetIndex } 1506 ::= { nhdpLibRemovedIfAddrSetTable 1 } 1508 NhdpLibRemovedIfAddrSetEntry ::= 1509 SEQUENCE { 1510 nhdpLibRemovedIfAddrSetIndex 1511 Integer32, 1512 nhdpLibRemovedIfAddrSetIpAddrType 1513 InetAddressType, 1515 nhdpLibRemovedIfAddrSetIpAddr 1516 InetAddress, 1517 nhdpLibRemovedIfAddrSetIpAddrPrefixLen 1518 InetAddressPrefixLength, 1519 nhdpLibRemovedIfAddrSetIfIndex 1520 InterfaceIndex, 1521 nhdpLibRemovedIfAddrSetIRTime 1522 TimeStamp 1523 } 1525 nhdpLibRemovedIfAddrSetIndex OBJECT-TYPE 1526 SYNTAX Integer32 (0..65535) 1527 MAX-ACCESS not-accessible 1528 STATUS current 1529 DESCRIPTION 1530 "The index for this table. Necessary 1531 because multiple addresses may be associated 1532 with a given nhdpIfIndex." 1533 REFERENCE 1534 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1535 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1536 C., and J. Dean, April 2011" 1537 ::= { nhdpLibRemovedIfAddrSetEntry 1 } 1539 nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE 1540 SYNTAX InetAddressType 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "The type of the nhdpLibRemovedIfAddrSetIpAddr 1545 in the InetAddress MIB (RFC 4001). 1547 Only the values 'ipv4(1)' and 1548 'ipv6(2)' are supported." 1549 REFERENCE 1550 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1551 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1552 C., and J. Dean, April 2011" 1553 ::= { nhdpLibRemovedIfAddrSetEntry 2 } 1555 nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE 1556 SYNTAX InetAddress (SIZE(4|16)) 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "nhdpLibRemovedIfAddrSetIpAddr is a 1561 recently used address of an interface of 1562 this router." 1564 REFERENCE 1565 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1566 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1567 C., and J. Dean, April 2011" 1568 ::= { nhdpLibRemovedIfAddrSetEntry 3 } 1570 nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE 1571 SYNTAX InetAddressPrefixLength 1572 MAX-ACCESS read-only 1573 STATUS current 1574 DESCRIPTION 1575 "Indicates the number of leading one bits that 1576 form the mask. The mask is logically ANDed 1577 to the nhdpLibRemovedIfAddrSetIpAddr to determine 1578 the address prefix. A row match is true 1579 if the address used as an index falls within 1580 the network address range defined by the 1581 address prefix." 1582 REFERENCE 1583 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1584 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1585 C., and J. Dean, April 2011" 1586 ::= { nhdpLibRemovedIfAddrSetEntry 4 } 1588 nhdpLibRemovedIfAddrSetIfIndex OBJECT-TYPE 1589 SYNTAX InterfaceIndex 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "Specifies the local IfIndex from which this 1594 IP address was recently removed." 1595 REFERENCE 1596 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1597 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1598 C., and J. Dean, April 2011" 1599 ::= { nhdpLibRemovedIfAddrSetEntry 5 } 1601 nhdpLibRemovedIfAddrSetIRTime OBJECT-TYPE 1602 SYNTAX TimeStamp 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "nhdpLibRemovedIfAddrSetIRTime specifies the value 1607 of sysUptime when this entry should expire and be 1608 removed from the nhdpLibRemovedIfAddrSetTable." 1609 REFERENCE 1610 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1611 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1612 C., and J. Dean, April 2011" 1613 ::= { nhdpLibRemovedIfAddrSetEntry 6 } 1615 -- 1616 -- nhdpStateObjGrp 1617 -- 1619 -- Contains information describing the current state of the NHDP 1620 -- process on this router. 1622 nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 } 1624 nhdpUpTime OBJECT-TYPE 1625 SYNTAX TimeStamp 1626 MAX-ACCESS read-only 1627 STATUS current 1628 DESCRIPTION 1629 "The value of sysUpTime at the time the current NHDP 1630 process was initialized." 1631 ::= { nhdpStateObjGrp 1 } 1633 nhdpInterfaceStateTable OBJECT-TYPE 1634 SYNTAX SEQUENCE OF NhdpInterfaceStateEntry 1635 MAX-ACCESS not-accessible 1636 STATUS current 1637 DESCRIPTION 1638 "nhdpInterfaceStateTable lists state information 1639 related to specific interfaces of this router. 1640 The value of nhdpIfIndex is an ifIndex from the 1641 interfaces group defined in the Interfaces Group 1642 MIB. 1644 The objects in this table are persistent, and when 1645 written, the entity SHOULD save the change to 1646 non-volatile storage." 1647 REFERENCE 1648 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1649 K., and F. Kastenholtz, June 2000." 1650 ::= { nhdpStateObjGrp 2 } 1652 nhdpInterfaceStateEntry OBJECT-TYPE 1653 SYNTAX NhdpInterfaceStateEntry 1654 MAX-ACCESS not-accessible 1655 STATUS current 1656 DESCRIPTION 1657 "nhdpInterfaceStateEntry describes one NHDP 1658 local interface state as indexed by 1659 its nhdpIfIndex." 1660 INDEX { nhdpIfIndex } 1661 ::= { nhdpInterfaceStateTable 1 } 1663 NhdpInterfaceStateEntry ::= 1664 SEQUENCE { 1665 nhdpIfStateUpTime 1666 TimeStamp 1667 } 1669 nhdpIfStateUpTime OBJECT-TYPE 1670 SYNTAX TimeStamp 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "The value of the sysUpTime when 1675 NHDP was last initialized on this 1676 MANET interface." 1677 ::= { nhdpInterfaceStateEntry 1 } 1679 -- 1680 -- This table allows for the mapping between discovered 1681 -- remote interfaces and routers and their addresses. 1682 -- 1684 nhdpDiscIfSetTable OBJECT-TYPE 1685 SYNTAX SEQUENCE OF NhdpDiscIfSetEntry 1686 MAX-ACCESS not-accessible 1687 STATUS current 1688 DESCRIPTION 1689 "A router's set of discovered interfaces on 1690 neighboring routers." 1691 REFERENCE 1692 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1693 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1694 C., and J. Dean, April 2011" 1695 ::= { nhdpStateObjGrp 3 } 1697 nhdpDiscIfSetEntry OBJECT-TYPE 1698 SYNTAX NhdpDiscIfSetEntry 1699 MAX-ACCESS not-accessible 1700 STATUS current 1701 DESCRIPTION 1702 "The entries include the nhdpDiscRouterIndex of 1703 the discovered router, the nhdpDiscIfIndex 1704 of the discovered interface, and the 1705 current set of addresses associated 1706 with this neighbor interface. The 1707 nhdpDiscIfIndex uniquely identifies 1708 the remote interface address sets 1709 through this table. It does not need 1710 to be unique across the MANET but MUST 1711 be locally unique within this router." 1712 REFERENCE 1713 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1714 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1715 C., and J. Dean, April 2011" 1716 INDEX { nhdpDiscIfSetIndex } 1717 ::= { nhdpDiscIfSetTable 1 } 1719 NhdpDiscIfSetEntry ::= 1720 SEQUENCE { 1721 nhdpDiscIfSetIndex 1722 Integer32, 1723 nhdpDiscIfIndex 1724 NeighborIfIndex, 1725 nhdpDiscRouterIndex 1726 NeighborRouterIndex, 1727 nhdpDiscIfSetIpAddrType 1728 InetAddressType, 1729 nhdpDiscIfSetIpAddr 1730 InetAddress, 1731 nhdpDiscIfSetIpAddrPrefixLen 1732 InetAddressPrefixLength 1733 } 1735 nhdpDiscIfSetIndex OBJECT-TYPE 1736 SYNTAX Integer32 (0..65535) 1737 MAX-ACCESS not-accessible 1738 STATUS current 1739 DESCRIPTION 1740 "The index for this table. Necessary 1741 because multiple addresses may be associated 1742 with a given nhdpDiscIfIndex." 1743 REFERENCE 1744 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1745 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1746 C., and J. Dean, April 2011" 1747 ::= { nhdpDiscIfSetEntry 1 } 1749 nhdpDiscIfIndex OBJECT-TYPE 1750 SYNTAX NeighborIfIndex 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "The NHDP interface index (locally created) 1755 of a neighbor's interface. Used for cross- 1756 indexing into other NHDP tables and other 1757 MIB modules." 1758 REFERENCE 1759 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1760 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1761 C., and J. Dean, April 2011" 1762 ::= { nhdpDiscIfSetEntry 2 } 1764 nhdpDiscRouterIndex OBJECT-TYPE 1765 SYNTAX NeighborRouterIndex 1766 MAX-ACCESS read-only 1767 STATUS current 1768 DESCRIPTION 1769 "The NHDP neighbor index (locally created) 1770 of a neighboring router. Used for cross- 1771 indexing into other NHDP tables and other 1772 MIB modules." 1773 REFERENCE 1774 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1775 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1776 C., and J. Dean, April 2011" 1777 ::= { nhdpDiscIfSetEntry 3 } 1779 nhdpDiscIfSetIpAddrType OBJECT-TYPE 1780 SYNTAX InetAddressType 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "The type of the nhdpDiscIfSetIpAddr 1785 in the InetAddress MIB (RFC 4001). 1787 Only the values 'ipv4(1)' and 1788 'ipv6(2)' are supported." 1789 REFERENCE 1790 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1791 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1792 C., and J. Dean, April 2011" 1793 ::= { nhdpDiscIfSetEntry 4 } 1795 nhdpDiscIfSetIpAddr OBJECT-TYPE 1796 SYNTAX InetAddress (SIZE(4|16)) 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The nhdpDiscIfSetIpAddr is a 1801 recently used address of a neighbor 1802 of this router." 1803 REFERENCE 1804 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1805 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1806 C., and J. Dean, April 2011" 1807 ::= { nhdpDiscIfSetEntry 5 } 1809 nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE 1810 SYNTAX InetAddressPrefixLength 1811 MAX-ACCESS read-only 1812 STATUS current 1813 DESCRIPTION 1814 "Indicates the number of leading one bits that 1815 form the mask. The mask is logically ANDed 1816 to the nhdpDiscIfSetIpAddr to determine 1817 the address prefix. A row match is true 1818 if the address used as an index falls within 1819 the network address range defined by the 1820 address prefix." 1821 REFERENCE 1822 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1823 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1824 C., and J. Dean, April 2011" 1825 ::= { nhdpDiscIfSetEntry 6 } 1827 -- Interface Information Base (IIB) 1829 -- 1830 -- Link Set 1831 -- 1833 nhdpIibLinkSetTable OBJECT-TYPE 1834 SYNTAX SEQUENCE OF NhdpIibLinkSetEntry 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "A Link Set of an interface records all links 1839 from other routers that are, or recently 1840 were, 1-hop neighbors." 1841 REFERENCE 1842 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1843 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1844 C., and J. Dean, April 2011" 1846 ::= { nhdpStateObjGrp 4 } 1848 nhdpIibLinkSetEntry OBJECT-TYPE 1849 SYNTAX NhdpIibLinkSetEntry 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "A Link Set consists of Link Tuples, each 1854 representing a single link indexed by the 1855 local and remote interface pair: 1857 (L_neighbor_iface_addr_list, L_HEARD_time, 1858 L_SYM_time, L_quality, L_pending, 1859 L_lost, L_time). 1861 The local interface is indexed via the 1862 nhdpIfIndex. The 1-hop interface is 1863 indexed via the nhdpDiscIfIndex. There 1864 SHOULD be an entry in this table for each 1865 local interface and associated 1-hop 1866 neighbor reachable on this local interface. 1868 Note that L_quality is not included in the 1869 entries below, because updates may be 1870 required too frequently." 1871 REFERENCE 1872 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1873 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1874 C., and J. Dean, April 2011" 1875 INDEX { nhdpIfIndex, 1876 nhdpDiscIfIndex } 1877 ::= { nhdpIibLinkSetTable 1 } 1879 NhdpIibLinkSetEntry ::= 1880 SEQUENCE { 1881 nhdpIibLinkSetLHeardTime 1882 TimeStamp, 1883 nhdpIibLinkSetLSymTime 1884 TimeStamp, 1885 nhdpIibLinkSetLPending 1886 TruthValue, 1887 nhdpIibLinkSetLLost 1888 TruthValue, 1889 nhdpIibLinkSetLTime 1890 TimeStamp 1891 } 1893 nhdpIibLinkSetLHeardTime OBJECT-TYPE 1894 SYNTAX TimeStamp 1895 MAX-ACCESS read-only 1896 STATUS current 1897 DESCRIPTION 1898 "nhdpIibLinkSetLHeardTime corresponds 1899 to L_HEARD_time of NHDP and represents the 1900 time up to which the MANET interface of the 1901 1-hop neighbor would be considered heard if 1902 not considering link quality." 1903 REFERENCE 1904 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1905 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1906 C., and J. Dean, April 2011" 1907 ::= { nhdpIibLinkSetEntry 1 } 1909 nhdpIibLinkSetLSymTime OBJECT-TYPE 1910 SYNTAX TimeStamp 1911 MAX-ACCESS read-only 1912 STATUS current 1913 DESCRIPTION 1914 "nhdpIibLinkSetLSymTime corresponds 1915 to L_SYM_time of NHDP and represents the time 1916 up to which the link to the 1-hop neighbor 1917 would be considered symmetric if not considering 1918 link quality." 1919 REFERENCE 1920 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1921 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1922 C., and J. Dean, April 2011" 1923 ::= { nhdpIibLinkSetEntry 2 } 1925 nhdpIibLinkSetLPending OBJECT-TYPE 1926 SYNTAX TruthValue 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "nhdpIibLinkSetLPending corresponds 1931 to L_pending of NHDP and is a boolean flag, 1932 describing if a link is considered pending 1933 (i.e., a candidate, but not yet established, 1934 link)." 1935 REFERENCE 1936 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1937 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1938 C., and J. Dean, April 2011" 1939 ::= { nhdpIibLinkSetEntry 3 } 1941 nhdpIibLinkSetLLost OBJECT-TYPE 1942 SYNTAX TruthValue 1943 MAX-ACCESS read-only 1944 STATUS current 1945 DESCRIPTION 1946 "nhdpIibLinkSetLLost corresponds 1947 to L_lost of NHDP and is a boolean flag, 1948 describing if a link is considered lost due 1949 to low link quality." 1950 REFERENCE 1951 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1952 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1953 C., and J. Dean, April 2011" 1954 ::= { nhdpIibLinkSetEntry 4 } 1956 nhdpIibLinkSetLTime OBJECT-TYPE 1957 SYNTAX TimeStamp 1958 MAX-ACCESS read-only 1959 STATUS current 1960 DESCRIPTION 1961 "nhdpIibLinkSetLTime specifies the value 1962 of sysUptime when this entry should expire and be 1963 removed from the nhdpIibLinkSetTable." 1964 REFERENCE 1965 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1966 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1967 C., and J. Dean, April 2011" 1968 ::= { nhdpIibLinkSetEntry 5 } 1970 -- 1971 -- 2-Hop Set 1972 -- 1973 nhdpIib2HopSetTable OBJECT-TYPE 1974 SYNTAX SEQUENCE OF NhdpIib2HopSetEntry 1975 MAX-ACCESS not-accessible 1976 STATUS current 1977 DESCRIPTION 1978 "A 2-Hop Set of an interface records network 1979 addresses of symmetric 2-hop neighbors and 1980 the symmetric links to symmetric 1-hop neighbors 1981 through which these symmetric 2-hop neighbors 1982 can be reached. It consists of 2-Hop Tuples." 1983 REFERENCE 1984 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1985 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1986 C., and J. Dean, April 2011" 1987 ::= { nhdpStateObjGrp 5 } 1988 nhdpIib2HopSetEntry OBJECT-TYPE 1989 SYNTAX NhdpIib2HopSetEntry 1990 MAX-ACCESS not-accessible 1991 STATUS current 1992 DESCRIPTION 1993 "nhdpIib2HopSetTable consists of 2-Hop Tuples, each 1994 representing a single network address of a symmetric 1995 2-hop neighbor and a single MANET interface of a 1996 symmetric 1-hop neighbor. 1998 (N2_neighbor_iface_addr_list, 1999 N2_2hop_addr, N2_lost, N2_time). 2001 The entries include: 2002 - the 2-hop neighbor addresses 2003 ('N2_neighbor_iface_addr_list'), which 2004 act as the table index, 2005 - the associated symmetric 1-hop 2006 neighbor address set ('N2_2hop_addr'), designated 2007 through nhdpDiscIfIndex, 2008 - a flag indicating if the 1-hop neighbor 2009 through which this 2-hop neighbor is reachable 2010 ('N2_lost') is considered lost due to link quality, 2011 or not, 2012 - and the expiration time ('N2_time'). 2014 The nhdpIfIndex in the INDEX is the interface index of 2015 the local interface through which these 2-hop addresses 2016 are accessible. The nhdpDiscIfIndex in the INDEX 2017 represents the 1-hop neighbor interface through which 2018 these 2-hop neighbor addresses are reachable." 2020 REFERENCE 2021 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2022 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2023 C., and J. Dean, April 2011, 2024 and 2025 RFC 7466 - 2026 An Optimization for the Mobile Ad Hoc Network (MANET) 2027 Neighborhood Discovery Protocol (NHDP), 2028 Dearlove, C., and T. Clausen, 2029 March 2015" 2030 INDEX { nhdpIfIndex, 2031 nhdpDiscIfIndex, 2032 nhdpIib2HopSetIpAddressType, 2033 nhdpIib2HopSetIpAddress 2034 } 2035 ::= { nhdpIib2HopSetTable 1 } 2036 NhdpIib2HopSetEntry ::= 2037 SEQUENCE { 2038 nhdpIib2HopSetIpAddressType 2039 InetAddressType, 2040 nhdpIib2HopSetIpAddress 2041 InetAddress, 2042 nhdpIib2HopSetIpAddrPrefixLen 2043 InetAddressPrefixLength, 2044 nhdpIib2HopSet1HopIfIndex 2045 NeighborIfIndex, 2046 nhdpIib2HopSetN2Time 2047 TimeStamp, 2048 nhdpIib2HopSetN2Lost 2049 TruthValue 2050 } 2052 nhdpIib2HopSetIpAddressType OBJECT-TYPE 2053 SYNTAX InetAddressType 2054 MAX-ACCESS not-accessible 2055 STATUS current 2056 DESCRIPTION 2057 "The type of the nhdpIib2HopSetIpAddress 2058 in the InetAddress MIB module (RFC 4001). 2060 Only the values 'ipv4(1)' and 2061 'ipv6(2)' are supported." 2062 REFERENCE 2063 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2064 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2065 C., and J. Dean, April 2011" 2066 ::= { nhdpIib2HopSetEntry 1 } 2068 nhdpIib2HopSetIpAddress OBJECT-TYPE 2069 SYNTAX InetAddress (SIZE(4|16)) 2070 MAX-ACCESS not-accessible 2071 STATUS current 2072 DESCRIPTION 2073 "nhdpIib2HopSetIpAddr corresponds 2074 to N2_2hop_addr of NHDP and is a network 2075 address of a symmetric 2-hop neighbor that 2076 has a symmetric link (using any MANET 2077 interface) to the indicated symmetric 2078 1-hop neighbor." 2079 REFERENCE 2080 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2081 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2082 C., and J. Dean, April 2011" 2083 ::= { nhdpIib2HopSetEntry 2 } 2084 nhdpIib2HopSetIpAddrPrefixLen OBJECT-TYPE 2085 SYNTAX InetAddressPrefixLength 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "Indicates the number of leading one bits that 2090 form the mask. The mask is logically ANDed 2091 to the nhdpIib2HopSetIpAddress to determine 2092 the address prefix. A row match is true 2093 if the address used as an index falls within 2094 the network address range defined by the 2095 address prefix." 2096 REFERENCE 2097 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2098 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2099 C., and J. Dean, April 2011" 2100 ::= { nhdpIib2HopSetEntry 3 } 2102 nhdpIib2HopSet1HopIfIndex OBJECT-TYPE 2103 SYNTAX NeighborIfIndex 2104 MAX-ACCESS read-only 2105 STATUS current 2106 DESCRIPTION 2107 "nhdpIib2HopSet1HopIfIndex is 2108 nhdpDiscIfIndex of the 1-hop 2109 neighbor that communicated the ipAddress 2110 of the 2-hop neighbor in this row entry." 2111 REFERENCE 2112 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2113 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2114 C., and J. Dean, April 2011" 2115 ::= { nhdpIib2HopSetEntry 4 } 2117 nhdpIib2HopSetN2Time OBJECT-TYPE 2118 SYNTAX TimeStamp 2119 MAX-ACCESS read-only 2120 STATUS current 2121 DESCRIPTION 2122 "nhdpIib2HopSetN2Time specifies the value 2123 of sysUptime when this entry should expire and be 2124 removed from the nhdpIib2HopSetTable." 2125 REFERENCE 2126 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2127 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2128 C., and J. Dean, April 2011" 2129 ::= { nhdpIib2HopSetEntry 5 } 2130 nhdpIib2HopSetN2Lost OBJECT-TYPE 2131 SYNTAX TruthValue 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and 2136 is a boolean flag, describing if for a 2-Hop Tuple, the 2137 corresponding Link Tuple currently is considered lost 2138 due to link quality." 2140 REFERENCE 2141 "RFC 7466 - 2142 An Optimization for the Mobile Ad Hoc Network (MANET) 2143 Neighborhood Discovery Protocol (NHDP), 2144 Dearlove, C., and T. Clausen, 2145 March 2015" 2146 ::= {nhdpIib2HopSetEntry 6} 2148 -- 2149 -- Neighbor Information Base (NIB) 2150 -- 2151 -- Each router maintains a Neighbor Information Base 2152 -- that records information about addresses of 2153 -- current and recently symmetric 1-hop neighbors. 2155 -- 2156 -- Neighbor Set 2157 -- 2158 -- The Neighbor Set Table is small because 2159 -- most of the corresponding information is found 2160 -- in the nhdpDiscoveredIfTable above. 2161 -- 2163 nhdpNibNeighborSetTable OBJECT-TYPE 2164 SYNTAX SEQUENCE OF NhdpNibNeighborSetEntry 2165 MAX-ACCESS not-accessible 2166 STATUS current 2167 DESCRIPTION 2168 "A router's Neighbor Set records all 2169 network addresses of each 1-hop 2170 neighbor." 2171 REFERENCE 2172 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2173 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2174 C., and J. Dean, April 2011" 2175 ::= { nhdpStateObjGrp 6 } 2176 nhdpNibNeighborSetEntry OBJECT-TYPE 2177 SYNTAX NhdpNibNeighborSetEntry 2178 MAX-ACCESS not-accessible 2179 STATUS current 2180 DESCRIPTION 2181 "A router's Neighbor Set consists 2182 of Neighbor Tuples, each representing 2183 a single 1-hop neighbor: 2185 (N_neighbor_addr_list, N_symmetric)" 2186 REFERENCE 2187 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2188 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2189 C., and J. Dean, April 2011" 2190 INDEX { nhdpDiscRouterIndex } 2191 ::= { nhdpNibNeighborSetTable 1 } 2193 NhdpNibNeighborSetEntry ::= 2194 SEQUENCE { 2195 nhdpNibNeighborSetNSymmetric 2196 TruthValue 2197 } 2199 nhdpNibNeighborSetNSymmetric OBJECT-TYPE 2200 SYNTAX TruthValue 2201 MAX-ACCESS read-only 2202 STATUS current 2203 DESCRIPTION 2204 "nhdpNibNeighborNSymmetric corresponds 2205 to N_symmetric of NHDP and is a boolean flag, 2206 describing if this is a symmetric 1-hop neighbor." 2207 REFERENCE 2208 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2209 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2210 C., and J. Dean, April 2011" 2211 ::= { nhdpNibNeighborSetEntry 1 } 2213 -- 2214 -- Lost Neighbor Set 2215 -- 2216 nhdpNibLostNeighborSetTable OBJECT-TYPE 2217 SYNTAX SEQUENCE OF NhdpNibLostNeighborSetEntry 2218 MAX-ACCESS not-accessible 2219 STATUS current 2220 DESCRIPTION 2221 "A router's Lost Neighbor Set records network 2222 addresses of routers that were recently 2223 symmetric 1-hop neighbors but are now 2224 advertised as lost." 2225 REFERENCE 2226 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2227 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2228 C., and J. Dean, April 2011" 2229 ::= { nhdpStateObjGrp 7 } 2231 nhdpNibLostNeighborSetEntry OBJECT-TYPE 2232 SYNTAX NhdpNibLostNeighborSetEntry 2233 MAX-ACCESS not-accessible 2234 STATUS current 2235 DESCRIPTION 2236 "A router's Lost Neighbor Set consists of 2237 Lost Neighbor Tuples, each representing a 2238 single such network address: 2240 (NL_neighbor_addr, NL_time)" 2241 REFERENCE 2242 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2243 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2244 C., and J. Dean, April 2011" 2245 INDEX { nhdpDiscRouterIndex } 2246 ::= { nhdpNibLostNeighborSetTable 1 } 2248 NhdpNibLostNeighborSetEntry ::= 2249 SEQUENCE { 2250 nhdpNibLostNeighborSetNLTime 2251 TimeStamp 2252 } 2254 nhdpNibLostNeighborSetNLTime OBJECT-TYPE 2255 SYNTAX TimeStamp 2256 MAX-ACCESS read-only 2257 STATUS current 2258 DESCRIPTION 2259 "nhdpNibLostNeighborSetNLTime 2260 specifies the value of sysUptime when this entry 2261 should expire and be removed from the 2262 nhdpNibLostNeighborSetTable." 2263 REFERENCE 2264 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2265 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2266 C., and J. Dean, April 2011" 2267 ::= { nhdpNibLostNeighborSetEntry 1 } 2269 -- 2270 -- nhdpPerformanceObjGrp 2271 -- 2273 -- Contains objects that help to characterize the performance of 2274 -- the NHDP process, typically counters. 2275 -- 2276 nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 } 2278 -- 2279 -- Objects per local interface 2280 -- 2282 nhdpInterfacePerfTable OBJECT-TYPE 2283 SYNTAX SEQUENCE OF NhdpInterfacePerfEntry 2284 MAX-ACCESS not-accessible 2285 STATUS current 2286 DESCRIPTION 2287 "This table summarizes performance objects that are 2288 measured per local NHDP interface. 2289 nhdpIfPerfCounterDiscontinuityTime indicates 2290 the most recent occasion at which any one or more 2291 of this interface's counters listed in this table 2292 suffered a discontinuity." 2293 REFERENCE 2294 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2295 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2296 C., and J. Dean, April 2011" 2297 ::= { nhdpPerformanceObjGrp 1 } 2299 nhdpInterfacePerfEntry OBJECT-TYPE 2300 SYNTAX NhdpInterfacePerfEntry 2301 MAX-ACCESS not-accessible 2302 STATUS current 2303 DESCRIPTION 2304 "A single entry contains performance counters for 2305 a local NHDP interface." 2306 INDEX { nhdpIfIndex } 2307 ::= { nhdpInterfacePerfTable 1 } 2309 NhdpInterfacePerfEntry ::= 2310 SEQUENCE { 2311 nhdpIfHelloMessageXmits 2312 Counter32, 2313 nhdpIfHelloMessageRecvd 2314 Counter32, 2315 nhdpIfHelloMessageXmitAccumulatedSize 2316 Counter64, 2318 nhdpIfHelloMessageRecvdAccumulatedSize 2319 Counter64, 2320 nhdpIfHelloMessageTriggeredXmits 2321 Counter32, 2322 nhdpIfHelloMessagePeriodicXmits 2323 Counter32, 2324 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount 2325 Counter32, 2326 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount 2327 Counter32, 2328 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount 2329 Counter32, 2330 nhdpIfPerfCounterDiscontinuityTime 2331 TimeStamp 2332 } 2334 nhdpIfHelloMessageXmits OBJECT-TYPE 2335 SYNTAX Counter32 2336 UNITS "messages" 2337 MAX-ACCESS read-only 2338 STATUS current 2339 DESCRIPTION 2340 "A counter is incremented each time a HELLO 2341 message has been transmitted on that interface." 2342 ::= { nhdpInterfacePerfEntry 1 } 2344 nhdpIfHelloMessageRecvd OBJECT-TYPE 2345 SYNTAX Counter32 2346 UNITS "messages" 2347 MAX-ACCESS read-only 2348 STATUS current 2349 DESCRIPTION 2350 "A counter is incremented each time a 2351 HELLO message has been received on that interface." 2352 ::= { nhdpInterfacePerfEntry 2 } 2354 nhdpIfHelloMessageXmitAccumulatedSize OBJECT-TYPE 2355 SYNTAX Counter64 2356 UNITS "octets" 2357 MAX-ACCESS read-only 2358 STATUS current 2359 DESCRIPTION 2360 "A counter is incremented by the number of octets in 2361 a HELLO message each time a 2362 HELLO message has been sent." 2363 ::= { nhdpInterfacePerfEntry 3 } 2365 nhdpIfHelloMessageRecvdAccumulatedSize OBJECT-TYPE 2366 SYNTAX Counter64 2367 UNITS "octets" 2368 MAX-ACCESS read-only 2369 STATUS current 2370 DESCRIPTION 2371 "A counter is incremented by the number of octets in 2372 a HELLO message each time a 2373 HELLO message has been received." 2374 ::= { nhdpInterfacePerfEntry 4 } 2376 nhdpIfHelloMessageTriggeredXmits OBJECT-TYPE 2377 SYNTAX Counter32 2378 UNITS "messages" 2379 MAX-ACCESS read-only 2380 STATUS current 2381 DESCRIPTION 2382 "A counter is incremented each time a triggered 2383 HELLO message has been sent." 2384 ::= { nhdpInterfacePerfEntry 5 } 2386 nhdpIfHelloMessagePeriodicXmits OBJECT-TYPE 2387 SYNTAX Counter32 2388 UNITS "messages" 2389 MAX-ACCESS read-only 2390 STATUS current 2391 DESCRIPTION 2392 "A counter is incremented each time a periodic 2393 HELLO message has been sent." 2394 ::= { nhdpInterfacePerfEntry 6 } 2396 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount OBJECT-TYPE 2397 SYNTAX Counter32 2398 UNITS "neighbors" 2399 MAX-ACCESS read-only 2400 STATUS current 2401 DESCRIPTION 2402 "A counter is incremented by the number of advertised 2403 symmetric neighbors in a HELLO each time a HELLO 2404 message has been sent." 2405 ::= { nhdpInterfacePerfEntry 7 } 2407 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount OBJECT-TYPE 2408 SYNTAX Counter32 2409 UNITS "neighbors" 2410 MAX-ACCESS read-only 2411 STATUS current 2412 DESCRIPTION 2413 "A counter is incremented by the number of advertised 2414 heard neighbors in a HELLO each time a HELLO 2415 message has been sent." 2416 ::= { nhdpInterfacePerfEntry 8 } 2418 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount OBJECT-TYPE 2419 SYNTAX Counter32 2420 UNITS "neighbors" 2421 MAX-ACCESS read-only 2422 STATUS current 2423 DESCRIPTION 2424 "A counter is incremented by the number of advertised 2425 lost neighbors in a HELLO each time a HELLO 2426 message has been sent." 2427 ::= { nhdpInterfacePerfEntry 9 } 2429 nhdpIfPerfCounterDiscontinuityTime OBJECT-TYPE 2430 SYNTAX TimeStamp 2431 MAX-ACCESS read-only 2432 STATUS current 2433 DESCRIPTION 2434 "The value of sysUpTime on the most recent occasion at which 2435 any one or more of this interface's counters suffered a 2436 discontinuity. If no such discontinuities have occurred 2437 since the last reinitialization of the local management 2438 subsystem, then this object contains a zero value." 2439 ::= { nhdpInterfacePerfEntry 10 } 2441 -- 2442 -- Objects per discovered neighbor interface 2443 -- 2444 nhdpDiscIfSetPerfTable OBJECT-TYPE 2445 SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry 2446 MAX-ACCESS not-accessible 2447 STATUS current 2448 DESCRIPTION 2449 "A router's set of performance properties for 2450 each discovered interface of a neighbor." 2451 REFERENCE 2452 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2453 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2454 C., and J. Dean, April 2011" 2455 ::= { nhdpPerformanceObjGrp 2 } 2457 nhdpDiscIfSetPerfEntry OBJECT-TYPE 2458 SYNTAX NhdpDiscIfSetPerfEntry 2459 MAX-ACCESS not-accessible 2460 STATUS current 2461 DESCRIPTION 2462 "There is an entry for each discovered 2463 interface of a neighbor." 2464 REFERENCE 2465 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2466 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2467 C., and J. Dean, April 2011" 2468 INDEX { nhdpDiscIfIndex } 2469 ::= { nhdpDiscIfSetPerfTable 1 } 2471 NhdpDiscIfSetPerfEntry ::= 2472 SEQUENCE { 2473 nhdpDiscIfRecvdPackets 2474 Counter32, 2475 nhdpDiscIfExpectedPackets 2476 Counter32 2477 } 2479 nhdpDiscIfRecvdPackets OBJECT-TYPE 2480 SYNTAX Counter32 2481 UNITS "packets" 2482 MAX-ACCESS read-only 2483 STATUS current 2484 DESCRIPTION 2485 "This counter increments each 2486 time this router receives a packet from that interface 2487 of the neighbor." 2488 REFERENCE 2489 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2490 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2491 C., and J. Dean, April 2011" 2492 ::= { nhdpDiscIfSetPerfEntry 1 } 2494 nhdpDiscIfExpectedPackets OBJECT-TYPE 2495 SYNTAX Counter32 2496 UNITS "packets" 2497 MAX-ACCESS read-only 2498 STATUS current 2499 DESCRIPTION 2500 "This counter increments by the number 2501 of missed packets from this neighbor based 2502 on the packet sequence number each time this 2503 router receives a packet from that interface 2504 of the neighbor." 2505 REFERENCE 2506 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2507 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2508 C., and J. Dean, April 2011" 2509 ::= { nhdpDiscIfSetPerfEntry 2 } 2511 -- 2512 -- Objects concerning the Neighbor Set 2513 -- 2514 nhdpNibNeighborSetChanges OBJECT-TYPE 2515 SYNTAX Counter32 2516 UNITS "changes" 2517 MAX-ACCESS read-only 2518 STATUS current 2519 DESCRIPTION 2520 "This counter increments each time the Neighbor Set changes. 2521 A change occurs whenever a new Neighbor Tuple has been 2522 added, a Neighbor Tuple has been removed, or any entry of 2523 a Neighbor Tuple has been modified." 2524 ::= { nhdpPerformanceObjGrp 3 } 2526 -- 2527 -- Objects per discovered neighbor 2528 -- 2529 nhdpDiscNeighborSetPerfTable OBJECT-TYPE 2530 SYNTAX SEQUENCE OF NhdpDiscNeighborSetPerfEntry 2531 MAX-ACCESS not-accessible 2532 STATUS current 2533 DESCRIPTION 2534 "A router's set of discovered neighbors and 2535 their properties." 2536 REFERENCE 2537 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2538 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2539 C., and J. Dean, April 2011" 2540 ::= { nhdpPerformanceObjGrp 4 } 2542 nhdpDiscNeighborSetPerfEntry OBJECT-TYPE 2543 SYNTAX NhdpDiscNeighborSetPerfEntry 2544 MAX-ACCESS not-accessible 2545 STATUS current 2546 DESCRIPTION 2547 "The entries include the nhdpDiscRouterIndex of 2548 the discovered router as well as performance 2549 objects related to changes of the Neighbor 2550 Set." 2552 REFERENCE 2553 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2554 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2555 C., and J. Dean, April 2011" 2556 INDEX { nhdpDiscRouterIndex } 2557 ::= { nhdpDiscNeighborSetPerfTable 1 } 2559 NhdpDiscNeighborSetPerfEntry ::= 2560 SEQUENCE { 2561 nhdpDiscNeighborNibNeighborSetChanges 2562 Counter32, 2563 nhdpDiscNeighborNibNeighborSetUpTime 2564 TimeStamp, 2565 nhdpDiscNeighborNibNeighborSetReachableLinkChanges 2566 Counter32 2567 } 2569 nhdpDiscNeighborNibNeighborSetChanges OBJECT-TYPE 2570 SYNTAX Counter32 2571 UNITS "changes" 2572 MAX-ACCESS read-only 2573 STATUS current 2574 DESCRIPTION 2575 "This object returns the number of changes 2576 to the given Neighbor Tuple." 2577 REFERENCE 2578 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2579 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2580 C., and J. Dean, April 2011" 2581 ::= { nhdpDiscNeighborSetPerfEntry 1 } 2583 nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE 2584 SYNTAX TimeStamp 2585 MAX-ACCESS read-only 2586 STATUS current 2587 DESCRIPTION 2588 "This object returns the sysUpTime when 2589 a new nhdpNibNeighborSetEntry 2590 has been created for a particular 2591 nhdpNibNeighborSetRouterIndex." 2592 REFERENCE 2593 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2594 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2595 C., and J. Dean, April 2011" 2596 ::= { nhdpDiscNeighborSetPerfEntry 2 } 2598 nhdpDiscNeighborNibNeighborSetReachableLinkChanges OBJECT-TYPE 2599 SYNTAX Counter32 2600 UNITS "changes" 2601 MAX-ACCESS read-only 2602 STATUS current 2603 DESCRIPTION 2604 "This object counts each time the neighbor changes 2605 the interface(s) over which it is reachable. 2606 A change in the set of Link Tuples corresponding 2607 to the appropriate Neighbor Tuple is registered, 2608 i.e., a corresponding Link Tuple is added or removed 2609 from the set of all corresponding Link Tuples." 2610 REFERENCE 2611 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2612 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2613 C., and J. Dean, April 2011" 2614 ::= { nhdpDiscNeighborSetPerfEntry 3 } 2616 -- 2617 -- Objects per discovered 2-hop neighbor 2618 -- 2619 nhdpIib2HopSetPerfTable OBJECT-TYPE 2620 SYNTAX SEQUENCE OF NhdpIib2HopSetPerfEntry 2621 MAX-ACCESS not-accessible 2622 STATUS current 2623 DESCRIPTION 2624 "This table contains performance objects per 2625 discovered 2-hop neighbor." 2626 REFERENCE 2627 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2628 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2629 C., and J. Dean, April 2011" 2630 ::= { nhdpPerformanceObjGrp 5 } 2632 nhdpIib2HopSetPerfEntry OBJECT-TYPE 2633 SYNTAX NhdpIib2HopSetPerfEntry 2634 MAX-ACCESS not-accessible 2635 STATUS current 2636 DESCRIPTION 2637 "The entries contain performance objects per 2638 discovered 2-hop neighbor." 2639 REFERENCE 2640 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2641 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2642 C., and J. Dean, April 2011" 2643 INDEX { nhdpDiscRouterIndex } 2645 ::= { nhdpIib2HopSetPerfTable 1 } 2647 NhdpIib2HopSetPerfEntry ::= 2648 SEQUENCE { 2649 nhdpIib2HopSetPerfChanges 2650 Counter32, 2651 nhdpIib2HopSetPerfUpTime 2652 TimeStamp 2653 } 2655 nhdpIib2HopSetPerfChanges OBJECT-TYPE 2656 SYNTAX Counter32 2657 UNITS "changes" 2658 MAX-ACCESS read-only 2659 STATUS current 2660 DESCRIPTION 2661 "This object counts the changes of the union of all 2662 N2_neighbor_iface_addr_list of 2-Hop Tuples with an 2663 N2_2hop_addr equal to one of the given 2-hop 2664 neighbor's addresses." 2665 REFERENCE 2666 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2667 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2668 C., and J. Dean, April 2011" 2669 ::= { nhdpIib2HopSetPerfEntry 1 } 2671 nhdpIib2HopSetPerfUpTime OBJECT-TYPE 2672 SYNTAX TimeStamp 2673 MAX-ACCESS read-only 2674 STATUS current 2675 DESCRIPTION 2676 "This object returns the sysUpTime 2677 when the 2-Hop Tuple 2678 corresponding to the given 2-hop neighbor IP address 2679 was registered in the nhdpIib2HopSetTable." 2680 REFERENCE 2681 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2682 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2683 C., and J. Dean, April 2011" 2684 ::= { nhdpIib2HopSetPerfEntry 2 } 2686 -- 2687 -- nhdpNotifications 2688 -- 2689 nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 0 } 2690 nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 } 2691 nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 2 } 2693 -- nhdpNotificationsObjects 2695 nhdpNbrStateChange NOTIFICATION-TYPE 2696 OBJECTS { nhdpIfName, -- The originator of the notification. 2697 nhdpNbrState -- The new state 2698 } 2699 STATUS current 2700 DESCRIPTION 2701 "nhdpNbrStateChange is a notification sent when 2702 more than nhdpNbrStateChangeThreshold neighbors change 2703 their status (i.e., 'down(0)', 'asymmetric(1)', or 2704 'symmetric(2)') within a time window of 2705 nhdpNbrStateChangeWindow." 2706 ::= { nhdpNotificationsObjects 1 } 2708 nhdp2HopNbrStateChange NOTIFICATION-TYPE 2709 OBJECTS { nhdpIfName, -- The originator 2710 -- of the notification 2711 nhdp2HopNbrState -- The new state 2712 } 2713 STATUS current 2714 DESCRIPTION 2715 "nhdp2HopNbrStateChange is a notification sent 2716 when more than nhdp2HopNbrStateChangeThreshold 2-hop 2717 neighbors change their nhdp2HopNbrState 2718 within a time window of 2719 nhdp2HopNbrStateChangeWindow." 2720 ::= { nhdpNotificationsObjects 2 } 2722 nhdpIfStateChange NOTIFICATION-TYPE 2723 OBJECTS { nhdpIfName, -- The local interface 2724 nhdpIfStatus -- The new status 2725 } 2726 STATUS current 2727 DESCRIPTION 2728 "nhdpIfStateChange is a notification sent when 2729 nhdpIfStatus has changed on this interface." 2730 ::= { nhdpNotificationsObjects 3 } 2732 -- nhdpNotificationsControl 2734 nhdpNbrStateChangeThreshold OBJECT-TYPE 2735 SYNTAX Integer32 (0..255) 2736 UNITS "changes" 2737 MAX-ACCESS read-write 2738 STATUS current 2739 DESCRIPTION 2740 "A threshold value for the 2741 nhdpNbrStateChange object. If the 2742 number of occurrences exceeds this threshold 2743 within the previous nhdpNbrStateChangeWindow, 2744 then the nhdpNbrStateChange notification 2745 is to be sent. 2747 It is recommended that the value of this 2748 threshold be set to at least 10 and higher 2749 in dense topologies with frequent expected 2750 topology changes." 2751 DEFVAL { 10 } 2752 ::= { nhdpNotificationsControl 1 } 2754 nhdpNbrStateChangeWindow OBJECT-TYPE 2755 SYNTAX TimeTicks 2756 MAX-ACCESS read-write 2757 STATUS current 2758 DESCRIPTION 2759 "A time window for the 2760 nhdpNbrStateChange object. If the 2761 number of occurrences exceeds the 2762 nhdpNbrStateChangeThreshold 2763 within the previous nhdpNbrStateChangeWindow, 2764 then the nhdpNbrStateChange notification 2765 is to be sent. 2767 It is recommended that the value for this 2768 window be set to at least 5 times the 2769 nhdpHelloInterval. 2771 This object represents the time in hundredths 2772 of a second." 2773 DEFVAL { 1000 } 2774 ::= { nhdpNotificationsControl 2 } 2776 nhdp2HopNbrStateChangeThreshold OBJECT-TYPE 2777 SYNTAX Integer32 (0..255) 2778 UNITS "changes" 2779 MAX-ACCESS read-write 2780 STATUS current 2781 DESCRIPTION 2782 "A threshold value for the 2783 nhdp2HopNbrStateChange object. If the 2784 number of occurrences exceeds this threshold 2785 within the previous nhdp2HopNbrStateChangeWindow, 2786 then the nhdp2HopNbrStateChange notification 2787 is to be sent. 2789 It is recommended that the value of this 2790 threshold be set to at least 10 and higher 2791 when topologies are expected to be highly dynamic." 2792 DEFVAL { 10 } 2793 ::= { nhdpNotificationsControl 3 } 2795 nhdp2HopNbrStateChangeWindow OBJECT-TYPE 2796 SYNTAX TimeTicks 2797 MAX-ACCESS read-write 2798 STATUS current 2799 DESCRIPTION 2800 "A time window for the 2801 nhdp2HopNbrStateChange object. If the 2802 number of occurrences exceeds the 2803 nhdp2HopNbrStateChangeThreshold 2804 within the previous nhdp2HopNbrStateChangeWindow, 2805 then the nhdp2HopNbrStateChange notification 2806 is to be sent. 2808 It is recommended that the value for this 2809 window be set to at least 5 times 2810 nhdpHelloInterval. 2812 This object represents the time in hundredths 2813 of a second." 2814 DEFVAL { 1000 } 2815 ::= { nhdpNotificationsControl 4 } 2817 -- nhdpNotificationStates 2819 nhdpNbrState OBJECT-TYPE 2820 SYNTAX INTEGER { 2821 down(0), 2822 asymmetric(1), 2823 symmetric(2) 2824 } 2825 MAX-ACCESS read-only 2826 STATUS current 2827 DESCRIPTION 2828 "NHDP neighbor states. In NHDP, it is not 2829 necessary to remove Protocol Tuples from Protocol Sets 2830 at the exact time indicated, only to behave as if the 2831 Protocol Tuples were removed at that time. This case is 2832 indicated here as 'down(0)', all other cases being 2833 indicated as 'asymmetric(1)' or 'symmetric(2)'. If 'down(0)', 2834 the direct neighbor is also added to the 2835 nhdpNibLostNeighborSetTable." 2836 ::= { nhdpNotificationsStates 1 } 2838 nhdp2HopNbrState OBJECT-TYPE 2839 SYNTAX INTEGER { 2840 down(0), 2841 up(1), 2842 notconsidered(2) 2843 } 2844 MAX-ACCESS read-only 2845 STATUS current 2846 DESCRIPTION 2847 "NHDP 2-hop neighbor states. In NHDP, it is not necessary 2848 to remove Protocol Tuples from Protocol Sets at the 2849 exact time indicated, only to behave as if the Protocol 2850 Tuples were removed at that time. This case is indicated 2851 here as 'down(0)'; otherwise, it is either 'up(1)', if 2852 N2_lost for the 2-Hop Tuple is equal to false, or 2853 'notconsidered(2)' otherwise." 2854 ::= { nhdpNotificationsStates 2 } 2856 -- 2857 -- nhdpConformance information 2858 -- 2860 nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 } 2861 nhdpMIBGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 } 2863 -- Compliance Statements 2864 nhdpBasicCompliance MODULE-COMPLIANCE 2865 STATUS current 2866 DESCRIPTION 2867 "The basic implementation requirements for 2868 managed network entities that implement 2869 NHDP." 2870 MODULE -- this module 2871 MANDATORY-GROUPS { nhdpConfigurationGroup } 2872 ::= { nhdpCompliances 1 } 2874 nhdpFullCompliance2 MODULE-COMPLIANCE 2875 STATUS current 2876 DESCRIPTION 2877 "The full implementation requirements for 2878 managed network entities that implement 2879 NHDP." 2880 MODULE -- this module 2881 MANDATORY-GROUPS { nhdpConfigurationGroup, 2882 nhdpStateGroup2, 2883 nhdpNotificationObjectGroup, 2884 nhdpNotificationGroup, 2885 nhdpPerformanceGroup 2886 } 2887 ::= { nhdpCompliances 3 } 2889 -- 2890 -- Units of Conformance 2891 -- 2893 nhdpConfigurationGroup OBJECT-GROUP 2894 OBJECTS { 2895 nhdpIfName, 2896 nhdpIfStatus, 2897 nhdpHelloInterval, 2898 nhdpHelloMinInterval, 2899 nhdpRefreshInterval, 2900 nhdpLHoldTime, 2901 nhdpHHoldTime, 2902 nhdpHystAcceptQuality, 2903 nhdpHystRejectQuality, 2904 nhdpInitialQuality, 2905 nhdpInitialPending, 2906 nhdpHpMaxJitter, 2907 nhdpHtMaxJitter, 2908 nhdpNHoldTime, 2909 nhdpIHoldTime, 2910 nhdpIfRowStatus, 2911 nhdpLibLocalIfSetIfIndex, 2912 nhdpLibLocalIfSetIpAddrType, 2913 nhdpLibLocalIfSetIpAddr, 2914 nhdpLibLocalIfSetIpAddrPrefixLen, 2915 nhdpLibLocalIfSetRowStatus, 2916 nhdpLibRemovedIfAddrSetIpAddrType, 2917 nhdpLibRemovedIfAddrSetIpAddr, 2918 nhdpLibRemovedIfAddrSetIpAddrPrefixLen, 2919 nhdpLibRemovedIfAddrSetIfIndex, 2920 nhdpLibRemovedIfAddrSetIRTime 2921 } 2922 STATUS current 2923 DESCRIPTION 2924 "Set of NHDP configuration objects implemented 2925 in this module." 2926 ::= { nhdpMIBGroups 2 } 2928 nhdpPerformanceGroup OBJECT-GROUP 2929 OBJECTS { 2930 nhdpIfHelloMessageXmits, 2931 nhdpIfHelloMessageRecvd, 2932 nhdpIfHelloMessageXmitAccumulatedSize, 2933 nhdpIfHelloMessageRecvdAccumulatedSize, 2934 nhdpIfHelloMessageTriggeredXmits, 2935 nhdpIfHelloMessagePeriodicXmits, 2936 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount, 2937 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount, 2938 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount, 2939 nhdpIfPerfCounterDiscontinuityTime, 2940 nhdpDiscIfRecvdPackets, 2941 nhdpDiscIfExpectedPackets, 2942 nhdpNibNeighborSetChanges, 2943 nhdpDiscNeighborNibNeighborSetChanges, 2944 nhdpDiscNeighborNibNeighborSetUpTime, 2945 nhdpDiscNeighborNibNeighborSetReachableLinkChanges, 2946 nhdpIib2HopSetPerfChanges, 2947 nhdpIib2HopSetPerfUpTime 2948 } 2949 STATUS current 2950 DESCRIPTION 2951 "Set of NHDP performance objects implemented 2952 in this module." 2953 ::= { nhdpMIBGroups 4 } 2955 nhdpNotificationObjectGroup OBJECT-GROUP 2956 OBJECTS { 2957 nhdpNbrStateChangeThreshold, 2958 nhdpNbrStateChangeWindow, 2959 nhdp2HopNbrStateChangeThreshold, 2960 nhdp2HopNbrStateChangeWindow, 2961 nhdpNbrState, 2962 nhdp2HopNbrState 2963 } 2964 STATUS current 2965 DESCRIPTION 2966 "Set of NHDP notification objects implemented 2967 in this module." 2968 ::= { nhdpMIBGroups 5 } 2969 nhdpNotificationGroup NOTIFICATION-GROUP 2970 NOTIFICATIONS { 2971 nhdpNbrStateChange, 2972 nhdp2HopNbrStateChange, 2973 nhdpIfStateChange 2974 } 2975 STATUS current 2976 DESCRIPTION 2977 "Set of NHDP notifications implemented 2978 in this module." 2979 ::= { nhdpMIBGroups 6 } 2981 nhdpStateGroup2 OBJECT-GROUP 2982 OBJECTS { 2983 nhdpUpTime, 2984 nhdpIfStateUpTime, 2985 nhdpDiscRouterIndex, 2986 nhdpDiscIfIndex, 2987 nhdpDiscIfSetIpAddrType, 2988 nhdpDiscIfSetIpAddr, 2989 nhdpDiscIfSetIpAddrPrefixLen, 2990 nhdpIibLinkSetLHeardTime, 2991 nhdpIibLinkSetLSymTime, 2992 nhdpIibLinkSetLPending, 2993 nhdpIibLinkSetLLost, 2994 nhdpIibLinkSetLTime, 2995 nhdpIib2HopSetIpAddrPrefixLen, 2996 nhdpIib2HopSet1HopIfIndex, 2997 nhdpIib2HopSetN2Time, 2998 nhdpIib2HopSetN2Lost, 2999 nhdpNibNeighborSetNSymmetric, 3000 nhdpNibLostNeighborSetNLTime 3001 } 3002 STATUS current 3003 DESCRIPTION 3004 "Set of NHDP state objects implemented 3005 in this module." 3006 ::= { nhdpMIBGroups 7 } 3008 -- 3009 -- Deprecated compliance statements and groups 3010 -- 3012 nhdpFullCompliance MODULE-COMPLIANCE 3013 STATUS deprecated 3014 DESCRIPTION 3015 "The full implementation requirements for 3016 managed network entities that implement 3017 NHDP. 3019 For version-independence, this compliance statement 3020 is deprecated in favor of nhdpFullCompliance2." 3021 MODULE -- this module 3022 MANDATORY-GROUPS { nhdpConfigurationGroup, 3023 nhdpStateGroup, 3024 nhdpNotificationObjectGroup, 3025 nhdpNotificationGroup, 3026 nhdpPerformanceGroup 3027 } 3028 ::= { nhdpCompliances 2 } 3030 nhdpStateGroup OBJECT-GROUP 3031 OBJECTS { 3032 nhdpUpTime, 3033 nhdpIfStateUpTime, 3034 nhdpDiscRouterIndex, 3035 nhdpDiscIfIndex, 3036 nhdpDiscIfSetIpAddrType, 3037 nhdpDiscIfSetIpAddr, 3038 nhdpDiscIfSetIpAddrPrefixLen, 3039 nhdpIibLinkSetLHeardTime, 3040 nhdpIibLinkSetLSymTime, 3041 nhdpIibLinkSetLPending, 3042 nhdpIibLinkSetLLost, 3043 nhdpIibLinkSetLTime, 3044 nhdpIib2HopSetIpAddrPrefixLen, 3045 nhdpIib2HopSet1HopIfIndex, 3046 nhdpIib2HopSetN2Time, 3047 nhdpNibNeighborSetNSymmetric, 3048 nhdpNibLostNeighborSetNLTime 3049 } 3050 STATUS deprecated 3051 DESCRIPTION 3052 "Set of NHDP state objects implemented 3053 in this module. 3055 For version-independence, this compliance statement 3056 is deprecated in favor of nhdpStateGroup2." 3057 ::= { nhdpMIBGroups 3 } 3059 END 3060 8. Security Considerations 3062 This MIB module defines objects for the configuration, monitoring, 3063 and notification of the Mobile Ad Hoc Network (MANET) Neighborhood 3064 Discovery Protocol (NHDP) [RFC6130]. NHDP allows routers to acquire 3065 topological information up to two hops away by virtue of exchanging 3066 HELLO messages. The information acquired by NHDP may be used by 3067 routing protocols. The neighborhood information, exchanged between 3068 routers using NHDP, serves these routing protocols as a baseline for 3069 calculating paths to all destinations in the MANET, relay set 3070 selection for network-wide transmissions, etc. 3072 There are a number of management objects defined in this MIB module 3073 with a MAX-ACCESS clause of read-write and/or read-create. Such 3074 objects may be considered sensitive or vulnerable in some network 3075 environments. The support for SET operations in a non-secure 3076 environment without proper protection opens devices to attack. These 3077 are the tables and objects and their sensitivity/vulnerability: 3079 o nhdpIfStatus - This writable object turns on or off the NHDP 3080 process for the specified interface. If disabled, higher-level 3081 protocol functions, e.g., routing, would fail, causing network- 3082 wide disruptions. 3084 o nhdpHelloInterval, nhdpHelloMinInterval, and nhdpRefreshInterval - 3085 These writable objects control the rate at which HELLO messages 3086 are sent on an interface. If set at too high a rate, this could 3087 represent a form of denial-of-service (DoS) attack by overloading 3088 interface resources. 3090 o nhdpHystAcceptQuality, nhdpHystRejectQuality, nhdpInitialQuality, 3091 and nhdpInitialPending - These writable objects affect the 3092 perceived quality of the NHDP links and hence the overall 3093 stability of the network. If improperly set, these settings could 3094 result in network-wide disruptions. 3096 o nhdpInterfaceTable - This table contains writable objects that 3097 affect the overall performance and stability of the NHDP process. 3098 Failure of the NHDP process would result in network-wide failure. 3099 Particularly sensitive objects from this table are discussed in 3100 the previous list items. This is the only table in the NHDP-MIB 3101 module with writable objects. 3103 Some of the readable objects in this MIB module (i.e., objects with a 3104 MAX-ACCESS other than not-accessible) may be considered sensitive or 3105 vulnerable in some network environments. It is thus important to 3106 control even GET and/or NOTIFY access to these objects and possibly 3107 to even encrypt the values of these objects when sending them over 3108 the network via SNMP. These are the tables and objects and their 3109 sensitivity/vulnerability: 3111 o nhdpDiscIfSetTable - The object contains information on discovered 3112 neighbors, specifically their IP address in the 3113 nhdpDiscIfSetIpAddr object. This information provides an 3114 adversary broad information on the members of the MANET, located 3115 within this single table. This information can be used to 3116 expedite attacks on the other members of the MANET without having 3117 to go through a laborious discovery process on their own. This 3118 object is the index into the table and has a MAX-ACCESS of 'not- 3119 accessible'. However, this information can be exposed using SNMP 3120 operations. 3122 MANET technology is often deployed to support communications of 3123 emergency services or military tactical applications. In these 3124 applications, it is imperative to maintain the proper operation of 3125 the communications network and to protect sensitive information 3126 related to its operation. Therefore, it is RECOMMENDED to provide 3127 support for the Transport Security Model (TSM) [RFC5591] in 3128 combination with TLS/DTLS [RFC6353]. 3130 SNMP versions prior to SNMPv3 did not include adequate security. 3131 Even if the network itself is secure (for example by using IPsec), 3132 there is no control as to who on the secure network is allowed to 3133 access and GET/SET (read/change/create/delete) the objects in this 3134 MIB module. 3136 Implementations SHOULD provide the security features described by the 3137 SNMPv3 framework (see [RFC3410]), and implementations claiming 3138 compliance to the SNMPv3 standard MUST include full support for 3139 authentication and privacy via the User-based Security Model (USM) 3140 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 3141 MAY also provide support for the Transport Security Model (TSM) 3142 [RFC5591] in combination with a secure transport such as SSH 3143 [RFC5592] or TLS/DTLS [RFC6353]. 3145 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3146 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3147 enable cryptographic security. It is then a customer/operator 3148 responsibility to ensure that the SNMP entity giving access to an 3149 instance of this MIB module is properly configured to give access to 3150 the objects only to those principals (users) that have legitimate 3151 rights to indeed GET or SET (change/create/delete) them. 3153 9. Applicability Statement 3155 This document describes objects for configuring parameters of the 3156 Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) 3157 [RFC6130] process on a router. This MIB module, denoted NHDP-MIB, 3158 also reports state, performance information, and notifications. This 3159 section provides some examples of how this MIB module can be used in 3160 MANET network deployments. 3162 NHDP is designed to allow routers to automatically discover and track 3163 routers one hop remote (denoted "neighbors") and routers two hops 3164 remote (denoted "two-hop neighbors"). This information is used by 3165 other MANET protocols in operation on the router to perform routing, 3166 multicast forwarding, and other functions with ad hoc and mobile 3167 networks. In the following, three example scenarios are listed where 3168 this MIB module is useful: 3170 o For a Parking Lot Initial Configuration Situation - It is common 3171 for the vehicles comprising the MANET being forward deployed at a 3172 remote location, e.g., the site of a natural disaster, to be off- 3173 loaded in a parking lot where an initial configuration of the 3174 networking devices is performed. The configuration is loaded into 3175 the devices from a fixed location Network Operation Center (NOC) 3176 at the parking lot, and the vehicles are stationary at the parking 3177 lot while the configuration changes are made. Standards-based 3178 methods for configuration management from the co-located NOC are 3179 necessary for this deployment option. 3181 o For Mobile Vehicles with Low-Bandwidth Satellite Link to a Fixed 3182 NOC - Here, the vehicles carrying the MANET routers carry multiple 3183 wireless interfaces, one of which is a relatively low-bandwidth, 3184 on-the-move satellite connection that interconnects a fix NOC to 3185 the nodes of the MANET. Standards-based methods for monitoring 3186 and fault management from the fixed NOC are necessary for this 3187 deployment option. 3189 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 3190 larger vehicles, a hierarchical network management arrangement is 3191 useful. Centralized network management is performed from a fixed 3192 NOC while local management is performed locally from within the 3193 vehicles. Standards-based methods for configuration, monitoring, 3194 and fault management are necessary for this deployment option. 3196 10. IANA Considerations 3198 The MIB module in this document uses the following IANA-assigned 3199 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 3201 Descriptor OBJECT IDENTIFIER value 3202 ---------- ----------------------- 3203 NHDP-MIB { mib-2 213 } 3205 11. Acknowledgements 3207 The authors wish to thank Benoit Claise, Elwyn Davies, Justin Dean, 3208 Adrian Farrel, Joel Halpern, Michael MacFaden, Al Morton, and Thomas 3209 Nadeau for their detailed reviews and insightful comments regarding 3210 RFC6779 and this document. 3212 This MIB document uses the template authored by D. Harrington, which 3213 is based on contributions from the MIB Doctors, especially Juergen 3214 Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn. 3216 12. References 3218 12.1. Normative References 3220 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3221 Requirement Levels", BCP 14, RFC 2119, March 1997. 3223 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3224 Schoenwaelder, Ed., "Structure of Management Information 3225 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3227 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3228 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3229 STD 58, RFC 2579, April 1999. 3231 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3232 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3233 April 1999. 3235 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3236 MIB", RFC 2863, June 2000. 3238 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3239 Simple Network Management Protocol (SNMP)", STD 62, 3240 RFC 3418, December 2002. 3242 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 3243 Schoenwaelder, "Textual Conventions for Internet Network 3244 Addresses", RFC 4001, February 2005. 3246 [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc 3247 Network (MANET) Neighborhood Discovery Protocol (NHDP)", 3248 RFC 6130, April 2011. 3250 [RFC6340] Presuhn, R., "Textual Conventions for the Representation 3251 of Floating-Point Numbers", RFC 6340, August 2011. 3253 [RFC7466] Dearlove, C. and T. Clausen, "An Optimization for the 3254 Mobile Ad Hoc Network (MANET) Neighborhood Discovery 3255 Protocol (NHDP)", RFC 7466, March 2015. 3257 12.2. Informative References 3259 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3260 "Introduction and Applicability Statements for Internet- 3261 Standard Management Framework", RFC 3410, December 2002. 3263 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3264 Architecture for Describing Simple Network Management 3265 Protocol (SNMP) Management Frameworks", RFC 3411, 3266 December 2002. 3268 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 3269 (USM) for version 3 of the Simple Network Management 3270 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 3272 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 3273 Advanced Encryption Standard (AES) Cipher Algorithm in the 3274 SNMP User-based Security Model", RFC 3826, June 2004. 3276 [RFC4293] Routhier, S., "Management Information Base for the 3277 Internet Protocol (IP)", RFC 4293, April 2006. 3279 [RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F. 3280 Baker, "OSPF Version 2 Management Information Base", 3281 RFC 4750, December 2006. 3283 [RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter 3284 Considerations in Mobile Ad Hoc Networks (MANETs)", 3285 RFC 5148, February 2008. 3287 [RFC5497] Clausen, T. and C. Dearlove, "Representing Multi-Value 3288 Time in Mobile Ad Hoc Networks (MANETs)", RFC 5497, 3289 March 2009. 3291 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 3292 for the Simple Network Management Protocol (SNMP)", 3293 RFC 5591, June 2009. 3295 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 3296 Shell Transport Model for the Simple Network Management 3297 Protocol (SNMP)", RFC 5592, June 2009. 3299 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 3300 Model for the Simple Network Management Protocol (SNMP)", 3301 RFC 6353, July 2011. 3303 [RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of 3304 Managed Objects for the Neighborhood Discovery Protocol", 3305 RFC 6779, October 2012. 3307 Authors' Addresses 3309 Ulrich Herberg 3310 United States 3312 EMail: ulrich@herberg.name 3313 URI: http://www.herberg.name/ 3315 Robert G. Cole 3316 US Army CERDEC 3317 Space and Terrestrial Communications 3318 6010 Frankford Road 3319 Aberdeen Proving Ground, Maryland 21005 3320 United States 3322 Phone: +1 443 395-8744 3323 EMail: robert.g.cole@us.army.mil 3324 URI: http://www.cs.jhu.edu/~rgcole/ 3326 Ian D Chakeres 3327 Delvin 3328 Ellicott City, Maryland 21042 3329 United States 3331 EMail: ian.chakeres@gmail.com 3332 URI: http://www.ianchak.com/ 3334 Thomas Heide Clausen 3335 Ecole Polytechnique 3337 Phone: +33 6 6058 9349 3338 EMail: T.Clausen@computer.org 3339 URI: http://www.ThomasClausen.org/