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