idnits 2.17.1 draft-ietf-manet-rfc6779bis-03.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 (March 3, 2015) is 3342 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 6779 (Obsoleted by RFC 7939) Summary: 0 errors (**), 0 flaws (~~), 2 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: September 4, 2015 I. Chakeres 7 Delvin 8 T. Clausen 9 LIX, Ecole Polytechnique 10 March 3, 2015 12 Definition of Managed Objects for the Neighborhood Discovery Protocol 13 draft-ietf-manet-rfc6779bis-03 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 September 4, 2015. 45 Copyright Notice 47 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . 64 85 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 66 86 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 87 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67 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 Neighborhood Discovery Protocol (NHDP) [RFC6130] 98 process on a router. The MIB module defined in this document, 99 denoted NHDP-MIB, also reports state, performance information, and 100 notifications about NHDP. This additional state and performance 101 information is useful to troubleshoot problems and performance issues 102 during neighbor discovery. 104 1.1. Difference from RFC 6779 106 This document obsoletes [RFC6779], replacing that document as the 107 specification of the MIB module for [RFC6130]. 109 Specifically, the MIB module for [RFC6130], specified in this 110 document, captures the new information and states for each symmetric 111 2-hop neighbor, recorded in the Neighbor Information Base of a router 112 and to be reflected in the appropriate tables, introduced by 113 [draft-ietf-manet-nhdp-optimization]. 115 2. The Internet-Standard Management Framework 117 For a detailed overview of the documents that describe the current 118 Internet-Standard Management Framework, please refer to section 7 of 119 RFC 3410 [RFC3410]. 121 Managed objects are accessed via a virtual information store, termed 122 the Management Information Base or MIB. MIB objects are generally 123 accessed through the Simple Network Management Protocol (SNMP). 124 Objects in the MIB are defined using the mechanisms defined in the 125 Structure of Management Information (SMI). This memo specifies a MIB 126 module that is compliant to the SMIv2, which is described in STD 58, 127 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 128 [RFC2580]. 130 3. Conventions 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 134 OPTIONAL" in this document are to be interpreted as described in 135 [RFC2119]. 137 4. Overview 139 [RFC6130] allows a router to discover and track topological 140 information of routers up to two hops away by virtue of exchanging 141 HELLO messages. This information is useful for routers running 142 various routing and multicast flooding protocols developed within the 143 IETF MANET Working Group. 145 4.1. Terms 147 The following definitions apply throughout this document: 149 o Notification Objects - triggers and associated notification 150 messages allowing for asynchronous tracking of pre-defined events 151 on the managed router. 153 o Configuration Objects - switches, tables, and objects that are 154 initialized to default settings or set through the management 155 interface defined by this MIB module. 157 o State Objects - automatically generated values that define the 158 current operating state of the NHDP instance in the router. 160 o Performance Objects - automatically generated values that help an 161 administrator or automated tool to assess the performance of the 162 NHDP instance on the router and the overall discovery performance 163 within the Mobile Ad Hoc Network (MANET). 165 4.2. Notation 167 The same notations as defined in [RFC6130] are used throughout this 168 document. 170 5. Structure of the MIB Module 172 This section presents the structure of the NHDP-MIB module. The MIB 173 module is arranged into the following structure: 175 o nhdpNotifications - objects defining NHDP-MIB notifications. 177 o nhdpObjects - defining objects within this MIB module. The 178 objects are arranged into the following groups: 180 * Configuration Group - defining objects related to the 181 configuration of the NHDP instance on the router. 183 * State Group - defining objects that reflect the current state 184 of the NHDP instance running on the router. 186 * Performance Group - defining objects that are useful to a 187 management station when characterizing the performance of NHDP 188 on the router and in the MANET. 190 o nhdpConformance - defining the minimal and maximal conformance 191 requirements for implementations of this MIB module. 193 5.1. Notifications 195 This section describes the use of notifications and mechanisms to 196 enhance the ability to manage NHDP routing domains. 198 5.1.1. Introduction 200 Notifications can be emitted by a router running an instance of this 201 specification as a reaction to a specific event. This allows a 202 network manager to efficiently determine the source of problems or 203 significant changes of configuration or topology, instead of polling 204 a possibly large number of routers. 206 5.1.2. Notification Generation 208 When an exception event occurs, the application notifies the local 209 agent, which sends a notification to the appropriate SNMP management 210 stations. The message includes the notification type and may include 211 a list of notification-specific variables. Section 7 contains the 212 notification definitions, which includes the variable lists. At 213 least one IP address of the router that originates the notification 214 is included in the variable list so that the network manager may 215 determine the source of the notification. 217 5.1.3. Limiting Frequency of Notifications 219 To limit the frequency of notifications, the following additional 220 mechanisms are suggested, similar to those in [RFC4750]. 222 5.1.3.1. Ignoring Initial Activity 224 The majority of critical events occur when NHDP is first enabled on a 225 router, at which time the symmetric neighbors and two-hop neighbors 226 of the router are discovered. During this initial period, a 227 potential flood of notifications is unnecessary since the events are 228 expected. To avoid unnecessary notifications, a router SHOULD NOT 229 originate expected notifications until a certain time interval has 230 elapsed, which is to be predefined by the network manager. It is 231 RECOMMENDED that this time interval is at least 3 x 232 nhdpHelloInterval, so that symmetric neighbors are discovered. The 233 suppression window for notifications is started when the nhdpIfStatus 234 transitions from its default value of 'false(2)' to 'true(1)'. 236 5.1.3.2. Throttling Notifications 238 The mechanism for throttling the notifications is the same as in 239 [RFC4750] (i.e., the number of transmitted notifications per time is 240 bounded). 242 Appropriate values for the window time and upper bound are to be 243 selected by the network manager and depend on the deployment of the 244 MANET. If NHDP is deployed on a lossy, wireless medium, sending too 245 many notifications in a short time interval may lead to collisions 246 and dropped packets. In particular, in dense deployments of routers 247 running NHDP (i.e., where each router has many neighbors), a change 248 of the local topology may trigger many notifications at the same 249 time. [RFC4750] recommends "7 traps with a window time of 10 250 seconds" as the upper bound. As NHDP is expected to be deployed in 251 more lossy channels than OSPF, it is RECOMMENDED to choose a lower 252 threshold for the number of notifications per time than that. 253 Specifically, it is RECOMMENDED that the threshold value for the 254 objects reflecting the change be set to a value of '10' and the 255 DEFAULT values for these objects within the Notifications Group be 256 set to this value. Further, a time window for the change objects is 257 defined within this MIB module. It is RECOMMENDED that if the number 258 of occurrences exceeds the change threshold within the previous 259 change window, then the notification is to be sent. Furthermore, it 260 is RECOMMENDED that the value for this window be set to at least 5 261 times the nhdpHelloInterval. 263 The following objects are used to define the thresholds and time 264 windows for specific notifications defined in the NHDP-MIB module: 265 nhdpNbrStateChangeThreshold, nhdpNbrStateChangeWindow, 266 nhdp2HopNbrStateChangeThreshold, and nhdp2HopNbrStateChangeWindow. 268 5.1.3.3. One Notification per Event 270 Similar to the mechanism in [RFC4750], only one notification is sent 271 per event. 273 5.2. The Configuration Group 275 The router running NHDP is configured with a set of controls. The 276 authoritative list of configuration controls within the NHDP-MIB 277 module are found within the MIB module itself. Generally, an attempt 278 was made in developing the NHDP-MIB module to support all 279 configuration objects defined in [RFC6130]. For all of the 280 configuration parameters, the same constraints and default values of 281 these parameters as defined in [RFC6130] are followed. Refer to 283 [RFC5148] for guidance on setting jitter-related parameters, e.g., 284 nhdpMaxJitter. 286 5.3. The State Group 288 The State Group reports current state information of a router running 289 NHDP. The NHDP-MIB State Group tables were designed to contain the 290 complete set of state information defined within the information 291 bases specified in Sections 6, 7, and 8 of [RFC6130]. 293 Two constructs, i.e., TEXTUAL-CONVENTIONs, are defined to support the 294 tables in the State Group. NHDP stores and indexes information 295 through sets of (dynamically defined) addresses, i.e., address sets. 296 Within SMIv2, it is not possible to index tables with variably 297 defined address sets. Hence, these TEXTUAL-CONVENTIONs are defined 298 to provide a local mapping between NHDP-managed address sets and 299 SMIv2 table indexing. These constructs are the NeighborIfIndex and 300 NeighborRouterIndex. These are locally (to the router) defined, 301 unique identifiers of virtual neighbors and neighbor interfaces. Due 302 to the nature of NHDP, the local router may have identified distinct 303 address sets but is not able to associate these as a single 304 interface. Hence, two or more NeighborIfIndexes pointing to multiple 305 distinct address sets may, in fact, be related to a common neighbor 306 interface. This ambiguity may also hold with respect to the 307 assignment of the NeighborRouterIndex. The local MIB agent is 308 responsible for managing, aggregating, and retiring the defined 309 indexes and for updating MIB tables using these indexes as the local 310 router learns more about its neighbors' topologies. These constructs 311 are used to define indexes to the appropriate State Group tables and 312 to correlate table entries to address sets, virtual neighbor 313 interfaces, and virtual neighbors within the MANET. 315 5.4. The Performance Group 317 The Performance Group reports values relevant to system performance. 318 Unstable neighbors or 2-hop neighbors and frequent changes of sets 319 can have a negative influence on the performance of NHDP. This MIB 320 module defines several objects that can be polled in order to, e.g., 321 calculate histories or monitor frequencies of changes. This may help 322 the network administrator to determine unusual topology changes or 323 other changes that affect stability and reliability of the MANET. 325 5.5. Tables and Indexing 327 The NHDP-MIB module contains a number of tables that record data 328 related to: 330 o the local router, 332 o a local MANET interface on the router, 334 o other routers that are 1 hop removed from the local router, 336 o interfaces on other routers that are 1 hop removed from the local 337 router, and 339 o other routers that are 2 hops removed from the local router. 341 The NHDP-MIB module's tables are indexed via the following 342 constructs: 344 o nhdpIfIndex - the IfIndex of the local router on which NHDP is 345 configured. 347 o nhdpDiscIfIndex - a locally managed index representing a known 348 interface on a neighboring router. 350 o nhdpDiscRouterIndex - a locally managed index representing an ID 351 of a known neighboring router. 353 These tables and their indexing are: 355 o nhdpInterfaceTable - describes the configuration of the interfaces 356 of this router. This table has INDEX { nhdpIfIndex }. 358 o nhdpLibLocalIfSetTable - records all network addresses that are 359 defined as local interface network addresses on this router. This 360 table has INDEX { nhdpLibLocalIfSetIndex }. 362 o nhdpLibRemovedIfAddrSetTable - records network addresses that were 363 recently used as local interface network addresses on this router 364 but have been removed. This table has INDEX 365 { nhdpLibRemovedIfAddrSetIndex }. 367 o nhdpInterfaceStateTable - records state information related to 368 specific interfaces of this router. This table has INDEX 369 { nhdpIfIndex }. 371 o nhdpDiscIfSetTable - includes the nhdpDiscRouterIndex of the 372 discovered router, the nhdpDiscIfIndex of the discovered 373 interface, and the current set of addresses associated with this 374 neighbor interface. This table has INDEX { nhdpDiscIfSetIndex }. 376 o nhdpIibLinkSetTable - for each local interface, records all links 377 belonging to other routers that are, or recently were, 1-hop 378 neighbors to this router. This table has INDEX { nhdpIfIndex, 379 nhdpDiscIfIndex }. 381 o nhdpIib2HopSetTable - for each local interface, records network 382 addresses (one at a time) of symmetric 2-hop neighbors and the 383 symmetric links to symmetric 1-hop neighbors of this router 384 through which these symmetric 2-hop neighbors can be reached. 385 This table has INDEX { nhdpIfIndex, nhdpDiscIfIndex, 386 nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress }. 388 o nhdpNibNeighborSetTable - records all network addresses of each 389 1-hop neighbor to this router. This table has INDEX 390 { nhdpDiscRouterIndex }. 392 o nhdpNibLostNeighborSetTable - records network addresses of other 393 routers that were recently symmetric 1-hop neighbors to this 394 router but are now advertised as lost. This table has INDEX 395 { nhdpDiscRouterIndex }. 397 o nhdpInterfacePerfTable - records performance objects that are 398 measured for each local NHDP interface on this router. This table 399 has INDEX { nhdpIfIndex }. 401 o nhdpDiscIfSetPerfTable - records performance objects that are 402 measured for each discovered interface of a neighbor of this 403 router. This table has INDEX { nhdpDiscIfIndex }. 405 o nhdpDiscNeighborSetPerfTable - records performance objects that 406 are measured for discovered neighbors of this router. This table 407 has INDEX { nhdpDiscRouterIndex }. 409 o nhdpIib2HopSetPerfTable - records performance objects that are 410 measured for discovered 2-hop neighbors of this router. This 411 table has INDEX { nhdpDiscRouterIndex }. 413 6. Relationship to Other MIB Modules 415 This section specifies the relationship of the MIB module contained 416 in this document to other standards, particularly to standards 417 containing other MIB modules. MIB modules and specific definitions 418 imported from MIB modules that SHOULD be implemented in conjunction 419 with the MIB module contained within this document are identified in 420 this section. 422 6.1. Relationship to the SNMPv2-MIB 424 The System group in the SNMPv2-MIB module [RFC3418] is defined as 425 being mandatory for all systems, and the objects apply to the entity 426 as a whole. The System group provides identification of the 427 management entity and certain other system-wide data. The NHDP-MIB 428 module does not duplicate those objects. 430 6.2. Relationship to Routing Protocol MIB Modules Relying on the NHDP- 431 MIB Module 433 [RFC6130] allows routing protocols to rely on the neighborhood 434 information that is discovered by means of HELLO message exchange. 435 In order to allow for troubleshooting, fault isolation, and 436 management of such routing protocols through a routing protocol MIB 437 module, it may be desired to align the State Group tables of the 438 NHDP-MIB module and the routing protocol MIB module. This is 439 accomplished through the definition of two TEXTUAL-CONVENTIONs in the 440 NHDP-MIB module: the NeighborIfIndex and the NeighborRouterIndex. 441 These object types are used to develop indexes into common NHDP-MIB 442 module and routing protocol State Group tables. These objects are 443 locally significant but should be locally common to the NHDP-MIB 444 module and the routing protocol MIB module implemented on a common 445 networked router. This will allow for improved cross-referencing of 446 information across the two MIB modules. 448 6.3. MIB Modules Required for IMPORTS 450 The following NHDP-MIB module IMPORTS objects from SNMPv2-SMI 451 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB 452 [RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340]. 454 7. Definitions 456 This section contains the MIB module defined by the specification. 458 NHDP-MIB DEFINITIONS ::= BEGIN 460 -- This MIB module defines objects for the management of 461 -- NHDP (RFC 6130) - The Neighborhood Discovery Protocol, 462 -- Clausen, T., Dearlove, C., and J. Dean, January 2011. 464 IMPORTS 466 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 467 Counter32, Counter64, Integer32, Unsigned32, mib-2, 468 TimeTicks 469 FROM SNMPv2-SMI -- RFC 2578 471 TEXTUAL-CONVENTION, TruthValue, TimeStamp, 472 RowStatus 473 FROM SNMPv2-TC -- RFC 2579 475 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 476 FROM SNMPv2-CONF -- STD 58 478 SnmpAdminString 479 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 481 InetAddressType, InetAddress, 482 InetAddressPrefixLength 483 FROM INET-ADDRESS-MIB -- RFC 4001 485 InterfaceIndex 486 FROM IF-MIB -- RFC 2863 488 Float32TC 489 FROM FLOAT-TC-MIB -- RFC 6340 490 ; 492 nhdpMIB MODULE-IDENTITY 493 LAST-UPDATED "201503031100Z" -- 3 March 2015 494 ORGANIZATION "IETF MANET Working Group" 495 CONTACT-INFO 496 "WG E-Mail: manet@ietf.org 497 WG web page: https://datatracker.ietf.org/wg/manet 499 Editors: Ulrich Herberg 500 USA 501 ulrich@herberg.name 502 http://www.herberg.name/ 504 Robert G. Cole 505 US Army CERDEC 506 Space and Terrestrial Communications 507 6010 Frankford Street 508 Aberdeen Proving Ground, Maryland 21005 509 USA 510 +1 443 395-8744 511 robert.g.cole@us.army.mil 512 http://www.cs.jhu.edu/~rgcole/ 514 Ian D Chakeres 515 Delvin 516 Ellicott City, Maryland 21042 517 USA 518 ian.chakeres@gmail.com 519 http://www.ianchak.com/ 520 Thomas Heide Clausen 521 Ecole Polytechnique 522 LIX 523 91128 Palaiseau Cedex 524 France 525 Email: T.Clausen@computer.org 526 URI: http://www.thomasclausen.org/" 528 DESCRIPTION 529 "This NHDP-MIB module is applicable to routers 530 implementing the Neighborhood Discovery Protocol 531 defined in RFC 6130. 533 Copyright (c) 2014 IETF Trust and the persons 534 identified as authors of the code. All rights reserved. 536 Redistribution and use in source and binary forms, with 537 or without modification, is permitted pursuant to, and 538 subject to the license terms contained in, the Simplified 539 BSD License set forth in Section 4.c of the IETF Trust's 540 Legal Provisions Relating to IETF Documents 541 (http://trustee.ietf.org/license-info). 543 This version of this MIB module is part of RFC 6779; see 544 the RFC itself for full legal notices." 546 -- revision 547 REVISION "201503031100Z" -- 3 March 2015 548 DESCRIPTION 549 "Updated version of this MIB module, 550 including updates made to NHDP by 551 draft-ietf-manet-nhdp-optimization, 552 published as RFC xxxx." 553 REVISION "201210221000Z" -- 22 October 2012 554 DESCRIPTION 555 "Initial version of this MIB module, 556 published as RFC 6779." 557 ::= { mib-2 213 } 559 -- 560 -- Top-Level Components of this MIB Module 561 -- 562 nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 } 563 nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 } 564 nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 } 566 -- 567 -- TEXTUAL-CONVENTIONs 568 -- 569 -- Two new TEXTUAL-CONVENTIONs have been defined in 570 -- this MIB module for indexing into the following 571 -- tables and indexing into other tables in other MIB modules. 572 -- This was necessary because NHDP manages and 573 -- indexes based upon dynamic address tuples, i.e., 574 -- address sets, while SMI requires statically 575 -- defined indexes for accessing its table rows. 576 -- The NeighborIfIndex defines a unique (to the local router) 577 -- index referencing a discovered virtual interface on another 578 -- neighbor within the MANET. The NeighborRouterIndex defines a 579 -- unique (to the local router) index referencing a discovered 580 -- virtual neighbor within the MANET. 581 -- 582 -- Due to the nature of NHDP, 583 -- different indexes may be related to common neighbor 584 -- interfaces or common neighbor routers, but the information 585 -- obtained through NHDP has not allowed the local router 586 -- to relate these virtual objects (i.e., interfaces or routers) 587 -- at this point in time. As more topology information 588 -- is gathered by the local router, it may associate 589 -- virtual interfaces or routers and collapse these 590 -- indexes appropriately. 592 -- Multiple addresses can be associated with a 593 -- given NeighborIfIndex. Each NeighborIfIndex is 594 -- associated with a NeighborRouterIndex. Throughout 595 -- the nhdpStateObjGroup, the 596 -- NeighborIfIndex and the NeighborRouterIndex are used 597 -- to define the set of IpAddrs related to a virtual 598 -- neighbor interface or virtual neighbor under discussion. 600 NeighborIfIndex ::= TEXTUAL-CONVENTION 601 DISPLAY-HINT "d" 602 STATUS current 603 DESCRIPTION 604 "An arbitrary, locally unique identifier associated with a 605 virtual interface of a discovered NHDP neighbor. 606 Due to the nature of NHDP, the local router 607 may not know if two distinct addresses belong to the 608 same interface of a neighbor or to two different 609 interfaces. As the local router gains more 610 knowledge of its neighbors, its local view may change, and 611 this table will be updated to reflect the local router's 612 current understanding, associating address sets to neighbor 613 interfaces. The local router identifies a virtual neighbor 614 interface through the receipt of address lists advertised 615 through an NHDP HELLO message. 617 All objects of type NeighborIfIndex are assigned by the agent 618 out of a common number space. 620 The value for each discovered virtual neighbor 621 interface may not remain constant from 622 one re-initialization of the entity's network management 623 agent to the next re-initialization. If the 624 local router gains information associating two virtual 625 interfaces on a neighbor as a common interface, 626 then the agent MUST aggregate the two address sets to 627 a single index chosen from the set of aggregated indexes, 628 and it MUST update all tables in this 629 MIB module that are indexed by indexes 630 of type NeighborIfIndex. It MAY then reuse freed 631 index values following the next agent restart. 633 The specific value is meaningful only within a given SNMP 634 entity." 635 SYNTAX Unsigned32 (1..2147483647) 637 NeighborRouterIndex ::= TEXTUAL-CONVENTION 638 DISPLAY-HINT "d" 639 STATUS current 640 DESCRIPTION 641 "An arbitrary, locally unique identifier associated with a 642 virtual discovered neighbor (one or two hop). Due to the 643 nature of NHDP, the local router may identify 644 multiple virtual neighbors that, in fact, are one and 645 the same. Neighbors that are two hops away with more than 646 one advertised address will exhibit this behavior. As the 647 local router's knowledge of its neighbors' topology 648 increases, the local router will be able to associate 649 multiple virtual neighbor indexes into a single virtual 650 neighbor index chosen from the set of aggregated indexes; 651 it MUST update all tables in this MIB module indexed by these 652 indexes, and it MAY reuse the freed indexes following the 653 next agent re-initialization. 655 All objects of type NeighborRouterIndex are assigned by 656 the agent out of a common number space. 658 The NeighborRouterIndex defines a discovered NHDP peer 659 virtual neighbor of the local router. 660 The value for each discovered virtual neighbor index MUST 661 remain constant at least from one re-initialization of 662 the entity's network management agent to the next 663 re-initialization, except if an application is deleted 664 and re-created. 666 The specific value is meaningful only within a given SNMP 667 entity. A NeighborRouterIndex value MUST NOT be reused 668 until the next agent restart." 669 SYNTAX Unsigned32 (1..2147483647) 671 -- 672 -- nhdpObjects 673 -- 675 -- 1) Configuration Objects Group 676 -- 2) State Objects Group 677 -- 3) Performance Objects Group 679 -- 680 -- nhdpConfigurationObjGrp 681 -- 683 -- Contains the NHDP objects that configure specific options 684 -- that determine the overall performance and operation of 685 -- NHDP. 687 nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } 689 nhdpInterfaceTable OBJECT-TYPE 690 SYNTAX SEQUENCE OF NhdpInterfaceEntry 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "The nhdpInterfaceTable describes the 695 configuration of the interfaces of this router 696 that are intended to use MANET control protocols. 697 As such, this table 'sparse augments' the ifTable 698 specifically when NHDP is to be configured to 699 operate over this interface. The interface is 700 identified by the ifIndex from the interfaces 701 group defined in the Interfaces Group MIB module. 703 A conceptual row in this table exists if and only 704 if either a manager has explicitly created the row 705 or there is an interface on the managed device 706 that supports and runs NHDP. 708 The manager can create a row by setting 709 rowStatus to 'createAndGo' or 'createAndWait'. 710 Row objects having associated DEFVAL clauses are 711 automatically defined by the agent with these 712 values during row creation, unless the manager 713 explicitly defines these object values during the 714 row creation. 716 If the corresponding entry with ifIndex value 717 is deleted from the Interface Table, then the entry 718 in this table is automatically deleted, 719 NHDP is disabled on this interface, 720 and all configuration and state information 721 related to this interface is to be removed 722 from memory." 723 REFERENCE 724 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 725 K., and F. Kastenholtz, June 2000" 726 ::= { nhdpConfigurationObjGrp 1 } 728 nhdpInterfaceEntry OBJECT-TYPE 729 SYNTAX NhdpInterfaceEntry 730 MAX-ACCESS not-accessible 731 STATUS current 732 DESCRIPTION 733 "The nhdpInterfaceEntry describes one NHDP 734 local interface configuration as indexed by 735 its ifIndex as defined in the Standard MIB II 736 Interface Table (RFC 2863). 738 The objects in this table are persistent, and when 739 written, the device SHOULD save the change to 740 non-volatile storage. For further information 741 on the storage behavior for these objects, refer 742 to the description for the nhdpIfRowStatus 743 object." 744 INDEX { nhdpIfIndex } 745 ::= { nhdpInterfaceTable 1 } 747 NhdpInterfaceEntry ::= 748 SEQUENCE { 749 nhdpIfIndex 750 InterfaceIndex, 751 nhdpIfName 752 SnmpAdminString, 753 nhdpIfStatus 754 TruthValue, 755 nhdpHelloInterval 756 Unsigned32, 757 nhdpHelloMinInterval 758 Unsigned32, 759 nhdpRefreshInterval 760 Unsigned32, 761 nhdpLHoldTime 762 Unsigned32, 763 nhdpHHoldTime 764 Unsigned32, 765 nhdpHystAcceptQuality 766 Float32TC, 767 nhdpHystRejectQuality 768 Float32TC, 769 nhdpInitialQuality 770 Float32TC, 771 nhdpInitialPending 772 TruthValue, 773 nhdpHpMaxJitter 774 Unsigned32, 775 nhdpHtMaxJitter 776 Unsigned32, 777 nhdpIfRowStatus 778 RowStatus 779 } 781 nhdpIfIndex OBJECT-TYPE 782 SYNTAX InterfaceIndex 783 MAX-ACCESS not-accessible 784 STATUS current 785 DESCRIPTION 786 "This value MUST correspond to an ifIndex referring 787 to a valid entry in the Interfaces Table." 788 REFERENCE 789 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 790 and F. Kastenholtz, June 2000" 791 ::= { nhdpInterfaceEntry 1 } 793 nhdpIfName OBJECT-TYPE 794 SYNTAX SnmpAdminString 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "The textual name of the interface. The value of this 799 object SHOULD be the name of the interface as assigned by 800 the local device. This can be a text-name, such as 'le0' 801 or a simple port number, such as '1', 802 depending on the interface-naming syntax of the device. 804 If there is no local name or this object is otherwise not 805 applicable, then this object contains a zero-length string." 806 ::= { nhdpInterfaceEntry 2 } 808 nhdpIfStatus OBJECT-TYPE 809 SYNTAX TruthValue 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "nhdpIfStatus indicates whether this interface is 814 currently running NHDP. A value of 'true(1)' indicates 815 that NHDP is running on this interface. 816 A value of 'false(2)' indicates that NHDP is not 817 currently running on this interface. This corresponds 818 to the I_manet parameter in the Local Interface Set 819 of NHDP." 820 DEFVAL { false } 821 ::= { nhdpInterfaceEntry 3 } 823 -- 824 -- Interface Parameters - Message Intervals 825 -- 827 nhdpHelloInterval OBJECT-TYPE 828 SYNTAX Unsigned32 829 UNITS "milliseconds" 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 "nhdpHelloInterval corresponds to 834 HELLO_INTERVAL of NHDP and represents the 835 maximum time between the transmission of two 836 successive HELLO messages on this MANET interface. 838 Guidance for setting this object may be found 839 in Section 5 of the NHDP specification (RFC 6130), 840 which indicates that: 841 o nhdpHelloInterval > 0 842 o nhdpHelloInterval >= nhdpHelloMinInterval" 843 REFERENCE 844 "Section 5 on Protocol Parameters and 845 Constraints of RFC 6130 - Mobile Ad Hoc 846 Network (MANET) Neighborhood Discovery 847 Protocol (NHDP), Clausen, T., Dearlove, 848 C., and J. Dean, April 2011" 849 DEFVAL { 2000 } 850 ::= { nhdpInterfaceEntry 4 } 852 nhdpHelloMinInterval OBJECT-TYPE 853 SYNTAX Unsigned32 854 UNITS "milliseconds" 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "nhdpHelloMinInterval corresponds to 859 HELLO_MIN_INTERVAL of NHDP and represents 860 the minimum interval between transmission 861 of two successive HELLO messages on this 862 MANET interface. 864 Guidance for setting this object may be found 865 in Section 5 of the NHDP specification (RFC 6130), 866 which indicates that: 867 o nhdpHelloMinInterval <= nhdpHelloInterval" 868 REFERENCE 869 "Section 5 on Protocol Parameters and 870 Constraints of RFC 6130 - Mobile Ad Hoc Network 871 (MANET) Neighborhood Discovery Protocol (NHDP), 872 Clausen, T., Dearlove, C., and J. Dean, April 2011" 873 DEFVAL { 500 } 874 ::= { nhdpInterfaceEntry 5 } 876 nhdpRefreshInterval OBJECT-TYPE 877 SYNTAX Unsigned32 878 UNITS "milliseconds" 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "nhdpRefreshInterval corresponds to 883 REFRESH_INTERVAL of NHDP and represents the 884 maximum interval between advertisements of 885 each 1-hop neighbor network address and its 886 status. Each advertisement is in a HELLO 887 message on this MANET interface. 889 Guidance for setting this object may be found 890 in Section 5 of the NHDP specification (RFC 6130), 891 which indicates that: 892 o nhdpRefreshInterval >= nhdpHelloInterval" 893 REFERENCE 894 "Section 5 on Protocol Parameters and 895 Constraints of RFC 6130 - Mobile Ad Hoc Network 896 (MANET) Neighborhood Discovery Protocol (NHDP), 897 Clausen, T., Dearlove, C., and J. Dean, April 2011" 898 DEFVAL { 2000 } 899 ::= { nhdpInterfaceEntry 6 } 901 -- 902 -- Interface Parameters - Information Validity times 903 -- 905 nhdpLHoldTime OBJECT-TYPE 906 SYNTAX Unsigned32 907 UNITS "milliseconds" 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "nhdpLHoldTime corresponds to 912 L_HOLD_TIME of NHDP and represents the period 913 of advertisement, on this MANET interface, of 914 former 1-hop neighbor network addresses as lost 915 in HELLO messages, allowing recipients of these 916 HELLO messages to accelerate removal of this 917 information from their Link Sets. 919 Guidance for setting this object may be found 920 in Section 5 of the NHDP specification (RFC 6130), 921 which indicates that it should be assigned a 922 value significantly greater than the refresh 923 interval held by nhdpRefreshInterval." 924 REFERENCE 925 "Section 5 on Protocol Parameters and 926 Constraints of RFC 6130 - Mobile Ad Hoc Network 927 (MANET) Neighborhood Discovery Protocol (NHDP), 928 Clausen, T., Dearlove, C., and J. Dean, April 2011" 929 DEFVAL { 6000 } 930 ::= { nhdpInterfaceEntry 7 } 932 nhdpHHoldTime OBJECT-TYPE 933 SYNTAX Unsigned32 934 UNITS "milliseconds" 935 MAX-ACCESS read-create 936 STATUS current 937 DESCRIPTION 938 "nhdpHHoldTime corresponds to 939 H_HOLD_TIME of NHDP and is used as the value 940 in the VALIDITY_TIME Message TLV included in all 941 HELLO messages on this MANET interface. It is then 942 used by each router receiving such a HELLO message 943 to indicate the validity of the information taken 944 from that HELLO message and recorded in the receiving 945 router's Information Bases. 947 Guidance for setting this object may be found 948 in Section 5 of the NHDP specification (RFC 6130), 949 which indicates that it should be assigned a 950 value significantly greater than the refresh interval 951 held by nhdpRefreshInterval and must be representable 952 as described in RFC 5497." 953 REFERENCE 954 "Section 5 on Protocol Parameters and 955 Constraints of RFC 6130 - Mobile Ad Hoc Network 956 (MANET) Neighborhood Discovery Protocol (NHDP), 957 Clausen, T., Dearlove, C., and J. Dean, April 2011" 958 DEFVAL { 6000 } 959 ::= { nhdpInterfaceEntry 8 } 961 -- 962 -- Interface Parameters - Link Quality 963 -- 965 nhdpHystAcceptQuality OBJECT-TYPE 966 SYNTAX Float32TC 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "nhdpHystAcceptQuality corresponds to 971 HYST_ACCEPT of NHDP and represents the link 972 quality threshold at or above which a link becomes 973 usable, if it was not already so. 975 Guidance for setting this object may be found 976 in Section 5 of the NHDP specification (RFC 6130), 977 which indicates that: 978 o 0 <= nhdpHystRejectQuality 979 <= nhdpHystAcceptQuality <= 1.0 981 The default value for this object is 1.0. According to 982 RFC 6340: 983 Since these textual conventions are defined in terms 984 of the OCTET STRING type, the SMI's mechanisms for 985 formally setting range constraints are not available. 986 MIB designers using these textual conventions will need 987 to use DESCRIPTION clauses to spell out any applicable 988 range constraints beyond those implied by the underlying 989 IEEE types. 991 Therefore, this object does not have a DEFVAL clause." 992 REFERENCE 993 "Section 5 on Protocol Parameters and 994 Constraints of RFC 6130 - Mobile Ad Hoc Network 995 (MANET) Neighborhood Discovery Protocol (NHDP), 996 Clausen, T., Dearlove, C., and J. Dean, April 2011" 997 -- DEFVAL { 1.0 } see DESCRIPTION 998 ::= { nhdpInterfaceEntry 9 } 1000 nhdpHystRejectQuality OBJECT-TYPE 1001 SYNTAX Float32TC 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION 1005 "nhdpHystRejectQuality corresponds to 1006 HYST_REJECT of NHDP and represents the 1007 link quality threshold below which a 1008 link becomes unusable, if it was not 1009 already so. 1011 Guidance for setting this object may be found 1012 in Section 5 of the NHDP specification (RFC 6130), 1013 which indicates that: 1014 o 0 <= nhdpHystRejectQuality 1015 <= nhdpHystAcceptQuality <= 1.0 1017 The default value for this object is 0.0. According to 1018 RFC 6340: 1019 Since these textual conventions are defined in terms 1020 of the OCTET STRING type, the SMI's mechanisms for 1021 formally setting range constraints are not available. 1022 MIB designers using these textual conventions will need 1023 to use DESCRIPTION clauses to spell out any applicable 1024 range constraints beyond those implied by the underlying 1025 IEEE types. 1026 Therefore, this object does not have a DEFVAL clause." 1027 REFERENCE 1028 "Section 5 on Protocol Parameters and 1029 Constraints of RFC 6130 - Mobile Ad Hoc Network 1030 (MANET) Neighborhood Discovery Protocol (NHDP), 1031 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1032 -- DEFVAL { 0.0 } see DESCRIPTION 1033 ::= { nhdpInterfaceEntry 10 } 1035 nhdpInitialQuality OBJECT-TYPE 1036 SYNTAX Float32TC 1037 MAX-ACCESS read-create 1038 STATUS current 1039 DESCRIPTION 1040 "nhdpInitialQuality corresponds to 1041 INITIAL_QUALITY of NHDP and represents the 1042 initial quality of a newly identified link. 1044 Guidance for setting this object may be found 1045 in Section 5 of the NHDP specification (RFC 6130), 1046 which indicates that: 1047 o 0 <= nhdpInitialQuality <= 1.0 1049 The default value for this object is 1.0. According to 1050 RFC 6340: 1051 Since these textual conventions are defined in terms 1052 of the OCTET STRING type, the SMI's mechanisms for 1053 formally setting range constraints are not available. 1054 MIB designers using these textual conventions will need 1055 to use DESCRIPTION clauses to spell out any applicable 1056 range constraints beyond those implied by the underlying 1057 IEEE types. 1058 Therefore, this object does not have a DEFVAL clause." 1059 REFERENCE 1060 "Section 5 on Protocol Parameters and 1061 Constraints of RFC 6130 - Mobile Ad Hoc Network 1062 (MANET) Neighborhood Discovery Protocol (NHDP), 1063 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1064 -- DEFVAL { 1.0 } see DESCRIPTION 1065 ::= { nhdpInterfaceEntry 11 } 1067 nhdpInitialPending OBJECT-TYPE 1068 SYNTAX TruthValue 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION 1072 "nhdpInitialPending corresponds to 1073 INITIAL_PENDING of NHDP. If the value of this object 1074 is 'true(1)', then a newly identified link is considered 1075 pending and is not usable until the link quality 1076 has reached or exceeded the nhdpHystAcceptQuality 1077 threshold. 1079 Guidance for setting this object may be found 1080 in Section 5 of the NHDP specification (RFC 6130), 1081 which indicates that: 1082 o If nhdpInitialQuality >= nhdpHystAcceptQuality, 1083 then nhdpInitialPending := false(2). 1084 o If nhdpInitialQuality < nhdpHystRejectQuality, 1085 then nhdpInitialPending := true(1)." 1086 REFERENCE 1087 "Section 5 on Protocol Parameters and 1088 Constraints of RFC 6130 - Mobile Ad Hoc Network 1089 (MANET) Neighborhood Discovery Protocol (NHDP), 1090 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1091 DEFVAL { false } 1092 ::= { nhdpInterfaceEntry 12 } 1094 -- 1095 -- Interface Parameters - Jitter 1096 -- 1097 nhdpHpMaxJitter OBJECT-TYPE 1098 SYNTAX Unsigned32 1099 UNITS "milliseconds" 1100 MAX-ACCESS read-create 1101 STATUS current 1102 DESCRIPTION 1103 "nhdpHpMaxJitter corresponds to 1104 HP_MAXJITTER of NHDP and represents the 1105 value of MAXJITTER used in RFC 5148 for 1106 periodically generated HELLO messages on 1107 this MANET interface. 1109 Guidance for setting this object may be found 1110 in Section 5 of RFC 5148, which indicates that: 1111 o nhdpHpMaxJitter <= nhdpHelloInterval / 2 1112 o nhdpHpMaxJitter should not be greater 1113 than nhdpHelloInterval / 4 1114 o If nhdpMinHelloInterval > 0, then 1115 nhdpHpMaxJitter <= nhdpHelloMinInterval; and 1116 nhdpHpMaxJitter should not be greater than 1117 nhdpHelloMinInterval / 2" 1118 REFERENCE 1119 "Section 5 of RFC 5148 - Jitter Considerations in 1120 Mobile Ad Hoc Networks (MANETs), 1121 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1122 DEFVAL { 500 } 1123 ::= { nhdpInterfaceEntry 13 } 1125 nhdpHtMaxJitter OBJECT-TYPE 1126 SYNTAX Unsigned32 1127 UNITS "milliseconds" 1128 MAX-ACCESS read-create 1129 STATUS current 1130 DESCRIPTION 1131 "nhdpHtMaxJitter corresponds to 1132 HT_MAXJITTER of NHDP and represents the 1133 value of MAXJITTER used in RFC 5148 for 1134 externally triggered HELLO messages on this 1135 MANET interface. 1137 Guidance for setting this object may be found 1138 in Section 5 of RFC 5148, which indicates that: 1139 o nhdpHtMaxJitter <= nhdpHelloInterval / 2 1140 o nhdpHtMaxJitter should not be greater 1141 than nhdpHelloInterval / 4 1142 o If nhdpMinHelloInterval > 0, then 1143 nhdpHtMaxJitter <= nhdpHelloMinInterval; and 1144 nhdpHtMaxJitter should not be greater than 1145 nhdpHelloMinInterval / 2" 1146 REFERENCE 1147 "Section 5 of RFC 5148 - Jitter Considerations in 1148 Mobile Ad Hoc Networks (MANETs), 1149 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1150 DEFVAL { 500 } 1151 ::= { nhdpInterfaceEntry 14 } 1153 nhdpIfRowStatus OBJECT-TYPE 1154 SYNTAX RowStatus 1155 MAX-ACCESS read-create 1156 STATUS current 1157 DESCRIPTION 1158 "This object permits management of the table 1159 by facilitating actions such as row creation, 1160 construction, and destruction. The value of 1161 this object has no effect on whether other 1162 objects in this conceptual row can be 1163 modified. 1165 An entry may not exist in the 'active(1)' state unless all 1166 objects in the entry have a defined appropriate value. For 1167 objects with DEFVAL clauses, the management station 1168 does not need to specify the value of this object in order 1169 for the row to transit to the 'active(1)' state; the default 1170 value for this object is used. For objects that do not 1171 have DEFVAL clauses, then the network manager MUST 1172 specify the value of this object prior to this row 1173 transitioning to the 'active(1)' state. 1175 When this object transitions to 'active(1)', all objects 1176 in this row SHOULD be written to non-volatile (stable) 1177 storage. Read-create objects in this row MAY be modified. 1178 When an object in a row with nhdpIfRowStatus of 'active(1)' 1179 is changed, then the updated value MUST be reflected in NHDP, 1180 and this new object value MUST be written to non-volatile 1181 storage. 1183 If the value of this object is not equal to 'active(1)', 1184 all associated entries in the nhdpLibLocalIfSetTable, 1185 nhdpInterfaceStateTable, nhdpIibLinkSetTable, and 1186 nhdpInterfacePerfTable MUST be deleted." 1187 REFERENCE 1188 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1189 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1190 C., and J. Dean, April 2011" 1191 DEFVAL { active } 1192 ::= { nhdpInterfaceEntry 15 } 1194 -- 1195 -- Router Parameters - Information Validity Time 1196 -- 1197 nhdpNHoldTime OBJECT-TYPE 1198 SYNTAX Unsigned32 1199 UNITS "milliseconds" 1200 MAX-ACCESS read-write 1201 STATUS current 1202 DESCRIPTION 1203 "nhdpNHoldTime corresponds to 1204 N_HOLD_TIME of NHDP and is used as the period 1205 during which former 1-hop neighbor network 1206 addresses are advertised as lost in HELLO 1207 messages, allowing recipients of these HELLO 1208 messages to accelerate removal of this information 1209 from their 2-Hop Sets. 1211 This object is persistent, and when written, 1212 the entity SHOULD save the change to 1213 non-volatile storage." 1214 REFERENCE 1215 "Section 5 on Protocol Parameters and 1216 Constraints of RFC 6130 - Mobile Ad Hoc Network 1217 (MANET) Neighborhood Discovery Protocol (NHDP), 1218 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1219 DEFVAL { 6000 } 1220 ::= { nhdpConfigurationObjGrp 2 } 1222 nhdpIHoldTime OBJECT-TYPE 1223 SYNTAX Unsigned32 1224 UNITS "milliseconds" 1225 MAX-ACCESS read-write 1226 STATUS current 1227 DESCRIPTION 1228 "nhdpIHoldTime corresponds to 1229 I_HOLD_TIME of NHDP and represents the period 1230 for which a recently used local interface network 1231 address is recorded. 1233 This object is persistent, and when written, 1234 the entity SHOULD save the change to 1235 non-volatile storage." 1236 REFERENCE 1237 "Section 5 on Protocol Parameters and 1238 Constraints of RFC 6130 - Mobile Ad Hoc Network 1239 (MANET) Neighborhood Discovery Protocol (NHDP), 1240 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1241 DEFVAL { 6000 } 1242 ::= { nhdpConfigurationObjGrp 3 } 1244 -- A router's Local Information Base (LIB) 1246 -- 1247 -- Local Interface Set Table 1248 -- 1250 nhdpLibLocalIfSetTable OBJECT-TYPE 1251 SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "A router's Local Interface Set records all 1256 network addresses that are defined as local 1257 MANET interface network addresses. 1258 As such, this table 'sparse augments' the 1259 nhdpInterfaceTable when network addresses are 1260 being defined for the interfaces existing within 1261 the nhdpInterfaceTable. The local interface 1262 is defined by the nhdpIfIndex. 1264 The Local Interface Set consists of Local Interface 1265 Address Tuples per MANET interface and their prefix 1266 lengths (in order to determine the network addresses 1267 related to the interface). 1269 A conceptual row in this table exists if and only 1270 if a manager has explicitly created the row. The 1271 manager can create a row by setting rowStatus 1272 to 'createAndGo' or 'createAndWait'. 1274 Further guidance on the addition or removal of 1275 local addresses and network addresses is found 1276 in Section 9 of RFC 6130." 1277 REFERENCE 1278 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1279 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1280 C., and J. Dean, April 2011" 1281 ::= { nhdpConfigurationObjGrp 4 } 1283 nhdpLibLocalIfSetEntry OBJECT-TYPE 1284 SYNTAX NhdpLibLocalIfSetEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "A router's Local Interface Set consists 1289 of Configured Interface Address Tuples for each network 1290 interface. 1292 The objects in this table are persistent, and when 1293 written, the device SHOULD save the change to 1294 non-volatile storage. For further information 1295 on the storage behavior for these objects, refer 1296 to the description for the nhdpLibLocalIfSetRowStatus 1297 object." 1298 REFERENCE 1299 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1300 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1301 C., and J. Dean, April 2011" 1302 INDEX { nhdpLibLocalIfSetIndex } 1303 ::= { nhdpLibLocalIfSetTable 1 } 1305 NhdpLibLocalIfSetEntry ::= 1306 SEQUENCE { 1307 nhdpLibLocalIfSetIndex 1308 Integer32, 1309 nhdpLibLocalIfSetIfIndex 1310 InterfaceIndex, 1311 nhdpLibLocalIfSetIpAddrType 1312 InetAddressType, 1313 nhdpLibLocalIfSetIpAddr 1314 InetAddress, 1315 nhdpLibLocalIfSetIpAddrPrefixLen 1316 InetAddressPrefixLength, 1317 nhdpLibLocalIfSetRowStatus 1318 RowStatus 1319 } 1321 nhdpLibLocalIfSetIndex OBJECT-TYPE 1322 SYNTAX Integer32 (0..65535) 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "The index for this table. Necessary 1327 because multiple addresses may be associated 1328 with a given nhdpIfIndex." 1329 REFERENCE 1330 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1331 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1332 C., and J. Dean, April 2011" 1333 ::= { nhdpLibLocalIfSetEntry 1 } 1335 nhdpLibLocalIfSetIfIndex OBJECT-TYPE 1336 SYNTAX InterfaceIndex 1337 MAX-ACCESS read-only 1338 STATUS current 1339 DESCRIPTION 1340 "Specifies the local nhdpIfIndex for which this 1341 IP address was added." 1342 REFERENCE 1343 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1344 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1345 C., and J. Dean, April 2011" 1346 ::= { nhdpLibLocalIfSetEntry 2 } 1348 nhdpLibLocalIfSetIpAddrType OBJECT-TYPE 1349 SYNTAX InetAddressType 1350 MAX-ACCESS read-create 1351 STATUS current 1352 DESCRIPTION 1353 "The type of the nhdpLibLocalIfSetIpAddr 1354 in the InetAddress MIB (RFC 4001). 1356 Only the values 'ipv4(1)' and 1357 'ipv6(2)' are supported." 1358 REFERENCE 1359 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1360 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1361 C., and J. Dean, April 2011" 1362 ::= { nhdpLibLocalIfSetEntry 3 } 1364 nhdpLibLocalIfSetIpAddr OBJECT-TYPE 1365 SYNTAX InetAddress (SIZE(4|16)) 1366 MAX-ACCESS read-create 1367 STATUS current 1368 DESCRIPTION 1369 "nhdpLibLocalIfSetIpAddr is an 1370 address of an interface of 1371 this router. 1373 This object is interpreted according to 1374 the setting of nhdpLibLocalIfSetIpAddrType." 1375 REFERENCE 1376 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1377 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1378 C., and J. Dean, April 2011" 1379 ::= { nhdpLibLocalIfSetEntry 4 } 1381 nhdpLibLocalIfSetIpAddrPrefixLen OBJECT-TYPE 1382 SYNTAX InetAddressPrefixLength 1383 MAX-ACCESS read-create 1384 STATUS current 1385 DESCRIPTION 1386 "Indicates the number of leading one bits that 1387 form the mask. The mask is logically ANDed 1388 to the nhdpLibLocalIfSetIpAddr to determine 1389 the address prefix. A row match is true 1390 if the address used as an index falls within 1391 the network address range defined by the 1392 address prefix." 1393 REFERENCE 1394 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1395 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1396 C., and J. Dean, April 2011" 1397 ::= { nhdpLibLocalIfSetEntry 5 } 1399 nhdpLibLocalIfSetRowStatus OBJECT-TYPE 1400 SYNTAX RowStatus 1401 MAX-ACCESS read-create 1402 STATUS current 1403 DESCRIPTION 1404 "This object permits management of the table 1405 by facilitating actions such as row creation, 1406 construction, and destruction. The value of 1407 this object has no effect on whether other 1408 objects in this conceptual row can be 1409 modified. 1411 An entry may not exist in the 'active(1)' state unless all 1412 read-create objects in the entry have a defined 1413 appropriate value. As no objects in this table have 1414 DEFVAL clauses, the management station MUST specify 1415 the values of all read-create objects prior to this row 1416 transitioning to the 'active(1)' state. 1418 When this object transitions to 'active(1)', all objects 1419 in this row SHOULD be written to non-volatile (stable) 1420 storage. Read-create objects in this row MAY be modified. 1422 When an object in a row with nhdpIfRowStatus of 'active(1)' 1423 is changed, then the updated value MUST be reflected in NHDP, 1424 and this new object value MUST be written to non-volatile 1425 storage." 1426 REFERENCE 1427 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1428 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1429 C., and J. Dean, April 2011" 1430 DEFVAL { notReady } 1431 ::= { nhdpLibLocalIfSetEntry 6 } 1433 -- 1434 -- Removed Interface Addr Set Table 1435 -- 1437 nhdpLibRemovedIfAddrSetTable OBJECT-TYPE 1438 SYNTAX SEQUENCE OF NhdpLibRemovedIfAddrSetEntry 1439 MAX-ACCESS not-accessible 1440 STATUS current 1441 DESCRIPTION 1442 "A router's Removed Interface Address Set records 1443 network addresses that were recently used as local 1444 interface network addresses. If a router's interface 1445 network addresses are immutable, then the Removed 1446 Interface Address Set is always empty and may be omitted. 1447 It consists of Removed Interface Address Tuples, one 1448 per network address." 1449 REFERENCE 1450 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1451 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1452 C., and J. Dean, April 2011" 1453 ::= { nhdpConfigurationObjGrp 5 } 1455 nhdpLibRemovedIfAddrSetEntry OBJECT-TYPE 1456 SYNTAX NhdpLibRemovedIfAddrSetEntry 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "A router's Removed Interface Address Set consists 1461 of Removed Interface Address Tuples, one per network 1462 address: 1464 (IR_local_iface_addr, IR_time) 1466 The association between these addresses and the 1467 router's Interface is found in the Standard MIB II's 1468 IP address table (RFC 1213)." 1469 REFERENCE 1470 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1471 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1472 C., and J. Dean, April 2011" 1473 INDEX { nhdpLibRemovedIfAddrSetIndex } 1474 ::= { nhdpLibRemovedIfAddrSetTable 1 } 1476 NhdpLibRemovedIfAddrSetEntry ::= 1477 SEQUENCE { 1478 nhdpLibRemovedIfAddrSetIndex 1479 Integer32, 1480 nhdpLibRemovedIfAddrSetIpAddrType 1481 InetAddressType, 1482 nhdpLibRemovedIfAddrSetIpAddr 1483 InetAddress, 1484 nhdpLibRemovedIfAddrSetIpAddrPrefixLen 1485 InetAddressPrefixLength, 1486 nhdpLibRemovedIfAddrSetIfIndex 1487 InterfaceIndex, 1488 nhdpLibRemovedIfAddrSetIRTime 1489 TimeStamp 1490 } 1492 nhdpLibRemovedIfAddrSetIndex OBJECT-TYPE 1493 SYNTAX Integer32 (0..65535) 1494 MAX-ACCESS not-accessible 1495 STATUS current 1496 DESCRIPTION 1497 "The index for this table. Necessary 1498 because multiple addresses may be associated 1499 with a given nhdpIfIndex." 1500 REFERENCE 1501 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1502 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1503 C., and J. Dean, April 2011" 1504 ::= { nhdpLibRemovedIfAddrSetEntry 1 } 1506 nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE 1507 SYNTAX InetAddressType 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "The type of the nhdpLibRemovedIfAddrSetIpAddr 1512 in the InetAddress MIB (RFC 4001). 1514 Only the values 'ipv4(1)' and 1515 'ipv6(2)' are supported." 1517 REFERENCE 1518 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1519 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1520 C., and J. Dean, April 2011" 1521 ::= { nhdpLibRemovedIfAddrSetEntry 2 } 1523 nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE 1524 SYNTAX InetAddress (SIZE(4|16)) 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "nhdpLibRemovedIfAddrSetIpAddr is a 1529 recently used address of an interface of 1530 this router." 1531 REFERENCE 1532 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1533 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1534 C., and J. Dean, April 2011" 1535 ::= { nhdpLibRemovedIfAddrSetEntry 3 } 1537 nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE 1538 SYNTAX InetAddressPrefixLength 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "Indicates the number of leading one bits that 1543 form the mask. The mask is logically ANDed 1544 to the nhdpLibRemovedIfAddrSetIpAddr to determine 1545 the address prefix. A row match is true 1546 if the address used as an index falls within 1547 the network address range defined by the 1548 address prefix." 1549 REFERENCE 1550 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1551 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1552 C., and J. Dean, April 2011" 1553 ::= { nhdpLibRemovedIfAddrSetEntry 4 } 1555 nhdpLibRemovedIfAddrSetIfIndex OBJECT-TYPE 1556 SYNTAX InterfaceIndex 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "Specifies the local IfIndex from which this 1561 IP address was recently removed." 1562 REFERENCE 1563 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1564 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1565 C., and J. Dean, April 2011" 1566 ::= { nhdpLibRemovedIfAddrSetEntry 5 } 1568 nhdpLibRemovedIfAddrSetIRTime OBJECT-TYPE 1569 SYNTAX TimeStamp 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "nhdpLibRemovedIfAddrSetIRTime specifies the value 1574 of sysUptime when this entry should expire and be 1575 removed from the nhdpLibRemovedIfAddrSetTable." 1576 REFERENCE 1577 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1578 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1579 C., and J. Dean, April 2011" 1580 ::= { nhdpLibRemovedIfAddrSetEntry 6 } 1582 -- 1583 -- nhdpStateObjGrp 1584 -- 1586 -- Contains information describing the current state of the NHDP 1587 -- process on this router. 1589 nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 } 1591 nhdpUpTime OBJECT-TYPE 1592 SYNTAX TimeStamp 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "The value of sysUpTime at the time the current NHDP 1597 process was initialized." 1598 ::= { nhdpStateObjGrp 1 } 1600 nhdpInterfaceStateTable OBJECT-TYPE 1601 SYNTAX SEQUENCE OF NhdpInterfaceStateEntry 1602 MAX-ACCESS not-accessible 1603 STATUS current 1604 DESCRIPTION 1605 "nhdpInterfaceStateTable lists state information 1606 related to specific interfaces of this router. 1607 The value of nhdpIfIndex is an ifIndex from the 1608 interfaces group defined in the Interfaces Group 1609 MIB. 1611 The objects in this table are persistent, and when 1612 written, the entity SHOULD save the change to 1613 non-volatile storage." 1614 REFERENCE 1615 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1616 K., and F. Kastenholtz, June 2000." 1617 ::= { nhdpStateObjGrp 2 } 1619 nhdpInterfaceStateEntry OBJECT-TYPE 1620 SYNTAX NhdpInterfaceStateEntry 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "nhdpInterfaceStateEntry describes one NHDP 1625 local interface state as indexed by 1626 its nhdpIfIndex." 1627 INDEX { nhdpIfIndex } 1628 ::= { nhdpInterfaceStateTable 1 } 1630 NhdpInterfaceStateEntry ::= 1631 SEQUENCE { 1632 nhdpIfStateUpTime 1633 TimeStamp 1634 } 1636 nhdpIfStateUpTime OBJECT-TYPE 1637 SYNTAX TimeStamp 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "The value of the sysUpTime when 1642 NHDP was last initialized on this 1643 MANET interface." 1644 ::= { nhdpInterfaceStateEntry 1 } 1646 -- 1647 -- This table allows for the mapping between discovered 1648 -- remote interfaces and routers and their addresses. 1649 -- 1651 nhdpDiscIfSetTable OBJECT-TYPE 1652 SYNTAX SEQUENCE OF NhdpDiscIfSetEntry 1653 MAX-ACCESS not-accessible 1654 STATUS current 1655 DESCRIPTION 1656 "A router's set of discovered interfaces on 1657 neighboring routers." 1658 REFERENCE 1659 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1660 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1661 C., and J. Dean, April 2011" 1662 ::= { nhdpStateObjGrp 3 } 1664 nhdpDiscIfSetEntry OBJECT-TYPE 1665 SYNTAX NhdpDiscIfSetEntry 1666 MAX-ACCESS not-accessible 1667 STATUS current 1668 DESCRIPTION 1669 "The entries include the nhdpDiscRouterIndex of 1670 the discovered router, the nhdpDiscIfIndex 1671 of the discovered interface, and the 1672 current set of addresses associated 1673 with this neighbor interface. The 1674 nhdpDiscIfIndex uniquely identifies 1675 the remote interface address sets 1676 through this table. It does not need 1677 to be unique across the MANET but MUST 1678 be locally unique within this router." 1679 REFERENCE 1680 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1681 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1682 C., and J. Dean, April 2011" 1683 INDEX { nhdpDiscIfSetIndex } 1684 ::= { nhdpDiscIfSetTable 1 } 1686 NhdpDiscIfSetEntry ::= 1687 SEQUENCE { 1688 nhdpDiscIfSetIndex 1689 Integer32, 1690 nhdpDiscIfIndex 1691 NeighborIfIndex, 1692 nhdpDiscRouterIndex 1693 NeighborRouterIndex, 1694 nhdpDiscIfSetIpAddrType 1695 InetAddressType, 1696 nhdpDiscIfSetIpAddr 1697 InetAddress, 1698 nhdpDiscIfSetIpAddrPrefixLen 1699 InetAddressPrefixLength 1700 } 1702 nhdpDiscIfSetIndex OBJECT-TYPE 1703 SYNTAX Integer32 (0..65535) 1704 MAX-ACCESS not-accessible 1705 STATUS current 1706 DESCRIPTION 1707 "The index for this table. Necessary 1708 because multiple addresses may be associated 1709 with a given nhdpDiscIfIndex." 1710 REFERENCE 1711 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1712 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1713 C., and J. Dean, April 2011" 1714 ::= { nhdpDiscIfSetEntry 1 } 1716 nhdpDiscIfIndex OBJECT-TYPE 1717 SYNTAX NeighborIfIndex 1718 MAX-ACCESS read-only 1719 STATUS current 1720 DESCRIPTION 1721 "The NHDP interface index (locally created) 1722 of a neighbor's interface. Used for cross- 1723 indexing into other NHDP tables and other 1724 MIB modules." 1725 REFERENCE 1726 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1727 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1728 C., and J. Dean, April 2011" 1729 ::= { nhdpDiscIfSetEntry 2 } 1731 nhdpDiscRouterIndex OBJECT-TYPE 1732 SYNTAX NeighborRouterIndex 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "The NHDP neighbor index (locally created) 1737 of a neighboring router. Used for cross- 1738 indexing into other NHDP tables and other 1739 MIB modules." 1740 REFERENCE 1741 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1742 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1743 C., and J. Dean, April 2011" 1744 ::= { nhdpDiscIfSetEntry 3 } 1746 nhdpDiscIfSetIpAddrType OBJECT-TYPE 1747 SYNTAX InetAddressType 1748 MAX-ACCESS read-only 1749 STATUS current 1750 DESCRIPTION 1751 "The type of the nhdpDiscIfSetIpAddr 1752 in the InetAddress MIB (RFC 4001). 1754 Only the values 'ipv4(1)' and 1755 'ipv6(2)' are supported." 1756 REFERENCE 1757 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1758 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1759 C., and J. Dean, April 2011" 1760 ::= { nhdpDiscIfSetEntry 4 } 1762 nhdpDiscIfSetIpAddr OBJECT-TYPE 1763 SYNTAX InetAddress (SIZE(4|16)) 1764 MAX-ACCESS read-only 1765 STATUS current 1766 DESCRIPTION 1767 "The nhdpDiscIfSetIpAddr is a 1768 recently used address of a neighbor 1769 of this router." 1770 REFERENCE 1771 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1772 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1773 C., and J. Dean, April 2011" 1774 ::= { nhdpDiscIfSetEntry 5 } 1776 nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE 1777 SYNTAX InetAddressPrefixLength 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "Indicates the number of leading one bits that 1782 form the mask. The mask is logically ANDed 1783 to the nhdpDiscIfSetIpAddr to determine 1784 the address prefix. A row match is true 1785 if the address used as an index falls within 1786 the network address range defined by the 1787 address prefix." 1788 REFERENCE 1789 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1790 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1791 C., and J. Dean, April 2011" 1792 ::= { nhdpDiscIfSetEntry 6 } 1794 -- Interface Information Base (IIB) 1796 -- 1797 -- Link Set 1798 -- 1800 nhdpIibLinkSetTable OBJECT-TYPE 1801 SYNTAX SEQUENCE OF NhdpIibLinkSetEntry 1802 MAX-ACCESS not-accessible 1803 STATUS current 1804 DESCRIPTION 1805 "A Link Set of an interface records all links 1806 from other routers that are, or recently 1807 were, 1-hop neighbors." 1808 REFERENCE 1809 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1810 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1811 C., and J. Dean, April 2011" 1812 ::= { nhdpStateObjGrp 4 } 1814 nhdpIibLinkSetEntry OBJECT-TYPE 1815 SYNTAX NhdpIibLinkSetEntry 1816 MAX-ACCESS not-accessible 1817 STATUS current 1818 DESCRIPTION 1819 "A Link Set consists of Link Tuples, each 1820 representing a single link indexed by the 1821 local and remote interface pair: 1823 (L_neighbor_iface_addr_list, L_HEARD_time, 1824 L_SYM_time, L_quality, L_pending, 1825 L_lost, L_time). 1827 The local interface is indexed via the 1828 nhdpIfIndex. The 1-hop interface is 1829 indexed via the nhdpDiscIfIndex. There 1830 SHOULD be an entry in this table for each 1831 local interface and associated 1-hop 1832 neighbor reachable on this local interface. 1834 Note that L_quality is not included in the 1835 entries below, because updates may be 1836 required too frequently." 1837 REFERENCE 1838 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1839 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1840 C., and J. Dean, April 2011" 1841 INDEX { nhdpIfIndex, 1842 nhdpDiscIfIndex } 1843 ::= { 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 draft-ietf-manet-nhdp-optimization-04 - 1993 An Optimization for the MANET Neighborhood Discovery 1994 Protocol (NHDP), Dearlove, C., and T. Clausen, 1995 January 2015" 1996 INDEX { nhdpIfIndex, 1997 nhdpDiscIfIndex, 1998 nhdpIib2HopSetIpAddressType, 1999 nhdpIib2HopSetIpAddress 2000 } 2001 ::= { nhdpIib2HopSetTable 1 } 2003 NhdpIib2HopSetEntry ::= 2004 SEQUENCE { 2005 nhdpIib2HopSetIpAddressType 2006 InetAddressType, 2007 nhdpIib2HopSetIpAddress 2008 InetAddress, 2009 nhdpIib2HopSetIpAddrPrefixLen 2010 InetAddressPrefixLength, 2011 nhdpIib2HopSet1HopIfIndex 2012 NeighborIfIndex, 2013 nhdpIib2HopSetN2Lost 2014 TruthValue, 2015 nhdpIib2HopSetN2Time 2016 TimeStamp 2017 } 2019 nhdpIib2HopSetIpAddressType OBJECT-TYPE 2020 SYNTAX InetAddressType 2021 MAX-ACCESS not-accessible 2022 STATUS current 2023 DESCRIPTION 2024 "The type of the nhdpIib2HopSetIpAddress 2025 in the InetAddress MIB module (RFC 4001). 2027 Only the values 'ipv4(1)' and 2028 'ipv6(2)' are supported." 2029 REFERENCE 2030 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2031 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2032 C., and J. Dean, April 2011" 2033 ::= { 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" 2083 ::= { nhdpIib2HopSetEntry 4 } 2084 nhdpIib2HopSetN2Lost OBJECT-TYPE 2085 SYNTAX TruthValue 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and 2090 is a boolean flag, describing if for a 2-Hop Tuple, the 2091 corresponding Link Tuple currently is considered lost 2092 due to link quality." 2094 REFERENCE 2095 "draft-ietf-manet-nhdp-optimization-04 - 2096 An Optimization for the MANET Neighborhood Discovery 2097 Protocol (NHDP), Dearlove, C., and T. Clausen, 2098 January 2015" 2099 ::= {nhdpIib2HopSetEntry 5} 2101 nhdpIib2HopSetN2Time OBJECT-TYPE 2102 SYNTAX TimeStamp 2103 MAX-ACCESS read-only 2104 STATUS current 2105 DESCRIPTION 2106 "nhdpIib2HopSetN2Time specifies the value 2107 of sysUptime when this entry should expire and be 2108 removed from the nhdpIib2HopSetTable." 2109 REFERENCE 2110 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2111 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2112 C., and J. Dean, April 2011" 2113 ::= { nhdpIib2HopSetEntry 6 } 2115 -- 2116 -- Neighbor Information Base (NIB) 2117 -- 2118 -- Each router maintains a Neighbor Information Base 2119 -- that records information about addresses of 2120 -- current and recently symmetric 1-hop neighbors. 2122 -- 2123 -- Neighbor Set 2124 -- 2125 -- The Neighbor Set Table is small because 2126 -- most of the corresponding information is found 2127 -- in the nhdpDiscoveredIfTable above. 2128 -- 2129 nhdpNibNeighborSetTable OBJECT-TYPE 2130 SYNTAX SEQUENCE OF NhdpNibNeighborSetEntry 2131 MAX-ACCESS not-accessible 2132 STATUS current 2133 DESCRIPTION 2134 "A router's Neighbor Set records all 2135 network addresses of each 1-hop 2136 neighbor." 2137 REFERENCE 2138 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2139 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2140 C., and J. Dean, April 2011" 2141 ::= { nhdpStateObjGrp 6 } 2143 nhdpNibNeighborSetEntry OBJECT-TYPE 2144 SYNTAX NhdpNibNeighborSetEntry 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "A router's Neighbor Set consists 2149 of Neighbor Tuples, each representing 2150 a single 1-hop neighbor: 2152 (N_neighbor_addr_list, N_symmetric)" 2153 REFERENCE 2154 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2155 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2156 C., and J. Dean, April 2011" 2157 INDEX { nhdpDiscRouterIndex } 2158 ::= { nhdpNibNeighborSetTable 1 } 2160 NhdpNibNeighborSetEntry ::= 2161 SEQUENCE { 2162 nhdpNibNeighborSetNSymmetric 2163 TruthValue 2164 } 2166 nhdpNibNeighborSetNSymmetric OBJECT-TYPE 2167 SYNTAX TruthValue 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "nhdpNibNeighborNSymmetric corresponds 2172 to N_symmetric of NHDP and is a boolean flag, 2173 describing if this is a symmetric 1-hop neighbor." 2174 REFERENCE 2175 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2176 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2177 C., and J. Dean, April 2011" 2178 ::= { nhdpNibNeighborSetEntry 1 } 2180 -- 2181 -- Lost Neighbor Set 2182 -- 2183 nhdpNibLostNeighborSetTable OBJECT-TYPE 2184 SYNTAX SEQUENCE OF NhdpNibLostNeighborSetEntry 2185 MAX-ACCESS not-accessible 2186 STATUS current 2187 DESCRIPTION 2188 "A router's Lost Neighbor Set records network 2189 addresses of routers that were recently 2190 symmetric 1-hop neighbors but are now 2191 advertised as lost." 2192 REFERENCE 2193 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2194 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2195 C., and J. Dean, April 2011" 2196 ::= { nhdpStateObjGrp 7 } 2198 nhdpNibLostNeighborSetEntry OBJECT-TYPE 2199 SYNTAX NhdpNibLostNeighborSetEntry 2200 MAX-ACCESS not-accessible 2201 STATUS current 2202 DESCRIPTION 2203 "A router's Lost Neighbor Set consists of 2204 Lost Neighbor Tuples, each representing a 2205 single such network address: 2207 (NL_neighbor_addr, NL_time)" 2208 REFERENCE 2209 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2210 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2211 C., and J. Dean, April 2011" 2212 INDEX { nhdpDiscRouterIndex } 2213 ::= { nhdpNibLostNeighborSetTable 1 } 2215 NhdpNibLostNeighborSetEntry ::= 2216 SEQUENCE { 2217 nhdpNibLostNeighborSetNLTime 2218 TimeStamp 2219 } 2221 nhdpNibLostNeighborSetNLTime OBJECT-TYPE 2222 SYNTAX TimeStamp 2223 MAX-ACCESS read-only 2224 STATUS current 2225 DESCRIPTION 2226 "nhdpNibLostNeighborSetNLTime 2227 specifies the value of sysUptime when this entry 2228 should expire and be removed from the 2229 nhdpNibLostNeighborSetTable." 2230 REFERENCE 2231 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2232 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2233 C., and J. Dean, April 2011" 2234 ::= { nhdpNibLostNeighborSetEntry 1 } 2236 -- 2237 -- nhdpPerformanceObjGrp 2238 -- 2240 -- Contains objects that help to characterize the performance of 2241 -- the NHDP process, typically counters. 2242 -- 2243 nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 } 2245 -- 2246 -- Objects per local interface 2247 -- 2249 nhdpInterfacePerfTable OBJECT-TYPE 2250 SYNTAX SEQUENCE OF NhdpInterfacePerfEntry 2251 MAX-ACCESS not-accessible 2252 STATUS current 2253 DESCRIPTION 2254 "This table summarizes performance objects that are 2255 measured per local NHDP interface." 2256 REFERENCE 2257 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2258 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2259 C., and J. Dean, April 2011" 2260 ::= { nhdpPerformanceObjGrp 1 } 2262 nhdpInterfacePerfEntry OBJECT-TYPE 2263 SYNTAX NhdpInterfacePerfEntry 2264 MAX-ACCESS not-accessible 2265 STATUS current 2266 DESCRIPTION 2267 "A single entry contains performance counters for 2268 a local NHDP interface." 2269 INDEX { nhdpIfIndex } 2271 ::= { nhdpInterfacePerfTable 1 } 2273 NhdpInterfacePerfEntry ::= 2274 SEQUENCE { 2275 nhdpIfHelloMessageXmits 2276 Counter32, 2277 nhdpIfHelloMessageRecvd 2278 Counter32, 2279 nhdpIfHelloMessageXmitAccumulatedSize 2280 Counter64, 2281 nhdpIfHelloMessageRecvdAccumulatedSize 2282 Counter64, 2283 nhdpIfHelloMessageTriggeredXmits 2284 Counter32, 2285 nhdpIfHelloMessagePeriodicXmits 2286 Counter32, 2287 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount 2288 Counter32, 2289 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount 2290 Counter32, 2291 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount 2292 Counter32 2293 } 2295 nhdpIfHelloMessageXmits OBJECT-TYPE 2296 SYNTAX Counter32 2297 UNITS "messages" 2298 MAX-ACCESS read-only 2299 STATUS current 2300 DESCRIPTION 2301 "A counter is incremented each time a HELLO 2302 message has been transmitted on that interface." 2303 ::= { nhdpInterfacePerfEntry 1 } 2305 nhdpIfHelloMessageRecvd OBJECT-TYPE 2306 SYNTAX Counter32 2307 UNITS "messages" 2308 MAX-ACCESS read-only 2309 STATUS current 2310 DESCRIPTION 2311 "A counter is incremented each time a 2312 HELLO message has been received on that interface." 2313 ::= { nhdpInterfacePerfEntry 2 } 2315 nhdpIfHelloMessageXmitAccumulatedSize OBJECT-TYPE 2316 SYNTAX Counter64 2317 UNITS "octets" 2318 MAX-ACCESS read-only 2319 STATUS current 2320 DESCRIPTION 2321 "A counter is incremented by the number of octets in 2322 a HELLO message each time a 2323 HELLO message has been sent." 2324 ::= { nhdpInterfacePerfEntry 3 } 2326 nhdpIfHelloMessageRecvdAccumulatedSize OBJECT-TYPE 2327 SYNTAX Counter64 2328 UNITS "octets" 2329 MAX-ACCESS read-only 2330 STATUS current 2331 DESCRIPTION 2332 "A counter is incremented by the number of octets in 2333 a HELLO message each time a 2334 HELLO message has been received." 2335 ::= { nhdpInterfacePerfEntry 4 } 2337 nhdpIfHelloMessageTriggeredXmits OBJECT-TYPE 2338 SYNTAX Counter32 2339 UNITS "messages" 2340 MAX-ACCESS read-only 2341 STATUS current 2342 DESCRIPTION 2343 "A counter is incremented each time a triggered 2344 HELLO message has been sent." 2345 ::= { nhdpInterfacePerfEntry 5 } 2347 nhdpIfHelloMessagePeriodicXmits OBJECT-TYPE 2348 SYNTAX Counter32 2349 UNITS "messages" 2350 MAX-ACCESS read-only 2351 STATUS current 2352 DESCRIPTION 2353 "A counter is incremented each time a periodic 2354 HELLO message has been sent." 2355 ::= { nhdpInterfacePerfEntry 6 } 2357 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount OBJECT-TYPE 2358 SYNTAX Counter32 2359 UNITS "neighbors" 2360 MAX-ACCESS read-only 2361 STATUS current 2362 DESCRIPTION 2363 "A counter is incremented by the number of advertised 2364 symmetric neighbors in a HELLO each time a HELLO 2365 message has been sent." 2366 ::= { nhdpInterfacePerfEntry 7 } 2367 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount OBJECT-TYPE 2368 SYNTAX Counter32 2369 UNITS "neighbors" 2370 MAX-ACCESS read-only 2371 STATUS current 2372 DESCRIPTION 2373 "A counter is incremented by the number of advertised 2374 heard neighbors in a HELLO each time a HELLO 2375 message has been sent." 2376 ::= { nhdpInterfacePerfEntry 8 } 2378 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount OBJECT-TYPE 2379 SYNTAX Counter32 2380 UNITS "neighbors" 2381 MAX-ACCESS read-only 2382 STATUS current 2383 DESCRIPTION 2384 "A counter is incremented by the number of advertised 2385 lost neighbors in a HELLO each time a HELLO 2386 message has been sent." 2387 ::= { nhdpInterfacePerfEntry 9 } 2389 -- 2390 -- Objects per discovered neighbor interface 2391 -- 2392 nhdpDiscIfSetPerfTable OBJECT-TYPE 2393 SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry 2394 MAX-ACCESS not-accessible 2395 STATUS current 2396 DESCRIPTION 2397 "A router's set of performance properties for 2398 each discovered interface of a neighbor." 2399 REFERENCE 2400 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2401 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2402 C., and J. Dean, April 2011" 2403 ::= { nhdpPerformanceObjGrp 2 } 2405 nhdpDiscIfSetPerfEntry OBJECT-TYPE 2406 SYNTAX NhdpDiscIfSetPerfEntry 2407 MAX-ACCESS not-accessible 2408 STATUS current 2409 DESCRIPTION 2410 "There is an entry for each discovered 2411 interface of a neighbor." 2413 REFERENCE 2414 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2415 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2416 C., and J. Dean, April 2011" 2417 INDEX { nhdpDiscIfIndex } 2418 ::= { nhdpDiscIfSetPerfTable 1 } 2420 NhdpDiscIfSetPerfEntry ::= 2421 SEQUENCE { 2422 nhdpDiscIfRecvdPackets 2423 Counter32, 2424 nhdpDiscIfExpectedPackets 2425 Counter32 2426 } 2428 nhdpDiscIfRecvdPackets OBJECT-TYPE 2429 SYNTAX Counter32 2430 UNITS "packets" 2431 MAX-ACCESS read-only 2432 STATUS current 2433 DESCRIPTION 2434 "This counter increments each 2435 time this router receives a packet from that interface 2436 of the neighbor." 2437 REFERENCE 2438 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2439 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2440 C., and J. Dean, April 2011" 2441 ::= { nhdpDiscIfSetPerfEntry 1 } 2443 nhdpDiscIfExpectedPackets OBJECT-TYPE 2444 SYNTAX Counter32 2445 UNITS "packets" 2446 MAX-ACCESS read-only 2447 STATUS current 2448 DESCRIPTION 2449 "This counter increments by the number 2450 of missed packets from this neighbor based 2451 on the packet sequence number each time this 2452 router receives a packet from that interface 2453 of the neighbor." 2454 REFERENCE 2455 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2456 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2457 C., and J. Dean, April 2011" 2458 ::= { nhdpDiscIfSetPerfEntry 2 } 2459 -- 2460 -- Objects concerning the Neighbor Set 2461 -- 2462 nhdpNibNeighborSetChanges OBJECT-TYPE 2463 SYNTAX Counter32 2464 UNITS "changes" 2465 MAX-ACCESS read-only 2466 STATUS current 2467 DESCRIPTION 2468 "This counter increments each time the Neighbor Set changes. 2469 A change occurs whenever a new Neighbor Tuple has been 2470 added, a Neighbor Tuple has been removed, or any entry of 2471 a Neighbor Tuple has been modified." 2472 ::= { nhdpPerformanceObjGrp 3 } 2474 -- 2475 -- Objects per discovered neighbor 2476 -- 2477 nhdpDiscNeighborSetPerfTable OBJECT-TYPE 2478 SYNTAX SEQUENCE OF NhdpDiscNeighborSetPerfEntry 2479 MAX-ACCESS not-accessible 2480 STATUS current 2481 DESCRIPTION 2482 "A router's set of discovered neighbors and 2483 their properties." 2484 REFERENCE 2485 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2486 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2487 C., and J. Dean, April 2011" 2488 ::= { nhdpPerformanceObjGrp 4 } 2490 nhdpDiscNeighborSetPerfEntry OBJECT-TYPE 2491 SYNTAX NhdpDiscNeighborSetPerfEntry 2492 MAX-ACCESS not-accessible 2493 STATUS current 2494 DESCRIPTION 2495 "The entries include the nhdpDiscRouterIndex of 2496 the discovered router as well as performance 2497 objects related to changes of the Neighbor 2498 Set." 2499 REFERENCE 2500 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2501 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2502 C., and J. Dean, April 2011" 2503 INDEX { nhdpDiscRouterIndex } 2504 ::= { nhdpDiscNeighborSetPerfTable 1 } 2505 NhdpDiscNeighborSetPerfEntry ::= 2506 SEQUENCE { 2507 nhdpDiscNeighborNibNeighborSetChanges 2508 Counter32, 2509 nhdpDiscNeighborNibNeighborSetUpTime 2510 TimeStamp, 2511 nhdpDiscNeighborNibNeighborSetReachableLinkChanges 2512 Counter32 2513 } 2515 nhdpDiscNeighborNibNeighborSetChanges OBJECT-TYPE 2516 SYNTAX Counter32 2517 UNITS "changes" 2518 MAX-ACCESS read-only 2519 STATUS current 2520 DESCRIPTION 2521 "This object returns the number of changes 2522 to the given Neighbor Tuple." 2523 REFERENCE 2524 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2525 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2526 C., and J. Dean, April 2011" 2527 ::= { nhdpDiscNeighborSetPerfEntry 1 } 2529 nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE 2530 SYNTAX TimeStamp 2531 MAX-ACCESS read-only 2532 STATUS current 2533 DESCRIPTION 2534 "This object returns the sysUpTime when 2535 the neighbor becomes 'nbrup'. A neighbor is 2536 said to become 'nbrup' if a new nhdpNibNeighborSetEntry 2537 is created for a particular nhdpNibNeighborSetRouterIndex. 2538 It becomes 'nbrdown' if the entry for that neighbor 2539 has been deleted." 2540 REFERENCE 2541 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2542 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2543 C., and J. Dean, April 2011" 2544 ::= { nhdpDiscNeighborSetPerfEntry 2 } 2546 nhdpDiscNeighborNibNeighborSetReachableLinkChanges OBJECT-TYPE 2547 SYNTAX Counter32 2548 UNITS "changes" 2549 MAX-ACCESS read-only 2550 STATUS current 2551 DESCRIPTION 2552 "This object counts each time the neighbor changes 2553 the interface(s) over which it is reachable. 2554 A change in the set of Link Tuples corresponding 2555 to the appropriate Neighbor Tuple is registered, 2556 i.e., a corresponding Link Tuple is added or removed 2557 from the set of all corresponding Link Tuples." 2558 REFERENCE 2559 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2560 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2561 C., and J. Dean, April 2011" 2562 ::= { nhdpDiscNeighborSetPerfEntry 3 } 2564 -- 2565 -- Objects per discovered 2-hop neighbor 2566 -- 2567 nhdpIib2HopSetPerfTable OBJECT-TYPE 2568 SYNTAX SEQUENCE OF NhdpIib2HopSetPerfEntry 2569 MAX-ACCESS not-accessible 2570 STATUS current 2571 DESCRIPTION 2572 "This table contains performance objects per 2573 discovered 2-hop neighbor." 2574 REFERENCE 2575 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2576 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2577 C., and J. Dean, April 2011" 2578 ::= { nhdpPerformanceObjGrp 5 } 2580 nhdpIib2HopSetPerfEntry OBJECT-TYPE 2581 SYNTAX NhdpIib2HopSetPerfEntry 2582 MAX-ACCESS not-accessible 2583 STATUS current 2584 DESCRIPTION 2585 "The entries contain performance objects per 2586 discovered 2-hop neighbor." 2587 REFERENCE 2588 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2589 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2590 C., and J. Dean, April 2011" 2591 INDEX { nhdpDiscRouterIndex } 2592 ::= { nhdpIib2HopSetPerfTable 1 } 2594 NhdpIib2HopSetPerfEntry ::= 2595 SEQUENCE { 2596 nhdpIib2HopSetPerfChanges 2597 Counter32, 2598 nhdpIib2HopSetPerfUpTime 2599 TimeStamp 2600 } 2602 nhdpIib2HopSetPerfChanges OBJECT-TYPE 2603 SYNTAX Counter32 2604 UNITS "changes" 2605 MAX-ACCESS read-only 2606 STATUS current 2607 DESCRIPTION 2608 "This object counts the changes of the union of all 2609 N2_neighbor_iface_addr_list of 2-Hop Tuples with an 2610 N2_2hop_addr equal to one of the given 2-hop 2611 neighbor's addresses." 2612 REFERENCE 2613 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2614 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2615 C., and J. Dean, April 2011" 2616 ::= { nhdpIib2HopSetPerfEntry 1 } 2618 nhdpIib2HopSetPerfUpTime OBJECT-TYPE 2619 SYNTAX TimeStamp 2620 MAX-ACCESS read-only 2621 STATUS current 2622 DESCRIPTION 2623 "This object returns the sysUpTime 2624 when the 2-Hop Tuple 2625 corresponding to the given 2-hop neighbor IP address 2626 was registered in the nhdpIib2HopSetTable." 2627 REFERENCE 2628 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2629 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2630 C., and J. Dean, April 2011" 2631 ::= { nhdpIib2HopSetPerfEntry 2 } 2633 -- 2634 -- nhdpNotifications 2635 -- 2637 nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 0 } 2638 nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 } 2639 nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 2 } 2640 -- nhdpNotificationsObjects 2642 nhdpNbrStateChange NOTIFICATION-TYPE 2643 OBJECTS { nhdpIfName, -- The originator of 2644 -- the notification. 2645 nhdpNbrState -- The new state 2646 } 2647 STATUS current 2648 DESCRIPTION 2649 "nhdpNbrStateChange is a notification sent when 2650 more than nhdpNbrStateChangeThreshold neighbors change 2651 their status (i.e., 'down(0)', 'asymmetric(1)', or 2652 'symmetric(2)') within a time window of 2653 nhdpNbrStateChangeWindow." 2654 ::= { nhdpNotificationsObjects 1 } 2656 nhdp2HopNbrStateChange NOTIFICATION-TYPE 2657 OBJECTS { nhdpIfName, -- The originator 2658 -- of the notification 2659 nhdp2HopNbrState -- The new state 2660 } 2661 STATUS current 2662 DESCRIPTION 2663 "nhdp2HopNbrStateChange is a notification sent 2664 when more than nhdp2HopNbrStateChangeThreshold 2-hop 2665 neighbors change their nhdp2HopNbrState 2666 within a time window of 2667 nhdp2HopNbrStateChangeWindow." 2668 ::= { nhdpNotificationsObjects 2 } 2670 nhdpIfStateChange NOTIFICATION-TYPE 2671 OBJECTS { nhdpIfName, -- The local interface 2672 nhdpIfStatus -- The new status 2673 } 2674 STATUS current 2675 DESCRIPTION 2676 "nhdpIfStateChange is a notification sent when 2677 nhdpIfStatus has changed on this interface." 2678 ::= { nhdpNotificationsObjects 3 } 2680 -- nhdpNotificationsControl 2682 nhdpNbrStateChangeThreshold OBJECT-TYPE 2683 SYNTAX Integer32 (0..255) 2684 UNITS "changes" 2685 MAX-ACCESS read-write 2686 STATUS current 2687 DESCRIPTION 2688 "A threshold value for the 2689 nhdpNbrStateChange object. If the 2690 number of occurrences exceeds this threshold 2691 within the previous nhdpNbrStateChangeWindow, 2692 then the nhdpNbrStateChange notification 2693 is to be sent. 2695 It is recommended that the value of this 2696 threshold be set to at least 10 and higher 2697 in dense topologies with frequent expected 2698 topology changes." 2699 DEFVAL { 10 } 2700 ::= { nhdpNotificationsControl 1 } 2702 nhdpNbrStateChangeWindow OBJECT-TYPE 2703 SYNTAX TimeTicks 2704 MAX-ACCESS read-write 2705 STATUS current 2706 DESCRIPTION 2707 "A time window for the 2708 nhdpNbrStateChange object. If the 2709 number of occurrences exceeds the 2710 nhdpNbrStateChangeThreshold 2711 within the previous nhdpNbrStateChangeWindow, 2712 then the nhdpNbrStateChange notification 2713 is to be sent. 2715 It is recommended that the value for this 2716 window be set to at least 5 times the 2717 nhdpHelloInterval. 2719 This object represents the time in hundredths 2720 of a second." 2721 DEFVAL { 1000 } 2722 ::= { nhdpNotificationsControl 2 } 2724 nhdp2HopNbrStateChangeThreshold OBJECT-TYPE 2725 SYNTAX Integer32 (0..255) 2726 UNITS "changes" 2727 MAX-ACCESS read-write 2728 STATUS current 2729 DESCRIPTION 2730 "A threshold value for the 2731 nhdp2HopNbrStateChange object. If the 2732 number of occurrences exceeds this threshold 2733 within the previous nhdp2HopNbrStateChangeWindow, 2734 then the nhdp2HopNbrStateChange notification 2735 is to be sent. 2737 It is recommended that the value of this 2738 threshold be set to at least 10 and higher 2739 when topologies are expected to be highly dynamic." 2740 DEFVAL { 10 } 2741 ::= { nhdpNotificationsControl 3 } 2743 nhdp2HopNbrStateChangeWindow OBJECT-TYPE 2744 SYNTAX TimeTicks 2745 MAX-ACCESS read-write 2746 STATUS current 2747 DESCRIPTION 2748 "A time window for the 2749 nhdp2HopNbrStateChange object. If the 2750 number of occurrences exceeds the 2751 nhdp2HopNbrStateChangeThreshold 2752 within the previous nhdp2HopNbrStateChangeWindow, 2753 then the nhdp2HopNbrStateChange notification 2754 is to be sent. 2756 It is recommended that the value for this 2757 window be set to at least 5 times 2758 nhdpHelloInterval. 2760 This object represents the time in hundredths 2761 of a second." 2762 DEFVAL { 1000 } 2763 ::= { nhdpNotificationsControl 4 } 2765 -- nhdpNotificationStates 2767 nhdpNbrState OBJECT-TYPE 2768 SYNTAX INTEGER { 2769 down(0), 2770 asymmetric(1), 2771 symmetric(2) 2772 } 2773 MAX-ACCESS read-only 2774 STATUS current 2775 DESCRIPTION 2776 "NHDP neighbor states. In NHDP, it is not 2777 necessary to remove Protocol Tuples from Protocol Sets 2778 at the exact time indicated, only to behave as if the 2779 Protocol Tuples were removed at that time. This case is 2780 indicated here as 'down(0)', all other cases being 2781 indicated as 'asymmetric(1)' or 'symmetric(2)'. If 'down(0)', 2782 the direct neighbor is also added to the 2783 nhdpNibLostNeighborSetTable." 2784 ::= { nhdpNotificationsStates 1 } 2786 nhdp2HopNbrState OBJECT-TYPE 2787 SYNTAX INTEGER { 2788 down(0), 2789 up(1), 2790 notconsidered(2) 2791 } 2792 MAX-ACCESS read-only 2793 STATUS current 2794 DESCRIPTION 2795 "NHDP 2-hop neighbor states. In NHDP, it is not necessary 2796 to remove Protocol Tuples from Protocol Sets at the 2797 exact time indicated, only to behave as if the Protocol 2798 Tuples were removed at that time. This case is indicated 2799 here as 'down(0)'; otherwise, it is either 'up(1)', if 2800 N2_lost for the 2-Hop Tuple is equal to false, or 2801 'notconsidered(2)' otherwise." 2802 ::= { nhdpNotificationsStates 2 } 2804 -- 2805 -- nhdpConformance information 2806 -- 2808 nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 } 2809 nhdpMIBGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 } 2811 -- Compliance Statements 2812 nhdpBasicCompliance MODULE-COMPLIANCE 2813 STATUS current 2814 DESCRIPTION 2815 "The basic implementation requirements for 2816 managed network entities that implement 2817 NHDP." 2818 MODULE -- this module 2819 MANDATORY-GROUPS { nhdpConfigurationGroup } 2820 ::= { nhdpCompliances 1 } 2822 nhdpFullCompliance2 MODULE-COMPLIANCE 2823 STATUS current 2824 DESCRIPTION 2825 "The full implementation requirements for 2826 managed network entities that implement 2827 NHDP." 2828 MODULE -- this module 2829 MANDATORY-GROUPS { nhdpConfigurationGroup, 2830 nhdpStateGroup2, 2831 nhdpNotificationObjectGroup, 2832 nhdpNotificationGroup, 2833 nhdpPerformanceGroup 2834 } 2835 ::= { nhdpCompliances 3 } 2837 -- 2838 -- Units of Conformance 2839 -- 2841 nhdpConfigurationGroup OBJECT-GROUP 2842 OBJECTS { 2843 nhdpIfName, 2844 nhdpIfStatus, 2845 nhdpHelloInterval, 2846 nhdpHelloMinInterval, 2847 nhdpRefreshInterval, 2848 nhdpLHoldTime, 2849 nhdpHHoldTime, 2850 nhdpHystAcceptQuality, 2851 nhdpHystRejectQuality, 2852 nhdpInitialQuality, 2853 nhdpInitialPending, 2854 nhdpHpMaxJitter, 2855 nhdpHtMaxJitter, 2856 nhdpNHoldTime, 2857 nhdpIHoldTime, 2858 nhdpIfRowStatus, 2859 nhdpLibLocalIfSetIfIndex, 2860 nhdpLibLocalIfSetIpAddrType, 2861 nhdpLibLocalIfSetIpAddr, 2862 nhdpLibLocalIfSetIpAddrPrefixLen, 2863 nhdpLibLocalIfSetRowStatus, 2864 nhdpLibRemovedIfAddrSetIpAddrType, 2865 nhdpLibRemovedIfAddrSetIpAddr, 2866 nhdpLibRemovedIfAddrSetIpAddrPrefixLen, 2867 nhdpLibRemovedIfAddrSetIfIndex, 2868 nhdpLibRemovedIfAddrSetIRTime 2869 } 2870 STATUS current 2871 DESCRIPTION 2872 "Set of NHDP configuration objects implemented 2873 in this module." 2875 ::= { nhdpMIBGroups 2 } 2877 nhdpPerformanceGroup OBJECT-GROUP 2878 OBJECTS { 2879 nhdpIfHelloMessageXmits, 2880 nhdpIfHelloMessageRecvd, 2881 nhdpIfHelloMessageXmitAccumulatedSize, 2882 nhdpIfHelloMessageRecvdAccumulatedSize, 2883 nhdpIfHelloMessageTriggeredXmits, 2884 nhdpIfHelloMessagePeriodicXmits, 2885 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount, 2886 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount, 2887 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount, 2888 nhdpDiscIfRecvdPackets, 2889 nhdpDiscIfExpectedPackets, 2890 nhdpNibNeighborSetChanges, 2891 nhdpDiscNeighborNibNeighborSetChanges, 2892 nhdpDiscNeighborNibNeighborSetUpTime, 2893 nhdpDiscNeighborNibNeighborSetReachableLinkChanges, 2894 nhdpIib2HopSetPerfChanges, 2895 nhdpIib2HopSetPerfUpTime 2896 } 2897 STATUS current 2898 DESCRIPTION 2899 "Set of NHDP performance objects implemented 2900 in this module." 2901 ::= { nhdpMIBGroups 4 } 2903 nhdpNotificationObjectGroup OBJECT-GROUP 2904 OBJECTS { 2905 nhdpNbrStateChangeThreshold, 2906 nhdpNbrStateChangeWindow, 2907 nhdp2HopNbrStateChangeThreshold, 2908 nhdp2HopNbrStateChangeWindow, 2909 nhdpNbrState, 2910 nhdp2HopNbrState 2911 } 2912 STATUS current 2913 DESCRIPTION 2914 "Set of NHDP notification objects implemented 2915 in this module." 2916 ::= { nhdpMIBGroups 5 } 2918 nhdpNotificationGroup NOTIFICATION-GROUP 2919 NOTIFICATIONS { 2920 nhdpNbrStateChange, 2921 nhdp2HopNbrStateChange, 2922 nhdpIfStateChange 2923 } 2924 STATUS current 2925 DESCRIPTION 2926 "Set of NHDP notifications implemented 2927 in this module." 2928 ::= { nhdpMIBGroups 6 } 2930 nhdpStateGroup2 OBJECT-GROUP 2931 OBJECTS { 2932 nhdpUpTime, 2933 nhdpIfStateUpTime, 2934 nhdpDiscRouterIndex, 2935 nhdpDiscIfIndex, 2936 nhdpDiscIfSetIpAddrType, 2937 nhdpDiscIfSetIpAddr, 2938 nhdpDiscIfSetIpAddrPrefixLen, 2939 nhdpIibLinkSetLHeardTime, 2940 nhdpIibLinkSetLSymTime, 2941 nhdpIibLinkSetLPending, 2942 nhdpIibLinkSetLLost, 2943 nhdpIibLinkSetLTime, 2944 nhdpIib2HopSetIpAddrPrefixLen, 2945 nhdpIib2HopSet1HopIfIndex, 2946 nhdpIib2HopSetN2Time, 2947 nhdpIib2HopSetN2Lost, 2948 nhdpNibNeighborSetNSymmetric, 2949 nhdpNibLostNeighborSetNLTime 2950 } 2951 STATUS current 2952 DESCRIPTION 2953 "Set of NHDP state objects implemented 2954 in this module." 2955 ::= { nhdpMIBGroups 7 } 2957 -- 2958 -- Deprecated compliance statements and groups 2959 -- 2961 nhdpFullCompliance MODULE-COMPLIANCE 2962 STATUS deprecated 2963 DESCRIPTION 2964 "The full implementation requirements for 2965 managed network entities that implement 2966 NHDP. 2968 For version-independence, this compliance statement 2969 is deprecated in favor of nhdpFullCompliance2." 2970 MODULE -- this module 2971 MANDATORY-GROUPS { nhdpConfigurationGroup, 2972 nhdpStateGroup, 2973 nhdpNotificationObjectGroup, 2974 nhdpNotificationGroup, 2975 nhdpPerformanceGroup 2976 } 2977 ::= { nhdpCompliances 2 } 2979 nhdpStateGroup OBJECT-GROUP 2980 OBJECTS { 2981 nhdpUpTime, 2982 nhdpIfStateUpTime, 2983 nhdpDiscRouterIndex, 2984 nhdpDiscIfIndex, 2985 nhdpDiscIfSetIpAddrType, 2986 nhdpDiscIfSetIpAddr, 2987 nhdpDiscIfSetIpAddrPrefixLen, 2988 nhdpIibLinkSetLHeardTime, 2989 nhdpIibLinkSetLSymTime, 2990 nhdpIibLinkSetLPending, 2991 nhdpIibLinkSetLLost, 2992 nhdpIibLinkSetLTime, 2993 nhdpIib2HopSetIpAddrPrefixLen, 2994 nhdpIib2HopSet1HopIfIndex, 2995 nhdpIib2HopSetN2Time, 2996 nhdpNibNeighborSetNSymmetric, 2997 nhdpNibLostNeighborSetNLTime 2998 } 2999 STATUS deprecated 3000 DESCRIPTION 3001 "Set of NHDP state objects implemented 3002 in this module. 3004 For version-independence, this compliance statement 3005 is deprecated in favor of nhdpStateGroup2." 3006 ::= { nhdpMIBGroups 3 } 3008 END 3010 8. Security Considerations 3012 This MIB module defines objects for the configuration, monitoring, 3013 and notification of the Neighborhood Discovery Protocol [RFC6130]. 3014 NHDP allows routers to acquire topological information up to two hops 3015 away by virtue of exchanging HELLO messages. The information 3016 acquired by NHDP may be used by routing protocols. The neighborhood 3017 information, exchanged between routers using NHDP, serves these 3018 routing protocols as a baseline for calculating paths to all 3019 destinations in the MANET, relay set selection for network-wide 3020 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 Neighborhood Discovery Protocol [RFC6130] process on a router. This 3107 MIB module, denoted NHDP-MIB, also reports state, performance 3108 information, and notifications. This section provides some examples 3109 of how this MIB module can be used in MANET network deployments. A 3110 fuller discussion of MANET network management use cases and 3111 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 3171 in RFCs to Indicate Requirement 3172 Levels", BCP 14, RFC 2119, 3173 March 1997. 3175 [RFC2578] McCloghrie, K., Ed., Perkins, 3176 D., Ed., and J. Schoenwaelder, 3177 Ed., "Structure of Management 3178 Information Version 2 (SMIv2)", 3179 STD 58, RFC 2578, April 1999. 3181 [RFC2579] McCloghrie, K., Ed., Perkins, 3182 D., Ed., and J. Schoenwaelder, 3183 Ed., "Textual Conventions for 3184 SMIv2", STD 58, RFC 2579, 3185 April 1999. 3187 [RFC2580] McCloghrie, K., Perkins, D., 3188 and J. Schoenwaelder, 3189 "Conformance Statements for 3190 SMIv2", STD 58, RFC 2580, 3191 April 1999. 3193 [RFC2863] McCloghrie, K. and F. 3194 Kastenholz, "The Interfaces 3195 Group MIB", RFC 2863, 3196 June 2000. 3198 [RFC3418] Presuhn, R., "Management 3199 Information Base (MIB) for the 3200 Simple Network Management 3201 Protocol (SNMP)", STD 62, 3202 RFC 3418, December 2002. 3204 [RFC4001] Daniele, M., Haberman, B., 3205 Routhier, S., and J. 3206 Schoenwaelder, "Textual 3207 Conventions for Internet 3208 Network Addresses", RFC 4001, 3209 February 2005. 3211 [RFC6130] Clausen, T., Dearlove, C., and 3212 J. Dean, "Mobile Ad Hoc Network 3213 (MANET) Neighborhood Discovery 3214 Protocol (NHDP)", RFC 6130, 3215 April 2011. 3217 [RFC6340] Presuhn, R., "Textual 3218 Conventions for the 3219 Representation of Floating- 3220 Point Numbers", RFC 6340, 3221 August 2011. 3223 [draft-ietf-manet-nhdp-optimization] Dearlove, C. and T. Clausen, 3224 "An Optimization for the MANET 3225 Neighborhood Discovery Protocol 3226 (NHDP)", work in progress draft 3227 -ietf-manet-nhdp-optimization- 3228 04, January 2015. 3230 12.2. Informative References 3232 [RFC3410] Case, J., Mundy, R., Partain, 3233 D., and B. Stewart, 3234 "Introduction and Applicability 3235 Statements for Internet- 3236 Standard Management Framework", 3237 RFC 3410, December 2002. 3239 [RFC3414] Blumenthal, U. and B. Wijnen, 3240 "User-based Security Model 3241 (USM) for version 3 of the 3242 Simple Network Management 3243 Protocol (SNMPv3)", STD 62, 3244 RFC 3414, December 2002. 3246 [RFC3826] Blumenthal, U., Maino, F., and 3247 K. McCloghrie, "The Advanced 3248 Encryption Standard (AES) 3249 Cipher Algorithm in the SNMP 3250 User-based Security Model", 3251 RFC 3826, June 2004. 3253 [RFC4750] Joyal, D., Galecki, P., 3254 Giacalone, S., Coltun, R., and 3255 F. Baker, "OSPF Version 2 3256 Management Information Base", 3257 RFC 4750, December 2006. 3259 [RFC5148] Clausen, T., Dearlove, C., and 3260 B. Adamson, "Jitter 3261 Considerations in Mobile Ad Hoc 3262 Networks (MANETs)", RFC 5148, 3263 February 2008. 3265 [RFC5591] Harrington, D. and W. Hardaker, 3266 "Transport Security Model for 3267 the Simple Network Management 3268 Protocol (SNMP)", RFC 5591, 3269 June 2009. 3271 [RFC5592] Harrington, D., Salowey, J., 3272 and W. Hardaker, "Secure Shell 3273 Transport Model for the Simple 3274 Network Management Protocol 3275 (SNMP)", RFC 5592, June 2009. 3277 [RFC6353] Hardaker, W., "Transport Layer 3278 Security (TLS) Transport Model 3279 for the Simple Network 3280 Management Protocol (SNMP)", 3281 RFC 6353, July 2011. 3283 [RFC6779] Herberg, U., Cole, R., and I. 3284 Chakeres, "Definition of 3285 Managed Objects for the 3286 Neighborhood Discovery 3287 Protocol", RFC 6779, 3288 October 2012. 3290 Authors' Addresses 3292 Ulrich Herberg 3293 United States 3295 EMail: ulrich@herberg.name 3296 URI: http://www.herberg.name/ 3297 Robert G. Cole 3298 US Army CERDEC 3299 Space and Terrestrial Communications 3300 6010 Frankford Road 3301 Aberdeen Proving Ground, Maryland 21005 3302 United States 3304 Phone: +1 443 395-8744 3305 EMail: robert.g.cole@us.army.mil 3306 URI: http://www.cs.jhu.edu/~rgcole/ 3308 Ian D Chakeres 3309 Delvin 3310 Ellicott City, Maryland 21042 3311 United States 3313 EMail: ian.chakeres@gmail.com 3314 URI: http://www.ianchak.com/ 3316 Thomas Heide Clausen 3317 LIX, Ecole Polytechnique 3319 Phone: +33 6 6058 9349 3320 EMail: T.Clausen@computer.org 3321 URI: http://www.ThomasClausen.org/