idnits 2.17.1 draft-ietf-manet-rfc6779bis-02.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-02 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 . . . . . . . . . . . . . . . . . . . 65 85 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 67 86 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68 87 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 68 88 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 68 89 12.1. Normative References . . . . . . . . . . . . . . . . . . . 68 90 12.2. Informative References . . . . . . . . . . . . . . . . . . 69 92 1. Introduction 94 This document defines a portion of the Management Information Base 95 (MIB) for use with network management protocols in the Internet 96 community. In particular, it describes objects for configuring 97 parameters of the 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 "201503031000Z" -- 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/documents 499 Editors: Ulrich Herberg 500 USA 502 ulrich@herberg.name 503 http://www.herberg.name/ 505 Robert G. Cole 506 US Army CERDEC 507 Space and Terrestrial Communications 508 6010 Frankford Street 509 Aberdeen Proving Ground, Maryland 21005 510 USA 511 +1 443 395-8744 513 robert.g.cole@us.army.mil 514 http://www.cs.jhu.edu/~rgcole/ 516 Ian D Chakeres 517 Delvin 518 Ellicott City, Maryland 21042 519 USA 520 ian.chakeres@gmail.com 521 http://www.ianchak.com/ 523 Thomas Heide Clausen 524 Ecole Polytechnique 525 LIX 526 91128 Palaiseau Cedex 527 France 528 Email: T.Clausen@computer.org 529 URI: http://www.thomasclausen.org/" 531 DESCRIPTION 532 "This NHDP-MIB module is applicable to routers 533 implementing the Neighborhood Discovery Protocol 534 defined in RFC 6130. 536 Copyright (c) 2014 IETF Trust and the persons 537 identified as authors of the code. All rights reserved. 539 Redistribution and use in source and binary forms, with 540 or without modification, is permitted pursuant to, and 541 subject to the license terms contained in, the Simplified 542 BSD License set forth in Section 4.c of the IETF Trust's 543 Legal Provisions Relating to IETF Documents 544 (http://trustee.ietf.org/license-info). 546 This version of this MIB module is part of RFC 6779; see 547 the RFC itself for full legal notices." 549 -- revision 550 REVISION "201503031000Z" -- 3 March 2015 551 DESCRIPTION 552 "Updated version of this MIB module, 553 including updates made to NHDP by 554 draft-ietf-manet-nhdp-optimization, 555 published as RFC xxxx." 556 REVISION "201210221000Z" -- 22 October 2012 557 DESCRIPTION 558 "Initial version of this MIB module, 559 published as RFC 6779." 560 ::= { mib-2 213 } 562 -- 563 -- Top-Level Components of this MIB Module 564 -- 565 nhdpNotifications OBJECT IDENTIFIER ::= { nhdpMIB 0 } 566 nhdpObjects OBJECT IDENTIFIER ::= { nhdpMIB 1 } 567 nhdpConformance OBJECT IDENTIFIER ::= { nhdpMIB 2 } 568 -- 569 -- TEXTUAL-CONVENTIONs 570 -- 571 -- Two new TEXTUAL-CONVENTIONs have been defined in 572 -- this MIB module for indexing into the following 573 -- tables and indexing into other tables in other MIB modules. 574 -- This was necessary because NHDP manages and 575 -- indexes based upon dynamic address tuples, i.e., 576 -- address sets, while SMI requires statically 577 -- defined indexes for accessing its table rows. 578 -- The NeighborIfIndex defines a unique (to the local router) 579 -- index referencing a discovered virtual interface on another 580 -- neighbor within the MANET. The NeighborRouterIndex defines a 581 -- unique (to the local router) index referencing a discovered 582 -- virtual neighbor within the MANET. 583 -- 584 -- Due to the nature of NHDP, 585 -- different indexes may be related to common neighbor 586 -- interfaces or common neighbor routers, but the information 587 -- obtained through NHDP has not allowed the local router 588 -- to relate these virtual objects (i.e., interfaces or routers) 589 -- at this point in time. As more topology information 590 -- is gathered by the local router, it may associate 591 -- virtual interfaces or routers and collapse these 592 -- indexes appropriately. 594 -- Multiple addresses can be associated with a 595 -- given NeighborIfIndex. Each NeighborIfIndex is 596 -- associated with a NeighborRouterIndex. Throughout 597 -- the nhdpStateObjGroup, the 598 -- NeighborIfIndex and the NeighborRouterIndex are used 599 -- to define the set of IpAddrs related to a virtual 600 -- neighbor interface or virtual neighbor under discussion. 602 NeighborIfIndex ::= TEXTUAL-CONVENTION 603 DISPLAY-HINT "d" 604 STATUS current 605 DESCRIPTION 606 "An arbitrary, locally unique identifier associated with a 607 virtual interface of a discovered NHDP neighbor. 608 Due to the nature of NHDP, the local router 609 may not know if two distinct addresses belong to the 610 same interface of a neighbor or to two different 611 interfaces. As the local router gains more 612 knowledge of its neighbors, its local view may change, and 613 this table will be updated to reflect the local router's 614 current understanding, associating address sets to neighbor 615 interfaces. The local router identifies a virtual neighbor 616 interface through the receipt of address lists advertised 617 through an NHDP HELLO message. 619 All objects of type NeighborIfIndex are assigned by the agent 620 out of a common number space. 622 The value for each discovered virtual neighbor 623 interface may not remain constant from 624 one re-initialization of the entity's network management 625 agent to the next re-initialization. If the 626 local router gains information associating two virtual 627 interfaces on a neighbor as a common interface, 628 then the agent MUST aggregate the two address sets to 629 a single index chosen from the set of aggregated indexes, 630 and it MUST update all tables in this 631 MIB module that are indexed by indexes 632 of type NeighborIfIndex. It MAY then reuse freed 633 index values following the next agent restart. 635 The specific value is meaningful only within a given SNMP 636 entity." 637 SYNTAX Unsigned32 (1..2147483647) 639 NeighborRouterIndex ::= TEXTUAL-CONVENTION 640 DISPLAY-HINT "d" 641 STATUS current 642 DESCRIPTION 643 "An arbitrary, locally unique identifier associated with a 644 virtual discovered neighbor (one or two hop). Due to the 645 nature of NHDP, the local router may identify 646 multiple virtual neighbors that, in fact, are one and 647 the same. Neighbors that are two hops away with more than 648 one advertised address will exhibit this behavior. As the 649 local router's knowledge of its neighbors' topology 650 increases, the local router will be able to associate 651 multiple virtual neighbor indexes into a single virtual 652 neighbor index chosen from the set of aggregated indexes; 653 it MUST update all tables in this MIB module indexed by these 654 indexes, and it MAY reuse the freed indexes following the 655 next agent re-initialization. 657 All objects of type NeighborRouterIndex are assigned by 658 the agent out of a common number space. 660 The NeighborRouterIndex defines a discovered NHDP peer 661 virtual neighbor of the local router. 663 The value for each discovered virtual neighbor index MUST 664 remain constant at least from one re-initialization of 665 the entity's network management agent to the next 666 re-initialization, except if an application is deleted 667 and re-created. 669 The specific value is meaningful only within a given SNMP 670 entity. A NeighborRouterIndex value MUST NOT be reused 671 until the next agent restart." 672 SYNTAX Unsigned32 (1..2147483647) 674 -- 675 -- nhdpObjects 676 -- 678 -- 1) Configuration Objects Group 679 -- 2) State Objects Group 680 -- 3) Performance Objects Group 682 -- 683 -- nhdpConfigurationObjGrp 684 -- 686 -- Contains the NHDP objects that configure specific options 687 -- that determine the overall performance and operation of 688 -- NHDP. 690 nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } 692 nhdpInterfaceTable OBJECT-TYPE 693 SYNTAX SEQUENCE OF NhdpInterfaceEntry 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "The nhdpInterfaceTable describes the 698 configuration of the interfaces of this router 699 that are intended to use MANET control protocols. 700 As such, this table 'sparse augments' the ifTable 701 specifically when NHDP is to be configured to 702 operate over this interface. The interface is 703 identified by the ifIndex from the interfaces 704 group defined in the Interfaces Group MIB module. 706 A conceptual row in this table exists if and only 707 if either a manager has explicitly created the row 708 or there is an interface on the managed device 709 that supports and runs NHDP. 711 The manager can create a row by setting 712 rowStatus to 'createAndGo' or 'createAndWait'. 713 Row objects having associated DEFVAL clauses are 714 automatically defined by the agent with these 715 values during row creation, unless the manager 716 explicitly defines these object values during the 717 row creation. 719 If the corresponding entry with ifIndex value 720 is deleted from the Interface Table, then the entry 721 in this table is automatically deleted, 722 NHDP is disabled on this interface, 723 and all configuration and state information 724 related to this interface is to be removed 725 from memory." 726 REFERENCE 727 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 728 K., and F. Kastenholtz, June 2000" 729 ::= { nhdpConfigurationObjGrp 1 } 731 nhdpInterfaceEntry OBJECT-TYPE 732 SYNTAX NhdpInterfaceEntry 733 MAX-ACCESS not-accessible 734 STATUS current 735 DESCRIPTION 736 "The nhdpInterfaceEntry describes one NHDP 737 local interface configuration as indexed by 738 its ifIndex as defined in the Standard MIB II 739 Interface Table (RFC 2863). 741 The objects in this table are persistent, and when 742 written, the device SHOULD save the change to 743 non-volatile storage. For further information 744 on the storage behavior for these objects, refer 745 to the description for the nhdpIfRowStatus 746 object." 747 INDEX { nhdpIfIndex } 748 ::= { nhdpInterfaceTable 1 } 750 NhdpInterfaceEntry ::= 751 SEQUENCE { 752 nhdpIfIndex 753 InterfaceIndex, 755 nhdpIfName 756 SnmpAdminString, 757 nhdpIfStatus 758 TruthValue, 759 nhdpHelloInterval 760 Unsigned32, 761 nhdpHelloMinInterval 762 Unsigned32, 763 nhdpRefreshInterval 764 Unsigned32, 765 nhdpLHoldTime 766 Unsigned32, 767 nhdpHHoldTime 768 Unsigned32, 769 nhdpHystAcceptQuality 770 Float32TC, 771 nhdpHystRejectQuality 772 Float32TC, 773 nhdpInitialQuality 774 Float32TC, 775 nhdpInitialPending 776 TruthValue, 777 nhdpHpMaxJitter 778 Unsigned32, 779 nhdpHtMaxJitter 780 Unsigned32, 781 nhdpIfRowStatus 782 RowStatus 783 } 785 nhdpIfIndex OBJECT-TYPE 786 SYNTAX InterfaceIndex 787 MAX-ACCESS not-accessible 788 STATUS current 789 DESCRIPTION 790 "This value MUST correspond to an ifIndex referring 791 to a valid entry in the Interfaces Table." 792 REFERENCE 793 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 794 and F. Kastenholtz, June 2000" 795 ::= { nhdpInterfaceEntry 1 } 797 nhdpIfName OBJECT-TYPE 798 SYNTAX SnmpAdminString 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "The textual name of the interface. The value of this 803 object SHOULD be the name of the interface as assigned by 804 the local device. This can be a text-name, such as 'le0' 805 or a simple port number, such as '1', 806 depending on the interface-naming syntax of the device. 808 If there is no local name or this object is otherwise not 809 applicable, then this object contains a zero-length string." 810 ::= { nhdpInterfaceEntry 2 } 812 nhdpIfStatus OBJECT-TYPE 813 SYNTAX TruthValue 814 MAX-ACCESS read-create 815 STATUS current 816 DESCRIPTION 817 "nhdpIfStatus indicates whether this interface is 818 currently running NHDP. A value of 'true(1)' indicates 819 that NHDP is running on this interface. 820 A value of 'false(2)' indicates that NHDP is not 821 currently running on this interface. This corresponds 822 to the I_manet parameter in the Local Interface Set 823 of NHDP." 824 DEFVAL { false } 825 ::= { nhdpInterfaceEntry 3 } 827 -- 828 -- Interface Parameters - Message Intervals 829 -- 831 nhdpHelloInterval OBJECT-TYPE 832 SYNTAX Unsigned32 833 UNITS "milliseconds" 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "nhdpHelloInterval corresponds to 838 HELLO_INTERVAL of NHDP and represents the 839 maximum time between the transmission of two 840 successive HELLO messages on this MANET interface. 842 Guidance for setting this object may be found 843 in Section 5 of the NHDP specification (RFC 6130), 844 which indicates that: 845 o nhdpHelloInterval > 0 846 o nhdpHelloInterval >= nhdpHelloMinInterval" 847 REFERENCE 848 "Section 5 on Protocol Parameters and 849 Constraints of RFC 6130 - Mobile Ad Hoc 850 Network (MANET) Neighborhood Discovery 851 Protocol (NHDP), Clausen, T., Dearlove, 852 C., and J. Dean, April 2011" 853 DEFVAL { 2000 } 854 ::= { nhdpInterfaceEntry 4 } 856 nhdpHelloMinInterval OBJECT-TYPE 857 SYNTAX Unsigned32 858 UNITS "milliseconds" 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "nhdpHelloMinInterval corresponds to 863 HELLO_MIN_INTERVAL of NHDP and represents 864 the minimum interval between transmission 865 of two successive HELLO messages on this 866 MANET interface. 868 Guidance for setting this object may be found 869 in Section 5 of the NHDP specification (RFC 6130), 870 which indicates that: 871 o nhdpHelloMinInterval <= nhdpHelloInterval" 872 REFERENCE 873 "Section 5 on Protocol Parameters and 874 Constraints of RFC 6130 - Mobile Ad Hoc Network 875 (MANET) Neighborhood Discovery Protocol (NHDP), 876 Clausen, T., Dearlove, C., and J. Dean, April 2011" 877 DEFVAL { 500 } 878 ::= { nhdpInterfaceEntry 5 } 880 nhdpRefreshInterval OBJECT-TYPE 881 SYNTAX Unsigned32 882 UNITS "milliseconds" 883 MAX-ACCESS read-create 884 STATUS current 885 DESCRIPTION 886 "nhdpRefreshInterval corresponds to 887 REFRESH_INTERVAL of NHDP and represents the 888 maximum interval between advertisements of 889 each 1-hop neighbor network address and its 890 status. Each advertisement is in a HELLO 891 message on this MANET interface. 893 Guidance for setting this object may be found 894 in Section 5 of the NHDP specification (RFC 6130), 895 which indicates that: 896 o nhdpRefreshInterval >= nhdpHelloInterval" 898 REFERENCE 899 "Section 5 on Protocol Parameters and 900 Constraints of RFC 6130 - Mobile Ad Hoc Network 901 (MANET) Neighborhood Discovery Protocol (NHDP), 902 Clausen, T., Dearlove, C., and J. Dean, April 2011" 903 DEFVAL { 2000 } 904 ::= { nhdpInterfaceEntry 6 } 906 -- 907 -- Interface Parameters - Information Validity times 908 -- 910 nhdpLHoldTime OBJECT-TYPE 911 SYNTAX Unsigned32 912 UNITS "milliseconds" 913 MAX-ACCESS read-create 914 STATUS current 915 DESCRIPTION 916 "nhdpLHoldTime corresponds to 917 L_HOLD_TIME of NHDP and represents the period 918 of advertisement, on this MANET interface, of 919 former 1-hop neighbor network addresses as lost 920 in HELLO messages, allowing recipients of these 921 HELLO messages to accelerate removal of this 922 information from their Link Sets. 924 Guidance for setting this object may be found 925 in Section 5 of the NHDP specification (RFC 6130), 926 which indicates that it should be assigned a 927 value significantly greater than the refresh 928 interval held by nhdpRefreshInterval." 929 REFERENCE 930 "Section 5 on Protocol Parameters and 931 Constraints of RFC 6130 - Mobile Ad Hoc Network 932 (MANET) Neighborhood Discovery Protocol (NHDP), 933 Clausen, T., Dearlove, C., and J. Dean, April 2011" 934 DEFVAL { 6000 } 935 ::= { nhdpInterfaceEntry 7 } 937 nhdpHHoldTime OBJECT-TYPE 938 SYNTAX Unsigned32 939 UNITS "milliseconds" 940 MAX-ACCESS read-create 941 STATUS current 942 DESCRIPTION 943 "nhdpHHoldTime corresponds to 944 H_HOLD_TIME of NHDP and is used as the value 945 in the VALIDITY_TIME Message TLV included in all 946 HELLO messages on this MANET interface. It is then 947 used by each router receiving such a HELLO message 948 to indicate the validity of the information taken 949 from that HELLO message and recorded in the receiving 950 router's Information Bases. 952 Guidance for setting this object may be found 953 in Section 5 of the NHDP specification (RFC 6130), 954 which indicates that it should be assigned a 955 value significantly greater than the refresh interval 956 held by nhdpRefreshInterval and must be representable 957 as described in RFC 5497." 958 REFERENCE 959 "Section 5 on Protocol Parameters and 960 Constraints of RFC 6130 - Mobile Ad Hoc Network 961 (MANET) Neighborhood Discovery Protocol (NHDP), 962 Clausen, T., Dearlove, C., and J. Dean, April 2011" 963 DEFVAL { 6000 } 964 ::= { nhdpInterfaceEntry 8 } 966 -- 967 -- Interface Parameters - Link Quality 968 -- 970 nhdpHystAcceptQuality OBJECT-TYPE 971 SYNTAX Float32TC 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "nhdpHystAcceptQuality corresponds to 976 HYST_ACCEPT of NHDP and represents the link 977 quality threshold at or above which a link becomes 978 usable, if it was not already so. 980 Guidance for setting this object may be found 981 in Section 5 of the NHDP specification (RFC 6130), 982 which indicates that: 983 o 0 <= nhdpHystRejectQuality 984 <= nhdpHystAcceptQuality <= 1.0 986 The default value for this object is 1.0. According to 987 RFC 6340: 988 Since these textual conventions are defined in terms 989 of the OCTET STRING type, the SMI's mechanisms for 990 formally setting range constraints are not available. 991 MIB designers using these textual conventions will need 992 to use DESCRIPTION clauses to spell out any applicable 993 range constraints beyond those implied by the underlying 994 IEEE types. 995 Therefore, this object does not have a DEFVAL clause." 996 REFERENCE 997 "Section 5 on Protocol Parameters and 998 Constraints of RFC 6130 - Mobile Ad Hoc Network 999 (MANET) Neighborhood Discovery Protocol (NHDP), 1000 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1001 -- DEFVAL { 1.0 } see DESCRIPTION 1002 ::= { nhdpInterfaceEntry 9 } 1004 nhdpHystRejectQuality OBJECT-TYPE 1005 SYNTAX Float32TC 1006 MAX-ACCESS read-create 1007 STATUS current 1008 DESCRIPTION 1009 "nhdpHystRejectQuality corresponds to 1010 HYST_REJECT of NHDP and represents the 1011 link quality threshold below which a 1012 link becomes unusable, if it was not 1013 already so. 1015 Guidance for setting this object may be found 1016 in Section 5 of the NHDP specification (RFC 6130), 1017 which indicates that: 1018 o 0 <= nhdpHystRejectQuality 1019 <= nhdpHystAcceptQuality <= 1.0 1021 The default value for this object is 0.0. According to 1022 RFC 6340: 1023 Since these textual conventions are defined in terms 1024 of the OCTET STRING type, the SMI's mechanisms for 1025 formally setting range constraints are not available. 1026 MIB designers using these textual conventions will need 1027 to use DESCRIPTION clauses to spell out any applicable 1028 range constraints beyond those implied by the underlying 1029 IEEE types. 1030 Therefore, this object does not have a DEFVAL clause." 1031 REFERENCE 1032 "Section 5 on Protocol Parameters and 1033 Constraints of RFC 6130 - Mobile Ad Hoc Network 1034 (MANET) Neighborhood Discovery Protocol (NHDP), 1035 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1036 -- DEFVAL { 0.0 } see DESCRIPTION 1037 ::= { nhdpInterfaceEntry 10 } 1039 nhdpInitialQuality OBJECT-TYPE 1040 SYNTAX Float32TC 1041 MAX-ACCESS read-create 1042 STATUS current 1043 DESCRIPTION 1044 "nhdpInitialQuality corresponds to 1045 INITIAL_QUALITY of NHDP and represents the 1046 initial quality of a newly identified link. 1048 Guidance for setting this object may be found 1049 in Section 5 of the NHDP specification (RFC 6130), 1050 which indicates that: 1051 o 0 <= nhdpInitialQuality <= 1.0 1053 The default value for this object is 1.0. According to 1054 RFC 6340: 1055 Since these textual conventions are defined in terms 1056 of the OCTET STRING type, the SMI's mechanisms for 1057 formally setting range constraints are not available. 1058 MIB designers using these textual conventions will need 1059 to use DESCRIPTION clauses to spell out any applicable 1060 range constraints beyond those implied by the underlying 1061 IEEE types. 1062 Therefore, this object does not have a DEFVAL clause." 1063 REFERENCE 1064 "Section 5 on Protocol Parameters and 1065 Constraints of RFC 6130 - Mobile Ad Hoc Network 1066 (MANET) Neighborhood Discovery Protocol (NHDP), 1067 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1068 -- DEFVAL { 1.0 } see DESCRIPTION 1069 ::= { nhdpInterfaceEntry 11 } 1071 nhdpInitialPending OBJECT-TYPE 1072 SYNTAX TruthValue 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "nhdpInitialPending corresponds to 1077 INITIAL_PENDING of NHDP. If the value of this object 1078 is 'true(1)', then a newly identified link is considered 1079 pending and is not usable until the link quality 1080 has reached or exceeded the nhdpHystAcceptQuality 1081 threshold. 1083 Guidance for setting this object may be found 1084 in Section 5 of the NHDP specification (RFC 6130), 1085 which indicates that: 1086 o If nhdpInitialQuality >= nhdpHystAcceptQuality, 1087 then nhdpInitialPending := false(2). 1088 o If nhdpInitialQuality < nhdpHystRejectQuality, 1089 then nhdpInitialPending := true(1)." 1091 REFERENCE 1092 "Section 5 on Protocol Parameters and 1093 Constraints of RFC 6130 - Mobile Ad Hoc Network 1094 (MANET) Neighborhood Discovery Protocol (NHDP), 1095 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1096 DEFVAL { false } 1097 ::= { nhdpInterfaceEntry 12 } 1099 -- 1100 -- Interface Parameters - Jitter 1101 -- 1102 nhdpHpMaxJitter OBJECT-TYPE 1103 SYNTAX Unsigned32 1104 UNITS "milliseconds" 1105 MAX-ACCESS read-create 1106 STATUS current 1107 DESCRIPTION 1108 "nhdpHpMaxJitter corresponds to 1109 HP_MAXJITTER of NHDP and represents the 1110 value of MAXJITTER used in RFC 5148 for 1111 periodically generated HELLO messages on 1112 this MANET interface. 1114 Guidance for setting this object may be found 1115 in Section 5 of RFC 5148, which indicates that: 1116 o nhdpHpMaxJitter <= nhdpHelloInterval / 2 1117 o nhdpHpMaxJitter should not be greater 1118 than nhdpHelloInterval / 4 1119 o If nhdpMinHelloInterval > 0, then 1120 nhdpHpMaxJitter <= nhdpHelloMinInterval; and 1121 nhdpHpMaxJitter should not be greater than 1122 nhdpHelloMinInterval / 2" 1123 REFERENCE 1124 "Section 5 of RFC 5148 - Jitter Considerations in 1125 Mobile Ad Hoc Networks (MANETs), 1126 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1127 DEFVAL { 500 } 1128 ::= { nhdpInterfaceEntry 13 } 1130 nhdpHtMaxJitter OBJECT-TYPE 1131 SYNTAX Unsigned32 1132 UNITS "milliseconds" 1133 MAX-ACCESS read-create 1134 STATUS current 1135 DESCRIPTION 1136 "nhdpHtMaxJitter corresponds to 1137 HT_MAXJITTER of NHDP and represents the 1138 value of MAXJITTER used in RFC 5148 for 1139 externally triggered HELLO messages on this 1140 MANET interface. 1142 Guidance for setting this object may be found 1143 in Section 5 of RFC 5148, which indicates that: 1144 o nhdpHtMaxJitter <= nhdpHelloInterval / 2 1145 o nhdpHtMaxJitter should not be greater 1146 than nhdpHelloInterval / 4 1147 o If nhdpMinHelloInterval > 0, then 1148 nhdpHtMaxJitter <= nhdpHelloMinInterval; and 1149 nhdpHtMaxJitter should not be greater than 1150 nhdpHelloMinInterval / 2" 1151 REFERENCE 1152 "Section 5 of RFC 5148 - Jitter Considerations in 1153 Mobile Ad Hoc Networks (MANETs), 1154 Clausen, T., Dearlove, C., and B. Adamson, February 2008" 1155 DEFVAL { 500 } 1156 ::= { nhdpInterfaceEntry 14 } 1158 nhdpIfRowStatus OBJECT-TYPE 1159 SYNTAX RowStatus 1160 MAX-ACCESS read-create 1161 STATUS current 1162 DESCRIPTION 1163 "This object permits management of the table 1164 by facilitating actions such as row creation, 1165 construction, and destruction. The value of 1166 this object has no effect on whether other 1167 objects in this conceptual row can be 1168 modified. 1170 An entry may not exist in the 'active(1)' state unless all 1171 objects in the entry have a defined appropriate value. For 1172 objects with DEFVAL clauses, the management station 1173 does not need to specify the value of this object in order 1174 for the row to transit to the 'active(1)' state; the default 1175 value for this object is used. For objects that do not 1176 have DEFVAL clauses, then the network manager MUST 1177 specify the value of this object prior to this row 1178 transitioning to the 'active(1)' state. 1180 When this object transitions to 'active(1)', all objects 1181 in this row SHOULD be written to non-volatile (stable) 1182 storage. Read-create objects in this row MAY be modified. 1183 When an object in a row with nhdpIfRowStatus of 'active(1)' 1184 is changed, then the updated value MUST be reflected in NHDP, 1185 and this new object value MUST be written to non-volatile 1186 storage. 1188 If the value of this object is not equal to 'active(1)', 1189 all associated entries in the nhdpLibLocalIfSetTable, 1190 nhdpInterfaceStateTable, nhdpIibLinkSetTable, and 1191 nhdpInterfacePerfTable MUST be deleted." 1192 REFERENCE 1193 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1194 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1195 C., and J. Dean, April 2011" 1196 DEFVAL { active } 1197 ::= { nhdpInterfaceEntry 15 } 1199 -- 1200 -- Router Parameters - Information Validity Time 1201 -- 1202 nhdpNHoldTime OBJECT-TYPE 1203 SYNTAX Unsigned32 1204 UNITS "milliseconds" 1205 MAX-ACCESS read-write 1206 STATUS current 1207 DESCRIPTION 1208 "nhdpNHoldTime corresponds to 1209 N_HOLD_TIME of NHDP and is used as the period 1210 during which former 1-hop neighbor network 1211 addresses are advertised as lost in HELLO 1212 messages, allowing recipients of these HELLO 1213 messages to accelerate removal of this information 1214 from their 2-Hop Sets. 1216 This object is persistent, and when written, 1217 the entity SHOULD save the change to 1218 non-volatile storage." 1219 REFERENCE 1220 "Section 5 on Protocol Parameters and 1221 Constraints of RFC 6130 - Mobile Ad Hoc Network 1222 (MANET) Neighborhood Discovery Protocol (NHDP), 1223 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1224 DEFVAL { 6000 } 1225 ::= { nhdpConfigurationObjGrp 2 } 1227 nhdpIHoldTime OBJECT-TYPE 1228 SYNTAX Unsigned32 1229 UNITS "milliseconds" 1230 MAX-ACCESS read-write 1231 STATUS current 1232 DESCRIPTION 1233 "nhdpIHoldTime corresponds to 1234 I_HOLD_TIME of NHDP and represents the period 1235 for which a recently used local interface network 1236 address is recorded. 1238 This object is persistent, and when written, 1239 the entity SHOULD save the change to 1240 non-volatile storage." 1241 REFERENCE 1242 "Section 5 on Protocol Parameters and 1243 Constraints of RFC 6130 - Mobile Ad Hoc Network 1244 (MANET) Neighborhood Discovery Protocol (NHDP), 1245 Clausen, T., Dearlove, C., and J. Dean, April 2011" 1246 DEFVAL { 6000 } 1247 ::= { nhdpConfigurationObjGrp 3 } 1249 -- A router's Local Information Base (LIB) 1251 -- 1252 -- Local Interface Set Table 1253 -- 1255 nhdpLibLocalIfSetTable OBJECT-TYPE 1256 SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 "A router's Local Interface Set records all 1261 network addresses that are defined as local 1262 MANET interface network addresses. 1263 As such, this table 'sparse augments' the 1264 nhdpInterfaceTable when network addresses are 1265 being defined for the interfaces existing within 1266 the nhdpInterfaceTable. The local interface 1267 is defined by the nhdpIfIndex. 1269 The Local Interface Set consists of Local Interface 1270 Address Tuples per MANET interface and their prefix 1271 lengths (in order to determine the network addresses 1272 related to the interface). 1274 A conceptual row in this table exists if and only 1275 if a manager has explicitly created the row. The 1276 manager can create a row by setting rowStatus 1277 to 'createAndGo' or 'createAndWait'. 1279 Further guidance on the addition or removal of 1280 local addresses and network addresses is found 1281 in Section 9 of RFC 6130." 1282 REFERENCE 1283 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1284 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1285 C., and J. Dean, April 2011" 1286 ::= { nhdpConfigurationObjGrp 4 } 1288 nhdpLibLocalIfSetEntry OBJECT-TYPE 1289 SYNTAX NhdpLibLocalIfSetEntry 1290 MAX-ACCESS not-accessible 1291 STATUS current 1292 DESCRIPTION 1293 "A router's Local Interface Set consists 1294 of Configured Interface Address Tuples for each network 1295 interface. 1297 The objects in this table are persistent, and when 1298 written, the device SHOULD save the change to 1299 non-volatile storage. For further information 1300 on the storage behavior for these objects, refer 1301 to the description for the nhdpLibLocalIfSetRowStatus 1302 object." 1303 REFERENCE 1304 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1305 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1306 C., and J. Dean, April 2011" 1307 INDEX { nhdpLibLocalIfSetIndex } 1308 ::= { nhdpLibLocalIfSetTable 1 } 1310 NhdpLibLocalIfSetEntry ::= 1311 SEQUENCE { 1312 nhdpLibLocalIfSetIndex 1313 Integer32, 1314 nhdpLibLocalIfSetIfIndex 1315 InterfaceIndex, 1316 nhdpLibLocalIfSetIpAddrType 1317 InetAddressType, 1318 nhdpLibLocalIfSetIpAddr 1319 InetAddress, 1320 nhdpLibLocalIfSetIpAddrPrefixLen 1321 InetAddressPrefixLength, 1322 nhdpLibLocalIfSetRowStatus 1323 RowStatus 1324 } 1326 nhdpLibLocalIfSetIndex OBJECT-TYPE 1327 SYNTAX Integer32 (0..65535) 1328 MAX-ACCESS not-accessible 1329 STATUS current 1330 DESCRIPTION 1331 "The index for this table. Necessary 1332 because multiple addresses may be associated 1333 with a given nhdpIfIndex." 1334 REFERENCE 1335 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1336 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1337 C., and J. Dean, April 2011" 1338 ::= { nhdpLibLocalIfSetEntry 1 } 1340 nhdpLibLocalIfSetIfIndex OBJECT-TYPE 1341 SYNTAX InterfaceIndex 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "Specifies the local nhdpIfIndex for which this 1346 IP address was added." 1347 REFERENCE 1348 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1349 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1350 C., and J. Dean, April 2011" 1351 ::= { nhdpLibLocalIfSetEntry 2 } 1353 nhdpLibLocalIfSetIpAddrType OBJECT-TYPE 1354 SYNTAX InetAddressType 1355 MAX-ACCESS read-create 1356 STATUS current 1357 DESCRIPTION 1358 "The type of the nhdpLibLocalIfSetIpAddr 1359 in the InetAddress MIB (RFC 4001). 1361 Only the values 'ipv4(1)' and 1362 'ipv6(2)' are supported." 1363 REFERENCE 1364 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1365 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1366 C., and J. Dean, April 2011" 1367 ::= { nhdpLibLocalIfSetEntry 3 } 1369 nhdpLibLocalIfSetIpAddr OBJECT-TYPE 1370 SYNTAX InetAddress (SIZE(4|16)) 1371 MAX-ACCESS read-create 1372 STATUS current 1373 DESCRIPTION 1374 "nhdpLibLocalIfSetIpAddr is an 1375 address of an interface of 1376 this router. 1378 This object is interpreted according to 1379 the setting of nhdpLibLocalIfSetIpAddrType." 1380 REFERENCE 1381 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1382 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1383 C., and J. Dean, April 2011" 1384 ::= { nhdpLibLocalIfSetEntry 4 } 1386 nhdpLibLocalIfSetIpAddrPrefixLen OBJECT-TYPE 1387 SYNTAX InetAddressPrefixLength 1388 MAX-ACCESS read-create 1389 STATUS current 1390 DESCRIPTION 1391 "Indicates the number of leading one bits that 1392 form the mask. The mask is logically ANDed 1393 to the nhdpLibLocalIfSetIpAddr to determine 1394 the address prefix. A row match is true 1395 if the address used as an index falls within 1396 the network address range defined by the 1397 address prefix." 1398 REFERENCE 1399 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1400 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1401 C., and J. Dean, April 2011" 1402 ::= { nhdpLibLocalIfSetEntry 5 } 1404 nhdpLibLocalIfSetRowStatus OBJECT-TYPE 1405 SYNTAX RowStatus 1406 MAX-ACCESS read-create 1407 STATUS current 1408 DESCRIPTION 1409 "This object permits management of the table 1410 by facilitating actions such as row creation, 1411 construction, and destruction. The value of 1412 this object has no effect on whether other 1413 objects in this conceptual row can be 1414 modified. 1416 An entry may not exist in the 'active(1)' state unless all 1417 read-create objects in the entry have a defined 1418 appropriate value. As no objects in this table have 1419 DEFVAL clauses, the management station MUST specify 1420 the values of all read-create objects prior to this row 1421 transitioning to the 'active(1)' state. 1423 When this object transitions to 'active(1)', all objects 1424 in this row SHOULD be written to non-volatile (stable) 1425 storage. Read-create objects in this row MAY be modified. 1426 When an object in a row with nhdpIfRowStatus of 'active(1)' 1427 is changed, then the updated value MUST be reflected in NHDP, 1428 and this new object value MUST be written to non-volatile 1429 storage." 1430 REFERENCE 1431 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1432 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1433 C., and J. Dean, April 2011" 1434 DEFVAL { notReady } 1435 ::= { nhdpLibLocalIfSetEntry 6 } 1437 -- 1438 -- Removed Interface Addr Set Table 1439 -- 1441 nhdpLibRemovedIfAddrSetTable OBJECT-TYPE 1442 SYNTAX SEQUENCE OF NhdpLibRemovedIfAddrSetEntry 1443 MAX-ACCESS not-accessible 1444 STATUS current 1445 DESCRIPTION 1446 "A router's Removed Interface Address Set records 1447 network addresses that were recently used as local 1448 interface network addresses. If a router's interface 1449 network addresses are immutable, then the Removed 1450 Interface Address Set is always empty and may be omitted. 1451 It consists of Removed Interface Address Tuples, one 1452 per network address." 1453 REFERENCE 1454 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1455 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1456 C., and J. Dean, April 2011" 1457 ::= { nhdpConfigurationObjGrp 5 } 1459 nhdpLibRemovedIfAddrSetEntry OBJECT-TYPE 1460 SYNTAX NhdpLibRemovedIfAddrSetEntry 1461 MAX-ACCESS not-accessible 1462 STATUS current 1463 DESCRIPTION 1464 "A router's Removed Interface Address Set consists 1465 of Removed Interface Address Tuples, one per network 1466 address: 1468 (IR_local_iface_addr, IR_time) 1469 The association between these addresses and the 1470 router's Interface is found in the Standard MIB II's 1471 IP address table (RFC 1213)." 1472 REFERENCE 1473 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1474 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1475 C., and J. Dean, April 2011" 1476 INDEX { nhdpLibRemovedIfAddrSetIndex } 1477 ::= { nhdpLibRemovedIfAddrSetTable 1 } 1479 NhdpLibRemovedIfAddrSetEntry ::= 1480 SEQUENCE { 1481 nhdpLibRemovedIfAddrSetIndex 1482 Integer32, 1483 nhdpLibRemovedIfAddrSetIpAddrType 1484 InetAddressType, 1485 nhdpLibRemovedIfAddrSetIpAddr 1486 InetAddress, 1487 nhdpLibRemovedIfAddrSetIpAddrPrefixLen 1488 InetAddressPrefixLength, 1489 nhdpLibRemovedIfAddrSetIfIndex 1490 InterfaceIndex, 1491 nhdpLibRemovedIfAddrSetIRTime 1492 TimeStamp 1493 } 1495 nhdpLibRemovedIfAddrSetIndex OBJECT-TYPE 1496 SYNTAX Integer32 (0..65535) 1497 MAX-ACCESS not-accessible 1498 STATUS current 1499 DESCRIPTION 1500 "The index for this table. Necessary 1501 because multiple addresses may be associated 1502 with a given nhdpIfIndex." 1503 REFERENCE 1504 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1505 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1506 C., and J. Dean, April 2011" 1507 ::= { nhdpLibRemovedIfAddrSetEntry 1 } 1509 nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE 1510 SYNTAX InetAddressType 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "The type of the nhdpLibRemovedIfAddrSetIpAddr 1515 in the InetAddress MIB (RFC 4001). 1517 Only the values 'ipv4(1)' and 1518 'ipv6(2)' are supported." 1519 REFERENCE 1520 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1521 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1522 C., and J. Dean, April 2011" 1523 ::= { nhdpLibRemovedIfAddrSetEntry 2 } 1525 nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE 1526 SYNTAX InetAddress (SIZE(4|16)) 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "nhdpLibRemovedIfAddrSetIpAddr is a 1531 recently used address of an interface of 1532 this router." 1533 REFERENCE 1534 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1535 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1536 C., and J. Dean, April 2011" 1537 ::= { nhdpLibRemovedIfAddrSetEntry 3 } 1539 nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE 1540 SYNTAX InetAddressPrefixLength 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "Indicates the number of leading one bits that 1545 form the mask. The mask is logically ANDed 1546 to the nhdpLibRemovedIfAddrSetIpAddr to determine 1547 the address prefix. A row match is true 1548 if the address used as an index falls within 1549 the network address range defined by the 1550 address prefix." 1551 REFERENCE 1552 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1553 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1554 C., and J. Dean, April 2011" 1555 ::= { nhdpLibRemovedIfAddrSetEntry 4 } 1557 nhdpLibRemovedIfAddrSetIfIndex OBJECT-TYPE 1558 SYNTAX InterfaceIndex 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "Specifies the local IfIndex from which this 1563 IP address was recently removed." 1565 REFERENCE 1566 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1567 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1568 C., and J. Dean, April 2011" 1569 ::= { nhdpLibRemovedIfAddrSetEntry 5 } 1571 nhdpLibRemovedIfAddrSetIRTime OBJECT-TYPE 1572 SYNTAX TimeStamp 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "nhdpLibRemovedIfAddrSetIRTime specifies the value 1577 of sysUptime when this entry should expire and be 1578 removed from the nhdpLibRemovedIfAddrSetTable." 1579 REFERENCE 1580 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1581 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1582 C., and J. Dean, April 2011" 1583 ::= { nhdpLibRemovedIfAddrSetEntry 6 } 1585 -- 1586 -- nhdpStateObjGrp 1587 -- 1589 -- Contains information describing the current state of the NHDP 1590 -- process on this router. 1592 nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 } 1594 nhdpUpTime OBJECT-TYPE 1595 SYNTAX TimeStamp 1596 MAX-ACCESS read-only 1597 STATUS current 1598 DESCRIPTION 1599 "The value of sysUpTime at the time the current NHDP 1600 process was initialized." 1601 ::= { nhdpStateObjGrp 1 } 1603 nhdpInterfaceStateTable OBJECT-TYPE 1604 SYNTAX SEQUENCE OF NhdpInterfaceStateEntry 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1608 "nhdpInterfaceStateTable lists state information 1609 related to specific interfaces of this router. 1611 The value of nhdpIfIndex is an ifIndex from the 1612 interfaces group defined in the Interfaces Group 1613 MIB. 1615 The objects in this table are persistent, and when 1616 written, the entity SHOULD save the change to 1617 non-volatile storage." 1618 REFERENCE 1619 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1620 K., and F. Kastenholtz, June 2000." 1621 ::= { nhdpStateObjGrp 2 } 1623 nhdpInterfaceStateEntry OBJECT-TYPE 1624 SYNTAX NhdpInterfaceStateEntry 1625 MAX-ACCESS not-accessible 1626 STATUS current 1627 DESCRIPTION 1628 "nhdpInterfaceStateEntry describes one NHDP 1629 local interface state as indexed by 1630 its nhdpIfIndex." 1631 INDEX { nhdpIfIndex } 1632 ::= { nhdpInterfaceStateTable 1 } 1634 NhdpInterfaceStateEntry ::= 1635 SEQUENCE { 1636 nhdpIfStateUpTime 1637 TimeStamp 1638 } 1640 nhdpIfStateUpTime OBJECT-TYPE 1641 SYNTAX TimeStamp 1642 MAX-ACCESS read-only 1643 STATUS current 1644 DESCRIPTION 1645 "The value of the sysUpTime when 1646 NHDP was last initialized on this 1647 MANET interface." 1648 ::= { nhdpInterfaceStateEntry 1 } 1650 -- 1651 -- This table allows for the mapping between discovered 1652 -- remote interfaces and routers and their addresses. 1653 -- 1655 nhdpDiscIfSetTable OBJECT-TYPE 1656 SYNTAX SEQUENCE OF NhdpDiscIfSetEntry 1657 MAX-ACCESS not-accessible 1658 STATUS current 1659 DESCRIPTION 1660 "A router's set of discovered interfaces on 1661 neighboring routers." 1662 REFERENCE 1663 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1664 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1665 C., and J. Dean, April 2011" 1666 ::= { nhdpStateObjGrp 3 } 1668 nhdpDiscIfSetEntry OBJECT-TYPE 1669 SYNTAX NhdpDiscIfSetEntry 1670 MAX-ACCESS not-accessible 1671 STATUS current 1672 DESCRIPTION 1673 "The entries include the nhdpDiscRouterIndex of 1674 the discovered router, the nhdpDiscIfIndex 1675 of the discovered interface, and the 1676 current set of addresses associated 1677 with this neighbor interface. The 1678 nhdpDiscIfIndex uniquely identifies 1679 the remote interface address sets 1680 through this table. It does not need 1681 to be unique across the MANET but MUST 1682 be locally unique within this router." 1683 REFERENCE 1684 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1685 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1686 C., and J. Dean, April 2011" 1687 INDEX { nhdpDiscIfSetIndex } 1688 ::= { nhdpDiscIfSetTable 1 } 1690 NhdpDiscIfSetEntry ::= 1691 SEQUENCE { 1692 nhdpDiscIfSetIndex 1693 Integer32, 1694 nhdpDiscIfIndex 1695 NeighborIfIndex, 1696 nhdpDiscRouterIndex 1697 NeighborRouterIndex, 1698 nhdpDiscIfSetIpAddrType 1699 InetAddressType, 1700 nhdpDiscIfSetIpAddr 1701 InetAddress, 1702 nhdpDiscIfSetIpAddrPrefixLen 1703 InetAddressPrefixLength 1704 } 1706 nhdpDiscIfSetIndex OBJECT-TYPE 1707 SYNTAX Integer32 (0..65535) 1708 MAX-ACCESS not-accessible 1709 STATUS current 1710 DESCRIPTION 1711 "The index for this table. Necessary 1712 because multiple addresses may be associated 1713 with a given nhdpDiscIfIndex." 1714 REFERENCE 1715 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1716 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1717 C., and J. Dean, April 2011" 1718 ::= { nhdpDiscIfSetEntry 1 } 1720 nhdpDiscIfIndex OBJECT-TYPE 1721 SYNTAX NeighborIfIndex 1722 MAX-ACCESS read-only 1723 STATUS current 1724 DESCRIPTION 1725 "The NHDP interface index (locally created) 1726 of a neighbor's interface. Used for cross- 1727 indexing into other NHDP tables and other 1728 MIB modules." 1729 REFERENCE 1730 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1731 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1732 C., and J. Dean, April 2011" 1733 ::= { nhdpDiscIfSetEntry 2 } 1735 nhdpDiscRouterIndex OBJECT-TYPE 1736 SYNTAX NeighborRouterIndex 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The NHDP neighbor index (locally created) 1741 of a neighboring router. Used for cross- 1742 indexing into other NHDP tables and other 1743 MIB modules." 1744 REFERENCE 1745 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1746 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1747 C., and J. Dean, April 2011" 1748 ::= { nhdpDiscIfSetEntry 3 } 1750 nhdpDiscIfSetIpAddrType OBJECT-TYPE 1751 SYNTAX InetAddressType 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "The type of the nhdpDiscIfSetIpAddr 1756 in the InetAddress MIB (RFC 4001). 1758 Only the values 'ipv4(1)' and 1759 'ipv6(2)' are supported." 1760 REFERENCE 1761 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1762 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1763 C., and J. Dean, April 2011" 1764 ::= { nhdpDiscIfSetEntry 4 } 1766 nhdpDiscIfSetIpAddr OBJECT-TYPE 1767 SYNTAX InetAddress (SIZE(4|16)) 1768 MAX-ACCESS read-only 1769 STATUS current 1770 DESCRIPTION 1771 "The nhdpDiscIfSetIpAddr is a 1772 recently used address of a neighbor 1773 of this router." 1774 REFERENCE 1775 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1776 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1777 C., and J. Dean, April 2011" 1778 ::= { nhdpDiscIfSetEntry 5 } 1780 nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE 1781 SYNTAX InetAddressPrefixLength 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "Indicates the number of leading one bits that 1786 form the mask. The mask is logically ANDed 1787 to the nhdpDiscIfSetIpAddr to determine 1788 the address prefix. A row match is true 1789 if the address used as an index falls within 1790 the network address range defined by the 1791 address prefix." 1792 REFERENCE 1793 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1794 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1795 C., and J. Dean, April 2011" 1796 ::= { nhdpDiscIfSetEntry 6 } 1798 -- Interface Information Base (IIB) 1800 -- 1801 -- Link Set 1802 -- 1804 nhdpIibLinkSetTable OBJECT-TYPE 1805 SYNTAX SEQUENCE OF NhdpIibLinkSetEntry 1806 MAX-ACCESS not-accessible 1807 STATUS current 1808 DESCRIPTION 1809 "A Link Set of an interface records all links 1810 from other routers that are, or recently 1811 were, 1-hop neighbors." 1812 REFERENCE 1813 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1814 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1815 C., and J. Dean, April 2011" 1816 ::= { nhdpStateObjGrp 4 } 1818 nhdpIibLinkSetEntry OBJECT-TYPE 1819 SYNTAX NhdpIibLinkSetEntry 1820 MAX-ACCESS not-accessible 1821 STATUS current 1822 DESCRIPTION 1823 "A Link Set consists of Link Tuples, each 1824 representing a single link indexed by the 1825 local and remote interface pair: 1827 (L_neighbor_iface_addr_list, L_HEARD_time, 1828 L_SYM_time, L_quality, L_pending, 1829 L_lost, L_time). 1831 The local interface is indexed via the 1832 nhdpIfIndex. The 1-hop interface is 1833 indexed via the nhdpDiscIfIndex. There 1834 SHOULD be an entry in this table for each 1835 local interface and associated 1-hop 1836 neighbor reachable on this local interface. 1838 Note that L_quality is not included in the 1839 entries below, because updates may be 1840 required too frequently." 1841 REFERENCE 1842 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1843 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1844 C., and J. Dean, April 2011" 1845 INDEX { nhdpIfIndex, 1846 nhdpDiscIfIndex } 1847 ::= { nhdpIibLinkSetTable 1 } 1848 NhdpIibLinkSetEntry ::= 1849 SEQUENCE { 1850 nhdpIibLinkSetLHeardTime 1851 TimeStamp, 1852 nhdpIibLinkSetLSymTime 1853 TimeStamp, 1854 nhdpIibLinkSetLPending 1855 TruthValue, 1856 nhdpIibLinkSetLLost 1857 TruthValue, 1858 nhdpIibLinkSetLTime 1859 TimeStamp 1860 } 1862 nhdpIibLinkSetLHeardTime OBJECT-TYPE 1863 SYNTAX TimeStamp 1864 MAX-ACCESS read-only 1865 STATUS current 1866 DESCRIPTION 1867 "nhdpIibLinkSetLHeardTime corresponds 1868 to L_HEARD_time of NHDP and represents the 1869 time up to which the MANET interface of the 1870 1-hop neighbor would be considered heard if 1871 not considering link quality." 1872 REFERENCE 1873 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1874 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1875 C., and J. Dean, April 2011" 1876 ::= { nhdpIibLinkSetEntry 1 } 1878 nhdpIibLinkSetLSymTime OBJECT-TYPE 1879 SYNTAX TimeStamp 1880 MAX-ACCESS read-only 1881 STATUS current 1882 DESCRIPTION 1883 "nhdpIibLinkSetLSymTime corresponds 1884 to L_SYM_time of NHDP and represents the time 1885 up to which the link to the 1-hop neighbor 1886 would be considered symmetric if not considering 1887 link quality." 1888 REFERENCE 1889 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1890 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1891 C., and J. Dean, April 2011" 1892 ::= { nhdpIibLinkSetEntry 2 } 1894 nhdpIibLinkSetLPending OBJECT-TYPE 1895 SYNTAX TruthValue 1896 MAX-ACCESS read-only 1897 STATUS current 1898 DESCRIPTION 1899 "nhdpIibLinkSetLPending corresponds 1900 to L_pending of NHDP and is a boolean flag, 1901 describing if a link is considered pending 1902 (i.e., a candidate, but not yet established, 1903 link)." 1904 REFERENCE 1905 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1906 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1907 C., and J. Dean, April 2011" 1908 ::= { nhdpIibLinkSetEntry 3 } 1910 nhdpIibLinkSetLLost OBJECT-TYPE 1911 SYNTAX TruthValue 1912 MAX-ACCESS read-only 1913 STATUS current 1914 DESCRIPTION 1915 "nhdpIibLinkSetLLost corresponds 1916 to L_lost of NHDP and is a boolean flag, 1917 describing if a link is considered lost due 1918 to low link quality." 1919 REFERENCE 1920 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1921 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1922 C., and J. Dean, April 2011" 1923 ::= { nhdpIibLinkSetEntry 4 } 1925 nhdpIibLinkSetLTime OBJECT-TYPE 1926 SYNTAX TimeStamp 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "nhdpIibLinkSetLTime specifies the value 1931 of sysUptime when this entry should expire and be 1932 removed from the nhdpIibLinkSetTable." 1933 REFERENCE 1934 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1935 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1936 C., and J. Dean, April 2011" 1937 ::= { nhdpIibLinkSetEntry 5 } 1939 -- 1940 -- 2-Hop Set 1941 -- 1942 nhdpIib2HopSetTable OBJECT-TYPE 1943 SYNTAX SEQUENCE OF NhdpIib2HopSetEntry 1944 MAX-ACCESS not-accessible 1945 STATUS current 1946 DESCRIPTION 1947 "A 2-Hop Set of an interface records network 1948 addresses of symmetric 2-hop neighbors and 1949 the symmetric links to symmetric 1-hop neighbors 1950 through which these symmetric 2-hop neighbors 1951 can be reached. It consists of 2-Hop Tuples." 1952 REFERENCE 1953 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1954 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1955 C., and J. Dean, April 2011" 1956 ::= { nhdpStateObjGrp 5 } 1958 nhdpIib2HopSetEntry OBJECT-TYPE 1959 SYNTAX NhdpIib2HopSetEntry 1960 MAX-ACCESS not-accessible 1961 STATUS current 1962 DESCRIPTION 1963 "nhdpIib2HopSetTable consists of 2-Hop Tuples, each 1964 representing a single network address of a symmetric 1965 2-hop neighbor and a single MANET interface of a 1966 symmetric 1-hop neighbor. 1968 (N2_neighbor_iface_addr_list, 1969 N2_2hop_addr, N2_lost, N2_time). 1971 The entries include: 1972 - the 2-hop neighbor addresses 1973 ('N2_neighbor_iface_addr_list'), which 1974 act as the table index, 1975 - the associated symmetric 1-hop 1976 neighbor address set ('N2_2hop_addr'), designated 1977 through nhdpDiscIfIndex, 1978 - a flag indicating if the 1-hop neighbor 1979 through which this 2-hop neighbor is reachable 1980 ('N2_lost') is considered lost due to link quality, 1981 or not, 1982 - and the expiration time ('N2_time'). 1984 The nhdpIfIndex in the INDEX is the interface index of 1985 the local interface through which these 2-hop addresses 1986 are accessible. The nhdpDiscIfIndex in the INDEX 1987 represents the 1-hop neighbor interface through which 1988 these 2-hop neighbor addresses are reachable." 1990 REFERENCE 1991 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 1992 Discovery Protocol (NHDP), Clausen, T., Dearlove, 1993 C., and J. Dean, April 2011, 1994 and 1995 draft-ietf-manet-nhdp-optimization-04 - 1996 An Optimization for the MANET Neighborhood Discovery 1997 Protocol (NHDP), Dearlove, C., and T. Clausen, 1998 January 2015" 1999 INDEX { nhdpIfIndex, 2000 nhdpDiscIfIndex, 2001 nhdpIib2HopSetIpAddressType, 2002 nhdpIib2HopSetIpAddress 2003 } 2004 ::= { nhdpIib2HopSetTable 1 } 2006 NhdpIib2HopSetEntry ::= 2007 SEQUENCE { 2008 nhdpIib2HopSetIpAddressType 2009 InetAddressType, 2010 nhdpIib2HopSetIpAddress 2011 InetAddress, 2012 nhdpIib2HopSetIpAddrPrefixLen 2013 InetAddressPrefixLength, 2014 nhdpIib2HopSet1HopIfIndex 2015 NeighborIfIndex, 2016 nhdpIib2HopSetN2Lost 2017 TruthValue, 2018 nhdpIib2HopSetN2Time 2019 TimeStamp 2020 } 2022 nhdpIib2HopSetIpAddressType OBJECT-TYPE 2023 SYNTAX InetAddressType 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "The type of the nhdpIib2HopSetIpAddress 2028 in the InetAddress MIB module (RFC 4001). 2030 Only the values 'ipv4(1)' and 2031 'ipv6(2)' are supported." 2032 REFERENCE 2033 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2034 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2035 C., and J. Dean, April 2011" 2036 ::= { nhdpIib2HopSetEntry 1 } 2038 nhdpIib2HopSetIpAddress OBJECT-TYPE 2039 SYNTAX InetAddress (SIZE(4|16)) 2040 MAX-ACCESS not-accessible 2041 STATUS current 2042 DESCRIPTION 2043 "nhdpIib2HopSetIpAddr corresponds 2044 to N2_2hop_addr of NHDP and is a network 2045 address of a symmetric 2-hop neighbor that 2046 has a symmetric link (using any MANET 2047 interface) to the indicated symmetric 2048 1-hop neighbor." 2049 REFERENCE 2050 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2051 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2052 C., and J. Dean, April 2011" 2053 ::= { nhdpIib2HopSetEntry 2 } 2055 nhdpIib2HopSetIpAddrPrefixLen OBJECT-TYPE 2056 SYNTAX InetAddressPrefixLength 2057 MAX-ACCESS read-only 2058 STATUS current 2059 DESCRIPTION 2060 "Indicates the number of leading one bits that 2061 form the mask. The mask is logically ANDed 2062 to the nhdpIib2HopSetIpAddress to determine 2063 the address prefix. A row match is true 2064 if the address used as an index falls within 2065 the network address range defined by the 2066 address prefix." 2067 REFERENCE 2068 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2069 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2070 C., and J. Dean, April 2011" 2071 ::= { nhdpIib2HopSetEntry 3 } 2073 nhdpIib2HopSet1HopIfIndex OBJECT-TYPE 2074 SYNTAX NeighborIfIndex 2075 MAX-ACCESS read-only 2076 STATUS current 2077 DESCRIPTION 2078 "nhdpIib2HopSet1HopIfIndex is 2079 nhdpDiscIfIndex of the 1-hop 2080 neighbor that communicated the ipAddress 2081 of the 2-hop neighbor in this row entry." 2082 REFERENCE 2083 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2084 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2085 C., and J. Dean, April 2011" 2086 ::= { nhdpIib2HopSetEntry 4 } 2087 nhdpIib2HopSetN2Lost OBJECT-TYPE 2088 SYNTAX TruthValue 2089 MAX-ACCESS read-only 2090 STATUS current 2091 DESCRIPTION 2092 "nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and 2093 is a boolean flag, describing if for a 2-Hop Tuple, the 2094 corresponding Link Tuple currently is considered lost 2095 due to link quality." 2097 REFERENCE 2098 "draft-ietf-manet-nhdp-optimization-04 - 2099 An Optimization for the MANET Neighborhood Discovery 2100 Protocol (NHDP), Dearlove, C., and T. Clausen, 2101 January 2015" 2102 ::= {nhdpIib2HopSetEntry 5} 2104 nhdpIib2HopSetN2Time OBJECT-TYPE 2105 SYNTAX TimeStamp 2106 MAX-ACCESS read-only 2107 STATUS current 2108 DESCRIPTION 2109 "nhdpIib2HopSetN2Time specifies the value 2110 of sysUptime when this entry should expire and be 2111 removed from the nhdpIib2HopSetTable." 2112 REFERENCE 2113 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2114 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2115 C., and J. Dean, April 2011" 2116 ::= { nhdpIib2HopSetEntry 6 } 2118 -- 2119 -- Neighbor Information Base (NIB) 2120 -- 2121 -- Each router maintains a Neighbor Information Base 2122 -- that records information about addresses of 2123 -- current and recently symmetric 1-hop neighbors. 2125 -- 2126 -- Neighbor Set 2127 -- 2128 -- The Neighbor Set Table is small because 2129 -- most of the corresponding information is found 2130 -- in the nhdpDiscoveredIfTable above. 2131 -- 2132 nhdpNibNeighborSetTable OBJECT-TYPE 2133 SYNTAX SEQUENCE OF NhdpNibNeighborSetEntry 2134 MAX-ACCESS not-accessible 2135 STATUS current 2136 DESCRIPTION 2137 "A router's Neighbor Set records all 2138 network addresses of each 1-hop 2139 neighbor." 2140 REFERENCE 2141 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2142 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2143 C., and J. Dean, April 2011" 2144 ::= { nhdpStateObjGrp 6 } 2146 nhdpNibNeighborSetEntry OBJECT-TYPE 2147 SYNTAX NhdpNibNeighborSetEntry 2148 MAX-ACCESS not-accessible 2149 STATUS current 2150 DESCRIPTION 2151 "A router's Neighbor Set consists 2152 of Neighbor Tuples, each representing 2153 a single 1-hop neighbor: 2155 (N_neighbor_addr_list, N_symmetric)" 2156 REFERENCE 2157 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2158 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2159 C., and J. Dean, April 2011" 2160 INDEX { nhdpDiscRouterIndex } 2161 ::= { nhdpNibNeighborSetTable 1 } 2163 NhdpNibNeighborSetEntry ::= 2164 SEQUENCE { 2165 nhdpNibNeighborSetNSymmetric 2166 TruthValue 2167 } 2169 nhdpNibNeighborSetNSymmetric OBJECT-TYPE 2170 SYNTAX TruthValue 2171 MAX-ACCESS read-only 2172 STATUS current 2173 DESCRIPTION 2174 "nhdpNibNeighborNSymmetric corresponds 2175 to N_symmetric of NHDP and is a boolean flag, 2176 describing if this is a symmetric 1-hop neighbor." 2177 REFERENCE 2178 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2179 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2180 C., and J. Dean, April 2011" 2181 ::= { nhdpNibNeighborSetEntry 1 } 2183 -- 2184 -- Lost Neighbor Set 2185 -- 2186 nhdpNibLostNeighborSetTable OBJECT-TYPE 2187 SYNTAX SEQUENCE OF NhdpNibLostNeighborSetEntry 2188 MAX-ACCESS not-accessible 2189 STATUS current 2190 DESCRIPTION 2191 "A router's Lost Neighbor Set records network 2192 addresses of routers that were recently 2193 symmetric 1-hop neighbors but are now 2194 advertised as lost." 2195 REFERENCE 2196 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2197 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2198 C., and J. Dean, April 2011" 2199 ::= { nhdpStateObjGrp 7 } 2201 nhdpNibLostNeighborSetEntry OBJECT-TYPE 2202 SYNTAX NhdpNibLostNeighborSetEntry 2203 MAX-ACCESS not-accessible 2204 STATUS current 2205 DESCRIPTION 2206 "A router's Lost Neighbor Set consists of 2207 Lost Neighbor Tuples, each representing a 2208 single such network address: 2210 (NL_neighbor_addr, NL_time)" 2211 REFERENCE 2212 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2213 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2214 C., and J. Dean, April 2011" 2215 INDEX { nhdpDiscRouterIndex } 2216 ::= { nhdpNibLostNeighborSetTable 1 } 2218 NhdpNibLostNeighborSetEntry ::= 2219 SEQUENCE { 2220 nhdpNibLostNeighborSetNLTime 2221 TimeStamp 2222 } 2224 nhdpNibLostNeighborSetNLTime OBJECT-TYPE 2225 SYNTAX TimeStamp 2226 MAX-ACCESS read-only 2227 STATUS current 2228 DESCRIPTION 2229 "nhdpNibLostNeighborSetNLTime 2230 specifies the value of sysUptime when this entry 2231 should expire and be removed from the 2232 nhdpNibLostNeighborSetTable." 2233 REFERENCE 2234 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2235 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2236 C., and J. Dean, April 2011" 2237 ::= { nhdpNibLostNeighborSetEntry 1 } 2239 -- 2240 -- nhdpPerformanceObjGrp 2241 -- 2243 -- Contains objects that help to characterize the performance of 2244 -- the NHDP process, typically counters. 2245 -- 2246 nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 } 2248 -- 2249 -- Objects per local interface 2250 -- 2252 nhdpInterfacePerfTable OBJECT-TYPE 2253 SYNTAX SEQUENCE OF NhdpInterfacePerfEntry 2254 MAX-ACCESS not-accessible 2255 STATUS current 2256 DESCRIPTION 2257 "This table summarizes performance objects that are 2258 measured per local NHDP interface." 2259 REFERENCE 2260 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2261 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2262 C., and J. Dean, April 2011" 2263 ::= { nhdpPerformanceObjGrp 1 } 2265 nhdpInterfacePerfEntry OBJECT-TYPE 2266 SYNTAX NhdpInterfacePerfEntry 2267 MAX-ACCESS not-accessible 2268 STATUS current 2269 DESCRIPTION 2270 "A single entry contains performance counters for 2271 a local NHDP interface." 2272 INDEX { nhdpIfIndex } 2274 ::= { nhdpInterfacePerfTable 1 } 2276 NhdpInterfacePerfEntry ::= 2277 SEQUENCE { 2278 nhdpIfHelloMessageXmits 2279 Counter32, 2280 nhdpIfHelloMessageRecvd 2281 Counter32, 2282 nhdpIfHelloMessageXmitAccumulatedSize 2283 Counter64, 2284 nhdpIfHelloMessageRecvdAccumulatedSize 2285 Counter64, 2286 nhdpIfHelloMessageTriggeredXmits 2287 Counter32, 2288 nhdpIfHelloMessagePeriodicXmits 2289 Counter32, 2290 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount 2291 Counter32, 2292 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount 2293 Counter32, 2294 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount 2295 Counter32 2296 } 2298 nhdpIfHelloMessageXmits OBJECT-TYPE 2299 SYNTAX Counter32 2300 UNITS "messages" 2301 MAX-ACCESS read-only 2302 STATUS current 2303 DESCRIPTION 2304 "A counter is incremented each time a HELLO 2305 message has been transmitted on that interface." 2306 ::= { nhdpInterfacePerfEntry 1 } 2308 nhdpIfHelloMessageRecvd OBJECT-TYPE 2309 SYNTAX Counter32 2310 UNITS "messages" 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "A counter is incremented each time a 2315 HELLO message has been received on that interface." 2316 ::= { nhdpInterfacePerfEntry 2 } 2318 nhdpIfHelloMessageXmitAccumulatedSize OBJECT-TYPE 2319 SYNTAX Counter64 2320 UNITS "octets" 2321 MAX-ACCESS read-only 2322 STATUS current 2323 DESCRIPTION 2324 "A counter is incremented by the number of octets in 2325 a HELLO message each time a 2326 HELLO message has been sent." 2327 ::= { nhdpInterfacePerfEntry 3 } 2329 nhdpIfHelloMessageRecvdAccumulatedSize OBJECT-TYPE 2330 SYNTAX Counter64 2331 UNITS "octets" 2332 MAX-ACCESS read-only 2333 STATUS current 2334 DESCRIPTION 2335 "A counter is incremented by the number of octets in 2336 a HELLO message each time a 2337 HELLO message has been received." 2338 ::= { nhdpInterfacePerfEntry 4 } 2340 nhdpIfHelloMessageTriggeredXmits OBJECT-TYPE 2341 SYNTAX Counter32 2342 UNITS "messages" 2343 MAX-ACCESS read-only 2344 STATUS current 2345 DESCRIPTION 2346 "A counter is incremented each time a triggered 2347 HELLO message has been sent." 2348 ::= { nhdpInterfacePerfEntry 5 } 2350 nhdpIfHelloMessagePeriodicXmits OBJECT-TYPE 2351 SYNTAX Counter32 2352 UNITS "messages" 2353 MAX-ACCESS read-only 2354 STATUS current 2355 DESCRIPTION 2356 "A counter is incremented each time a periodic 2357 HELLO message has been sent." 2358 ::= { nhdpInterfacePerfEntry 6 } 2360 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount OBJECT-TYPE 2361 SYNTAX Counter32 2362 UNITS "neighbors" 2363 MAX-ACCESS read-only 2364 STATUS current 2365 DESCRIPTION 2366 "A counter is incremented by the number of advertised 2367 symmetric neighbors in a HELLO each time a HELLO 2368 message has been sent." 2369 ::= { nhdpInterfacePerfEntry 7 } 2370 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount OBJECT-TYPE 2371 SYNTAX Counter32 2372 UNITS "neighbors" 2373 MAX-ACCESS read-only 2374 STATUS current 2375 DESCRIPTION 2376 "A counter is incremented by the number of advertised 2377 heard neighbors in a HELLO each time a HELLO 2378 message has been sent." 2379 ::= { nhdpInterfacePerfEntry 8 } 2381 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount OBJECT-TYPE 2382 SYNTAX Counter32 2383 UNITS "neighbors" 2384 MAX-ACCESS read-only 2385 STATUS current 2386 DESCRIPTION 2387 "A counter is incremented by the number of advertised 2388 lost neighbors in a HELLO each time a HELLO 2389 message has been sent." 2390 ::= { nhdpInterfacePerfEntry 9 } 2392 -- 2393 -- Objects per discovered neighbor interface 2394 -- 2395 nhdpDiscIfSetPerfTable OBJECT-TYPE 2396 SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry 2397 MAX-ACCESS not-accessible 2398 STATUS current 2399 DESCRIPTION 2400 "A router's set of performance properties for 2401 each discovered interface of a neighbor." 2402 REFERENCE 2403 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2404 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2405 C., and J. Dean, April 2011" 2406 ::= { nhdpPerformanceObjGrp 2 } 2408 nhdpDiscIfSetPerfEntry OBJECT-TYPE 2409 SYNTAX NhdpDiscIfSetPerfEntry 2410 MAX-ACCESS not-accessible 2411 STATUS current 2412 DESCRIPTION 2413 "There is an entry for each discovered 2414 interface of a neighbor." 2416 REFERENCE 2417 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2418 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2419 C., and J. Dean, April 2011" 2420 INDEX { nhdpDiscIfIndex } 2421 ::= { nhdpDiscIfSetPerfTable 1 } 2423 NhdpDiscIfSetPerfEntry ::= 2424 SEQUENCE { 2425 nhdpDiscIfRecvdPackets 2426 Counter32, 2427 nhdpDiscIfExpectedPackets 2428 Counter32 2429 } 2431 nhdpDiscIfRecvdPackets OBJECT-TYPE 2432 SYNTAX Counter32 2433 UNITS "packets" 2434 MAX-ACCESS read-only 2435 STATUS current 2436 DESCRIPTION 2437 "This counter increments each 2438 time this router receives a packet from that interface 2439 of the neighbor." 2440 REFERENCE 2441 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2442 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2443 C., and J. Dean, April 2011" 2444 ::= { nhdpDiscIfSetPerfEntry 1 } 2446 nhdpDiscIfExpectedPackets OBJECT-TYPE 2447 SYNTAX Counter32 2448 UNITS "packets" 2449 MAX-ACCESS read-only 2450 STATUS current 2451 DESCRIPTION 2452 "This counter increments by the number 2453 of missed packets from this neighbor based 2454 on the packet sequence number each time this 2455 router receives a packet from that interface 2456 of the neighbor." 2457 REFERENCE 2458 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2459 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2460 C., and J. Dean, April 2011" 2461 ::= { nhdpDiscIfSetPerfEntry 2 } 2462 -- 2463 -- Objects concerning the Neighbor Set 2464 -- 2465 nhdpNibNeighborSetChanges OBJECT-TYPE 2466 SYNTAX Counter32 2467 UNITS "changes" 2468 MAX-ACCESS read-only 2469 STATUS current 2470 DESCRIPTION 2471 "This counter increments each time the Neighbor Set changes. 2472 A change occurs whenever a new Neighbor Tuple has been 2473 added, a Neighbor Tuple has been removed, or any entry of 2474 a Neighbor Tuple has been modified." 2475 ::= { nhdpPerformanceObjGrp 3 } 2477 -- 2478 -- Objects per discovered neighbor 2479 -- 2480 nhdpDiscNeighborSetPerfTable OBJECT-TYPE 2481 SYNTAX SEQUENCE OF NhdpDiscNeighborSetPerfEntry 2482 MAX-ACCESS not-accessible 2483 STATUS current 2484 DESCRIPTION 2485 "A router's set of discovered neighbors and 2486 their properties." 2487 REFERENCE 2488 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2489 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2490 C., and J. Dean, April 2011" 2491 ::= { nhdpPerformanceObjGrp 4 } 2493 nhdpDiscNeighborSetPerfEntry OBJECT-TYPE 2494 SYNTAX NhdpDiscNeighborSetPerfEntry 2495 MAX-ACCESS not-accessible 2496 STATUS current 2497 DESCRIPTION 2498 "The entries include the nhdpDiscRouterIndex of 2499 the discovered router as well as performance 2500 objects related to changes of the Neighbor 2501 Set." 2502 REFERENCE 2503 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2504 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2505 C., and J. Dean, April 2011" 2506 INDEX { nhdpDiscRouterIndex } 2507 ::= { nhdpDiscNeighborSetPerfTable 1 } 2508 NhdpDiscNeighborSetPerfEntry ::= 2509 SEQUENCE { 2510 nhdpDiscNeighborNibNeighborSetChanges 2511 Counter32, 2512 nhdpDiscNeighborNibNeighborSetUpTime 2513 TimeStamp, 2514 nhdpDiscNeighborNibNeighborSetReachableLinkChanges 2515 Counter32 2516 } 2518 nhdpDiscNeighborNibNeighborSetChanges OBJECT-TYPE 2519 SYNTAX Counter32 2520 UNITS "changes" 2521 MAX-ACCESS read-only 2522 STATUS current 2523 DESCRIPTION 2524 "This object returns the number of changes 2525 to the given Neighbor Tuple." 2526 REFERENCE 2527 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2528 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2529 C., and J. Dean, April 2011" 2530 ::= { nhdpDiscNeighborSetPerfEntry 1 } 2532 nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE 2533 SYNTAX TimeStamp 2534 MAX-ACCESS read-only 2535 STATUS current 2536 DESCRIPTION 2537 "This object returns the sysUpTime when 2538 the neighbor becomes 'nbrup'. A neighbor is 2539 said to become 'nbrup' if a new nhdpNibNeighborSetEntry 2540 is created for a particular nhdpNibNeighborSetRouterIndex. 2541 It becomes 'nbrdown' if the entry for that neighbor 2542 has been deleted." 2543 REFERENCE 2544 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2545 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2546 C., and J. Dean, April 2011" 2547 ::= { nhdpDiscNeighborSetPerfEntry 2 } 2549 nhdpDiscNeighborNibNeighborSetReachableLinkChanges OBJECT-TYPE 2550 SYNTAX Counter32 2551 UNITS "changes" 2552 MAX-ACCESS read-only 2553 STATUS current 2554 DESCRIPTION 2555 "This object counts each time the neighbor changes 2556 the interface(s) over which it is reachable. 2557 A change in the set of Link Tuples corresponding 2558 to the appropriate Neighbor Tuple is registered, 2559 i.e., a corresponding Link Tuple is added or removed 2560 from the set of all corresponding Link Tuples." 2561 REFERENCE 2562 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2563 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2564 C., and J. Dean, April 2011" 2565 ::= { nhdpDiscNeighborSetPerfEntry 3 } 2567 -- 2568 -- Objects per discovered 2-hop neighbor 2569 -- 2570 nhdpIib2HopSetPerfTable OBJECT-TYPE 2571 SYNTAX SEQUENCE OF NhdpIib2HopSetPerfEntry 2572 MAX-ACCESS not-accessible 2573 STATUS current 2574 DESCRIPTION 2575 "This table contains performance objects per 2576 discovered 2-hop neighbor." 2577 REFERENCE 2578 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2579 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2580 C., and J. Dean, April 2011" 2581 ::= { nhdpPerformanceObjGrp 5 } 2583 nhdpIib2HopSetPerfEntry OBJECT-TYPE 2584 SYNTAX NhdpIib2HopSetPerfEntry 2585 MAX-ACCESS not-accessible 2586 STATUS current 2587 DESCRIPTION 2588 "The entries contain performance objects per 2589 discovered 2-hop neighbor." 2590 REFERENCE 2591 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2592 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2593 C., and J. Dean, April 2011" 2594 INDEX { nhdpDiscRouterIndex } 2595 ::= { nhdpIib2HopSetPerfTable 1 } 2597 NhdpIib2HopSetPerfEntry ::= 2598 SEQUENCE { 2599 nhdpIib2HopSetPerfChanges 2600 Counter32, 2601 nhdpIib2HopSetPerfUpTime 2602 TimeStamp 2603 } 2605 nhdpIib2HopSetPerfChanges OBJECT-TYPE 2606 SYNTAX Counter32 2607 UNITS "changes" 2608 MAX-ACCESS read-only 2609 STATUS current 2610 DESCRIPTION 2611 "This object counts the changes of the union of all 2612 N2_neighbor_iface_addr_list of 2-Hop Tuples with an 2613 N2_2hop_addr equal to one of the given 2-hop 2614 neighbor's addresses." 2615 REFERENCE 2616 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2617 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2618 C., and J. Dean, April 2011" 2619 ::= { nhdpIib2HopSetPerfEntry 1 } 2621 nhdpIib2HopSetPerfUpTime OBJECT-TYPE 2622 SYNTAX TimeStamp 2623 MAX-ACCESS read-only 2624 STATUS current 2625 DESCRIPTION 2626 "This object returns the sysUpTime 2627 when the 2-Hop Tuple 2628 corresponding to the given 2-hop neighbor IP address 2629 was registered in the nhdpIib2HopSetTable." 2630 REFERENCE 2631 "RFC 6130 - Mobile Ad Hoc Network (MANET) Neighborhood 2632 Discovery Protocol (NHDP), Clausen, T., Dearlove, 2633 C., and J. Dean, April 2011" 2634 ::= { nhdpIib2HopSetPerfEntry 2 } 2636 -- 2637 -- nhdpNotifications 2638 -- 2640 nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 0 } 2641 nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 } 2642 nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 2 } 2643 -- nhdpNotificationsObjects 2645 nhdpNbrStateChange NOTIFICATION-TYPE 2646 OBJECTS { nhdpIfName, -- The originator of 2647 -- the notification. 2648 nhdpNbrState -- The new state 2649 } 2650 STATUS current 2651 DESCRIPTION 2652 "nhdpNbrStateChange is a notification sent when 2653 more than nhdpNbrStateChangeThreshold neighbors change 2654 their status (i.e., 'down(0)', 'asymmetric(1)', or 2655 'symmetric(2)') within a time window of 2656 nhdpNbrStateChangeWindow." 2657 ::= { nhdpNotificationsObjects 1 } 2659 nhdp2HopNbrStateChange NOTIFICATION-TYPE 2660 OBJECTS { nhdpIfName, -- The originator 2661 -- of the notification 2662 nhdp2HopNbrState -- The new state 2663 } 2664 STATUS current 2665 DESCRIPTION 2666 "nhdp2HopNbrStateChange is a notification sent 2667 when more than nhdp2HopNbrStateChangeThreshold 2-hop 2668 neighbors change their nhdp2HopNbrState from either: 2669 - 'down(0)' to 'up(1)', or 2670 - 'up(1)' to 'down(0)', or 2671 - 'notconsidered(2)' to 'down(0)', or 2672 - 'down(0)' to 'notconsidered(2)' 2673 within a time window of 2674 nhdp2HopNbrStateChangeWindow." 2675 ::= { nhdpNotificationsObjects 2 } 2677 nhdpIfStateChange NOTIFICATION-TYPE 2678 OBJECTS { nhdpIfName, -- The local interface 2679 nhdpIfStatus -- The new status 2680 } 2681 STATUS current 2682 DESCRIPTION 2683 "nhdpIfStateChange is a notification sent when 2684 nhdpIfStatus has changed on this interface." 2685 ::= { nhdpNotificationsObjects 3 } 2687 -- nhdpNotificationsControl 2689 nhdpNbrStateChangeThreshold OBJECT-TYPE 2690 SYNTAX Integer32 (0..255) 2691 UNITS "changes" 2692 MAX-ACCESS read-write 2693 STATUS current 2694 DESCRIPTION 2695 "A threshold value for the 2696 nhdpNbrStateChange object. If the 2697 number of occurrences exceeds this threshold 2698 within the previous nhdpNbrStateChangeWindow, 2699 then the nhdpNbrStateChange notification 2700 is to be sent. 2702 It is recommended that the value of this 2703 threshold be set to at least 10 and higher 2704 in dense topologies with frequent expected 2705 topology changes." 2706 DEFVAL { 10 } 2707 ::= { nhdpNotificationsControl 1 } 2709 nhdpNbrStateChangeWindow OBJECT-TYPE 2710 SYNTAX TimeTicks 2711 MAX-ACCESS read-write 2712 STATUS current 2713 DESCRIPTION 2714 "A time window for the 2715 nhdpNbrStateChange object. If the 2716 number of occurrences exceeds the 2717 nhdpNbrStateChangeThreshold 2718 within the previous nhdpNbrStateChangeWindow, 2719 then the nhdpNbrStateChange notification 2720 is to be sent. 2722 It is recommended that the value for this 2723 window be set to at least 5 times the 2724 nhdpHelloInterval. 2726 This object represents the time in hundredths 2727 of a second." 2728 DEFVAL { 1000 } 2729 ::= { nhdpNotificationsControl 2 } 2731 nhdp2HopNbrStateChangeThreshold OBJECT-TYPE 2732 SYNTAX Integer32 (0..255) 2733 UNITS "changes" 2734 MAX-ACCESS read-write 2735 STATUS current 2736 DESCRIPTION 2737 "A threshold value for the 2738 nhdp2HopNbrStateChange object. If the 2739 number of occurrences exceeds this threshold 2740 within the previous nhdp2HopNbrStateChangeWindow, 2741 then the nhdp2HopNbrStateChange notification 2742 is to be sent. 2744 It is recommended that the value of this 2745 threshold be set to at least 10 and higher 2746 when topologies are expected to be highly dynamic." 2747 DEFVAL { 10 } 2748 ::= { nhdpNotificationsControl 3 } 2750 nhdp2HopNbrStateChangeWindow OBJECT-TYPE 2751 SYNTAX TimeTicks 2752 MAX-ACCESS read-write 2753 STATUS current 2754 DESCRIPTION 2755 "A time window for the 2756 nhdp2HopNbrStateChange object. If the 2757 number of occurrences exceeds the 2758 nhdp2HopNbrStateChangeThreshold 2759 within the previous nhdp2HopNbrStateChangeWindow, 2760 then the nhdp2HopNbrStateChange notification 2761 is to be sent. 2763 It is recommended that the value for this 2764 window be set to at least 5 times 2765 nhdpHelloInterval. 2767 This object represents the time in hundredths 2768 of a second." 2769 DEFVAL { 1000 } 2770 ::= { nhdpNotificationsControl 4 } 2772 -- nhdpNotificationStates 2774 nhdpNbrState OBJECT-TYPE 2775 SYNTAX INTEGER { 2776 down(0), 2777 asymmetric(1), 2778 symmetric(2) 2779 } 2780 MAX-ACCESS read-only 2781 STATUS current 2782 DESCRIPTION 2783 "NHDP neighbor states. In NHDP, it is not 2784 necessary to remove Protocol Tuples from Protocol Sets 2785 at the exact time indicated, only to behave as if the 2786 Protocol Tuples were removed at that time. This case is 2787 indicated here as 'down(0)', all other cases being 2788 indicated as 'asymmetric(1)' or 'symmetric(2)'. If 'down(0)', 2789 the direct neighbor is also added to the 2790 nhdpNibLostNeighborSetTable." 2791 ::= { nhdpNotificationsStates 1 } 2793 nhdp2HopNbrState OBJECT-TYPE 2794 SYNTAX INTEGER { 2795 down(0), 2796 up(1), 2797 notconsidered(2) 2798 } 2799 MAX-ACCESS read-only 2800 STATUS current 2801 DESCRIPTION 2802 "NHDP 2-hop neighbor states. In NHDP, it is not necessary 2803 to remove Protocol Tuples from Protocol Sets at the 2804 exact time indicated, only to behave as if the Protocol 2805 Tuples were removed at that time. This case is indicated 2806 here as 'down(0)'; otherwise, it is either 'up(1)', if 2807 N2_lost for the 2-Hop Tuple is equal to false, or 2808 'notconsidered(2)' otherwise." 2809 ::= { nhdpNotificationsStates 2 } 2811 -- 2812 -- nhdpConformance information 2813 -- 2815 nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 } 2816 nhdpMIBGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 } 2818 -- Compliance Statements 2819 nhdpBasicCompliance MODULE-COMPLIANCE 2820 STATUS current 2821 DESCRIPTION 2822 "The basic implementation requirements for 2823 managed network entities that implement 2824 NHDP." 2825 MODULE -- this module 2826 MANDATORY-GROUPS { nhdpConfigurationGroup } 2827 ::= { nhdpCompliances 1 } 2829 nhdpFullCompliance2 MODULE-COMPLIANCE 2830 STATUS current 2831 DESCRIPTION 2832 "The full implementation requirements for 2833 managed network entities that implement 2834 NHDP." 2835 MODULE -- this module 2836 MANDATORY-GROUPS { nhdpConfigurationGroup, 2837 nhdpStateGroup2, 2838 nhdpNotificationObjectGroup, 2839 nhdpNotificationGroup, 2840 nhdpPerformanceGroup 2841 } 2842 ::= { nhdpCompliances 3 } 2844 -- 2845 -- Units of Conformance 2846 -- 2848 nhdpConfigurationGroup OBJECT-GROUP 2849 OBJECTS { 2850 nhdpIfName, 2851 nhdpIfStatus, 2852 nhdpHelloInterval, 2853 nhdpHelloMinInterval, 2854 nhdpRefreshInterval, 2855 nhdpLHoldTime, 2856 nhdpHHoldTime, 2857 nhdpHystAcceptQuality, 2858 nhdpHystRejectQuality, 2859 nhdpInitialQuality, 2860 nhdpInitialPending, 2861 nhdpHpMaxJitter, 2862 nhdpHtMaxJitter, 2863 nhdpNHoldTime, 2864 nhdpIHoldTime, 2865 nhdpIfRowStatus, 2866 nhdpLibLocalIfSetIfIndex, 2867 nhdpLibLocalIfSetIpAddrType, 2868 nhdpLibLocalIfSetIpAddr, 2869 nhdpLibLocalIfSetIpAddrPrefixLen, 2870 nhdpLibLocalIfSetRowStatus, 2871 nhdpLibRemovedIfAddrSetIpAddrType, 2872 nhdpLibRemovedIfAddrSetIpAddr, 2873 nhdpLibRemovedIfAddrSetIpAddrPrefixLen, 2874 nhdpLibRemovedIfAddrSetIfIndex, 2875 nhdpLibRemovedIfAddrSetIRTime 2876 } 2877 STATUS current 2878 DESCRIPTION 2879 "Set of NHDP configuration objects implemented 2880 in this module." 2881 ::= { nhdpMIBGroups 2 } 2883 nhdpPerformanceGroup OBJECT-GROUP 2884 OBJECTS { 2885 nhdpIfHelloMessageXmits, 2886 nhdpIfHelloMessageRecvd, 2887 nhdpIfHelloMessageXmitAccumulatedSize, 2888 nhdpIfHelloMessageRecvdAccumulatedSize, 2889 nhdpIfHelloMessageTriggeredXmits, 2890 nhdpIfHelloMessagePeriodicXmits, 2891 nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount, 2892 nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount, 2893 nhdpIfHelloMessageXmitAccumulatedLostNeighborCount, 2894 nhdpDiscIfRecvdPackets, 2895 nhdpDiscIfExpectedPackets, 2896 nhdpNibNeighborSetChanges, 2897 nhdpDiscNeighborNibNeighborSetChanges, 2898 nhdpDiscNeighborNibNeighborSetUpTime, 2899 nhdpDiscNeighborNibNeighborSetReachableLinkChanges, 2900 nhdpIib2HopSetPerfChanges, 2901 nhdpIib2HopSetPerfUpTime 2902 } 2903 STATUS current 2904 DESCRIPTION 2905 "Set of NHDP performance objects implemented 2906 in this module." 2907 ::= { nhdpMIBGroups 4 } 2909 nhdpNotificationObjectGroup OBJECT-GROUP 2910 OBJECTS { 2911 nhdpNbrStateChangeThreshold, 2912 nhdpNbrStateChangeWindow, 2913 nhdp2HopNbrStateChangeThreshold, 2914 nhdp2HopNbrStateChangeWindow, 2915 nhdpNbrState, 2916 nhdp2HopNbrState 2917 } 2918 STATUS current 2919 DESCRIPTION 2920 "Set of NHDP notification objects implemented 2921 in this module." 2922 ::= { nhdpMIBGroups 5 } 2923 nhdpNotificationGroup NOTIFICATION-GROUP 2924 NOTIFICATIONS { 2925 nhdpNbrStateChange, 2926 nhdp2HopNbrStateChange, 2927 nhdpIfStateChange 2928 } 2929 STATUS current 2930 DESCRIPTION 2931 "Set of NHDP notifications implemented 2932 in this module." 2933 ::= { nhdpMIBGroups 6 } 2935 nhdpStateGroup2 OBJECT-GROUP 2936 OBJECTS { 2937 nhdpUpTime, 2938 nhdpIfStateUpTime, 2939 nhdpDiscRouterIndex, 2940 nhdpDiscIfIndex, 2941 nhdpDiscIfSetIpAddrType, 2942 nhdpDiscIfSetIpAddr, 2943 nhdpDiscIfSetIpAddrPrefixLen, 2944 nhdpIibLinkSetLHeardTime, 2945 nhdpIibLinkSetLSymTime, 2946 nhdpIibLinkSetLPending, 2947 nhdpIibLinkSetLLost, 2948 nhdpIibLinkSetLTime, 2949 nhdpIib2HopSetIpAddrPrefixLen, 2950 nhdpIib2HopSet1HopIfIndex, 2951 nhdpIib2HopSetN2Time, 2952 nhdpIib2HopSetN2Lost, 2953 nhdpNibNeighborSetNSymmetric, 2954 nhdpNibLostNeighborSetNLTime 2955 } 2956 STATUS current 2957 DESCRIPTION 2958 "Set of NHDP state objects implemented 2959 in this module." 2960 ::= { nhdpMIBGroups 7 } 2962 -- 2963 -- Deprecated compliance statements and groups 2964 -- 2966 nhdpFullCompliance MODULE-COMPLIANCE 2967 STATUS deprecated 2968 DESCRIPTION 2969 "The full implementation requirements for 2970 managed network entities that implement 2971 NHDP. 2973 For version-independence, this compliance statement 2974 is deprecated in favor of nhdpFullCompliance2." 2975 MODULE -- this module 2976 MANDATORY-GROUPS { nhdpConfigurationGroup, 2977 nhdpStateGroup, 2978 nhdpNotificationObjectGroup, 2979 nhdpNotificationGroup, 2980 nhdpPerformanceGroup 2981 } 2982 ::= { nhdpCompliances 2 } 2984 nhdpStateGroup OBJECT-GROUP 2985 OBJECTS { 2986 nhdpUpTime, 2987 nhdpIfStateUpTime, 2988 nhdpDiscRouterIndex, 2989 nhdpDiscIfIndex, 2990 nhdpDiscIfSetIpAddrType, 2991 nhdpDiscIfSetIpAddr, 2992 nhdpDiscIfSetIpAddrPrefixLen, 2993 nhdpIibLinkSetLHeardTime, 2994 nhdpIibLinkSetLSymTime, 2995 nhdpIibLinkSetLPending, 2996 nhdpIibLinkSetLLost, 2997 nhdpIibLinkSetLTime, 2998 nhdpIib2HopSetIpAddrPrefixLen, 2999 nhdpIib2HopSet1HopIfIndex, 3000 nhdpIib2HopSetN2Time, 3001 nhdpNibNeighborSetNSymmetric, 3002 nhdpNibLostNeighborSetNLTime 3003 } 3004 STATUS deprecated 3005 DESCRIPTION 3006 "Set of NHDP state objects implemented 3007 in this module. 3009 For version-independence, this compliance statement 3010 is deprecated in favor of nhdpStateGroup2." 3011 ::= { nhdpMIBGroups 3 } 3013 END 3014 8. Security Considerations 3016 This MIB module defines objects for the configuration, monitoring, 3017 and notification of the Neighborhood Discovery Protocol [RFC6130]. 3018 NHDP allows routers to acquire topological information up to two hops 3019 away by virtue of exchanging HELLO messages. The information 3020 acquired by NHDP may be used by routing protocols. The neighborhood 3021 information, exchanged between routers using NHDP, serves these 3022 routing protocols as a baseline for calculating paths to all 3023 destinations in the MANET, relay set selection for network-wide 3024 transmissions, etc. 3026 There are a number of management objects defined in this MIB module 3027 with a MAX-ACCESS clause of read-write and/or read-create. Such 3028 objects may be considered sensitive or vulnerable in some network 3029 environments. The support for SET operations in a non-secure 3030 environment without proper protection can have a negative effect on 3031 network operations. These are the tables and objects and their 3032 sensitivity/vulnerability: 3034 o nhdpIfStatus - This writable object turns on or off the NHDP 3035 process for the specified interface. If disabled, higher-level 3036 protocol functions, e.g., routing, would fail, causing network- 3037 wide disruptions. 3039 o nhdpHelloInterval, nhdpHelloMinInterval, and nhdpRefreshInterval - 3040 These writable objects control the rate at which HELLO messages 3041 are sent on an interface. If set at too high a rate, this could 3042 represent a form of denial-of-service (DoS) attack by overloading 3043 interface resources. 3045 o nhdpHystAcceptQuality, nhdpHystRejectQuality, nhdpInitialQuality, 3046 and nhdpInitialPending - These writable objects affect the 3047 perceived quality of the NHDP links and hence the overall 3048 stability of the network. If improperly set, these settings could 3049 result in network-wide disruptions. 3051 o nhdpInterfaceTable - This table contains writable objects that 3052 affect the overall performance and stability of the NHDP process. 3053 Failure of the NHDP process would result in network-wide failure. 3054 Particularly sensitive objects from this table are discussed in 3055 the previous list items. This is the only table in the NHDP-MIB 3056 module with writable objects. 3058 Some of the readable objects in this MIB module (i.e., objects with a 3059 MAX-ACCESS other than not-accessible) may be considered sensitive or 3060 vulnerable in some network environments. It is thus important to 3061 control even GET and/or NOTIFY access to these objects and possibly 3062 to even encrypt the values of these objects when sending them over 3063 the network via SNMP. These are the tables and objects and their 3064 sensitivity/vulnerability: 3066 o nhdpDiscIfSetTable - The object contains information on discovered 3067 neighbors, specifically their IP address in the 3068 nhdpDiscIfSetIpAddr object. This information provides an 3069 adversary broad information on the members of the MANET, located 3070 within this single table. This information can be used to 3071 expedite attacks on the other members of the MANET without having 3072 to go through a laborious discovery process on their own. This 3073 object is the index into the table and has a MAX-ACCESS of 'not- 3074 accessible'. However, this information can be exposed using SNMP 3075 operations. 3077 MANET technology is often deployed to support communications of 3078 emergency services or military tactical applications. In these 3079 applications, it is imperative to maintain the proper operation of 3080 the communications network and to protect sensitive information 3081 related to its operation. Therefore, it is RECOMMENDED to provide 3082 support for the Transport Security Model (TSM) [RFC5591] in 3083 combination with TLS/DTLS [RFC6353]. 3085 SNMP versions prior to SNMPv3 did not include adequate security. 3086 Even if the network itself is secure (for example by using IPsec), 3087 there is no control as to who on the secure network is allowed to 3088 access and GET/SET (read/change/create/delete) the objects in this 3089 MIB module. 3091 Implementations MUST provide the security features described by the 3092 SNMPv3 framework (see [RFC3410]), including full support for 3093 authentication and privacy via the User-based Security Model (USM) 3094 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 3095 MAY also provide support for the Transport Security Model (TSM) 3096 [RFC5591] in combination with a secure transport such as SSH 3097 [RFC5592] or TLS/DTLS [RFC6353]. 3099 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3100 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3101 enable cryptographic security. It is then a customer/operator 3102 responsibility to ensure that the SNMP entity giving access to an 3103 instance of this MIB module is properly configured to give access to 3104 the objects only to those principals (users) that have legitimate 3105 rights to indeed GET or SET (change/create/delete) them. 3107 9. Applicability Statement 3109 This document describes objects for configuring parameters of the 3110 Neighborhood Discovery Protocol [RFC6130] process on a router. This 3111 MIB module, denoted NHDP-MIB, also reports state, performance 3112 information, and notifications. This section provides some examples 3113 of how this MIB module can be used in MANET network deployments. A 3114 fuller discussion of MANET network management use cases and 3115 challenges will be provided elsewhere. 3117 NHDP is designed to allow routers to automatically discover and track 3118 routers one hop remote (denoted "neighbors") and routers two hops 3119 remote (denoted "two-hop neighbors"). This information is used by 3120 other MANET protocols in operation on the router to perform routing, 3121 multicast forwarding, and other functions with ad hoc and mobile 3122 networks. In the following, three example scenarios are listed where 3123 this MIB module is useful: 3125 o For a Parking Lot Initial Configuration Situation - It is common 3126 for the vehicles comprising the MANET being forward deployed at a 3127 remote location, e.g., the site of a natural disaster, to be off- 3128 loaded in a parking lot where an initial configuration of the 3129 networking devices is performed. The configuration is loaded into 3130 the devices from a fixed location Network Operation Center (NOC) 3131 at the parking lot, and the vehicles are stationary at the parking 3132 lot while the configuration changes are made. Standards-based 3133 methods for configuration management from the co-located NOC are 3134 necessary for this deployment option. 3136 o For Mobile Vehicles with Low-Bandwidth Satellite Link to a Fixed 3137 NOC - Here, the vehicles carrying the MANET routers carry multiple 3138 wireless interfaces, one of which is a relatively low-bandwidth, 3139 on-the-move satellite connection that interconnects a fix NOC to 3140 the nodes of the MANET. Standards-based methods for monitoring 3141 and fault management from the fixed NOC are necessary for this 3142 deployment option. 3144 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 3145 larger vehicles, a hierarchical network management arrangement is 3146 useful. Centralized network management is performed from a fixed 3147 NOC while local management is performed locally from within the 3148 vehicles. Standards-based methods for configuration, monitoring, 3149 and fault management are necessary for this deployment option. 3151 10. IANA Considerations 3153 The MIB module in this document uses the following IANA-assigned 3154 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 3156 Descriptor OBJECT IDENTIFIER value 3157 ---------- ----------------------- 3158 NHDP-MIB { mib-2 213 } 3160 11. Acknowledgements 3162 The authors wish to thank Benoit Claise, Justin Dean, Adrian Farrel, 3163 Joel Halpern, Al Morton, and Thomas Nadeau for their detailed reviews 3164 and insightful comments regarding RFC6779 and this document. 3166 This MIB document uses the template authored by D. Harrington, which 3167 is based on contributions from the MIB Doctors, especially Juergen 3168 Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn. 3170 12. References 3172 12.1. Normative References 3174 [RFC2119] Bradner, S., "Key words for use 3175 in RFCs to Indicate Requirement 3176 Levels", BCP 14, RFC 2119, 3177 March 1997. 3179 [RFC2578] McCloghrie, K., Ed., Perkins, 3180 D., Ed., and J. Schoenwaelder, 3181 Ed., "Structure of Management 3182 Information Version 2 (SMIv2)", 3183 STD 58, RFC 2578, April 1999. 3185 [RFC2579] McCloghrie, K., Ed., Perkins, 3186 D., Ed., and J. Schoenwaelder, 3187 Ed., "Textual Conventions for 3188 SMIv2", STD 58, RFC 2579, 3189 April 1999. 3191 [RFC2580] McCloghrie, K., Perkins, D., 3192 and J. Schoenwaelder, 3193 "Conformance Statements for 3194 SMIv2", STD 58, RFC 2580, 3195 April 1999. 3197 [RFC2863] McCloghrie, K. and F. 3198 Kastenholz, "The Interfaces 3199 Group MIB", RFC 2863, 3200 June 2000. 3202 [RFC3418] Presuhn, R., "Management 3203 Information Base (MIB) for the 3204 Simple Network Management 3205 Protocol (SNMP)", STD 62, 3206 RFC 3418, December 2002. 3208 [RFC4001] Daniele, M., Haberman, B., 3209 Routhier, S., and J. 3210 Schoenwaelder, "Textual 3211 Conventions for Internet 3212 Network Addresses", RFC 4001, 3213 February 2005. 3215 [RFC6130] Clausen, T., Dearlove, C., and 3216 J. Dean, "Mobile Ad Hoc Network 3217 (MANET) Neighborhood Discovery 3218 Protocol (NHDP)", RFC 6130, 3219 April 2011. 3221 [RFC6340] Presuhn, R., "Textual 3222 Conventions for the 3223 Representation of Floating- 3224 Point Numbers", RFC 6340, 3225 August 2011. 3227 [draft-ietf-manet-nhdp-optimization] Dearlove, C. and T. Clausen, 3228 "An Optimization for the MANET 3229 Neighborhood Discovery Protocol 3230 (NHDP)", work in progress draft 3231 -ietf-manet-nhdp-optimization- 3232 04, January 2015. 3234 12.2. Informative References 3236 [RFC3410] Case, J., Mundy, R., Partain, 3237 D., and B. Stewart, 3238 "Introduction and Applicability 3239 Statements for Internet- 3240 Standard Management Framework", 3241 RFC 3410, December 2002. 3243 [RFC3414] Blumenthal, U. and B. Wijnen, 3244 "User-based Security Model 3245 (USM) for version 3 of the 3246 Simple Network Management 3247 Protocol (SNMPv3)", STD 62, 3248 RFC 3414, December 2002. 3250 [RFC3826] Blumenthal, U., Maino, F., and 3251 K. McCloghrie, "The Advanced 3252 Encryption Standard (AES) 3253 Cipher Algorithm in the SNMP 3254 User-based Security Model", 3255 RFC 3826, June 2004. 3257 [RFC4750] Joyal, D., Galecki, P., 3258 Giacalone, S., Coltun, R., and 3259 F. Baker, "OSPF Version 2 3260 Management Information Base", 3261 RFC 4750, December 2006. 3263 [RFC5148] Clausen, T., Dearlove, C., and 3264 B. Adamson, "Jitter 3265 Considerations in Mobile Ad Hoc 3266 Networks (MANETs)", RFC 5148, 3267 February 2008. 3269 [RFC5591] Harrington, D. and W. Hardaker, 3270 "Transport Security Model for 3271 the Simple Network Management 3272 Protocol (SNMP)", RFC 5591, 3273 June 2009. 3275 [RFC5592] Harrington, D., Salowey, J., 3276 and W. Hardaker, "Secure Shell 3277 Transport Model for the Simple 3278 Network Management Protocol 3279 (SNMP)", RFC 5592, June 2009. 3281 [RFC6353] Hardaker, W., "Transport Layer 3282 Security (TLS) Transport Model 3283 for the Simple Network 3284 Management Protocol (SNMP)", 3285 RFC 6353, July 2011. 3287 [RFC6779] Herberg, U., Cole, R., and I. 3288 Chakeres, "Definition of 3289 Managed Objects for the 3290 Neighborhood Discovery 3291 Protocol", RFC 6779, 3292 October 2012. 3294 Authors' Addresses 3296 Ulrich Herberg 3297 United States 3299 EMail: ulrich@herberg.name 3300 URI: http://www.herberg.name/ 3302 Robert G. Cole 3303 US Army CERDEC 3304 Space and Terrestrial Communications 3305 6010 Frankford Road 3306 Aberdeen Proving Ground, Maryland 21005 3307 United States 3309 Phone: +1 443 395-8744 3310 EMail: robert.g.cole@us.army.mil 3311 URI: http://www.cs.jhu.edu/~rgcole/ 3313 Ian D Chakeres 3314 Delvin 3315 Ellicott City, Maryland 21042 3316 United States 3318 EMail: ian.chakeres@gmail.com 3319 URI: http://www.ianchak.com/ 3321 Thomas Heide Clausen 3322 LIX, Ecole Polytechnique 3324 Phone: +33 6 6058 9349 3325 EMail: T.Clausen@computer.org 3326 URI: http://www.ThomasClausen.org/