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