idnits 2.17.1 draft-ietf-manet-smf-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1315 has weird spacing: '...s state table...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (May 28, 2012) is 4343 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'SMF' is mentioned on line 877, but not defined Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft US Army CERDEC 4 Intended status: Experimental J. Macker 5 Expires: November 29, 2012 B. Adamson 6 Naval Research Laboratory 7 May 28, 2012 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-04 13 Abstract 15 This memo defines a portion of the Management Information Base (MIB) 16 for use with network management protocols in the Internet community. 17 In particular, it describes objects for configuring aspects of the 18 Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc 19 Networks (MANETs). The SMF-MIB also reports state information, 20 performance metrics, and notifications. In addition to 21 configuration, the additional state and performance information is 22 useful to operators troubleshooting multicast forwarding problems. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on November 29, 2012. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 63 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 65 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 66 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 67 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 68 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 69 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 70 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 71 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 72 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 73 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 74 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 8 75 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 76 8. Security Considerations . . . . . . . . . . . . . . . . . . . 49 77 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 78 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 52 79 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 52 80 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 52 81 12.1. Normative References . . . . . . . . . . . . . . . . . . . 52 82 12.2. Informative References . . . . . . . . . . . . . . . . . . 53 83 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 54 84 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 55 85 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 55 87 1. Introduction 89 This memo defines a portion of the Management Information Base (MIB) 90 for use with network management protocols in the Internet community. 91 In particular, it describes objects for configuring aspects of a 92 process implementing Simplified Multicast Forwarding (SMF) 93 [I-D.ietf-manet-smf] for Mobile Ad-Hoc Networks (MANETs). SMF 94 provides multicast Duplicate Packet Detection (DPD) and supports 95 algorithms for constructing an estimate of a MANET Minimum Connected 96 Dominating Set (MCDS) for efficient multicast forwarding. The SMF- 97 MIB also reports state information, performance metrics, and 98 notifications. In addition to configuration, this additional state 99 and performance information is useful to operators troubleshooting 100 multicast forwarding problems. 102 2. The Internet-Standard Management Framework 104 For a detailed overview of the documents that describe the current 105 Internet-Standard Management Framework, please refer to section 7 of 106 RFC 3410 [RFC3410]. 108 Managed objects are accessed via a virtual information store, termed 109 the Management Information Base or MIB. MIB objects are generally 110 accessed through the Simple Network Management Protocol (SNMP). 111 Objects in the MIB are defined using the mechanisms defined in the 112 Structure of Management Information (SMI). This memo specifies a MIB 113 module that is compliant to the SMIv2, which is described in STD 58, 114 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 115 [RFC2580]. 117 3. Conventions 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 121 document are to be interpreted as described in RFC 2119 [RFC2119]. 123 4. Overview 125 SMF provides methods for implementing DPD-based multicast forwarding 126 with the optional use of Connected Dominating Set (CDS)-based relay 127 sets. The CDS provides a complete connected coverage of the nodes 128 comprising the MANET. The MCDS is the smallest set of MANET nodes 129 (comprising a connected cluster) which cover all the nodes in the 130 cluster with their transmissions. As the density of the MANET nodes 131 increase, the fraction of nodes required in an MCDS decreases. Using 132 the MCDS as a multicast forwarding set then becomes an efficient 133 multicast mechanism for MANETs. 135 Various algorithms for the construction of estimates of the MCDS 136 exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] 137 describes some of these. It further defines various operational 138 modes for a node which is participating in the collective creation of 139 the MCDS estimates. These modes depend upon the set of related MANET 140 routing and discovery protocols and mechanisms in operation in the 141 specific MANET node. 143 A SMF router's MIB contains SMF process configuration parameters 144 (e.g. specific CDS algorithm), state information (e.g., current 145 membership in the CDS), performance counters (e.g., packet counters), 146 and notifications. 148 4.1. SMF Management Model 150 This section describes the management model for the SMF node process. 152 Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the 153 relationship between the SMF Relay Set selection algorithm and the 154 related algorithms, processes and protocols running in the MANET 155 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 156 topology information gotten from the MANET Neighborhood Discovery 157 Protocol (NHDP), from the specific MANET routing protocol running on 158 the node, or from Layer 2 information passed up to the higher layer 159 protocol processes. 161 ______________ ____________ 162 | | | | 163 | Neighborhood | | Relay Set | 164 | Discovery |------------->| Selection | 165 | Protocol | neighbor | Algorithm | 166 |______________| info |____________| 167 \ / 168 \ / 169 neighbor\ / forwarding 170 info* \ _____________ / status 171 \ | | / 172 `-->| Forwarding |<--' 173 | Process | 174 ----------------->|_____________|-----------------> 175 incoming packet, forwarded packets 176 interface id*, and 177 previous hop* 179 Figure 1: SMF Node Architecture 181 4.2. Terms 183 The following definitions apply throughout this document: 185 o Configuration Objects - switches, tables, objects which are 186 initialized to default settings or set through the management 187 interface defined by this MIB. 189 o Tunable Configuration Objects - objects whose values affect timing 190 or attempt bounds on the SMF RS process. 192 o State Objects - automatically generated values which define the 193 current operating state of the SMF RS process in the router. 195 o Performance Objects - automatically generated values which help an 196 administrator or automated tool to assess the performance of the 197 CDS multicast process on the router and the overall multicasting 198 performance within the MANET routing domain. 200 5. Structure of the MIB Module 202 This section presents the structure of the SMF-MIB module. The 203 objects are arranged into the following groups: 205 o smfMIBNotifications - defines the notifications associated with 206 the SMF-MIB. 208 o smfMIBObjects - defines the objects forming the basis for the SMF- 209 MIB. These objects are divided up by function into the following 210 groups: 212 o 214 * Capabilities Group - This group contains the SMF objects that 215 the device uses to advertise its local capabilities with 216 respect to, e.g., the supported RSSAs. 218 * Configuration Group - This group contains the SMF objects that 219 configure specific options that determine the overall operation 220 of the SMF RSSA and the resulting multicast performance. 222 * State Group - Contains information describing the current state 223 of the SMF RSSA process such as the Neighbor Table. 225 * Performance Group - Contains objects which help to characterize 226 the performance of the SMF RSSA process, typically statistics 227 counters. 229 o smfMIBConformance - defines minimal and full conformance of 230 implementations to this SMF-MIB. 232 5.1. Textual Conventions 234 The textual conventions defined within the SMF-MIB are as follows: 236 o The SmfStatus is defined within the SMF-MIB. This contains the 237 current operational status of the SMF process on an interface. 239 o The SmfOpModeID represents an index that identifies a specific SMF 240 operational mode. 242 o The SmfRssaID represents an index that identifies, through 243 reference, a specific RSSA available for operation on the device. 245 5.2. The Capabilities Group 247 The SMF device supports a set of capabilities. The list of 248 capabilities which the device can advertise are: 250 o Operational Mode - topology information from NHDP, CDS-aware 251 unicast routing or Cross-layer from Layer 2. 253 o SMF RSSA - the specific RSSA operational on the device. Note that 254 configuration, state and performance objects related to a specific 255 RSSA must be defined within another separate MIB. 257 5.3. The Configuration Group 259 The SMF device is configured with a set of controls. Some of the 260 prominent configuration controls for the SMF device follow: 262 o Operational Mode - topology information from NHDP, CDS-aware 263 unicast routing or Cross-layer from Layer 2. 265 o SMF RSSA - the specific RSSA operational on the device. 267 o Duplicate Packet detection for IPv4 - Identification-based or 268 Hash-based DPD. 270 o Duplicate Packet detection for IPv6 - Identification-based or 271 Hash-based DPD. 273 o SMF Type Message TLV - if NHDP mode is selected, then is the SMF 274 Type Message TLV may be included in the NHDP exchanges. 276 o SMF Address Block TLV - if NHDP mode is selected, then is the SMF 277 Address Block TLV should be included in the NHDP exchanges. 279 5.4. The State Group 281 The State Subtree reports current state information, e.g., 283 o Node RSS State - is the node currently in or out of the Relay Set. 285 o Neighbors Table - a table containing current neighbors and their 286 operational RSSA. 288 5.5. The Performance Group 290 The Performance subtree reports primarily counters that relate to SMF 291 RSSA performance. The SMF performance counters consists of per node 292 and per interface objects: 294 o Total multicast packets received. 296 o Total multicast packets forwarded. 298 o Total duplicate multicast packets detected. 300 o Per interface statistics table with the following entries: 302 o 303 * Multicast packets received. 305 * Multicast packets forwarded. 307 * Duplicate multicast packets detected. 309 5.6. The Notifications Group 311 The Notifications Subtree contains the list of notifications 312 supported within the SMF-MIB and their intended purpose or utility. 314 6. Relationship to Other MIB Modules 316 6.1. Relationship to the SNMPv2-MIB 318 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 319 mandatory for all systems, and the objects apply to the entity as a 320 whole. The 'system' group provides identification of the management 321 entity and certain other system-wide data. The SMF-MIB does not 322 duplicate those objects. 324 6.2. MIB modules required for IMPORTS 326 The textual conventions imported for use in the SMF-MIB are as 327 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 328 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 329 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 330 and TruthValue textual conventions are imported from RFC 2579 331 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 332 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 333 InterfaceIndexOrZero textual convention is imported from RFC 2863 334 [RFC2863]. The SnmpAdminString textual convention is imported from 335 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 336 InetAddressPrefixLength textual conventions are imported from RFC 337 4001 [RFC4001]. 339 6.3. Relationship to the Future RSSA-MIBs 341 In a sense, the SMF-MIB is a general front-end to a set of, yet to be 342 developed, RSSA-specific MIBs. These RSSA-specific MIBs will define 343 the objects for the configuration, state, performance and 344 notification objects required for the operation of these specific 345 RSSAs. The SMF-MIB Capabilities Group allows the remote management 346 station the ability to query the router to discover the set of 347 supported RSSAs. 349 7. Definitions 351 MANET-SMF-MIB DEFINITIONS ::= BEGIN 353 IMPORTS 355 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 356 Counter32, Integer32, TimeTicks, experimental 357 FROM SNMPv2-SMI -- [RFC2578] 359 TEXTUAL-CONVENTION, RowStatus, TruthValue, 360 DisplayString 361 FROM SNMPv2-TC -- [RFC2579] 363 MODULE-COMPLIANCE, OBJECT-GROUP, 364 NOTIFICATION-GROUP 365 FROM SNMPv2-CONF -- [RFC2580] 367 InterfaceIndexOrZero 368 FROM IF-MIB -- [RFC2863] 370 SnmpAdminString 371 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 373 InetAddress, InetAddressType, 374 InetAddressPrefixLength 375 FROM INET-ADDRESS-MIB -- [RFC4001] 376 ; 378 manetSmfMIB MODULE-IDENTITY 379 LAST-UPDATED "201205281300Z" -- May 28, 2012 380 ORGANIZATION "IETF MANET Working Group" 381 CONTACT-INFO 382 "WG E-Mail: manet@ietf.org 384 WG Chairs: ian.chakeres@gmail.com 385 jmacker@nrl.navy.mil 387 Editors: Robert G. Cole 388 US Army CERDEC 389 Space and Terrestrial Communications 390 6010 Frankford Road 391 Aberdeen Proving Ground, MD 21005 392 USA 393 +1 443 395-8744 394 robert.g.cole@us.army.mil 395 http://www.cs.jhu.edu/~rgcole/ 397 Joseph Macker 398 Naval Research Laboratory 399 Washington, D.C. 20375 400 USA 401 macker@itd.nrl.navy.mil 403 Brian Adamson 404 Naval Research Laboratory 405 Washington, D.C. 20375 406 USA 407 adamson@itd.nrl.navy.mil 408 " 410 DESCRIPTION 411 "This MIB module contains managed object definitions for 412 the Manet SMF RSSA process defined in: 414 [SMF] Macker, J.(ed.), 415 Simplified Multicast Forwarding draft-ietf-manet-smf-10, 416 March 06, 2010. 418 Copyright (C) The IETF Trust (2008). This version 419 of this MIB module is part of RFC xxxx; see the RFC 420 itself for full legal notices." 422 -- Revision History 423 REVISION "201205281300Z" -- May 28, 2012 424 DESCRIPTION 425 "Updated 7th revision of the 426 draft of this MIB module published as 427 draft-ietf-manet-smf-mib-04.txt. The changes 428 made in this revision include: 429 - Removed the bitmap switch in the notifications 430 control group. 431 - Moved the notification Objects group up 432 to support reverse-mapping between SNMPv1 433 traps and SNMPv2 nootifications. 434 - Removed reference to the notifications 435 state group. 436 - Replaced smfIfIndex with smfIfName in 437 notifications. 438 " 439 REVISION "201110021300Z" -- October 02, 2011 440 DESCRIPTION 441 "Updated 6th revision of the 442 draft of this MIB module published as 443 draft-ietf-manet-smf-mib-03.txt. The changes 444 made in this revision include: 445 - Added some notes to the MIB module 446 - Clarified and defined default settings 447 " 448 REVISION "201101161300Z" -- January 16, 2011 449 DESCRIPTION 450 "Updated 5th revision of the 451 draft of this MIB module published as 452 draft-ietf-manet-smf-mib-02.txt. The changes 453 made in this revision include: 454 - Added the Notification Group and cleaned 455 up the Conformance section 456 - Completed the TEXTUAL CONVENTION for the 457 smfOpMode. 458 - Completed the Description clauses of 459 several objects within the MIB. 460 - Removed the routerPriority object. 461 - Added the definition of a smfRouterID 462 object and associated smfRouterIDAddrType 463 object. 464 " 465 REVISION "200910261300Z" -- October 26, 2009 466 DESCRIPTION 467 "Updated draft of this MIB module published as 468 draft-ietf-manet-smf-mib-01.txt. A few changes 469 were made in the development of this draft. 470 Specifically, the following changes were made: 471 - Updated the textual material, included 472 section on IMPORTS, relationship to other 473 MIBs, etc. 474 " 475 REVISION "200904211300Z" -- April 21, 2009 476 DESCRIPTION 477 "Updated draft of this MIB module published as 478 draft-ietf-manet-smf-mib-00.txt. A few changes 479 were made in the development of this draft. 480 Specifically, the following changes were made: 481 - Removed the smfGatewayFilterTable from this 482 draft. It is a useful construct, e.g., 483 an IPTABLES-MIB, but might best be handled 484 as a seperate MIB and worked within a 485 security focused working group. 486 - Removed the smfReportsGroup. This capability 487 is being replaced with a new and more general 488 method for offline reporting. This is being 489 worked as a new MIB module refered to as the 490 REPORT-MIB. 491 - Rev'd as a new MANET WG document. 492 " 493 REVISION "200902271300Z" -- February 27, 2009 494 DESCRIPTION 495 "Updated draft of this MIB module published as 496 draft-cole-manet-smf-mib-02.txt. Fairly extensive 497 revisions and additions to this MIB were made 498 in this version. Specifically, the following 499 changes were made in development of this version: 500 - added a Capabilities Group within the Objects 501 Group to allow the device to report supported 502 capabilities, e.g., RSSAs supported. 503 - added administrative status objects for device 504 and interfaces 505 - added multicast address forwarding tables, both 506 for configured (within Configuration Group) and 507 discovered (within the State Group). 508 - added additional Performance counters related 509 to DPD functions. 510 - Split up the performance counters into IPv4 511 and IPv6, for both global and per interface 512 statistics. 513 - Split out the reports capability into a seperate 514 Reports Group under the Objects Group. 515 " 516 REVISION "200811031300Z" -- November 03, 2008 517 DESCRIPTION 518 "Updated draft of this MIB module published as 519 draft-cole-manet-smf-mib-01.txt. Added gateway filter 520 table and reports capabilities following rmon." 521 REVISION "200807071200Z" -- July 07, 2008 522 DESCRIPTION 523 "Initial draft of this MIB module published as 524 draft-cole-manet-smf-mib-00.txt." 525 -- RFC-Editor assigns XXXX 526 ::= { experimental 998 } -- to be assigned by IANA 528 -- 529 -- TEXTUAL CONVENTIONs 530 -- 532 SmfStatus ::= TEXTUAL-CONVENTION 533 STATUS current 534 DESCRIPTION 535 "An indication of the operability of a SMF 536 function or feature. For example, the status 537 of an interface: 'enabled' indicates that 538 it is performing SMF functions, 539 and 'disabled' indicates that it is not." 540 SYNTAX INTEGER { 541 enabled (1), 542 disabled (2) 543 } 545 SmfOpModeID ::= TEXTUAL-CONVENTION 546 STATUS current 547 DESCRIPTION 548 "An index that identifies through reference to a specific 549 SMF operations mode. There are basically three styles 550 of SMF operation with reduced relay sets: 552 Independent operation - SMF performs its own relay 553 set selection using information from an associated 554 MANET NHDP process. 556 CDS-aware unicast routing operation - a coexistent 557 unicast routing protocol provides dynamic relay 558 set state based upon its own control plane 559 CDS or neighborhood discovery information. 561 Cross-layer operation - SMF operates using 562 neighborhood status and triggers from a 563 cross-layer information base for dynamic relay 564 set selection and maintenance 565 " 566 SYNTAX INTEGER { 567 independent (1), 568 routing (2), 569 crossLayer (3) 570 -- future (4-255) 571 } 573 SmfRssaID ::= TEXTUAL-CONVENTION 574 STATUS current 575 DESCRIPTION 576 "An index that identifies through reference to a specific 577 RSSA algorithms. Several are currently defined 578 in the appendix of 579 " 580 SYNTAX INTEGER { 581 cF(1), 582 sMPR(2), 583 eCDS(3), 584 mprCDS(4) 585 -- future(5-127) 586 -- noStdAction(128-239) 587 -- experimental(240-255) 588 } 590 -- 591 -- Top-Level Object Identifier Assignments 592 -- 594 smfMIBNotifications OBJECT IDENTIFIER ::= { manetSmfMIB 0 } 595 smfMIBObjects OBJECT IDENTIFIER ::= { manetSmfMIB 1 } 596 smfMIBConformance OBJECT IDENTIFIER ::= { manetSmfMIB 2 } 598 -- 599 -- smfMIBObjects Assignments: 600 -- smfCapabilitiesGroup - 1 601 -- smfConfigurationGroup - 2 602 -- smfStateGroup - 3 603 -- smfPerformanceGroup - 4 604 -- 606 -- 607 -- smfCapabilitiesGroup 608 -- 609 -- This group contains the SMF objects that identify specific 610 -- capabilities within this device related to SMF functions. 611 -- 613 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 615 -- 616 -- SMF Operational Mode Capabilities Table 617 -- 619 smfOpModeCapabilitiesTable OBJECT-TYPE 620 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "The smfOpModeCapabilitiesTable identifies the 625 resident set of SMF Operational Modes on this 626 router. 627 " 629 ::= { smfCapabilitiesGroup 1 } 631 smfOpModeCapabilitiesEntry OBJECT-TYPE 632 SYNTAX SmfOpModeCapabilitiesEntry 633 MAX-ACCESS not-accessible 634 STATUS current 635 DESCRIPTION 636 "Information about a particular operational 637 mode. 638 " 639 INDEX { smfOpModeCapabilitiesID } 640 ::= { smfOpModeCapabilitiesTable 1 } 642 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 643 smfOpModeCapabilitiesID SmfOpModeID, 644 smfOpModeCapabilitiesName SnmpAdminString, 645 smfOpModeCapabilitiesReference SnmpAdminString 646 } 648 smfOpModeCapabilitiesID OBJECT-TYPE 649 SYNTAX SmfOpModeID 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "The index for this entry. This object identifies 654 the particular operational mode for this device. 655 " 656 ::= { smfOpModeCapabilitiesEntry 1 } 658 smfOpModeCapabilitiesName OBJECT-TYPE 659 SYNTAX SnmpAdminString 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "The textual name of this operational 664 mode. Current operational modes include: 665 Independent Mode, CDS-aware Routing Mode, 666 and Cross-layer Mode. Others may be defined 667 in future revisions of [SMF]. 668 " 669 ::= { smfOpModeCapabilitiesEntry 2 } 671 smfOpModeCapabilitiesReference OBJECT-TYPE 672 SYNTAX SnmpAdminString 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "This object contains a reference to the document 677 that defines this operational mode. 678 " 679 ::= { smfOpModeCapabilitiesEntry 3 } 681 -- 682 -- SMF RSSA Capabilities Table 683 -- 685 smfRssaCapabilitiesTable OBJECT-TYPE 686 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "The smfRssaCapabilitiesTable contains 691 reference to the specific set of RSSAs 692 currently supported on this device. 693 " 694 ::= { smfCapabilitiesGroup 2 } 696 smfRssaCapabilitiesEntry OBJECT-TYPE 697 SYNTAX SmfRssaCapabilitiesEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "Information about a particular RSSA 702 algorithm." 703 INDEX { smfRssaCapabilitiesID } 704 ::= { smfRssaCapabilitiesTable 1 } 706 SmfRssaCapabilitiesEntry ::= SEQUENCE { 707 smfRssaCapabilitiesID SmfRssaID, 708 smfRssaCapabilitiesName SnmpAdminString, 709 smfRssaCapabilitiesReference SnmpAdminString 710 } 712 smfRssaCapabilitiesID OBJECT-TYPE 713 SYNTAX SmfRssaID 714 MAX-ACCESS not-accessible 715 STATUS current 716 DESCRIPTION 717 "The index for this entry. This object identifies 718 the particular RSSA algorithm in this MIB 719 module. Example RSSAs are found in the 720 appendix of [SMF]. 722 By default, the agent should support at least the 723 Classical Flooding algorithm. All compliant 724 SMF forwarders must support Classical Flooding. 725 Hence, at least one entry in this table must 726 exist." 727 ::= { smfRssaCapabilitiesEntry 1 } 729 smfRssaCapabilitiesName OBJECT-TYPE 730 SYNTAX SnmpAdminString 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "The textual name of this RSSA algorithm. 735 Currently defined names are: 736 Classical Flooding - cF, 737 Source-based MultiPoint 738 Relay - sMPR, 739 Essential Connecting Dominating 740 Set - eCDS, 741 MultiPoint Relay Connected 742 Dominating Set - mprCDS. 743 " 744 ::= { smfRssaCapabilitiesEntry 2 } 746 smfRssaCapabilitiesReference OBJECT-TYPE 747 SYNTAX SnmpAdminString 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "This object contains a published reference 752 to the document that defines this algorithm. 753 " 754 ::= { smfRssaCapabilitiesEntry 3 } 756 -- 757 -- smfConfigurationGroup 758 -- 759 -- This group contains the SMF objects that configure specific 760 -- options that determine the overall performance and operation 761 -- of the multicast forwarding process for the router device 762 -- and its interfaces. 763 -- 765 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 767 smfAdminStatus OBJECT-TYPE 768 SYNTAX SmfStatus 769 MAX-ACCESS read-write 770 STATUS current 771 DESCRIPTION 772 "The configured status of the SMF process 773 on this device. Enabled(1) means that 774 SMF is configured to run on this device. 775 Disabled(2) mean that the SMF process 776 is configured off. 778 This object is persistent and when written 779 the entity SHOULD save the change to 780 non-volatile storage. 781 " 782 ::= { smfConfigurationGroup 1 } 784 smfRouterIDAddrType OBJECT-TYPE 785 SYNTAX InetAddressType 786 MAX-ACCESS read-write 787 STATUS current 788 DESCRIPTION 789 "The address type of the address used for 790 SMF ID of this router as specified 791 in the 'smfRouterID' next. 793 Only the values ipv4(1) and ipv6(2) 794 are supported. 796 This can be set by the management station, 797 the smfRouterID must be a routable address 798 assigned to this router. If the management 799 station does not assign this value, then the 800 router should choose the highest routable 801 IP address assigned to this router. 803 This object is persistent and when written 804 the entity SHOULD save the change to 805 non-volatile storage. 806 " 807 ::= { smfConfigurationGroup 2 } 809 smfRouterID OBJECT-TYPE 810 SYNTAX InetAddress (SIZE(4|16)) 811 MAX-ACCESS read-write 812 STATUS current 813 DESCRIPTION 814 "The IP address used as the SMF router ID. 815 This can be set by the management station. 816 If not explicitly set, then the device 817 should select a routable IP address 818 assigned to this router for use as 819 the 'smfRouterID'. 821 The smfRouterID is a logical identification 822 that MUST be consistent across interoperating 823 SMF neighborhoods and it is RECOMMENDED to be 824 chosen as the numerically largest address 825 contained in a node's 'Neighbor Address List' 826 as defined in NHDP. A smfRouterID MUST be 827 unique within the scope of the operating 828 MANET network regardless of the method used 829 for selecting it. 831 This object is persistent and when written 832 the entity SHOULD save the change to 833 non-volatile storage. 834 " 835 ::= { smfConfigurationGroup 3 } 837 smfConfiguredOpMode OBJECT-TYPE 838 SYNTAX INTEGER { 839 withNHDP(1), 840 cdsAwareRouting(2), 841 crossLayer(3), 842 other(4) 843 } 844 MAX-ACCESS read-write 845 STATUS current 846 DESCRIPTION 847 "The SMF RSS node operational mode as defined 848 in the TEXTUAL CONVENTION for `SmfOpModeID' 849 and in [SMF].. 851 The value withNHDP(1) indicates Independent 852 Mode of operation. 854 The value cdsAwareRouting(2) indicates 855 CDS-aware Routing Mode of operation. 857 The value crossLayer(3) indicates 858 Cross-layer Mode of operation. 860 The default value for this object is 861 withNHDP(1). 863 This object is persistent and when written 864 the entity SHOULD save the change to 865 non-volatile storage. 866 " 867 DEFVAL { 1 } 868 ::= { smfConfigurationGroup 4 } 870 smfConfiguredRssa OBJECT-TYPE 871 SYNTAX SmfRssaID 872 MAX-ACCESS read-write 873 STATUS current 874 DESCRIPTION 875 "The SMF RSS currently operational algorithm 876 as defined in the TEXTUAL CONVENTION for 877 `SmfRssaID' and in [SMF]. 879 The defluat value for this object is 880 cF(1), i.e., Classical Flooding. 882 This object is persistent and when written 883 the entity SHOULD save the change to 884 non-volatile storage. 885 " 886 DEFVAL { 1 } 887 ::= { smfConfigurationGroup 5 } 889 smfRssaMember OBJECT-TYPE 890 SYNTAX INTEGER { 891 potential(1), 892 always(2), 893 never(3) 894 } 895 MAX-ACCESS read-write 896 STATUS current 897 DESCRIPTION 898 "The RSSA downselects a set of forwarders for 899 multicast forwarding. Sometimes it is useful 900 to force an agent to be included or excluded 901 from the resulting RSS. This object is a 902 switch to allow for this behavior. 904 The value potential(1) allows the selected 905 RSSA to determine if this agent is included 906 or excluded from the RSS. 908 The value always(1) forces the selected 909 RSSA include this agent in the RSS. 911 The value never(3) forces the selected 912 RSSA to exclude this agent from the RSS. 914 The default setting for this object is 915 'potential(1)'. Other settings could pose 916 operational risks under certain conditions. 918 This object is persistent and when written 919 the entity SHOULD save the change to 920 non-volatile storage. 921 " 922 DEFVAL { 1 } 923 ::= { smfConfigurationGroup 6 } 925 smfIpv4Dpd OBJECT-TYPE 926 SYNTAX INTEGER { 927 hashBased(1), 928 identificationBased(2) 929 } 930 MAX-ACCESS read-write 931 STATUS current 932 DESCRIPTION 933 "The current method for IPv4 duplicate packet 934 detection. 936 The value hashBased(1) indicates that the 937 routers duplicate packet detection is based 938 upon comparing a hash over the packet fields. 939 This is the default setting for this object. 941 The value identificationBased(2) 942 indicates that the duplicate packet 943 detection relies upon header information 944 in the multicast packets to identify 945 previously received packets. 947 This object is persistent and when written 948 the entity SHOULD save the change to 949 non-volatile storage. 950 " 951 DEFVAL { 1 } 952 ::= { smfConfigurationGroup 7 } 954 smfIpv6Dpd OBJECT-TYPE 955 SYNTAX INTEGER { 956 hashBased(1), 957 identificationBased(2) 958 } 959 MAX-ACCESS read-write 960 STATUS current 961 DESCRIPTION 962 "The current method for IPv6 duplicate packet 963 detection. 965 The values indicate the type of method used 966 for duplicate packet detection as described 967 the previous description for the object 968 `smfIpv4Dpd'. 970 The default value for this object is 971 hashBased(1). 973 This object is persistent and when written 974 the entity SHOULD save the change to 975 non-volatile storage. 976 " 977 DEFVAL { 1 } 978 ::= { smfConfigurationGroup 8 } 980 smfMaxPktLifetime OBJECT-TYPE 981 SYNTAX Integer32 (0..65535) 982 UNITS "Seconds" 983 MAX-ACCESS read-write 984 STATUS current 985 DESCRIPTION 986 "The estimate of the network packet 987 traversal time. 989 This object is persistent and when written 990 the entity SHOULD save the change to 991 non-volatile storage. 992 " 993 DEFVAL { 60 } 994 ::= { smfConfigurationGroup 9 } 996 smfDpdMaxMemorySize OBJECT-TYPE 997 SYNTAX Integer32 (0..65535) 998 UNITS "Kilo-Bytes" 999 MAX-ACCESS read-write 1000 STATUS current 1001 DESCRIPTION 1002 "The locally reserved memory for storage 1003 of cached DPD records for both IPv4 and 1004 IPv6 methods. 1006 The local SMF device should protect itself 1007 against the SNMP manager from requesting 1008 too large a memory value. If this is the case, 1009 an error indication should be returned in response 1010 to the SNMP SET request. 1012 This object is persistent and when written 1013 the entity SHOULD save the change to 1014 non-volatile storage. 1015 " 1016 DEFVAL { 1024 } 1017 ::= { smfConfigurationGroup 10 } 1019 smfDpdEntryMaxLifetime OBJECT-TYPE 1020 SYNTAX Integer32 (0..65525) 1021 UNITS "Seconds" 1022 MAX-ACCESS read-write 1023 STATUS current 1024 DESCRIPTION 1025 "The maximum lifetime of a cached DPD 1026 record in the local device storage. 1028 If the memory is running low prior to the 1029 MaxLifetimes being exceeded, the local SMF 1030 devices should purge the oldest records first. 1032 This object is persistent and when written 1033 the entity SHOULD save the change to 1034 non-volatile storage. 1035 " 1036 DEFVAL { 600 } 1037 ::= { smfConfigurationGroup 11 } 1039 -- 1040 -- Configuration of messages to be included in 1041 -- NHDP message exchanges in support of SMF 1042 -- operations. 1043 -- 1045 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 1046 SYNTAX TruthValue 1047 MAX-ACCESS read-write 1048 STATUS current 1049 DESCRIPTION 1050 "Indicates whether the associated NHDP messages 1051 include the RSSA Message TLV, or not. This 1052 is an optional SMF operational setting. 1053 The value true(1) indicates that this TLV is 1054 included; the value false(2) indicates that it 1055 is not included. 1057 It is RECOMMENDED that the RSSA Message TLV 1058 be included in the NHDP messages. 1060 This object is persistent and when written 1061 the entity SHOULD save the change to 1062 non-volatile storage. 1063 " 1064 ::= { smfConfigurationGroup 12 } 1066 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 1067 SYNTAX TruthValue 1068 MAX-ACCESS read-write 1069 STATUS current 1070 DESCRIPTION 1071 "Indicates whether the associated NHDP messages 1072 include the RSSA Address Block TLV, or not. 1073 This is an optional SMF operational setting. 1074 The value true(1) indicates that this TLV is 1075 included; the value false(2) indicates that it 1076 is not included. 1078 The smfNhdpRssaAddrBlockTLVIncluded is optional 1079 in all cases as it depends on the existence of 1080 an address block which may not be present. 1081 If this SMF device is configured with NHDP, 1082 then this object should be set to 'true(1)'. 1084 This object is persistent and when written 1085 the entity SHOULD save the change to 1086 non-volatile storage. 1087 " 1088 ::= { smfConfigurationGroup 13 } 1090 -- 1091 -- Table identifying configured multicast addresses to be forwarded. 1092 -- 1094 smfConfiguredAddrForwardingTable OBJECT-TYPE 1095 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 1096 MAX-ACCESS not-accessible 1097 STATUS current 1098 DESCRIPTION 1099 "The (conceptual) table containing information on multicast 1100 addresses which are to be forwarded by the SMF process. 1102 Entries in this table are configured. As well, addresses 1103 to be forwarded by the SMF device can be dynamically 1104 discovered by other means. The corresponding state 1105 table, smfDiscoveredAddrForwardingTable, contains 1106 these additional, dynamically discovered address for 1107 forwarding. 1109 Each row is associated with a range of multicast 1110 addresses, and ranges for different rows must be disjoint. 1112 The objects in this table are persistent and when written 1113 the entity SHOULD save the change to 1114 non-volatile storage. 1115 " 1116 ::= { smfConfigurationGroup 15 } 1118 smfConfiguredAddrForwardingEntry OBJECT-TYPE 1119 SYNTAX SmfConfiguredAddrForwardingEntry 1120 MAX-ACCESS not-accessible 1121 STATUS current 1122 DESCRIPTION 1123 "An entry (conceptual row) containing the information on a 1124 particular multicast scope." 1125 INDEX { smfConfiguredAddrForwardingAddrType, 1126 smfConfiguredAddrForwardingFirstAddr } 1127 ::= { smfConfiguredAddrForwardingTable 1 } 1129 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 1130 smfConfiguredAddrForwardingAddrType InetAddressType, 1131 smfConfiguredAddrForwardingFirstAddr InetAddress, 1132 smfConfiguredAddrForwardingLastAddr InetAddress, 1133 smfConfiguredAddrForwardingStatus RowStatus 1134 } 1136 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 1137 SYNTAX InetAddressType 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "The type of the addresses in the multicast forwarding 1142 range. Legal values correspond to the subset of 1143 address families for which multicast address allocation 1144 is supported. 1146 Only the values ipv4(1) and 1147 ipv6(2) are supported." 1148 ::= { smfConfiguredAddrForwardingEntry 1 } 1149 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 1150 SYNTAX InetAddress (SIZE(4|16)) 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "The first address in the multicast scope range. The type 1155 of this address is determined by the value of the 1156 smfConfiguredAddrForwardingAddrType object." 1157 ::= { smfConfiguredAddrForwardingEntry 2 } 1159 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 1160 SYNTAX InetAddress (SIZE(4|16)) 1161 MAX-ACCESS read-create 1162 STATUS current 1163 DESCRIPTION 1164 "The last address in the multicast scope range. 1165 The type of this address is determined by the 1166 value of the smfConfiguredAddrForwardingAddrType 1167 object." 1168 ::= { smfConfiguredAddrForwardingEntry 3 } 1170 smfConfiguredAddrForwardingStatus OBJECT-TYPE 1171 SYNTAX RowStatus 1172 MAX-ACCESS read-create 1173 STATUS current 1174 DESCRIPTION 1175 "The status of this row, by which new entries may be 1176 created, or old entries deleted from this table. If write 1177 access is supported, the other writable objects in this 1178 table may be modified even while the status is `active'." 1179 ::= { smfConfiguredAddrForwardingEntry 4 } 1181 -- 1182 -- SMF Interfaces Configuration Table 1183 -- 1185 smfInterfaceTable OBJECT-TYPE 1186 SYNTAX SEQUENCE OF SmfInterfaceEntry 1187 MAX-ACCESS not-accessible 1188 STATUS current 1189 DESCRIPTION 1190 "The SMF Interface Table describes the SMF 1191 interfaces that are participating in the 1192 SMF packet forwarding process. The ifIndex is 1193 from the interfaces group defined in the 1194 Interfaces Group MIB. 1196 The objects in this table are persistent 1197 and when written the entity SHOULD save 1198 the change to non-volatile storage. 1199 " 1200 REFERENCE 1201 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1202 K., and F. Kastenholtz, June 2000." 1203 ::= { smfConfigurationGroup 16 } 1205 smfInterfaceEntry OBJECT-TYPE 1206 SYNTAX SmfInterfaceEntry 1207 MAX-ACCESS not-accessible 1208 STATUS current 1209 DESCRIPTION 1210 "The SMF interface entry describes one SMF 1211 interface as indexed by its ifIndex." 1212 INDEX { smfIfIndex } 1213 ::= { smfInterfaceTable 1 } 1215 SmfInterfaceEntry ::= 1216 SEQUENCE { 1217 smfIfIndex InterfaceIndexOrZero, 1218 smfIfName DisplayString, 1219 smfIfAdminStatus SmfStatus, 1220 smfIfRowStatus RowStatus 1221 } 1223 smfIfIndex OBJECT-TYPE 1224 SYNTAX InterfaceIndexOrZero 1225 MAX-ACCESS not-accessible 1226 STATUS current 1227 DESCRIPTION 1228 "The ifIndex for this SMF interface." 1229 ::= { smfInterfaceEntry 1 } 1231 smfIfName OBJECT-TYPE 1232 SYNTAX DisplayString 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "The textual name of the interface. The value of this 1237 object should be the name of the interface as assigned by 1238 the local device and should be suitable for use in commands 1239 entered at the device's `console'. This might be a text 1240 name, such as `le0' or a simple port number, such as `1', 1241 depending on the interface naming syntax of the device. 1243 If there is no local name, or this object is otherwise not 1244 applicable, then this object contains a zero-length string." 1245 ::= { smfInterfaceEntry 2 } 1247 smfIfAdminStatus OBJECT-TYPE 1248 SYNTAX SmfStatus 1249 MAX-ACCESS read-create 1250 STATUS current 1251 DESCRIPTION 1252 "The SMF interface's administrative status. 1253 The value 'enabled' denotes that the interface 1254 is running the SMF forwarding process. 1255 The value 'disabled' denotes that the interface is 1256 external to the SMF forwarding process. 1257 " 1258 ::= { smfInterfaceEntry 3 } 1260 smfIfRowStatus OBJECT-TYPE 1261 SYNTAX RowStatus 1262 MAX-ACCESS read-create 1263 STATUS current 1264 DESCRIPTION 1265 "This object permits management of the table 1266 by facilitating actions such as row creation, 1267 construction, and destruction. The value of 1268 this object has no effect on whether other 1269 objects in this conceptual row can be 1270 modified." 1271 ::= { smfInterfaceEntry 4 } 1273 -- 1274 -- smfStateGroup 1275 -- 1276 -- Contains information describing the current state of the SMF 1277 -- process such as the current inclusion in the RS or not. 1278 -- 1280 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1282 smfNodeRsStatusIncluded OBJECT-TYPE 1283 SYNTAX TruthValue 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "The current status of the SMF node in the context of 1288 the MANETs relay set. A value of true(1) indicates 1289 that the node is currently part of the MANET Relay 1290 Set. A value of false(2) indicates that the node 1291 is currently not part of the MANET Relay Set." 1292 ::= { smfStateGroup 1 } 1294 smfDpdMemoryOverflow OBJECT-TYPE 1295 SYNTAX Counter32 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The number of times that the memory for caching 1300 records for DPD overran and records had to be flushed. 1301 The number of records to be flushed upon a buffer 1302 overflow is an implementation specific decision. 1303 " 1304 ::= { smfStateGroup 2 } 1306 -- 1307 -- Dynamically Discovered Multicast Addr Table 1308 -- 1310 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1311 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1312 MAX-ACCESS not-accessible 1313 STATUS current 1314 DESCRIPTION 1315 "This state table, smfDiscoveredAddrForwardingTable 1316 contains additional, dynamically discovered address 1317 for forwarding. 1319 Each row is associated with a range of 1320 multicast addresses, and ranges for different rows 1321 must be disjoint. 1322 " 1323 ::= { smfStateGroup 3 } 1325 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1326 SYNTAX SmfDiscoveredAddrForwardingEntry 1327 MAX-ACCESS not-accessible 1328 STATUS current 1329 DESCRIPTION 1330 "An entry (conceptual row) containing the information on a 1331 particular multicast scope." 1332 INDEX { smfDiscoveredAddrForwardingAddrType, 1333 smfDiscoveredAddrForwardingFirstAddr } 1334 ::= { smfDiscoveredAddrForwardingTable 1 } 1336 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1337 smfDiscoveredAddrForwardingAddrType InetAddressType, 1338 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1339 smfDiscoveredAddrForwardingLastAddr InetAddress 1340 } 1342 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1343 SYNTAX InetAddressType 1344 MAX-ACCESS not-accessible 1345 STATUS current 1346 DESCRIPTION 1347 "The type of the addresses in the multicast forwarding 1348 range. Legal values correspond to the subset of 1349 address families for which multicast address allocation 1350 is supported. 1352 Only the values ipv4(1) and 1353 ipv6(2) are supported." 1354 ::= { smfDiscoveredAddrForwardingEntry 1 } 1356 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1357 SYNTAX InetAddress (SIZE(4|16)) 1358 MAX-ACCESS not-accessible 1359 STATUS current 1360 DESCRIPTION 1361 "The first address in the multicast scope range. The type 1362 of this address is determined by the value of the 1363 smfConfiguredAddrForwardingAddrType object." 1364 ::= { smfDiscoveredAddrForwardingEntry 2 } 1366 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1367 SYNTAX InetAddress (SIZE(4|16)) 1368 MAX-ACCESS read-create 1369 STATUS current 1370 DESCRIPTION 1371 "The last address in the multicast scope range. 1372 The type of this address is determined by the 1373 value of the smfConfiguredAddrForwardingAddrType 1374 object." 1375 ::= { smfDiscoveredAddrForwardingEntry 3 } 1377 -- 1378 -- SMF Neighbor Table 1379 -- 1381 smfNeighborTable OBJECT-TYPE 1382 SYNTAX SEQUENCE OF SmfNeighborEntry 1383 MAX-ACCESS not-accessible 1384 STATUS current 1385 DESCRIPTION 1386 "The SMF NeighborTable describes the 1387 current neighbor nodes, their address 1388 and SMF RSSA and the interface on which 1389 they can be reached." 1390 REFERENCE 1391 "Simplified Multicast Forwarding for MANET 1392 (SMF), Macker, J., July 2009. 1393 Section 7: SMF Neighborhood Discovery 1394 Requirements." 1395 ::= { smfStateGroup 4 } 1397 smfNeighborEntry OBJECT-TYPE 1398 SYNTAX SmfNeighborEntry 1399 MAX-ACCESS not-accessible 1400 STATUS current 1401 DESCRIPTION 1402 "The SMF Neighbor Table contains the 1403 set of one-hop neighbors, the interface 1404 they are reachable on and the SMF RSSA 1405 they are currently running." 1406 INDEX { smfNeighborIpAddrType, 1407 smfNeighborIpAddr, 1408 smfNeighborPrefixLen } 1409 ::= { smfNeighborTable 1 } 1411 SmfNeighborEntry ::= 1412 SEQUENCE { 1413 smfNeighborIpAddrType InetAddressType, 1414 smfNeighborIpAddr InetAddress, 1415 smfNeighborPrefixLen InetAddressPrefixLength, 1416 smfNeighborRSSA SmfRssaID, 1417 smfNeighborNextHopInterface InterfaceIndexOrZero 1418 } 1420 smfNeighborIpAddrType OBJECT-TYPE 1421 SYNTAX InetAddressType 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "The neighbor IP address type. 1427 Only the values ipv4(1) and 1428 ipv6(2) are supported." 1429 ::= { smfNeighborEntry 1 } 1430 smfNeighborIpAddr OBJECT-TYPE 1431 SYNTAX InetAddress (SIZE(4|16)) 1432 MAX-ACCESS not-accessible 1433 STATUS current 1434 DESCRIPTION 1435 "The neighbor Inet IPv4 or IPv6 address." 1436 ::= { smfNeighborEntry 2 } 1438 smfNeighborPrefixLen OBJECT-TYPE 1439 SYNTAX InetAddressPrefixLength 1440 MAX-ACCESS not-accessible 1441 STATUS current 1442 DESCRIPTION 1443 "The prefix length. This is a decimal value that 1444 indicates the number of contiguous, higher-order 1445 bits of the address that make up the network 1446 portion of the address." 1447 ::= { smfNeighborEntry 3 } 1449 smfNeighborRSSA OBJECT-TYPE 1450 SYNTAX SmfRssaID 1451 MAX-ACCESS read-only 1452 STATUS current 1453 DESCRIPTION 1454 "The current RSSA running on the neighbor. 1455 The list is identical to that described 1456 above for the smfRssa object." 1457 ::= { smfNeighborEntry 4 } 1459 smfNeighborNextHopInterface OBJECT-TYPE 1460 SYNTAX InterfaceIndexOrZero 1461 MAX-ACCESS read-only 1462 STATUS current 1463 DESCRIPTION 1464 "The interface ifIndex over which the 1465 neighbor is reachable in one-hop." 1466 ::= { smfNeighborEntry 5 } 1468 -- 1469 -- SMF Performance Group 1470 -- 1471 -- Contains objects which help to characterize the 1472 -- performance of the SMF RSSA process, such as statistics 1473 -- counters. There are two types of SMF RSSA statistics: 1474 -- global counters and per interface counters. 1476 -- 1478 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1480 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1482 -- 1483 -- IPv4 packet counters 1484 -- 1486 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1487 SYNTAX Counter32 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "A counter of the total number of 1492 multicast IPv4 packets received by the 1493 device." 1494 ::= { smfGlobalPerfGroup 1 } 1496 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1497 SYNTAX Counter32 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "A counter of the total number of 1502 multicast IPv4 packets forwarded by the 1503 device." 1504 ::= { smfGlobalPerfGroup 2 } 1506 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1507 SYNTAX Counter32 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "A counter of the total number of duplicate 1512 multicast IPv4 packets detected by the 1513 device." 1514 ::= { smfGlobalPerfGroup 3 } 1516 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1517 SYNTAX Counter32 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "A counter of the total number of dropped 1522 multicast IPv4 packets by the 1523 device due to TTL exceeded." 1525 ::= { smfGlobalPerfGroup 4 } 1527 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "A counter of the total number of IPv4 packets 1533 recieved which have a TTL larger than that 1534 of a previously received identical packet. 1535 " 1536 ::= { smfGlobalPerfGroup 5 } 1538 -- 1539 -- IPv6 packet counters 1540 -- 1542 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1543 SYNTAX Counter32 1544 MAX-ACCESS read-only 1545 STATUS current 1546 DESCRIPTION 1547 "A counter of the total number of 1548 multicast IPv6 packets received by the 1549 device." 1550 ::= { smfGlobalPerfGroup 6 } 1552 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1553 SYNTAX Counter32 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "A counter of the total number of 1558 multicast IPv6 packets forwarded by the 1559 device." 1560 ::= { smfGlobalPerfGroup 7 } 1562 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1563 SYNTAX Counter32 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "A counter of the total number of duplicate 1568 multicast IPv6 packets detected by the 1569 device." 1570 ::= { smfGlobalPerfGroup 8 } 1572 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1573 SYNTAX Counter32 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "A counter of the total number of dropped 1578 multicast IPv6 packets by the 1579 device due to TTL exceeded." 1580 ::= { smfGlobalPerfGroup 9 } 1582 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1583 SYNTAX Counter32 1584 MAX-ACCESS read-only 1585 STATUS current 1586 DESCRIPTION 1587 "A counter of the total number of IPv6 packets 1588 recieved which have a TTL larger than that 1589 of a previously recived identical packet. 1590 " 1591 ::= { smfGlobalPerfGroup 10 } 1593 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1594 SYNTAX Counter32 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "A counter of the total number of IPv6 packets 1599 recieved which required the HAV assist for DPD. 1600 " 1601 ::= { smfGlobalPerfGroup 11 } 1603 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1604 SYNTAX Counter32 1605 MAX-ACCESS read-only 1606 STATUS current 1607 DESCRIPTION 1608 "A counter of the total number of IPv6 packets 1609 recieved which the device inserted the 1610 DPD header option. 1611 " 1612 ::= { smfGlobalPerfGroup 12 } 1614 -- 1615 -- Per SMF Interface Performance Table 1616 -- 1618 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1619 smfIpv4InterfacePerfTable OBJECT-TYPE 1620 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "The SMF Interface Performance Table 1625 describes the SMF statistics per 1626 interface." 1627 ::= { smfInterfacePerfGroup 1 } 1629 smfIpv4InterfacePerfEntry OBJECT-TYPE 1630 SYNTAX SmfIpv4InterfacePerfEntry 1631 MAX-ACCESS not-accessible 1632 STATUS current 1633 DESCRIPTION 1634 "The SMF Interface Performance entry 1635 describes the statistics for a particular 1636 node interface." 1637 INDEX { smfIpv4IfPerfIfIndex } 1638 ::= { smfIpv4InterfacePerfTable 1 } 1640 SmfIpv4InterfacePerfEntry ::= 1641 SEQUENCE { 1642 smfIpv4IfPerfIfIndex InterfaceIndexOrZero, 1643 smfIpv4MultiPktsRecvPerIf Counter32, 1644 smfIpv4MultiPktsForwardedPerIf Counter32, 1645 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1646 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1647 smfIpv4TTLLargerThanPreviousPerIf Counter32 1648 } 1650 smfIpv4IfPerfIfIndex OBJECT-TYPE 1651 SYNTAX InterfaceIndexOrZero 1652 MAX-ACCESS not-accessible 1653 STATUS current 1654 DESCRIPTION 1655 "The ifIndex for this node interface 1656 that is collecting this set of 1657 performance management statistics." 1658 ::= { smfIpv4InterfacePerfEntry 1 } 1660 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1661 SYNTAX Counter32 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "A counter of the number of 1666 multicast IP packets received by the 1667 device on this interface." 1668 ::= { smfIpv4InterfacePerfEntry 2 } 1670 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1671 SYNTAX Counter32 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "A counter of the number of 1676 multicast IP packets forwarded by the 1677 device on this interface." 1678 ::= { smfIpv4InterfacePerfEntry 3 } 1680 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1681 SYNTAX Counter32 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "A counter of the number of duplicate 1686 multicast IP packets detected by the 1687 device on this interface." 1688 ::= { smfIpv4InterfacePerfEntry 4 } 1690 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1691 SYNTAX Counter32 1692 MAX-ACCESS read-only 1693 STATUS current 1694 DESCRIPTION 1695 "A counter of the total number of dropped 1696 multicast IPv4 packets by the 1697 device due to TTL exceeded." 1698 ::= { smfIpv4InterfacePerfEntry 5 } 1700 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1701 SYNTAX Counter32 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "A counter of the total number of IPv4 packets 1706 recieved which have a TTL larger than that 1707 of a previously recived identical packet. 1708 " 1709 ::= { smfIpv4InterfacePerfEntry 6 } 1711 smfIpv6InterfacePerfTable OBJECT-TYPE 1712 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1713 MAX-ACCESS not-accessible 1714 STATUS current 1715 DESCRIPTION 1716 "The SMF Interface Performance Table 1717 describes the SMF statistics per 1718 interface." 1719 ::= { smfInterfacePerfGroup 2 } 1721 smfIpv6InterfacePerfEntry OBJECT-TYPE 1722 SYNTAX SmfIpv6InterfacePerfEntry 1723 MAX-ACCESS not-accessible 1724 STATUS current 1725 DESCRIPTION 1726 "The SMF Interface Performance entry 1727 describes the statistics for a particular 1728 node interface." 1729 INDEX { smfIpv6IfPerfIfIndex } 1730 ::= { smfIpv6InterfacePerfTable 1 } 1732 SmfIpv6InterfacePerfEntry ::= 1733 SEQUENCE { 1734 smfIpv6IfPerfIfIndex InterfaceIndexOrZero, 1735 smfIpv6MultiPktsRecvPerIf Counter32, 1736 smfIpv6MultiPktsForwardedPerIf Counter32, 1737 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1738 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1739 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1740 smfIpv6HAVAssistsReqdPerIf Counter32, 1741 smfIpv6DpdHeaderInsertionsPerIf Counter32 1742 } 1744 smfIpv6IfPerfIfIndex OBJECT-TYPE 1745 SYNTAX InterfaceIndexOrZero 1746 MAX-ACCESS not-accessible 1747 STATUS current 1748 DESCRIPTION 1749 "The ifIndex for this node interface 1750 that is collecting this set of 1751 performance management statistics. 1753 For packets generated locally at 1754 this node, performance counters 1755 are assigned to the loopback 1756 interface. 1757 " 1758 ::= { smfIpv6InterfacePerfEntry 1 } 1760 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1761 SYNTAX Counter32 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "A counter of the number of 1766 multicast IP packets received by the 1767 device on this interface." 1768 ::= { smfIpv6InterfacePerfEntry 2 } 1770 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1771 SYNTAX Counter32 1772 MAX-ACCESS read-only 1773 STATUS current 1774 DESCRIPTION 1775 "A counter of the number of 1776 multicast IP packets forwarded by the 1777 device on this interface." 1778 ::= { smfIpv6InterfacePerfEntry 3 } 1780 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1781 SYNTAX Counter32 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "A counter of the number of duplicate 1786 multicast IP packets detected by the 1787 device on this interface." 1788 ::= { smfIpv6InterfacePerfEntry 4 } 1790 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1791 SYNTAX Counter32 1792 MAX-ACCESS read-only 1793 STATUS current 1794 DESCRIPTION 1795 "A counter of the number of dropped 1796 multicast IP packets by the 1797 device on this interface due to TTL 1798 exceeded." 1799 ::= { smfIpv6InterfacePerfEntry 5 } 1801 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1802 SYNTAX Counter32 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "A counter of the total number of IPv6 packets 1807 recieved which have a TTL larger than that 1808 of a previously recived identical packet. 1809 " 1811 ::= { smfIpv6InterfacePerfEntry 6 } 1813 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 1814 SYNTAX Counter32 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "A counter of the total number of IPv6 packets 1819 recieved which required the HAV assist for DPD. 1820 " 1821 ::= { smfIpv6InterfacePerfEntry 7 } 1823 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 1824 SYNTAX Counter32 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "A counter of the total number of IPv6 packets 1829 recieved which the device inserted the 1830 DPD header option. 1831 " 1832 ::= { smfIpv6InterfacePerfEntry 8 } 1834 -- 1835 -- Notifications 1836 -- 1838 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 1839 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 1841 -- smfMIBNotifObjects 1843 smfAdminStatusChange NOTIFICATION-TYPE 1844 OBJECTS { smfRouterIDAddrType, -- The originator of 1845 -- the notification. 1846 smfRouterID, -- The originator of 1847 -- the notification. 1848 smfAdminStatus -- The new status of the 1849 -- SMF process. 1850 } 1851 STATUS current 1852 DESCRIPTION 1853 "smfAdminStatusChange is a notification sent when a 1854 the 'smfAdminStatus' object changes. 1855 " 1857 ::= { smfMIBNotifObjects 1 } 1859 smfConfiguredOpModeChange NOTIFICATION-TYPE 1860 OBJECTS { smfRouterIDAddrType, -- The originator of 1861 -- the notification. 1862 smfRouterID, -- The originator of 1863 -- the notification. 1864 smfConfiguredOpMode -- The new Operations 1865 -- Mode of the SMF 1866 -- process. 1867 } 1868 STATUS current 1869 DESCRIPTION 1870 "smfConfiguredOpModeChange is a notification 1871 sent when a the 'smfConfiguredOpMode' object 1872 changes. 1873 " 1874 ::= { smfMIBNotifObjects 2 } 1876 smfConfiguredRssaChange NOTIFICATION-TYPE 1877 OBJECTS { smfRouterIDAddrType, -- The originator of 1878 -- the notification. 1879 smfRouterID, -- The originator of 1880 -- the notification. 1881 smfConfiguredRssa -- The new RSSA for 1882 -- the SMF process. 1883 } 1884 STATUS current 1885 DESCRIPTION 1886 "smfAdminStatusChange is a notification sent when a 1887 the 'smfConfiguredRssa' object changes. 1888 " 1889 ::= { smfMIBNotifObjects 3 } 1891 smfIfAdminStatusChange NOTIFICATION-TYPE 1892 OBJECTS { smfRouterIDAddrType, -- The originator of 1893 -- the notification. 1894 smfRouterID, -- The originator of 1895 -- the notification. 1896 smfIfName, -- The interface whose 1897 -- status has changed. 1898 smfIfAdminStatus -- The new status of the 1899 -- SMF interface. 1900 } 1901 STATUS current 1902 DESCRIPTION 1903 "smfIfAdminStatusChange is a notification sent when a 1904 the 'smfIfAdminStatus' object changes. 1906 " 1907 ::= { smfMIBNotifObjects 4 } 1909 smfDpdMemoryOverflowEvent NOTIFICATION-TYPE 1910 OBJECTS { smfRouterIDAddrType, -- The originator of 1911 -- the notification. 1912 smfRouterID, -- The originator of 1913 -- the notification. 1914 smfDpdMemoryOverflow -- The counter of 1915 -- the overflows. 1916 } 1917 STATUS current 1918 DESCRIPTION 1919 "smfDpdMemoryOverflowEvents is sent when the 1920 number of memory overflow events exceeds the 1921 the 'smfDpdMemoryOverflowThreshold' within the 1922 previous number of seconds defined by the 1923 'smfDpdMemoryOverflowWindow'. 1924 " 1925 ::= { smfMIBNotifObjects 5 } 1927 smfIpv4DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 1928 OBJECTS { smfRouterIDAddrType, -- The originator of 1929 -- the notification. 1930 smfRouterID, -- The originator of 1931 -- the notification. 1932 smfIpv4DuplMultiPktsDetectedTotal 1933 -- The counter of detected 1934 -- duplicates. 1935 } 1936 STATUS current 1937 DESCRIPTION 1938 "smfIpv4DuplMultiPktsDetectedTotal is a 1939 notification sent when the number of 1940 IPv4 duplicate packets detected exceeds the 1941 'smfIpv4DuplMultiPktsDetectedTotalThreshold' 1942 during the previous number of seconds 1943 'smfIpv4DuplPktsDetectedTotalWindow'. 1944 " 1945 ::= { smfMIBNotifObjects 6 } 1947 smfIpv6DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 1948 OBJECTS { smfRouterIDAddrType, -- The originator of 1949 -- the notification. 1950 smfRouterID, -- The originator of 1951 -- the notification. 1952 smfIpv6DuplMultiPktsDetectedTotal 1953 -- The counter of detected 1954 -- duplicates. 1955 } 1956 STATUS current 1957 DESCRIPTION 1958 "smfIpv6DuplMultiPktsDetectedTotal is a 1959 notification sent when the number of 1960 IPv6 duplicate packets detected exceeds the 1961 'smfIpv6DuplMultiPktsDetectedTotalThreshold' 1962 during the previous number of seconds 1963 'smfIpv6DuplPktsDetectedTotalWindow'. 1964 " 1965 ::= { smfMIBNotifObjects 7 } 1967 -- smfMIBNotifControl 1968 smfDpdMemoryOverflowThreshold OBJECT-TYPE 1969 SYNTAX Integer32 (0..255) 1970 MAX-ACCESS read-write 1971 STATUS current 1972 DESCRIPTION 1973 "A threshold value for the 1974 `smfDpdmemoryOverflowEvents' object. 1975 If the number of occurences exceeds 1976 this threshold within the previous 1977 number of seconds 1978 'smfDpdMemoryOverflowWindow', 1979 then the `smfDpdMemoryOverflowEvent' 1980 notification is sent. 1981 " 1982 ::= { smfMIBNotifControl 1 } 1984 smfDpdMemoryOverflowWindow OBJECT-TYPE 1985 SYNTAX TimeTicks 1986 MAX-ACCESS read-write 1987 STATUS current 1988 DESCRIPTION 1989 "A time window value for the 1990 `smfDpdmemoryOverflowEvents' object. 1991 If the number of occurences exceeds 1992 the `smfDpdMemoryOverflowThreshold' 1993 within the previous number of seconds 1994 'smfDpdMemoryOverflowWindow', 1995 then the `smfDpdMemoryOverflowEvent' 1996 notification is sent. 1997 " 1998 ::= { smfMIBNotifControl 2 } 2000 smfIpv4DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 2001 SYNTAX Integer32 (0..255) 2002 MAX-ACCESS read-write 2003 STATUS current 2004 DESCRIPTION 2005 "A threshold value for the 2006 `smfIpv4DuplMultiPktsDetectedTotal' 2007 object. If the number of occurences 2008 exceeds this threshold within the 2009 previous number of seconds 2010 `smfIpv4DuplMultiPktsDetectedTotalWindow', 2011 then the 2012 `smfIpv4DuplMultiPktsDetectedTotalEvent' 2013 notification is sent. 2014 " 2015 ::= { smfMIBNotifControl 3 } 2017 smfIpv4DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 2018 SYNTAX TimeTicks 2019 MAX-ACCESS read-write 2020 STATUS current 2021 DESCRIPTION 2022 "A time window value for the 2023 `smfIpv4DuplMultiPktsDetectedTotalEvents' 2024 object. If the number of occurences 2025 exceeds the 2026 `smfIpv4DuplMultiPktsDetectedTotalThreshold' 2027 within the previous number of seconds 2028 'smfIpv4DuplMultiPktsDetectedTotalWindow', 2029 then the 2030 `smfIpv4DuplMultiPktsDetectedTotalEvent' 2031 notification is sent. 2032 " 2033 ::= { smfMIBNotifControl 4 } 2035 smfIpv6DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 2036 SYNTAX Integer32 (0..255) 2037 MAX-ACCESS read-write 2038 STATUS current 2039 DESCRIPTION 2040 "A threshold value for the 2041 `smfIpv6DuplMultiPktsDetectedTotal' 2042 object. If the number of occurences 2043 exceeds this threshold within the 2044 previous number of seconds 2045 `smfIpv6DuplMultiPktsDetectedTotalWindow', 2046 then the 2047 `smfIpv6DuplMultiPktsDetectedTotalEvent' 2048 notification is sent. 2049 " 2050 ::= { smfMIBNotifControl 5 } 2052 smfIpv6DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 2053 SYNTAX TimeTicks 2054 MAX-ACCESS read-write 2055 STATUS current 2056 DESCRIPTION 2057 "A time window value for the 2058 `smfIpv6DuplMultiPktsDetectedTotalEvents' 2059 object. If the number of occurences 2060 exceeds the 2061 `smfIpv6DuplMultiPktsDetectedTotalThreshold' 2062 within the previous number of seconds 2063 'smfIpv6DuplMultiPktsDetectedTotalWindow', 2064 then the 2065 `smfIpv6DuplMultiPktsDetectedTotalEvent' 2066 notification is sent. 2067 " 2068 ::= { smfMIBNotifControl 6 } 2070 -- 2071 -- Compliance Statements 2072 -- 2074 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2075 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2077 smfBasicCompliance MODULE-COMPLIANCE 2078 STATUS current 2079 DESCRIPTION "The basic implementation requirements for 2080 managed network entities that implement 2081 the SMF RSSA process." 2082 MODULE -- this module 2083 MANDATORY-GROUPS { smfCapabObjectsGroup, 2084 smfConfigObjectsGroup } 2085 ::= { smfCompliances 1 } 2087 smfFullCompliance MODULE-COMPLIANCE 2088 STATUS current 2089 DESCRIPTION "The full implementation requirements for 2090 managed network entities that implement 2091 the SMF RSSA process." 2092 MODULE -- this module 2093 MANDATORY-GROUPS { smfCapabObjectsGroup, 2094 smfConfigObjectsGroup, 2095 smfStateObjectsGroup, 2096 smfPerfObjectsGroup, 2097 smfNotifObjectsGroup, 2098 smfNotificationsGroup 2099 } 2100 ::= { smfCompliances 2 } 2102 -- 2103 -- Units of Conformance 2104 -- 2106 smfCapabObjectsGroup OBJECT-GROUP 2107 OBJECTS { 2108 smfOpModeCapabilitiesName, 2109 smfOpModeCapabilitiesReference, 2111 smfRssaCapabilitiesName, 2112 smfRssaCapabilitiesReference 2113 } 2114 STATUS current 2115 DESCRIPTION 2116 "Set of SMF configuration objects implemented 2117 in this module." 2118 ::= { smfMIBGroups 1 } 2120 smfConfigObjectsGroup OBJECT-GROUP 2121 OBJECTS { 2122 smfAdminStatus, 2123 smfRouterIDAddrType, 2124 smfRouterID, 2125 smfIfName, 2126 smfConfiguredOpMode, 2127 smfConfiguredRssa, 2128 smfRssaMember, 2129 smfIpv4Dpd, 2130 smfIpv6Dpd, 2131 smfMaxPktLifetime, 2132 smfDpdMaxMemorySize, 2133 smfDpdEntryMaxLifetime, 2134 smfNhdpRssaMesgTLVIncluded, 2135 smfNhdpRssaAddrBlockTLVIncluded, 2137 smfConfiguredAddrForwardingLastAddr, 2138 smfConfiguredAddrForwardingStatus, 2140 smfIfAdminStatus, 2141 smfIfRowStatus 2142 } 2143 STATUS current 2144 DESCRIPTION 2145 "Set of SMF configuration objects implemented 2146 in this module." 2147 ::= { smfMIBGroups 2 } 2149 smfStateObjectsGroup OBJECT-GROUP 2150 OBJECTS { 2151 smfNodeRsStatusIncluded, 2152 smfDpdMemoryOverflow, 2154 smfDiscoveredAddrForwardingLastAddr, 2156 smfNeighborRSSA, 2157 smfNeighborNextHopInterface 2158 } 2159 STATUS current 2160 DESCRIPTION 2161 "Set of SMF state objects implemented 2162 in this module." 2163 ::= { smfMIBGroups 3 } 2165 smfPerfObjectsGroup OBJECT-GROUP 2166 OBJECTS { 2167 smfIpv4MultiPktsRecvTotal, 2168 smfIpv4MultiPktsForwardedTotal, 2169 smfIpv4DuplMultiPktsDetectedTotal, 2170 smfIpv4DroppedMultiPktsTTLExceededTotal, 2171 smfIpv4TTLLargerThanPreviousTotal, 2173 smfIpv6MultiPktsRecvTotal, 2174 smfIpv6MultiPktsForwardedTotal, 2175 smfIpv6DuplMultiPktsDetectedTotal, 2176 smfIpv6DroppedMultiPktsTTLExceededTotal, 2177 smfIpv6TTLLargerThanPreviousTotal, 2178 smfIpv6HAVAssistsReqdTotal, 2179 smfIpv6DpdHeaderInsertionsTotal, 2181 smfIpv4MultiPktsRecvPerIf, 2182 smfIpv4MultiPktsForwardedPerIf, 2183 smfIpv4DuplMultiPktsDetectedPerIf, 2184 smfIpv4DroppedMultiPktsTTLExceededPerIf, 2185 smfIpv4TTLLargerThanPreviousPerIf, 2187 smfIpv6MultiPktsRecvPerIf, 2188 smfIpv6MultiPktsForwardedPerIf, 2189 smfIpv6DuplMultiPktsDetectedPerIf, 2190 smfIpv6DroppedMultiPktsTTLExceededPerIf, 2191 smfIpv6TTLLargerThanPreviousPerIf, 2192 smfIpv6HAVAssistsReqdPerIf, 2193 smfIpv6DpdHeaderInsertionsPerIf 2194 } 2195 STATUS current 2196 DESCRIPTION 2197 "Set of SMF performance objects implemented 2198 in this module by total and per interface." 2199 ::= { smfMIBGroups 4 } 2201 smfNotifObjectsGroup OBJECT-GROUP 2202 OBJECTS { 2203 smfDpdMemoryOverflowThreshold, 2204 smfDpdMemoryOverflowWindow, 2205 smfIpv4DuplMultiPktsDetectedTotalThreshold, 2206 smfIpv4DuplMultiPktsDetectedTotalWindow, 2207 smfIpv6DuplMultiPktsDetectedTotalThreshold, 2208 smfIpv6DuplMultiPktsDetectedTotalWindow 2209 } 2210 STATUS current 2211 DESCRIPTION 2212 "Set of SMF notification control 2213 objects implemented in this module." 2214 ::= { smfMIBGroups 5 } 2216 smfNotificationsGroup NOTIFICATION-GROUP 2217 NOTIFICATIONS { 2218 smfAdminStatusChange, 2219 smfConfiguredOpModeChange, 2220 smfConfiguredRssaChange, 2221 smfIfAdminStatusChange, 2222 smfDpdMemoryOverflowEvent, 2223 smfIpv4DuplMultiPktsDetectedTotalEvents, 2224 smfIpv6DuplMultiPktsDetectedTotalEvents 2225 } 2226 STATUS current 2227 DESCRIPTION 2228 "Set of SMF notifications implemented 2229 in this module." 2230 ::= { smfMIBGroups 6 } 2232 END 2234 8. Security Considerations 2236 This section discusses security implications of the choices made in 2237 this SMF-MIB module. 2239 There are a number of management objects defined in this MIB module 2240 with a MAX-ACCESS clause of read-write and/or read-create. Such 2241 objects may be considered sensitive or vulnerable in some network 2242 environments. The support for SET operations in a non-secure 2243 environment without proper protection can have a negative effect on 2244 network operations. These are the tables and objects and their 2245 sensitivity/vulnerability: 2247 o 'smfAdminStatus' - this writable configuration object controls the 2248 operational status of the SMF process. If this setting is 2249 configured inconsistently across the MANET multicasting domain, 2250 then delivery of multicast data may be inconsistent across the 2251 domain; some nodes may not receive multicast data intended for 2252 them. 2254 o 'smfRouterIDAddrType' and 'smfRouterID' - these writable 2255 configuration objects define the ID of the SMF process. These 2256 objects should be configured with a routable address defined on 2257 the local SMF device. The smfRouterID is a logical identification 2258 that MUST be consistent across interoperating SMF neighborhoods 2259 and it is RECOMMENDED to be chosen as the numerically largest 2260 address contained in a node's 'Neighbor Address List' as defined 2261 in NHDP. A smfRouterID MUST be unique within the scope of the 2262 operating MANET network regardless of the method used for 2263 selecting it. 2265 o 'smfConfiguredOpMode' - this writable configuration objects define 2266 the operational mode of the SMF process. The operational mode 2267 defines how the SMF process develops its local estimate of the 2268 CDS. 2270 o 'smfConfiguredRssa' - this writable configuration object sets the 2271 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2272 process. If this object is set inconsistently across the MANET 2273 domain, multicast delivery of data will fail. 2275 o 'smfRssaMember' - this writable configuration object sets the 2276 'interest' of the local SMF node in participating in the CDS. 2277 Setting this object to 'never(3)' on a highly highly connected 2278 device could lead to frequent island formation. Setting this 2279 object to 'always(2)' could support data ex-filtration from the 2280 MANET domain. 2282 o 'smfIpv4Dpd' - this writable configuration object sets the 2283 duplicate packet detection method for forwarding of IPv4 multicast 2284 packets. 2286 o 'smfIpv6Dpd' - this writable configuration object sets the 2287 duplicate packet detection method for forwarding of IPv6 multicast 2288 packets. 2290 o 'smfMaxPktLifetime' - this writable configuration object sets the 2291 estimate of the network packet traversal time. If set too small, 2292 this could lead to poor multicast data delivery ratios throughout 2293 the MANET domain. 2295 o 'smfDpdMaxMemorySize' - this writable configuration object sets 2296 the memory storage size (in Kilo-Bytes) for the cached DPD records 2297 for the combined IPv4 and IPv6 methods. If set too small this 2298 could lead to poor performance of the duplicate packet protection 2299 algorithms and lead to inefficient resource, e.g., link, 2300 utilization within the MANET domain. The local SMF device should 2301 protect itself against memory overruns in the event that too large 2302 a setting is requested. 2304 o 'smfDpdEntryMaxLifetime' - this writable configuration object sets 2305 the maximum lifetime (in seconds) for the cached DPD records for 2306 the combined IPv4 and IPv6 methods. If the memory is running low 2307 prior to the MaxLifetimes being exceeded, the local SMF devices 2308 should purge the oldest records first. 2310 o 'smfNhdpRssaMesgTLVIncluded' - this writable configuration object 2311 indicates whether the associated NHDP messages include the the 2312 RSSA Message TLV, or not. It is highly RECOMMENDED that this 2313 object be set to 'true(1)'. 2315 o 'smfNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2316 object indicates whether the associated NHDP messages include the 2317 the RSSA Address Block TLV, or not. The 2318 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2319 depends on the existence of an address block which may not be 2320 present. If this SMF device is configured with NHDP, then this 2321 object should be set to 'true(1)'. 2323 o 'smfConfiguredAddrForwardingTable' - the writable configuration 2324 objects in this table indicate which multicast IP address are to 2325 be forwarded by this SMF node. Misconfiguration of rows within 2326 this table can limit the ability of this SMF device to forward 2327 multicast data. 2329 o 'smfInterfaceTable' - the writable configuration objects in this 2330 table indicate which SMF node interfaces are participating in the 2331 SMF packet forwarding process. Misconfiguration of rows within 2332 this table can limit the ability of this SMF device to forward 2333 multicast data. 2335 Some of the readable objects in this MIB module (i.e., objects with a 2336 MAX-ACCESS other than not-accessible) may be considered sensitive or 2337 vulnerable in some network environments. It is thus important to 2338 control even GET and/or NOTIFY access to these objects and possibly 2339 to even encrypt the values of these objects when sending them over 2340 the network via SNMP. These are the tables and objects and their 2341 sensitivity/vulnerability: 2343 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2344 that this SMF node is part of the CDS, or not. Being part of the 2345 CDS makes this node a distinguished device. It could be exploited 2346 for data ex-filtration, or denial of service attacks. 2348 o 'smfDiscoveredAddrForwardingTable' - the readable state objects in 2349 this table indicate which, dynamically discovered, multicast IP 2350 address are to be forwarded by this SMF node. 2352 o 'smfNeighborTable' - the readable state objects in this table 2353 indicate current neighbor nodes to this SMF node. Exposing this 2354 information to an attacker could allow the attacker easier access 2355 to the larger MANET domain. 2357 The remainder of the objects in the SMF-MIB are performance counter 2358 objects. While these give an indication of the activity of the SMF 2359 process on this node, it is not expected that exposing these values 2360 pose a security risk to the MANET network. 2362 SNMP versions prior to SNMPv3 did not include adequate security. 2363 Even if the network itself is secure (for example by using IPSec), 2364 even then, there is no control as to who on the secure network is 2365 allowed to access and GET/SET (read/change/create/delete) the objects 2366 in this MIB module. 2368 Implementations MUST provide the security features described by the 2369 SNMPv3 framework (see [RFC3410] ), including full support for 2370 authentication and privacy via the User-based Security Model (USM) 2371 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2372 MAY also provide support for the Transport Security Model (TSM) 2373 [RFC5591] in combination with a secure transport such as SSH 2374 [RFC5592] or TLS/DTLS [RFC6353]. 2376 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2377 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2378 enable cryptographic security. It is then a customer/operator 2379 responsibility to ensure that the SNMP entity giving access to an 2380 instance of this MIB module is properly configured to give access to 2381 the objects only to those principals (users) that have legitimate 2382 rights to indeed GET or SET (change/create/delete) them. 2384 9. IANA Considerations 2386 Editor's Note (to be removed prior to publication): the IANA is 2387 requested to assign a value for "XXXX" under the 'experimental' 2388 subtree and to record the assignment in the SMI Numbers registry. 2389 When the assignment has been made, the RFC Editor is asked to replace 2390 "XXXX" (here and in the MIB module) with the assigned value and to 2391 remove this note. Note well: prior to official assignment by the 2392 IANA, a draft document MUST use placeholders (such as "XXXX" above) 2393 rather than actual numbers. See RFC4181 Section 4.5 for an example 2394 of how this is done in a draft MIB module. 2396 10. Contributors 2398 This MIB document uses the template authored by D. Harrington which 2399 is based on contributions from the MIB Doctors, especially Juergen 2400 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2402 11. Acknowledgements 2404 The authors would like to acknowledge the valuable comments from Sean 2405 Harnedy in the early phases of the development of this MIB-module. 2407 12. References 2409 12.1. Normative References 2411 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 2412 Interfaces Group MIB", RFC 2863, June 2000. 2414 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2415 Architecture for Describing Simple Network 2416 Management Protocol (SNMP) Management 2417 Frameworks", STD 62, RFC 3411, December 2002. 2419 [RFC3418] Presuhn, R., "Management Information Base (MIB) 2420 for the Simple Network Management Protocol 2421 (SNMP)", STD 62, RFC 3418, December 2002. 2423 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2424 Schoenwaelder, "Textual Conventions for 2425 Internet Network Addresses", RFC 4001, 2426 February 2005. 2428 [RFC2119] Bradner, S., "Key words for use in RFCs to 2429 Indicate Requirement Levels", BCP 14, RFC 2119, 2430 March 1997. 2432 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2433 Schoenwaelder, Ed., "Structure of Management 2434 Information Version 2 (SMIv2)", STD 58, 2435 RFC 2578, April 1999. 2437 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2438 Schoenwaelder, Ed., "Textual Conventions for 2439 SMIv2", STD 58, RFC 2579, April 1999. 2441 [RFC2580] McCloghrie, K., Perkins, D., and J. 2442 Schoenwaelder, "Conformance Statements for 2443 SMIv2", STD 58, RFC 2580, April 1999. 2445 [I-D.ietf-manet-smf] Macker, J., "Simplified Multicast Forwarding", 2446 draft-ietf-manet-smf-14 (work in progress), 2447 March 2012. 2449 12.2. Informative References 2451 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 2452 Stewart, "Introduction and Applicability 2453 Statements for Internet-Standard Management 2454 Framework", RFC 3410, December 2002. 2456 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based 2457 Security Model (USM) for version 3 of the 2458 Simple Network Management Protocol (SNMPv3)", 2459 STD 62, RFC 3414, December 2002. 2461 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, 2462 "The Advanced Encryption Standard (AES) Cipher 2463 Algorithm in the SNMP User-based Security 2464 Model", RFC 3826, June 2004. 2466 [RFC5591] Harrington, D. and W. Hardaker, "Transport 2467 Security Model for the Simple Network 2468 Management Protocol (SNMP)", RFC 5591, 2469 June 2009. 2471 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, 2472 "Secure Shell Transport Model for the Simple 2473 Network Management Protocol (SNMP)", RFC 5592, 2474 June 2009. 2476 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) 2477 Transport Model for the Simple Network 2478 Management Protocol (SNMP)", RFC 6353, 2479 July 2011. 2481 Appendix A. Change Log 2483 This section tracks the revision history in the development of this 2484 SMF-MIB. It will be removed from the final version of this document. 2486 These changes were made from draft-ietf-manet-smf-mib-03 to 2487 draft-ietf-manet-smf-mib-04. 2489 1. Removed the bitmap switch in the notifications control group. 2491 2. Moved the notification Objects group up to support reverse- 2492 mapping between SNMPv1 traps and SNMPv2 nootifications. 2494 3. Removed reference to the notifications state group. 2496 4. Replaced smfIfIndex with smfIfName in notifications. 2498 These changes were made from draft-ietf-manet-smf-mib-02 to 2499 draft-ietf-manet-smf-mib-03. 2501 1. Clarified and added discussion of default values for several of 2502 the configuration objects within the MIB. 2504 2. Added the security section. 2506 These changes were made from draft-ietf-manet-smf-mib-01 to 2507 draft-ietf-manet-smf-mib-02. 2509 1. Added the NotificationGroup to the MIB and updated the 2510 ConformanceGroup. 2512 2. Added the definition of an smfRouterID to the MIB. This is later 2513 used in the Notifications to indicate the origin of the event to 2514 the management station. 2516 3. Removed the Router Priority object as this was used only in the 2517 eCDS algorithm and hence should be contained within the future 2518 eCDS-MIB. 2520 4. Cleaned up the TEXTUAL CONVENTION for the `SmfOpMode'. 2522 5. Filled in some of the missing text in various object 2523 descriptions. 2525 These changes were made from draft-ietf-manet-smf-mib-00 to 2526 draft-ietf-manet-dsmf-mib-01. 2528 1. Editorial changes to the textual material. These included the 2529 addition of the paragraphs on TEXTUAL-CONVENTIONS defined and 2530 imported into this MIB and relationships to other MIBs. 2532 2. Identified those objects in the SMF-MIB requiring non-volatile 2533 storage. 2535 3. Changed the name of the TEXTUAL-CONVENTION 'Status', defined 2536 within this MIB to 'SmfStatus'. 2538 Appendix B. Open Issues 2540 This section contains the set of open issues related to the 2541 development and design of the SMF-MIB. This section will not be 2542 present in the final version of the MIB and will be removed once all 2543 the open issues have been resolved. 2545 1. A careful review by the working group. 2547 Appendix C. 2549 *************************************************************** 2550 * Note to the RFC Editor (to be removed prior to publication) * 2551 * * 2552 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2553 * of the MIB module point to this draft and are to be * 2554 * assigned by the RFC Editor. * 2555 * * 2556 * 2) The reference to RFCXXX2 throughout this document point * 2557 * to the current draft-ietf-manet-smf-xx.txt. This * 2558 * need to be replaced with the XXX RFC number. * 2559 * * 2560 *************************************************************** 2562 Authors' Addresses 2564 Robert G. Cole 2565 US Army CERDEC 2566 6010 Frankford Road 2567 Aberdeen Proving Ground, Maryland 21005 2568 USA 2570 Phone: +1 443 395 8744 2571 EMail: robert.g.cole@us.army.mil 2572 URI: http://www.cs.jhu.edu/~rgcole/ 2574 Joseph Macker 2575 Naval Research Laboratory 2576 Washington, D.C. 20375 2577 USA 2579 EMail: macker@itd.nrl.navy.mil 2581 Brian Adamson 2582 Naval Research Laboratory 2583 Washington, D.C. 20375 2584 USA 2586 EMail: adamson@itd.nrl.navy.mil