idnits 2.17.1 draft-ietf-manet-smf-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (January 16, 2011) is 4820 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) == Missing Reference: 'TODO' is mentioned on line 2284, but not defined == Missing Reference: 'SMF' is mentioned on line 851, but not defined == Missing Reference: 'TODOs' is mentioned on line 2425, but not defined == Outdated reference: A later version (-14) exists of draft-ietf-manet-smf-10 ** Downref: Normative reference to an Experimental draft: draft-ietf-manet-smf (ref. 'I-D.ietf-manet-smf') Summary: 1 error (**), 0 flaws (~~), 6 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: Standards Track J. Macker 5 Expires: July 20, 2011 B. Adamson 6 Naval Research Laboratory 7 S. Harnedy 8 Booz Allen Hamilton 9 January 16, 2011 11 Definition of Managed Objects for the Manet Simplified Multicast 12 Framework Relay Set Process 13 draft-ietf-manet-smf-mib-02 15 Abstract 17 This memo defines a portion of the Management Information Base (MIB) 18 for use with network management protocols in the Internet community. 19 In particular, it describes objects for configuring aspects of the 20 Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc 21 Networks (MANETs). The SMF-MIB also reports state information, 22 performance metrics, and notifications. In addition to 23 configuration, the additional state and performance information is 24 useful to operators troubleshooting multicast forwarding problems. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on July 20, 2011. 43 Copyright Notice 45 Copyright (c) 2011 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. The Internet-Standard Management Framework . . . . . . . . . . 3 62 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 65 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 67 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 68 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 69 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 70 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 71 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 72 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 73 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 74 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 75 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 76 6.3. Relationship to the Future RSSA-MIBs . . . . . . . . . . . 8 77 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 78 8. Security Considerations . . . . . . . . . . . . . . . . . . . 48 79 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 80 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 50 81 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50 82 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 83 12.1. Normative References . . . . . . . . . . . . . . . . . . . 50 84 12.2. Informative References . . . . . . . . . . . . . . . . . . 51 85 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 51 86 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 52 87 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 53 89 1. Introduction 91 This memo defines a portion of the Management Information Base (MIB) 92 for use with network management protocols in the Internet community. 93 In particular, it describes objects for configuring aspects of a 94 process implementing Simplified Multicast Forwarding (SMF) 95 [I-D.ietf-manet-smf] for Mobile Ad-Hoc Networks (MANETs). SMF 96 provides multicast Duplicate Packet Detection (DPD) and supports 97 algorithms for constructing an estimate of a MANET Minimum Connected 98 Dominating Set (MCDS) for efficient multicast forwarding. The SMF- 99 MIB also reports state information, performance metrics, and 100 notifications. In addition to configuration, this additional state 101 and performance information is useful to operators troubleshooting 102 multicast forwarding problems. 104 2. The Internet-Standard Management Framework 106 For a detailed overview of the documents that describe the current 107 Internet-Standard Management Framework, please refer to section 7 of 108 RFC 3410 [RFC3410]. 110 Managed objects are accessed via a virtual information store, termed 111 the Management Information Base or MIB. MIB objects are generally 112 accessed through the Simple Network Management Protocol (SNMP). 113 Objects in the MIB are defined using the mechanisms defined in the 114 Structure of Management Information (SMI). This memo specifies a MIB 115 module that is compliant to the SMIv2, which is described in STD 58, 116 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 117 [RFC2580]. 119 3. Conventions 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 4. Overview 127 SMF provides methods for implementing DPD-based multicast forwarding 128 with the optional use of Connected Dominating Set (CDS)-based relay 129 sets. The CDS provides a complete connected coverage of the nodes 130 comprising the MANET. The MCDS is the smallest set of MANET nodes 131 (comprising a connected cluster) which cover all the nodes in the 132 cluster with their transmissions. As the density of the MANET nodes 133 increase, the fraction of nodes required in an MCDS decreases. Using 134 the MCDS as a multicast forwarding set then becomes an efficient 135 multicast mechanism for MANETs. 137 Various algorithms for the construction of estimates of the MCDS 138 exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] 139 describes some of these. It further defines various operational 140 modes for a node which is participating in the collective creation of 141 the MCDS estimates. These modes depend upon the set of related MANET 142 routing and discovery protocols and mechanisms in operation in the 143 specific MANET node. 145 A SMF router's MIB contains SMF process configuration parameters 146 (e.g. specific CDS algorithm), state information (e.g., current 147 membership in the CDS), performance counters (e.g., packet counters), 148 and notifications. 150 4.1. SMF Management Model 152 This section describes the management model for the SMF node process. 154 Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the 155 relationship between the SMF Relay Set selection algorithm and the 156 related algorithms, processes and protocols running in the MANET 157 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 158 topology information gotten from the MANET Neighborhood Discovery 159 Protocol (NHDP), from the specific MANET routing protocol running on 160 the node, or from Layer 2 information passed up to the higher layer 161 protocol processes. 163 RGC Note: update this figure from the latest SMF draft. 165 ______________ ____________ 166 | | | | 167 | Neighborhood | | Relay Set | 168 | Discovery |------------->| Selection | 169 | Protocol | neighbor | Algorithm | 170 |______________| info |____________| 171 \ / 172 \ / 173 neighbor\ / forwarding 174 info* \ _____________ / status 175 \ | | / 176 `-->| Forwarding |<--' 177 | Process | 178 ----------------->|_____________|-----------------> 179 incoming packet, forwarded packets 180 interface id*, and 181 previous hop* 183 Figure 1: SMF Node Architecture 185 4.2. Terms 187 The following definitions apply throughout this document: 189 o Configuration Objects - switches, tables, objects which are 190 initialized to default settings or set through the management 191 interface defined by this MIB. 193 o Tunable Configuration Objects - objects whose values affect timing 194 or attempt bounds on the SMF RS process. 196 o State Objects - automatically generated values which define the 197 current operating state of the SMF RS process in the router. 199 o Performance Objects - automatically generated values which help an 200 administrator or automated tool to assess the performance of the 201 CDS multicast process on the router and the overall multicasting 202 performance within the MANET routing domain. 204 5. Structure of the MIB Module 206 This section presents the structure of the SMF-MIB module. The 207 objects are arranged into the following groups: 209 o smfMIBNotifications - defines the notifications associated with 210 the SMF-MIB. 212 o smfMIBObjects - defines the objects forming the basis for the SMF- 213 MIB. These objects are divided up by function into the following 214 groups: 216 o 218 * Capabilities Group - This group contains the SMF objects that 219 the device uses to advertise its local capabilities with 220 respect to, e.g., the supported RSSAs. 222 * Configuration Group - This group contains the SMF objects that 223 configure specific options that determine the overall operation 224 of the SMF RSSA and the resulting multicast performance. 226 * State Group - Contains information describing the current state 227 of the SMF RSSA process such as the Neighbor Table. 229 * Performance Group - Contains objects which help to characterize 230 the performance of the SMF RSSA process, typically statistics 231 counters. 233 o smfMIBConformance - defines minimal and full conformance of 234 implementations to this SMF-MIB. 236 5.1. Textual Conventions 238 The textual conventions defined within the SMF-MIB are as follows: 240 o The SmfStatus is defined within the SMF-MIB. This contains the 241 current operational status of the SMF process on an interface. 243 o The SmfOpModeID represents an index that identifies a specific SMF 244 operational mode. 246 o The SmfRssaID represents an index that identifies, through 247 reference, a specific RSSA available for operation on the device. 249 5.2. The Capabilities Group 251 The SMF device supports a set of capabilities. The list of 252 capabilities which the device can advertise are: 254 o Operational Mode - topology information from NHDP, CDS-aware 255 unicast routing or Cross-layer from Layer 2. 257 o SMF RSSA - the specific RSSA operational on the device. Note that 258 configuration, state and performance objects related to a specific 259 RSSA must be defined within another separate MIB. 261 5.3. The Configuration Group 263 The SMF device is configured with a set of controls. Some of the 264 prominent configuration controls for the SMF device follow: 266 o Operational Mode - topology information from NHDP, CDS-aware 267 unicast routing or Cross-layer from Layer 2. 269 o SMF RSSA - the specific RSSA operational on the device. 271 o Duplicate Packet detection for IPv4 - Identification-based or 272 Hash-based DPD. 274 o Duplicate Packet detection for IPv6 - Identification-based or 275 Hash-based DPD. 277 o SMF Type Message TLV - if NHDP mode is selected, then is the SMF 278 Type Message TLV may be included in the NHDP exchanges. 280 o SMF Address Block TLV - if NHDP mode is selected, then is the SMF 281 Address Block TLV included in the NHDP exchanges. (Note: is this 282 correct?) 284 5.4. The State Group 286 The State Subtree reports current state information, e.g., 288 o Node RSS State - is the node currently in or out of the Relay Set. 290 o Neighbors Table - a table containing current neighbors and their 291 operational RSSA. 293 5.5. The Performance Group 295 The Performance subtree reports primarily counters that relate to SMF 296 RSSA performance. The SMF performance counters consists of per node 297 and per interface objects: 299 o Total multicast packets received. 301 o Total multicast packets forwarded. 303 o Total duplicate multicast packets detected. 305 o Per interface statistics table with the following entries: 307 o 308 * Multicast packets received. 310 * Multicast packets forwarded. 312 * Duplicate multicast packets detected. 314 5.6. The Notifications Group 316 The Notifications Subtree contains the list of notifications 317 supported within the SMF-MIB and their intended purpose or utility. 319 6. Relationship to Other MIB Modules 321 [TODO]: The text of this section specifies the relationship of the 322 MIB modules contained in this document to other standards, 323 particularly to standards containing other MIB modules. Definitions 324 imported from other MIB modules and other MIB modules that SHOULD be 325 implemented in conjunction with the MIB module contained within this 326 document are identified in this section. 328 6.1. Relationship to the SNMPv2-MIB 330 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 331 mandatory for all systems, and the objects apply to the entity as a 332 whole. The 'system' group provides identification of the management 333 entity and certain other system-wide data. The SMF-MIB does not 334 duplicate those objects. 336 6.2. MIB modules required for IMPORTS 338 The textual conventions imported for use in the SMF-MIB are as 339 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 340 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 341 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 342 and TruthValue textual conventions are imported from RFC 2579 343 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 344 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 345 InterfaceIndexOrZero textual convention is imported from RFC 2863 346 [RFC2863]. The SnmpAdminString textual convention is imported from 347 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 348 InetAddressPrefixLength textual conventions are imported from RFC 349 4001 [RFC4001]. 351 6.3. Relationship to the Future RSSA-MIBs 353 In a sense, the SMF-MIB is a general front-end to a set of, yet to be 354 developed, RSSA-specific MIBs. These RSSA-specific MIBs will define 355 the objects for the configuration, state, performance and 356 notification objects required for the operation of these specific 357 RSSAs. The SMF-MIB Capabilities Group allows the remote management 358 station the ability to query the router to discover the set of 359 supported RSSAs. 361 7. Definitions 363 MANET-SMF-MIB DEFINITIONS ::= BEGIN 365 IMPORTS 367 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 368 Counter32, Unsigned32, Integer32, TimeTicks, mib-2 369 FROM SNMPv2-SMI -- [RFC2578] 371 TEXTUAL-CONVENTION, RowStatus, TruthValue 372 FROM SNMPv2-TC -- [RFC2579] 374 MODULE-COMPLIANCE, OBJECT-GROUP, 375 NOTIFICATION-GROUP 376 FROM SNMPv2-CONF -- [RFC2580] 378 InterfaceIndexOrZero 379 FROM IF-MIB -- [RFC2863] 381 SnmpAdminString 382 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 384 InetAddress, InetAddressType, 385 InetAddressPrefixLength 386 FROM INET-ADDRESS-MIB -- [RFC4001] 387 ; 389 manetSmfMIB MODULE-IDENTITY 390 LAST-UPDATED "201101161300Z" -- January 16, 2011 391 ORGANIZATION "IETF MANET Working Group" 392 CONTACT-INFO 393 "WG E-Mail: manet@ietf.org 395 WG Chairs: ian.chakeres@gmail.com 396 jmacker@nrl.navy.mil 398 Editors: Robert G. Cole 399 US Army CERDEC 400 Space and Terrestrial Communications 401 328 Hopkins Road 402 Bldg 245, Room 16 403 Aberdeen Proving Ground, MD 21005 404 USA 405 +1 410 278-6779 406 robert.g.cole@us.army.mil 407 http://www.cs.jhu.edu/~rgcole/ 409 Joseph Macker 410 Naval Research Laboratory 411 Washington, D.C. 20375 412 USA 413 macker@itd.nrl.navy.mil 415 Brian Adamson 416 Naval Research Laboratory 417 Washington, D.C. 20375 418 USA 419 adamson@itd.nrl.navy.mil 421 Sean Harnedy 422 Booz Allen Hamilton 423 333 City Boulevard West 424 Orange, CA 92868 425 USA 426 +1 714 938-3898 427 harnedy_sean@bah.com" 429 DESCRIPTION 430 "This MIB module contains managed object definitions for 431 the Manet SMF RSSA process defined in: 433 [SMF] Macker, J.(ed.), 434 Simplified Multicast Forwarding draft-ietf-manet-smf-10, 435 March 06, 2010. 437 Copyright (C) The IETF Trust (2008). This version 438 of this MIB module is part of RFC xxxx; see the RFC 439 itself for full legal notices." 441 -- Revision History 442 REVISION "201101161300Z" -- January 16, 2011 443 DESCRIPTION 444 "Updated 5th revision of the 445 draft of this MIB module published as 446 draft-ietf-manet-smf-mib-02.txt. The changes 447 made in this revision include: 448 - Added the Notification Group and cleaned 449 up the Conformance section 450 - Completed the TEXTUAL CONVENTION for the 451 smfOpMode. 452 - Completed the Description clauses of 453 several objects within the MIB. 454 - Removed the routerPriority object. 455 - Added the definition of a smfRouterID 456 object and associated smfRouterIDAddrType 457 object. 458 " 459 REVISION "200910261300Z" -- October 26, 2009 460 DESCRIPTION 461 "Updated draft of this MIB module published as 462 draft-ietf-manet-smf-mib-01.txt. A few changes 463 were made in the development of this draft. 464 Specifically, the following changes were made: 465 - Updated the textual material, included 466 section on IMPORTS, relationship to other 467 MIBs, etc. 468 " 469 REVISION "200904211300Z" -- April 21, 2009 470 DESCRIPTION 471 "Updated draft of this MIB module published as 472 draft-ietf-manet-smf-mib-00.txt. A few changes 473 were made in the development of this draft. 474 Specifically, the following changes were made: 475 - Removed the smfGatewayFilterTable from this 476 draft. It is a useful construct, e.g., 477 an IPTABLES-MIB, but might best be handled 478 as a seperate MIB and worked within a 479 security focused working group. 480 - Removed the smfReportsGroup. This capability 481 is being replaced with a new and more general 482 method for offline reporting. This is being 483 worked as a new MIB module refered to as the 484 REPORT-MIB. 485 - Rev'd as a new MANET WG document. 486 " 487 REVISION "200902271300Z" -- February 27, 2009 488 DESCRIPTION 489 "Updated draft of this MIB module published as 490 draft-cole-manet-smf-mib-02.txt. Fairly extensive 491 revisions and additions to this MIB were made 492 in this version. Specifically, the following 493 changes were made in development of this version: 494 - added a Capabilities Group within the Objects 495 Group to allow the device to report supported 496 capabilities, e.g., RSSAs supported. 498 - added administrative status objects for device 499 and interfaces 500 - added multicast address forwarding tables, both 501 for configured (within Configuration Group) and 502 discovered (within the State Group). 503 - added additional Performance counters related 504 to DPD functions. 505 - Split up the performance counters into IPv4 506 and IPv6, for both global and per interface 507 statistics. 508 - Split out the reports capability into a seperate 509 Reports Group under the Objects Group. 510 " 511 REVISION "200811031300Z" -- November 03, 2008 512 DESCRIPTION 513 "Updated draft of this MIB module published as 514 draft-cole-manet-smf-mib-01.txt. Added gateway filter 515 table and reports capabilities following rmon." 516 REVISION "200807071200Z" -- July 07, 2008 517 DESCRIPTION 518 "Initial draft of this MIB module published as 519 draft-cole-manet-smf-mib-00.txt." 520 -- RFC-Editor assigns XXXX 521 ::= { mib-2 998 } -- to be assigned by IANA 523 -- 524 -- TEXTUAL CONVENTIONs 525 -- 527 SmfStatus ::= TEXTUAL-CONVENTION 528 STATUS current 529 DESCRIPTION 530 "An indication of the operability of a SMF 531 function or feature. For example, the status 532 of an interface: 'enabled' indicates that 533 it is performing SMF functions, 534 and 'disabled' indicates that it is not." 535 SYNTAX INTEGER { 536 enabled (1), 537 disabled (2) 538 } 540 SmfOpModeID ::= TEXTUAL-CONVENTION 541 STATUS current 542 DESCRIPTION 543 "An index that identifies through reference to a specific 544 SMF operations mode. There are basically three styles 545 of SMF operation with reduced relay sets: 547 Independent operation - SMF performs its own relay 548 set selection using information from an associated 549 MANET NHDP process. 551 CDS-aware unicast routing operation - a coexistent 552 unicast routing protocol provides dynamic relay 553 set state based upon its own control plane 554 CDS or neighborhood discovery information. 556 Cross-layer operation - SMF operates using 557 neighborhood status and triggers from a 558 cross-layer information base for dynamic relay 559 set selection and maintenance 560 " 561 SYNTAX INTEGER { 562 independent (1), 563 routing (2), 564 crossLayer (3) 565 -- future (4-255) 566 } 568 SmfRssaID ::= TEXTUAL-CONVENTION 569 STATUS current 570 DESCRIPTION 571 "An index that identifies through reference to a specific 572 RSSA algorithms. Several are currently defined 573 in the appendix of 574 " 575 SYNTAX INTEGER { 576 cF(1), 577 sMPR(2), 578 eCDS(3), 579 mprCDS(4) 580 -- future(5-127) 581 -- noStdAction(128-239) 582 -- experimental(240-255) 583 } 585 -- 586 -- Top-Level Object Identifier Assignments 587 -- 589 smfMIBNotifications OBJECT IDENTIFIER ::= { manetSmfMIB 0 } 590 smfMIBObjects OBJECT IDENTIFIER ::= { manetSmfMIB 1 } 591 smfMIBConformance OBJECT IDENTIFIER ::= { manetSmfMIB 2 } 593 -- 594 -- smfMIBObjects Assignments: 595 -- smfCapabilitiesGroup - 1 596 -- smfConfigurationGroup - 2 597 -- smfStateGroup - 3 598 -- smfPerformanceGroup - 4 599 -- 601 -- 602 -- smfCapabilitiesGroup 603 -- 604 -- This group contains the SMF objects that identify specific 605 -- capabilities within this device related to SMF functions. 606 -- 608 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 610 -- 611 -- SMF Operational Mode Capabilities Table 612 -- 614 smfOpModeCapabilitiesTable OBJECT-TYPE 615 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "The smfOpModeCapabilitiesTable identifies the 620 resident set of SMF Operational Modes on this 621 router. 622 " 623 ::= { smfCapabilitiesGroup 1 } 625 smfOpModeCapabilitiesEntry OBJECT-TYPE 626 SYNTAX SmfOpModeCapabilitiesEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "Information about a particular operational 631 mode. 632 " 633 INDEX { smfOpModeCapabilitiesID } 634 ::= { smfOpModeCapabilitiesTable 1 } 636 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 637 smfOpModeCapabilitiesID SmfOpModeID, 638 smfOpModeCapabilitiesName SnmpAdminString, 639 smfOpModeCapabilitiesReference SnmpAdminString 640 } 642 smfOpModeCapabilitiesID OBJECT-TYPE 643 SYNTAX SmfOpModeID 644 MAX-ACCESS not-accessible 645 STATUS current 646 DESCRIPTION 647 "The index for this entry. This object identifies 648 the particular operational mode for this device. 649 " 650 ::= { smfOpModeCapabilitiesEntry 1 } 652 smfOpModeCapabilitiesName OBJECT-TYPE 653 SYNTAX SnmpAdminString 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "The textual name of this operational 658 mode. Current operational modes include: 659 Independent Mode, CDS-aware Routing Mode, 660 and Cross-layer Mode. Others may be defined 661 in future revisions of [SMF]. 662 " 663 ::= { smfOpModeCapabilitiesEntry 2 } 665 smfOpModeCapabilitiesReference OBJECT-TYPE 666 SYNTAX SnmpAdminString 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "This object contains a reference to the document that 671 defines this operational mode. 672 " 673 ::= { smfOpModeCapabilitiesEntry 3 } 675 -- 676 -- SMF RSSA Capabilities Table 677 -- 679 smfRssaCapabilitiesTable OBJECT-TYPE 680 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 681 MAX-ACCESS not-accessible 682 STATUS current 683 DESCRIPTION 684 "The smfRssaCapabilitiesTable contains 685 reference to the specific set of RSSAs 686 currently supported on this device. 687 " 688 ::= { smfCapabilitiesGroup 2 } 690 smfRssaCapabilitiesEntry OBJECT-TYPE 691 SYNTAX SmfRssaCapabilitiesEntry 692 MAX-ACCESS not-accessible 693 STATUS current 694 DESCRIPTION 695 "Information about a particular RSSA 696 algorithm." 697 INDEX { smfRssaCapabilitiesID } 698 ::= { smfRssaCapabilitiesTable 1 } 700 SmfRssaCapabilitiesEntry ::= SEQUENCE { 701 smfRssaCapabilitiesID SmfRssaID, 702 smfRssaCapabilitiesName SnmpAdminString, 703 smfRssaCapabilitiesReference SnmpAdminString 704 } 706 smfRssaCapabilitiesID OBJECT-TYPE 707 SYNTAX SmfRssaID 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "The index for this entry. This object identifies 712 the particular RSSA algorithm in this MIB 713 module. Example RSSAs are found in the 714 appendix of [SMF]." 715 ::= { smfRssaCapabilitiesEntry 1 } 717 smfRssaCapabilitiesName OBJECT-TYPE 718 SYNTAX SnmpAdminString 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The textual name of this RSSA algorithm. 723 Currently defined names are: 724 Classical Flooding - cF, 725 Source-based MultiPoint 726 Relay - sMPR, 727 Essential Connecting Dominating 728 Set - eCDS, 729 MultiPoint Relay Connected 730 Dominating Set - mprCDS. 732 " 733 ::= { smfRssaCapabilitiesEntry 2 } 735 smfRssaCapabilitiesReference OBJECT-TYPE 736 SYNTAX SnmpAdminString 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "This object contains a published reference 741 to the document that defines this algorithm. 742 " 743 ::= { smfRssaCapabilitiesEntry 3 } 745 -- 746 -- smfConfigurationGroup 747 -- 748 -- This group contains the SMF objects that configure specific 749 -- options that determine the overall performance and operation 750 -- of the multicast forwarding process for the router device 751 -- and its interfaces. 752 -- 754 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 756 smfAdminStatus OBJECT-TYPE 757 SYNTAX SmfStatus 758 MAX-ACCESS read-write 759 STATUS current 760 DESCRIPTION 761 "The configured status of the SMF process 762 on this device. Enabled(1) means that 763 SMF is configured to run on this device. 764 Disabled(2) mean that the SMF process 765 is configured off. 767 This object is persistent and when written 768 the entity SHOULD save the change to 769 non-volatile storage. 770 " 771 ::= { smfConfigurationGroup 1 } 773 -- Note: need to better define the algorithm to 774 -- choose the smfRouterID. 775 smfRouterIDAddrType OBJECT-TYPE 776 SYNTAX InetAddressType 777 MAX-ACCESS read-write 778 STATUS current 779 DESCRIPTION 780 "The address type of the address used for 781 SMF ID of this router as specified 782 in the 'smfRouterID' next. 784 This can be set by the management station, must 785 the smfRouterID must be a routable address 786 assigned to this router. If the management 787 station does not assign this value, then the 788 router should choose the highest IP address 789 assigned to this router. 791 This object is persistent and when written 792 the entity SHOULD save the change to 793 non-volatile storage. 794 " 795 ::= { smfConfigurationGroup 2 } 797 smfRouterID OBJECT-TYPE 798 SYNTAX InetAddress 799 MAX-ACCESS read-write 800 STATUS current 801 DESCRIPTION 802 "The IP address used as the SMF router ID. 803 this can be set by the management station. 804 If not explicitly set, then the device 805 should select a routable IP address 806 assigned to this router for use as 807 the 'smfRouterID'. 809 This object is persistent and when written 810 the entity SHOULD save the change to 811 non-volatile storage. 812 " 813 ::= { smfConfigurationGroup 3 } 815 smfConfiguredOpMode OBJECT-TYPE 816 SYNTAX INTEGER { 817 withNHDP(1), 818 cdsAwareRouting(2), 819 crossLayer(3), 820 other(4) 821 } 822 MAX-ACCESS read-write 823 STATUS current 824 DESCRIPTION 825 "The SMF RSS node operational mode as defined 826 in the TEXTUAL CONVENTION for `SmfOpModeID' 827 and in [SMF].. 829 The value withNHDP(1) indicates Independent 830 Mode of operation. 832 The value cdsAwareRouting(2) indicates 833 CDS-aware Routing Mode of operation. 835 The value crossLayer(3) indicates 836 Cross-layer Mode of operation. 838 This object is persistent and when written 839 the entity SHOULD save the change to 840 non-volatile storage. 841 " 842 ::= { smfConfigurationGroup 4 } 844 smfConfiguredRssa OBJECT-TYPE 845 SYNTAX SmfRssaID 846 MAX-ACCESS read-write 847 STATUS current 848 DESCRIPTION 849 "The SMF RSS currently operational algorithm 850 as defined in the TEXTUAL CONVENTION for 851 `SmfRssaID' and in [SMF]. 853 This object is persistent and when written 854 the entity SHOULD save the change to 855 non-volatile storage. 856 " 857 ::= { smfConfigurationGroup 5 } 859 smfRssaMember OBJECT-TYPE 860 SYNTAX INTEGER { 861 potential(1), 862 always(2), 863 never(3) 864 } 865 MAX-ACCESS read-write 866 STATUS current 867 DESCRIPTION 868 "The RSSA downselects a set of forwarders for 869 multicast forwarding. Sometimes it is useful 870 to force an agent to be included or excluded 871 from the resulting RSS. This object is a 872 switch to allow for this behavior. 874 The value potential(1) allows the selected 875 RSSA to determine if this agent is included 876 or excluded from the RSS. 878 The value always(1) forces the selected 879 RSSA include this agent in the RSS. 881 The value never(3) forces the selected 882 RSSA to exclude this agent from the RSS. 884 This object is persistent and when written 885 the entity SHOULD save the change to 886 non-volatile storage. 887 " 888 ::= { smfConfigurationGroup 6 } 890 smfIpv4Dpd OBJECT-TYPE 891 SYNTAX INTEGER { 892 identificationBased(1), 893 hashBased(2) 894 } 895 MAX-ACCESS read-write 896 STATUS current 897 DESCRIPTION 898 "The current method for IPv4 duplicate packet 899 detection. 901 The value identificationBased(1) 902 indicates that the duplicate packet 903 detection relies upon header information 904 in the multicast packets to identify 905 previously received packets. 907 The value 'hashBased(2) indicates that the 908 routers duplicate packet detection is based 909 upon comparing a hash over the packet fields. 911 This object is persistent and when written 912 the entity SHOULD save the change to 913 non-volatile storage. 914 " 915 ::= { smfConfigurationGroup 7 } 917 smfIpv6Dpd OBJECT-TYPE 918 SYNTAX INTEGER { 919 identificationBased(1), 920 hashBased(2) 921 } 922 MAX-ACCESS read-write 923 STATUS current 924 DESCRIPTION 925 "The current method for IPv6 duplicate packet 926 detection. 928 The values indicate the type of method used 929 for duplicate packet detection as described 930 the previous description for the object 931 `smfIpv4Dpd'. 933 This object is persistent and when written 934 the entity SHOULD save the change to 935 non-volatile storage. 936 " 937 ::= { smfConfigurationGroup 8 } 939 smfMaxPktLifetime OBJECT-TYPE 940 SYNTAX Integer32 (0..65535) 941 UNITS "Seconds" 942 MAX-ACCESS read-write 943 STATUS current 944 DESCRIPTION 945 "The estimate of the network packet 946 traversal time. 948 This object is persistent and when written 949 the entity SHOULD save the change to 950 non-volatile storage. 951 " 952 DEFVAL { 60 } 953 ::= { smfConfigurationGroup 9 } 955 smfDpdMaxMemorySize OBJECT-TYPE 956 SYNTAX Integer32 (0..65535) 957 UNITS "Kilo-Bytes" 958 MAX-ACCESS read-write 959 STATUS current 960 DESCRIPTION 961 "The locally reserved memory for storage 962 of cached DPD records for both IPv4 and 963 IPv6 methods. 965 This object is persistent and when written 966 the entity SHOULD save the change to 967 non-volatile storage. 969 " 970 DEFVAL { 1024 } 971 ::= { smfConfigurationGroup 10 } 973 smfDpdEntryMaxLifetime OBJECT-TYPE 974 SYNTAX Integer32 (0..65525) 975 UNITS "Seconds" 976 MAX-ACCESS read-write 977 STATUS current 978 DESCRIPTION 979 "The maximum lifetime of a cached DPD 980 record in the local device storage. 982 This object is persistent and when written 983 the entity SHOULD save the change to 984 non-volatile storage. 985 " 986 DEFVAL { 600 } 987 ::= { smfConfigurationGroup 11 } 989 -- 990 -- Configuration of messages to be included in 991 -- NHDP message exchanges in support of SMF 992 -- operations. 993 -- 995 -- Note: need to clarify whether this is an option 996 -- or is required when the smfOpMode is set 997 -- to 'independent'. 998 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 999 SYNTAX TruthValue 1000 MAX-ACCESS read-write 1001 STATUS current 1002 DESCRIPTION 1003 "Indicates whether the associated NHDP messages 1004 include the RSSA Message TLV, or not. This 1005 is an optional SMF operational setting. 1006 The value true(1) indicates that this TLV is 1007 included; the value false(2) indicates that it 1008 is not included. 1010 This object is persistent and when written 1011 the entity SHOULD save the change to 1012 non-volatile storage. 1013 " 1014 ::= { smfConfigurationGroup 12 } 1015 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 1016 SYNTAX TruthValue 1017 MAX-ACCESS read-write 1018 STATUS current 1019 DESCRIPTION 1020 "Indicates whether the associated NHDP messages 1021 include the RSSA Address Block TLV, or not. 1022 This is an optional SMF operational setting. 1023 The value true(1) indicates that this TLV is 1024 included; the value false(2) indicates that it 1025 is not included. 1027 This object is persistent and when written 1028 the entity SHOULD save the change to 1029 non-volatile storage. 1030 " 1031 ::= { smfConfigurationGroup 13 } 1033 -- 1034 -- Table identifying configured multicast addresses to be forwarded. 1035 -- 1037 smfConfiguredAddrForwardingTable OBJECT-TYPE 1038 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 1039 MAX-ACCESS not-accessible 1040 STATUS current 1041 DESCRIPTION 1042 "The (conceptual) table containing information on multicast 1043 addresses which are to be forwarded by the SMF process. 1045 Entries in this table are configured. As well, addresses 1046 to be forwarded by the SMF device can be dynamically 1047 discovered by other means. The corresponding state 1048 table, smfDiscoveredAddrForwardingTable, contains 1049 these additional, dynamically discovered address for 1050 forwarding. 1052 Each row is associated with a range of multicast 1053 addresses, and ranges for different rows must be disjoint. 1055 The objects in this table are persistent and when written 1056 the entity SHOULD save the change to 1057 non-volatile storage. 1058 " 1059 ::= { smfConfigurationGroup 15 } 1060 smfConfiguredAddrForwardingEntry OBJECT-TYPE 1061 SYNTAX SmfConfiguredAddrForwardingEntry 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "An entry (conceptual row) containing the information on a 1066 particular multicast scope." 1067 INDEX { smfConfiguredAddrForwardingAddrType, 1068 smfConfiguredAddrForwardingFirstAddr } 1069 ::= { smfConfiguredAddrForwardingTable 1 } 1071 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 1072 smfConfiguredAddrForwardingAddrType InetAddressType, 1073 smfConfiguredAddrForwardingFirstAddr InetAddress, 1074 smfConfiguredAddrForwardingLastAddr InetAddress, 1075 smfConfiguredAddrForwardingStatus RowStatus 1076 } 1078 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 1079 SYNTAX InetAddressType 1080 MAX-ACCESS not-accessible 1081 STATUS current 1082 DESCRIPTION 1083 "The type of the addresses in the multicast forwarding 1084 range. Legal values correspond to the subset of 1085 address families for which multicast address allocation 1086 is supported." 1087 ::= { smfConfiguredAddrForwardingEntry 1 } 1089 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 1090 SYNTAX InetAddress (SIZE(0..20)) 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "The first address in the multicast scope range. The type 1095 of this address is determined by the value of the 1096 smfConfiguredAddrForwardingAddrType object." 1097 ::= { smfConfiguredAddrForwardingEntry 2 } 1099 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 1100 SYNTAX InetAddress (SIZE(0..20)) 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "The last address in the multicast scope range. 1105 The type of this address is determined by the 1106 value of the smfConfiguredAddrForwardingAddrType 1107 object." 1109 ::= { smfConfiguredAddrForwardingEntry 3 } 1111 smfConfiguredAddrForwardingStatus OBJECT-TYPE 1112 SYNTAX RowStatus 1113 MAX-ACCESS read-create 1114 STATUS current 1115 DESCRIPTION 1116 "The status of this row, by which new entries may be 1117 created, or old entries deleted from this table. If write 1118 access is supported, the other writable objects in this 1119 table may be modified even while the status is `active'." 1120 ::= { smfConfiguredAddrForwardingEntry 4 } 1122 -- 1123 -- SMF Interfaces Configuration Table 1124 -- 1126 smfInterfaceTable OBJECT-TYPE 1127 SYNTAX SEQUENCE OF SmfInterfaceEntry 1128 MAX-ACCESS not-accessible 1129 STATUS current 1130 DESCRIPTION 1131 "The SMF Interface Table describes the SMF 1132 interfaces that are participating in the 1133 SMF packet forwarding process. The ifIndex is 1134 from the interfaces group defined in the 1135 Interfaces Group MIB. 1137 The objects in this table are persistent 1138 and when written the entity SHOULD save 1139 the change to non-volatile storage. 1140 " 1141 REFERENCE 1142 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1143 K., and F. Kastenholtz, June 2000." 1144 ::= { smfConfigurationGroup 16 } 1146 smfInterfaceEntry OBJECT-TYPE 1147 SYNTAX SmfInterfaceEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "The SMF interface entry describes one SMF 1152 interface as indexed by its ifIndex." 1153 INDEX { smfIfIndex } 1154 ::= { smfInterfaceTable 1 } 1155 SmfInterfaceEntry ::= 1156 SEQUENCE { 1157 smfIfIndex InterfaceIndexOrZero, 1158 smfIfAdminStatus SmfStatus, 1159 smfIfRowStatus RowStatus 1160 } 1162 smfIfIndex OBJECT-TYPE 1163 SYNTAX InterfaceIndexOrZero 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "The ifIndex for this SMF interface." 1168 ::= { smfInterfaceEntry 1 } 1170 smfIfAdminStatus OBJECT-TYPE 1171 SYNTAX SmfStatus 1172 MAX-ACCESS read-create 1173 STATUS current 1174 DESCRIPTION 1175 "The SMF interface's administrative status. 1176 The value 'enabled' denotes that the interface 1177 is running the SMF forwarding process. 1178 The value 'disabled' denotes that the interface is 1179 external to the SMF forwarding process. 1180 " 1181 ::= { smfInterfaceEntry 2 } 1183 smfIfRowStatus OBJECT-TYPE 1184 SYNTAX RowStatus 1185 MAX-ACCESS read-create 1186 STATUS current 1187 DESCRIPTION 1188 "This object permits management of the table 1189 by facilitating actions such as row creation, 1190 construction, and destruction. The value of 1191 this object has no effect on whether other 1192 objects in this conceptual row can be 1193 modified." 1194 ::= { smfInterfaceEntry 3 } 1196 -- 1197 -- smfStateGroup 1198 -- 1199 -- Contains information describing the current state of the SMF 1200 -- process such as the current inclusion in the RS or not. 1202 -- 1204 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1206 smfNodeRsStatusIncluded OBJECT-TYPE 1207 SYNTAX TruthValue 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The current status of the SMF node in the context of 1212 the MANETs relay set. A value of true(1) indicates 1213 that the node is currently part of the MANET Relay 1214 Set. A value of false(2) indicates that the node 1215 is currently not part of the MANET Relay Set." 1216 ::= { smfStateGroup 1 } 1218 smfDpdMemoryOverflow OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "The number of times that the memory for caching 1224 records for DPD overran and records had to be flushed. 1225 The number of records to be flushed upon a buffer 1226 overflow is an implementation specific decision. 1227 " 1228 ::= { smfStateGroup 2 } 1230 -- 1231 -- Dynamically Discovered Multicast Addr Table 1232 -- 1234 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1235 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1236 MAX-ACCESS not-accessible 1237 STATUS current 1238 DESCRIPTION 1239 "The (conceptual) table containing information on multicast 1240 addresses which are to be forwarded by the SMF process. 1242 Entries in this table are configured. As well, addresses 1243 to be forwarded by the SMF device can be dynamically 1244 discovered by other means. The corresponding state 1245 table, smfDiscoveredAddrForwardingTable contains 1246 these additional, dynamically discovered address for 1247 forwarding. 1249 Each row is associated with a range of 1250 multicast addresses, and ranges for different rows 1251 must be disjoint. 1252 " 1253 ::= { smfStateGroup 3 } 1255 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1256 SYNTAX SmfDiscoveredAddrForwardingEntry 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 "An entry (conceptual row) containing the information on a 1261 particular multicast scope." 1262 INDEX { smfDiscoveredAddrForwardingAddrType, 1263 smfDiscoveredAddrForwardingFirstAddr } 1264 ::= { smfDiscoveredAddrForwardingTable 1 } 1266 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1267 smfDiscoveredAddrForwardingAddrType InetAddressType, 1268 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1269 smfDiscoveredAddrForwardingLastAddr InetAddress, 1270 smfDiscoveredAddrForwardingStatus RowStatus 1271 } 1273 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1274 SYNTAX InetAddressType 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "The type of the addresses in the multicast forwarding 1279 range. Legal values correspond to the subset of 1280 address families for which multicast address allocation 1281 is supported." 1282 ::= { smfDiscoveredAddrForwardingEntry 1 } 1284 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1285 SYNTAX InetAddress (SIZE(0..20)) 1286 MAX-ACCESS not-accessible 1287 STATUS current 1288 DESCRIPTION 1289 "The first address in the multicast scope range. The type 1290 of this address is determined by the value of the 1291 smfConfiguredAddrForwardingAddrType object." 1292 ::= { smfDiscoveredAddrForwardingEntry 2 } 1294 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1295 SYNTAX InetAddress (SIZE(0..20)) 1296 MAX-ACCESS read-create 1297 STATUS current 1298 DESCRIPTION 1299 "The last address in the multicast scope range. 1300 The type of this address is determined by the 1301 value of the smfConfiguredAddrForwardingAddrType 1302 object." 1303 ::= { smfDiscoveredAddrForwardingEntry 3 } 1305 smfDiscoveredAddrForwardingStatus OBJECT-TYPE 1306 SYNTAX RowStatus 1307 MAX-ACCESS read-create 1308 STATUS current 1309 DESCRIPTION 1310 "The status of this row, by which new entries may be 1311 created, or old entries deleted from this table. If write 1312 access is supported, the other writable objects in this 1313 table may be modified even while the status is `active'." 1314 ::= { smfDiscoveredAddrForwardingEntry 4 } 1316 -- 1317 -- SMF Neighbor Table 1318 -- 1320 smfNeighborTable OBJECT-TYPE 1321 SYNTAX SEQUENCE OF SmfNeighborEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "The SMF NeighborTable describes the 1326 current neighbor nodes, their address 1327 and SMF RSSA and the interface on which 1328 they can be reached." 1329 REFERENCE 1330 "Simplified Multicast Forwarding for MANET 1331 (SMF), Macker, J., July 2009. 1332 Section 7: SMF Neighborhood Discovery 1333 Requirements." 1334 ::= { smfStateGroup 4 } 1336 smfNeighborEntry OBJECT-TYPE 1337 SYNTAX SmfNeighborEntry 1338 MAX-ACCESS not-accessible 1339 STATUS current 1340 DESCRIPTION 1341 "The SMF Neighbor Table contains the 1342 set of one-hop neighbors, the interface 1343 they are reachable on and the SMF RSSA 1344 they are currently running." 1345 INDEX { smfNeighborIpAddrType, 1346 smfNeighborIpAddr, 1347 smfNeighborPrefixLen } 1348 ::= { smfNeighborTable 1 } 1350 SmfNeighborEntry ::= 1351 SEQUENCE { 1352 smfNeighborIpAddrType InetAddressType, 1353 smfNeighborIpAddr InetAddress, 1354 smfNeighborPrefixLen InetAddressPrefixLength, 1355 smfNeighborRSSA SmfRssaID, 1356 smfNeighborNextHopInterface InterfaceIndexOrZero 1357 } 1359 smfNeighborIpAddrType OBJECT-TYPE 1360 SYNTAX InetAddressType 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "The neighbor IP address type." 1365 ::= { smfNeighborEntry 1 } 1367 smfNeighborIpAddr OBJECT-TYPE 1368 SYNTAX InetAddress 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "The neighbor Inet IPv4 or IPv6 address." 1373 ::= { smfNeighborEntry 2 } 1375 smfNeighborPrefixLen OBJECT-TYPE 1376 SYNTAX InetAddressPrefixLength 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "The prefix length. This is a decimal value that 1381 indicates the number of contiguous, higher-order 1382 bits of the address that make up the network 1383 portion of the address." 1384 ::= { smfNeighborEntry 3 } 1386 smfNeighborRSSA OBJECT-TYPE 1387 SYNTAX SmfRssaID 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "The current RSSA running on the neighbor. 1392 The list is identical to that described 1393 above for the smfRssa object." 1394 ::= { smfNeighborEntry 4 } 1396 smfNeighborNextHopInterface OBJECT-TYPE 1397 SYNTAX InterfaceIndexOrZero 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "The interface ifIndex over which the 1402 neighbor is reachable in one-hop." 1403 ::= { smfNeighborEntry 5 } 1405 -- 1406 -- SMF Performance Group 1407 -- 1408 -- Contains objects which help to characterize the 1409 -- performance of the SMF RSSA process, such as statistics 1410 -- counters. There are two types of SMF RSSA statistics: 1411 -- global counters and per interface counters. 1412 -- 1414 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1416 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1418 -- 1419 -- IPv4 packet counters 1420 -- 1422 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1423 SYNTAX Counter32 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "A counter of the total number of 1428 multicast IPv4 packets received by the 1429 device." 1430 ::= { smfGlobalPerfGroup 1 } 1432 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1433 SYNTAX Counter32 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "A counter of the total number of 1438 multicast IPv4 packets forwarded by the 1439 device." 1440 ::= { smfGlobalPerfGroup 2 } 1442 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1443 SYNTAX Counter32 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "A counter of the total number of duplicate 1448 multicast IPv4 packets detected by the 1449 device." 1450 ::= { smfGlobalPerfGroup 3 } 1452 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1453 SYNTAX Counter32 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "A counter of the total number of dropped 1458 multicast IPv4 packets by the 1459 device due to TTL exceeded." 1460 ::= { smfGlobalPerfGroup 4 } 1462 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1463 SYNTAX Counter32 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "A counter of the total number of IPv4 packets 1468 recieved which have a TTL larger than that 1469 of a previously received identical packet. 1470 " 1471 ::= { smfGlobalPerfGroup 5 } 1473 -- 1474 -- IPv6 packet counters 1475 -- 1477 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1478 SYNTAX Counter32 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "A counter of the total number of 1483 multicast IPv6 packets received by the 1484 device." 1485 ::= { smfGlobalPerfGroup 6 } 1487 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1488 SYNTAX Counter32 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "A counter of the total number of 1493 multicast IPv6 packets forwarded by the 1494 device." 1495 ::= { smfGlobalPerfGroup 7 } 1497 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1498 SYNTAX Counter32 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "A counter of the total number of duplicate 1503 multicast IPv6 packets detected by the 1504 device." 1505 ::= { smfGlobalPerfGroup 8 } 1507 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1508 SYNTAX Counter32 1509 MAX-ACCESS read-only 1510 STATUS current 1511 DESCRIPTION 1512 "A counter of the total number of dropped 1513 multicast IPv6 packets by the 1514 device due to TTL exceeded." 1515 ::= { smfGlobalPerfGroup 9 } 1517 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1518 SYNTAX Counter32 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "A counter of the total number of IPv6 packets 1523 recieved which have a TTL larger than that 1524 of a previously recived identical packet. 1525 " 1526 ::= { smfGlobalPerfGroup 10 } 1528 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1529 SYNTAX Counter32 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "A counter of the total number of IPv6 packets 1534 recieved which required the HAV assist for DPD. 1535 " 1536 ::= { smfGlobalPerfGroup 11 } 1538 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1539 SYNTAX Counter32 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "A counter of the total number of IPv6 packets 1544 recieved which the device inserted the 1545 DPD header option. 1546 " 1547 ::= { smfGlobalPerfGroup 12 } 1549 -- 1550 -- Per SMF Interface Performance Table 1551 -- 1553 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1555 smfIpv4InterfacePerfTable OBJECT-TYPE 1556 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1557 MAX-ACCESS not-accessible 1558 STATUS current 1559 DESCRIPTION 1560 "The SMF Interface Performance Table 1561 describes the SMF statistics per 1562 interface." 1563 ::= { smfInterfacePerfGroup 1 } 1565 smfIpv4InterfacePerfEntry OBJECT-TYPE 1566 SYNTAX SmfIpv4InterfacePerfEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "The SMF Interface Performance entry 1571 describes the statistics for a particular 1572 node interface." 1573 INDEX { smfIpv4IfPerfIfIndex } 1574 ::= { smfIpv4InterfacePerfTable 1 } 1576 SmfIpv4InterfacePerfEntry ::= 1577 SEQUENCE { 1578 smfIpv4IfPerfIfIndex InterfaceIndexOrZero, 1579 smfIpv4MultiPktsRecvPerIf Counter32, 1580 smfIpv4MultiPktsForwardedPerIf Counter32, 1581 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1582 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1583 smfIpv4TTLLargerThanPreviousPerIf Counter32 1584 } 1586 smfIpv4IfPerfIfIndex OBJECT-TYPE 1587 SYNTAX InterfaceIndexOrZero 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "The ifIndex for this node interface 1592 that is collecting this set of 1593 performance management statistics." 1594 ::= { smfIpv4InterfacePerfEntry 1 } 1596 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1597 SYNTAX Counter32 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "A counter of the number of 1602 multicast IP packets received by the 1603 device on this interface." 1604 ::= { smfIpv4InterfacePerfEntry 2 } 1606 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1607 SYNTAX Counter32 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "A counter of the number of 1612 multicast IP packets forwarded by the 1613 device on this interface." 1614 ::= { smfIpv4InterfacePerfEntry 3 } 1616 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1617 SYNTAX Counter32 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "A counter of the number of duplicate 1622 multicast IP packets detected by the 1623 device on this interface." 1624 ::= { smfIpv4InterfacePerfEntry 4 } 1626 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1627 SYNTAX Counter32 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "A counter of the total number of dropped 1632 multicast IPv4 packets by the 1633 device due to TTL exceeded." 1634 ::= { smfIpv4InterfacePerfEntry 5 } 1636 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1637 SYNTAX Counter32 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "A counter of the total number of IPv4 packets 1642 recieved which have a TTL larger than that 1643 of a previously recived identical packet. 1644 " 1645 ::= { smfIpv4InterfacePerfEntry 6 } 1647 smfIpv6InterfacePerfTable OBJECT-TYPE 1648 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1649 MAX-ACCESS not-accessible 1650 STATUS current 1651 DESCRIPTION 1652 "The SMF Interface Performance Table 1653 describes the SMF statistics per 1654 interface." 1655 ::= { smfInterfacePerfGroup 2 } 1657 smfIpv6InterfacePerfEntry OBJECT-TYPE 1658 SYNTAX SmfIpv6InterfacePerfEntry 1659 MAX-ACCESS not-accessible 1660 STATUS current 1661 DESCRIPTION 1662 "The SMF Interface Performance entry 1663 describes the statistics for a particular 1664 node interface." 1665 INDEX { smfIpv6IfPerfIfIndex } 1666 ::= { smfIpv6InterfacePerfTable 1 } 1668 SmfIpv6InterfacePerfEntry ::= 1669 SEQUENCE { 1670 smfIpv6IfPerfIfIndex InterfaceIndexOrZero, 1671 smfIpv6MultiPktsRecvPerIf Counter32, 1672 smfIpv6MultiPktsForwardedPerIf Counter32, 1673 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1674 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1675 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1676 smfIpv6HAVAssistsReqdPerIf Counter32, 1677 smfIpv6DpdHeaderInsertionsPerIf Counter32 1678 } 1680 smfIpv6IfPerfIfIndex OBJECT-TYPE 1681 SYNTAX InterfaceIndexOrZero 1682 MAX-ACCESS not-accessible 1683 STATUS current 1684 DESCRIPTION 1685 "The ifIndex for this node interface 1686 that is collecting this set of 1687 performance management statistics. 1689 For packets generated locally at 1690 this node, performance counters 1691 are assigned to the loopback 1692 interface. 1693 " 1694 ::= { smfIpv6InterfacePerfEntry 1 } 1696 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1697 SYNTAX Counter32 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "A counter of the number of 1702 multicast IP packets received by the 1703 device on this interface." 1704 ::= { smfIpv6InterfacePerfEntry 2 } 1706 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1707 SYNTAX Counter32 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "A counter of the number of 1712 multicast IP packets forwarded by the 1713 device on this interface." 1714 ::= { smfIpv6InterfacePerfEntry 3 } 1716 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1717 SYNTAX Counter32 1718 MAX-ACCESS read-only 1719 STATUS current 1720 DESCRIPTION 1721 "A counter of the number of duplicate 1722 multicast IP packets detected by the 1723 device on this interface." 1724 ::= { smfIpv6InterfacePerfEntry 4 } 1726 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1727 SYNTAX Counter32 1728 MAX-ACCESS read-only 1729 STATUS current 1730 DESCRIPTION 1731 "A counter of the number of dropped 1732 multicast IP packets by the 1733 device on this interface due to TTL 1734 exceeded." 1735 ::= { smfIpv6InterfacePerfEntry 5 } 1737 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1738 SYNTAX Counter32 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "A counter of the total number of IPv6 packets 1743 recieved which have a TTL larger than that 1744 of a previously recived identical packet. 1745 " 1746 ::= { smfIpv6InterfacePerfEntry 6 } 1748 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 1749 SYNTAX Counter32 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "A counter of the total number of IPv6 packets 1754 recieved which required the HAV assist for DPD. 1755 " 1756 ::= { smfIpv6InterfacePerfEntry 7 } 1758 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 1759 SYNTAX Counter32 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "A counter of the total number of IPv6 packets 1764 recieved which the device inserted the 1765 DPD header option. 1766 " 1767 ::= { smfIpv6InterfacePerfEntry 8 } 1768 -- 1769 -- Notifications 1770 -- 1772 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 1773 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 2 } 1774 smfMIBNotifStates OBJECT IDENTIFIER ::= { smfMIBNotifications 3 } 1776 -- smfMIBNotifControl 1777 smfSetNotification OBJECT-TYPE 1778 SYNTAX OCTET STRING (SIZE(4)) 1779 MAX-ACCESS read-write 1780 STATUS current 1781 DESCRIPTION 1782 "A 4-octet string serving as a bit map for 1783 the notification events defined by the SMF MIB 1784 notifications. This object is used to enable 1785 and disable specific SMF MIB notifications where 1786 a 1 in the bit field represents enabled. The 1787 right-most bit (least significant) represents 1788 notification 0. 1790 This object is persistent and when written 1791 the entity SHOULD save the change to 1792 non-volatile storage. 1793 " 1794 ::= { smfMIBNotifControl 1 } 1796 smfDpdMemoryOverflowThreshold OBJECT-TYPE 1797 SYNTAX Integer32 (0..255) 1798 MAX-ACCESS read-write 1799 STATUS current 1800 DESCRIPTION 1801 "A threshold value for the 1802 `smfDpdmemoryOverflowEvents' object. 1803 If the number of occurences exceeds 1804 this threshold within the previous 1805 number of seconds 1806 'smfDpdMemoryOverflowWindow', 1807 then the `smfDpdMemoryOverflowEvent' 1808 notification is sent. 1809 " 1810 ::= { smfMIBNotifControl 2 } 1812 smfDpdMemoryOverflowWindow OBJECT-TYPE 1813 SYNTAX TimeTicks 1814 MAX-ACCESS read-write 1815 STATUS current 1816 DESCRIPTION 1817 "A time window value for the 1818 `smfDpdmemoryOverflowEvents' object. 1819 If the number of occurences exceeds 1820 the `smfDpdMemoryOverflowThreshold' 1821 within the previous number of seconds 1822 'smfDpdMemoryOverflowWindow', 1823 then the `smfDpdMemoryOverflowEvent' 1824 notification is sent. 1825 " 1826 ::= { smfMIBNotifControl 3 } 1828 smfIpv4DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 1829 SYNTAX Integer32 (0..255) 1830 MAX-ACCESS read-write 1831 STATUS current 1832 DESCRIPTION 1833 "A threshold value for the 1834 `smfIpv4DuplMultiPktsDetectedTotal' 1835 object. If the number of occurences 1836 exceeds this threshold within the 1837 previous number of seconds 1838 `smfIpv4DuplMultiPktsDetectedTotalWindow', 1839 then the 1840 `smfIpv4DuplMultiPktsDetectedTotalEvent' 1841 notification is sent. 1842 " 1843 ::= { smfMIBNotifControl 4 } 1845 smfIpv4DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 1846 SYNTAX TimeTicks 1847 MAX-ACCESS read-write 1848 STATUS current 1849 DESCRIPTION 1850 "A time window value for the 1851 `smfIpv4DuplMultiPktsDetectedTotalEvents' 1852 object. If the number of occurences 1853 exceeds the 1854 `smfIpv4DuplMultiPktsDetectedTotalThreshold' 1855 within the previous number of seconds 1856 'smfIpv4DuplMultiPktsDetectedTotalWindow', 1857 then the 1858 `smfIpv4DuplMultiPktsDetectedTotalEvent' 1859 notification is sent. 1860 " 1861 ::= { smfMIBNotifControl 5 } 1863 smfIpv6DuplMultiPktsDetectedTotalThreshold OBJECT-TYPE 1864 SYNTAX Integer32 (0..255) 1865 MAX-ACCESS read-write 1866 STATUS current 1867 DESCRIPTION 1868 "A threshold value for the 1869 `smfIpv6DuplMultiPktsDetectedTotal' 1870 object. If the number of occurences 1871 exceeds this threshold within the 1872 previous number of seconds 1873 `smfIpv6DuplMultiPktsDetectedTotalWindow', 1874 then the 1875 `smfIpv6DuplMultiPktsDetectedTotalEvent' 1876 notification is sent. 1877 " 1878 ::= { smfMIBNotifControl 6 } 1880 smfIpv6DuplMultiPktsDetectedTotalWindow OBJECT-TYPE 1881 SYNTAX TimeTicks 1882 MAX-ACCESS read-write 1883 STATUS current 1884 DESCRIPTION 1885 "A time window value for the 1886 `smfIpv6DuplMultiPktsDetectedTotalEvents' 1887 object. If the number of occurences 1888 exceeds the 1889 `smfIpv6DuplMultiPktsDetectedTotalThreshold' 1890 within the previous number of seconds 1891 'smfIpv6DuplMultiPktsDetectedTotalWindow', 1892 then the 1893 `smfIpv6DuplMultiPktsDetectedTotalEvent' 1894 notification is sent. 1895 " 1896 ::= { smfMIBNotifControl 7 } 1898 -- smfMIBNotifObjects 1900 smfAdminStatusChange NOTIFICATION-TYPE 1901 OBJECTS { smfRouterIDAddrType, -- The originator of 1902 -- the notification. 1903 smfRouterID, -- The originator of 1904 -- the notification. 1905 smfAdminStatus -- The new status of the 1906 -- SMF process. 1907 } 1908 STATUS current 1909 DESCRIPTION 1910 "smfAdminStatusChange is a notification sent when a 1911 the 'smfAdminStatus' object changes. 1912 " 1913 ::= { smfMIBNotifObjects 1 } 1915 smfConfiguredOpModeChange NOTIFICATION-TYPE 1916 OBJECTS { smfRouterIDAddrType, -- The originator of 1917 -- the notification. 1918 smfRouterID, -- The originator of 1919 -- the notification. 1920 smfConfiguredOpMode -- The new Operations 1921 -- Mode of the SMF 1922 -- process. 1923 } 1924 STATUS current 1925 DESCRIPTION 1926 "smfConfiguredOpModeChange is a notification 1927 sent when a the 'smfConfiguredOpMode' object 1928 changes. 1929 " 1930 ::= { smfMIBNotifObjects 2 } 1932 smfConfiguredRssaChange NOTIFICATION-TYPE 1933 OBJECTS { smfRouterIDAddrType, -- The originator of 1934 -- the notification. 1935 smfRouterID, -- The originator of 1936 -- the notification. 1937 smfConfiguredRssa -- The new RSSA for 1938 -- the SMF process. 1939 } 1940 STATUS current 1941 DESCRIPTION 1942 "smfAdminStatusChange is a notification sent when a 1943 the 'smfConfiguredRssa' object changes. 1944 " 1945 ::= { smfMIBNotifObjects 3 } 1947 smfIfAdminStatusChange NOTIFICATION-TYPE 1948 OBJECTS { smfRouterIDAddrType, -- The originator of 1949 -- the notification. 1950 smfRouterID, -- The originator of 1951 -- the notification. 1952 smfIfIndex, -- The interface whose 1953 -- status has changed. 1954 smfIfAdminStatus -- The new status of the 1955 -- SMF interface. 1956 } 1958 STATUS current 1959 DESCRIPTION 1960 "smfIfAdminStatusChange is a notification sent when a 1961 the 'smfIfAdminStatus' object changes. 1962 " 1963 ::= { smfMIBNotifObjects 4 } 1965 smfDpdMemoryOverflowEvent NOTIFICATION-TYPE 1966 OBJECTS { smfRouterIDAddrType, -- The originator of 1967 -- the notification. 1968 smfRouterID, -- The originator of 1969 -- the notification. 1970 smfDpdMemoryOverflow -- The counter of 1971 -- the overflows. 1972 } 1973 STATUS current 1974 DESCRIPTION 1975 "smfDpdMemoryOverflowEvents is sent when the 1976 number of memory overflow events exceeds the 1977 the 'smfDpdMemoryOverflowThreshold' within the 1978 previous number of seconds defined by the 1979 'smfDpdMemoryOverflowWindow'. 1980 " 1981 ::= { smfMIBNotifObjects 5 } 1983 smfIpv4DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 1984 OBJECTS { smfRouterIDAddrType, -- The originator of 1985 -- the notification. 1986 smfRouterID, -- The originator of 1987 -- the notification. 1988 smfIpv4DuplMultiPktsDetectedTotal -- The 1989 -- counter of detected 1990 -- duplicates. 1991 } 1992 STATUS current 1993 DESCRIPTION 1994 "smfIpv4DuplMultiPktsDetectedTotal is a 1995 notification sent when the number of 1996 IPv4 duplicate packets detected exceeds the 1997 'smfIpv4DuplMultiPktsDetectedTotalThreshold' 1998 during the previous number of seconds 1999 'smfIpv4DuplPktsDetectedTotalWindow'. 2000 " 2001 ::= { smfMIBNotifObjects 6 } 2003 smfIpv6DuplMultiPktsDetectedTotalEvents NOTIFICATION-TYPE 2004 OBJECTS { smfRouterIDAddrType, -- The originator of 2005 -- the notification. 2007 smfRouterID, -- The originator of 2008 -- the notification. 2009 smfIpv6DuplMultiPktsDetectedTotal -- The 2010 -- counter of detected 2011 -- duplicates. 2012 } 2013 STATUS current 2014 DESCRIPTION 2015 "smfIpv6DuplMultiPktsDetectedTotal is a 2016 notification sent when the number of 2017 IPv6 duplicate packets detected exceeds the 2018 'smfIpv6DuplMultiPktsDetectedTotalThreshold' 2019 during the previous number of seconds 2020 'smfIpv6DuplPktsDetectedTotalWindow'. 2021 " 2022 ::= { smfMIBNotifObjects 7 } 2024 -- smfMIBNotifStates 2025 -- is empty. 2027 -- 2028 -- Compliance Statements 2029 -- 2031 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2032 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2034 smfBasicCompliance MODULE-COMPLIANCE 2035 STATUS current 2036 DESCRIPTION "The basic implementation requirements for 2037 managed network entities that implement 2038 the SMF RSSA process." 2039 MODULE -- this module 2040 MANDATORY-GROUPS { smfCapabObjectsGroup, 2041 smfConfigObjectsGroup } 2042 ::= { smfCompliances 1 } 2044 smfFullCompliance MODULE-COMPLIANCE 2045 STATUS current 2046 DESCRIPTION "The full implementation requirements for 2047 managed network entities that implement 2048 the SMF RSSA process." 2050 MODULE -- this module 2051 MANDATORY-GROUPS { smfCapabObjectsGroup, 2052 smfConfigObjectsGroup, 2053 smfStateObjectsGroup, 2054 smfPerfObjectsGroup, 2055 smfNotifObjectsGroup, 2056 smfNotificationsGroup 2057 } 2058 ::= { smfCompliances 2 } 2060 -- 2061 -- Units of Conformance 2062 -- 2064 smfCapabObjectsGroup OBJECT-GROUP 2065 OBJECTS { 2066 smfOpModeCapabilitiesName, 2067 smfOpModeCapabilitiesReference, 2069 smfRssaCapabilitiesName, 2070 smfRssaCapabilitiesReference 2071 } 2072 STATUS current 2073 DESCRIPTION 2074 "Set of SMF configuration objects implemented 2075 in this module." 2076 ::= { smfMIBGroups 1 } 2078 smfConfigObjectsGroup OBJECT-GROUP 2079 OBJECTS { 2080 smfAdminStatus, 2081 smfRouterIDAddrType, 2082 smfRouterID, 2083 smfIfIndex, 2084 smfConfiguredOpMode, 2085 smfConfiguredRssa, 2086 smfRssaMember, 2087 smfIpv4Dpd, 2088 smfIpv6Dpd, 2089 smfMaxPktLifetime, 2090 smfDpdMaxMemorySize, 2091 smfDpdEntryMaxLifetime, 2092 smfNhdpRssaMesgTLVIncluded, 2093 smfNhdpRssaAddrBlockTLVIncluded, 2095 smfConfiguredAddrForwardingLastAddr, 2096 smfConfiguredAddrForwardingStatus, 2097 smfIfAdminStatus, 2098 smfIfRowStatus 2099 } 2100 STATUS current 2101 DESCRIPTION 2102 "Set of SMF configuration objects implemented 2103 in this module." 2104 ::= { smfMIBGroups 2 } 2106 smfStateObjectsGroup OBJECT-GROUP 2107 OBJECTS { 2108 smfNodeRsStatusIncluded, 2109 smfDpdMemoryOverflow, 2111 smfDiscoveredAddrForwardingLastAddr, 2112 smfDiscoveredAddrForwardingStatus, 2114 smfNeighborRSSA, 2115 smfNeighborNextHopInterface 2116 } 2117 STATUS current 2118 DESCRIPTION 2119 "Set of SMF state objects implemented 2120 in this module." 2121 ::= { smfMIBGroups 3 } 2123 smfPerfObjectsGroup OBJECT-GROUP 2124 OBJECTS { 2125 smfIpv4MultiPktsRecvTotal, 2126 smfIpv4MultiPktsForwardedTotal, 2127 smfIpv4DuplMultiPktsDetectedTotal, 2128 smfIpv4DroppedMultiPktsTTLExceededTotal, 2129 smfIpv4TTLLargerThanPreviousTotal, 2131 smfIpv6MultiPktsRecvTotal, 2132 smfIpv6MultiPktsForwardedTotal, 2133 smfIpv6DuplMultiPktsDetectedTotal, 2134 smfIpv6DroppedMultiPktsTTLExceededTotal, 2135 smfIpv6TTLLargerThanPreviousTotal, 2136 smfIpv6HAVAssistsReqdTotal, 2137 smfIpv6DpdHeaderInsertionsTotal, 2139 smfIpv4MultiPktsRecvPerIf, 2140 smfIpv4MultiPktsForwardedPerIf, 2141 smfIpv4DuplMultiPktsDetectedPerIf, 2142 smfIpv4DroppedMultiPktsTTLExceededPerIf, 2143 smfIpv4TTLLargerThanPreviousPerIf, 2144 smfIpv6MultiPktsRecvPerIf, 2145 smfIpv6MultiPktsForwardedPerIf, 2146 smfIpv6DuplMultiPktsDetectedPerIf, 2147 smfIpv6DroppedMultiPktsTTLExceededPerIf, 2148 smfIpv6TTLLargerThanPreviousPerIf, 2149 smfIpv6HAVAssistsReqdPerIf, 2150 smfIpv6DpdHeaderInsertionsPerIf 2151 } 2152 STATUS current 2153 DESCRIPTION 2154 "Set of SMF performance objects implemented 2155 in this module by total and per interface." 2156 ::= { smfMIBGroups 4 } 2158 smfNotifObjectsGroup OBJECT-GROUP 2159 OBJECTS { 2160 smfSetNotification, 2161 smfDpdMemoryOverflowThreshold, 2162 smfDpdMemoryOverflowWindow, 2163 smfIpv4DuplMultiPktsDetectedTotalThreshold, 2164 smfIpv4DuplMultiPktsDetectedTotalWindow, 2165 smfIpv6DuplMultiPktsDetectedTotalThreshold, 2166 smfIpv6DuplMultiPktsDetectedTotalWindow 2167 } 2168 STATUS current 2169 DESCRIPTION 2170 "Set of SMF notification control 2171 objects implemented in this module." 2172 ::= { smfMIBGroups 5 } 2174 smfNotificationsGroup NOTIFICATION-GROUP 2175 NOTIFICATIONS { 2176 smfAdminStatusChange, 2177 smfConfiguredOpModeChange, 2178 smfConfiguredRssaChange, 2179 smfIfAdminStatusChange, 2180 smfDpdMemoryOverflowEvent, 2181 smfIpv4DuplMultiPktsDetectedTotalEvents, 2182 smfIpv6DuplMultiPktsDetectedTotalEvents 2183 } 2184 STATUS current 2185 DESCRIPTION 2186 "Set of SMF notifications implemented 2187 in this module." 2188 ::= { smfMIBGroups 6 } 2189 END 2191 8. Security Considerations 2193 [TODO] Each specification that defines one or more MIB modules MUST 2194 contain a section that discusses security considerations relevant to 2195 those modules. This section MUST be patterned after the latest 2196 approved template (available at 2197 http://www.ops.ietf.org/mib-security.html). Remember that the 2198 objective is not to blindly copy text from the template, but rather 2199 to think and evaluate the risks/vulnerabilities and then state/ 2200 document the result of this evaluation. 2202 [TODO] if you have any read-write and/or read-create objects, please 2203 include the following boilerplate paragraph. 2205 There are a number of management objects defined in this MIB module 2206 with a MAX-ACCESS clause of read-write and/or read-create. Such 2207 objects may be considered sensitive or vulnerable in some network 2208 environments. The support for SET operations in a non-secure 2209 environment without proper protection can have a negative effect on 2210 network operations. These are the tables and objects and their 2211 sensitivity/vulnerability: 2213 o [TODO] writable MIB objects that could be especially disruptive if 2214 abused MUST be explicitly listed by name and the associated 2215 security risks MUST be spelled out; RFC 2669 has a very good 2216 example. 2218 o [TODO] list the writable tables and objects and state why they are 2219 sensitive. 2221 [TODO] else if there are no read-write objects in your MIB module, 2222 use the following boilerplate paragraph. 2224 There are no management objects defined in this MIB module that have 2225 a MAX-ACCESS clause of read-write and/or read-create. So, if this 2226 MIB module is implemented correctly, then there is no risk that an 2227 intruder can alter or create any management objects of this MIB 2228 module via direct SNMP SET operations. 2230 [TODO] if you have any sensitive readable objects, please include the 2231 following boilerplate paragraph. 2233 Some of the readable objects in this MIB module (i.e., objects with a 2234 MAX-ACCESS other than not-accessible) may be considered sensitive or 2235 vulnerable in some network environments. It is thus important to 2236 control even GET and/or NOTIFY access to these objects and possibly 2237 to even encrypt the values of these objects when sending them over 2238 the network via SNMP. These are the tables and objects and their 2239 sensitivity/vulnerability: 2241 o [TODO] you must explicitly list by name any readable objects that 2242 are sensitive or vulnerable and the associated security risks MUST 2243 be spelled out (for instance, if they might reveal customer 2244 information or violate personal privacy laws such as those of the 2245 European Union if exposed to unauthorized parties) 2247 o [TODO] list the tables and objects and state why they are 2248 sensitive. 2250 [TODO] discuss what security the protocol used to carry the 2251 information should have. The following three boilerplate paragraphs 2252 should not be changed without very good reason. Changes will almost 2253 certainly require justification during IESG review. 2255 SNMP versions prior to SNMPv3 did not include adequate security. 2256 Even if the network itself is secure (for example by using IPSec), 2257 even then, there is no control as to who on the secure network is 2258 allowed to access and GET/SET (read/change/create/delete) the objects 2259 in this MIB module. 2261 It is RECOMMENDED that implementers consider the security features as 2262 provided by the SNMPv3 framework (see [RFC3410], section 8), 2263 including full support for the SNMPv3 cryptographic mechanisms (for 2264 authentication and privacy). 2266 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2267 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2268 enable cryptographic security. It is then a customer/operator 2269 responsibility to ensure that the SNMP entity giving access to an 2270 instance of this MIB module is properly configured to give access to 2271 the objects only to those principals (users) that have legitimate 2272 rights to indeed GET or SET (change/create/delete) them. 2274 9. IANA Considerations 2276 [TODO] In order to comply with IESG policy as set forth in 2277 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 2278 submitted to the IESG for publication MUST contain an IANA 2279 Considerations section. The requirements for this section vary 2280 depending what actions are required of the IANA. see RFC4181 section 2281 3.5 for more information on writing an IANA clause for a MIB module 2282 document. 2284 [TODO] select an option and provide the necessary details. 2286 Option #1: 2288 The MIB module in this document uses the following IANA-assigned 2289 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2291 Descriptor OBJECT IDENTIFIER value 2292 ---------- ----------------------- 2294 sampleMIB { mib-2 XXX } 2296 Option #2: 2298 Editor's Note (to be removed prior to publication): the IANA is 2299 requested to assign a value for "XXX" under the 'mib-2' subtree and 2300 to record the assignment in the SMI Numbers registry. When the 2301 assignment has been made, the RFC Editor is asked to replace "XXX" 2302 (here and in the MIB module) with the assigned value and to remove 2303 this note. 2305 Note well: prior to official assignment by the IANA, a draft document 2306 MUST use placeholders (such as "XXX" above) rather than actual 2307 numbers. See RFC4181 Section 4.5 for an example of how this is done 2308 in a draft MIB module. 2310 Option #3: 2312 This memo includes no request to IANA. 2314 10. Contributors 2316 This MIB document uses the template authored by D. Harrington which 2317 is based on contributions from the MIB Doctors, especially Juergen 2318 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2320 11. Acknowledgements 2322 12. References 2324 12.1. Normative References 2326 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 2327 Interfaces Group MIB", RFC 2863, June 2000. 2329 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2330 Architecture for Describing Simple Network 2331 Management Protocol (SNMP) Management 2332 Frameworks", STD 62, RFC 3411, December 2002. 2334 [RFC3418] Presuhn, R., "Management Information Base (MIB) 2335 for the Simple Network Management Protocol 2336 (SNMP)", STD 62, RFC 3418, December 2002. 2338 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2339 Schoenwaelder, "Textual Conventions for 2340 Internet Network Addresses", RFC 4001, 2341 February 2005. 2343 [RFC2119] Bradner, S., "Key words for use in RFCs to 2344 Indicate Requirement Levels", BCP 14, RFC 2119, 2345 March 1997. 2347 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2348 Schoenwaelder, Ed., "Structure of Management 2349 Information Version 2 (SMIv2)", STD 58, 2350 RFC 2578, April 1999. 2352 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2353 Schoenwaelder, Ed., "Textual Conventions for 2354 SMIv2", STD 58, RFC 2579, April 1999. 2356 [RFC2580] McCloghrie, K., Perkins, D., and J. 2357 Schoenwaelder, "Conformance Statements for 2358 SMIv2", STD 58, RFC 2580, April 1999. 2360 [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast 2361 Forwarding", draft-ietf-manet-smf-10 (work in 2362 progress), March 2010. 2364 12.2. Informative References 2366 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 2367 Stewart, "Introduction and Applicability 2368 Statements for Internet-Standard Management 2369 Framework", RFC 3410, December 2002. 2371 Appendix A. Change Log 2373 This section tracks the revision history in the development of this 2374 SMF-MIB. It will be removed from the final version of this document. 2376 These changes were made from draft-ietf-manet-smf-mib-01 to 2377 draft-ietf-manet-smf-mib-02. 2379 1. Added the NotificationGroup to the MIB and updated the 2380 ConformanceGroup. 2382 2. Added the definition of an smfRouterID to the MIB. This is later 2383 used in the Notifications to indicate the origin of the event to 2384 the management station. 2386 3. Removed the Router Priority object as this was used only in the 2387 eCDS algorithm and hence should be contained within the future 2388 eCDS-MIB. 2390 4. Cleaned up the TEXTUAL CONVENTION for the `SmfOpMode'. 2392 5. Filled in some of the missing text in various object 2393 descriptions. 2395 These changes were made from draft-ietf-manet-smf-mib-00 to 2396 draft-ietf-manet-dsmf-mib-01. 2398 1. Editorial changes to the textual material. These included the 2399 addition of the paragraphs on TEXTUAL-CONVENTIONS defined and 2400 imported into this MIB and relationships to other MIBs. 2402 2. Identified those objects in the SMF-MIB requiring non-volatile 2403 storage. 2405 3. Changed the name of the TEXTUAL-CONVENTION 'Status', defined 2406 within this MIB to 'SmfStatus'. 2408 Appendix B. Open Issues 2410 This section contains the set of open issues related to the 2411 development and design of the SMF-MIB. This section will not be 2412 present in the final version of the MIB and will be removed once all 2413 the open issues have been resolved. 2415 1. The SMF draft states that use of the SMF Type Message TLV is 2416 optional and is used when the router runs NHDP. But the draft 2417 does not clearly state if the use of the SMF Address Block TLV is 2418 also optional. 2420 2. Is it useful to track the effectiveness of the coverage of the 2421 current RSSA? Is it possible to track this? 2423 3. Complete the security analysis and section. 2425 4. Cleanup all the [TODOs] from the MIB template. 2427 Appendix C. 2429 *************************************************************** 2430 * Note to the RFC Editor (to be removed prior to publication) * 2431 * * 2432 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2433 * of the MIB module point to this draft and are to be * 2434 * assigned by the RFC Editor. * 2435 * * 2436 * 2) The reference to RFCXXX2 throughout this document point * 2437 * to the current draft-ietf-manet-smf-xx.txt. This * 2438 * need to be replaced with the XXX RFC number. * 2439 * * 2440 *************************************************************** 2442 Authors' Addresses 2444 Robert G. Cole 2445 US Army CERDEC 2446 328 Hopkins Road, Bldg 245 2447 Aberdeen Proving Ground, Maryland 21005 2448 USA 2450 Phone: +1 410 278 6779 2451 EMail: robert.g.cole@us.army.mil 2452 URI: http://www.cs.jhu.edu/~rgcole/ 2454 Joseph Macker 2455 Naval Research Laboratory 2456 Washington, D.C. 20375 2457 USA 2459 EMail: macker@itd.nrl.navy.mil 2461 Brian Adamson 2462 Naval Research Laboratory 2463 Washington, D.C. 20375 2464 USA 2466 EMail: adamson@itd.nrl.navy.mil 2467 Sean Harnedy 2468 Booz Allen Hamilton 2469 333 City Boulevard West 2470 Orange, CA 92868 2471 USA 2473 EMail: harnedy_sean@bah.com