idnits 2.17.1 draft-ietf-trill-oam-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 727 has weird spacing: '...d. The maxim...' == Line 728 has weird spacing: '...address is 16...' == Line 807 has weird spacing: '...treated as si...' == Line 963 has weird spacing: '...try for the d...' == Line 964 has weird spacing: '...e first three...' -- The document date (August 23, 2015) is 3168 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 383, but not defined == Missing Reference: 'RFC3414' is mentioned on line 2099, but not defined == Missing Reference: 'RFC3826' is mentioned on line 2099, but not defined == Missing Reference: 'RFC5591' is mentioned on line 2101, but not defined == Missing Reference: 'RFC5592' is mentioned on line 2102, but not defined == Missing Reference: 'RFC6353' is mentioned on line 2102, but not defined == Unused Reference: 'LLDP-MIB' is defined on line 2160, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MIB' Summary: 0 errors (**), 0 flaws (~~), 13 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 January 2016 August 23, 2015 9 TRILL OAM MIB 10 draft-ietf-trill-oam-mib-08.txt 12 Status of this Memo 14 This Internet-Draft is submitted in full conformance with the 15 provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on February 24, 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 Abstract 52 This document specifies the Management Information Base (MIB) for the 53 IETF TRILL (Transparent Interconnection of Lots of Links) OAM 54 (Operations, Administration, and Maintenance) objects. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 5. Structure of the MIB module . . . . . . . . . . . . . . . . . . 4 63 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . . 4 64 5.2. TRILL-OAM-MIB relationship to IEEE8021-TC-MIB . . . . . . 4 65 5.3. TRILL OAM MIB Tree . . . . . . . . . . . . . . . . . . . . 5 66 5.3.1. TRILL OAM MIB Notifications . . . . . . . . . . . . . 5 67 5.3.2. TRILL OAM MIB Per MEP Objects . . . . . . . . . . . . . 5 68 5.3.2.1. trillOamMepTable Objects . . . . . . . . . . . . . 5 69 5.3.2.2. trillOamMepFlowCfgTable Objects . . . . . . . . . . 6 70 5.3.2.3. trillOamPtrTable Objects . . . . . . . . . . . . . 6 71 5.3.2.4. trillOamMtvrTable Objects . . . . . . . . . . . . . 6 72 5.3.2.5. trillOamMepDbTable Objects . . . . . . . . . . . . 6 73 6. Relationship to other MIB module . . . . . . . . . . . . . . . 7 74 6.1. Relationship to IEEE8021-CFM-MIB . . . . . . . . . . . . . 7 75 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 76 7. Definition of the TRILL OAM MIB module . . . . . . . . . . . . 8 77 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 43 78 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 45 79 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 45 80 10.1. Normative References . . . . . . . . . . . . . . . . . . 45 81 10.2. Informative References . . . . . . . . . . . . . . . . . 46 82 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47 83 12. Copyright and Disclaimer . . . . . . . . . . . . . . . . . . . 47 85 1. Introduction 87 Overall, TRILL OAM is intended to meet the requirements given in 88 [RFC6905]. The general framework for TRILL OAM is specified in 89 [RFC7174]. The details of the Fault Management (FM) solution, 90 conforming to that framework, are presented in RFC 7455. The solution 91 leverages the message format defined in Ethernet Connectivity Fault 92 Management (CFM) [802.1Q] as the basis for the TRILL OAM message 93 channel. 95 This document uses the CFM MIB modules defined in [802.1Q] as the 96 basis for TRILL OAM MIB, and augments the existing tables to add new 97 TRILL managed objects required by TRILL. This document further 98 specifies a new table with associated managed objects for TRILL OAM 99 specific capabilities. 101 2. The Internet-Standard Management Framework 103 For a detailed overview of the documents that describe the current 104 Internet-Standard Management Framework, please refer to section 7 of 105 RFC 3410 [RFC3410]. 107 Managed objects are accessed via a virtual information store, termed 108 the Management Information Base or MIB. MIB objects are generally 109 accessed through the Simple Network Management Protocol (SNMP). 110 Objects in the MIB are defined using the mechanisms defined in the 111 Structure of Management Information (SMI). This memo specifies a MIB 112 module that is compliant to the SMIv2, which is described in STD 58, 113 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 114 [RFC2580]. 116 3. Overview 118 The TRILL-OAM-MIB module is intended to provide an overall framework 119 for managing TRILL OAM. It leverages the IEEE8021-CFM-MIB and 120 IEEE8021-CFM-V2-MIB modules defined in [802.1Q], and augments the 121 Maintenance End Point(MEP) and MEP Db entries. It also adds a new 122 table for TRILL OAM specific messages. 124 4. Conventions 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 128 "OPTIONAL" in this document are to be interpreted as described in 129 RFC-2119 [RFC2119]. 131 Acronyms used in the document include the following: 132 MTVM - Multi-destination Tree Verification Message [RFC7455] 134 MTVR - Multi-destination Tree Verification Reply [RFC7455] 136 PTM - Path Trace Message [RFC7455] 138 PTR - Path Trace Reply [RFC7455] 140 MEP - Maintenance End Point [RFC7174] [802.1Q] 141 MIP - Maintenance Intermediate Point [RFC7174] [802.1Q] 143 MP - Maintenance Point [RFC7174] 145 CCM - Continuity Check Message [802.1Q] 147 FGL - Fine-Grained Label 149 LBM - Loopback Message [802.1Q] 151 LBR - Loopback Reply [802.1Q] 153 TRILL - Transparent Interconnection of Lots of Links [RFC6325] 155 5. Structure of the MIB module 157 Objects in this MIB module are arranged into subtrees. Each subtree is 158 organized as a set of related objects. The various subtrees are shown 159 below, supplemented with the required elements of the IEEE8021-CFM-MIB 160 module. 162 5.1. Textual Conventions 164 Textual conventions are defined to represent object types relevant to 165 the TRILL OAM MIB. 167 5.2. TRILL-OAM-MIB relationship to IEEE8021-TC-MIB 169 In TRILL, traffic labeling can be done using either a 12-bit VLAN or a 170 24-bit fine grain label [RFC7172]. 172 The IEEE8021-TC-MIB definition of IEEE8021ServiceSelectorType includes 173 the two values: 175 - 1 representing a vlanId, and 177 - 2 representing a 24 bit isid 179 We have chosen to use value 2 for TRILL's fine grain label. As such, 180 TRILL-OAM-MIB will import IEEE8021ServiceSelectorType, 181 IEEE8021ServiceSelectorValueOrNone, and IEEE8021ServiceSelectorValue 182 from IEEE8021-TC-MIB. 184 5.3. TRILL OAM MIB Tree 186 TRILL-OAM MIB Tree describe below consists of trilloamNotifications 187 (Traps) and trillOamMibObjects. trilloamNotifications are sent to 188 management entity whenever a MEP loses/restores contact with its peer 189 Flow MEPs. 191 The TRILL OAM MIB Per MEP Objects are defined in the trillOamMepTable. 192 The trillOamMepTable augments the dot1agCfmMepEntry (please see section 193 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally 194 defined for an individual MEP and its associated Flow. 196 TRILL-OAM-MIB 198 |--trillOamNotifications (trillOamMib 0} 200 |--trillOamFaultAlarm 202 |--trillOamMibObjects {trillOamMib 1} 204 |--trillOamMep {trillOamMibObjects 1} 206 |--trillOamMepTable {trillOamMep 1} - Local TRLL config 208 |--trillOamMepFlowCfgTable 210 |--trillOamPtrTable 212 |--trillOamMtvrTable 214 |--trillOamMepDbTable 216 5.3.1. TRILL OAM MIB Notifications 218 Notifications (fault alarm) are sent to the management entity with the 219 OID of the MEP that has detected the fault. Notifications are generated 220 whenever MEP loses/restores contact with its peer Flow MEPs. 222 5.3.2. TRILL OAM MIB Per MEP Objects 224 The TRILL OAM MIB Per MEP Objects are defined in the trillOamMepTable. 225 The trillOamMepTable augments the dot1agCfmMepEntry (please see section 226 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally 227 defined for an individual MEP and its associated Flow. 229 5.3.2.1. trillOamMepTable Objects 230 This table is an extension of the dot1agCfmMepTable and rows are 231 automatically added or deleted from this table based upon row 232 creation and destruction of the dot1agCfmMepTable. 234 This table represents the local MEP TRILL OAM configuration table. 235 The primary purpose of this table is provide local parameters for the 236 TRILL OAM function found in RFC 7455 and instantiated at a MEP. 238 5.3.2.2. trillOamMepFlowCfgTable Objects 240 Each row in this table represents a Flow Configuration Entry for the 241 associated MEP. This table uses four indices. The first three indices 242 are the indices of the Maintenance Domain, MaNet, and MEP tables. The 243 fourth index is the specific Flow Configuration Entry on the selected 244 MEP. Some write-able objects in this table are only applicable in 245 certain cases (as described under each object below), and attempts to 246 write values for them in other cases will be ignored. 248 5.3.2.3. trillOamPtrTable Objects 250 Each row in this table represents a Path Trace reply Entry for the 251 Defined MEP and Transaction. This table uses four indices. The first 252 three indices identify the MEP and the fourth index specifies the 253 transaction identifier. This transaction identifier uniquely 254 identifies the response for a MEP which can have multiple flow. 256 5.3.2.4. trillOamMtvrTable Objects 258 This table includes managed objects for the Multi-Destination Reply. 259 Each row in the table represents a Multi-destination Reply Entry for 260 the defined MEP and Transaction. This table uses the following five 261 indices: 1) Maintenance Domain, 2) MANET, 3) MEP tables, 4) 262 Transaction identifier of selected MEP, and 5) receive order of 263 Multi-destination replies. 265 Some write-able objects in this table are only applicable in certain 266 cases (as described under each object below), and attempts to write a 267 value for them in other cases will be ignored. 269 5.3.2.5. trillOamMepDbTable Objects 271 This table is an augmentation of the dot1agCfmMepDbTable, and rows 272 are automatically added or deleted from this table based upon row 273 creation and destruction of the dot1agCfmMepDbTable. 275 6. Relationship to other MIB module 277 The IEEE8021-CFM-MIB, and LLDP-MIB contain objects relevant to TRILL 278 OAM MIB. Management objects contained in these modules are not 279 duplicated here, to reduce overlap to the extent possible. From 280 IEEE8021-CFM-MIB following objects are imported 282 o dot1agCfmMdIndex 284 o dot1agCfmMaIndex 286 o dot1agCfmMepIdentifier 288 o dot1agCfmMepEntry 290 o dot1agCfmMepDbEntry 292 o Dot1agCfmIngressActionFieldValue 294 o Dot1agCfmEgressActionFieldValue 296 o Dot1agCfmRemoteMepState 298 From LLDP-MIB following objects are imported 300 o LldpChassisId 302 o LldpChassisIdSubtype 304 o LldpPortId 306 6.1. Relationship to IEEE8021-CFM-MIB 308 trillOamMepTable Augments dot1agCfmMepEntry. Implementation of 309 IEEE8021-CFM-MIB is required as we are Augmenting the IEEE-CFM-MIB 310 Table. Objects/Tables that are not applicable to a TRILL 311 implementation have to be handled by the TRILL implementation back 312 end and appropriate default values as described in IEEE8021-CFM-MIB 313 have to be returned. 315 TRILL Implementation doesn't support Link Trace Message and Link 316 Trace Reply as RFC7455 substituted it with Path Trace Message and 317 Reply for unicast traffic and Multi-destination Tree verification 318 Message and Reply for multicast traffic, and statistics with respect 319 of these message should be default as per IEEE8021-CFM-MIB. 321 6.2. MIB modules required for IMPORTS 323 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 324 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IEEE-8021-CFM-MIB, LLDP- 325 MIB. 327 7. Definition of the TRILL OAM MIB module 329 TRILL-OAM-MIB DEFINITIONS ::= BEGIN 331 IMPORTS 333 MODULE-IDENTITY, 334 OBJECT-TYPE, 335 Counter32, 336 Unsigned32, 337 Integer32, 338 mib-2, 339 NOTIFICATION-TYPE 340 FROM SNMPv2-SMI 341 RowStatus, 342 TruthValue, 343 TimeStamp, 344 MacAddress 345 FROM SNMPv2-TC 346 OBJECT-GROUP, 347 NOTIFICATION-GROUP, 348 MODULE-COMPLIANCE 349 FROM SNMPv2-CONF 350 dot1agCfmMdIndex, 351 dot1agCfmMaIndex, 352 dot1agCfmMepIdentifier, 353 dot1agCfmMepEntry, 354 dot1agCfmMepDbEntry, 355 Dot1agCfmIngressActionFieldValue, 356 Dot1agCfmEgressActionFieldValue, 357 Dot1agCfmRemoteMepState 358 FROM IEEE8021-CFM-MIB 359 LldpChassisId, 360 LldpChassisIdSubtype, 361 LldpPortId, 362 LldpPortIdSubtype 363 FROM LLDP-MIB; 365 trillOamMib MODULE-IDENTITY 366 LAST-UPDATED "201508231200Z" 367 ORGANIZATION "IETF TRILL WG" 368 CONTACT-INFO 369 "E-mail: trill@ietf.org" 370 DESCRIPTION 371 "This MIB module contains the management objects for the 372 management of Trill Services Operations, Administration 373 and Maintenance. 374 Initial version. Published as RFC xxxx. 376 ------------------------------------------------------------- 377 Reference Overview 379 A number of base documents have been used to create the 380 Textual Conventions MIB. The following are the 381 abbreviations for the baseline documents: 383 [CFM] refers to 'Connectivity Fault Management', 384 IEEE 802.1Q-2014, December 2014 385 [Q.840.1] refers to 'ITU-T Requirements and analysis for 386 NMS-EMS management interface of Ethernet over Transport and 387 Metro Ethernet Network (EoT/MEN)', March 2007 388 [Y.1731] refers to ITU-T Y.1731 'OAM functions and mechanisms 389 for Ethernet based networks', February 2011 390 ------------------------------------------------------------- 392 Abbreviations Used 394 Term Definition 395 CCM Continuity Check Message 396 CFM Connectivity Fault Management 397 CoS Class of Service 398 IEEE Institute of Electrical and Electronics 399 Engineers 400 IETF Internet Engineering Task Force 401 ITU-T International Telecommunication Union - 402 Telecommunication Standardization Bureau 403 MAC Media Access Control 404 MA Maintenance Association (equivalent to a MEG) 405 MD Maintenance Domain (equivalent to a OAM 406 Domain in MEF 17) 407 MD Level Maintenance Domain Level (equivalent to a 408 MEG level) 409 ME Maintenance Entity 410 MEG Maintenance Entity Group (equivalent to a MA) 411 MEG Level Maintenance Entity Group Level (equivalent to 412 MD Level) 413 MEP Maintenance Association End Point or MEG End 414 Point 415 MIB Management Information Base 416 MIP Maintenance Domain Intermediate Point or 417 MEG Intermediate Point 418 MP Maintenance Point. One of either a MEP or a MIP 419 OAM Operations, Administration, and Maintenance 420 On-Demand OAM actions that are initiated via 421 manual intervention for a limited time to carry 422 out diagnostics. On-Demand OAM can result in 423 singular or periodic OAM actions during the 424 diagnostic time interval 425 PDU Protocol Data Unit 426 RFC Request for Comment 427 SNMP Simple Network Management Protocol 428 SNMP Agent An SNMP entity containing one or more command 429 responder and/or notification originator 430 applications(along with their associated SNMP 431 engine). Typically implemented in Network 432 Element. 433 SNMP Manager An SNMP entity containing one or more command 434 generator and/or notification receiver 435 applications (along with their associated SNMP 436 engine). Typically implemented in an 437 EMS or NMS. 438 TLV Type Length Value, a method of encoding Objects 439 UTC Coordinated Universal Time 440 UNI User-to-Network Interface 441 VLAN Virtual LAN 442 PTR Path Trace Reply 443 PTM Path Trace Message 444 MTVR Multi-destination Tree Verification Reply 445 MTVM Multi-destination Tree Verification Message" 447 REVISION "201508231200Z" 448 DESCRIPTION 449 "Initial version. Published as RFC xxxx." 450 ::= { mib-2 12000 } 452 -- RFC Ed.: assigned by IANA, see section 9 for details 453 -- 454 -- ***************************************************************** 455 -- Object definitions in the TRILL OAM MIB Module 456 -- ***************************************************************** 458 trillOamNotifications OBJECT IDENTIFIER 459 ::= { trillOamMib 0 } 461 trillOamMibObjects OBJECT IDENTIFIER 462 ::= { trillOamMib 1 } 464 trillOamMibConformance OBJECT IDENTIFIER 465 ::= { trillOamMib 2 } 467 -- ***************************************************************** 468 -- Groups in the TRILL OAM MIB Module 469 -- ***************************************************************** 471 trillOamMep OBJECT IDENTIFIER 472 ::= { trillOamMibObjects 1 } 474 -- ***************************************************************** 475 -- TRILL OAM MEP Configuration 476 -- ***************************************************************** 478 trillOamMepTable OBJECT-TYPE 479 SYNTAX SEQUENCE OF TrillOamMepEntry 480 MAX-ACCESS not-accessible 481 STATUS current 482 DESCRIPTION 483 "This table is an extension of the dot1agCfmMepTable and 484 rows are automatically added or deleted from this table 485 based upon row creation and destruction of the 486 dot1agCfmMepTable. 488 This table represents the local MEP TRILL OAM 489 configuration table. The primary purpose of this table 490 is provide local parameters for the TRILL OAM function 491 found in RFC 7455 and instantiated at a MEP." 492 REFERENCE "RFC 7455" 493 ::= { trillOamMep 1 } 495 trillOamMepEntry OBJECT-TYPE 496 SYNTAX TrillOamMepEntry 497 MAX-ACCESS not-accessible 498 STATUS current 499 DESCRIPTION 500 "The conceptual row of trillOamMepTable." 501 AUGMENTS { dot1agCfmMepEntry } 502 ::= { trillOamMepTable 1 } 504 TrillOamMepEntry ::= SEQUENCE { 505 trillOamMepRName Unsigned32, 506 trillOamMepNextPtmTId Counter32, 507 trillOamMepNextMtvmTId Counter32, 508 trillOamMepPtrIn Counter32, 509 trillOamMepPtrInOutofOrder Counter32, 510 trillOamMepPtrOut Counter32, 511 trillOamMepMtvrIn Counter32, 512 trillOamMepMtvrInOutofOrder Counter32, 513 trillOamMepMtvrOut Counter32, 514 trillOamMepTxLbmDestRName Unsigned32, 515 trillOamMepTxLbmHC Unsigned32, 516 trillOamMepTxLbmReplyModeOob TruthValue, 517 trillOamMepTransmitLbmReplyIp OCTET STRING, 518 trillOamMepTxLbmFlowEntropy OCTET STRING, 519 trillOamMepTxPtmDestRName Unsigned32, 520 trillOamMepTxPtmHC Unsigned32, 521 trillOamMepTxPtmReplyModeOob TruthValue, 522 trillOamMepTransmitPtmReplyIp OCTET STRING, 523 trillOamMepTxPtmFlowEntropy OCTET STRING, 524 trillOamMepTxPtmStatus TruthValue, 525 trillOamMepTxPtmResultOK TruthValue, 526 trillOamMepTxPtmSeqNumber Unsigned32, 527 trillOamMepTxPtmMessages Integer32, 528 trillOamMepTxMtvmTree Unsigned32, 529 trillOamMepTxMtvmHC Unsigned32, 530 trillOamMepTxMtvmReplyModeOob TruthValue, 531 trillOamMepTransmitMtvmReplyIp OCTET STRING, 532 trillOamMepTxMtvmFlowEntropy OCTET STRING, 533 trillOamMepTxMtvmStatus TruthValue, 534 trillOamMepTxMtvmResultOK TruthValue, 535 trillOamMepTxMtvmMessages Integer32, 536 trillOamMepTxMtvmSeqNumber Unsigned32, 537 trillOamMepTxMtvmScopeList OCTET STRING, 538 trillOamMepDiscontinuityTime TimeStamp 539 } 541 trillOamMepRName OBJECT-TYPE 542 SYNTAX Unsigned32 (0..65471) 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "This object contains Rbridge NickName of TRILL Rbridge as 547 defined in RFC 6325 section 3.7." 548 REFERENCE "RFC 7455 and RFC 6325 section 3.7" 549 ::= { trillOamMepEntry 1 } 551 trillOamMepNextPtmTId OBJECT-TYPE 552 SYNTAX Counter32 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "Next sequence number/transaction identifier to be sent in a 557 Multi-destination message. This sequence number can be zero 558 because it wraps around. Implementation of this identifier 559 should be should provide a unique code value in order to 560 identify Transaction Id for a MEP with multiple flows." 561 REFERENCE "RFC 7455 10.1.1" 562 ::= { trillOamMepEntry 2 } 564 trillOamMepNextMtvmTId OBJECT-TYPE 565 SYNTAX Counter32 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "Next sequence number/transaction identifier to be sent in a 570 Multi-destination message. This sequence number can be zero 571 because it wraps around. Implementation should be unique to 572 identify Transaction Id for a MEP with multiple flows." 573 REFERENCE "RFC 7455 11.2.1" 574 ::= { trillOamMepEntry 3 } 576 trillOamMepPtrIn OBJECT-TYPE 577 SYNTAX Counter32 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "Total number of valid, in-order Path Trace Replies 582 received." 583 REFERENCE "RFC 7455 section 10" 584 ::= { trillOamMepEntry 4 } 586 trillOamMepPtrInOutofOrder OBJECT-TYPE 587 SYNTAX Counter32 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "Total number of valid, out-of-order Path Trace Replies 592 received." 593 REFERENCE "RFC 7455 section 10" 594 ::= { trillOamMepEntry 5 } 596 trillOamMepPtrOut OBJECT-TYPE 597 SYNTAX Counter32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Total number of valid, Path Trace Replies 602 transmitted." 603 REFERENCE "RFC 7455 section 10" 604 ::= { trillOamMepEntry 6 } 606 trillOamMepMtvrIn OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "Total number of valid, in-order Multi-destination 612 Replies received." 613 REFERENCE "RFC 7455 section 11" 614 ::= { trillOamMepEntry 7 } 616 trillOamMepMtvrInOutofOrder OBJECT-TYPE 617 SYNTAX Counter32 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "Total number of valid, out-of-order Multi-destination 622 Replies received." 623 REFERENCE "RFC 7455 section 11" 624 ::= { trillOamMepEntry 8 } 626 trillOamMepMtvrOut OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "Total number of valid, Multi-destination Replies 632 transmitted." 633 REFERENCE "RFC 7455 section 11" 634 ::= { trillOamMepEntry 9 } 636 trillOamMepTxLbmDestRName OBJECT-TYPE 637 SYNTAX Unsigned32 (0..65471) 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "The Target Destination Rbridge NickName Field as 642 defined in RFC 6325 section 3.7 to be transmitted." 643 REFERENCE "RFC 7455 and RFC6325 section 3.7" 644 ::= { trillOamMepEntry 10 } 646 trillOamMepTxLbmHC OBJECT-TYPE 647 SYNTAX Unsigned32(1..63) 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "The Hop Count to be transmitted. 652 " 653 REFERENCE "RFC 7455 section 9 and 3" 654 ::= { trillOamMepEntry 11 } 656 trillOamMepTxLbmReplyModeOob OBJECT-TYPE 657 SYNTAX TruthValue 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "True Indicates that Reply of Lbm is out of band and 662 out of band IP Address TLV is to be transmitted. 663 False indicates that In band reply is transmitted." 664 REFERENCE "RFC 7455 9.2.1" 665 ::= { trillOamMepEntry 12 } 667 trillOamMepTransmitLbmReplyIp OBJECT-TYPE 668 SYNTAX OCTET STRING (SIZE (4..16)) 669 MAX-ACCESS read-create 670 STATUS current 671 DESCRIPTION 672 "IP address for out of band IP Address TLV is to be 673 transmitted, Maximum length for IPv6 is 16 OCTET 674 and IPv4 is 4 OCTET." 675 REFERENCE "RFC 7455 section 3" 676 ::= { trillOamMepEntry 13 } 678 trillOamMepTxLbmFlowEntropy OBJECT-TYPE 679 SYNTAX OCTET STRING (SIZE (96)) 680 MAX-ACCESS read-create 681 STATUS current 682 DESCRIPTION 683 "96 Byte Flow Entropy as defined in RFC 7455 to be 684 transmitted." 685 REFERENCE "RFC 7455 section 3" 686 ::= { trillOamMepEntry 14 } 688 trillOamMepTxPtmDestRName OBJECT-TYPE 689 SYNTAX Unsigned32 (0..65471) 690 MAX-ACCESS read-create 691 STATUS current 692 DESCRIPTION 693 "The Target Destination Rbridge NickName Field 694 as defined in RFC 6325 section 3.7 to be transmitted." 695 REFERENCE "RFC 7455 and RFC6325 section 3.7" 696 ::= { trillOamMepEntry 15 } 698 trillOamMepTxPtmHC OBJECT-TYPE 699 SYNTAX Unsigned32 (1..63) 700 MAX-ACCESS read-create 701 STATUS current 702 DESCRIPTION 703 "The Hop Count field to be transmitted." 705 REFERENCE "RFC 7455 section 3" 706 ::= { trillOamMepEntry 16 } 708 trillOamMepTxPtmReplyModeOob OBJECT-TYPE 709 SYNTAX TruthValue 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "True Indicates that Reply of Ptm will be made out of 714 band and out of band IP Address TLV is to be 715 transmitted. False indicates that In band reply 716 is transmitted." 717 REFERENCE "RFC 7455 section 10" 718 DEFVAL { false } 719 ::= { trillOamMepEntry 17 } 721 trillOamMepTransmitPtmReplyIp OBJECT-TYPE 722 SYNTAX OCTET STRING (SIZE (4..16)) 723 MAX-ACCESS read-create 724 STATUS current 725 DESCRIPTION 726 "IP address for out of band IP Address TLV is to be 727 Transmitted. The maximum length for IPv6 728 address is 16 Octets. The maximum length 729 for an IPv4 address is 4 octets." 730 REFERENCE "RFC 7455 section 3 and 10" 731 ::= { trillOamMepEntry 18 } 733 trillOamMepTxPtmFlowEntropy OBJECT-TYPE 734 SYNTAX OCTET STRING (SIZE (96)) 735 MAX-ACCESS read-create 736 STATUS current 737 DESCRIPTION 738 "96 Byte Flow Entropy as defined in RFC 7455 to be 739 transmitted." 740 REFERENCE "RFC 7455 section 3" 741 ::= { trillOamMepEntry 19 } 743 trillOamMepTxPtmStatus OBJECT-TYPE 744 SYNTAX TruthValue 745 MAX-ACCESS read-create 746 STATUS current 747 DESCRIPTION 748 "A Boolean flag set to true by the MEP Path Trace 749 Initiator State 750 Machine or an MIB manager to indicate that another 751 PTM is being transmitted. 752 This is Reset to false by the MEP Initiator 753 State Machine. 754 The PTM managed objects in the MEP table are used 755 in a manner similar to that described for LBM 756 transmission in dot1agCfmMepTable. As per RFC7455 757 section 10, Operation of the Path Trace Message is 758 identical to the Loopback Message except that it is 759 first transmitted with a TRILL Header Hop count 760 field value of 1 and then retransmitted with 761 incrementing Hop count until a response is received 762 from the destination RBridge, or the Hop Count 763 reaches a configured maximum value. 764 trillOamMepTxPtmStatus Status is reset to FALSE 765 by initiator when last PTM is transmitted." 766 REFERENCE "RFC 7455 section 10" 767 DEFVAL { false } 768 ::= { trillOamMepEntry 20 } 770 trillOamMepTxPtmResultOK OBJECT-TYPE 771 SYNTAX TruthValue 772 MAX-ACCESS read-create 773 STATUS current 774 DESCRIPTION 775 "Indicates the following results of the operation: 776 - true The Path Trace Message(s) will be (or has been) 777 sent. 778 - false The Path Trace Message(s) will not be sent." 779 REFERENCE "RFC 7455 section 10" 780 DEFVAL { true } 781 ::= { trillOamMepEntry 21 } 783 trillOamMepTxPtmSeqNumber OBJECT-TYPE 784 SYNTAX Unsigned32 785 MAX-ACCESS read-create 786 STATUS current 787 DESCRIPTION 788 "The Path Trace Transaction Identifier of the first 789 PTM (to be) sent. The value returned is 790 undefined if trillOamMepTxPtmResultOK is false." 791 REFERENCE "RFC 7455 section 10" 792 ::= { trillOamMepEntry 22 } 794 trillOamMepTxPtmMessages OBJECT-TYPE 795 SYNTAX Integer32 (1..1024) 796 MAX-ACCESS read-create 797 STATUS current 798 DESCRIPTION 799 "The number of Path Trace messages to be transmitted. 800 As per RFC section 10 first Path Trace Messages 801 is transmitted with Hop count 1 and An RBridge may 802 continue to retransmit the request at periodic 803 interval until response is received from destination 804 Rbridge, or the Hop Count reaches a configured 805 maximum value. The event of the Destination 806 response being received or the Hop count reaching 807 its maximum is treated as single Counter 808 increment of this object, and above process is 809 repeated starting 810 Hop count 1 till maximum PTM transmission 811 is reached. It's treated as Repeat Counter for 812 above described operation." 813 REFERENCE "RFC 7455 section 10" 814 ::= { trillOamMepEntry 23 } 816 trillOamMepTxMtvmTree OBJECT-TYPE 817 SYNTAX Unsigned32 818 MAX-ACCESS read-create 819 STATUS current 820 DESCRIPTION 821 "The Multi-destination Tree is identifier for tree as 822 defined in RFC6325." 823 ::= { trillOamMepEntry 24 } 825 trillOamMepTxMtvmHC OBJECT-TYPE 826 SYNTAX Unsigned32(1..63) 827 MAX-ACCESS read-create 828 STATUS current 829 DESCRIPTION 830 "The Hop Count field to be transmitted. 831 " 832 REFERENCE "RFC 7455 section 3, RFC 6325 section 3" 833 ::= { trillOamMepEntry 25 } 835 trillOamMepTxMtvmReplyModeOob OBJECT-TYPE 836 SYNTAX TruthValue 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "A True Indicates that Reply of Mtvm is out of band and 841 out of band IP Address TLV is to be transmitted. 842 A False indicates that In band reply is transmitted." 843 REFERENCE "RFC 7455 section 11" 844 ::= { trillOamMepEntry 26 } 846 trillOamMepTransmitMtvmReplyIp OBJECT-TYPE 847 SYNTAX OCTET STRING (SIZE (4..16)) 848 MAX-ACCESS read-create 849 STATUS current 850 DESCRIPTION 851 "IP address for out of band IP Address TLV is to be 852 transmitted. The Maximum length for IPv6 is 16 OCTET 853 and IPv4 is 4 OCTET." 854 REFERENCE "RFC 7455 section 11" 855 ::= { trillOamMepEntry 27 } 857 trillOamMepTxMtvmFlowEntropy OBJECT-TYPE 858 SYNTAX OCTET STRING (SIZE (96)) 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "96 Byte Flow Entropy as defined in RFC 7455 to be 863 transmitted." 864 REFERENCE "RFC 7455 section 3" 865 ::= { trillOamMepEntry 28 } 867 trillOamMepTxMtvmStatus OBJECT-TYPE 868 SYNTAX TruthValue 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "A Boolean flag set to true by the MEP Multi Destination 873 Initiator State Machine or an MIB manager to indicate 874 that another Mtvm is being transmitted. 875 Reset to false by the MEP Initiator State Machine. 876 The Mtvm managed objects in the MEP table are used 877 in a manner similar to that described for LBM 878 transmission in dot1agCfmMepTable. As per RFC7455 879 section 11, Operation of the MTvm Message is 880 identical to the Loopback Message except that it is 881 first transmitted with a TRILL Header Hop count 882 field value of 1 and it is retransmitted incrementing 883 Hop count until a response is received from the 884 destination RBridge, or the Hop Count reaches a 885 configured maximum value. trillOamMepTxMtvmStatus 886 Status is reset to FALSE by initiator when last Mtvm 887 is transmitted." 888 REFERENCE "RFC 7455 section 11" 889 DEFVAL { false } 890 ::= { trillOamMepEntry 29 } 892 trillOamMepTxMtvmResultOK OBJECT-TYPE 893 SYNTAX TruthValue 894 MAX-ACCESS read-create 895 STATUS current 896 DESCRIPTION 897 "Indicates the result of the operation in 898 the following way: 899 - true The Multi-destination Message(s) will be 900 (or has been) sent. 901 - false The Multi-destination Message(s) will not be sent." 902 REFERENCE "RFC 7455 section 11" 903 DEFVAL { true } 904 ::= { trillOamMepEntry 30 } 906 trillOamMepTxMtvmMessages OBJECT-TYPE 907 SYNTAX Integer32 (1..1024) 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "The number of Multi Destination messages to be transmitted. 912 Rbridge retransmit the Multi Destination message 913 incrementing the session Identification Number at periodic 914 interval until either retransmission count expires." 915 REFERENCE "RFC 7455 section 11" 916 ::= { trillOamMepEntry 31 } 918 trillOamMepTxMtvmSeqNumber OBJECT-TYPE 919 SYNTAX Unsigned32 920 MAX-ACCESS read-create 921 STATUS current 922 DESCRIPTION 923 "The Multi-destination Transaction Identifier of the 924 first MTVM (to be) 925 sent. The value returned is undefined if 926 trillOamMepTxMtvmResultOK is false." 927 REFERENCE "RFC 7455 section 11" 928 ::= { trillOamMepEntry 32 } 930 trillOamMepTxMtvmScopeList OBJECT-TYPE 931 SYNTAX OCTET STRING 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 "The Multi-destination Rbridge Scope list which 936 requires 2 octets per Rbridge." 937 REFERENCE "RFC 7455 section 11" 938 ::= { trillOamMepEntry 33 } 940 trillOamMepDiscontinuityTime OBJECT-TYPE 941 SYNTAX TimeStamp 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "Snapshot of the value of the sysUpTime object at the 946 beginning of the latest period of continuity of the 947 statistical counters associated with this MEP." 948 ::= { trillOamMepEntry 34 } 950 -- ***************************************************************** 951 -- TRILL OAM Tx Measurement Configuration Table 952 -- ***************************************************************** 954 trillOamMepFlowCfgTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF TrillOamMepFlowCfgEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "This table includes configuration objects and operations 960 for the Trill OAM RFC 7455. 962 Each row in the table represents a Flow configuration 963 Entry for the defined MEP. This table uses four indices. 964 The first three indices are the indices of the Maintenance 965 Domain, MaNet, and MEP tables. The fourth index is the 966 specific flow configuration Entry on the selected MEP. 968 Some writable objects in this table are only applicable in 969 certain cases (as described under each object), and 970 attempts to write values for them in other cases 971 will be ignored." 972 REFERENCE "RFC 7455" 973 ::= { trillOamMep 2 } 975 trillOamMepFlowCfgEntry OBJECT-TYPE 976 SYNTAX TrillOamMepFlowCfgEntry 977 MAX-ACCESS not-accessible 978 STATUS current 979 DESCRIPTION 980 "The conceptual row of trillOamMepFlowCfgTable." 981 INDEX { 982 dot1agCfmMdIndex, 983 dot1agCfmMaIndex, 984 dot1agCfmMepIdentifier, 985 trillOamMepFlowCfgIndex 986 } 987 ::= { trillOamMepFlowCfgTable 1 } 989 TrillOamMepFlowCfgEntry ::= SEQUENCE { 990 trillOamMepFlowCfgIndex Unsigned32, 991 trillOamMepFlowCfgFlowEntropy OCTET STRING, 992 trillOamMepFlowCfgDestRName Unsigned32, 993 trillOamMepFlowCfgFlowHC Unsigned32, 994 trillOamMepFlowCfgRowStatus RowStatus 995 } 997 trillOamMepFlowCfgIndex OBJECT-TYPE 998 SYNTAX Unsigned32 (1..65535) 999 MAX-ACCESS not-accessible 1000 STATUS current 1001 DESCRIPTION 1002 "An index to the Trill OAM MEP Flow Configuration table which 1003 indicates the specific Flow for the MEP. 1005 The index is never reused for other flow sessions on the 1006 same 1007 MEP while this session is active. The index value keeps 1008 increasing until it wraps to 0. This value can also be 1009 used in Flow-identifier TLV RFC 7455." 1010 REFERENCE "RFC 7455" 1011 ::= { trillOamMepFlowCfgEntry 1 } 1013 trillOamMepFlowCfgFlowEntropy OBJECT-TYPE 1014 SYNTAX OCTET STRING (SIZE (96)) 1015 MAX-ACCESS read-create 1016 STATUS current 1017 DESCRIPTION 1018 "This is 96 byte of Flow Entropy as described in 1019 TRILL OAM RFC 7455." 1020 REFERENCE "RFC 7455 section 3" 1021 ::= { trillOamMepFlowCfgEntry 2 } 1023 trillOamMepFlowCfgDestRName OBJECT-TYPE 1024 SYNTAX Unsigned32 (0..65471) 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "The Target Destination Rbridge NickName Field as 1029 defined in RFC 6325 section 3.7 to be transmitted." 1030 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1031 ::= { trillOamMepFlowCfgEntry 3 } 1033 trillOamMepFlowCfgFlowHC OBJECT-TYPE 1034 SYNTAX Unsigned32 (1..63) 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "The Time to Live field to be transmitted. 1039 to be transmitted." 1041 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1042 ::= { trillOamMepFlowCfgEntry 4 } 1044 trillOamMepFlowCfgRowStatus OBJECT-TYPE 1045 SYNTAX RowStatus 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 "The status of the row. 1051 The writable columns in a row cannot be changed if the row 1052 is active. All columns MUST have a valid value before a row 1053 can be activated." 1054 ::= { trillOamMepFlowCfgEntry 5 } 1056 -- ****************************************************************** 1057 -- TRILL OAM Path Trace Reply Table 1058 -- ****************************************************************** 1060 trillOamPtrTable OBJECT-TYPE 1061 SYNTAX SEQUENCE OF TrillOamPtrEntry 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "This table includes Path Trace Reply objects and 1066 operations for the Trill OAM RFC 7455. 1068 Each row in the table represents a Path Trace Reply Entry for 1069 the defined MEP and Transaction. 1070 This table uses four indices. 1071 The first three indices are the indices of the 1072 Maintenance Domain, 1073 MaNet, and MEP tables. The fourth index is the specific 1074 Transaction Identifier on the selected MEP. 1076 Some writable objects in this table are only applicable in 1077 certain cases (as described under each object), 1078 and attempts to 1079 write values for them in other cases will be ignored." 1080 REFERENCE "RFC 7455" 1081 ::= { trillOamMep 3 } 1083 trillOamPtrEntry OBJECT-TYPE 1084 SYNTAX TrillOamPtrEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "The conceptual row of trillOamPtrTable." 1089 INDEX { 1090 dot1agCfmMdIndex, 1091 dot1agCfmMaIndex, 1092 dot1agCfmMepIdentifier, 1093 trillOamMepPtrTransactionId 1094 } 1095 ::= { trillOamPtrTable 1 } 1097 TrillOamPtrEntry ::= SEQUENCE { 1098 trillOamMepPtrTransactionId Unsigned32, 1099 trillOamMepPtrHC Unsigned32, 1100 trillOamMepPtrFlag Unsigned32, 1101 trillOamMepPtrErrorCode Unsigned32, 1102 trillOamMepPtrTerminalMep TruthValue, 1103 trillOamMepPtrLastEgressId Unsigned32, 1104 trillOamMepPtrIngress Dot1agCfmIngressActionFieldValue, 1105 trillOamMepPtrIngressMac MacAddress, 1106 trillOamMepPtrIngressPortIdSubtype LldpPortIdSubtype, 1107 trillOamMepPtrIngressPortId LldpPortId, 1108 trillOamMepPtrEgress Dot1agCfmEgressActionFieldValue, 1109 trillOamMepPtrEgressMac MacAddress, 1110 trillOamMepPtrEgressPortIdSubtype LldpPortIdSubtype, 1111 trillOamMepPtrEgressPortId LldpPortId, 1112 trillOamMepPtrChassisIdSubtype LldpChassisIdSubtype, 1113 trillOamMepPtrChassisId LldpChassisId, 1114 trillOamMepPtrOrganizationSpecificTlv OCTET STRING, 1115 trillOamMepPtrNextHopNicknames OCTET STRING 1116 } 1118 trillOamMepPtrTransactionId OBJECT-TYPE 1119 SYNTAX Unsigned32 (0..4294967295) 1120 MAX-ACCESS not-accessible 1121 STATUS current 1122 DESCRIPTION 1123 "Transaction identifier/sequence number returned by a 1124 previous transmit path trace message command, 1125 indicating which PTM's response is going to be returned." 1126 REFERENCE "RFC 7455 section 10" 1127 ::= { trillOamPtrEntry 1 } 1129 trillOamMepPtrHC OBJECT-TYPE 1130 SYNTAX Unsigned32 (1..63) 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "Hop Count field value for a returned PTR." 1135 REFERENCE "RFC 7455" 1136 ::= { trillOamPtrEntry 2 } 1138 trillOamMepPtrFlag OBJECT-TYPE 1139 SYNTAX Unsigned32 (0..15) 1140 MAX-ACCESS read-only 1141 STATUS current 1142 DESCRIPTION 1143 "FCOI (TRILL OAM Message TLV) field value for a 1144 returned PTR." 1145 REFERENCE "RFC 7455, 8.4.3" 1146 ::= { trillOamPtrEntry 3 } 1148 trillOamMepPtrErrorCode OBJECT-TYPE 1149 SYNTAX Unsigned32 (0..65535) 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "Return Code and Return Sub code value for a returned PTR." 1154 REFERENCE "RFC 7455, 8.4.3" 1155 ::= { trillOamPtrEntry 4 } 1157 trillOamMepPtrTerminalMep OBJECT-TYPE 1158 SYNTAX TruthValue 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 "A boolean value stating whether the forwarded PTM reached a 1163 MEP enclosing its MA, as returned in the Terminal MEP flag of 1164 the Flags field." 1165 REFERENCE "RFC 7455" 1166 ::= { trillOamPtrEntry 5 } 1168 trillOamMepPtrLastEgressId OBJECT-TYPE 1169 SYNTAX Unsigned32 (0..65535) 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "An Integer field holding the Last Egress Identifier returned 1174 in the PTR Upstream Rbridge nickname TLV of the PTR. 1175 The Last Egress Identifier identifies the Upstream Nickname." 1176 REFERENCE "RFC 7455 8.4.1" 1177 ::= { trillOamPtrEntry 6 } 1179 trillOamMepPtrIngress OBJECT-TYPE 1180 SYNTAX Dot1agCfmIngressActionFieldValue 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "The value returned in the Ingress Action Field of the PTR. 1185 The value ingNoTlv(0) indicates that no Reply Ingress TLV was 1186 returned in the PTM." 1187 REFERENCE "RFC 7455 8.4.1" 1188 ::= { trillOamPtrEntry 7 } 1190 trillOamMepPtrIngressMac OBJECT-TYPE 1191 SYNTAX MacAddress 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "MAC address returned in the ingress MAC address field." 1196 REFERENCE "RFC 7455 8.4.1" 1197 ::= { trillOamPtrEntry 8 } 1199 trillOamMepPtrIngressPortIdSubtype OBJECT-TYPE 1200 SYNTAX LldpPortIdSubtype 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "Ingress Port ID. The format of this object is determined by 1205 the value of the trillOamMepPtrIngressPortIdSubtype object." 1206 REFERENCE "RFC 7455 8.4.1" 1207 ::= { trillOamPtrEntry 9 } 1209 trillOamMepPtrIngressPortId OBJECT-TYPE 1210 SYNTAX LldpPortId 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "Ingress Port ID. The format of this object is determined by 1215 the value of the trillOamMepPtrIngressPortId object." 1216 REFERENCE "RFC 7455 8.4.1" 1217 ::= { trillOamPtrEntry 10 } 1219 trillOamMepPtrEgress OBJECT-TYPE 1220 SYNTAX Dot1agCfmEgressActionFieldValue 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "The value returned in the Egress Action Field of the PTR. 1225 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1226 returned in the PTM." 1227 REFERENCE "RFC 7455 8.4.1" 1228 ::= { trillOamPtrEntry 11 } 1230 trillOamMepPtrEgressMac OBJECT-TYPE 1231 SYNTAX MacAddress 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "MAC address returned in the egress MAC address field." 1236 REFERENCE "RFC 7455 8.4.1" 1237 ::= { trillOamPtrEntry 12 } 1239 trillOamMepPtrEgressPortIdSubtype OBJECT-TYPE 1240 SYNTAX LldpPortIdSubtype 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "Egress Port ID. The format of this object is determined by 1245 the value of the trillOamMepPtrEgressPortIdSubtype object." 1246 REFERENCE "RFC 7455 8.4.1" 1247 ::= { trillOamPtrEntry 13 } 1249 trillOamMepPtrEgressPortId OBJECT-TYPE 1250 SYNTAX LldpPortId 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "Egress Port ID. The format of this object is determined by 1255 the value of the trillOamMepPtrEgressPortId object." 1256 REFERENCE "RFC 7455 8.4.1" 1257 ::= { trillOamPtrEntry 14 } 1259 trillOamMepPtrChassisIdSubtype OBJECT-TYPE 1260 SYNTAX LldpChassisIdSubtype 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "This object specifies the format of the Chassis ID returned 1265 in the Sender ID TLV of the PTR, if any. This value is 1266 meaningless if the trillOamMepPtrChassisId 1267 has a length of 0." 1268 REFERENCE "RFC 7455 8.4.1" 1269 ::= { trillOamPtrEntry 15 } 1271 trillOamMepPtrChassisId OBJECT-TYPE 1272 SYNTAX LldpChassisId 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "The Chassis ID returned in the Sender ID TLV of the PTR, if 1277 any. The format of this object is determined by the 1278 value of the trillOamMepPtrChassisIdSubtype object." 1279 REFERENCE "RFC 7455 8.4.1" 1280 ::= { trillOamPtrEntry 16 } 1282 trillOamMepPtrOrganizationSpecificTlv OBJECT-TYPE 1283 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "All Organization specific TLVs 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 17 } 1293 trillOamMepPtrNextHopNicknames OBJECT-TYPE 1294 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "Next hop Rbridge List TLV returned in the PTR, if 1299 any. Includes all octets including and following the TLV 1300 Length field of each TLV, concatenated together." 1301 REFERENCE "RFC 7455 8.4.1" 1302 ::= { trillOamPtrEntry 18 } 1304 -- ****************************************************************** 1305 -- TRILL OAM Multi Destination Reply Table 1306 -- ****************************************************************** 1308 trillOamMtvrTable OBJECT-TYPE 1309 SYNTAX SEQUENCE OF TrillOamMtvrEntry 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "This table includes Multi-destination Reply objects and 1314 operations for the Trill OAM RFC 7455. 1316 Each row in the table represents a Multi-destination Reply 1317 Entry for the defined MEP and Transaction. 1318 This table uses five indices. 1319 The first three indices are the indices of the 1320 Maintenance Domain, 1321 MaNet, and MEP tables. The fourth index is the specific 1322 Transaction Identifier on the selected MEP. 1323 The fifth index is the receive order of Multi-destination 1324 replies. 1326 Some writable objects in this table are only applicable in 1327 certain cases (as described under each object), 1328 and attempts to 1329 write values for them in other cases will be ignored." 1330 REFERENCE "RFC 7455" 1331 ::= { trillOamMep 4 } 1333 trillOamMtvrEntry OBJECT-TYPE 1334 SYNTAX TrillOamMtvrEntry 1335 MAX-ACCESS not-accessible 1336 STATUS current 1337 DESCRIPTION 1338 "The conceptual row of trillOamMtvrTable." 1339 INDEX { 1340 dot1agCfmMdIndex, 1341 dot1agCfmMaIndex, 1342 dot1agCfmMepIdentifier, 1343 trillOamMepPtrTransactionId, 1344 trillOamMepMtvrReceiveOrder 1345 } 1346 ::= { trillOamMtvrTable 1 } 1348 TrillOamMtvrEntry ::= SEQUENCE { 1349 trillOamMepMtvrTransactionId Unsigned32, 1350 trillOamMepMtvrReceiveOrder Unsigned32, 1351 trillOamMepMtvrFlag Unsigned32, 1352 trillOamMepMtvrErrorCode Unsigned32, 1353 trillOamMepMtvrLastEgressId Unsigned32, 1354 trillOamMepMtvrIngress Dot1agCfmIngressActionFieldValue, 1355 trillOamMepMtvrIngressMac MacAddress, 1356 trillOamMepMtvrIngressPortIdSubtype LldpPortIdSubtype, 1357 trillOamMepMtvrIngressPortId LldpPortId, 1358 trillOamMepMtvrEgress Dot1agCfmEgressActionFieldValue, 1359 trillOamMepMtvrEgressMac MacAddress, 1360 trillOamMepMtvrEgressPortIdSubtype LldpPortIdSubtype, 1361 trillOamMepMtvrEgressPortId LldpPortId, 1362 trillOamMepMtvrChassisIdSubtype LldpChassisIdSubtype, 1363 trillOamMepMtvrChassisId LldpChassisId, 1364 trillOamMepMtvrOrganizationSpecificTlv OCTET STRING, 1365 trillOamMepMtvrNextHopNicknames OCTET STRING, 1366 trillOamMepMtvrReceiverAvailability TruthValue, 1367 trillOamMepMtvrReceiverCount TruthValue 1368 } 1370 trillOamMepMtvrTransactionId OBJECT-TYPE 1371 SYNTAX Unsigned32 (0..4294967295) 1372 MAX-ACCESS not-accessible 1373 STATUS current 1374 DESCRIPTION 1375 "Transaction identifier/sequence number returned by a 1376 previous 1377 transmit Multi-destination message command, indicating 1378 which MTVM's response is going to be returned." 1379 REFERENCE "RFC 7455 section 11" 1380 ::= { trillOamMtvrEntry 1 } 1382 trillOamMepMtvrReceiveOrder OBJECT-TYPE 1383 SYNTAX Unsigned32 (1..4294967295) 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "An index to distinguish among multiple MTVR with same 1388 MTVR Transaction Identifier field value. 1389 trillOamMepMtvrReceiveOrder are assigned sequentially 1390 from 1, 1391 in the order that the Multi-destination Tree Initiator 1392 received the MTVRs." 1393 REFERENCE "RFC 7455 section 11" 1394 ::= { trillOamMtvrEntry 2 } 1396 trillOamMepMtvrFlag OBJECT-TYPE 1397 SYNTAX Unsigned32 (0..15) 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "FCOI (TRILL OAM Message TLV) field value for a 1402 returned MTVR." 1403 REFERENCE "RFC 7455, 8.4.2" 1404 ::= { trillOamMtvrEntry 3 } 1406 trillOamMepMtvrErrorCode OBJECT-TYPE 1407 SYNTAX Unsigned32 (0..65535) 1408 MAX-ACCESS read-only 1409 STATUS current 1410 DESCRIPTION 1411 "Return Code and Return Sub code value for a returned MTVR." 1412 REFERENCE "RFC 7455, 8.4.2" 1413 ::= { trillOamMtvrEntry 4 } 1415 trillOamMepMtvrLastEgressId OBJECT-TYPE 1416 SYNTAX Unsigned32 (0..65535) 1417 MAX-ACCESS read-only 1418 STATUS current 1419 DESCRIPTION 1420 "An Integer field holding the Last Egress Identifier 1421 returned in the MTVR Upstream Rbridge Nickname TLV 1422 of the MTVR. 1424 The Last Egress Identifier identifies the 1425 Upstream Nickname." 1426 REFERENCE "RFC 7455 8.4.1" 1427 ::= { trillOamMtvrEntry 5 } 1429 trillOamMepMtvrIngress OBJECT-TYPE 1430 SYNTAX Dot1agCfmIngressActionFieldValue 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "The value returned in the Ingress Action Field of 1435 the MTVR. 1436 The value ingNoTlv(0) indicates that no 1437 Reply Ingress TLV was returned in the MTVM." 1438 REFERENCE "RFC 7455 11.2.3" 1439 ::= { trillOamMtvrEntry 6 } 1441 trillOamMepMtvrIngressMac OBJECT-TYPE 1442 SYNTAX MacAddress 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "MAC address returned in the ingress MAC address field." 1447 REFERENCE "RFC 7455 8.4.1" 1448 ::= { trillOamMtvrEntry 7 } 1450 trillOamMepMtvrIngressPortIdSubtype OBJECT-TYPE 1451 SYNTAX LldpPortIdSubtype 1452 MAX-ACCESS read-only 1453 STATUS current 1454 DESCRIPTION 1455 "Ingress Port ID. The format of this object is 1456 determined by 1457 the value of the trillOamMepMtvrIngressPortIdSubtype 1458 object." 1459 REFERENCE "RFC 7455 8.4.1" 1460 ::= { trillOamMtvrEntry 8 } 1462 trillOamMepMtvrIngressPortId OBJECT-TYPE 1463 SYNTAX LldpPortId 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "Ingress Port ID. The format of this object is determined by 1468 the value of the trillOamMepMtvrIngressPortId object." 1469 REFERENCE "RFC 7455 8.4.1" 1470 ::= { trillOamMtvrEntry 9 } 1472 trillOamMepMtvrEgress OBJECT-TYPE 1473 SYNTAX Dot1agCfmEgressActionFieldValue 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "The value returned in the Egress Action Field of the MTVR. 1478 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1479 returned in the MTVR." 1480 REFERENCE "RFC 7455 8.4.1" 1481 ::= { trillOamMtvrEntry 10 } 1483 trillOamMepMtvrEgressMac OBJECT-TYPE 1484 SYNTAX MacAddress 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "MAC address returned in the egress MAC address field." 1489 REFERENCE "RFC 7455 8.4.1" 1490 ::= { trillOamMtvrEntry 11 } 1492 trillOamMepMtvrEgressPortIdSubtype OBJECT-TYPE 1493 SYNTAX LldpPortIdSubtype 1494 MAX-ACCESS read-only 1495 STATUS current 1496 DESCRIPTION 1497 "Egress Port ID. The format of this object is determined by 1498 the value of the trillOamMepMtvrEgressPortIdSubtype object." 1499 REFERENCE "RFC 7455 8.4.1" 1500 ::= { trillOamMtvrEntry 12 } 1502 trillOamMepMtvrEgressPortId OBJECT-TYPE 1503 SYNTAX LldpPortId 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "Egress Port ID. The format of this object is determined by 1508 the value of the trillOamMepMtvrEgressPortId object." 1509 REFERENCE "RFC 7455 8.4.1" 1510 ::= { trillOamMtvrEntry 13 } 1512 trillOamMepMtvrChassisIdSubtype OBJECT-TYPE 1513 SYNTAX LldpChassisIdSubtype 1514 MAX-ACCESS read-only 1515 STATUS current 1516 DESCRIPTION 1517 "This object specifies the format of the Chassis ID returned 1518 in the Sender ID TLV of the MTVR, if any. This value is 1519 meaningless if the trillOamMepMtvrChassisId has a 1520 length of 0." 1521 REFERENCE "RFC 7455 8.4.1" 1522 ::= { trillOamMtvrEntry 14 } 1524 trillOamMepMtvrChassisId OBJECT-TYPE 1525 SYNTAX LldpChassisId 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "The Chassis ID returned in the Sender ID TLV of the MTVR, if 1530 any. The format of this object is determined by the 1531 value of the trillOamMepMtvrChassisIdSubtype object." 1532 REFERENCE "RFC 7455 8.4.1" 1533 ::= { trillOamMtvrEntry 15 } 1535 trillOamMepMtvrOrganizationSpecificTlv OBJECT-TYPE 1536 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "All Organization specific TLVs returned in the MTVR, if 1541 any. Includes all octets including and following the TLV 1542 Length field of each TLV, concatenated together." 1543 REFERENCE "RFC 7455 8.4.1" 1544 ::= { trillOamMtvrEntry 16 } 1546 trillOamMepMtvrNextHopNicknames OBJECT-TYPE 1547 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "Next hop Rbridge List TLV returned in the PTR, if 1552 any. Includes all octets including and following the TLV 1553 Length field of each TLV, concatenated together." 1554 REFERENCE "RFC 7455 8.4.3" 1555 ::= { trillOamMtvrEntry 17 } 1557 trillOamMepMtvrReceiverAvailability OBJECT-TYPE 1558 SYNTAX TruthValue 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "True value indicates that MTVR response contained 1563 Multicast receiver availability TLV." 1564 REFERENCE "RFC 7455 8.4.10" 1565 ::= { trillOamMtvrEntry 18 } 1567 trillOamMepMtvrReceiverCount OBJECT-TYPE 1568 SYNTAX TruthValue 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "Indicates the number of Multicast receivers available on 1573 responding RBridge on the VLAN specified by the 1574 diagnostic VLAN." 1575 REFERENCE "RFC 7455 8.4.10" 1576 ::= { trillOamMtvrEntry 19 } 1578 -- ***************************************************************** 1579 -- TRILL OAM MEP Database Table 1580 -- ***************************************************************** 1582 trillOamMepDbTable OBJECT-TYPE 1583 SYNTAX SEQUENCE OF TrillOamMepDbEntry 1584 MAX-ACCESS not-accessible 1585 STATUS current 1586 DESCRIPTION 1587 "This table is an extension of the dot1agCfmMepDbTable 1588 and rows 1589 are automatically added to or deleted from this table based 1590 upon row creation and destruction of the 1591 dot1agCfmMepDbTable." 1592 REFERENCE 1593 "RFC 7455" 1594 ::= { trillOamMep 5 } 1596 trillOamMepDbEntry OBJECT-TYPE 1597 SYNTAX TrillOamMepDbEntry 1598 MAX-ACCESS not-accessible 1599 STATUS current 1600 DESCRIPTION 1601 "The conceptual row of trillOamMepDbTable." 1602 AUGMENTS { 1603 dot1agCfmMepDbEntry 1604 } 1605 ::= { trillOamMepDbTable 1 } 1607 TrillOamMepDbEntry ::= SEQUENCE { 1608 trillOamMepDbFlowIndex Unsigned32, 1609 trillOamMepDbFlowEntropy OCTET STRING, 1610 trillOamMepDbFlowState Dot1agCfmRemoteMepState, 1611 trillOamMepDbFlowFailedOkTime TimeStamp, 1612 trillOamMepDbRbridgeName Unsigned32, 1613 trillOamMepDbLastGoodSeqNum Counter32 1614 } 1616 trillOamMepDbFlowIndex OBJECT-TYPE 1617 SYNTAX Unsigned32 (1..65535) 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "This object identifies the Flow. If Flow Identifier TLV 1622 is received 1623 than index received can also be used." 1624 REFERENCE "RFC 7455" 1625 ::= {trillOamMepDbEntry 1 } 1627 trillOamMepDbFlowEntropy OBJECT-TYPE 1628 SYNTAX OCTET STRING (SIZE (96)) 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "96 byte Flow Entropy." 1633 REFERENCE "RFC 7455 section 3." 1634 ::= {trillOamMepDbEntry 2 } 1636 trillOamMepDbFlowState OBJECT-TYPE 1637 SYNTAX Dot1agCfmRemoteMepState 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "The operational state of the remote MEP (flow based) 1642 IFF State machines. State Machine is running now per 1643 flow." 1644 REFERENCE "RFC 7455" 1645 ::= {trillOamMepDbEntry 3 } 1647 trillOamMepDbFlowFailedOkTime OBJECT-TYPE 1648 SYNTAX TimeStamp 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "The Time (sysUpTime) at which the Remote MEP Flow state 1653 machine last entered either the RMEP_FAILED or RMEP_OK 1654 state." 1655 REFERENCE "RFC 7455" 1656 ::= {trillOamMepDbEntry 4 } 1658 trillOamMepDbRbridgeName OBJECT-TYPE 1659 SYNTAX Unsigned32(0..65471) 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "Remote MEP Rbridge Nickname." 1665 REFERENCE "RFC 7455 RFC 6325 section 3" 1666 ::= {trillOamMepDbEntry 5 } 1668 trillOamMepDbLastGoodSeqNum OBJECT-TYPE 1669 SYNTAX Counter32 1670 MAX-ACCESS read-only 1671 STATUS current 1672 DESCRIPTION 1673 "Last Sequence Number received." 1674 REFERENCE "RFC 7455 13.1" 1675 ::= {trillOamMepDbEntry 6} 1677 -- ****************************************************************** 1678 -- TRILL OAM MIB NOTIFICATIONS (TRAPS) 1679 -- This notification is sent to management entity whenever a 1680 -- MEP loses/restores 1681 -- contact with its peer Flow Meps 1682 -- ****************************************************************** 1683 trillOamFaultAlarm NOTIFICATION-TYPE 1684 OBJECTS { trillOamMepDbFlowState } 1685 STATUS current 1686 DESCRIPTION 1687 "A MEP Flow has a persistent defect condition. 1688 A notification (fault alarm) is sent to the management 1689 entity with the OID of the Flow that has detected the fault. 1691 The management entity receiving the notification can identify 1692 the system from the network source address of the 1693 notification, and can identify the Flow reporting the defect 1694 by the indices in the OID of the 1695 trillOamMepFlowIndex, and trillOamFlowDefect 1696 variable in the notification: 1698 dot1agCfmMdIndex - Also the index of the MEP's 1699 Maintenance Domain table entry 1700 (dot1agCfmMdTable). 1701 dot1agCfmMaIndex - Also an index (with the MD table index) 1702 of the MEP's Maintenance Association 1703 network table entry 1704 (dot1agCfmMaNetTable), and (with the MD 1705 table index and component ID) of the 1706 MEP's MA component table entry 1707 (dot1agCfmMaCompTable). 1708 dot1agCfmMepIdentifier - MEP Identifier and final index 1709 into the MEP table (dot1agCfmMepTable). 1710 trillOamMepFlowCfgIndex - Index identifies 1711 indicates the specific Flow for 1712 the MEP" 1714 REFERENCE "RFC 7455" 1715 ::= { trillOamNotifications 1 } 1717 -- ****************************************************************** 1718 -- TRILL OAM MIB Module - Conformance Information 1719 -- ****************************************************************** 1721 trillOamMibCompliances OBJECT IDENTIFIER 1722 ::= { trillOamMibConformance 1 } 1724 trillOamMibGroups OBJECT IDENTIFIER 1725 ::= { trillOamMibConformance 2 } 1727 -- ****************************************************************** 1728 -- TRILL OAM MIB Units of conformance 1729 -- ****************************************************************** 1731 trillOamMepMandatoryGroup OBJECT-GROUP 1732 OBJECTS { 1733 trillOamMepRName, 1734 trillOamMepNextPtmTId, 1735 trillOamMepNextMtvmTId, 1736 trillOamMepPtrIn, 1737 trillOamMepPtrInOutofOrder, 1738 trillOamMepPtrOut, 1739 trillOamMepMtvrIn, 1740 trillOamMepMtvrInOutofOrder, 1741 trillOamMepMtvrOut, 1742 trillOamMepTxLbmDestRName, 1743 trillOamMepTxLbmHC, 1744 trillOamMepTxLbmReplyModeOob, 1745 trillOamMepTransmitLbmReplyIp, 1746 trillOamMepTxLbmFlowEntropy, 1747 trillOamMepTxPtmDestRName, 1748 trillOamMepTxPtmHC, 1749 trillOamMepTxPtmReplyModeOob, 1750 trillOamMepTransmitPtmReplyIp, 1751 trillOamMepTxPtmFlowEntropy, 1752 trillOamMepTxPtmStatus, 1753 trillOamMepTxPtmResultOK, 1754 trillOamMepTxPtmMessages, 1755 trillOamMepTxPtmSeqNumber, 1756 trillOamMepTxMtvmTree, 1757 trillOamMepTxMtvmHC, 1758 trillOamMepTxMtvmReplyModeOob, 1759 trillOamMepTransmitMtvmReplyIp, 1760 trillOamMepTxMtvmFlowEntropy, 1761 trillOamMepTxMtvmStatus, 1762 trillOamMepTxMtvmResultOK, 1763 trillOamMepTxMtvmMessages, 1764 trillOamMepTxMtvmSeqNumber, 1765 trillOamMepTxMtvmScopeList, 1766 trillOamMepDiscontinuityTime 1767 } 1768 STATUS current 1769 DESCRIPTION 1770 "Mandatory objects for the TRILL OAM MEP group." 1771 ::= { trillOamMibGroups 1 } 1773 trillOamMepFlowCfgTableGroup OBJECT-GROUP 1774 OBJECTS { 1775 trillOamMepFlowCfgFlowEntropy, 1776 trillOamMepFlowCfgDestRName, 1777 trillOamMepFlowCfgFlowHC, 1778 trillOamMepFlowCfgRowStatus 1779 } 1780 STATUS current 1781 DESCRIPTION 1782 "Trill OAM MEP Flow Configuration objects group." 1783 ::= { trillOamMibGroups 2 } 1785 trillOamPtrTableGroup OBJECT-GROUP 1786 OBJECTS { 1787 trillOamMepPtrHC, 1788 trillOamMepPtrFlag, 1789 trillOamMepPtrErrorCode, 1790 trillOamMepPtrTerminalMep, 1791 trillOamMepPtrLastEgressId, 1792 trillOamMepPtrIngress, 1793 trillOamMepPtrIngressMac, 1794 trillOamMepPtrIngressPortIdSubtype, 1795 trillOamMepPtrIngressPortId, 1796 trillOamMepPtrEgress, 1797 trillOamMepPtrEgressMac, 1798 trillOamMepPtrEgressPortIdSubtype, 1799 trillOamMepPtrEgressPortId, 1800 trillOamMepPtrChassisIdSubtype, 1801 trillOamMepPtrChassisId, 1802 trillOamMepPtrOrganizationSpecificTlv, 1803 trillOamMepPtrNextHopNicknames 1804 } 1805 STATUS current 1806 DESCRIPTION 1807 "Trill OAM MEP PTR objects group." 1808 ::= { trillOamMibGroups 3 } 1810 trillOamMtvrTableGroup OBJECT-GROUP 1811 OBJECTS { 1812 trillOamMepMtvrFlag, 1813 trillOamMepMtvrErrorCode, 1814 trillOamMepMtvrLastEgressId, 1815 trillOamMepMtvrIngress, 1816 trillOamMepMtvrIngressMac, 1817 trillOamMepMtvrIngressPortIdSubtype, 1818 trillOamMepMtvrIngressPortId, 1819 trillOamMepMtvrEgress, 1820 trillOamMepMtvrEgressMac, 1821 trillOamMepMtvrEgressPortIdSubtype, 1822 trillOamMepMtvrEgressPortId, 1823 trillOamMepMtvrChassisIdSubtype, 1824 trillOamMepMtvrChassisId, 1825 trillOamMepMtvrOrganizationSpecificTlv, 1826 trillOamMepMtvrNextHopNicknames, 1827 trillOamMepMtvrReceiverAvailability, 1828 trillOamMepMtvrReceiverCount 1829 } 1830 STATUS current 1831 DESCRIPTION 1832 "Trill OAM MEP MTVR objects group." 1833 ::= { trillOamMibGroups 4 } 1835 trillOamMepDbGroup OBJECT-GROUP 1836 OBJECTS { 1837 trillOamMepDbFlowIndex, 1838 trillOamMepDbFlowEntropy, 1839 trillOamMepDbFlowState, 1840 trillOamMepDbFlowFailedOkTime, 1841 trillOamMepDbRbridgeName, 1842 trillOamMepDbLastGoodSeqNum 1843 } 1845 STATUS current 1846 DESCRIPTION 1847 "Trill OAM MEP DB objects group." 1848 ::= { trillOamMibGroups 5 } 1850 trillOamNotificationGroup NOTIFICATION-GROUP 1851 NOTIFICATIONS { trillOamFaultAlarm } 1852 STATUS current 1853 DESCRIPTION 1854 "A collection of objects describing notifications(traps)." 1855 ::= { trillOamMibGroups 6 } 1857 -- ****************************************************************** 1858 -- TRILL OAM MIB Module Compliance statements 1859 -- ****************************************************************** 1861 trillOamMibCompliance MODULE-COMPLIANCE 1862 STATUS current 1863 DESCRIPTION 1864 "The compliance statement for the TRILL OAM MIB." 1865 MODULE -- this module 1866 MANDATORY-GROUPS { 1867 trillOamMepMandatoryGroup, 1868 trillOamMepFlowCfgTableGroup, 1869 trillOamPtrTableGroup, 1870 trillOamMtvrTableGroup, 1871 trillOamMepDbGroup, 1872 trillOamNotificationGroup 1873 } 1874 ::= { trillOamMibCompliances 1 } 1876 -- Compliance requirement for read-only implementation. 1878 trillOamMibReadOnlyCompliance MODULE-COMPLIANCE 1879 STATUS current 1880 DESCRIPTION 1881 "Compliance requirement for implementation that only 1882 provide read-only support for TRILL-OAM-MIB. 1883 Such devices can be monitored but cannot be configured 1884 using this MIB module." 1885 MODULE -- this module 1886 MANDATORY-GROUPS { 1887 trillOamMepMandatoryGroup, 1888 trillOamMepFlowCfgTableGroup, 1889 trillOamPtrTableGroup, 1890 trillOamMtvrTableGroup, 1891 trillOamMepDbGroup, 1892 trillOamNotificationGroup 1893 } 1894 -- trillOamMepTable 1896 OBJECT trillOamMepTxLbmDestRName 1897 MIN-ACCESS read-only 1898 DESCRIPTION 1899 "Write access is not required." 1901 OBJECT trillOamMepTxLbmHC 1902 MIN-ACCESS read-only 1903 DESCRIPTION 1904 "Write access is not required." 1906 OBJECT trillOamMepTxLbmReplyModeOob 1907 MIN-ACCESS read-only 1908 DESCRIPTION 1909 "Write access is not required." 1911 OBJECT trillOamMepTransmitLbmReplyIp 1912 MIN-ACCESS read-only 1913 DESCRIPTION 1914 "Write access is not required." 1916 OBJECT trillOamMepTxLbmFlowEntropy 1917 MIN-ACCESS read-only 1918 DESCRIPTION 1919 "Write access is not required." 1921 OBJECT trillOamMepTxPtmDestRName 1922 MIN-ACCESS read-only 1923 DESCRIPTION 1924 "Write access is not required." 1926 OBJECT trillOamMepTxPtmHC 1927 MIN-ACCESS read-only 1928 DESCRIPTION 1929 "Write access is not required." 1931 OBJECT trillOamMepTxPtmReplyModeOob 1932 MIN-ACCESS read-only 1933 DESCRIPTION 1934 "Write access is not required." 1936 OBJECT trillOamMepTransmitPtmReplyIp 1937 MIN-ACCESS read-only 1938 DESCRIPTION 1939 "Write access is not required." 1941 OBJECT trillOamMepTxPtmFlowEntropy 1942 MIN-ACCESS read-only 1943 DESCRIPTION 1944 "Write access is not required." 1946 OBJECT trillOamMepTxPtmStatus 1947 MIN-ACCESS read-only 1948 DESCRIPTION 1949 "Write access is not required." 1951 OBJECT trillOamMepTxPtmResultOK 1952 MIN-ACCESS read-only 1953 DESCRIPTION 1954 "Write access is not required." 1956 OBJECT trillOamMepTxPtmMessages 1957 MIN-ACCESS read-only 1958 DESCRIPTION 1959 "Write access is not required." 1961 OBJECT trillOamMepTxPtmSeqNumber 1962 MIN-ACCESS read-only 1963 DESCRIPTION 1964 "Write access is not required." 1966 OBJECT trillOamMepTxMtvmTree 1967 MIN-ACCESS read-only 1968 DESCRIPTION 1969 "Write access is not required." 1971 OBJECT trillOamMepTxMtvmHC 1972 MIN-ACCESS read-only 1973 DESCRIPTION 1974 "Write access is not required." 1976 OBJECT trillOamMepTxMtvmReplyModeOob 1977 MIN-ACCESS read-only 1978 DESCRIPTION 1979 "Write access is not required." 1981 OBJECT trillOamMepTransmitMtvmReplyIp 1982 MIN-ACCESS read-only 1983 DESCRIPTION 1984 "Write access is not required." 1986 OBJECT trillOamMepTxMtvmFlowEntropy 1987 MIN-ACCESS read-only 1988 DESCRIPTION 1989 "Write access is not required." 1991 OBJECT trillOamMepTxMtvmStatus 1992 MIN-ACCESS read-only 1993 DESCRIPTION 1994 "Write access is not required." 1996 OBJECT trillOamMepTxMtvmResultOK 1997 MIN-ACCESS read-only 1998 DESCRIPTION 1999 "Write access is not required." 2001 OBJECT trillOamMepTxMtvmMessages 2002 MIN-ACCESS read-only 2003 DESCRIPTION 2004 "Write access is not required." 2006 OBJECT trillOamMepTxMtvmSeqNumber 2007 MIN-ACCESS read-only 2008 DESCRIPTION 2009 "Write access is not required." 2011 OBJECT trillOamMepTxMtvmScopeList 2012 MIN-ACCESS read-only 2013 DESCRIPTION 2014 "Write access is not required." 2016 -- trillOamMepFlowCfgTable 2018 OBJECT trillOamMepFlowCfgFlowEntropy 2019 MIN-ACCESS read-only 2020 DESCRIPTION 2021 "Write access is not required." 2023 OBJECT trillOamMepFlowCfgDestRName 2024 MIN-ACCESS read-only 2025 DESCRIPTION 2026 "Write access is not required." 2028 OBJECT trillOamMepFlowCfgFlowHC 2029 MIN-ACCESS read-only 2030 DESCRIPTION 2031 "Write access is not required." 2033 OBJECT trillOamMepFlowCfgRowStatus 2034 MIN-ACCESS read-only 2035 DESCRIPTION 2036 "Write access is not required." 2038 ::= { trillOamMibCompliances 2 } 2040 END 2042 8. Security Considerations 2044 This MIB relates to a system that will provide network connectivity 2045 and packet forwarding services. As such, improper manipulation of the 2046 objects represented by this MIB may result in denial of service to a 2047 large number of end-users. 2049 There are number of management objects defined in this MIB module 2050 with a MAX-ACCESS clause of read-create. Such objects may be 2051 considered sensitive or vulnerable in some network environments. The 2052 support for SET operations in a non-secure environment without proper 2053 protection can have negative effect on sensitivity/vulnerability: 2055 The following table and objects in the TRILL-OAM-MIB can be 2056 manipulated to to interfere with the operation of RBridges by causing 2057 cpu spike: 2059 o trillOamMepTransmitLbmReplyIp allows reply of Loopback message to 2060 be transmitted to Ip address in the TLV and thus allowing replies to 2061 be sent to any system or single single system to cause Denial of 2062 Service. 2064 o trillOamMepTransmitPtmReplyIp allows reply of Path Trace message to 2065 be transmitted to Ip address in the TLV and thus allowing replies to 2066 be sent to any system or single single system to cause Denial of 2067 Service. 2069 o trillOamMepTxPtmMessages allows generation of Ptm Messages and can 2070 be used to generate lots of cpu driven traffic. 2072 o trillOamMepTransmitMtvmReplyIp allows reply of Mtv message to be 2073 transmitted to Ip address in the TLV and thus allowing replies to be 2074 sent to any system or single single system to cause Denial of 2075 Service. 2077 o trillOamMepTxMtvmMessages allows generation of Mtv Messages and can 2078 be used to generate lots of cpu driven traffic. 2080 Some of the readable objects in this MIB module (i.e., objects with a 2081 MAX-ACCESS other than not-accessible) may be considered sensitive or 2082 vulnerable in some network environments. It is thus important to 2083 control GET and/or NOTIFY access to these objects and possibly to 2084 encrypt the values of these objects when sending them over the 2085 network via SNMP. For example, Path trace message expose unicast 2086 topology of network and Multi-destination Tree verification message 2087 expose multicast tree topology of network and this information should 2088 not be available to all users of the network. 2090 SNMP version prior to SNMPv3 did not include adequate security. Even 2091 if the network itself is secure(for example by using IPsec), there is 2092 no control as to who on the secure network is allowed to access and 2093 GET/SET (read/change/create/delete) the objects in this MIB module. 2095 Implementation should provide the security features described by 2096 SNMPv3 framework (see [RFC3410]), and implementations claiming 2097 compliance to the SNMPv3 standard MUST include full support for 2098 authentication and privacy via the User-based Security Model 2099 (USM)[RFC3414] with the AES cipher algorithm [RFC3826]. 2100 Implementations MAY also provide support for the Transport Security 2101 Model (TSM) [RFC5591] in combination with a secure transport such as 2102 SSH [RFC5592] or TLS/DTLS [RFC6353]. 2104 Further, deployment of SNMP version prior to SNMPv3 is NOT 2105 RECOMMENDED. Instead, deployment of SNMPv3 with cryptographic 2106 security enabled is RECOMMENDED. It is then a customer/operator 2107 responsibility to ensure that the SNMP entity giving access to an 2108 instance of this MIB module is properly configured to give only those 2109 principals (users) that have legitimate rights to indeed GET or SET 2110 (change/create/delete) them access to the objects. 2112 9. IANA Considerations 2114 The MIB module in this document uses the following IANA-assigned 2115 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2117 Descriptor OBJECT IDENTIFIER value 2118 ---------------------------------------- 2119 trillOamMIB { mib-2 xxx } 2121 Editor's Note (to be removed prior to publication): the IANA is 2122 requested to assign a value for "xxx" under the 'mib-2' subtree and 2123 to record the assignment in the SMI Numbers registry. When the 2124 assignment has been made, the RFC Editor is asked to replace "XXX" 2125 (here and in the MIB module) with the assigned value and to remove 2126 this note. 2128 10. References 2129 10.1. Normative References 2131 [RFC2119] Bradner, S., "Key words for use in RFCs to 2132 Indicate Requirement Levels", BCP 14, RFC 2119, March 2133 1997. 2135 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2136 Schoenwaelder, Ed., "Structure of Management Information 2137 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2139 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2140 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2141 58, RFC 2579, April 1999. 2143 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2144 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2145 STD 58, RFC 2580, April 1999. 2147 [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, 2148 S., and A. Ghanwani, "Routing Bridges (RBridges): Base 2149 Protocol Specification", RFC 6325, July 2011. 2151 [RFC7172] Eastlake 3rd, D., Zhang, M., Agarwal, P., 2152 Perlman, R., and D. Dutt, "Transparent Interconnection of 2153 Lots of Links (TRILL): Fine-Grained Labeling", RFC 7172, 2154 May 2014. 2156 [RFC7455] Senevirathne, T., et.al., "Transparent 2157 Interconnection of Lots of Links (TRILL): Fault 2158 Management", March 2015. 2160 [LLDP-MIB] IEEE, 2161 http://www.ieee802.org/1/files/public/MIBs/LLDP-MIB- 2162 200505060000Z.txt 2164 [802.1Q] IEEE, "IEEE Standard for Local and metropolitan 2165 area networks - Media Access Control (MAC) Bridges and 2166 Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 2167 31 August 2011. 2169 10.2. Informative References 2171 [802.1Q] IEEE, "IEEE Standard for Local and metropolitan 2172 area networks - Media Access Control (MAC) Bridges and 2173 Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 2174 31 August 2011. 2176 [RFC3410] Case, J., Mundy, R., Partain, D., and B.Stewart, 2177 "Introduction and Applicability Statements for Internet- 2178 Standard Management Framework", RFC 3410, December 2002. 2180 [RFC6905] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., 2181 and R. Watve, "Requirements for Operations, 2182 Administration, and Maintenance (OAM) in Transparent 2183 Interconnection of Lots of Links (TRILL)", RFC 6905, March 2184 2013. 2186 [RFC7174] Salam, S., Senevirathne, T., Aldrin, S., and D. 2187 Eastlake 3rd, "Transparent Interconnection of Lots of 2188 Links (TRILL) Operations, Administration, and Maintenance 2189 (OAM) Framework", RFC 7174, May 2014. 2191 11. Acknowledgments 2193 We wish to thank members of the IETF TRILL WG, and mib-doctor for 2194 their comments and suggestions. Detailed comments were provided by 2195 Sam Aldrin, Donald Eastlake, Tom Taylor, and Harrie Hazewinkel. 2197 12. Copyright and Disclaimer 2198 Copyright (c) 2015 IETF Trust and the persons identified as authors 2199 of the code. All rights reserved. Redistribution and use in source 2200 and binary forms, with or without modification, is permitted pursuant 2201 to, and subject to the license terms contained in, the Simplified BSD 2202 License set forth in Section 4.c of the IETF Trust's Legal Provisions 2203 Relating to IETF Documents (http://trustee.ietf.org/license-info). 2205 Copyright (c) 2015 IETF Trust and the persons identified as authors 2206 of the code. All rights reserved. Redistribution and use in source 2207 and binary forms, with or without modification, are permitted 2208 provided that the following conditions are met: 2210 o Redistributions of source code must retain the above copyright 2211 notice, this list of conditions and the following disclaimer. 2213 o Redistributions in binary form must reproduce the above 2214 copyright notice, this list of conditions and the following 2215 disclaimer in the documentation and/or other materials provided 2216 with the distribution. 2218 o Neither the name of Internet Society, IETF or IETF Trust, nor 2219 the names of specific contributors, may be used to endorse or 2220 promote products derived from this software without specific prior 2221 written permission. 2223 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2224 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2225 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2226 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2227 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2228 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2229 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2230 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2231 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2232 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2233 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2235 Authors' Addresses 2237 Deepak Kumar 2238 Cisco 2239 510 McCarthy Blvd, 2240 Milpitas, CA 95035, USA 2241 Phone : +1 408-853-9760 2242 Email: dekumar@cisco.com 2244 Samer Salam 2245 Cisco 2246 595 Burrard St. Suite 2123 2247 Vancouver, BC V7X 1J1, Canada 2248 Email: ssalam@cisco.com 2250 Tissa Senevirathne 2251 Consultant 2252 Email: tsenevir@gmail.com