idnits 2.17.1 draft-ietf-trill-oam-mib-10.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 712 has weird spacing: '...d reply is tr...' == Line 723 has weird spacing: '...d. The maxim...' -- The document date (October 7, 2015) is 3123 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 2213, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MIB' Summary: 0 errors (**), 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 7, 2015 9 TRILL OAM MIB 10 draft-ietf-trill-oam-mib-10.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 March 30, 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 RFC 7455. 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 RFC 7455 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 RFC6325 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 forIPv6 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 RFC6325 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 745 Initiator State Machine or a MIB manager to 746 indicate that another PTM is being transmitted. 747 This is Reset to false by the MEP Initiator 748 State Machine. 749 The PTM managed objects in the MEP table are used 750 in a manner similar to that described for LBM 751 transmission in dot1agCfmMepTable. As per RFC7455 752 section 10, Operation of the Path Trace Message is 753 identical to the Loopback Message except that it is 754 first transmitted with a TRILL Header Hop count 755 field value of 1 and then retransmitted with an 756 incrementeing Hop count until a response is received 757 from the destination RBridge, or the Hop Count 758 reaches a configured maximum value. 759 trillOamMepTxPtmStatus Status is reset to FALSE 760 by initiator when last PTM is transmitted." 761 REFERENCE "RFC 7455 section 10" 762 DEFVAL { false } 763 ::= { trillOamMepEntry 20 } 765 trillOamMepTxPtmResultOK OBJECT-TYPE 766 SYNTAX TruthValue 767 MAX-ACCESS read-create 768 STATUS current 769 DESCRIPTION 770 "Indicates the following results of the operation: 771 - true The Path Trace Message(s) will be (or has been) 772 sent. 773 - false The Path Trace Message(s) will not be sent." 774 REFERENCE "RFC 7455 section 10" 775 DEFVAL { true } 776 ::= { trillOamMepEntry 21 } 778 trillOamMepTxPtmSeqNumber OBJECT-TYPE 779 SYNTAX Unsigned32 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "The Path Trace Transaction Identifier of the first 784 PTM (to be) sent. The value returned is 785 undefined if trillOamMepTxPtmResultOK is false." 786 REFERENCE "RFC 7455 section 10" 787 ::= { trillOamMepEntry 22 } 789 trillOamMepTxPtmMessages OBJECT-TYPE 790 SYNTAX Integer32 (1..1024) 791 MAX-ACCESS read-create 792 STATUS current 793 DESCRIPTION 794 "The number of Path Trace messages to be transmitted. 795 As per RFC 7455 section 10, the first Path Trace 796 Message is transmitted with a Hop count of 1 and an 797 RBridge may continue to retransmit the request at 798 periodic intervals with an incrementing Hop Count 799 until a response is received from the destination 800 Rbridge, or the Hop Count reaches a configured 801 maximum value. The event of the Destination 802 response being received or the Hop count reaching 803 its maximum is treated as a single Counter 804 increment of this object." 805 REFERENCE "RFC 7455 section 10" 806 ::= { trillOamMepEntry 23 } 808 trillOamMepTxMtvmTree OBJECT-TYPE 809 SYNTAX Unsigned32 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "The Multi-destination Tree identifier for, as 814 defined in RFC6325, for a MTVM." 815 ::= { trillOamMepEntry 24 } 817 trillOamMepTxMtvmHC OBJECT-TYPE 818 SYNTAX Unsigned32(1..63) 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "The Hop Count field to be transmitted. 823 " 824 REFERENCE "RFC 7455 section 3, RFC 6325 section 3" 825 ::= { trillOamMepEntry 25 } 827 trillOamMepTxMtvmReplyModeOob OBJECT-TYPE 828 SYNTAX TruthValue 829 MAX-ACCESS read-create 830 STATUS current 831 DESCRIPTION 832 "True Indicates that the reply to a MTVM is out of 833 band and the out of band IP Address TLV is where the 834 reply is to be transmitted. 835 False indicates that an in band reply is transmitted." 836 REFERENCE "RFC 7455 section 11" 837 ::= { trillOamMepEntry 26 } 839 trillOamMepTransmitMtvmReplyIp OBJECT-TYPE 840 SYNTAX OCTET STRING (SIZE (4..16)) 841 MAX-ACCESS read-create 842 STATUS current 843 DESCRIPTION 844 "IP address for an out of band IP Address TLV that is 845 to be transmitted. The Maximum length for IPv6 is 16 846 OCTET and IPv4 is 4 OCTET." 847 REFERENCE "RFC 7455 section 11" 848 ::= { trillOamMepEntry 27 } 850 trillOamMepTxMtvmFlowEntropy OBJECT-TYPE 851 SYNTAX OCTET STRING (SIZE (96)) 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "96 Byte Flow Entropy, as defined in RFC 7455, to be 856 transmitted." 857 REFERENCE "RFC 7455 section 3" 858 ::= { trillOamMepEntry 28 } 860 trillOamMepTxMtvmStatus OBJECT-TYPE 861 SYNTAX TruthValue 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "A Boolean flag set to true by the MEP Multi Destination 866 Initiator State Machine or a MIB manager to indicate 867 that another MTVM is being transmitted. 868 Reset to false by the MEP Initiator State Machine. 869 The MTVM managed objects in the MEP table are used 870 in a manner similar to that described for LBM 871 transmission in dot1agCfmMepTable. As per RFC7455 872 section 11, operation of the MTVM Message is 873 identical to the Loopback Message except that it is 874 first transmitted with a TRILL Header Hop count 875 field value of 1 and it is retransmitted incrementing 876 the Hop count until a response is received from the 877 destination RBridge or the Hop Count reaches a 878 configured maximum value. trillOamMepTxMtvmStatus 879 Status is reset to FALSE by the initiator when last 880 MTVM is transmitted." 881 REFERENCE "RFC 7455 section 11" 882 DEFVAL { false } 883 ::= { trillOamMepEntry 29 } 885 trillOamMepTxMtvmResultOK OBJECT-TYPE 886 SYNTAX TruthValue 887 MAX-ACCESS read-create 888 STATUS current 889 DESCRIPTION 890 "Indicates the result of the operation in 891 the following way: 892 - true The Multi-destination Message(s) will be 893 (or has been) sent. 894 - false The Multi-destination Message(s) will not be sent." 895 REFERENCE "RFC 7455 section 11" 896 DEFVAL { true } 897 ::= { trillOamMepEntry 30 } 899 trillOamMepTxMtvmMessages OBJECT-TYPE 900 SYNTAX Integer32 (1..1024) 901 MAX-ACCESS read-create 902 STATUS current 903 DESCRIPTION 904 "The number of Multi Destination messages to be transmitted. 905 The Rbridge transmit the Multi Destination message 906 incrementing the session Identification Number at periodic 907 interval until this count expires." 908 REFERENCE "RFC 7455 section 11" 909 ::= { trillOamMepEntry 31 } 911 trillOamMepTxMtvmSeqNumber OBJECT-TYPE 912 SYNTAX Unsigned32 913 MAX-ACCESS read-create 914 STATUS current 915 DESCRIPTION 916 "The Multi-destination Transaction Identifier of the 917 first MTVM (to be) 918 sent. The value returned is undefined if 919 trillOamMepTxMtvmResultOK is false." 920 REFERENCE "RFC 7455 section 11" 921 ::= { trillOamMepEntry 32 } 923 trillOamMepTxMtvmScopeList OBJECT-TYPE 924 SYNTAX OCTET STRING 925 MAX-ACCESS read-create 926 STATUS current 927 DESCRIPTION 928 "The Multi-destination Rbridge Scope list, which 929 requires 2 octets per Rbridge." 930 REFERENCE "RFC 7455 section 11" 931 ::= { trillOamMepEntry 33 } 933 trillOamMepDiscontinuityTime OBJECT-TYPE 934 SYNTAX TimeStamp 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "Snapshot of the value of the sysUpTime object at the 939 beginning of the latest period of continuity of the 940 statistical counters associated with this MEP." 941 ::= { trillOamMepEntry 34 } 943 -- ***************************************************************** 944 -- TRILL OAM Tx Measurement Configuration Table 945 -- ***************************************************************** 947 trillOamMepFlowCfgTable OBJECT-TYPE 948 SYNTAX SEQUENCE OF TrillOamMepFlowCfgEntry 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "This table includes configuration objects and operations 953 for the TRILL OAM RFC 7455. 955 Each row in the table represents a Flow configuration 956 Entry for the defined MEP. This table uses four indices. 957 The first three indices are the indices of the Maintenance 958 Domain, MaNet, and MEP tables. The fourth index is the 959 specific flow configuration Entry on the selected MEP. 961 Some writable objects in this table are only applicable in 962 certain cases (as described under each object), and 963 attempts to write values for them in other cases 964 will be ignored." 965 REFERENCE "RFC 7455" 966 ::= { trillOamMep 2 } 968 trillOamMepFlowCfgEntry OBJECT-TYPE 969 SYNTAX TrillOamMepFlowCfgEntry 970 MAX-ACCESS not-accessible 971 STATUS current 972 DESCRIPTION 973 "The conceptual row of trillOamMepFlowCfgTable." 974 INDEX { 975 dot1agCfmMdIndex, 976 dot1agCfmMaIndex, 977 dot1agCfmMepIdentifier, 978 trillOamMepFlowCfgIndex 979 } 980 ::= { trillOamMepFlowCfgTable 1 } 982 TrillOamMepFlowCfgEntry ::= SEQUENCE { 983 trillOamMepFlowCfgIndex Unsigned32, 984 trillOamMepFlowCfgFlowEntropy OCTET STRING, 985 trillOamMepFlowCfgDestRName Unsigned32, 986 trillOamMepFlowCfgFlowHC Unsigned32, 987 trillOamMepFlowCfgRowStatus RowStatus 988 } 990 trillOamMepFlowCfgIndex OBJECT-TYPE 991 SYNTAX Unsigned32 (1..65535) 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "An index to the TRILL OAM MEP Flow Configuration table which 996 indicates the specific Flow for the MEP. 998 The index is never reused for other flow sessions on the 999 same MEP while this session is active. 1000 The index value keeps increasing until it wraps to 0. 1001 This value can also be used in Flow-identifier TLV RFC 7455." 1002 REFERENCE "RFC 7455" 1003 ::= { trillOamMepFlowCfgEntry 1 } 1005 trillOamMepFlowCfgFlowEntropy OBJECT-TYPE 1006 SYNTAX OCTET STRING (SIZE (96)) 1007 MAX-ACCESS read-create 1008 STATUS current 1009 DESCRIPTION 1010 "This is 96 byte of Flow Entropy as described in 1011 TRILL OAM RFC 7455." 1012 REFERENCE "RFC 7455 section 3" 1013 ::= { trillOamMepFlowCfgEntry 2 } 1015 trillOamMepFlowCfgDestRName OBJECT-TYPE 1016 SYNTAX Unsigned32 (0..65471) 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "The Target Destination Rbridge NickName Field, as 1021 defined in RFC 6325 section 3.7, to be transmitted." 1022 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1023 ::= { trillOamMepFlowCfgEntry 3 } 1025 trillOamMepFlowCfgFlowHC OBJECT-TYPE 1026 SYNTAX Unsigned32 (1..63) 1027 MAX-ACCESS read-create 1028 STATUS current 1029 DESCRIPTION 1030 "The Time to Live field to be transmitted." 1031 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1032 ::= { trillOamMepFlowCfgEntry 4 } 1034 trillOamMepFlowCfgRowStatus OBJECT-TYPE 1035 SYNTAX RowStatus 1036 MAX-ACCESS read-create 1037 STATUS current 1038 DESCRIPTION 1039 "The status of the row. 1041 The writable columns in a row cannot be changed if the row 1042 is active. All columns MUST have a valid value before a row 1043 can be activated." 1044 ::= { trillOamMepFlowCfgEntry 5 } 1046 -- ****************************************************************** 1047 -- TRILL OAM Path Trace Reply Table 1048 -- ****************************************************************** 1050 trillOamPtrTable OBJECT-TYPE 1051 SYNTAX SEQUENCE OF TrillOamPtrEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "This table includes Path Trace Reply objects and 1056 operations for TRILL OAM as described in RFC 7455. 1058 Each row in the table represents a Path Trace Reply Entry for 1059 the defined MEP and Transaction. This table uses four 1060 indices. The first three indices are the indices of the 1061 Maintenance Domain, 1062 MaNet, and MEP tables. The fourth index is the specific 1063 Transaction Identifier on the selected MEP. 1065 Some writable objects in this table are only applicable in 1066 certain cases (as described under each object), 1067 and attempts to 1068 write values for them in other cases will be ignored." 1069 REFERENCE "RFC 7455" 1070 ::= { trillOamMep 3 } 1072 trillOamPtrEntry OBJECT-TYPE 1073 SYNTAX TrillOamPtrEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "The conceptual row of trillOamPtrTable." 1078 INDEX { 1079 dot1agCfmMdIndex, 1080 dot1agCfmMaIndex, 1081 dot1agCfmMepIdentifier, 1082 trillOamMepPtrTransactionId 1083 } 1084 ::= { trillOamPtrTable 1 } 1086 TrillOamPtrEntry ::= SEQUENCE { 1087 trillOamMepPtrTransactionId Unsigned32, 1088 trillOamMepPtrHC Unsigned32, 1089 trillOamMepPtrFlag Unsigned32, 1090 trillOamMepPtrErrorCode Unsigned32, 1091 trillOamMepPtrTerminalMep TruthValue, 1092 trillOamMepPtrLastEgressId Unsigned32, 1093 trillOamMepPtrIngress Dot1agCfmIngressActionFieldValue, 1094 trillOamMepPtrIngressMac MacAddress, 1095 trillOamMepPtrIngressPortIdSubtype LldpPortIdSubtype, 1096 trillOamMepPtrIngressPortId LldpPortId, 1097 trillOamMepPtrEgress Dot1agCfmEgressActionFieldValue, 1098 trillOamMepPtrEgressMac MacAddress, 1099 trillOamMepPtrEgressPortIdSubtype LldpPortIdSubtype, 1100 trillOamMepPtrEgressPortId LldpPortId, 1101 trillOamMepPtrChassisIdSubtype LldpChassisIdSubtype, 1102 trillOamMepPtrChassisId LldpChassisId, 1103 trillOamMepPtrOrganizationSpecificTlv OCTET STRING, 1104 trillOamMepPtrNextHopNicknames OCTET STRING 1105 } 1107 trillOamMepPtrTransactionId OBJECT-TYPE 1108 SYNTAX Unsigned32 (0..4294967295) 1109 MAX-ACCESS not-accessible 1110 STATUS current 1111 DESCRIPTION 1112 "Transaction identifier/sequence number returned by a 1113 previous transmit path trace message command, 1114 indicating which PTM's response is going to be returned." 1115 REFERENCE "RFC 7455 section 10" 1116 ::= { trillOamPtrEntry 1 } 1118 trillOamMepPtrHC OBJECT-TYPE 1119 SYNTAX Unsigned32 (1..63) 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "Hop Count field value for a returned PTR." 1124 REFERENCE "RFC 7455" 1125 ::= { trillOamPtrEntry 2 } 1127 trillOamMepPtrFlag OBJECT-TYPE 1128 SYNTAX Unsigned32 (0..15) 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "FCOI (TRILL OAM Message TLV) field value for a 1133 returned PTR." 1134 REFERENCE "RFC 7455, 8.4.3" 1135 ::= { trillOamPtrEntry 3 } 1137 trillOamMepPtrErrorCode OBJECT-TYPE 1138 SYNTAX Unsigned32 (0..65535) 1139 MAX-ACCESS read-only 1140 STATUS current 1141 DESCRIPTION 1142 "Return Code and Return Sub code value for a returned PTR." 1143 REFERENCE "RFC 7455, 8.4.3" 1144 ::= { trillOamPtrEntry 4 } 1146 trillOamMepPtrTerminalMep OBJECT-TYPE 1147 SYNTAX TruthValue 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "A boolean value stating whether the forwarded PTM reached a 1152 MEP enclosing its MA, as returned in the Terminal MEP flag of 1153 the Flags field." 1154 REFERENCE "RFC 7455" 1155 ::= { trillOamPtrEntry 5 } 1157 trillOamMepPtrLastEgressId OBJECT-TYPE 1158 SYNTAX Unsigned32 (0..65535) 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 "An Integer field holding the Last Egress Identifier returned 1163 in the PTR Upstream Rbridge nickname TLV of the PTR. 1164 The Last Egress Identifier identifies the Upstream Nickname." 1165 REFERENCE "RFC 7455 8.4.1" 1166 ::= { trillOamPtrEntry 6 } 1168 trillOamMepPtrIngress OBJECT-TYPE 1169 SYNTAX Dot1agCfmIngressActionFieldValue 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "The value returned in the Ingress Action Field of the PTR. 1174 The value ingNoTlv(0) indicates that no Reply Ingress TLV was 1175 returned in the PTM." 1176 REFERENCE "RFC 7455 8.4.1" 1177 ::= { trillOamPtrEntry 7 } 1179 trillOamMepPtrIngressMac OBJECT-TYPE 1180 SYNTAX MacAddress 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "MAC address returned in the ingress MAC address field." 1185 REFERENCE "RFC 7455 8.4.1" 1186 ::= { trillOamPtrEntry 8 } 1188 trillOamMepPtrIngressPortIdSubtype OBJECT-TYPE 1189 SYNTAX LldpPortIdSubtype 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "Ingress Port ID. The format of this object is determined by 1194 the value of the trillOamMepPtrIngressPortIdSubtype object." 1195 REFERENCE "RFC 7455 8.4.1" 1196 ::= { trillOamPtrEntry 9 } 1198 trillOamMepPtrIngressPortId OBJECT-TYPE 1199 SYNTAX LldpPortId 1200 MAX-ACCESS read-only 1201 STATUS current 1202 DESCRIPTION 1203 "Ingress Port ID. The format of this object is determined by 1204 the value of the trillOamMepPtrIngressPortId object." 1205 REFERENCE "RFC 7455 8.4.1" 1206 ::= { trillOamPtrEntry 10 } 1208 trillOamMepPtrEgress OBJECT-TYPE 1209 SYNTAX Dot1agCfmEgressActionFieldValue 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "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." 1258 REFERENCE "RFC 7455 8.4.1" 1259 ::= { trillOamPtrEntry 15 } 1261 trillOamMepPtrChassisId OBJECT-TYPE 1262 SYNTAX LldpChassisId 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "The Chassis ID returned in the Sender ID TLV of the PTR, if 1267 any. The format of this object is determined by the 1268 value of the trillOamMepPtrChassisIdSubtype object." 1269 REFERENCE "RFC 7455 8.4.1" 1270 ::= { trillOamPtrEntry 16 } 1272 trillOamMepPtrOrganizationSpecificTlv OBJECT-TYPE 1273 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "All Organization specific TLVs returned in the PTR, if 1278 any. Includes all octets including and following the TLV 1279 Length field of each TLV, concatenated together." 1280 REFERENCE "RFC 7455 8.4.1" 1281 ::= { trillOamPtrEntry 17 } 1283 trillOamMepPtrNextHopNicknames OBJECT-TYPE 1284 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "Next hop Rbridge List TLV returned in the PTR, if 1289 any. Includes all octets including and following the TLV 1290 Length field of each TLV, concatenated together." 1291 REFERENCE "RFC 7455 8.4.1" 1292 ::= { trillOamPtrEntry 18 } 1294 -- ****************************************************************** 1295 -- TRILL OAM Multi Destination Reply Table 1296 -- ****************************************************************** 1298 trillOamMtvrTable OBJECT-TYPE 1299 SYNTAX SEQUENCE OF TrillOamMtvrEntry 1300 MAX-ACCESS not-accessible 1301 STATUS current 1302 DESCRIPTION 1303 "This table includes Multi-destination Reply objects and 1304 operations for the TRILL OAM described in RFC 7455. 1306 Each row in the table represents a Multi-destination Reply 1307 Entry for the defined MEP and Transaction. This table uses 1308 five indices. The first three indices are the indices of the 1309 Maintenance Domain, MaNet, and MEP tables. 1310 The fourth index is the specific Transaction Identifier 1311 on the selected MEP. The fifth index is the receive order 1312 of Multi-destination replies. 1314 Some writable objects in this table are only applicable in 1315 certain cases (as described under each object), and attempts 1316 to write values for them in other cases will be ignored." 1317 REFERENCE "RFC 7455" 1318 ::= { trillOamMep 4 } 1320 trillOamMtvrEntry OBJECT-TYPE 1321 SYNTAX TrillOamMtvrEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "The conceptual row of trillOamMtvrTable." 1326 INDEX { 1327 dot1agCfmMdIndex, 1328 dot1agCfmMaIndex, 1329 dot1agCfmMepIdentifier, 1330 trillOamMepPtrTransactionId, 1331 trillOamMepMtvrReceiveOrder 1332 } 1333 ::= { trillOamMtvrTable 1 } 1335 TrillOamMtvrEntry ::= SEQUENCE { 1336 trillOamMepMtvrTransactionId Unsigned32, 1337 trillOamMepMtvrReceiveOrder Unsigned32, 1338 trillOamMepMtvrFlag Unsigned32, 1339 trillOamMepMtvrErrorCode Unsigned32, 1340 trillOamMepMtvrLastEgressId Unsigned32, 1341 trillOamMepMtvrIngress Dot1agCfmIngressActionFieldValue, 1342 trillOamMepMtvrIngressMac MacAddress, 1343 trillOamMepMtvrIngressPortIdSubtype LldpPortIdSubtype, 1344 trillOamMepMtvrIngressPortId LldpPortId, 1345 trillOamMepMtvrEgress Dot1agCfmEgressActionFieldValue, 1346 trillOamMepMtvrEgressMac MacAddress, 1347 trillOamMepMtvrEgressPortIdSubtype LldpPortIdSubtype, 1348 trillOamMepMtvrEgressPortId LldpPortId, 1349 trillOamMepMtvrChassisIdSubtype LldpChassisIdSubtype, 1350 trillOamMepMtvrChassisId LldpChassisId, 1351 trillOamMepMtvrOrganizationSpecificTlv OCTET STRING, 1352 trillOamMepMtvrNextHopNicknames OCTET STRING, 1353 trillOamMepMtvrReceiverAvailability TruthValue, 1354 trillOamMepMtvrReceiverCount TruthValue 1355 } 1357 trillOamMepMtvrTransactionId OBJECT-TYPE 1358 SYNTAX Unsigned32 (0..4294967295) 1359 MAX-ACCESS not-accessible 1360 STATUS current 1361 DESCRIPTION 1362 "Transaction identifier/sequence number returned by a 1363 previous transmit Multi-destination message command 1364 indicating which MTVM's response is going to be returned." 1365 REFERENCE "RFC 7455 section 11" 1366 ::= { trillOamMtvrEntry 1 } 1368 trillOamMepMtvrReceiveOrder OBJECT-TYPE 1369 SYNTAX Unsigned32 (1..4294967295) 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "An index to distinguish among multiple MTVR with same MTVR 1374 Transaction Identifier field value. 1375 trillOamMepMtvrReceiveOrder is assigned sequentially from 1, 1376 in the order that the Multi-destination Tree Initiator 1377 received the MTVRs." 1378 REFERENCE "RFC 7455 section 11" 1379 ::= { trillOamMtvrEntry 2 } 1381 trillOamMepMtvrFlag OBJECT-TYPE 1382 SYNTAX Unsigned32 (0..15) 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "FCOI (TRILL OAM Message TLV) field value for a 1387 returned MTVR." 1388 REFERENCE "RFC 7455, 8.4.2" 1389 ::= { trillOamMtvrEntry 3 } 1391 trillOamMepMtvrErrorCode OBJECT-TYPE 1392 SYNTAX Unsigned32 (0..65535) 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "Return Code and Return Sub code value for a returned MTVR." 1397 REFERENCE "RFC 7455, 8.4.2" 1398 ::= { trillOamMtvrEntry 4 } 1400 trillOamMepMtvrLastEgressId OBJECT-TYPE 1401 SYNTAX Unsigned32 (0..65535) 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "An Integer field holding the Last Egress Identifier returned 1406 in the MTVR Upstream Rbridge Nickname TLV of the MTVR. The 1407 Last Egress Identifier identifies the Upstream Nickname." 1408 REFERENCE "RFC 7455 8.4.1" 1409 ::= { trillOamMtvrEntry 5 } 1411 trillOamMepMtvrIngress OBJECT-TYPE 1412 SYNTAX Dot1agCfmIngressActionFieldValue 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "The value returned in the Ingress Action Field of 1417 the MTVR. The value ingNoTlv(0) indicates that no 1418 Reply Ingress TLV was returned in the MTVM." 1419 REFERENCE "RFC 7455 11.2.3" 1420 ::= { trillOamMtvrEntry 6 } 1422 trillOamMepMtvrIngressMac OBJECT-TYPE 1423 SYNTAX MacAddress 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "MAC address returned in the ingress MAC address field." 1428 REFERENCE "RFC 7455 8.4.1" 1429 ::= { trillOamMtvrEntry 7 } 1431 trillOamMepMtvrIngressPortIdSubtype OBJECT-TYPE 1432 SYNTAX LldpPortIdSubtype 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "Ingress Port ID. The format of this object is 1437 determined by the value of the 1438 trillOamMepMtvrIngressPortIdSubtype object." 1439 REFERENCE "RFC 7455 8.4.1" 1440 ::= { trillOamMtvrEntry 8 } 1442 trillOamMepMtvrIngressPortId OBJECT-TYPE 1443 SYNTAX LldpPortId 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "Ingress Port ID. The format of this object is determined by 1448 the value of the trillOamMepMtvrIngressPortId object." 1449 REFERENCE "RFC 7455 8.4.1" 1450 ::= { trillOamMtvrEntry 9 } 1452 trillOamMepMtvrEgress OBJECT-TYPE 1453 SYNTAX Dot1agCfmEgressActionFieldValue 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "The value returned in the Egress Action Field of the MTVR. 1458 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1459 returned in the MTVR." 1460 REFERENCE "RFC 7455 8.4.1" 1461 ::= { trillOamMtvrEntry 10 } 1463 trillOamMepMtvrEgressMac OBJECT-TYPE 1464 SYNTAX MacAddress 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "MAC address returned in the egress MAC address field." 1469 REFERENCE "RFC 7455 8.4.1" 1470 ::= { trillOamMtvrEntry 11 } 1472 trillOamMepMtvrEgressPortIdSubtype OBJECT-TYPE 1473 SYNTAX LldpPortIdSubtype 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "Egress Port ID. The format of this object is determined by 1478 the value of the trillOamMepMtvrEgressPortIdSubtype object." 1479 REFERENCE "RFC 7455 8.4.1" 1480 ::= { trillOamMtvrEntry 12 } 1482 trillOamMepMtvrEgressPortId OBJECT-TYPE 1483 SYNTAX LldpPortId 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "Egress Port ID. The format of this object is determined by 1488 the value of the trillOamMepMtvrEgressPortId object." 1489 REFERENCE "RFC 7455 8.4.1" 1490 ::= { trillOamMtvrEntry 13 } 1492 trillOamMepMtvrChassisIdSubtype OBJECT-TYPE 1493 SYNTAX LldpChassisIdSubtype 1494 MAX-ACCESS read-only 1495 STATUS current 1496 DESCRIPTION 1497 "This object specifies the format of the Chassis ID returned 1498 in the Sender ID TLV of the MTVR, if any. This value is 1499 meaningless if the trillOamMepMtvrChassisId has a 1500 length of 0." 1501 REFERENCE "RFC 7455 8.4.1" 1502 ::= { trillOamMtvrEntry 14 } 1504 trillOamMepMtvrChassisId OBJECT-TYPE 1505 SYNTAX LldpChassisId 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "The Chassis ID returned in the Sender ID TLV of the MTVR, if 1510 any. The format of this object is determined by the 1511 value of the trillOamMepMtvrChassisIdSubtype object." 1512 REFERENCE "RFC 7455 8.4.1" 1513 ::= { trillOamMtvrEntry 15 } 1515 trillOamMepMtvrOrganizationSpecificTlv OBJECT-TYPE 1516 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "All Organization specific TLVs returned in the MTVR, if 1521 any. Includes all octets including and following the TLV 1522 Length field of each TLV, concatenated together." 1523 REFERENCE "RFC 7455 8.4.1" 1524 ::= { trillOamMtvrEntry 16 } 1526 trillOamMepMtvrNextHopNicknames OBJECT-TYPE 1527 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "Next hop Rbridge List TLV returned in the PTR, if 1532 any. Includes all octets including and following the TLV 1533 Length field of each TLV, concatenated together." 1534 REFERENCE "RFC 7455 8.4.3" 1535 ::= { trillOamMtvrEntry 17 } 1537 trillOamMepMtvrReceiverAvailability OBJECT-TYPE 1538 SYNTAX TruthValue 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "True value indicates that MTVR response contained 1543 Multicast receiver availability TLV." 1544 REFERENCE "RFC 7455 8.4.10" 1545 ::= { trillOamMtvrEntry 18 } 1547 trillOamMepMtvrReceiverCount OBJECT-TYPE 1548 SYNTAX TruthValue 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "Indicates the number of Multicast receivers available on 1553 responding RBridge on the VLAN specified by the 1554 diagnostic VLAN." 1555 REFERENCE "RFC 7455 8.4.10" 1556 ::= { trillOamMtvrEntry 19 } 1558 -- ***************************************************************** 1559 -- TRILL OAM MEP Database Table 1560 -- ***************************************************************** 1562 trillOamMepDbTable OBJECT-TYPE 1563 SYNTAX SEQUENCE OF TrillOamMepDbEntry 1564 MAX-ACCESS not-accessible 1565 STATUS current 1566 DESCRIPTION 1567 "This table is an extension of the dot1agCfmMepDbTable 1568 and rows are automatically added to or deleted from 1569 this table based upon row creation and destruction of the 1570 dot1agCfmMepDbTable." 1571 REFERENCE 1572 "RFC 7455" 1573 ::= { trillOamMep 5 } 1575 trillOamMepDbEntry OBJECT-TYPE 1576 SYNTAX TrillOamMepDbEntry 1577 MAX-ACCESS not-accessible 1578 STATUS current 1579 DESCRIPTION 1580 "The conceptual row of trillOamMepDbTable." 1581 AUGMENTS { 1582 dot1agCfmMepDbEntry 1583 } 1584 ::= { trillOamMepDbTable 1 } 1586 TrillOamMepDbEntry ::= SEQUENCE { 1587 trillOamMepDbFlowIndex Unsigned32, 1588 trillOamMepDbFlowEntropy OCTET STRING, 1589 trillOamMepDbFlowState Dot1agCfmRemoteMepState, 1590 trillOamMepDbFlowFailedOkTime TimeStamp, 1591 trillOamMepDbRbridgeName Unsigned32, 1592 trillOamMepDbLastGoodSeqNum Counter32 1593 } 1595 trillOamMepDbFlowIndex OBJECT-TYPE 1596 SYNTAX Unsigned32 (1..65535) 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "This object identifies the Flow. If Flow Identifier TLV 1601 is received than index received can also be used." 1602 REFERENCE "RFC 7455" 1603 ::= {trillOamMepDbEntry 1 } 1605 trillOamMepDbFlowEntropy OBJECT-TYPE 1606 SYNTAX OCTET STRING (SIZE (96)) 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "96 byte Flow Entropy." 1611 REFERENCE "RFC 7455 section 3." 1612 ::= {trillOamMepDbEntry 2 } 1614 trillOamMepDbFlowState OBJECT-TYPE 1615 SYNTAX Dot1agCfmRemoteMepState 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "The operational state of the remote MEP (flow based) 1620 IFF State machines. State Machine is running now per 1621 flow." 1622 REFERENCE "RFC 7455" 1623 ::= {trillOamMepDbEntry 3 } 1625 trillOamMepDbFlowFailedOkTime OBJECT-TYPE 1626 SYNTAX TimeStamp 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "The Time (sysUpTime) at which the Remote MEP Flow state 1631 machine last entered either the RMEP_FAILED or RMEP_OK 1632 state." 1633 REFERENCE "RFC 7455" 1634 ::= {trillOamMepDbEntry 4 } 1636 trillOamMepDbRbridgeName OBJECT-TYPE 1637 SYNTAX Unsigned32(0..65471) 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "Remote MEP Rbridge Nickname." 1642 REFERENCE "RFC 7455 RFC 6325 section 3" 1643 ::= {trillOamMepDbEntry 5 } 1645 trillOamMepDbLastGoodSeqNum OBJECT-TYPE 1646 SYNTAX Counter32 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "Last Sequence Number received." 1651 REFERENCE "RFC 7455 13.1" 1652 ::= {trillOamMepDbEntry 6} 1654 -- ****************************************************************** 1655 -- TRILL OAM MIB NOTIFICATIONS (TRAPS) 1656 -- This notification is sent to management entity whenever a 1657 -- MEP loses/restores 1658 -- contact with its peer Flow Meps 1659 -- ****************************************************************** 1660 trillOamFaultAlarm NOTIFICATION-TYPE 1661 OBJECTS { trillOamMepDbFlowState } 1662 STATUS current 1663 DESCRIPTION 1664 "A MEP Flow has a persistent defect condition. 1665 A notification (fault alarm) is sent to the management 1666 entity with the OID of the Flow that has detected the fault. 1668 The management entity receiving the notification can identify 1669 the system from the network source address of the 1670 notification, and can identify the Flow reporting the defect 1671 by the indices in the OID of the trillOamMepFlowIndex, and 1672 trillOamFlowDefect variable in the notification: 1674 dot1agCfmMdIndex - Also the index of the MEP's 1675 Maintenance Domain table entry 1676 (dot1agCfmMdTable). 1677 dot1agCfmMaIndex - Also an index (with the MD table index) 1678 of the MEP's Maintenance Association 1679 network table entry 1680 (dot1agCfmMaNetTable), and (with the MD 1681 table index and component ID) of the 1682 MEP's MA component table entry 1683 (dot1agCfmMaCompTable). 1684 dot1agCfmMepIdentifier - MEP Identifier and final index 1685 into the MEP table (dot1agCfmMepTable). 1686 trillOamMepFlowCfgIndex - Index identifies 1687 indicates the specific Flow for 1688 the MEP" 1689 REFERENCE "RFC 7455" 1690 ::= { trillOamNotifications 1 } 1692 -- ****************************************************************** 1693 -- TRILL OAM MIB Module - Conformance Information 1694 -- ****************************************************************** 1696 trillOamMibCompliances OBJECT IDENTIFIER 1697 ::= { trillOamMibConformance 1 } 1699 trillOamMibGroups OBJECT IDENTIFIER 1700 ::= { trillOamMibConformance 2 } 1702 -- ****************************************************************** 1703 -- TRILL OAM MIB Units of conformance 1704 -- ****************************************************************** 1706 trillOamMepMandatoryGroup OBJECT-GROUP 1707 OBJECTS { 1708 trillOamMepRName, 1709 trillOamMepNextPtmTId, 1710 trillOamMepNextMtvmTId, 1711 trillOamMepPtrIn, 1712 trillOamMepPtrInOutofOrder, 1713 trillOamMepPtrOut, 1714 trillOamMepMtvrIn, 1715 trillOamMepMtvrInOutofOrder, 1716 trillOamMepMtvrOut, 1717 trillOamMepTxLbmDestRName, 1718 trillOamMepTxLbmHC, 1719 trillOamMepTxLbmReplyModeOob, 1720 trillOamMepTransmitLbmReplyIp, 1721 trillOamMepTxLbmFlowEntropy, 1722 trillOamMepTxPtmDestRName, 1723 trillOamMepTxPtmHC, 1724 trillOamMepTxPtmReplyModeOob, 1725 trillOamMepTransmitPtmReplyIp, 1726 trillOamMepTxPtmFlowEntropy, 1727 trillOamMepTxPtmStatus, 1728 trillOamMepTxPtmResultOK, 1729 trillOamMepTxPtmMessages, 1730 trillOamMepTxPtmSeqNumber, 1731 trillOamMepTxMtvmTree, 1732 trillOamMepTxMtvmHC, 1733 trillOamMepTxMtvmReplyModeOob, 1734 trillOamMepTransmitMtvmReplyIp, 1735 trillOamMepTxMtvmFlowEntropy, 1736 trillOamMepTxMtvmStatus, 1737 trillOamMepTxMtvmResultOK, 1738 trillOamMepTxMtvmMessages, 1739 trillOamMepTxMtvmSeqNumber, 1740 trillOamMepTxMtvmScopeList, 1741 trillOamMepDiscontinuityTime 1742 } 1743 STATUS current 1744 DESCRIPTION 1745 "Mandatory objects for the TRILL OAM MEP group." 1746 ::= { trillOamMibGroups 1 } 1748 trillOamMepFlowCfgTableGroup OBJECT-GROUP 1749 OBJECTS { 1750 trillOamMepFlowCfgFlowEntropy, 1751 trillOamMepFlowCfgDestRName, 1752 trillOamMepFlowCfgFlowHC, 1753 trillOamMepFlowCfgRowStatus 1754 } 1755 STATUS current 1756 DESCRIPTION 1757 "TRILL OAM MEP Flow Configuration objects group." 1758 ::= { trillOamMibGroups 2 } 1760 trillOamPtrTableGroup OBJECT-GROUP 1761 OBJECTS { 1762 trillOamMepPtrHC, 1763 trillOamMepPtrFlag, 1764 trillOamMepPtrErrorCode, 1765 trillOamMepPtrTerminalMep, 1766 trillOamMepPtrLastEgressId, 1767 trillOamMepPtrIngress, 1768 trillOamMepPtrIngressMac, 1769 trillOamMepPtrIngressPortIdSubtype, 1770 trillOamMepPtrIngressPortId, 1771 trillOamMepPtrEgress, 1772 trillOamMepPtrEgressMac, 1773 trillOamMepPtrEgressPortIdSubtype, 1774 trillOamMepPtrEgressPortId, 1775 trillOamMepPtrChassisIdSubtype, 1776 trillOamMepPtrChassisId, 1777 trillOamMepPtrOrganizationSpecificTlv, 1778 trillOamMepPtrNextHopNicknames 1779 } 1780 STATUS current 1781 DESCRIPTION 1782 "TRILL OAM MEP PTR objects group." 1783 ::= { trillOamMibGroups 3 } 1785 trillOamMtvrTableGroup OBJECT-GROUP 1786 OBJECTS { 1787 trillOamMepMtvrFlag, 1788 trillOamMepMtvrErrorCode, 1789 trillOamMepMtvrLastEgressId, 1790 trillOamMepMtvrIngress, 1791 trillOamMepMtvrIngressMac, 1792 trillOamMepMtvrIngressPortIdSubtype, 1793 trillOamMepMtvrIngressPortId, 1794 trillOamMepMtvrEgress, 1795 trillOamMepMtvrEgressMac, 1796 trillOamMepMtvrEgressPortIdSubtype, 1797 trillOamMepMtvrEgressPortId, 1798 trillOamMepMtvrChassisIdSubtype, 1799 trillOamMepMtvrChassisId, 1800 trillOamMepMtvrOrganizationSpecificTlv, 1801 trillOamMepMtvrNextHopNicknames, 1802 trillOamMepMtvrReceiverAvailability, 1803 trillOamMepMtvrReceiverCount 1804 } 1805 STATUS current 1806 DESCRIPTION 1807 "TRILL OAM MEP MTVR objects group." 1808 ::= { trillOamMibGroups 4 } 1810 trillOamMepDbGroup OBJECT-GROUP 1811 OBJECTS { 1812 trillOamMepDbFlowIndex, 1813 trillOamMepDbFlowEntropy, 1814 trillOamMepDbFlowState, 1815 trillOamMepDbFlowFailedOkTime, 1816 trillOamMepDbRbridgeName, 1817 trillOamMepDbLastGoodSeqNum 1818 } 1820 STATUS current 1821 DESCRIPTION 1822 "TRILL OAM MEP DB objects group." 1823 ::= { trillOamMibGroups 5 } 1825 trillOamNotificationGroup NOTIFICATION-GROUP 1826 NOTIFICATIONS { trillOamFaultAlarm } 1827 STATUS current 1828 DESCRIPTION 1829 "A collection of objects describing notifications(traps)." 1830 ::= { trillOamMibGroups 6 } 1832 -- ****************************************************************** 1833 -- TRILL OAM MIB Module Compliance statements 1834 -- ****************************************************************** 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 } 2168 Editor's Note (to be removed prior to publication): the IANA is 2169 requested to assign a value for "xxx" under the 'mib-2' subtree and 2170 to record the assignment in the SMI Numbers registry. When the 2171 assignment has been made, the RFC Editor is asked to replace "XXX" 2172 (here and in the MIB module) with the assigned value and to remove 2173 this note. 2175 10. Contributors 2177 We wish to thank members of the IETF TRILL WG and the MIB-Doctor for 2178 their comments and suggestions. Detailed comments were provided by 2179 Sam Aldrin, Donald Eastlake, Tom Taylor, and Harrie Hazewinkel. 2181 11. References 2182 11.1. Normative References 2184 [RFC2119] Bradner, S., "Key words for use in RFCs to 2185 Indicate Requirement Levels", BCP 14, RFC 2119, March 2186 1997. 2188 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2189 Schoenwaelder, Ed., "Structure of Management Information 2190 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2192 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2193 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2194 58, RFC 2579, April 1999. 2196 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2197 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2198 STD 58, RFC 2580, April 1999. 2200 [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, 2201 S., and A. Ghanwani, "Routing Bridges (RBridges): Base 2202 Protocol Specification", RFC 6325, July 2011. 2204 [RFC7172] Eastlake 3rd, D., Zhang, M., Agarwal, P., 2205 Perlman, R., and D. Dutt, "Transparent Interconnection of 2206 Lots of Links (TRILL): Fine-Grained Labeling", RFC 7172, 2207 May 2014. 2209 [RFC7455] Senevirathne, T., et.al., "Transparent 2210 Interconnection of Lots of Links (TRILL): Fault 2211 Management", March 2015. 2213 [LLDP-MIB] IEEE, 2214 http://www.ieee802.org/1/files/public/MIBs/LLDP-MIB- 2215 200505060000Z.txt 2217 [802.1Q] IEEE, "IEEE Standard for Local and metropolitan 2218 area networks - Media Access Control (MAC) Bridges and 2219 Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 2220 31 August 2011. 2222 11.2. Informative References 2224 [RFC3410] Case, J., Mundy, R., Partain, D., and B.Stewart, 2225 "Introduction and Applicability Statements for Internet- 2226 Standard Management Framework", RFC 3410, December 2002. 2228 [RFC6905] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., 2229 and R. Watve, "Requirements for Operations, 2230 Administration, and Maintenance (OAM) in Transparent 2231 Interconnection of Lots of Links (TRILL)", RFC 6905, March 2232 2013. 2234 [RFC7174] Salam, S., Senevirathne, T., Aldrin, S., and D. 2235 Eastlake 3rd, "Transparent Interconnection of Lots of 2236 Links (TRILL) Operations, Administration, and Maintenance 2237 (OAM) Framework", RFC 7174, May 2014. 2239 Authors' Addresses 2241 Deepak Kumar 2242 Cisco 2243 510 McCarthy Blvd, 2244 Milpitas, CA 95035, USA 2245 Phone : +1 408-853-9760 2246 Email: dekumar@cisco.com 2248 Samer Salam 2249 Cisco 2250 595 Burrard St. Suite 2123 2251 Vancouver, BC V7X 1J1, Canada 2252 Email: ssalam@cisco.com 2254 Tissa Senevirathne 2255 Consultant 2256 Email: tsenevir@gmail.com