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