idnits 2.17.1 draft-ietf-manet-smf-mib-12.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1146 has weird spacing: '...(1) and ipv6(...' == 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. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: o 'smfCfgIpv6Dpd' - this writable configuration object sets the duplicate packet detection method for forwarding of IPv6 multicast packets. Since IPv6 SMF does specifies an option header, the interoperability constraints are not as loose as in the IPv4 version, and forwarders SHOULD not operate with mixed H-DPD and I-DPD modes. Hence the value for this object SHOULD be consistently set within the forwarders comprising the MANET, else inconsistent forwarding may result unnecessary multicast packet dropping. -- The document date (July 30, 2014) is 3559 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'SMF' is mentioned on line 520, but not defined == Missing Reference: 'RFC3932' is mentioned on line 2442, but not defined ** Obsolete undefined reference: RFC 3932 (Obsoleted by RFC 5742) == Missing Reference: 'RFC3626' is mentioned on line 2544, but not defined == Missing Reference: 'RFC5614' is mentioned on line 2550, but not defined Summary: 1 error (**), 0 flaws (~~), 9 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: January 31, 2015 B. Adamson 6 Naval Research Laboratory 7 July 30, 2014 9 Definition of Managed Objects for the Manet Simplified Multicast 10 Framework Relay Set Process 11 draft-ietf-manet-smf-mib-12 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 module also reports state 20 information, performance information, and notifications. In addition 21 to 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 January 31, 2015. 41 Copyright Notice 43 Copyright (c) 2014 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 5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 72 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 73 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 74 6.2. Relationship to the IP-MIB . . . . . . . . . . . . . . . . 9 75 6.3. Relationship to the IPMCAST-MIB . . . . . . . . . . . . . 10 76 6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 77 6.5. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 78 7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 11 79 8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 52 80 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56 81 10. Applicability Statement . . . . . . . . . . . . . . . . . . . 59 82 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 83 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63 84 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63 85 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 86 14.1. Normative References . . . . . . . . . . . . . . . . . . . 63 87 14.2. Informative References . . . . . . . . . . . . . . . . . . 64 88 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 65 90 1. Introduction 92 This memo defines a portion of the Management Information Base (MIB) 93 for use with network management protocols in the Internet community. 94 In particular, it describes objects for configuring aspects of a 95 process implementing Simplified Multicast Forwarding (SMF) [RFC6621] 96 for Mobile Ad-Hoc Networks (MANETs). SMF provides multicast 97 Duplicate Packet Detection (DPD) and supports algorithms for 98 constructing an estimate of a MANET Minimum Connected Dominating Set 99 (MCDS) for efficient multicast forwarding. The SMF-MIB module also 100 reports state information, performance information, and 101 notifications. In addition to configuration, this additional state 102 and performance information is useful to operators troubleshooting 103 multicast forwarding problems. 105 2. The Internet-Standard Management Framework 107 For a detailed overview of the documents that describe the current 108 Internet-Standard Management Framework, please refer to section 7 of 109 RFC 3410 [RFC3410]. 111 Managed objects are accessed via a virtual information store, termed 112 the Management Information Base or MIB. MIB objects are generally 113 accessed through the Simple Network Management Protocol (SNMP). 114 Objects in the MIB are defined using the mechanisms defined in the 115 Structure of Management Information (SMI). This memo specifies a MIB 116 module that is compliant to the SMIv2, which is described in STD 58, 117 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 118 [RFC2580]. 120 3. Conventions 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in RFC 2119 [RFC2119]. 126 4. Overview 128 SMF provides methods for implementing Duplicate Packet Detection 129 (DPD)-based multicast forwarding with the optional use of Connected 130 Dominating Set (CDS)-based relay sets. The CDS provides a complete 131 connected coverage of the nodes comprising the MANET. The Minimum 132 CDS (MCDS) is the smallest set of MANET nodes (comprising a connected 133 cluster) which cover all the nodes in the cluster with their 134 transmissions. As the density of the MANET nodes increase, the 135 fraction of nodes required in an MCDS decreases. Using the MCDS as a 136 multicast forwarding set then becomes an efficient multicast 137 mechanism for MANETs. 139 Various algorithms for the construction of estimates of the MCDS 140 exist. The Simplified Multicast Framework [RFC6621] describes some 141 of these. It further defines various operational modes for a node 142 which is participating in the collective creation of the MCDS 143 estimates. These modes depend upon the set of related MANET routing 144 and discovery protocols and mechanisms in operation in the specific 145 MANET node. 147 A SMF router's MIB module contains SMF process configuration 148 parameters (e.g. specific CDS algorithm), state information (e.g., 149 current membership in the CDS), performance counters (e.g., packet 150 counters), and notifications. 152 4.1. SMF Management Model 154 This section describes the management model for the SMF node process. 156 Figure 1 (reproduced from Figure 1 of [RFC6621]) shows the 157 relationship between the SMF Relay Set selection algorithm and the 158 related algorithms, processes and protocols running in the MANET 159 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 160 topology information gotten from the MANET Neighborhood Discovery 161 Protocol (NHDP), from the specific MANET routing protocol running on 162 the node, or from Layer 2 information passed up to the higher layer 163 protocol processes. 165 ______________ ____________ 166 | | | | 167 | Neighborhood | | Relay Set | 168 | Discovery |------------->| Selection | 169 | | neighbor | | 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 Router 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 interfaces such as defined by this MIB module. 193 o Tunable Configuration Objects - objects whose values affect timing 194 or attempt bounds on the SMF Relay Set (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 multicast 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 process. 212 o smfMIBObjects - defines the objects forming the basis for the SMF- 213 MIB module. These objects are divided up by function into the 214 following groups: 216 * Capabilities Group - This group contains the SMF objects that 217 the device uses to advertise its local capabilities with 218 respect to, e.g., the supported RSSAs. 220 * Configuration Group - This group contains the SMF objects that 221 configure specific options that determine the overall operation 222 of the SMF process and the resulting multicast performance. 224 * State Group - Contains information describing the current state 225 of the SMF process such as the Neighbor Table. 227 * Performance Group - Contains objects which help to characterize 228 the performance of the SMF process, typically counters for 229 statistical computations. 231 o smfMIBConformance - defines two, i.e., minimal and full, 232 conformance implementations for the SMF-MIB module. 234 5.1. Textual Conventions 236 The textual conventions defined within the SMF-MIB module are: 238 o The SmfStatus is defined within the SMF-MIB module. This contains 239 the current operational status of the SMF process on an interface. 241 The textual conventions defined for the SMF-MIB module and maintained 242 by IANA are: 244 o The IANAsmfOpModeIdTC represents an index that identifies a 245 specific SMF operational mode. This textual convention is 246 maintained by IANA in the IANA-SMF-MIB. 248 o The IANAsmfRssaIdTC represents an index that identifies, through 249 reference, a specific RSSA available for operation on the device. 250 This textual convention is maintained by IANA also in the IANA- 251 SMF-MIB. 253 5.2. The Capabilities Group 255 The SMF device supports a set of capabilities. The list of 256 capabilities which the device can advertise are: 258 o Operational Mode - topology information from NHDP, CDS-aware 259 unicast routing or Cross-layer from Layer 2. 261 o SMF RSSA - the specific RSSA operational on the device. Note that 262 configuration, state and performance objects related to a specific 263 RSSA must be defined within a separate MIB module. 265 5.3. The Configuration Group 267 The SMF device is configured with a set of controls. Some of the 268 prominent configuration controls for the SMF device are: 270 o Operational Mode - determines where topology information is 271 derived from, e.g., NHDP, CDS-aware unicast routing or Cross-layer 272 from Layer 2. 274 o SMF RSSA - the specific RSSA operational on the device. 276 o Duplicate Packet detection for IPv4 - Identification-based or 277 Hash-based DPD. 279 o Duplicate Packet detection for IPv6 - Identification-based or 280 Hash-based DPD. 282 o SMF Type Message TLV - if NHDP mode is selected, then the SMF Type 283 Message TLV MAY be included in the NHDP exchanges. 285 o SMF Address Block TLV - if NHDP mode is selected, then the SMF 286 Address Block TLV SHOULD be included in the NHDP exchanges. 288 o SMF Address Forwarding Table - a table identifying configured 289 multicast addresses to be forwarded by the SMF process. 291 5.4. The State Group 293 The State sub-tree reports current state information, e.g., 295 o Node RSSA State - identifies whether the node is currently in or 296 out of the Relay Set. 298 o Neighbors Table - a table containing current one-hop neighbors and 299 their operational RSSA. 301 5.5. The Performance Group 303 The Performance sub-tree reports primarily counters that relate to 304 SMF RSSA performance. The SMF performance counters consists of per 305 node and per interface objects: 307 o Total multicast packets received. 309 o Total multicast packets forwarded. 311 o Total duplicate multicast packets detected. 313 o Per interface statistics table with the following entries: 315 * Multicast packets received. 317 * Multicast packets forwarded. 319 * Duplicate multicast packets detected. 321 5.6. The Notifications Group 323 The Notifications Sub-tree contains the list of notifications 324 supported within the SMF-MIB module and their intended purpose and 325 utility. 327 5.7. Tables and Indexing 329 The SMF-MIB module contains a number of tables which record data 330 related to: 332 o configuration and operation of packet forwarding on the local 333 router, 335 o configuration and operation of local MANET interfaces on the 336 router, and 338 o configuration and operation of various RSSA algorithms for packet 339 forwarding. 341 The SMF-MIB module's tables are indexed via the following constructs: 343 o smfCapabilitiesIndex - the index identifying the combination of 344 SMF mode and SMF RSSA available on this device. 346 o smfCfgAddrForwardingIndex - the index to configured multicast 347 addresses lists which are forwarded by the SMF process. 349 o smfCfgIfIndex - the IfIndex of the interface on the local router 350 on which SMF is configured. 352 o smfStateNeighborIpAddrType, smfStateNeighborIpAddr, and 353 smfStateNeighborPrefixLen - the interface index set of specific 354 one-hop neighbor nodes to this local router. 356 These tables and their associated indexing are: 358 o smfCapabilitiesTable - identifies the resident set of (SMF 359 Operational Modes, SMF RSSA algorithms) available on this router. 360 This table has 'INDEX { smfCapabilitiesIndex }. 362 o smfCfgAddrForwardingTable - contains information on multicast 363 addresses which are to be forwarded by the SMF process on this 364 device. This table has 'INDEX { smfCfgAddrForwardingIndex }'. 366 o smfCfgInterfaceTable - describes the SMF interfaces on this device 367 that are participating in the SMF packet forwarding process. This 368 table has 'INDEX { smfCfgIfIndex }'. 370 o smfStateNeighborTable - describes the current neighbor nodes, 371 their addresses and the SMF RSSA and the interface on which they 372 can be reached. This table has 'INDEX { 373 smfStateNeighborIpAddrType, smfStateNeighborIpAddr, 374 smfStateNeighborPrefixLen }'. 376 o smfPerfIpv4InterfacePerfTable - contains the IPv4 related SMF 377 statistics per each SMF interface on this device. This table has 378 'INDEX { smfCfgIfIndex }'. 380 o smfPerfIpv6InterfacePerfTable - contains the IPv6 related SMF 381 statistics per each SMF interface on this device. This table has 382 'INDEX { smfCfgIfIndex }'. 384 6. Relationship to Other MIB Modules 386 6.1. Relationship to the SNMPv2-MIB 388 The 'system' group in the SNMPv2-MIB module [RFC3418] is defined as 389 being mandatory for all systems, and the objects apply to the entity 390 as a whole. The 'system' group provides identification of the 391 management entity and certain other system-wide data. The SMF-MIB 392 module does not duplicate those objects. 394 6.2. Relationship to the IP-MIB 396 It is an expectation that SMF devices will implement the standard IP- 397 MIB module [RFC4293]. Exactly how to integrate SMF packet handling 398 and management into the standard IP-MIB module management are part of 399 the experiment. 401 The SMF-MIB module counters within the smfPerformanceGroup count 402 packets handled by the system and interface local SMF process (as 403 discussed above). Not all IP (unicast and multicast) packets on a 404 device interface are handled by the SMF process. So the counters are 405 tracking different packet streams in the IP-MIB and SMF-MIB modules. 407 6.3. Relationship to the IPMCAST-MIB 409 The smfCfgAddrForwardingTable is essentially a filter table (if 410 populated) that identifies addresses/packets to be forwarded via the 411 local SMF flooding process. The RFC 5132 IP Multicast MIB module 412 [RFC5132] manages objects related to standard IP multicast, which 413 could be running in parallel to SMF on the device. 415 RFC 5132 manages traditional IP-based multicast (based upon multicast 416 routing mechanisms). The SMF-MIB module provides management for a 417 MANET subnet-based flooding mechanism which, may be used for 418 multicast transport (through SMF broadcast) depending upon the MANET 419 dynamics and other factors regarding the MANET subnet. Further, they 420 may co-exist in certain MANET deployments using the 421 smfCfgAddrForwardingTable to hand certain IP multicast addresses to 422 the SMF process and other IP multicast packets to be forwarded by 423 other IP routed-based multicast mechanisms. SMF and the associated 424 SMF-MIB module are experimental and these are some of the experiments 425 to be had with SMF and the SMF-MIB module. 427 6.4. MIB modules required for IMPORTS 429 The textual conventions imported for use in the SMF-MIB module are as 430 follows. The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 431 Counter32, Unsigned32, Integer32 and mib-2 textual conventions are 432 imported from RFC 2578 [RFC2578]. The TEXTUAL-CONVENTION, RowStatus 433 and TruthValue textual conventions are imported from RFC 2579 434 [RFC2579]. The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION- 435 GROUP textual conventions are imported from RFC 2580 [RFC2580]. The 436 InterfaceIndexOrZero textual convention is imported from RFC 2863 437 [RFC2863]. The SnmpAdminString textual convention is imported from 438 RFC 3411 [RFC3411]. The InetAddress, InetAddressType and 439 InetAddressPrefixLength textual conventions are imported from RFC 440 4001 [RFC4001]. 442 6.5. Relationship to the Future RSSA-MIB Moduless 444 In a sense, the SMF-MIB module is a general front-end to a set of, 445 yet to be developed, RSSA-specific MIB modules. These RSSA-specific 446 MIB modules will define the objects for the configuration, state, 447 performance and notification required for the operation of these 448 specific RSSAs. The SMF-MIB module Capabilities Group allows the 449 remote management station the ability to query the router to discover 450 the set of supported RSSAs. 452 7. SMF-MIB Definitions 454 SMF-MIB DEFINITIONS ::= BEGIN 456 IMPORTS 458 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 459 Counter32, Integer32, TimeTicks, experimental 460 FROM SNMPv2-SMI -- [RFC2578] 462 TEXTUAL-CONVENTION, RowStatus, TruthValue 463 FROM SNMPv2-TC -- [RFC2579] 465 MODULE-COMPLIANCE, OBJECT-GROUP, 466 NOTIFICATION-GROUP 467 FROM SNMPv2-CONF -- [RFC2580] 469 InterfaceIndexOrZero, ifName 470 FROM IF-MIB -- [RFC2863] 472 SnmpAdminString 473 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 475 InetAddress, InetAddressType, 476 InetAddressPrefixLength 477 FROM INET-ADDRESS-MIB -- [RFC4001] 479 IANAsmfOpModeIdTC 480 FROM IANA-SMF-MIB 482 IANAsmfRssaIdTC 483 FROM IANA-SMF-MIB 484 ; 486 smfMIB MODULE-IDENTITY 487 LAST-UPDATED "201407301300Z" -- July 30, 2014 488 ORGANIZATION "IETF MANET Working Group" 489 CONTACT-INFO 490 "WG E-Mail: manet@ietf.org 492 WG Chairs: sratliff@cisco.com 493 jmacker@nrl.navy.mil 495 Editors: Robert G. Cole 496 US Army CERDEC 497 Space and Terrestrial Communications 498 6010 Frankford Road 499 Aberdeen Proving Ground, MD 21005 500 USA 501 +1 443 395-8744 502 robert.g.cole@us.army.mil 504 Joseph Macker 505 Naval Research Laboratory 506 Washington, D.C. 20375 507 USA 508 macker@itd.nrl.navy.mil 510 Brian Adamson 511 Naval Research Laboratory 512 Washington, D.C. 20375 513 USA 514 adamson@itd.nrl.navy.mil" 516 DESCRIPTION 517 "This MIB module contains managed object definitions for 518 the Manet SMF RSSA process defined in: 520 [SMF] Macker, J.(ed.), 521 Simplified Multicast Forwarding, RFC 6621, 522 May 2012. 524 Copyright (C) The IETF Trust (2014). This version 525 of this MIB module is part of RFC xxxx; see the RFC 526 itself for full legal notices." 528 -- Revision History 529 REVISION "201407301300Z" -- July 30, 2014 530 DESCRIPTION 531 "The first version of this MIB module, 532 published as RFC xxxx. 533 " 534 -- RFC-Editor assigns xxxx 535 ::= { experimental xxxx } -- to be assigned by IANA 537 -- 538 -- TEXTUAL CONVENTIONs 539 -- 541 SmfStatus ::= TEXTUAL-CONVENTION 542 STATUS current 543 DESCRIPTION 544 "An indication of the operability of a SMF 545 function or feature. For example, the status 546 of an interface: 'enabled' indicates that 547 this interface is performing SMF functions, 548 and 'disabled' indicates that it is not. 549 Similarly for the status of the device: 550 'enabled' indicates that the device has 551 enabled the SMF functions on the device and 552 'disabled' means that the device and all interfaces 553 have disabled all SMF functions." 554 SYNTAX INTEGER { 555 enabled (1), 556 disabled (2) 557 } 559 -- 560 -- Top-Level Object Identifier Assignments 561 -- 563 smfMIBNotifications OBJECT IDENTIFIER ::= { smfMIB 0 } 564 smfMIBObjects OBJECT IDENTIFIER ::= { smfMIB 1 } 565 smfMIBConformance OBJECT IDENTIFIER ::= { smfMIB 2 } 567 -- 568 -- smfMIBObjects Assignments: 569 -- smfCapabilitiesGroup - 1 570 -- smfConfigurationGroup - 2 571 -- smfStateGroup - 3 572 -- smfPerformanceGroup - 4 573 -- 575 -- 576 -- smfCapabilitiesGroup 577 -- 578 -- This group contains the SMF objects that identify specific 579 -- capabilities within this device related to SMF functions. 580 -- 582 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 584 -- 585 -- SMF Capabilities Table 586 -- 588 smfCapabilitiesTable OBJECT-TYPE 589 SYNTAX SEQUENCE OF SmfCapabilitiesEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "The smfCapabilitiesTable identifies the 594 resident set of SMF Operational Modes and 595 RSSA combinations that can run on this 596 forwarder." 597 REFERENCE 598 "See Section 7.2. 'Reduced Relay Set Forwarding', 599 Section 8.1.1. 'SMF Message TLV Type', and 600 the Appendices A, B and C in 601 RFC 6621 - Simplified Multicast Forwarding 602 (SMF), Macker, J., May 2012." 603 ::= { smfCapabilitiesGroup 1 } 605 smfCapabilitiesEntry OBJECT-TYPE 606 SYNTAX SmfCapabilitiesEntry 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "Information about a particular operational 611 mode and RSSA combination. 612 " 613 INDEX { smfCapabilitiesIndex } 614 ::= { smfCapabilitiesTable 1 } 616 SmfCapabilitiesEntry ::= SEQUENCE { 617 smfCapabilitiesIndex Integer32, 618 smfCapabilitiesOpModeID IANAsmfOpModeIdTC, 619 smfCapabilitiesRssaID IANAsmfRssaIdTC 620 } 622 smfCapabilitiesIndex OBJECT-TYPE 623 SYNTAX Integer32 (1..2147483647) 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "The index for this entry; a unique value, 628 greater than zero, for each combination of 629 a particular operational mode and RSSA 630 algorithm available on this device. 631 It is recommended that values are assigned 632 contiguously starting from 1. 634 Rows in this table are automatically 635 populated by the entity's management system 636 on initialization. 638 By default, the agent should support at least the 639 Classical Flooding 'cF' algorithm. All compliant 640 SMF forwarders must support Classical Flooding. 641 Hence, the first entry in this table MUST exist 642 and MUST be defined as: 644 smfCapabilitiesIndex i '1' 645 smfCapabilitiesOpModeID i 'cfOnly(1)' 646 smfCapabilitiesRssaID i 'cF(1)' 648 The value for each combination MUST remain 649 constant at least from one re-initialization 650 of the entity's management system to the 651 next re-initialization." 652 ::= { smfCapabilitiesEntry 1 } 654 smfCapabilitiesOpModeID OBJECT-TYPE 655 SYNTAX IANAsmfOpModeIdTC 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "This object identifies 660 the particular operational mode for this device." 661 ::= { smfCapabilitiesEntry 2 } 663 smfCapabilitiesRssaID OBJECT-TYPE 664 SYNTAX IANAsmfRssaIdTC 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION 668 "This object identifies 669 the particular RSSA algorithm in this MIB 670 module. Example RSSAs are found in the 671 appendix of RFC 6621." 672 REFERENCE 673 "See, e.g., Section 8.1.1. 'SMF Message TLV Type', 674 and the Appendices A, B and C in 675 RFC 6621 - Simplified Multicast Forwarding 676 (SMF), Macker, J., May 2012." 677 ::= { smfCapabilitiesEntry 3 } 679 -- 680 -- smfConfigurationGroup 681 -- 682 -- This group contains the SMF objects that configure specific 683 -- options that determine the overall performance and operation 684 -- of the multicast forwarding process for the router device 685 -- and its interfaces. 686 -- 688 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 690 smfCfgAdminStatus OBJECT-TYPE 691 SYNTAX SmfStatus 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "The configured status of the SMF process 696 on this device. 'enabled(1)' means that 697 SMF is configured to run on this device. 698 'disabled(2)' mean that the SMF process 699 is configured off. 701 Prior to SMF functions being performed over 702 specific interfaces, this object must first 703 be 'enabled'. If this object is 'disabled', 704 then no SMF functions are being performed on 705 the device and all smfCfgIfAdminStatus objects 706 MUST also be set to 'disabled'. When this 707 object is changed from 'enabled' to 'disabled' 708 by the manager, then all smfCfgIfAdminStatus 709 objects MUST also be automatically set to 710 'disabled' by the agent. 712 The default value for this object SHOULD be 713 'enabled'. 715 This object is persistent and when written 716 the entity SHOULD save the change to 717 non-volatile storage." 718 DEFVAL { enabled } 719 ::= { smfConfigurationGroup 1 } 721 smfCfgSmfSysUpTime OBJECT-TYPE 722 SYNTAX TimeTicks 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "The time (in hundredths of a second) since the 727 system SMF process was last re-initialized. 728 The SMF process is re-initialized when the 729 value of the 'smfCfgAdminStatus' object 730 transitions to 'enabled' from either a prior 731 value of 'disabled' or upon initialization 732 of this device." 734 ::= { smfConfigurationGroup 2 } 736 smfCfgRouterIDAddrType OBJECT-TYPE 737 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 738 MAX-ACCESS read-write 739 STATUS current 740 DESCRIPTION 741 "The address type of the address used for 742 SMF ID of this router as specified 743 in the 'smfCfgRouterID' next. 745 Only the values ipv4(1) and ipv6(2) 746 are supported. 748 This object is persistent and when written 749 the entity SHOULD save the change to 750 non-volatile storage." 751 DEFVAL { ipv4 } 752 ::= { smfConfigurationGroup 3 } 754 smfCfgRouterID OBJECT-TYPE 755 SYNTAX InetAddress (SIZE(4|16)) 756 MAX-ACCESS read-write 757 STATUS current 758 DESCRIPTION 759 "The IP address used as the SMF router ID. 760 This can be set by the management station. 761 If not explicitly set, then the device 762 SHOULD select a routable IP address 763 assigned to this router for use as 764 the 'smfCfgRouterID'. 766 The smfCfgRouterID is a logical identification 767 that MUST be consistent across interoperable 768 SMF neighborhoods and it is RECOMMENDED to be 769 chosen as the numerically largest address 770 contained in a node's 'Neighbor Address List' 771 as defined in NHDP. A smfCfgRouterID MUST be 772 unique within the scope of the operating 773 MANET network regardless of the method used 774 for selecting it. 776 This object is persistent and when written 777 the entity SHOULD save the change to 778 non-volatile storage." 779 REFERENCE 780 "See, e.g., 781 Appendix Section A.1. 'E-CDS Relay Set 782 Selection Overview' and 784 Appendix Secdtion C.1. 'MPR-CDS Relay 785 Set Selection Overview' 787 in RFC 6621 - Simplified Multicast Forwarding 788 (SMF), Macker, J., May 2012." 789 ::= { smfConfigurationGroup 4 } 791 smfCfgOperationalMode OBJECT-TYPE 792 SYNTAX Integer32 (1..2147483647) 793 MAX-ACCESS read-write 794 STATUS current 795 DESCRIPTION 796 "The SMF RSS node operational mode and 797 RSSA algorithm combination active on this 798 local forwarder. This object is defined 799 to be equal to the smfCapabilitiesIndex 800 which identifies the specific active 801 operational mode and RSSA. 803 The default value for this object is 804 '1' which corresponds to: 806 smfCapabilitiesOpModeID i 'cfOnly(1)' 807 smfCapabilitiesRssaID i 'cF(1)' 809 This object is persistent and when written 810 the entity SHOULD save the change to 811 non-volatile storage." 812 REFERENCE 813 "See Section 7.2. 'Reduced Relay Set Forwarding', 814 and the Appendices A, B and C in 815 RFC 6621 - Simplified Multicast Forwarding 816 (SMF), Macker, J., May 2012." 817 DEFVAL { 1 } 818 ::= { smfConfigurationGroup 5 } 820 smfCfgRssaMember OBJECT-TYPE 821 SYNTAX INTEGER { 822 potential(1), 823 always(2), 824 never(3) 825 } 826 MAX-ACCESS read-write 827 STATUS current 828 DESCRIPTION 829 "The RSSA downselects a set of forwarders for 830 multicast forwarding. Sometimes it is useful 831 to force an agent to be included or excluded 832 from the resulting RSS. This object is a 833 switch to allow for this behavior. 835 The value 'potential(1)' allows the selected 836 RSSA to determine if this agent is included 837 or excluded from the RSS. 839 The value 'always(2)' forces the selected 840 RSSA include this agent in the RSS. 842 The value 'never(3)' forces the selected 843 RSSA to exclude this agent from the RSS. 845 The default setting for this object is 846 'potential(1)'. Other settings could pose 847 operational risks under certain conditions. 849 This object is persistent and when written 850 the entity SHOULD save the change to 851 non-volatile storage." 852 REFERENCE 853 "See Section 7. 'Relay Set Selection' in 854 RFC 6621 - Simplified Multicast Forwarding 855 (SMF), Macker, J., May 2012." 856 DEFVAL { potential } 857 ::= { smfConfigurationGroup 6 } 859 smfCfgIpv4Dpd OBJECT-TYPE 860 SYNTAX INTEGER { 861 hashBased(1), 862 identificationBased(2) 863 } 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 "The current method for IPv4 duplicate packet 868 detection. 870 The value 'hashBased(1)' indicates that the 871 routers duplicate packet detection is based 872 upon comparing a hash over the packet fields. 873 This is the default setting for this object. 875 The value 'identificationBased(2)' 876 indicates that the duplicate packet 877 detection relies upon header information 878 in the multicast packets to identify 879 previously received packets. 881 This object is persistent and when written 882 the entity SHOULD save the change to 883 non-volatile storage." 884 REFERENCE 885 "See Section 6.2. 'IPv4 Duplicate Packet 886 Detection' in RFC 6621 - Simplified 887 Multicast Forwarding (SMF), Macker, J., 888 May 2012." 889 DEFVAL { hashBased } 890 ::= { smfConfigurationGroup 7 } 892 smfCfgIpv6Dpd OBJECT-TYPE 893 SYNTAX INTEGER { 894 hashBased(1), 895 identificationBased(2) 896 } 897 MAX-ACCESS read-write 898 STATUS current 899 DESCRIPTION 900 "The current method for IPv6 duplicate packet 901 detection. 903 The values indicate the type of method used 904 for duplicate packet detection as described 905 the previous description for the object 906 `smfCfgIpv4Dpd'. 908 The default value for this object is 909 'hashBased(1)'. 911 This object is persistent and when written 912 the entity SHOULD save the change to 913 non-volatile storage." 914 REFERENCE 915 "See Section 6.1. 'IPv6 Duplicate Packet 916 Detection' in RFC 6621 - Simplified 917 Multicast Forwarding (SMF), Macker, J., 918 May 2012." 919 DEFVAL { hashBased } 920 ::= { smfConfigurationGroup 8 } 922 smfCfgMaxPktLifetime OBJECT-TYPE 923 SYNTAX Integer32 (0..65535) 924 UNITS "Seconds" 925 MAX-ACCESS read-write 926 STATUS current 927 DESCRIPTION 928 "The estimate of the network packet 929 traversal time. 931 This object is persistent and when written 932 the entity SHOULD save the change to 933 non-volatile storage." 934 REFERENCE 935 "See Section 6. 'SMF Duplicate Packet 936 Detection' in RFC 6621 - Simplified 937 Multicast Forwarding (SMF), Macker, J., 938 May 2012." 939 DEFVAL { 60 } 940 ::= { smfConfigurationGroup 9 } 942 smfCfgDpdEntryMaxLifetime OBJECT-TYPE 943 SYNTAX Integer32 (0..65525) 944 UNITS "Seconds" 945 MAX-ACCESS read-write 946 STATUS current 947 DESCRIPTION 948 "The maximum lifetime of a cached DPD 949 record in the local device storage. 951 If the memory is running low prior to the 952 MaxLifetime being exceeded, the local SMF 953 devices should purge the oldest records first. 955 This object is persistent and when written 956 the entity SHOULD save the change to 957 non-volatile storage." 958 REFERENCE 959 "See Section 6. 'SMF Duplicate Packet 960 Detection' in RFC 6621 - Simplified 961 Multicast Forwarding (SMF), Macker, J., 962 May 2012." 963 DEFVAL { 600 } 964 ::= { smfConfigurationGroup 10 } 966 -- 967 -- Configuration of messages to be included in 968 -- NHDP message exchanges in support of SMF 969 -- operations. 970 -- 971 smfCfgNhdpRssaMesgTLVIncluded OBJECT-TYPE 972 SYNTAX TruthValue 973 MAX-ACCESS read-write 974 STATUS current 975 DESCRIPTION 976 "Indicates whether the associated NHDP messages 977 include the RSSA Message TLV, or not. This 978 is an optional SMF operational setting. 979 The value 'true(1)' indicates that this TLV is 980 included; the value 'false(2)' indicates that it 981 is not included. 983 It is RECOMMENDED that the RSSA Message TLV 984 be included in the NHDP messages. 986 This object is persistent and when written 987 the entity SHOULD save the change to 988 non-volatile storage." 989 REFERENCE 990 "See Section 8.1.1. 'SMF Message TLV Type' in 991 RFC 6621 - Simplified Multicast Forwarding 992 (SMF), Macker, J., May 2012." 993 DEFVAL { true } 994 ::= { smfConfigurationGroup 11 } 996 smfCfgNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 997 SYNTAX TruthValue 998 MAX-ACCESS read-write 999 STATUS current 1000 DESCRIPTION 1001 "Indicates whether the associated NHDP messages 1002 include the RSSA Address Block TLV, or not. 1003 This is an optional SMF operational setting. 1004 The value 'true(1)' indicates that this TLV is 1005 included; the value 'false(2)' indicates that it 1006 is not included. 1008 The smfCfgNhdpRssaAddrBlockTLVIncluded is optional 1009 in all cases as it depends on the existence of 1010 an address block which may not be present. 1011 If this SMF device is configured with NHDP, 1012 then this object SHOULD be set to 'true(1)'. 1014 This object is persistent and when written 1015 the entity SHOULD save the change to 1016 non-volatile storage." 1017 REFERENCE 1018 "See Section 8.1.2. 'SMF Address Block TLV 1019 Type' in RFC 6621 - Simplified Multicast 1020 Forwarding (SMF), Macker, J., May 2012." 1021 DEFVAL { true } 1022 ::= { smfConfigurationGroup 12 } 1024 -- 1025 -- Table identifying configured multicast addresses to be forwarded. 1026 -- 1028 smfCfgAddrForwardingTable OBJECT-TYPE 1029 SYNTAX SEQUENCE OF SmfCfgAddrForwardingEntry 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "The smfCfgAddrForwardingTable is essentially a filter 1034 table (if populated) that identifies addresses/packets 1035 to be forwarded viaathe local SMF flooding process. 1036 The RFC 5132 IP Multicast MIB module manages objects 1037 related to standard IP multicast, which could be running 1038 in parallel to SMF on the device. 1040 RFC 5132 manages traditional IP-based multicast (based 1041 upon multicast routing mechanisms). The SMF-MIB module 1042 provides management for a MANET subnet-based flooding 1043 mechanism which, may be used for multicast transport 1044 (through SMF broadcast) depending upon the MANET dynamics 1045 and other factors regarding the MANET subnet. Further, 1046 they may co-exist in certain MANET deployments 1047 using the smfCfgAddrForwardingTable to hand certain IP 1048 multicast addresses to the SMF process and other IP 1049 multicast packets to be forwarded by other IP 1050 routed-based multicast mechanisms. SMF and the 1051 associated SMF-MIB module are experimental and these 1052 are some of the experiments to be had with SMF and 1053 the SMF-MIB module. 1055 This is the (conceptual) table containing information on 1056 multicast addresses which are to be forwarded by the SMF 1057 process. This table represents an IP filters table for 1058 forwarding (or not) packets based upon their IP 1059 multicast address. 1061 The SMF process can be configured to forward only those 1062 multicast addresses found within the 1063 smfCfgAddrForwardingTable. As such, addresses which are 1064 to be forwarded by the SMF process MUST be found within 1065 the address ranges configured within this table, unless 1066 this table is empty. 1068 Each row is associated with a range of multicast 1069 addresses, and ranges for different rows must be disjoint. 1070 Different rows MAY share a common 1071 smfCfgAddrForwardingGroupName to administratively 1072 associate different rows. 1074 The objects in this table are persistent and when written 1075 the entity SHOULD save the change to non-volatile storage." 1076 REFERENCE 1077 "See Section 9.1. 'Forwarded Multicast Groups' in 1078 RFC 6621 - Simplified Multicast Forwarding 1079 (SMF), Macker, J., May 2012." 1080 ::= { smfConfigurationGroup 13 } 1082 smfCfgAddrForwardingEntry OBJECT-TYPE 1083 SYNTAX SmfCfgAddrForwardingEntry 1084 MAX-ACCESS not-accessible 1085 STATUS current 1086 DESCRIPTION 1087 "An entry (conceptual row) containing the information on a 1088 particular multicast scope." 1089 INDEX { smfCfgAddrForwardingIndex } 1090 ::= { smfCfgAddrForwardingTable 1 } 1092 SmfCfgAddrForwardingEntry ::= SEQUENCE { 1093 smfCfgAddrForwardingIndex Integer32, 1094 smfCfgAddrForwardingGroupName SnmpAdminString, 1095 smfCfgAddrForwardingAddrType InetAddressType, 1096 smfCfgAddrForwardingAddress InetAddress, 1097 smfCfgAddrForwardingAddrPrefixLength 1098 InetAddressPrefixLength, 1099 smfCfgAddrForwardingStatus RowStatus 1100 } 1102 smfCfgAddrForwardingIndex OBJECT-TYPE 1103 SYNTAX Integer32 (1..2147483647) 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "This object identifies an unique entry 1108 for a forwarding group. The index for 1109 this entry is a unique value, 1110 greater than zero, for each row. 1111 It is recommended that values are assigned 1112 contiguously starting from 1. 1114 The value for each row index MUST remain 1115 constant from one re-initialization 1116 of the entity's management system to the 1117 next re-initialization." 1118 ::= { smfCfgAddrForwardingEntry 1 } 1120 smfCfgAddrForwardingGroupName OBJECT-TYPE 1121 SYNTAX SnmpAdminString 1122 MAX-ACCESS read-create 1123 STATUS current 1124 DESCRIPTION 1125 "This object identifies a group name for a set of 1126 row entries in order to administratively associate 1127 a set of address ranges. 1129 If there is no group name or this object is 1130 otherwise not applicable, then this object contains 1131 a zero-length string. 1133 This object is persistent and when written 1134 the entity SHOULD save the change to 1135 non-volatile storage." 1136 ::= { smfCfgAddrForwardingEntry 2 } 1138 smfCfgAddrForwardingAddrType OBJECT-TYPE 1139 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1140 MAX-ACCESS read-create 1141 STATUS current 1142 DESCRIPTION 1143 "The type of the addresses in the multicast 1144 forwarding ranges identified by this table. 1146 Only the values ipv4(1) and ipv6(2) are 1147 supported. 1149 This object is persistent and when written 1150 the entity SHOULD save the change to 1151 non-volatile storage." 1152 ::= { smfCfgAddrForwardingEntry 3 } 1154 smfCfgAddrForwardingAddress OBJECT-TYPE 1155 SYNTAX InetAddress (SIZE(4|16)) 1156 MAX-ACCESS read-create 1157 STATUS current 1158 DESCRIPTION 1159 "The multicast group address which, when 1160 combined with smfCfgAddrForwardingAddrPrefixLength, 1161 gives the group prefix for this forwarding range. 1163 The InetAddressType is given by 1164 smfCfgAddrForwardingAddrType. 1166 This address object is only significant up to 1167 smfCfgAddrForwardingAddrPrefixLength bits. The 1168 remaining address bits are set to zero. This is 1169 especially important for this index field, 1170 Any non-zero bits would signify an entirely 1171 different entry. 1173 Legal values correspond to the subset of address 1174 families for which multicast address allocation 1175 is supported. 1177 This object is persistent and when written 1178 the entity SHOULD save the change to 1179 non-volatile storage." 1180 ::= { smfCfgAddrForwardingEntry 4 } 1182 smfCfgAddrForwardingAddrPrefixLength OBJECT-TYPE 1183 SYNTAX InetAddressPrefixLength 1184 MAX-ACCESS read-create 1185 STATUS current 1186 DESCRIPTION 1187 "The length in bits of the mask which, when 1188 combined with smfCfgAddrForwardingAddress, 1189 gives the group prefix for this forwarding 1190 range. 1192 This object is persistent and when written 1193 the entity SHOULD save the change to 1194 non-volatile storage." 1195 ::= { smfCfgAddrForwardingEntry 5 } 1197 smfCfgAddrForwardingStatus OBJECT-TYPE 1198 SYNTAX RowStatus 1199 MAX-ACCESS read-create 1200 STATUS current 1201 DESCRIPTION 1202 "The status of this row, by which new entries may be 1203 created, or old entries deleted from this table." 1204 ::= { smfCfgAddrForwardingEntry 6 } 1206 -- 1207 -- SMF Interfaces Configuration Table 1208 -- 1209 smfCfgInterfaceTable OBJECT-TYPE 1210 SYNTAX SEQUENCE OF SmfCfgInterfaceEntry 1211 MAX-ACCESS not-accessible 1212 STATUS current 1213 DESCRIPTION 1214 "The SMF Interface Table describes the SMF 1215 interfaces that are participating in the 1216 SMF packet forwarding process. The ifIndex is 1217 from the interfaces group defined in the 1218 Interfaces Group MIB module (RFC 2863). As such, 1219 this table 'sparse augments' the ifTable 1220 specifically when SMF is to be configured to 1221 operate over this interface. 1223 A conceptual row in this table exists if and only 1224 if either a manager has explicitly created the row 1225 or there is an interface on the managed device 1226 that automatically supports and runs SMF as part 1227 of the device's initialization process. 1229 The manager creates a row in this table by setting 1230 rowStatus to 'createAndGo' or 'createAndWait'. 1231 Row objects having associated DEFVAL clauses are 1232 automatically defined by the agent with these 1233 values during row creation, unless the manager 1234 explicitly defines these object values during the 1235 row creation. 1237 As the smfCfgInterfaceTable sparsely augments the 1238 IfTable. Hence, 1240 + an entry cannot exist in smfCfgInterfaceTable 1241 without a corresponding entry in the ifTable. 1243 + if an entry in the ifTable is removed, the 1244 corresponding entry (if it exists) in the 1245 smfCfgInterfaceTable MUST be removed. 1247 + the smfCfgIfStatus can have a value of 1248 'enabled' or 'disabled' independent of the 1249 current value of the ifAdminStatus of the 1250 corresponding entry in the ifTable. 1252 The values of the objects smfCfgAdminStatus and 1253 smfCfgIfAdminStatus reflect the up-down status of 1254 the SMF process running on the device and on the 1255 specific interfaces respectively. Hence, 1256 + the value of the smfCfgAdminStatus can be 1257 'enabled' or 'disabled' reflecting the current 1258 running status of the SMF process on the device. 1260 + the value of the smfCfgIfAdminStatus can be 1261 'enabled' or 'disabled' if the value of the 1262 smfCfgAdminStatus is set to 'enabled'. 1264 + if the value of the smfCfgAdminStatus is 1265 'disabled', then the corresponding 1266 smfCfgIfAdminStatus objects MUST be set 1267 to 'disabled' in the smfCfgInterfaceTable. 1269 + once the value of the smfCfgAdminStatus changes 1270 from 'disabled' to 'enabled', it is up to the 1271 management system to make the corresponding 1272 changes to the smfCfgIfAdminStatus values 1273 back to 'enabled'. 1274 " 1275 REFERENCE 1276 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1277 K., and F. Kastenholtz, June 2000." 1278 ::= { smfConfigurationGroup 14 } 1280 smfCfgInterfaceEntry OBJECT-TYPE 1281 SYNTAX SmfCfgInterfaceEntry 1282 MAX-ACCESS not-accessible 1283 STATUS current 1284 DESCRIPTION 1285 "The SMF interface entry describes one SMF 1286 interface as indexed by its ifIndex. 1288 The objects in this table are persistent and when 1289 written the device SHOULD save the change to 1290 non-volatile storage. For further information 1291 on the storage behavior for these objects, refer 1292 to the description for the smfCfgIfRowStatus 1293 object." 1294 INDEX { smfCfgIfIndex } 1295 ::= { smfCfgInterfaceTable 1 } 1297 SmfCfgInterfaceEntry ::= 1298 SEQUENCE { 1299 smfCfgIfIndex InterfaceIndexOrZero, 1300 smfCfgIfAdminStatus SmfStatus, 1301 smfCfgIfSmfUpTime TimeTicks, 1302 smfCfgIfRowStatus RowStatus 1303 } 1305 smfCfgIfIndex OBJECT-TYPE 1306 SYNTAX InterfaceIndexOrZero 1307 MAX-ACCESS not-accessible 1308 STATUS current 1309 DESCRIPTION 1310 "The ifIndex for this SMF interface. This value 1311 MUST correspond to an ifIndex referring 1312 to a valid entry in The Interfaces Table. 1313 If the manager attempts to create a row 1314 for which the ifIndex does not exist on the 1315 local device, then the agent SHOULD issue 1316 a return value of 'inconsistentValue' and 1317 the operation SHOULD fail." 1318 REFERENCE 1319 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 1320 K., and F. Kastenholtz, June 2000." 1321 ::= { smfCfgInterfaceEntry 1 } 1323 smfCfgIfAdminStatus OBJECT-TYPE 1324 SYNTAX SmfStatus 1325 MAX-ACCESS read-create 1326 STATUS current 1327 DESCRIPTION 1328 "The SMF interface's administrative status. 1329 The value 'enabled' denotes that the interface 1330 is running the SMF forwarding process. 1331 The value 'disabled' denotes that the interface is 1332 currently external to the SMF forwarding process. 1334 When the value of the smfCfgAdminStatus is 1335 'disabled', then the corresponding smfCfgIfAdminStatus 1336 objects MUST be set to 'disabled' in the 1337 smfCfgInterfaceTable. 1339 The default value for this object is 'enabled(1)'. 1341 This object SHOULD be persistent and when 1342 written the device SHOULD save the change to 1343 non-volatile storage." 1344 DEFVAL { enabled } 1345 ::= { smfCfgInterfaceEntry 2 } 1347 smfCfgIfSmfUpTime OBJECT-TYPE 1348 SYNTAX TimeTicks 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "The time (in hundredths of a second) since 1353 this interface SMF process was last 1354 re-initialized. The interface SMF process 1355 is re-initialized when the corresponding 1356 'smfCfgIfRowStatus' object transits to 1357 the 'active' state." 1358 ::= { smfCfgInterfaceEntry 3 } 1360 smfCfgIfRowStatus OBJECT-TYPE 1361 SYNTAX RowStatus 1362 MAX-ACCESS read-create 1363 STATUS current 1364 DESCRIPTION 1365 "This object permits management of this table 1366 by facilitating actions such as row creation, 1367 construction, and destruction. The value of 1368 this object has no effect on whether other 1369 objects in this conceptual row can be 1370 modified. 1372 An entry may not exist in the 'active' state unless all 1373 objects in the entry have a defined appropriate value. For 1374 objects with DEFVAL clauses, the management station 1375 does not need to specify the value of these objects in order 1376 for the row to transit to the 'active' state; the default 1377 value for these objects is used. For objects that do not 1378 have DEFVAL clauses, then the network manager MUST 1379 specify the value of these objects prior to this row 1380 transitioning to the 'active' state. 1382 When this object transitions to 'active', all objects 1383 in this row SHOULD be written to non-volatile (stable) 1384 storage. Read-create objects in this row MAY be modified. 1385 When an object in a row with smfCfgIfRowStatus of 'active' 1386 is changed, then the updated value MUST be reflected in SMF 1387 and this new object value MUST be written to non-volatile 1388 storage. 1390 If this object is not equal to 'active', all associated 1391 entries in the smfPerfIpv4InterfacePerfTable and the 1392 smfPerfIpv6InterfacePerfTable MUST be deleted." 1393 ::= { smfCfgInterfaceEntry 4 } 1395 -- 1396 -- smfStateGroup 1397 -- 1398 -- Contains information describing the current state of the SMF 1399 -- process such as the current inclusion in the RS or not. 1401 -- 1403 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1405 smfStateNodeRsStatusIncluded OBJECT-TYPE 1406 SYNTAX TruthValue 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "The current status of the SMF node in the context of 1411 the MANETs relay set. A value of 'true(1)' indicates 1412 that the node is currently part of the MANET Relay 1413 Set. A value of 'false(2)' indicates that the node 1414 is currently not part of the MANET Relay Set." 1415 REFERENCE 1416 "See Section 7. 'Relay Set Selection' in 1417 RFC 6621 - Simplified Multicast Forwarding 1418 (SMF), Macker, J., May 2012." 1419 ::= { smfStateGroup 1 } 1421 smfStateDpdMemoryOverflow OBJECT-TYPE 1422 SYNTAX Counter32 1423 UNITS "DPD Records" 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "The number of DPD records that had to be flushed to 1428 prevent memory overruns for caching of these records. 1429 The number of records to be flushed upon a buffer 1430 overflow is an implementation specific decision. 1432 There is the potential for a counter discontinuity 1433 in this object if the system SMF process had been 1434 disabled and later enabled. In order to check for 1435 the occurrence of such a discontinuity when monitoring 1436 this counter object, it is recommended that the 1437 smfCfgSmfSysUpTime object also be monitored." 1438 REFERENCE 1439 "See Section 6. 'SMF Duplicate Packet 1440 Detection' in RFC 6621 - Simplified 1441 Multicast Forwarding (SMF), Macker, J., 1442 May 2012." 1443 ::= { smfStateGroup 2 } 1445 -- 1446 -- SMF Neighbor Table 1447 -- 1448 smfStateNeighborTable OBJECT-TYPE 1449 SYNTAX SEQUENCE OF SmfStateNeighborEntry 1450 MAX-ACCESS not-accessible 1451 STATUS current 1452 DESCRIPTION 1453 "The SMF StateNeighborTable describes the 1454 current one-hop neighbor nodes, their address 1455 and SMF RSSA and the interface on which 1456 they can be reached." 1457 REFERENCE 1458 "See Section 7. 'SMF Neighborhood Discovery' and 1459 Section 8.1. 'SMF Relay Algorithm TLV 1460 Types' in RFC 6621 - Simplified Multicast 1461 Forwarding (SMF), Macker, J., May 2012." 1462 ::= { smfStateGroup 3 } 1464 smfStateNeighborEntry OBJECT-TYPE 1465 SYNTAX SmfStateNeighborEntry 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "The SMF Neighbor Table contains the 1470 set of one-hop neighbors, the interface 1471 they are reachable on and the SMF RSSA 1472 they are currently running." 1473 INDEX { smfStateNeighborIpAddrType, 1474 smfStateNeighborIpAddr, 1475 smfStateNeighborPrefixLen } 1476 ::= { smfStateNeighborTable 1 } 1478 SmfStateNeighborEntry ::= 1479 SEQUENCE { 1480 smfStateNeighborIpAddrType InetAddressType, 1481 smfStateNeighborIpAddr InetAddress, 1482 smfStateNeighborPrefixLen InetAddressPrefixLength, 1483 smfStateNeighborRSSA IANAsmfRssaIdTC, 1484 smfStateNeighborNextHopInterface InterfaceIndexOrZero 1485 } 1487 smfStateNeighborIpAddrType OBJECT-TYPE 1488 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "The one-hop neighbor IP address type. 1494 Only the values 'ipv4(1)' and 1495 'ipv6(2)' are supported." 1497 ::= { smfStateNeighborEntry 1 } 1499 smfStateNeighborIpAddr OBJECT-TYPE 1500 SYNTAX InetAddress (SIZE(4|16)) 1501 MAX-ACCESS not-accessible 1502 STATUS current 1503 DESCRIPTION 1504 "The one-hop neighbor Inet IPv4 or IPv6 1505 address. 1507 Only IPv4 and IPv6 addresses 1508 are supported." 1509 ::= { smfStateNeighborEntry 2 } 1511 smfStateNeighborPrefixLen OBJECT-TYPE 1512 SYNTAX InetAddressPrefixLength 1513 UNITS "bits" 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "The prefix length. This is a decimal value that 1518 indicates the number of contiguous, higher-order 1519 bits of the address that make up the network 1520 portion of the address." 1521 ::= { smfStateNeighborEntry 3 } 1523 smfStateNeighborRSSA OBJECT-TYPE 1524 SYNTAX IANAsmfRssaIdTC 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "The current RSSA running on the neighbor." 1529 ::= { smfStateNeighborEntry 4 } 1531 smfStateNeighborNextHopInterface OBJECT-TYPE 1532 SYNTAX InterfaceIndexOrZero 1533 MAX-ACCESS read-only 1534 STATUS current 1535 DESCRIPTION 1536 "The interface ifIndex over which the 1537 neighbor is reachable in one-hop." 1538 ::= { smfStateNeighborEntry 6 } 1540 -- 1541 -- SMF Performance Group 1542 -- 1543 -- Contains objects which help to characterize the 1544 -- performance of the SMF RSSA process, such as statistics 1545 -- counters. There are two types of SMF RSSA statistics: 1546 -- global counters and per interface counters. 1547 -- 1548 -- It is an expectation that SMF devices will 1549 -- implement the standard IP-MIB module RFC4293. 1550 -- Exactly how to integrate SMF packet handling and 1551 -- management into the standard IP-MIB module management 1552 -- are part of the experiment. 1553 -- 1554 -- The SMF-MIB module counters within the 1555 -- smfPerformanceGroup count packets handled by the 1556 -- system and interface local SMF process (as discussed 1557 -- above). Not all IP (unicast and multicast) packets 1558 -- on a device interface are handled by the SMF process. 1559 -- So the counters are tracking different packet streams 1560 -- in the IP-MIB and SMF-MIB modules. 1561 -- 1563 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1565 smfPerfGobalGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1567 -- 1568 -- IPv4 packet counters 1569 -- 1571 smfPerfIpv4MultiPktsRecvTotal OBJECT-TYPE 1572 SYNTAX Counter32 1573 UNITS "Packets" 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "A counter of the total number of 1578 multicast IPv4 packets received by the 1579 device and delivered to the SMF process. 1581 There is the potential for a counter discontinuity 1582 in this object if the system SMF process had been 1583 disabled and later enabled. In order to check for 1584 the occurrence of such a discontinuity when monitoring 1585 this counter object, it is recommended that the 1586 smfCfgSmfSysUpTime object also be monitored." 1587 ::= { smfPerfGobalGroup 1 } 1589 smfPerfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1590 SYNTAX Counter32 1591 UNITS "Packets" 1592 MAX-ACCESS read-only 1593 STATUS current 1594 DESCRIPTION 1595 "A counter of the total number of 1596 multicast IPv4 packets forwarded by the 1597 device. 1599 There is the potential for a counter discontinuity 1600 in this object if the system SMF process had been 1601 disabled and later enabled. In order to check for 1602 the occurrence of such a discontinuity when monitoring 1603 this counter object, it is recommended that the 1604 smfCfgSmfSysUpTime object also be monitored." 1605 ::= { smfPerfGobalGroup 2 } 1607 smfPerfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1608 SYNTAX Counter32 1609 UNITS "Packets" 1610 MAX-ACCESS read-only 1611 STATUS current 1612 DESCRIPTION 1613 "A counter of the total number of duplicate 1614 multicast IPv4 packets detected by the 1615 device. 1617 There is the potential for a counter discontinuity 1618 in this object if the system SMF process had been 1619 disabled and later enabled. In order to check for 1620 the occurrence of such a discontinuity when monitoring 1621 this counter object, it is recommended that the 1622 smfCfgSmfSysUpTime object also be monitored." 1623 REFERENCE 1624 "See Section 6.2. 'IPv4 Duplicate Packet 1625 Detection' in RFC 6621 - Simplified Multicast 1626 Forwarding (SMF), Macker, J., May 2012." 1627 ::= { smfPerfGobalGroup 3 } 1629 smfPerfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1630 SYNTAX Counter32 1631 UNITS "Packets" 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION 1635 "A counter of the total number of dropped 1636 multicast IPv4 packets by the 1637 device due to TTL exceeded. 1639 There is the potential for a counter discontinuity 1640 in this object if the system SMF process had been 1641 disabled and later enabled. In order to check for 1642 the occurrence of such a discontinuity when monitoring 1643 this counter object, it is recommended that the 1644 smfCfgSmfSysUpTime object also be monitored." 1645 REFERENCE 1646 "See Section 5. 'SMF Packet Processing and 1647 Forwarding' in RFC 6621 - Simplified 1648 Multicast Forwarding (SMF), Macker, J., 1649 May 2012." 1650 ::= { smfPerfGobalGroup 4 } 1652 smfPerfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1653 SYNTAX Counter32 1654 UNITS "Packets" 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "A counter of the total number of IPv4 packets 1659 recieved which have a TTL larger than that 1660 of a previously received identical packet. 1662 There is the potential for a counter discontinuity 1663 in this object if the system SMF process had been 1664 disabled and later enabled. In order to check for 1665 the occurrence of such a discontinuity when monitoring 1666 this counter object, it is recommended that the 1667 smfCfgSmfSysUpTime object also be monitored." 1668 REFERENCE 1669 "See Section 5. 'SMF Packet Processing and 1670 Forwarding' in RFC 6621 - Simplified Multicast 1671 Forwarding (SMF), Macker, J., May 2012." 1672 ::= { smfPerfGobalGroup 5 } 1674 -- 1675 -- IPv6 packet counters 1676 -- 1678 smfPerfIpv6MultiPktsRecvTotal OBJECT-TYPE 1679 SYNTAX Counter32 1680 UNITS "Packets" 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "A counter of the total number of 1685 multicast IPv6 packets received by the 1686 device and delivered to the SMF process. 1688 There is the potential for a counter discontinuity 1689 in this object if the system SMF process had been 1690 disabled and later enabled. In order to check for 1691 the occurrence of such a discontinuity when monitoring 1692 this counter object, it is recommended that the 1693 smfCfgSmfSysUpTime object also be monitored." 1694 ::= { smfPerfGobalGroup 6 } 1696 smfPerfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1697 SYNTAX Counter32 1698 UNITS "Packets" 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "A counter of the total number of 1703 multicast IPv6 packets forwarded by the 1704 device. 1706 There is the potential for a counter discontinuity 1707 in this object if the system SMF process had been 1708 disabled and later enabled. In order to check for 1709 the occurrence of such a discontinuity when monitoring 1710 this counter object, it is recommended that the 1711 smfCfgSmfSysUpTime object also be monitored." 1712 ::= { smfPerfGobalGroup 7 } 1714 smfPerfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1715 SYNTAX Counter32 1716 UNITS "Packets" 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "A counter of the total number of duplicate 1721 multicast IPv6 packets detected by the 1722 device. 1724 There is the potential for a counter discontinuity 1725 in this object if the system SMF process had been 1726 disabled and later enabled. In order to check for 1727 the occurrence of such a discontinuity when monitoring 1728 this counter object, it is recommended that the 1729 smfCfgSmfSysUpTime object also be monitored." 1730 REFERENCE 1731 "See Section 6.1. 'IPv6 Duplicate Packet 1732 Detection' in RFC 6621 - Simplified Multicast 1733 Forwarding (SMF), Macker, J., May 2012." 1734 ::= { smfPerfGobalGroup 8 } 1735 smfPerfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1736 SYNTAX Counter32 1737 UNITS "Packets" 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 "A counter of the total number of dropped 1742 multicast IPv6 packets by the 1743 device due to TTL exceeded. 1745 There is the potential for a counter discontinuity 1746 in this object if the system SMF process had been 1747 disabled and later enabled. In order to check for 1748 the occurrence of such a discontinuity when monitoring 1749 this counter object, it is recommended that the 1750 smfCfgSmfSysUpTime object also be monitored." 1751 REFERENCE 1752 "See Section 5. 'SMF Packet Processing and 1753 Forwarding' in RFC 6621 - Simplified 1754 Multicast Forwarding (SMF), Macker, J., 1755 May 2012." 1756 ::= { smfPerfGobalGroup 9 } 1758 smfPerfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1759 SYNTAX Counter32 1760 UNITS "Packets" 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "A counter of the total number of IPv6 packets 1765 recieved which have a TTL larger than that 1766 of a previously recived identical packet. 1768 There is the potential for a counter discontinuity 1769 in this object if the system SMF process had been 1770 disabled and later enabled. In order to check for 1771 the occurrence of such a discontinuity when monitoring 1772 this counter object, it is recommended that the 1773 smfCfgSmfSysUpTime object also be monitored." 1774 REFERENCE 1775 "See Section 5. 'SMF Packet Processing and 1776 Forwarding' in RFC 6621 - Simplified Multicast 1777 Forwarding (SMF), Macker, J., May 2012." 1778 ::= { smfPerfGobalGroup 10 } 1780 smfPerfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1781 SYNTAX Counter32 1782 UNITS "Packets" 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "A counter of the total number of IPv6 packets 1787 received which required the HAV assist for DPD. 1789 There is the potential for a counter discontinuity 1790 in this object if the system SMF process had been 1791 disabled and later enabled. In order to check for 1792 the occurrence of such a discontinuity when monitoring 1793 this counter object, it is recommended that the 1794 smfCfgSmfSysUpTime object also be monitored." 1795 REFERENCE 1796 "See Section 6.1.1. 'IPv6 SMF_DPD Option Header' 1797 in RFC 6621 - Simplified Multicast Forwarding 1798 (SMF), Macker, J., May 2012." 1799 ::= { smfPerfGobalGroup 11 } 1801 smfPerfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1802 SYNTAX Counter32 1803 UNITS "Packets" 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "A counter of the total number of IPv6 packets 1808 recieved which the device inserted the 1809 DPD header option. 1811 There is the potential for a counter discontinuity 1812 in this object if the system SMF process had been 1813 disabled and later enabled. In order to check for 1814 the occurrence of such a discontinuity when monitoring 1815 this counter object, it is recommended that the 1816 smfCfgSmfSysUpTime object also be monitored." 1817 REFERENCE 1818 "See Section 6.1.2. 'IPv6 Identification-Based 1819 DPD' in RFC 6621 - Simplified Multicast 1820 Forwarding (SMF), Macker, J., May 2012." 1821 ::= { smfPerfGobalGroup 12 } 1823 -- 1824 -- Per SMF Interface Performance Table 1825 -- 1827 smfPerfInterfaceGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1829 smfPerfIpv4InterfacePerfTable OBJECT-TYPE 1830 SYNTAX SEQUENCE OF SmfPerfIpv4InterfacePerfEntry 1831 MAX-ACCESS not-accessible 1832 STATUS current 1833 DESCRIPTION 1834 "The SMF Interface Performance Table 1835 describes the SMF counters per 1836 interface." 1837 ::= { smfPerfInterfaceGroup 1 } 1839 smfPerfIpv4InterfacePerfEntry OBJECT-TYPE 1840 SYNTAX SmfPerfIpv4InterfacePerfEntry 1841 MAX-ACCESS not-accessible 1842 STATUS current 1843 DESCRIPTION 1844 "The SMF Interface Performance entry 1845 describes the statistics for a particular 1846 node interface." 1847 INDEX { smfCfgIfIndex } 1848 ::= { smfPerfIpv4InterfacePerfTable 1 } 1850 SmfPerfIpv4InterfacePerfEntry ::= 1851 SEQUENCE { 1852 smfPerfIpv4MultiPktsRecvPerIf Counter32, 1853 smfPerfIpv4MultiPktsForwardedPerIf Counter32, 1854 smfPerfIpv4DuplMultiPktsDetectedPerIf Counter32, 1855 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1856 smfPerfIpv4TTLLargerThanPreviousPerIf Counter32 1857 } 1859 smfPerfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1860 SYNTAX Counter32 1861 UNITS "Packets" 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "A counter of the number of multicast IP 1866 packets received by the SMF process on 1867 this device on this interface. 1869 There is the potential for a counter discontinuity 1870 in this object if the system SMF process had been 1871 disabled and later enabled on this interface. 1872 In order to check for the occurrence of such a 1873 discontinuity when monitoring this counter object, 1874 it is recommended that the smfCfgIfSmfUpTime 1875 object also be monitored." 1876 ::= { smfPerfIpv4InterfacePerfEntry 1 } 1877 smfPerfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1878 SYNTAX Counter32 1879 UNITS "Packets" 1880 MAX-ACCESS read-only 1881 STATUS current 1882 DESCRIPTION 1883 "A counter of the number of 1884 multicast IP packets forwarded by the 1885 SMF process on this device 1886 on this interface. 1888 There is the potential for a counter discontinuity 1889 in this object if the system SMF process had been 1890 disabled and later enabled on this interface. 1891 In order to check for the occurrence of such a 1892 discontinuity when monitoring this counter object, 1893 it is recommended that the smfCfgIfSmfUpTime 1894 object also be monitored." 1895 ::= { smfPerfIpv4InterfacePerfEntry 2 } 1897 smfPerfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1898 SYNTAX Counter32 1899 UNITS "Packets" 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "A counter of the number of duplicate 1904 multicast IP packets detected by the 1905 SMF process on this device 1906 on this interface. 1908 There is the potential for a counter discontinuity 1909 in this object if the system SMF process had been 1910 disabled and later enabled on this interface. 1911 In order to check for the occurrence of such a 1912 discontinuity when monitoring this counter object, 1913 it is recommended that the smfCfgIfSmfUpTime 1914 object also be monitored." 1915 ::= { smfPerfIpv4InterfacePerfEntry 3 } 1917 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1918 SYNTAX Counter32 1919 UNITS "Packets" 1920 MAX-ACCESS read-only 1921 STATUS current 1922 DESCRIPTION 1923 "A counter of the total number of dropped 1924 multicast IPv4 packets by the SMF process 1925 on this device on this interface 1926 due to TTL exceeded. 1928 There is the potential for a counter discontinuity 1929 in this object if the system SMF process had been 1930 disabled and later enabled on this interface. 1931 In order to check for the occurrence of such a 1932 discontinuity when monitoring this counter object, 1933 it is recommended that the smfCfgIfSmfUpTime 1934 object also be monitored." 1935 ::= { smfPerfIpv4InterfacePerfEntry 4 } 1937 smfPerfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1938 SYNTAX Counter32 1939 UNITS "Packets" 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "A counter of the total number of IPv4 packets 1944 received by the SMF process on this device 1945 on this interface which have a TTL larger than 1946 that of a previously received identical packet. 1948 There is the potential for a counter discontinuity 1949 in this object if the system SMF process had been 1950 disabled and later enabled on this interface. 1951 In order to check for the occurrence of such a 1952 discontinuity when monitoring this counter object, 1953 it is recommended that the smfCfgIfSmfUpTime 1954 object also be monitored." 1955 ::= { smfPerfIpv4InterfacePerfEntry 5 } 1957 smfPerfIpv6InterfacePerfTable OBJECT-TYPE 1958 SYNTAX SEQUENCE OF SmfPerfIpv6InterfacePerfEntry 1959 MAX-ACCESS not-accessible 1960 STATUS current 1961 DESCRIPTION 1962 "The SMF Interface Performance Table 1963 describes the SMF counters per 1964 interface." 1965 ::= { smfPerfInterfaceGroup 2 } 1967 smfPerfIpv6InterfacePerfEntry OBJECT-TYPE 1968 SYNTAX SmfPerfIpv6InterfacePerfEntry 1969 MAX-ACCESS not-accessible 1970 STATUS current 1971 DESCRIPTION 1972 "The SMF Interface Performance entry 1973 describes the counters for a particular 1974 node interface." 1975 INDEX { smfCfgIfIndex } 1976 ::= { smfPerfIpv6InterfacePerfTable 1 } 1978 SmfPerfIpv6InterfacePerfEntry ::= 1979 SEQUENCE { 1980 smfPerfIpv6MultiPktsRecvPerIf Counter32, 1981 smfPerfIpv6MultiPktsForwardedPerIf Counter32, 1982 smfPerfIpv6DuplMultiPktsDetectedPerIf Counter32, 1983 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1984 smfPerfIpv6TTLLargerThanPreviousPerIf Counter32, 1985 smfPerfIpv6HAVAssistsReqdPerIf Counter32, 1986 smfPerfIpv6DpdHeaderInsertionsPerIf Counter32 1987 } 1989 smfPerfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1990 SYNTAX Counter32 1991 UNITS "Packets" 1992 MAX-ACCESS read-only 1993 STATUS current 1994 DESCRIPTION 1995 "A counter of the number of 1996 multicast IP packets received by the 1997 SMF process on this device 1998 on this interface. 2000 There is the potential for a counter discontinuity 2001 in this object if the system SMF process had been 2002 disabled and later enabled on this interface. 2003 In order to check for the occurrence of such a 2004 discontinuity when monitoring this counter object, 2005 it is recommended that the smfCfgIfSmfUpTime 2006 object also be monitored." 2007 ::= { smfPerfIpv6InterfacePerfEntry 1 } 2009 smfPerfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 2010 SYNTAX Counter32 2011 UNITS "Packets" 2012 MAX-ACCESS read-only 2013 STATUS current 2014 DESCRIPTION 2015 "A counter of the number of 2016 multicast IP packets forwarded by the 2017 SMF process on this device 2018 on this interface. 2020 There is the potential for a counter discontinuity 2021 in this object if the system SMF process had been 2022 disabled and later enabled on this interface. 2023 In order to check for the occurrence of such a 2024 discontinuity when monitoring this counter object, 2025 it is recommended that the smfCfgIfSmfUpTime 2026 object also be monitored." 2027 ::= { smfPerfIpv6InterfacePerfEntry 2 } 2029 smfPerfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 2030 SYNTAX Counter32 2031 UNITS "Packets" 2032 MAX-ACCESS read-only 2033 STATUS current 2034 DESCRIPTION 2035 "A counter of the number of duplicate 2036 multicast IP packets detected by the 2037 SMF process on this device 2038 on this interface. 2040 There is the potential for a counter discontinuity 2041 in this object if the system SMF process had been 2042 disabled and later enabled on this interface. 2043 In order to check for the occurrence of such a 2044 discontinuity when monitoring this counter object, 2045 it is recommended that the smfCfgIfSmfUpTime 2046 object also be monitored." 2047 ::= { smfPerfIpv6InterfacePerfEntry 3 } 2049 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 2050 SYNTAX Counter32 2051 UNITS "Packets" 2052 MAX-ACCESS read-only 2053 STATUS current 2054 DESCRIPTION 2055 "A counter of the number of dropped 2056 multicast IP packets by the 2057 SMF process on this device 2058 on this interface due to TTL 2059 exceeded. 2061 There is the potential for a counter discontinuity 2062 in this object if the system SMF process had been 2063 disabled and later enabled on this interface. 2064 In order to check for the occurrence of such a 2065 discontinuity when monitoring this counter object, 2066 it is recommended that the smfCfgIfSmfUpTime 2067 object also be monitored." 2069 ::= { smfPerfIpv6InterfacePerfEntry 4 } 2071 smfPerfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 2072 SYNTAX Counter32 2073 UNITS "Packets" 2074 MAX-ACCESS read-only 2075 STATUS current 2076 DESCRIPTION 2077 "A counter of the total number of IPv6 packets 2078 received which have a TTL larger than that 2079 of a previously received identical packet 2080 by the SMF process on this device on this 2081 interface. 2083 There is the potential for a counter discontinuity 2084 in this object if the system SMF process had been 2085 disabled and later enabled on this interface. 2086 In order to check for the occurrence of such a 2087 discontinuity when monitoring this counter object, 2088 it is recommended that the smfCfgIfSmfUpTime 2089 object also be monitored." 2090 ::= { smfPerfIpv6InterfacePerfEntry 5 } 2092 smfPerfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 2093 SYNTAX Counter32 2094 UNITS "Packets" 2095 MAX-ACCESS read-only 2096 STATUS current 2097 DESCRIPTION 2098 "A counter of the total number of IPv6 packets 2099 received by the SMF process on this device 2100 on this interface which required the 2101 HAV assist for DPD. 2103 There is the potential for a counter discontinuity 2104 in this object if the system SMF process had been 2105 disabled and later enabled on this interface. 2106 In order to check for the occurrence of such a 2107 discontinuity when monitoring this counter object, 2108 it is recommended that the smfCfgIfSmfUpTime 2109 object also be monitored." 2110 ::= { smfPerfIpv6InterfacePerfEntry 6 } 2112 smfPerfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 2113 SYNTAX Counter32 2114 UNITS "Packets" 2115 MAX-ACCESS read-only 2116 STATUS current 2117 DESCRIPTION 2118 "A counter of the total number of IPv6 packets 2119 received by the SMF process on this device 2120 on this interface which the device inserted the 2121 DPD header option. 2123 There is the potential for a counter discontinuity 2124 in this object if the system SMF process had been 2125 disabled and later enabled on this interface. 2126 In order to check for the occurrence of such a 2127 discontinuity when monitoring this counter object, 2128 it is recommended that the smfCfgIfSmfUpTime 2129 object also be monitored." 2130 ::= { smfPerfIpv6InterfacePerfEntry 7 } 2132 -- 2133 -- Notifications 2134 -- 2136 smfMIBNotifObjects OBJECT IDENTIFIER ::= { smfMIBNotifications 0 } 2137 smfMIBNotifControl OBJECT IDENTIFIER ::= { smfMIBNotifications 1 } 2139 -- smfMIBNotifObjects 2141 smfNotifAdminStatusChange NOTIFICATION-TYPE 2142 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2143 -- the notification. 2144 smfCfgRouterID, -- The originator of 2145 -- the notification. 2146 smfCfgAdminStatus -- The new status of the 2147 -- SMF process. 2148 } 2149 STATUS current 2150 DESCRIPTION 2151 "smfCfgAdminStatusChange is a notification sent when a 2152 the 'smfCfgAdminStatus' object changes." 2153 ::= { smfMIBNotifObjects 1 } 2155 smfNotifConfiguredOpModeChange NOTIFICATION-TYPE 2156 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2157 -- the notification. 2158 smfCfgRouterID, -- The originator of 2159 -- the notification. 2160 smfCfgOperationalMode -- The new Operations 2161 -- Mode of the SMF 2162 -- process. 2163 } 2164 STATUS current 2165 DESCRIPTION 2166 "smfNotifConfiguredOpModeChange is a notification 2167 sent when the 'smfCfgOperationalMode' object 2168 changes." 2169 ::= { smfMIBNotifObjects 2 } 2171 smfNotifIfAdminStatusChange NOTIFICATION-TYPE 2172 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2173 -- the notification. 2174 smfCfgRouterID, -- The originator of 2175 -- the notification. 2176 ifName, -- The interface whose 2177 -- status has changed. 2178 smfCfgIfAdminStatus -- The new status of the 2179 -- SMF interface. 2180 } 2181 STATUS current 2182 DESCRIPTION 2183 "smfCfgIfAdminStatusChange is a notification sent when a 2184 the 'smfCfgIfAdminStatus' object changes." 2185 ::= { smfMIBNotifObjects 3 } 2187 smfNotifDpdMemoryOverflowEvent NOTIFICATION-TYPE 2188 OBJECTS { smfCfgRouterIDAddrType, -- The originator of 2189 -- the notification. 2190 smfCfgRouterID, -- The originator of 2191 -- the notification. 2192 smfStateDpdMemoryOverflow -- The counter of 2193 -- the overflows. 2194 } 2195 STATUS current 2196 DESCRIPTION 2197 "smfNotifDpdMemoryOverflowEvents is sent when the 2198 number of memory overflow events exceeds the 2199 the 'smfNotifDpdMemoryOverflowThreshold' within the 2200 previous number of seconds defined by the 2201 'smfNotifDpdMemoryOverflowWindow'." 2202 ::= { smfMIBNotifObjects 4 } 2204 -- smfMIBNotifControl 2205 smfNotifDpdMemoryOverflowThreshold OBJECT-TYPE 2206 SYNTAX Integer32 (0..255) 2207 UNITS "Events" 2208 MAX-ACCESS read-write 2209 STATUS current 2210 DESCRIPTION 2211 "A threshold value for the 2212 `smfNotifDpdmemoryOverflowEvents' object. 2213 If the number of occurences exceeds 2214 this threshold within the previous 2215 number of seconds 2216 'smfNotifDpdMemoryOverflowWindow', 2217 then the `smfNotifDpdMemoryOverflowEvent' 2218 notification is sent. 2220 The default value for this object is 2221 '1'." 2222 DEFVAL { 1 } 2223 ::= { smfMIBNotifControl 1 } 2225 smfNotifDpdMemoryOverflowWindow OBJECT-TYPE 2226 SYNTAX TimeTicks 2227 MAX-ACCESS read-write 2228 STATUS current 2229 DESCRIPTION 2230 "A time window value for the 2231 `smfNotifDpdmemoryOverflowEvents' object. 2232 If the number of occurences exceeds 2233 the `smfNotifDpdMemoryOverflowThreshold' 2234 within the previous number of seconds 2235 'smfNotifDpdMemoryOverflowWindow', 2236 then the `smfNotifDpdMemoryOverflowEvent' 2237 notification is sent. 2239 The default value for this object is 2240 '1'." 2241 DEFVAL { 1 } 2242 ::= { smfMIBNotifControl 2 } 2244 -- 2245 -- Compliance Statements 2246 -- 2248 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 2249 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 2251 smfBasicCompliance MODULE-COMPLIANCE 2252 STATUS current 2253 DESCRIPTION "The basic implementation requirements for 2254 managed network entities that implement 2255 the SMF RSSA process." 2256 MODULE -- this module 2257 MANDATORY-GROUPS { smfCapabObjectsGroup, 2258 smfConfigObjectsGroup } 2259 ::= { smfCompliances 1 } 2261 smfFullCompliance MODULE-COMPLIANCE 2262 STATUS current 2263 DESCRIPTION "The full implementation requirements for 2264 managed network entities that implement 2265 the SMF RSSA process." 2266 MODULE -- this module 2267 MANDATORY-GROUPS { smfCapabObjectsGroup, 2268 smfConfigObjectsGroup, 2269 smfStateObjectsGroup, 2270 smfPerfObjectsGroup, 2271 smfNotifObjectsGroup, 2272 smfNotificationsGroup 2273 } 2274 ::= { smfCompliances 2 } 2276 -- 2277 -- Units of Conformance 2278 -- 2280 smfCapabObjectsGroup OBJECT-GROUP 2281 OBJECTS { 2282 smfCapabilitiesOpModeID, 2283 smfCapabilitiesRssaID 2284 } 2285 STATUS current 2286 DESCRIPTION 2287 "Set of SMF configuration objects implemented 2288 in this module." 2289 ::= { smfMIBGroups 1 } 2291 smfConfigObjectsGroup OBJECT-GROUP 2292 OBJECTS { 2293 smfCfgAdminStatus, 2294 smfCfgSmfSysUpTime, 2295 smfCfgRouterIDAddrType, 2296 smfCfgRouterID, 2297 smfCfgOperationalMode, 2298 smfCfgRssaMember, 2299 smfCfgIpv4Dpd, 2300 smfCfgIpv6Dpd, 2301 smfCfgMaxPktLifetime, 2302 smfCfgDpdEntryMaxLifetime, 2303 smfCfgNhdpRssaMesgTLVIncluded, 2304 smfCfgNhdpRssaAddrBlockTLVIncluded, 2306 smfCfgAddrForwardingGroupName, 2307 smfCfgAddrForwardingAddrType, 2308 smfCfgAddrForwardingAddress, 2309 smfCfgAddrForwardingAddrPrefixLength, 2310 smfCfgAddrForwardingStatus, 2312 smfCfgIfAdminStatus, 2313 smfCfgIfSmfUpTime, 2314 smfCfgIfRowStatus 2315 } 2316 STATUS current 2317 DESCRIPTION 2318 "Set of SMF configuration objects implemented 2319 in this module." 2320 ::= { smfMIBGroups 2 } 2322 smfStateObjectsGroup OBJECT-GROUP 2323 OBJECTS { 2324 smfStateNodeRsStatusIncluded, 2325 smfStateDpdMemoryOverflow, 2327 smfStateNeighborRSSA, 2328 smfStateNeighborNextHopInterface 2329 } 2330 STATUS current 2331 DESCRIPTION 2332 "Set of SMF state objects implemented 2333 in this module." 2334 ::= { smfMIBGroups 3 } 2336 smfPerfObjectsGroup OBJECT-GROUP 2337 OBJECTS { 2338 smfPerfIpv4MultiPktsRecvTotal, 2339 smfPerfIpv4MultiPktsForwardedTotal, 2340 smfPerfIpv4DuplMultiPktsDetectedTotal, 2341 smfPerfIpv4DroppedMultiPktsTTLExceededTotal, 2342 smfPerfIpv4TTLLargerThanPreviousTotal, 2344 smfPerfIpv6MultiPktsRecvTotal, 2345 smfPerfIpv6MultiPktsForwardedTotal, 2346 smfPerfIpv6DuplMultiPktsDetectedTotal, 2347 smfPerfIpv6DroppedMultiPktsTTLExceededTotal, 2348 smfPerfIpv6TTLLargerThanPreviousTotal, 2349 smfPerfIpv6HAVAssistsReqdTotal, 2350 smfPerfIpv6DpdHeaderInsertionsTotal, 2351 smfPerfIpv4MultiPktsRecvPerIf, 2352 smfPerfIpv4MultiPktsForwardedPerIf, 2353 smfPerfIpv4DuplMultiPktsDetectedPerIf, 2354 smfPerfIpv4DroppedMultiPktsTTLExceededPerIf, 2355 smfPerfIpv4TTLLargerThanPreviousPerIf, 2357 smfPerfIpv6MultiPktsRecvPerIf, 2358 smfPerfIpv6MultiPktsForwardedPerIf, 2359 smfPerfIpv6DuplMultiPktsDetectedPerIf, 2360 smfPerfIpv6DroppedMultiPktsTTLExceededPerIf, 2361 smfPerfIpv6TTLLargerThanPreviousPerIf, 2362 smfPerfIpv6HAVAssistsReqdPerIf, 2363 smfPerfIpv6DpdHeaderInsertionsPerIf 2364 } 2365 STATUS current 2366 DESCRIPTION 2367 "Set of SMF performance objects implemented 2368 in this module by total and per interface." 2369 ::= { smfMIBGroups 4 } 2371 smfNotifObjectsGroup OBJECT-GROUP 2372 OBJECTS { 2373 smfNotifDpdMemoryOverflowThreshold, 2374 smfNotifDpdMemoryOverflowWindow 2375 } 2376 STATUS current 2377 DESCRIPTION 2378 "Set of SMF notification control 2379 objects implemented in this module." 2380 ::= { smfMIBGroups 5 } 2382 smfNotificationsGroup NOTIFICATION-GROUP 2383 NOTIFICATIONS { 2384 smfNotifAdminStatusChange, 2385 smfNotifConfiguredOpModeChange, 2386 smfNotifIfAdminStatusChange, 2387 smfNotifDpdMemoryOverflowEvent 2388 } 2389 STATUS current 2390 DESCRIPTION 2391 "Set of SMF notifications implemented 2392 in this module." 2393 ::= { smfMIBGroups 6 } 2395 END 2397 8. IANA-SMF-MIB Definitions 2399 This section contains the IANA-SMF-MIB module. This MIB module 2400 defines two textual conventions for which IANA SHOULD maintain and 2401 keep synchronized with the registry identified below within the 2402 IANAsmfOpModeIdTC and the IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. 2404 The IANAsmfOpModeIdTC defines an index that identifies through 2405 reference to a specific SMF operations mode. The index is an integer 2406 valued named-number enumeration consisting of an integer and label. 2407 IANA is to create and maintain this textual convention. Future 2408 assignments are made to anyone on a first come, first served basis. 2409 There is no substantive review of the request, other than to ensure 2410 that it is well-formed and does not duplicate an existing assignment. 2411 However, requests must include a minimal amount of clerical 2412 information, such as a point of contact (including an email address) 2413 and a brief description of the method being identified as a new SMF 2414 operations mode. 2416 The IANAsmfRssaIdTC defines an index that identifies through 2417 reference to a specific Reduced Set Selection Algorithm (RSSA). The 2418 index is an integer valued named-number enumeration consisting of an 2419 integer and label. IANA is to create and maintain this textual 2420 convention. 2422 Future assignments to the IANAsmfRssaIdTC for the index range 5-127 2423 require an RFC publication (either as an IETF submission or as an RFC 2424 Editor Independent submission [RFC3932]). The type of RFC MUST be 2425 Standards Track. The specific RSSA algorithms MUST be documented in 2426 sufficient detail so that interoperability between independent 2427 implementations is possible. 2429 Future assignments to the IANAsmfRssaIdTC for the index range 128-239 2430 are private or local use only, with the type and purpose defined by 2431 the local site. No attempt is made to prevent multiple sites from 2432 using the same value in different (and incompatible) ways. There is 2433 no need for IANA to review such assignments (since IANA will not 2434 record these) and assignments are not generally useful for broad 2435 interoperability. It is the responsibility of the sites making use 2436 of the Private Use range to ensure that no conflicts occur (within 2437 the intended scope of use). 2439 Future assignments to the IANAsmfRssaIdTC for the index range 240-255 2440 are to facilitate experimentation. These require an RFC publication 2441 (either as an IETF submission or as an RFC Editor Independent 2442 submission [RFC3932]). The type of RFC MUST be Experimental. The 2443 RSSA algorithms MUST be documented in sufficient detail so that 2444 interoperability between independent implementations is possible. 2446 IANA-SMF-MIB DEFINITIONS ::= BEGIN 2448 IMPORTS 2449 MODULE-IDENTITY, mib-2 2450 FROM SNMPv2-SMI 2451 TEXTUAL-CONVENTION 2452 FROM SNMPv2-TC; 2454 ianaSmfMIB MODULE-IDENTITY 2455 LAST-UPDATED "201407301300Z" -- July 30, 2014 2456 ORGANIZATION "IANA" 2457 CONTACT-INFO "Internet Assigned Numbers Authority 2459 Postal: ICANN 2460 4676 Admiralty Way, Suite 330 2461 Marina del Rey, CA 90292 2463 Tel: +1 310 823 9358 2464 E-Mail: iana@iana.org" 2465 DESCRIPTION "This MIB module defines the 2466 IANAsmfOpModeIdTC and IANAsmfRssaIdTC 2467 Textual Conventions, and thus the 2468 enumerated values of the 2469 smfCapabilitiesOpModeID and 2470 smfCapabilitiesRssaID objects defined 2471 in the SMF-MIB." 2472 REVISION "201407301300Z" -- July 30, 2014 2473 DESCRIPTION "Initial version of this MIB as published in 2474 RFC KKKK." 2475 ::= { mib-2 kkkk } 2477 IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION 2478 STATUS current 2479 DESCRIPTION 2480 "An index that identifies through reference to a specific 2481 SMF operations mode. There are basically three styles 2482 of SMF operation with reduced relay sets currently 2483 identified: 2485 Independent operation 'independent(1)' - 2486 SMF performs its own relay 2487 set selection using information from an associated 2488 MANET NHDP process. 2490 CDS-aware unicast routing operation 'routing(2)'- 2491 a coexistent unicast routing 2492 protocol provides dynamic relay 2493 set state based upon its own control plane 2494 CDS or neighborhood discovery information. 2496 Cross-layer operation 'crossLayer(3)' - 2497 SMF operates using neighborhood 2498 status and triggers from a 2499 cross-layer information base for dynamic relay 2500 set selection and maintenance. 2502 IANA MUST update this textual convention accordingly. 2504 The definition of this textual convention with the 2505 addition of newly assigned values is published 2506 periodically by the IANA, in either the Assigned 2507 Numbers RFC, or some derivative of it specific to 2508 Internet Network Management number assignments. (The 2509 latest arrangements can be obtained by contacting the 2510 IANA.) 2512 Requests for new values SHOULD be made to IANA via 2513 email (iana@iana.org)." 2514 REFERENCE 2515 "See Section 7.2. 'Reduced Relay Set Forwarding', 2516 and the Appendices A, B and C in 2517 RFC 6621 - Simplified Multicast Forwarding 2518 (SMF), Macker, J., May 2012." 2519 SYNTAX INTEGER { 2520 independent (1), 2521 routing (2), 2522 crossLayer (3) 2523 -- future (4-255) 2524 } 2526 IANAsmfRssaIdTC ::= TEXTUAL-CONVENTION 2527 STATUS current 2528 DESCRIPTION 2529 "An index that identifies through reference to a specific 2530 RSSA algorithms. Several are currently defined 2531 in the Appendix A, B and C of RFC 6621. 2533 Examples of RSSA algorithms already identified within 2534 this TC are: 2536 Classical Flooding (cF(1)) - is the standard 2537 flooding algorithm where each node in the next 2538 retransmits the information on each of its interfaces. 2540 Source-Based Multipint Relay (sMPR(2)) - 2541 this algorithm is used by Optimized Link State Routing 2542 (OLSR) and OLSR version 2 (OLSRv2) protocols for the 2543 relay of link state updates and other control 2544 information [RFC3626]. Since each router picks 2545 its neighboring relays independently, sMPR 2546 forwarders depend upon previous hop information 2547 (e.g., source MAC address) to operate correctly. 2549 Extended Connected Dominating Set (eCDS(3)) - 2550 defined in [RFC5614] this algorithm forms a single 2551 CDS mesh for the SMF operating region. Its 2552 packet-forwarding rules are not dependent upon 2553 previous hop knowledge in contrast to sMPR. 2555 Multipoint Relay Connected Dominating Set (mprCDS(4)) - 2556 This algorithm is an extension to the basic sMPR 2557 election algorithm that results in a shared 2558 (non-source-specific) SMF CDS. Thus, its forwarding 2559 rules are not dependent upon previous hop information, 2560 similar to eCDS. 2562 IANA MUST update this textual convention accordingly. 2564 The definition of this textual convention with the 2565 addition of newly assigned values is published 2566 periodically by the IANA, in either the Assigned 2567 Numbers RFC, or some derivative of it specific to 2568 Internet Network Management number assignments. (The 2569 latest arrangements can be obtained by contacting the 2570 IANA.) 2572 Requests for new values SHOULD be made to IANA via 2573 email (iana@iana.org)." 2574 REFERENCE 2575 "See, e.g., 2577 Section 8.1.1. 'SMF Message TLV Type', 2578 Appendix A. 'Essential Connecting Dominating Set (E-CDS) 2579 Algorithm', 2580 Appendix B. 'Source-Based Multipoint Relay (S-MPR) 2581 Algorithm', and 2582 Appendix C. 'Multipoint Relay Connected Dominating Set 2583 (MPR-CDS) Algorithm' 2585 in RFC 6621 - Simplified Multicast Forwarding 2586 (SMF), Macker, J., May 2012." 2587 SYNTAX INTEGER { 2588 cF(1), 2589 sMPR(2), 2590 eCDS(3), 2591 mprCDS(4) 2592 -- future(5-127) 2593 -- noStdAction(128-239) 2594 -- experimental(240-255) 2595 } 2597 END 2599 9. Security Considerations 2601 This section discusses security implications of the choices made in 2602 this SMF-MIB module. 2604 There are a number of management objects defined in this MIB module 2605 with a MAX-ACCESS clause of read-write and/or read-create. Such 2606 objects may be considered sensitive or vulnerable in some network 2607 environments. The support for SET operations in a non-secure 2608 environment without proper protection can have a negative effect on 2609 network operations. These are the tables and objects and their 2610 sensitivity/vulnerability: 2612 o 'smfCfgAdminStatus' - this writable configuration object controls 2613 the operational status of the SMF process. If this setting is 2614 configured inconsistently across the MANET multicast domain, then 2615 delivery of multicast data may be inconsistent across the domain; 2616 some nodes may not receive multicast data intended for them. 2618 o 'smfCfgRouterIDAddrType' and 'smfCfgRouterID' - these writable 2619 configuration objects define the ID of the SMF process. These 2620 objects should be configured with a routable address defined on 2621 the local SMF device. The smfCfgRouterID is a logical 2622 identification that MUST be configured as unique across inter- 2623 operating SMF neighborhoods and it is RECOMMENDED to be chosen as 2624 the numerically largest address contained in a node's 'Neighbor 2625 Address List' as defined in NHDP. A smfCfgRouterID MUST be unique 2626 within the scope of the operating MANET network regardless of the 2627 method used for selecting it. If these objects are mis-configured 2628 or configured in-consistently across the MANET, then the ability 2629 of various RSSA algorithms, e.g., ECDS, may be compromised. This 2630 would potentially result in some routers within the MANET not 2631 receiving multicast packets destine to them. Hence, intentionally 2632 mis-configuring these objects could pose a form of Denial-of- 2633 Service (DOS) attack against the MANET. 2635 o 'smfCfgOpMode' - this writable configuration object defines the 2636 operational mode of the SMF process. The operational mode defines 2637 how the SMF process receives its data to form its local estimate 2638 of the CDS. It is recommended that the value for this object be 2639 set consistently across the MANET to ensure proper operation of 2640 the multicast packet forwarding. If the value for this object is 2641 set inconsistently across the MANET, the result may be that 2642 multicast packet delivery will be compromised within the MANET. 2643 Hence, intentionally mis-configuring this object could pose a form 2644 DOS attack against the MANET. 2646 o 'smfCfgRssa' - this writable configuration object sets the 2647 specific Reduced Set Selection Algorithm (RSSA) for the SMF 2648 process. If this object is set inconsistently across the MANET 2649 domain, multicast delivery of data will likely fail. Hence, 2650 intentionally mis-configuring this object could pose a form DOS 2651 attack against the MANET. 2653 o 'smfCfgRssaMember' - this writable configuration object sets the 2654 'interest' of the local SMF node in participating in the CDS. 2655 Setting this object to 'never(3)' on a highly highly connected 2656 device could lead to frequent island formation. Setting this 2657 object to 'always(2)' could support data ex-filtration from the 2658 MANET domain. 2660 o 'smfCfgIpv4Dpd' - this writable configuration object sets the 2661 duplicate packet detection method, i.e., H-DPD or I-DPD, for 2662 forwarding of IPv4 multicast packets. Forwarders may operate with 2663 mixed H-DPD and I-DPD modes as long as they consistently perform 2664 the appropriate DPD routines outlined [RFC6621]. However, it is 2665 RECOMMENDED that a deployment be configured with a common mode for 2666 operational consistency. 2668 o 'smfCfgIpv6Dpd' - this writable configuration object sets the 2669 duplicate packet detection method for forwarding of IPv6 multicast 2670 packets. Since IPv6 SMF does specifies an option header, the 2671 interoperability constraints are not as loose as in the IPv4 2672 version, and forwarders SHOULD not operate with mixed H-DPD and 2673 I-DPD modes. Hence the value for this object SHOULD be 2674 consistently set within the forwarders comprising the MANET, else 2675 inconsistent forwarding may result unnecessary multicast packet 2676 dropping. 2678 o 'smfCfgMaxPktLifetime' - this writable configuration object sets 2679 the estimate of the network packet traversal time. If set too 2680 small, this could lead to poor multicast data delivery ratios 2681 throughout the MANET domain. This could serve as a form of DOS 2682 attack if this object value is set too small. 2684 o 'smfCfgDpdEntryMaxLifetime' - this writable configuration object 2685 sets the maximum lifetime (in seconds) for the cached DPD records 2686 for the combined IPv4 and IPv6 methods. If the memory is running 2687 low prior to the MaxLifetime being exceeded, the local SMF devices 2688 should purge the oldest records first. If this object value is 2689 set too small, then the effectiveness of the SMF DPD algorithms 2690 may become greatly diminished causing a higher than necessary 2691 packet load on the MANET. 2693 o 'smfCfgNhdpRssaMesgTLVIncluded' - this writable configuration 2694 object indicates whether the associated NHDP messages include the 2695 RSSA Message TLV, or not. It is highly RECOMMENDED that this 2696 object be set to 'true(1)' when the SMF operation mode is set to 2697 independent as this information will inform the local forwarder of 2698 the RSSA algorithm implemented in neighboring forwarders and is 2699 used to ensure consistent forwarding across the MANET. While it 2700 is possible that SMF neighbors MAY be configured differently with 2701 respect to the RSSA algorithm and still operate cooperatively, but 2702 these cases will vary dependent upon the algorithm types 2703 designated and this situation SHOULD be avoided. 2705 o 'smfCfgNhdpRssaAddrBlockTLVIncluded' - this writable configuration 2706 object indicates whether the associated NHDP messages include the 2707 the RSSA Address Block TLV, or not. The 2708 smfNhdpRssaAddrBlockTLVIncluded is optional in all cases as it 2709 depends on the existence of an address block which may not be 2710 present. If this SMF device is configured with NHDP, then this 2711 object should be set to 'true(1)' as this TLV enables CDS relay 2712 algorithm operation and configuration to be shared among 2-hop 2713 neighborhoods. Some relay algorithms require 2-hop neighbor 2714 configuration in order to correctly select relay sets. 2716 o 'smfCfgAddrForwardingTable' - the writable configuration objects 2717 in this table indicate which multicast IP addresses are to be 2718 forwarded by this SMF node. Misconfiguration of rows within this 2719 table can limit the ability of this SMF device to properly forward 2720 multicast data. 2722 o 'smfCfgInterfaceTable' - the writable configuration objects in 2723 this table indicate which SMF node interfaces are participating in 2724 the SMF packet forwarding process. Misconfiguration of rows 2725 within this table can limit the ability of this SMF device to 2726 properly forward multicast data. 2728 Some of the readable objects in this MIB module (i.e., objects with a 2729 MAX-ACCESS other than not-accessible) may be considered sensitive or 2730 vulnerable in some network environments. It is thus important to 2731 control even GET and/or NOTIFY access to these objects and possibly 2732 to even encrypt the values of these objects when sending them over 2733 the network via SNMP. These are the tables and objects and their 2734 sensitivity/vulnerability: 2736 o 'smfNodeRsStatusIncluded' - this readable state object indicates 2737 that this SMF node is part of the CDS, or not. Being part of the 2738 CDS makes this node a distinguished device. It could be exploited 2739 for data ex-filtration, or denial of service attacks. 2741 o 'smfStateNeighborTable' - the readable state objects in this table 2742 indicate current neighbor nodes to this SMF node. Exposing this 2743 information to an attacker could allow the attacker easier access 2744 to the larger MANET domain. 2746 The remainder of the objects in the SMF-MIB module are performance 2747 counter objects. While these give an indication of the activity of 2748 the SMF process on this node, it is not expected that exposing these 2749 values pose a security risk to the MANET network. 2751 SNMP versions prior to SNMPv3 did not include adequate security. 2752 Even if the network itself is secure (for example by using IPSec), 2753 even then, there is no control as to who on the secure network is 2754 allowed to access and GET/SET (read/change/create/delete) the objects 2755 in this MIB module. 2757 Implementations MUST provide the security features described by the 2758 SNMPv3 framework (see [RFC3410] ), including full support for 2759 authentication and privacy via the User-based Security Model (USM) 2760 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2761 MAY also provide support for the Transport Security Model (TSM) 2762 [RFC5591] in combination with a secure transport such as SSH 2763 [RFC5592] or TLS/DTLS [RFC6353]. 2765 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2766 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2767 enable cryptographic security. It is then a customer/operator 2768 responsibility to ensure that the SNMP entity giving access to an 2769 instance of this MIB module is properly configured to give access to 2770 the objects only to those principals (users) that have legitimate 2771 rights to indeed GET or SET (change/create/delete) them. 2773 10. Applicability Statement 2775 This document describes objects for configuring parameters of the 2776 Simplified Multicast Forwarding [RFC6621] process on a Mobile Ad-Hoc 2777 Network (MANET) router. This MIB module, denoted SMF-MIB, also 2778 reports state and performance information and notifications. This 2779 section provides some examples of how this MIB module can be used in 2780 MANET network deployments. A fuller discussion of MANET network 2781 management use cases and challenges will be provided elsewhere. 2783 SMF is designed to allow MANET routers to forward IPv4 and IPv6 2784 packets over the MANET and cover the MANET nodes through the 2785 automatic discovery of efficient estimates of the Minimum Connected 2786 Dominating Set (MCDS) of nodes within the MANET. The MCDS are 2787 estimated using the Relay Set Selection Algorithms (RSSAs) discussed 2788 within this document. In the following, three scenarios are listed 2789 where this MIB module is useful, i.e., 2791 o For a Parking Lot Initial Configuration Situation - it is common 2792 for the vehicles comprising the MANET being forward deployed at a 2793 remote location, e.g., the site of a natural disaster, to be off- 2794 loaded in a parking lot where an initial configuration of the 2795 networking devices is performed. The configuration is loaded into 2796 the devices from a fixed location Network Operation Center (NOC) 2797 at the parking lot and the vehicles are stationary at the parking 2798 lot while the configuration changes are made. Standards-based 2799 methods for configuration management from the co-located NOC are 2800 necessary for this deployment option. The set of interesting 2801 configuration objects for the SMF process are listed within this 2802 MIB module. 2804 o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed 2805 NOC - Here the vehicles carrying the MANET routers carry multiple 2806 wireless interfaces, one of which is a relatively low-bandwidth 2807 on-the-move satellite connection which interconnects a fix NOC to 2808 the nodes of the MANET. Standards-based methods for monitoring 2809 and fault management from the fixed NOC are necessary for this 2810 deployment option. 2812 o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for 2813 larger vehicles, a hierarchical network management arrangement is 2814 useful. Centralized network management is performed from a fixed 2815 NOC while local management is performed locally from within the 2816 vehicles. Standards-based methods for configuration, monitoring 2817 and fault management are necessary for this deployment option. 2819 Here we provide an example of the simplest of configurations to 2820 establish an operational multicast forwarding capability in a MANET. 2821 This discussion only identifies the configuration necessary through 2822 the SMF-MIB module and assumes that other configuration has occurred. 2823 Assume that the MANET is to support only IPv4 addressing and that the 2824 MANET nodes are to be configured in the context of the Parking Lot 2825 Initialization case above. Then the SMF-MIB module defines ten 2826 configuration OIDs and two configuration tables, i.e., the 2827 smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten 2828 OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL 2829 clauses which allow for a functional configuration of the SMF process 2830 within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the 2831 smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP 2832 toolkit),: 2834 snmpset [options] .0 a 192.168.1.100 2836 If the smfCfgAddrForwardingTable is left empty, then the SMF local 2837 forwarder will forward all multicast addresses. So this table does 2838 not require configuration if you want to have the MANET forward all 2839 multicast addresses. 2841 All that remains is to configure at least one row in the 2842 smfCfgInterfaceTable. Assume that the node has a wireless interface 2843 with an ='wlan0' and an ='1'. All of the objects in 2844 the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only 2845 the RowStatus object needs to be set. So the SMF process will be 2846 activated on the 'wlan0' interface by the following network manager 2847 snmpset command: 2849 snmpset [options] .1 i active(1) 2851 At this point, the configured forwarder will begin a Classical 2852 Flooding algorithm to forward all multicast addresses IPv4 packets it 2853 receives. 2855 To provide a more efficient multicast forwarding within the MANET, 2856 the network manager could walk the smfCapabilitiesTable to identify 2857 other SMF operational modes, e.g.,: 2859 snmpwalk [options] 2861 SMF-MIB::smfCapabilitiesIndex.1 = INTEGER: 1 2863 SMF-MIB::smfCapabilitiesIndex.2 = INTEGER: 2 2865 SMF-MIB::smfCapabilitiesOpModeID.1 = INTEGER: cfOnly(1) 2867 SMF-MIB::smfCapabilitiesOpModeiD.2 = INTEGER: independent(2) 2869 SMF-MIB::smfCapabilitiesRssaID.1 = INTEGER: cF(1) 2871 SMF-MIB::smfCapabilitiesRssaID.2 = INTEGER: eCDS(3) 2873 In this example, the forwarding device also supports the Extended 2874 Connected Dominating Set (eCDS) RSSA with the forwarder in the 2875 'independent(2)' operational mode. If the network manager were to 2876 then issue an snmpset, e.g.,: 2878 snmpset [options] .0 i 2 2880 then the local forwarder would switch if forwarding behavior from 2881 Classical Flooding to the more efficient eCDS flooding. 2883 11. IANA Considerations 2885 This document defines two MIB modules: 2887 o SMF-MIB is defined in Section 7 and is an experimental MIB module. 2889 o IANA-SMF-MIB is defined in Section 8 and is an IANA MIB module 2890 that IANA is requested to maintain. 2892 Thus, there are three actions requested of IANA: 2894 1. IANA is requested to allocate an OBJECT IDENTIFIER value and 2895 record it in the SMI Numbers registry in the sub-registry called "SMI 2896 Experimental Codes" under the experimental branch (1.3.6.1.3). 2898 Decimal | Name | Description | Reference 2899 --------+---------+---------------+------------ 2900 xxxx | smfMib | SMF-MIB | [This.I-D] 2902 [RFC Editor Note: Please replace the tag "xxxx" in 2903 this document with the value assigned by IANA and 2904 remove this note.] 2906 2. IANA is requested to allocate an OBJECT IDENTIFIER value and 2907 record it in the SMI Numbers registry in the sub-registry called "SMI 2908 Network Management MGMT Codes Internet-standard MIB" under the mib-2 2909 branch (1.3.6.1.2.1). 2911 Decimal | Name | Description | Reference 2912 --------+---------------+-----------------+------------ 2913 kkkk | ianaSmfMIB | IANA-SMF-MIB | [This.I-D] 2915 [RFC Editor Note: Please replace the tag "kkkk" in 2916 this document with the value assigned by IANA and 2917 remove this note.] 2919 3. IANA is requested to maintain a MIB module called ianaSmfMIB and 2920 populate it with the initial MIB module defined in Section 8 of this 2921 document by creating a new entry in the registry "IANA Maintained 2922 MIBs" called "IANA-SMF-MIB". 2924 12. Contributors 2926 This MIB document uses the template authored by D. Harrington which 2927 is based on contributions from the MIB Doctors, especially Juergen 2928 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 2930 13. Acknowledgements 2932 The authors would like to acknowledge the valuable comments from Sean 2933 Harnedy in the early phases of the development of this MIB module. 2934 The authors would like to thank Adrian Farrel, Dan Romascanu, Juergen 2935 Shoenwaelder, Stephen Hanna, and Brian Haberman for their careful 2936 review of this documenti and their insightful comments. We also wish 2937 to thank the entire MANET WG for many reviews of this document. 2938 Further the authors would like to thank James Nguyen for his careful 2939 review and comments on this MIB module and his work on the 2940 definitions of the follow-on MIB modules to configure specific RSSA 2941 algorithms related to SMF. Further, the authors would like to 2942 acknowledge to work of James Nguyen, Brian Little, Ryan Morgan and 2943 Justin Dean on their software development of the SMF-MIB. 2945 14. References 2947 14.1. Normative References 2949 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2950 MIB", RFC 2863, June 2000. 2952 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2953 "Introduction and Applicability Statements for Internet- 2954 Standard Management Framework", RFC 3410, December 2002. 2956 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2957 Architecture for Describing Simple Network Management 2958 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2959 December 2002. 2961 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 2962 Simple Network Management Protocol (SNMP)", STD 62, 2963 RFC 3418, December 2002. 2965 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2966 Schoenwaelder, "Textual Conventions for Internet Network 2967 Addresses", RFC 4001, February 2005. 2969 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2970 Requirement Levels", BCP 14, RFC 2119, March 1997. 2972 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2973 Schoenwaelder, Ed., "Structure of Management Information 2974 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2976 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2977 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2978 STD 58, RFC 2579, April 1999. 2980 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2981 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2982 April 1999. 2984 [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, 2985 May 2012. 2987 14.2. Informative References 2989 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2990 (USM) for version 3 of the Simple Network Management 2991 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2993 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2994 Advanced Encryption Standard (AES) Cipher Algorithm in the 2995 SNMP User-based Security Model", RFC 3826, June 2004. 2997 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2998 for the Simple Network Management Protocol (SNMP)", 2999 STD 78, RFC 5591, June 2009. 3001 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 3002 Shell Transport Model for the Simple Network Management 3003 Protocol (SNMP)", RFC 5592, June 2009. 3005 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 3006 Model for the Simple Network Management Protocol (SNMP)", 3007 STD 78, RFC 6353, July 2011. 3009 [RFC4293] Routhier, S., "Management Information Base for the 3010 Internet Protocol (IP)", RFC 4293, April 2006. 3012 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 3013 MIB", RFC 5132, December 2007. 3015 Appendix A. 3017 *************************************************************** 3018 * Note to the RFC Editor (to be removed prior to publication) * 3019 * * 3020 * 1) The reference to RFCXXXX throughout this document point * 3021 * to the current draft-ietf-manet-smf-xx.txt. This needs * 3022 * to be replaced with the XXXX RFC number for the SMF * 3023 * publication. * 3024 * * 3025 * 2) This document also contains the IANA-SMF-MIB module * 3026 * which is defined by this specification above. IANA should * 3027 * take over the IANA-SMF-MIB and keep it synchronized with * 3028 * the registries identified within the contained * 3029 * IANAsmfOpModeIdTC and IANAsmfRssaIdTC TEXTUAL-CONVENTIONs. * 3030 * * 3031 *************************************************************** 3033 Authors' Addresses 3035 Robert G. Cole 3036 US Army CERDEC 3037 6010 Frankford Road 3038 Aberdeen Proving Ground, Maryland 21005 3039 USA 3041 Phone: +1 443 395 8744 3042 EMail: robert.g.cole@us.army.mil 3044 Joseph Macker 3045 Naval Research Laboratory 3046 Washington, D.C. 20375 3047 USA 3049 EMail: macker@itd.nrl.navy.mil 3051 Brian Adamson 3052 Naval Research Laboratory 3053 Washington, D.C. 20375 3054 USA 3056 EMail: adamson@itd.nrl.navy.mil