idnits 2.17.1 draft-ietf-trill-oam-mib-11.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 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 712 has weird spacing: '...d reply is tr...' == Line 723 has weird spacing: '...d. The maxim...' -- The document date (October 12, 2015) is 3118 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'CFM' is mentioned on line 378, but not defined == Missing Reference: 'RFC3414' is mentioned on line 2146, but not defined == Missing Reference: 'RFC3826' is mentioned on line 2146, but not defined == Missing Reference: 'RFC5591' is mentioned on line 2148, but not defined == Missing Reference: 'RFC5592' is mentioned on line 2149, but not defined == Missing Reference: 'RFC6353' is mentioned on line 2149, but not defined == Unused Reference: 'LLDP-MIB' is defined on line 2212, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MIB' Summary: 1 error (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TRILL Working Group Deepak Kumar 3 Internet Draft Samer Salam 4 Cisco 5 Intended Status: Standard Track Tissa Senevirathne 6 Consultant 7 Expires April 2016 October 12, 2015 9 TRILL OAM MIB 10 draft-ietf-trill-oam-mib-11.txt 12 Abstract 14 This document specifies the Management Information Base (MIB) for the 15 IETF TRILL (Transparent Interconnection of Lots of Links) OAM 16 (Operations, Administration, and Maintenance) objects. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on April 14, 2016. 35 Copyright Notice 37 Copyright (c) 2015 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. The Internet-Standard Management Framework . . . . . . . . . . 2 54 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 5. Structure of the MIB module . . . . . . . . . . . . . . . . . . 4 57 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . . 4 58 5.2. The TRILL OAM MIB Subtree . . . . . . . . . . . . . . . . 5 59 5.3.1. The Notifications Subtree . . . . . . . . . . . . . . 5 60 5.3.2. The Table Structures . . . . . . . . . . . . . . . . . 5 61 5.3.2.1. trillOamMepTable Objects . . . . . . . . . . . . . 5 62 5.3.2.2. trillOamMepFlowCfgTable Objects . . . . . . . . . . 6 63 5.3.2.3. trillOamPtrTable Objects . . . . . . . . . . . . . 6 64 5.3.2.4. trillOamMtvrTable Objects . . . . . . . . . . . . . 6 65 5.3.2.5. trillOamMepDbTable Objects . . . . . . . . . . . . 6 66 6. Relationship to other MIB modules . . . . . . . . . . . . . . . 7 67 6.1. Relationship to the IEEE8021-TC-MIB . . . . . . . . . . . 7 68 6.2. Relationship to the IEEE8021-CFM-MIB . . . . . . . . . . . 8 69 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 70 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 8 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 43 72 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 46 73 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 47 74 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 47 75 11.1. Normative References . . . . . . . . . . . . . . . . . . 47 76 11.2. Informative References . . . . . . . . . . . . . . . . . 48 78 1. Introduction 80 Overall, TRILL OAM (Operations, Administration, and Maintenance) 81 meets the requirements given in [RFC6905]. The general framework for 82 TRILL OAM is specified in [RFC7174]. The details of the Fault 83 Management (FM) solution, conforming to that framework, are presented 84 in [RFC7455]. The solution leverages the message format defined in 85 Ethernet Connectivity Fault Management (CFM) [802.1Q] as the basis 86 for the TRILL OAM message channel. 88 This document uses the CFM MIB modules defined in [802.1Q] as the 89 basis for TRILL OAM MIB and augments the existing tables to add new 90 TRILL managed objects required by TRILL. This document further 91 specifies a new table with associated managed objects for TRILL OAM 92 specific capabilities. 94 2. The Internet-Standard Management Framework 95 For a detailed overview of the documents that describe the current 96 Internet-Standard Management Framework, please refer to section 7 of 97 RFC 3410 [RFC3410]. 99 Managed objects are accessed via a virtual information store, termed 100 the Management Information Base or MIB. MIB objects are generally 101 accessed through the Simple Network Management Protocol (SNMP). 102 Objects in the MIB are defined using the mechanisms defined in the 103 Structure of Management Information (SMI). This memo specifies a MIB 104 module that is compliant to the SMIv2, which is described in STD 58, 105 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 106 [RFC2580]. 108 3. Conventions 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 112 "OPTIONAL" in this document are to be interpreted as described in 113 RFC-2119 [RFC2119]. 115 Acronyms used in the document include the following: 117 MTVM - Multi-destination Tree Verification Message [RFC7455] 119 MTVR - Multi-destination Tree Verification Reply [RFC7455] 121 PTM - Path Trace Message [RFC7455] 123 PTR - Path Trace Reply [RFC7455] 125 MEP - Maintenance End Point [RFC7174] [802.1Q] 127 MIP - Maintenance Intermediate Point [RFC7174] [802.1Q] 129 MP - Maintenance Point [RFC7174] 131 CCM - Continuity Check Message [802.1Q] 133 FGL - Fine-Grained Label 135 LBM - Loopback Message [802.1Q] 137 LBR - Loopback Reply [802.1Q] 139 TRILL - Transparent Interconnection of Lots of Links [RFC6325] 141 4. Overview 143 The TRILL-OAM-MIB module provides an overall framework for managing 144 TRILL OAM. It leverages the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB 145 modules defined in [802.1Q], and augments the Maintenance End Point 146 (MEP) and MEP Db entries. It also adds a new table for TRILL OAM 147 specific messages. 149 5. Structure of the MIB module 151 Objects in this MIB module are arranged into subtrees. Each subtree is 152 organized as a set of related objects. The various subtrees are shown 153 below, supplemented with the required elements of the IEEE8021-CFM-MIB 154 module. 156 5.1. Textual Conventions 158 Textual conventions are defined to represent object types relevant to 159 the TRILL OAM MIB. 161 5.2. The TRILL OAM MIB Subtree 163 TRILL-OAM MIB Tree describe below consists of trilloamNotifications 164 (Traps) and trillOamMibObjects. The trilloamNotifications are sent to 165 the management entity whenever a MEP loses/restores contact with its 166 peer Flow MEPs. 168 The TRILL OAM MIB Per MEP Objects are defined in the trillOamMepTable. 169 The trillOamMepTable augments the dot1agCfmMepEntry (please see section 170 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally 171 defined for an individual MEP and its associated Flow. 173 TRILL-OAM-MIB 175 |--trillOamNotifications (trillOamMib 0} 177 |--trillOamFaultAlarm 179 |--trillOamMibObjects {trillOamMib 1} 181 |--trillOamMep {trillOamMibObjects 1} 183 |--trillOamMepTable {trillOamMep 1} - Local TRLL config 185 |--trillOamMepFlowCfgTable 187 |--trillOamPtrTable 189 |--trillOamMtvrTable 191 |--trillOamMepDbTable 193 5.3.1. The Notifications Subtree 195 Notifications (fault alarms) are sent to the management entity with the 196 OID of the MEP that has detected the fault. Notifications are generated 197 whenever MEP loses/restores contact with its peer Flow MEPs. 199 5.3.2. The Table Structures 201 The TRILL OAM MIB Per MEP Objects are defined in the trillOamMepTable. 202 The trillOamMepTable augments the dot1agCfmMepEntry (please see section 203 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally 204 defined for an individual MEP and its associated Flow. 206 5.3.2.1. trillOamMepTable Objects 207 This table is an extension of the dot1agCfmMepTable. Rows are 208 automatically added or deleted from this table based upon row 209 creation and destruction of the dot1agCfmMepTable. 211 This table represents the local MEP TRILL OAM configuration table. 212 The primary purpose of this table is provide local parameters for the 213 TRILL OAM function found in [RFC7455] and instantiated at a MEP. 215 5.3.2.2. trillOamMepFlowCfgTable Objects 217 Each row in this table represents a Flow Configuration Entry for the 218 associated MEP. This table uses four indices. The first three indices 219 are the indices of the Maintenance Domain, MaNet, and MEP tables. The 220 fourth index is the specific Flow Configuration Entry on the selected 221 MEP. Some write-able objects in this table are only applicable in 222 certain cases (as described under each object below), and attempts to 223 write values for them in other cases will be ignored. 225 5.3.2.3. trillOamPtrTable Objects 227 Each row in this table represents a Path Trace reply Entry for the 228 Defined MEP and Transaction. This table uses four indices. The first 229 three indices identify the MEP and the fourth index specifies the 230 transaction identifier. This transaction identifier uniquely 231 identifies the response for a MEP, which can have multiple flow. 233 5.3.2.4. trillOamMtvrTable Objects 235 This table includes managed objects for the Multi-Destination Reply. 236 Each row in the table represents a Multi-destination Reply Entry for 237 the defined MEP and Transaction. This table uses the following five 238 indices: 1) Maintenance Domain, 2) MANET, 3) MEP tables, 4) 239 Transaction identifier of selected MEP, and 5) receive order of 240 Multi-destination replies. 242 Some write-able objects in this table are only applicable in certain 243 cases (as described under each object below), and attempts to write a 244 value for them in other cases will be ignored. 246 5.3.2.5. trillOamMepDbTable Objects 248 This table is an augmentation of the dot1agCfmMepDbTable, and rows 249 are automatically added or deleted from this table based upon row 250 creation and destruction of the dot1agCfmMepDbTable. 252 6. Relationship to other MIB modules 254 The IEEE8021-CFM-MIB, and LLDP-MIB contain objects that are relevant 255 to the TRILL OAM MIB. Management objects contained in these modules 256 are not duplicated here, to reduce overlap to the extent possible. 257 From the IEEE8021-CFM-MIB following objects are imported 259 o dot1agCfmMdIndex 261 o dot1agCfmMaIndex 263 o dot1agCfmMepIdentifier 265 o dot1agCfmMepEntry 267 o dot1agCfmMepDbEntry 269 o Dot1agCfmIngressActionFieldValue 271 o Dot1agCfmEgressActionFieldValue 273 o Dot1agCfmRemoteMepState 275 From the LLDP-MIB following objects are imported 277 o LldpChassisId 279 o LldpChassisIdSubtype 281 o LldpPortId 283 6.1. Relationship to the IEEE8021-TC-MIB 285 In TRILL, traffic labeling can be done using either a 12-bit VLAN 286 or a 24-bit fine grain label [RFC7172]. 288 The IEEE8021-TC-MIB definition of IEEE8021ServiceSelectorType 289 includes the following two values: 291 - 1 representing a vlanId, and 293 - 2 representing a 24-bit isid 295 We have chosen to use value 2 for TRILL's fine grain label. As 296 such, TRILL-OAM-MIB will import IEEE8021ServiceSelectorType, 297 IEEE8021ServiceSelectorValueOrNone, and 298 IEEE8021ServiceSelectorValue from IEEE8021-TC-MIB. 300 6.2. Relationship to the IEEE8021-CFM-MIB 302 trillOamMepTable augments dot1agCfmMepEntry. Implementation of 303 IEEE8021-CFM-MIB is required as we are augmenting the IEEE-CFM-MIB 304 Table. Objects/Tables that are not applicable to a TRILL 305 implementation have to be handled by the TRILL implementation back 306 end and appropriate default values, as described in IEEE8021-CFM-MIB, 307 have to be returned. 309 The TRILL OAM implementation doesn't support the Link Trace Message 310 or Link Trace Reply since, as described in RFC7455, the Path Trace 311 Message and Reply for unicast traffic and Multi-destination Tree 312 verification Message and Reply for multicast traffic have been 313 substituted for them. Statistics for these messages should default as 314 per IEEE8021-CFM-MIB. 316 6.3. MIB modules required for IMPORTS 318 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 319 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IEEE-8021-CFM-MIB, LLDP- 320 MIB. 322 7. Definitions 324 TRILL-OAM-MIB DEFINITIONS ::= BEGIN 326 IMPORTS 328 MODULE-IDENTITY, 329 OBJECT-TYPE, 330 Counter32, 331 Unsigned32, 332 Integer32, 333 mib-2, 334 NOTIFICATION-TYPE 335 FROM SNMPv2-SMI 336 RowStatus, 337 TruthValue, 338 TimeStamp, 339 MacAddress 340 FROM SNMPv2-TC 341 OBJECT-GROUP, 342 NOTIFICATION-GROUP, 343 MODULE-COMPLIANCE 344 FROM SNMPv2-CONF 345 dot1agCfmMdIndex, 346 dot1agCfmMaIndex, 347 dot1agCfmMepIdentifier, 348 dot1agCfmMepEntry, 349 dot1agCfmMepDbEntry, 350 Dot1agCfmIngressActionFieldValue, 351 Dot1agCfmEgressActionFieldValue, 352 Dot1agCfmRemoteMepState 353 FROM IEEE8021-CFM-MIB 354 LldpChassisId, 355 LldpChassisIdSubtype, 356 LldpPortId, 357 LldpPortIdSubtype 358 FROM LLDP-MIB; 360 trillOamMib MODULE-IDENTITY 361 LAST-UPDATED "201508231200Z" 362 ORGANIZATION "IETF TRILL WG" 363 CONTACT-INFO 364 "E-mail: trill@ietf.org" 365 DESCRIPTION 366 "This MIB module contains the management objects for the 367 management of TRILL Services Operations, Administration 368 and Maintenance. 369 Initial version. Published as RFC xxxx. 371 ------------------------------------------------------------- 372 Reference Overview 374 A number of base documents have been used to create the 375 Textual Conventions MIB. The following are the 376 abbreviations for the baseline documents: 378 [CFM] refers to 'Connectivity Fault Management', 379 IEEE 802.1Q-2014, December 2014 380 [Q.840.1] refers to 'ITU-T Requirements and analysis for 381 NMS-EMS management interface of Ethernet over Transport and 382 Metro Ethernet Network (EoT/MEN)', March 2007 383 [Y.1731] refers to ITU-T Y.1731 'OAM functions and mechanisms 384 for Ethernet based networks', February 2011 385 ------------------------------------------------------------- 387 Abbreviations Used 389 Term Definition 390 CCM Continuity Check Message 391 CFM Connectivity Fault Management 392 CoS Class of Service 393 IEEE Institute of Electrical and Electronics 394 Engineers 396 IETF Internet Engineering Task Force 397 ITU-T International Telecommunication Union - 398 Telecommunication Standardization Bureau 399 MAC Media Access Control 400 MA Maintenance Association (equivalent to a MEG) 401 MD Maintenance Domain (equivalent to a OAM 402 Domain in MEF 17) 403 MD Level Maintenance Domain Level (equivalent to a 404 MEG level) 405 ME Maintenance Entity 406 MEG Maintenance Entity Group (equivalent to a MA) 407 MEG Level Maintenance Entity Group Level (equivalent to 408 MD Level) 409 MEP Maintenance Association End Point or MEG End 410 Point 411 MIB Management Information Base 412 MIP Maintenance Domain Intermediate Point or 413 MEG Intermediate Point 414 MP Maintenance Point. One of either a MEP or a MIP 415 OAM Operations, Administration, and Maintenance 416 On-Demand OAM actions that are initiated via 417 manual intervention for a limited time to carry 418 out diagnostics. On-Demand OAM can result in 419 singular or periodic OAM actions during the 420 diagnostic time interval 421 PDU Protocol Data Unit 422 RFC Request for Comment 423 SNMP Simple Network Management Protocol 424 SNMP Agent An SNMP entity containing one or more command 425 responder and/or notification originator 426 applications(along with their associated SNMP 427 engine). Typically implemented in Network 428 Element. 429 SNMP Manager An SNMP entity containing one or more command 430 generator and/or notification receiver 431 applications (along with their associated SNMP 432 engine). Typically implemented in an 433 EMS or NMS. 434 TLV Type Length Value, a method of encoding Objects 435 UTC Coordinated Universal Time 436 UNI User-to-Network Interface 437 VLAN Virtual LAN 438 PTR Path Trace Reply 439 PTM Path Trace Message 440 MTVR Multi-destination Tree Verification Reply 441 MTVM Multi-destination Tree Verification Message" 443 REVISION "201508231200Z" 444 DESCRIPTION 445 "Initial version. Published as RFC xxxx." 446 ::= { mib-2 12000 } 448 -- RFC Ed.: assigned by IANA, see section 9 for details 449 -- 450 -- ***************************************************************** 451 -- Object definitions in the TRILL OAM MIB Module 452 -- ***************************************************************** 454 trillOamNotifications OBJECT IDENTIFIER 455 ::= { trillOamMib 0 } 457 trillOamMibObjects OBJECT IDENTIFIER 458 ::= { trillOamMib 1 } 460 trillOamMibConformance OBJECT IDENTIFIER 461 ::= { trillOamMib 2 } 463 -- ***************************************************************** 464 -- Groups in the TRILL OAM MIB Module 465 -- ***************************************************************** 467 trillOamMep OBJECT IDENTIFIER 468 ::= { trillOamMibObjects 1 } 470 -- ***************************************************************** 471 -- TRILL OAM MEP Configuration 472 -- ***************************************************************** 474 trillOamMepTable OBJECT-TYPE 475 SYNTAX SEQUENCE OF TrillOamMepEntry 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "This table is an extension of the dot1agCfmMepTable and 480 rows are automatically added or deleted from this table 481 based upon row creation and destruction of the 482 dot1agCfmMepTable. 484 This table represents the local MEP TRILL OAM 485 configuration table. The primary purpose of this table 486 is provide local parameters for the TRILL OAM function 487 found in RFC 7455 and instantiated at a MEP." 488 REFERENCE "RFC 7455" 489 ::= { trillOamMep 1 } 491 trillOamMepEntry OBJECT-TYPE 492 SYNTAX TrillOamMepEntry 493 MAX-ACCESS not-accessible 494 STATUS current 495 DESCRIPTION 496 "The conceptual row of trillOamMepTable." 497 AUGMENTS { dot1agCfmMepEntry } 498 ::= { trillOamMepTable 1 } 500 TrillOamMepEntry ::= SEQUENCE { 501 trillOamMepRName Unsigned32, 502 trillOamMepNextPtmTId Counter32, 503 trillOamMepNextMtvmTId Counter32, 504 trillOamMepPtrIn Counter32, 505 trillOamMepPtrInOutofOrder Counter32, 506 trillOamMepPtrOut Counter32, 507 trillOamMepMtvrIn Counter32, 508 trillOamMepMtvrInOutofOrder Counter32, 509 trillOamMepMtvrOut Counter32, 510 trillOamMepTxLbmDestRName Unsigned32, 511 trillOamMepTxLbmHC Unsigned32, 512 trillOamMepTxLbmReplyModeOob TruthValue, 513 trillOamMepTransmitLbmReplyIp OCTET STRING, 514 trillOamMepTxLbmFlowEntropy OCTET STRING, 515 trillOamMepTxPtmDestRName Unsigned32, 516 trillOamMepTxPtmHC Unsigned32, 517 trillOamMepTxPtmReplyModeOob TruthValue, 518 trillOamMepTransmitPtmReplyIp OCTET STRING, 519 trillOamMepTxPtmFlowEntropy OCTET STRING, 520 trillOamMepTxPtmStatus TruthValue, 521 trillOamMepTxPtmResultOK TruthValue, 522 trillOamMepTxPtmSeqNumber Unsigned32, 523 trillOamMepTxPtmMessages Integer32, 524 trillOamMepTxMtvmTree Unsigned32, 525 trillOamMepTxMtvmHC Unsigned32, 526 trillOamMepTxMtvmReplyModeOob TruthValue, 527 trillOamMepTransmitMtvmReplyIp OCTET STRING, 528 trillOamMepTxMtvmFlowEntropy OCTET STRING, 529 trillOamMepTxMtvmStatus TruthValue, 530 trillOamMepTxMtvmResultOK TruthValue, 531 trillOamMepTxMtvmMessages Integer32, 532 trillOamMepTxMtvmSeqNumber Unsigned32, 533 trillOamMepTxMtvmScopeList OCTET STRING, 534 trillOamMepDiscontinuityTime TimeStamp 535 } 537 trillOamMepRName OBJECT-TYPE 538 SYNTAX Unsigned32 (0..65471) 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "This object contains the Rbridge NickName of the TRILL 543 Rbridge as defined in RFC 6325 section 3.7." 544 REFERENCE "RFC 7455 and RFC 6325 section 3.7" 545 ::= { trillOamMepEntry 1 } 547 trillOamMepNextPtmTId OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "Next sequence number/transaction identifier to be sent in a 553 Multi-destination message. This sequence number can be zero 554 because it wraps around. Implementation of this identifier 555 should be should provide a unique code value in order to 556 identify the Transaction ID for a MEP with multiple flows." 557 REFERENCE "RFC 7455 10.1.1" 558 ::= { trillOamMepEntry 2 } 560 trillOamMepNextMtvmTId OBJECT-TYPE 561 SYNTAX Counter32 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "Next sequence number/transaction identifier to be sent in a 566 Multi-destination message. This sequence number can be zero 567 because it wraps around. Implementation should be unique to 568 identify Transaction ID for a MEP with multiple flows." 569 REFERENCE "RFC 7455 11.2.1" 570 ::= { trillOamMepEntry 3 } 572 trillOamMepPtrIn OBJECT-TYPE 573 SYNTAX Counter32 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "Total number of valid, in-order Path Trace Replies 578 received." 579 REFERENCE "RFC 7455 section 10" 580 ::= { trillOamMepEntry 4 } 582 trillOamMepPtrInOutofOrder OBJECT-TYPE 583 SYNTAX Counter32 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "Total number of valid, out-of-order Path Trace Replies 588 received." 589 REFERENCE "RFC 7455 section 10" 590 ::= { trillOamMepEntry 5 } 592 trillOamMepPtrOut OBJECT-TYPE 593 SYNTAX Counter32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "Total number of valid, Path Trace Replies 598 transmitted." 599 REFERENCE "RFC 7455 section 10" 600 ::= { trillOamMepEntry 6 } 602 trillOamMepMtvrIn OBJECT-TYPE 603 SYNTAX Counter32 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "Total number of valid, in-order Multi-destination 608 Replies received." 609 REFERENCE "RFC 7455 section 11" 610 ::= { trillOamMepEntry 7 } 612 trillOamMepMtvrInOutofOrder OBJECT-TYPE 613 SYNTAX Counter32 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "Total number of valid, out-of-order Multi-destination 618 Replies received." 619 REFERENCE "RFC 7455 section 11" 620 ::= { trillOamMepEntry 8 } 622 trillOamMepMtvrOut OBJECT-TYPE 623 SYNTAX Counter32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "Total number of valid, Multi-destination Replies 628 transmitted." 629 REFERENCE "RFC 7455 section 11" 630 ::= { trillOamMepEntry 9 } 632 trillOamMepTxLbmDestRName OBJECT-TYPE 633 SYNTAX Unsigned32 (0..65471) 634 MAX-ACCESS read-create 635 STATUS current 636 DESCRIPTION 637 "The Target Destination Rbridge NickName Field, as 638 defined in RFC 6325 section 3.7, to be transmitted." 639 REFERENCE "RFC 7455 and RFC 6325 section 3.7" 640 ::= { trillOamMepEntry 10 } 642 trillOamMepTxLbmHC OBJECT-TYPE 643 SYNTAX Unsigned32(1..63) 644 MAX-ACCESS read-create 645 STATUS current 646 DESCRIPTION 647 "The Hop Count to be transmitted. 648 " 649 REFERENCE "RFC 7455 section 9 and 3" 650 ::= { trillOamMepEntry 11 } 652 trillOamMepTxLbmReplyModeOob OBJECT-TYPE 653 SYNTAX TruthValue 654 MAX-ACCESS read-create 655 STATUS current 656 DESCRIPTION 657 "True indicates that the Reply to an LBM is out of 658 band and out of band IP Address TLV is to be 659 transmitted. False indicates that In band reply is 660 transmitted." 661 REFERENCE "RFC 7455 9.2.1" 662 ::= { trillOamMepEntry 12 } 664 trillOamMepTransmitLbmReplyIp OBJECT-TYPE 665 SYNTAX OCTET STRING (SIZE (4..16)) 666 MAX-ACCESS read-create 667 STATUS current 668 DESCRIPTION 669 "The IP address for an out of band IP Address TLV 670 that is to be transmitted. Maximum length for IPv6 671 is 16 OCTET and IPv4 is 4 OCTET." 672 REFERENCE "RFC 7455 section 3" 673 ::= { trillOamMepEntry 13 } 675 trillOamMepTxLbmFlowEntropy OBJECT-TYPE 676 SYNTAX OCTET STRING (SIZE (96)) 677 MAX-ACCESS read-create 678 STATUS current 679 DESCRIPTION 680 "96 Byte Flow Entropy, as defined in RFC 7455, to 681 be transmitted." 682 REFERENCE "RFC 7455 section 3" 683 ::= { trillOamMepEntry 14 } 685 trillOamMepTxPtmDestRName OBJECT-TYPE 686 SYNTAX Unsigned32 (0..65471) 687 MAX-ACCESS read-create 688 STATUS current 689 DESCRIPTION 690 "The Target Destination Rbridge NickName Field, 691 as defined in RFC 6325 section 3.7, to be transmitted." 692 REFERENCE "RFC 7455 and RFC 6325 section 3.7" 693 ::= { trillOamMepEntry 15 } 695 trillOamMepTxPtmHC OBJECT-TYPE 696 SYNTAX Unsigned32 (1..63) 697 MAX-ACCESS read-create 698 STATUS current 699 DESCRIPTION 700 "The Hop Count field to be transmitted." 701 REFERENCE "RFC 7455 section 3" 702 ::= { trillOamMepEntry 16 } 704 trillOamMepTxPtmReplyModeOob OBJECT-TYPE 705 SYNTAX TruthValue 706 MAX-ACCESS read-create 707 STATUS current 708 DESCRIPTION 709 "True indicates that a Reply to a PTM will be 710 out of band and the out of band IP Address TLV 711 is to be transmitted. False indicates that an 712 in band reply is transmitted." 713 REFERENCE "RFC 7455 section 10" 714 DEFVAL { false } 715 ::= { trillOamMepEntry 17 } 717 trillOamMepTransmitPtmReplyIp OBJECT-TYPE 718 SYNTAX OCTET STRING (SIZE (4..16)) 719 MAX-ACCESS read-create 720 STATUS current 721 DESCRIPTION 722 "The IP address for an out of band IP Address TLV 723 to be Transmitted. The maximum length for an 724 IPv6 address is 16 Octets. The maximum length 725 for an IPv4 address is 4 octets." 726 REFERENCE "RFC 7455 section 3 and 10" 727 ::= { trillOamMepEntry 18 } 729 trillOamMepTxPtmFlowEntropy OBJECT-TYPE 730 SYNTAX OCTET STRING (SIZE (96)) 731 MAX-ACCESS read-create 732 STATUS current 733 DESCRIPTION 734 "96 Byte Flow Entropy, as defined in RFC 7455, to be 735 transmitted." 736 REFERENCE "RFC 7455 section 3" 737 ::= { trillOamMepEntry 19 } 739 trillOamMepTxPtmStatus OBJECT-TYPE 740 SYNTAX TruthValue 741 MAX-ACCESS read-create 742 STATUS current 743 DESCRIPTION 744 "A Boolean flag set to true by the MEP Path Trace Initiator 745 State Machine or a MIB manager to indicate that another PTM is 746 being transmitted. This is Reset to false by the MEP 747 Initiator State Machine. The PTM managed objects in the MEP 748 table are used in a manner similar to that described for LBM 749 transmission in dot1agCfmMepTable. As per RFC7455 section 10, 750 Operation of the Path Trace Message is identical to the 751 Loopback Message except that it is first transmitted with a 752 TRILL Header Hop count field value of 1 and then retransmitted 753 with an incrementeing Hop count until a response is received 754 from the destination RBridge, or the Hop Count reaches a 755 configured maximum value. trillOamMepTxPtmStatus Status is 756 reset to FALSE by initiator when last PTM is transmitted." 757 REFERENCE "RFC 7455 section 10" 758 DEFVAL { false } 759 ::= { trillOamMepEntry 20 } 761 trillOamMepTxPtmResultOK OBJECT-TYPE 762 SYNTAX TruthValue 763 MAX-ACCESS read-create 764 STATUS current 765 DESCRIPTION 766 "Indicates the following results of the operation: 767 - true The Path Trace Message(s) will be (or has been) 768 sent. 769 - false The Path Trace Message(s) will not be sent." 770 REFERENCE "RFC 7455 section 10" 771 DEFVAL { true } 772 ::= { trillOamMepEntry 21 } 774 trillOamMepTxPtmSeqNumber OBJECT-TYPE 775 SYNTAX Unsigned32 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "The Path Trace Transaction Identifier of the first 780 PTM (to be) sent. The value returned is 781 undefined if trillOamMepTxPtmResultOK is false." 782 REFERENCE "RFC 7455 section 10" 783 ::= { trillOamMepEntry 22 } 785 trillOamMepTxPtmMessages OBJECT-TYPE 786 SYNTAX Integer32 (1..1024) 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "The number of Path Trace messages to be transmitted. 791 As per RFC 7455 section 10, the first Path Trace 792 Message is transmitted with a Hop count of 1 and an 793 RBridge may continue to retransmit the request at 794 periodic intervals with an incrementing Hop Count 795 until a response is received from the destination 796 Rbridge, or the Hop Count reaches a configured 797 maximum value. The event of the Destination 798 response being received or the Hop count reaching 799 its maximum is treated as a single Counter 800 increment of this object." 801 REFERENCE "RFC 7455 section 10" 802 ::= { trillOamMepEntry 23 } 804 trillOamMepTxMtvmTree OBJECT-TYPE 805 SYNTAX Unsigned32 806 MAX-ACCESS read-create 807 STATUS current 808 DESCRIPTION 809 "The Multi-destination Tree identifier, as 810 defined in RFC6325, for an MTVM." 811 ::= { trillOamMepEntry 24 } 813 trillOamMepTxMtvmHC OBJECT-TYPE 814 SYNTAX Unsigned32(1..63) 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "The Hop Count field to be transmitted. 819 " 820 REFERENCE "RFC 7455 section 3, RFC 6325 section 3" 821 ::= { trillOamMepEntry 25 } 823 trillOamMepTxMtvmReplyModeOob OBJECT-TYPE 824 SYNTAX TruthValue 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "True Indicates that the reply to an MTVM is out of 829 band and this out of band IP Address TLV is where the 830 reply is to be transmitted. 831 False indicates that an in band reply is transmitted." 832 REFERENCE "RFC 7455 section 11" 833 ::= { trillOamMepEntry 26 } 835 trillOamMepTransmitMtvmReplyIp OBJECT-TYPE 836 SYNTAX OCTET STRING (SIZE (4..16)) 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "IP address for an out of band IP Address TLV that is 841 to be transmitted. The Maximum length for IPv6 is 16 842 OCTET and IPv4 is 4 OCTET." 843 REFERENCE "RFC 7455 section 11" 844 ::= { trillOamMepEntry 27 } 846 trillOamMepTxMtvmFlowEntropy OBJECT-TYPE 847 SYNTAX OCTET STRING (SIZE (96)) 848 MAX-ACCESS read-create 849 STATUS current 850 DESCRIPTION 851 "96 Byte Flow Entropy, as defined in RFC 7455, to be 852 transmitted." 853 REFERENCE "RFC 7455 section 3" 854 ::= { trillOamMepEntry 28 } 856 trillOamMepTxMtvmStatus OBJECT-TYPE 857 SYNTAX TruthValue 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "A Boolean flag set to true by the MEP Multi Destination 862 Initiator State Machine or a MIB manager to indicate 863 that another MTVM is being transmitted. 864 Reset to false by the MEP Initiator State Machine. 865 The MTVM managed objects in the MEP table are used 866 in a manner similar to that described for LBM 867 transmission in dot1agCfmMepTable. As per RFC7455 868 section 11, operation of the MTVM Message is 869 identical to the Loopback Message except that it is 870 first transmitted with a TRILL Header Hop count 871 field value of 1 and it is retransmitted incrementing 872 the Hop count until a response is received from the 873 destination RBridge or the Hop Count reaches a 874 configured maximum value. trillOamMepTxMtvmStatus 875 Status is reset to FALSE by the initiator when the last 876 MTVM is transmitted." 877 REFERENCE "RFC 7455 section 11" 878 DEFVAL { false } 879 ::= { trillOamMepEntry 29 } 881 trillOamMepTxMtvmResultOK OBJECT-TYPE 882 SYNTAX TruthValue 883 MAX-ACCESS read-create 884 STATUS current 885 DESCRIPTION 886 "Indicates the result of the operation in 887 the following way: 888 - true The Multi-destination Message(s) will be 889 (or has been) sent. 890 - false The Multi-destination Message(s) will not be sent." 891 REFERENCE "RFC 7455 section 11" 892 DEFVAL { true } 893 ::= { trillOamMepEntry 30 } 895 trillOamMepTxMtvmMessages OBJECT-TYPE 896 SYNTAX Integer32 (1..1024) 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "The number of Multi Destination messages to be transmitted. 901 The Rbridge transmit the Multi Destination message 902 incrementing the session Identification Number at periodic 903 interval until this count expires." 904 REFERENCE "RFC 7455 section 11" 905 ::= { trillOamMepEntry 31 } 907 trillOamMepTxMtvmSeqNumber OBJECT-TYPE 908 SYNTAX Unsigned32 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "The Multi-destination Transaction Identifier of the 913 first MTVM (to be) 914 sent. The value returned is undefined if 915 trillOamMepTxMtvmResultOK is false." 916 REFERENCE "RFC 7455 section 11" 917 ::= { trillOamMepEntry 32 } 919 trillOamMepTxMtvmScopeList OBJECT-TYPE 920 SYNTAX OCTET STRING 921 MAX-ACCESS read-create 922 STATUS current 923 DESCRIPTION 924 "The Multi-destination Rbridge Scope list, which 925 requires 2 octets per Rbridge." 926 REFERENCE "RFC 7455 section 11" 927 ::= { trillOamMepEntry 33 } 929 trillOamMepDiscontinuityTime OBJECT-TYPE 930 SYNTAX TimeStamp 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "Snapshot of the value of the sysUpTime object at the 935 beginning of the latest period of continuity of the 936 statistical counters associated with this MEP." 937 ::= { trillOamMepEntry 34 } 939 -- ***************************************************************** 940 -- TRILL OAM Tx Measurement Configuration Table 941 -- ***************************************************************** 943 trillOamMepFlowCfgTable OBJECT-TYPE 944 SYNTAX SEQUENCE OF TrillOamMepFlowCfgEntry 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "This table includes configuration objects and operations 949 for the TRILL OAM RFC 7455. 951 Each row in the table represents a Flow configuration 952 Entry for the defined MEP. This table uses four indices. 953 The first three indices are the indices of the Maintenance 954 Domain, MaNet, and MEP tables. The fourth index is the 955 specific flow configuration Entry on the selected MEP. 957 Some writable objects in this table are only applicable in 958 certain cases (as described under each object), and 959 attempts to write values for them in other cases 960 will be ignored." 961 REFERENCE "RFC 7455" 962 ::= { trillOamMep 2 } 964 trillOamMepFlowCfgEntry OBJECT-TYPE 965 SYNTAX TrillOamMepFlowCfgEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "The conceptual row of trillOamMepFlowCfgTable." 971 INDEX { 972 dot1agCfmMdIndex, 973 dot1agCfmMaIndex, 974 dot1agCfmMepIdentifier, 975 trillOamMepFlowCfgIndex 976 } 977 ::= { trillOamMepFlowCfgTable 1 } 979 TrillOamMepFlowCfgEntry ::= SEQUENCE { 980 trillOamMepFlowCfgIndex Unsigned32, 981 trillOamMepFlowCfgFlowEntropy OCTET STRING, 982 trillOamMepFlowCfgDestRName Unsigned32, 983 trillOamMepFlowCfgFlowHC Unsigned32, 984 trillOamMepFlowCfgRowStatus RowStatus 985 } 987 trillOamMepFlowCfgIndex OBJECT-TYPE 988 SYNTAX Unsigned32 (1..65535) 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "An index to the TRILL OAM MEP Flow Configuration table which 993 indicates the specific Flow for the MEP. 995 The index is never reused for other flow sessions on the 996 same MEP while this session is active. The index value 997 keeps increasing until it wraps to 0. This value can also be 998 used in Flow-identifier TLV RFC 7455." 999 REFERENCE "RFC 7455" 1000 ::= { trillOamMepFlowCfgEntry 1 } 1002 trillOamMepFlowCfgFlowEntropy OBJECT-TYPE 1003 SYNTAX OCTET STRING (SIZE (96)) 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "This is 96 byte of Flow Entropy as described in 1008 TRILL OAM RFC 7455." 1009 REFERENCE "RFC 7455 section 3" 1010 ::= { trillOamMepFlowCfgEntry 2 } 1012 trillOamMepFlowCfgDestRName OBJECT-TYPE 1013 SYNTAX Unsigned32 (0..65471) 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "The Target Destination Rbridge NickName Field, as 1018 defined in RFC 6325 section 3.7, to be transmitted." 1020 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1021 ::= { trillOamMepFlowCfgEntry 3 } 1023 trillOamMepFlowCfgFlowHC OBJECT-TYPE 1024 SYNTAX Unsigned32 (1..63) 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "The Time to Live field to be transmitted." 1029 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1030 ::= { trillOamMepFlowCfgEntry 4 } 1032 trillOamMepFlowCfgRowStatus OBJECT-TYPE 1033 SYNTAX RowStatus 1034 MAX-ACCESS read-create 1035 STATUS current 1036 DESCRIPTION 1037 "The status of the row. 1039 The writable columns in a row cannot be changed if the row 1040 is active. All columns MUST have a valid value before a row 1041 can be activated." 1042 ::= { trillOamMepFlowCfgEntry 5 } 1044 -- ****************************************************************** 1045 -- TRILL OAM Path Trace Reply Table 1046 -- ****************************************************************** 1048 trillOamPtrTable OBJECT-TYPE 1049 SYNTAX SEQUENCE OF TrillOamPtrEntry 1050 MAX-ACCESS not-accessible 1051 STATUS current 1052 DESCRIPTION 1053 "This table includes Path Trace Reply objects and 1054 operations for TRILL OAM as described in RFC 7455. 1056 Each row in the table represents a Path Trace Reply Entry for 1057 the defined MEP and Transaction. This table uses four 1058 indices. The first three indices are the indices of the 1059 Maintenance Domain, 1060 MaNet, and MEP tables. The fourth index is the specific 1061 Transaction Identifier on the selected MEP. 1063 Some writable objects in this table are only applicable in 1064 certain cases (as described under each object), 1065 and attempts to 1066 write values for them in other cases will be ignored." 1068 REFERENCE "RFC 7455" 1069 ::= { trillOamMep 3 } 1071 trillOamPtrEntry OBJECT-TYPE 1072 SYNTAX TrillOamPtrEntry 1073 MAX-ACCESS not-accessible 1074 STATUS current 1075 DESCRIPTION 1076 "The conceptual row of trillOamPtrTable." 1077 INDEX { 1078 dot1agCfmMdIndex, 1079 dot1agCfmMaIndex, 1080 dot1agCfmMepIdentifier, 1081 trillOamMepPtrTransactionId 1082 } 1083 ::= { trillOamPtrTable 1 } 1085 TrillOamPtrEntry ::= SEQUENCE { 1086 trillOamMepPtrTransactionId Unsigned32, 1087 trillOamMepPtrHC Unsigned32, 1088 trillOamMepPtrFlag Unsigned32, 1089 trillOamMepPtrErrorCode Unsigned32, 1090 trillOamMepPtrTerminalMep TruthValue, 1091 trillOamMepPtrLastEgressId Unsigned32, 1092 trillOamMepPtrIngress Dot1agCfmIngressActionFieldValue, 1093 trillOamMepPtrIngressMac MacAddress, 1094 trillOamMepPtrIngressPortIdSubtype LldpPortIdSubtype, 1095 trillOamMepPtrIngressPortId LldpPortId, 1096 trillOamMepPtrEgress Dot1agCfmEgressActionFieldValue, 1097 trillOamMepPtrEgressMac MacAddress, 1098 trillOamMepPtrEgressPortIdSubtype LldpPortIdSubtype, 1099 trillOamMepPtrEgressPortId LldpPortId, 1100 trillOamMepPtrChassisIdSubtype LldpChassisIdSubtype, 1101 trillOamMepPtrChassisId LldpChassisId, 1102 trillOamMepPtrOrganizationSpecificTlv OCTET STRING, 1103 trillOamMepPtrNextHopNicknames OCTET STRING 1104 } 1106 trillOamMepPtrTransactionId OBJECT-TYPE 1107 SYNTAX Unsigned32 (0..4294967295) 1108 MAX-ACCESS not-accessible 1109 STATUS current 1110 DESCRIPTION 1111 "Transaction identifier/sequence number returned by a 1112 previous transmit path trace message command, 1113 indicating which PTM's response is going to be returned." 1114 REFERENCE "RFC 7455 section 10" 1115 ::= { trillOamPtrEntry 1 } 1117 trillOamMepPtrHC OBJECT-TYPE 1118 SYNTAX Unsigned32 (1..63) 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Hop Count field value for a returned PTR." 1123 REFERENCE "RFC 7455" 1124 ::= { trillOamPtrEntry 2 } 1126 trillOamMepPtrFlag OBJECT-TYPE 1127 SYNTAX Unsigned32 (0..15) 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "FCOI (TRILL OAM Message TLV) field value for a 1132 returned PTR." 1133 REFERENCE "RFC 7455, 8.4.3" 1134 ::= { trillOamPtrEntry 3 } 1136 trillOamMepPtrErrorCode OBJECT-TYPE 1137 SYNTAX Unsigned32 (0..65535) 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "Return Code and Return Sub code value for a returned PTR." 1142 REFERENCE "RFC 7455, 8.4.3" 1143 ::= { trillOamPtrEntry 4 } 1145 trillOamMepPtrTerminalMep OBJECT-TYPE 1146 SYNTAX TruthValue 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "A boolean value stating whether the forwarded PTM reached a 1151 MEP enclosing its MA, as returned in the Terminal MEP flag of 1152 the Flags field." 1153 REFERENCE "RFC 7455" 1154 ::= { trillOamPtrEntry 5 } 1156 trillOamMepPtrLastEgressId OBJECT-TYPE 1157 SYNTAX Unsigned32 (0..65535) 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "An Integer field holding the Last Egress Identifier returned 1162 in the PTR Upstream Rbridge nickname TLV of the PTR. 1163 The Last Egress Identifier identifies the Upstream Nickname." 1164 REFERENCE "RFC 7455 8.4.1" 1165 ::= { trillOamPtrEntry 6 } 1167 trillOamMepPtrIngress OBJECT-TYPE 1168 SYNTAX Dot1agCfmIngressActionFieldValue 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "The value returned in the Ingress Action Field of the PTR. 1173 The value ingNoTlv(0) indicates that no Reply Ingress TLV was 1174 returned in the PTM." 1175 REFERENCE "RFC 7455 8.4.1" 1176 ::= { trillOamPtrEntry 7 } 1178 trillOamMepPtrIngressMac OBJECT-TYPE 1179 SYNTAX MacAddress 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "MAC address returned in the ingress MAC address field." 1184 REFERENCE "RFC 7455 8.4.1" 1185 ::= { trillOamPtrEntry 8 } 1187 trillOamMepPtrIngressPortIdSubtype OBJECT-TYPE 1188 SYNTAX LldpPortIdSubtype 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "Ingress Port ID. The format of this object is determined by 1193 the value of the trillOamMepPtrIngressPortIdSubtype object." 1194 REFERENCE "RFC 7455 8.4.1" 1195 ::= { trillOamPtrEntry 9 } 1197 trillOamMepPtrIngressPortId OBJECT-TYPE 1198 SYNTAX LldpPortId 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "Ingress Port ID. The format of this object is determined by 1203 the value of the trillOamMepPtrIngressPortId object." 1204 REFERENCE "RFC 7455 8.4.1" 1205 ::= { trillOamPtrEntry 10 } 1207 trillOamMepPtrEgress OBJECT-TYPE 1208 SYNTAX Dot1agCfmEgressActionFieldValue 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION 1212 "The value returned in the Egress Action Field of the PTR. 1214 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1215 returned in the PTM." 1216 REFERENCE "RFC 7455 8.4.1" 1217 ::= { trillOamPtrEntry 11 } 1219 trillOamMepPtrEgressMac OBJECT-TYPE 1220 SYNTAX MacAddress 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "MAC address returned in the egress MAC address field." 1225 REFERENCE "RFC 7455 8.4.1" 1226 ::= { trillOamPtrEntry 12 } 1228 trillOamMepPtrEgressPortIdSubtype OBJECT-TYPE 1229 SYNTAX LldpPortIdSubtype 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "Egress Port ID. The format of this object is determined by 1234 the value of the trillOamMepPtrEgressPortIdSubtype object." 1235 REFERENCE "RFC 7455 8.4.1" 1236 ::= { trillOamPtrEntry 13 } 1238 trillOamMepPtrEgressPortId OBJECT-TYPE 1239 SYNTAX LldpPortId 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "Egress Port ID. The format of this object is determined by 1244 the value of the trillOamMepPtrEgressPortId object." 1245 REFERENCE "RFC 7455 8.4.1" 1246 ::= { trillOamPtrEntry 14 } 1248 trillOamMepPtrChassisIdSubtype OBJECT-TYPE 1249 SYNTAX LldpChassisIdSubtype 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "This object specifies the format of the Chassis ID returned 1254 in the Sender ID TLV of the PTR, if any. This value is 1255 meaningless if the trillOamMepPtrChassisId 1256 has a length of 0." 1257 REFERENCE "RFC 7455 8.4.1" 1258 ::= { trillOamPtrEntry 15 } 1260 trillOamMepPtrChassisId OBJECT-TYPE 1261 SYNTAX LldpChassisId 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "The Chassis ID returned in the Sender ID TLV of the PTR, if 1266 any. The format of this object is determined by the 1267 value of the trillOamMepPtrChassisIdSubtype object." 1268 REFERENCE "RFC 7455 8.4.1" 1269 ::= { trillOamPtrEntry 16 } 1271 trillOamMepPtrOrganizationSpecificTlv OBJECT-TYPE 1272 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "All Organization specific TLVs returned in the PTR, if 1277 any. Includes all octets including and following the TLV 1278 Length field of each TLV, concatenated together." 1279 REFERENCE "RFC 7455 8.4.1" 1280 ::= { trillOamPtrEntry 17 } 1282 trillOamMepPtrNextHopNicknames OBJECT-TYPE 1283 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Next hop Rbridge List TLV returned in the PTR, if 1288 any. Includes all octets including and following the TLV 1289 Length field of each TLV, concatenated together." 1290 REFERENCE "RFC 7455 8.4.1" 1291 ::= { trillOamPtrEntry 18 } 1293 -- ****************************************************************** 1294 -- TRILL OAM Multi Destination Reply Table 1295 -- ****************************************************************** 1297 trillOamMtvrTable OBJECT-TYPE 1298 SYNTAX SEQUENCE OF TrillOamMtvrEntry 1299 MAX-ACCESS not-accessible 1300 STATUS current 1301 DESCRIPTION 1302 "This table includes Multi-destination Reply objects and 1303 operations for the TRILL OAM described in RFC 7455. 1305 Each row in the table represents a Multi-destination Reply 1306 Entry for the defined MEP and Transaction. This table uses 1307 five indices. The first three indices are the indices of the 1308 Maintenance Domain, MaNet, and MEP tables. The fourth index 1309 is the specific Transaction Identifier on the selected MEP. 1310 The fifth index is the receive order of Multi-destination 1311 replies. 1313 Some writable objects in this table are only applicable in 1314 certain cases (as described under each object), and attempts 1315 to write values for them in other cases will be ignored." 1316 REFERENCE "RFC 7455" 1317 ::= { trillOamMep 4 } 1319 trillOamMtvrEntry OBJECT-TYPE 1320 SYNTAX TrillOamMtvrEntry 1321 MAX-ACCESS not-accessible 1322 STATUS current 1323 DESCRIPTION 1324 "The conceptual row of trillOamMtvrTable." 1325 INDEX { 1326 dot1agCfmMdIndex, 1327 dot1agCfmMaIndex, 1328 dot1agCfmMepIdentifier, 1329 trillOamMepPtrTransactionId, 1330 trillOamMepMtvrReceiveOrder 1331 } 1332 ::= { trillOamMtvrTable 1 } 1334 TrillOamMtvrEntry ::= SEQUENCE { 1335 trillOamMepMtvrTransactionId Unsigned32, 1336 trillOamMepMtvrReceiveOrder Unsigned32, 1337 trillOamMepMtvrFlag Unsigned32, 1338 trillOamMepMtvrErrorCode Unsigned32, 1339 trillOamMepMtvrLastEgressId Unsigned32, 1340 trillOamMepMtvrIngress Dot1agCfmIngressActionFieldValue, 1341 trillOamMepMtvrIngressMac MacAddress, 1342 trillOamMepMtvrIngressPortIdSubtype LldpPortIdSubtype, 1343 trillOamMepMtvrIngressPortId LldpPortId, 1344 trillOamMepMtvrEgress Dot1agCfmEgressActionFieldValue, 1345 trillOamMepMtvrEgressMac MacAddress, 1346 trillOamMepMtvrEgressPortIdSubtype LldpPortIdSubtype, 1347 trillOamMepMtvrEgressPortId LldpPortId, 1348 trillOamMepMtvrChassisIdSubtype LldpChassisIdSubtype, 1349 trillOamMepMtvrChassisId LldpChassisId, 1350 trillOamMepMtvrOrganizationSpecificTlv OCTET STRING, 1351 trillOamMepMtvrNextHopNicknames OCTET STRING, 1352 trillOamMepMtvrReceiverAvailability TruthValue, 1353 trillOamMepMtvrReceiverCount TruthValue 1354 } 1356 trillOamMepMtvrTransactionId OBJECT-TYPE 1357 SYNTAX Unsigned32 (0..4294967295) 1358 MAX-ACCESS not-accessible 1359 STATUS current 1360 DESCRIPTION 1361 "Transaction identifier/sequence number returned by a 1362 previous transmit Multi-destination message command 1363 indicating which MTVM's response is going to be returned." 1364 REFERENCE "RFC 7455 section 11" 1365 ::= { trillOamMtvrEntry 1 } 1367 trillOamMepMtvrReceiveOrder OBJECT-TYPE 1368 SYNTAX Unsigned32 (1..4294967295) 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "An index to distinguish among multiple MTVR with same MTVR 1373 Transaction Identifier field value. 1374 trillOamMepMtvrReceiveOrder is assigned sequentially from 1, 1375 in the order that the Multi-destination Tree Initiator 1376 received the MTVRs." 1377 REFERENCE "RFC 7455 section 11" 1378 ::= { trillOamMtvrEntry 2 } 1380 trillOamMepMtvrFlag OBJECT-TYPE 1381 SYNTAX Unsigned32 (0..15) 1382 MAX-ACCESS read-only 1383 STATUS current 1384 DESCRIPTION 1385 "FCOI (TRILL OAM Message TLV) field value for a 1386 returned MTVR." 1387 REFERENCE "RFC 7455, 8.4.2" 1388 ::= { trillOamMtvrEntry 3 } 1390 trillOamMepMtvrErrorCode OBJECT-TYPE 1391 SYNTAX Unsigned32 (0..65535) 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "Return Code and Return Sub code value for a returned MTVR." 1396 REFERENCE "RFC 7455, 8.4.2" 1397 ::= { trillOamMtvrEntry 4 } 1399 trillOamMepMtvrLastEgressId OBJECT-TYPE 1400 SYNTAX Unsigned32 (0..65535) 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "An Integer field holding the Last Egress Identifier returned 1405 in the MTVR Upstream Rbridge Nickname TLV of the MTVR. The 1406 Last Egress Identifier identifies the Upstream Nickname." 1407 REFERENCE "RFC 7455 8.4.1" 1408 ::= { trillOamMtvrEntry 5 } 1410 trillOamMepMtvrIngress OBJECT-TYPE 1411 SYNTAX Dot1agCfmIngressActionFieldValue 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The value returned in the Ingress Action Field of 1416 the MTVR. The value ingNoTlv(0) indicates that no 1417 Reply Ingress TLV was returned in the MTVM." 1418 REFERENCE "RFC 7455 11.2.3" 1419 ::= { trillOamMtvrEntry 6 } 1421 trillOamMepMtvrIngressMac OBJECT-TYPE 1422 SYNTAX MacAddress 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "MAC address returned in the ingress MAC address field." 1427 REFERENCE "RFC 7455 8.4.1" 1428 ::= { trillOamMtvrEntry 7 } 1430 trillOamMepMtvrIngressPortIdSubtype OBJECT-TYPE 1431 SYNTAX LldpPortIdSubtype 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "Ingress Port ID. The format of this object is 1436 determined by the value of the 1437 trillOamMepMtvrIngressPortIdSubtype object." 1438 REFERENCE "RFC 7455 8.4.1" 1439 ::= { trillOamMtvrEntry 8 } 1441 trillOamMepMtvrIngressPortId OBJECT-TYPE 1442 SYNTAX LldpPortId 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "Ingress Port ID. The format of this object is determined by 1447 the value of the trillOamMepMtvrIngressPortId object." 1448 REFERENCE "RFC 7455 8.4.1" 1449 ::= { trillOamMtvrEntry 9 } 1451 trillOamMepMtvrEgress OBJECT-TYPE 1452 SYNTAX Dot1agCfmEgressActionFieldValue 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "The value returned in the Egress Action Field of the MTVR. 1457 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1458 returned in the MTVR." 1459 REFERENCE "RFC 7455 8.4.1" 1460 ::= { trillOamMtvrEntry 10 } 1462 trillOamMepMtvrEgressMac OBJECT-TYPE 1463 SYNTAX MacAddress 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "MAC address returned in the egress MAC address field." 1468 REFERENCE "RFC 7455 8.4.1" 1469 ::= { trillOamMtvrEntry 11 } 1471 trillOamMepMtvrEgressPortIdSubtype OBJECT-TYPE 1472 SYNTAX LldpPortIdSubtype 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "Egress Port ID. The format of this object is determined by 1477 the value of the trillOamMepMtvrEgressPortIdSubtype object." 1478 REFERENCE "RFC 7455 8.4.1" 1479 ::= { trillOamMtvrEntry 12 } 1481 trillOamMepMtvrEgressPortId OBJECT-TYPE 1482 SYNTAX LldpPortId 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "Egress Port ID. The format of this object is determined by 1487 the value of the trillOamMepMtvrEgressPortId object." 1488 REFERENCE "RFC 7455 8.4.1" 1489 ::= { trillOamMtvrEntry 13 } 1491 trillOamMepMtvrChassisIdSubtype OBJECT-TYPE 1492 SYNTAX LldpChassisIdSubtype 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "This object specifies the format of the Chassis ID returned 1497 in the Sender ID TLV of the MTVR, if any. This value is 1498 meaningless if the trillOamMepMtvrChassisId has a 1499 length of 0." 1500 REFERENCE "RFC 7455 8.4.1" 1501 ::= { trillOamMtvrEntry 14 } 1503 trillOamMepMtvrChassisId OBJECT-TYPE 1504 SYNTAX LldpChassisId 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "The Chassis ID returned in the Sender ID TLV of the MTVR, if 1509 any. The format of this object is determined by the 1510 value of the trillOamMepMtvrChassisIdSubtype object." 1511 REFERENCE "RFC 7455 8.4.1" 1512 ::= { trillOamMtvrEntry 15 } 1514 trillOamMepMtvrOrganizationSpecificTlv OBJECT-TYPE 1515 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "All Organization specific TLVs returned in the MTVR, if 1520 any. Includes all octets including and following the TLV 1521 Length field of each TLV, concatenated together." 1522 REFERENCE "RFC 7455 8.4.1" 1523 ::= { trillOamMtvrEntry 16 } 1525 trillOamMepMtvrNextHopNicknames OBJECT-TYPE 1526 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "Next hop Rbridge List TLV returned in the PTR, if 1531 any. Includes all octets including and following the TLV 1532 Length field of each TLV, concatenated together." 1533 REFERENCE "RFC 7455 8.4.3" 1534 ::= { trillOamMtvrEntry 17 } 1536 trillOamMepMtvrReceiverAvailability OBJECT-TYPE 1537 SYNTAX TruthValue 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "True value indicates that MTVR response contained 1542 Multicast receiver availability TLV." 1543 REFERENCE "RFC 7455 8.4.10" 1544 ::= { trillOamMtvrEntry 18 } 1546 trillOamMepMtvrReceiverCount OBJECT-TYPE 1547 SYNTAX TruthValue 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "Indicates the number of Multicast receivers available on 1552 responding RBridge on the VLAN specified by the 1553 diagnostic VLAN." 1554 REFERENCE "RFC 7455 8.4.10" 1555 ::= { trillOamMtvrEntry 19 } 1557 -- ***************************************************************** 1558 -- TRILL OAM MEP Database Table 1559 -- ***************************************************************** 1561 trillOamMepDbTable OBJECT-TYPE 1562 SYNTAX SEQUENCE OF TrillOamMepDbEntry 1563 MAX-ACCESS not-accessible 1564 STATUS current 1565 DESCRIPTION 1566 "This table is an extension of the dot1agCfmMepDbTable 1567 and rows are automatically added to or deleted from 1568 this table based upon row creation and destruction of the 1569 dot1agCfmMepDbTable." 1570 REFERENCE 1571 "RFC 7455" 1572 ::= { trillOamMep 5 } 1574 trillOamMepDbEntry OBJECT-TYPE 1575 SYNTAX TrillOamMepDbEntry 1576 MAX-ACCESS not-accessible 1577 STATUS current 1578 DESCRIPTION 1579 "The conceptual row of trillOamMepDbTable." 1580 AUGMENTS { 1581 dot1agCfmMepDbEntry 1582 } 1583 ::= { trillOamMepDbTable 1 } 1585 TrillOamMepDbEntry ::= SEQUENCE { 1586 trillOamMepDbFlowIndex Unsigned32, 1587 trillOamMepDbFlowEntropy OCTET STRING, 1588 trillOamMepDbFlowState Dot1agCfmRemoteMepState, 1589 trillOamMepDbFlowFailedOkTime TimeStamp, 1590 trillOamMepDbRbridgeName Unsigned32, 1591 trillOamMepDbLastGoodSeqNum Counter32 1592 } 1594 trillOamMepDbFlowIndex OBJECT-TYPE 1595 SYNTAX Unsigned32 (1..65535) 1596 MAX-ACCESS read-only 1597 STATUS current 1598 DESCRIPTION 1599 "This object identifies the Flow. If Flow Identifier TLV 1600 is received than index received can also be used." 1601 REFERENCE "RFC 7455" 1602 ::= {trillOamMepDbEntry 1 } 1604 trillOamMepDbFlowEntropy OBJECT-TYPE 1605 SYNTAX OCTET STRING (SIZE (96)) 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "96 byte Flow Entropy." 1610 REFERENCE "RFC 7455 section 3." 1611 ::= {trillOamMepDbEntry 2 } 1613 trillOamMepDbFlowState OBJECT-TYPE 1614 SYNTAX Dot1agCfmRemoteMepState 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "The operational state of the remote MEP (flow based) 1619 IFF State machines. State Machine is running now per 1620 flow." 1621 REFERENCE "RFC 7455" 1622 ::= {trillOamMepDbEntry 3 } 1624 trillOamMepDbFlowFailedOkTime OBJECT-TYPE 1625 SYNTAX TimeStamp 1626 MAX-ACCESS read-only 1627 STATUS current 1628 DESCRIPTION 1629 "The Time (sysUpTime) at which the Remote MEP Flow state 1630 machine last entered either the RMEP_FAILED or RMEP_OK 1631 state." 1632 REFERENCE "RFC 7455" 1633 ::= {trillOamMepDbEntry 4 } 1635 trillOamMepDbRbridgeName OBJECT-TYPE 1636 SYNTAX Unsigned32(0..65471) 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "Remote MEP Rbridge Nickname." 1641 REFERENCE "RFC 7455 RFC 6325 section 3" 1642 ::= {trillOamMepDbEntry 5 } 1644 trillOamMepDbLastGoodSeqNum OBJECT-TYPE 1645 SYNTAX Counter32 1646 MAX-ACCESS read-only 1647 STATUS current 1648 DESCRIPTION 1649 "Last Sequence Number received." 1650 REFERENCE "RFC 7455 13.1" 1651 ::= {trillOamMepDbEntry 6} 1653 -- ****************************************************************** 1654 -- TRILL OAM MIB NOTIFICATIONS (TRAPS) 1655 -- This notification is sent to management entity whenever a 1656 -- MEP loses/restores 1657 -- contact with its peer Flow Meps 1658 -- ****************************************************************** 1659 trillOamFaultAlarm NOTIFICATION-TYPE 1660 OBJECTS { trillOamMepDbFlowState } 1661 STATUS current 1662 DESCRIPTION 1663 "A MEP Flow has a persistent defect condition. 1664 A notification (fault alarm) is sent to the management 1665 entity with the OID of the Flow that has detected the fault. 1667 The management entity receiving the notification can identify 1668 the system from the network source address of the 1669 notification, and can identify the Flow reporting the defect 1670 by the indices in the OID of the trillOamMepFlowIndex, and 1671 trillOamFlowDefect variable in the notification: 1673 dot1agCfmMdIndex - Also the index of the MEP's 1674 Maintenance Domain table entry 1675 (dot1agCfmMdTable). 1676 dot1agCfmMaIndex - Also an index (with the MD table index) 1677 of the MEP's Maintenance Association 1678 network table entry 1679 (dot1agCfmMaNetTable), and (with the MD 1680 table index and component ID) of the 1681 MEP's MA component table entry 1682 (dot1agCfmMaCompTable). 1683 dot1agCfmMepIdentifier - MEP Identifier and final index 1684 into the MEP table (dot1agCfmMepTable). 1685 trillOamMepFlowCfgIndex - Index identifies 1686 indicates the specific Flow for 1687 the MEP" 1688 REFERENCE "RFC 7455" 1689 ::= { trillOamNotifications 1 } 1691 -- ****************************************************************** 1692 -- TRILL OAM MIB Module - Conformance Information 1693 -- ****************************************************************** 1695 trillOamMibCompliances OBJECT IDENTIFIER 1696 ::= { trillOamMibConformance 1 } 1698 trillOamMibGroups OBJECT IDENTIFIER 1699 ::= { trillOamMibConformance 2 } 1701 -- ****************************************************************** 1702 -- TRILL OAM MIB Units of conformance 1703 -- ****************************************************************** 1705 trillOamMepMandatoryGroup OBJECT-GROUP 1706 OBJECTS { 1707 trillOamMepRName, 1708 trillOamMepNextPtmTId, 1709 trillOamMepNextMtvmTId, 1710 trillOamMepPtrIn, 1711 trillOamMepPtrInOutofOrder, 1712 trillOamMepPtrOut, 1713 trillOamMepMtvrIn, 1714 trillOamMepMtvrInOutofOrder, 1715 trillOamMepMtvrOut, 1716 trillOamMepTxLbmDestRName, 1717 trillOamMepTxLbmHC, 1718 trillOamMepTxLbmReplyModeOob, 1719 trillOamMepTransmitLbmReplyIp, 1720 trillOamMepTxLbmFlowEntropy, 1721 trillOamMepTxPtmDestRName, 1722 trillOamMepTxPtmHC, 1723 trillOamMepTxPtmReplyModeOob, 1724 trillOamMepTransmitPtmReplyIp, 1725 trillOamMepTxPtmFlowEntropy, 1726 trillOamMepTxPtmStatus, 1727 trillOamMepTxPtmResultOK, 1728 trillOamMepTxPtmMessages, 1729 trillOamMepTxPtmSeqNumber, 1730 trillOamMepTxMtvmTree, 1731 trillOamMepTxMtvmHC, 1732 trillOamMepTxMtvmReplyModeOob, 1733 trillOamMepTransmitMtvmReplyIp, 1734 trillOamMepTxMtvmFlowEntropy, 1735 trillOamMepTxMtvmStatus, 1736 trillOamMepTxMtvmResultOK, 1737 trillOamMepTxMtvmMessages, 1738 trillOamMepTxMtvmSeqNumber, 1739 trillOamMepTxMtvmScopeList, 1740 trillOamMepDiscontinuityTime 1741 } 1742 STATUS current 1743 DESCRIPTION 1744 "Mandatory objects for the TRILL OAM MEP group." 1745 ::= { trillOamMibGroups 1 } 1747 trillOamMepFlowCfgTableGroup OBJECT-GROUP 1748 OBJECTS { 1749 trillOamMepFlowCfgFlowEntropy, 1750 trillOamMepFlowCfgDestRName, 1751 trillOamMepFlowCfgFlowHC, 1752 trillOamMepFlowCfgRowStatus 1753 } 1754 STATUS current 1755 DESCRIPTION 1756 "TRILL OAM MEP Flow Configuration objects group." 1757 ::= { trillOamMibGroups 2 } 1759 trillOamPtrTableGroup OBJECT-GROUP 1760 OBJECTS { 1761 trillOamMepPtrHC, 1762 trillOamMepPtrFlag, 1763 trillOamMepPtrErrorCode, 1764 trillOamMepPtrTerminalMep, 1765 trillOamMepPtrLastEgressId, 1766 trillOamMepPtrIngress, 1767 trillOamMepPtrIngressMac, 1768 trillOamMepPtrIngressPortIdSubtype, 1769 trillOamMepPtrIngressPortId, 1770 trillOamMepPtrEgress, 1771 trillOamMepPtrEgressMac, 1772 trillOamMepPtrEgressPortIdSubtype, 1773 trillOamMepPtrEgressPortId, 1774 trillOamMepPtrChassisIdSubtype, 1775 trillOamMepPtrChassisId, 1776 trillOamMepPtrOrganizationSpecificTlv, 1777 trillOamMepPtrNextHopNicknames 1778 } 1779 STATUS current 1780 DESCRIPTION 1781 "TRILL OAM MEP PTR objects group." 1782 ::= { trillOamMibGroups 3 } 1784 trillOamMtvrTableGroup OBJECT-GROUP 1785 OBJECTS { 1786 trillOamMepMtvrFlag, 1787 trillOamMepMtvrErrorCode, 1788 trillOamMepMtvrLastEgressId, 1789 trillOamMepMtvrIngress, 1790 trillOamMepMtvrIngressMac, 1791 trillOamMepMtvrIngressPortIdSubtype, 1792 trillOamMepMtvrIngressPortId, 1793 trillOamMepMtvrEgress, 1794 trillOamMepMtvrEgressMac, 1795 trillOamMepMtvrEgressPortIdSubtype, 1796 trillOamMepMtvrEgressPortId, 1797 trillOamMepMtvrChassisIdSubtype, 1798 trillOamMepMtvrChassisId, 1799 trillOamMepMtvrOrganizationSpecificTlv, 1800 trillOamMepMtvrNextHopNicknames, 1801 trillOamMepMtvrReceiverAvailability, 1802 trillOamMepMtvrReceiverCount 1803 } 1804 STATUS current 1805 DESCRIPTION 1806 "TRILL OAM MEP MTVR objects group." 1807 ::= { trillOamMibGroups 4 } 1809 trillOamMepDbGroup OBJECT-GROUP 1810 OBJECTS { 1811 trillOamMepDbFlowIndex, 1812 trillOamMepDbFlowEntropy, 1813 trillOamMepDbFlowState, 1814 trillOamMepDbFlowFailedOkTime, 1815 trillOamMepDbRbridgeName, 1816 trillOamMepDbLastGoodSeqNum 1817 } 1819 STATUS current 1820 DESCRIPTION 1821 "TRILL OAM MEP DB objects group." 1822 ::= { trillOamMibGroups 5 } 1824 trillOamNotificationGroup NOTIFICATION-GROUP 1825 NOTIFICATIONS { trillOamFaultAlarm } 1826 STATUS current 1827 DESCRIPTION 1828 "A collection of objects describing notifications(traps)." 1829 ::= { trillOamMibGroups 6 } 1831 -- ****************************************************************** 1832 -- TRILL OAM MIB Module Compliance statements 1833 -- ****************************************************************** 1835 trillOamMibCompliance MODULE-COMPLIANCE 1836 STATUS current 1837 DESCRIPTION 1838 "The compliance statement for the TRILL OAM MIB." 1839 MODULE -- this module 1840 MANDATORY-GROUPS { 1841 trillOamMepMandatoryGroup, 1842 trillOamMepFlowCfgTableGroup, 1843 trillOamPtrTableGroup, 1844 trillOamMtvrTableGroup, 1845 trillOamMepDbGroup, 1846 trillOamNotificationGroup 1847 } 1848 ::= { trillOamMibCompliances 1 } 1850 -- Compliance requirement for read-only implementation. 1852 trillOamMibReadOnlyCompliance MODULE-COMPLIANCE 1853 STATUS current 1854 DESCRIPTION 1855 "Compliance requirement for implementation that only 1856 provide read-only support for TRILL-OAM-MIB. 1857 Such devices can be monitored but cannot be configured 1858 using this MIB module." 1859 MODULE -- this module 1860 MANDATORY-GROUPS { 1861 trillOamMepMandatoryGroup, 1862 trillOamMepFlowCfgTableGroup, 1863 trillOamPtrTableGroup, 1864 trillOamMtvrTableGroup, 1865 trillOamMepDbGroup, 1866 trillOamNotificationGroup 1867 } 1868 -- trillOamMepTable 1870 OBJECT trillOamMepTxLbmDestRName 1871 MIN-ACCESS read-only 1872 DESCRIPTION 1873 "Write access is not required." 1875 OBJECT trillOamMepTxLbmHC 1876 MIN-ACCESS read-only 1877 DESCRIPTION 1878 "Write access is not required." 1880 OBJECT trillOamMepTxLbmReplyModeOob 1881 MIN-ACCESS read-only 1882 DESCRIPTION 1883 "Write access is not required." 1885 OBJECT trillOamMepTransmitLbmReplyIp 1886 MIN-ACCESS read-only 1887 DESCRIPTION 1888 "Write access is not required." 1890 OBJECT trillOamMepTxLbmFlowEntropy 1891 MIN-ACCESS read-only 1892 DESCRIPTION 1893 "Write access is not required." 1895 OBJECT trillOamMepTxPtmDestRName 1896 MIN-ACCESS read-only 1897 DESCRIPTION 1898 "Write access is not required." 1900 OBJECT trillOamMepTxPtmHC 1901 MIN-ACCESS read-only 1902 DESCRIPTION 1903 "Write access is not required." 1905 OBJECT trillOamMepTxPtmReplyModeOob 1906 MIN-ACCESS read-only 1907 DESCRIPTION 1908 "Write access is not required." 1910 OBJECT trillOamMepTransmitPtmReplyIp 1911 MIN-ACCESS read-only 1912 DESCRIPTION 1913 "Write access is not required." 1915 OBJECT trillOamMepTxPtmFlowEntropy 1916 MIN-ACCESS read-only 1917 DESCRIPTION 1918 "Write access is not required." 1920 OBJECT trillOamMepTxPtmStatus 1921 MIN-ACCESS read-only 1922 DESCRIPTION 1923 "Write access is not required." 1925 OBJECT trillOamMepTxPtmResultOK 1926 MIN-ACCESS read-only 1927 DESCRIPTION 1928 "Write access is not required." 1930 OBJECT trillOamMepTxPtmMessages 1931 MIN-ACCESS read-only 1932 DESCRIPTION 1933 "Write access is not required." 1935 OBJECT trillOamMepTxPtmSeqNumber 1936 MIN-ACCESS read-only 1937 DESCRIPTION 1938 "Write access is not required." 1940 OBJECT trillOamMepTxMtvmTree 1941 MIN-ACCESS read-only 1942 DESCRIPTION 1943 "Write access is not required." 1945 OBJECT trillOamMepTxMtvmHC 1946 MIN-ACCESS read-only 1947 DESCRIPTION 1948 "Write access is not required." 1950 OBJECT trillOamMepTxMtvmReplyModeOob 1951 MIN-ACCESS read-only 1952 DESCRIPTION 1953 "Write access is not required." 1955 OBJECT trillOamMepTransmitMtvmReplyIp 1956 MIN-ACCESS read-only 1957 DESCRIPTION 1958 "Write access is not required." 1960 OBJECT trillOamMepTxMtvmFlowEntropy 1961 MIN-ACCESS read-only 1962 DESCRIPTION 1963 "Write access is not required." 1965 OBJECT trillOamMepTxMtvmStatus 1966 MIN-ACCESS read-only 1967 DESCRIPTION 1968 "Write access is not required." 1970 OBJECT trillOamMepTxMtvmResultOK 1971 MIN-ACCESS read-only 1972 DESCRIPTION 1973 "Write access is not required." 1975 OBJECT trillOamMepTxMtvmMessages 1976 MIN-ACCESS read-only 1977 DESCRIPTION 1978 "Write access is not required." 1980 OBJECT trillOamMepTxMtvmSeqNumber 1981 MIN-ACCESS read-only 1982 DESCRIPTION 1983 "Write access is not required." 1985 OBJECT trillOamMepTxMtvmScopeList 1986 MIN-ACCESS read-only 1987 DESCRIPTION 1988 "Write access is not required." 1990 -- trillOamMepFlowCfgTable 1992 OBJECT trillOamMepFlowCfgFlowEntropy 1993 MIN-ACCESS read-only 1994 DESCRIPTION 1995 "Write access is not required." 1997 OBJECT trillOamMepFlowCfgDestRName 1998 MIN-ACCESS read-only 1999 DESCRIPTION 2000 "Write access is not required." 2002 OBJECT trillOamMepFlowCfgFlowHC 2003 MIN-ACCESS read-only 2004 DESCRIPTION 2005 "Write access is not required." 2007 OBJECT trillOamMepFlowCfgRowStatus 2008 MIN-ACCESS read-only 2009 DESCRIPTION 2010 "Write access is not required." 2012 ::= { trillOamMibCompliances 2 } 2014 END 2016 8. Security Considerations 2018 This MIB relates to a system that will provide network connectivity 2019 and packet forwarding services. As such, improper manipulation of the 2020 objects represented by this MIB may result in denial of service to a 2021 large number of end-users. 2023 There are number of management objects defined in this MIB module 2024 with a MAX-ACCESS clause of read-create. Such objects may be 2025 considered sensitive or vulnerable in some network environments. 2026 Support for SET operations in a non-secure environment without proper 2027 protection can have negative effect on sensitivity/vulnerability: 2029 The following table and objects in the TRILL-OAM-MIB can be 2030 manipulated to interfere with the operation of RBridges by causing 2031 cpu use spikes: 2033 o trillOamMepTransmitLbmReplyIp allows the reply from a Loopback 2034 message to be transmitted to an IP address in the TLV thus allowing 2035 replies to be sent to any system to cause Denial of Service. 2037 o trillOamMepTransmitPtmReplyIp allows the reply from a Path Trace 2038 message to be transmitted to an IP address in the TLV and thus 2039 allowing replies to be sent to any system to cause Denial of Service. 2041 o trillOamMepTxPtmMessages allows the generation of PTM Messages and 2042 can be used to generate lots of cpu driven traffic. 2044 o trillOamMepTransmitMtvmReplyIp allows from reply from an MTV 2045 message to be transmitted to an IP address in the TLV and thus 2046 allowing replies to be sent to any system to cause Denial of 2047 Service. 2049 o trillOamMepTxMtvmMessages allows the generation of MTV Messages and 2050 can be used to generate lots of cpu driven traffic. 2052 The following objects in the TRILL-OAM-MIB are read-create and can be 2053 manipulated to interfere with the OAM operations of RBridges. If the 2054 number of OAM frames generated in the network is high, this can cause 2055 a cpu spike on destination Rbridges if Control plane policing is not 2056 properly implemented or configured on destination Rbridges. 2058 o trillOamMepTxLbmHC is used to set the Maximum Hop count for the LBM 2059 message. As OAM frame don't leak out of the TRILL network, it has no 2060 side effects. 2062 o trillOamMepTxLbmReplyModeOob is used to indicate whether the reply 2063 is in-band or out-of-band. This object's vulnerability is covered as 2064 part of trillOamMepTransmitLbmReplyIp. 2066 o trillOamMepTxLbmFlowEntropy is used to indicate the customer flow 2067 and find the exact path in the network. The creation of valid flows 2068 is its intended purpose. If invalid flows are created on vulnerable 2069 system they will be dropped in forwarding. 2071 o trillOamMepTxLbmDestRName is read-create but it's not vulnerable as 2072 invalid-name routes won't be present and will be rejected by the OAM 2073 application as part of normal processing. 2075 o trillOamMepTxPtmHC is used to set the Maximum Hop count for the PTM 2076 message. As OAM frame don't leak out of the TRILL network, it has no 2077 side effect. 2079 o trillOamMepTxPtmReplyModeOob is used to indicate whether the reply 2080 is in-band or out-of-band. This object's vulnerability is covered as 2081 part of trillOamMepTransmitPtmReplyIp. 2083 o trillOamMepTxPtmFlowEntropy is used to indicate the customer flow 2084 and find the exact path in the network. Creation of valid flows is 2085 its intended purpose. If invalid flows are created on vulnerable 2086 systems they will be dropped in forwarding. 2088 o trillOamMepTxPtmDestRName is read-create but it's not vulnerable as 2089 invalid-name routes won't be present and will be rejected by the OAM 2090 application as part of normal processing. 2092 o trillOamMepTxPtmStatus is required for normal PTM operation. 2094 o trillOamMepTxPtmResultOK is required for normal PTM operation. 2096 o trillOamMepTxPtmSeqNumber is required for normal PTM operation. 2098 o trillOamMepTxPtmMessages is required for normal PTM operation. 2100 o trillOamMepTxMtvmTree is required for normal MTVM operation. 2102 o trillOamMepTxMtvmHC is used to set the Maximum Hop count for the 2103 MTVM message. As OAM frame don't leak out of the TRILL network, it 2104 has no side effect 2106 o trillOamMepTxMtvmReplyModeOob is used to indicate whether the reply 2107 is in-band or out-of-band. This object's vulnerability is covered as 2108 part of trillOamMepTransmitMtmReplyIp 2110 o trillOamMepTxMtvmFlowEntropy is used to indicate the customer flow 2111 and find the exact path in the network. Creation of valid flows is 2112 its intended purpose. If invalid flows are created on vulnerable 2113 systems they will be dropped in forwarding. 2115 o trillOamMepTxMtvmStatus is required for normal MTVM operation. 2117 o trillOamMepTxMtvmResultOK, trillOamMepTxMtvmMessages, 2118 trillOamMepTxMtvmSeqNumber, and trillOamMepTxMtvmScopeList is 2119 required for normal MTVM operation. 2121 trillOamMepTransmitLbmReplyIp, trillOamMepTransmitPtmReplyIp, and 2122 trillOamMepTransmitMtvmReplyIp allow setting of the IP address to 2123 which reports are sent and thus it can be used for Denial of Service 2124 for that IP. 2126 Some of the readable objects in this MIB module (i.e., objects with a 2127 MAX-ACCESS other than not-accessible) may be considered sensitive or 2128 vulnerable in some network environments. It is thus important to 2129 control GET and/or NOTIFY access to these objects and possibly to 2130 encrypt the values of these objects when sending them over the 2131 network via SNMP. For example, Path Trace messages expose the unicast 2132 topology of the network and Multi-destination Tree Verification 2133 Messages expose the multicast tree topology of the network. This 2134 information should not be available to all users of the network. 2136 SNMP versions prior to SNMPv3 did not include adequate security. Even 2137 if the network itself is secure (for example by using IPsec), there 2138 is no control as to who on the secure network is allowed to access 2139 and GET/SET (read/change/create/delete) the objects in this MIB 2140 module. 2142 Implementation should provide the security features described by 2143 SNMPv3 framework (see [RFC3410]), and implementations claiming 2144 compliance to the SNMPv3 standard MUST include full support for 2145 authentication and privacy via the User-based Security Model 2146 (USM)[RFC3414] with the AES cipher algorithm [RFC3826]. 2147 Implementations MAY also provide support for the Transport Security 2148 Model (TSM) [RFC5591] in combination with a secure transport such as 2149 SSH [RFC5592] or TLS/DTLS [RFC6353]. 2151 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2152 RECOMMENDED. Instead, deployment of SNMPv3 with cryptographic 2153 security enabled is RECOMMENDED. It is then a customer/operator 2154 responsibility to ensure that the SNMP entity giving access to an 2155 instance of this MIB module is properly configured to give only those 2156 principals (users) that have legitimate rights to indeed GET or SET 2157 (change/create/delete) access to the objects. 2159 9. IANA Considerations 2161 The MIB module in this document uses the following IANA-assigned 2162 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2164 Descriptor OBJECT IDENTIFIER value 2165 ---------------------------------------- 2166 trillOamMIB { mib-2 xxx } 2167 Editor's Note (to be removed prior to publication): the IANA is 2168 requested to assign a value for "xxx" under the 'mib-2' subtree and 2169 to record the assignment in the SMI Numbers registry. When the 2170 assignment has been made, the RFC Editor is asked to replace "XXX" 2171 (here and in the MIB module) with the assigned value and to remove 2172 this note. 2174 10. Contributors 2176 We wish to thank members of the IETF TRILL WG and the MIB-Doctor for 2177 their comments and suggestions. Detailed comments were provided by 2178 Sam Aldrin, Donald Eastlake, Tom Taylor, and Harrie Hazewinkel. 2180 11. References 2181 11.1. Normative References 2183 [RFC2119] Bradner, S., "Key words for use in RFCs to 2184 Indicate Requirement Levels", BCP 14, RFC 2119, March 2185 1997. 2187 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2188 Schoenwaelder, Ed., "Structure of Management Information 2189 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2191 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2192 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2193 58, RFC 2579, April 1999. 2195 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2196 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2197 STD 58, RFC 2580, April 1999. 2199 [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, 2200 S., and A. Ghanwani, "Routing Bridges (RBridges): Base 2201 Protocol Specification", RFC 6325, July 2011. 2203 [RFC7172] Eastlake 3rd, D., Zhang, M., Agarwal, P., 2204 Perlman, R., and D. Dutt, "Transparent Interconnection of 2205 Lots of Links (TRILL): Fine-Grained Labeling", RFC 7172, 2206 May 2014. 2208 [RFC7455] Senevirathne, T., et.al., "Transparent 2209 Interconnection of Lots of Links (TRILL): Fault 2210 Management", March 2015. 2212 [LLDP-MIB] IEEE, 2213 http://www.ieee802.org/1/files/public/MIBs/LLDP-MIB- 2214 200505060000Z.txt 2216 [802.1Q] IEEE, "IEEE Standard for Local and metropolitan 2217 area networks - Media Access Control (MAC) Bridges and 2218 Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 2219 31 August 2011. 2221 11.2. Informative References 2223 [RFC3410] Case, J., Mundy, R., Partain, D., and B.Stewart, 2224 "Introduction and Applicability Statements for Internet- 2225 Standard Management Framework", RFC 3410, December 2002. 2227 [RFC6905] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., 2228 and R. Watve, "Requirements for Operations, 2229 Administration, and Maintenance (OAM) in Transparent 2230 Interconnection of Lots of Links (TRILL)", RFC 6905, March 2231 2013. 2233 [RFC7174] Salam, S., Senevirathne, T., Aldrin, S., and D. 2234 Eastlake 3rd, "Transparent Interconnection of Lots of 2235 Links (TRILL) Operations, Administration, and Maintenance 2236 (OAM) Framework", RFC 7174, May 2014. 2238 Authors' Addresses 2240 Deepak Kumar 2241 Cisco 2242 510 McCarthy Blvd, 2243 Milpitas, CA 95035, USA 2244 Phone : +1 408-853-9760 2245 Email: dekumar@cisco.com 2247 Samer Salam 2248 Cisco 2249 595 Burrard St. Suite 2123 2250 Vancouver, BC V7X 1J1, Canada 2251 Email: ssalam@cisco.com 2253 Tissa Senevirathne 2254 Consultant 2255 Email: tsenevir@gmail.com