idnits 2.17.1 draft-ietf-trill-oam-mib-09.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 718 has weird spacing: '...d. The maxim...' == Line 719 has weird spacing: '...address is 16...' == Line 798 has weird spacing: '...treated as si...' == Line 954 has weird spacing: '...try for the d...' == Line 955 has weird spacing: '...e first three...' -- The document date (September 29, 2015) is 3131 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 375, but not defined == Missing Reference: 'RFC3414' is mentioned on line 2161, but not defined == Missing Reference: 'RFC3826' is mentioned on line 2161, but not defined == Missing Reference: 'RFC5591' is mentioned on line 2163, but not defined == Missing Reference: 'RFC5592' is mentioned on line 2164, but not defined == Missing Reference: 'RFC6353' is mentioned on line 2164, but not defined == Unused Reference: 'LLDP-MIB' is defined on line 2228, 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 March 2016 September 29, 2015 9 TRILL OAM MIB 10 draft-ietf-trill-oam-mib-09.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 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 module . . . . . . . . . . . . . . . 7 67 6.1. Relationship to IEEE8021-TC-MIB . . . . . . . . . . . . . 7 68 6.2. Relationship to IEEE8021-CFM-MIB . . . . . . . . . . . . . 8 69 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 70 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 8 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 44 72 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 47 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 is intended to meet the requirements given in 81 [RFC6905]. The general framework for TRILL OAM is specified in 82 [RFC7174]. The details of the Fault Management (FM) solution, 83 conforming to that framework, are presented in RFC 7455. The solution 84 leverages the message format defined in Ethernet Connectivity Fault 85 Management (CFM) [802.1Q] as the basis for the TRILL OAM message 86 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: 116 MTVM - Multi-destination Tree Verification Message [RFC7455] 118 MTVR - Multi-destination Tree Verification Reply [RFC7455] 120 PTM - Path Trace Message [RFC7455] 122 PTR - Path Trace Reply [RFC7455] 124 MEP - Maintenance End Point [RFC7174] [802.1Q] 126 MIP - Maintenance Intermediate Point [RFC7174] [802.1Q] 128 MP - Maintenance Point [RFC7174] 130 CCM - Continuity Check Message [802.1Q] 132 FGL - Fine-Grained Label 134 LBM - Loopback Message [802.1Q] 136 LBR - Loopback Reply [802.1Q] 138 TRILL - Transparent Interconnection of Lots of Links [RFC6325] 140 4. Overview 141 The TRILL-OAM-MIB module is intended to provide an overall framework for 142 managing TRILL OAM. It leverages the IEEE8021-CFM-MIB and IEEE8021-CFM- 143 V2-MIB modules defined in [802.1Q], and augments the Maintenance End 144 Point(MEP) and MEP Db entries. It also adds a new table for TRILL OAM 145 specific messages. 147 5. Structure of the MIB module 149 Objects in this MIB module are arranged into subtrees. Each subtree is 150 organized as a set of related objects. The various subtrees are shown 151 below, supplemented with the required elements of the IEEE8021-CFM-MIB 152 module. 154 5.1. Textual Conventions 156 Textual conventions are defined to represent object types relevant to 157 the TRILL OAM MIB. 159 5.2. The TRILL OAM MIB Subtree 161 TRILL-OAM MIB Tree describe below consists of trilloamNotifications 162 (Traps) and trillOamMibObjects. The trilloamNotifications are sent to 163 management entity whenever a MEP loses/restores contact with its peer 164 Flow MEPs. 166 The TRILL OAM MIB Per MEP Objects are defined in the trillOamMepTable. 167 The trillOamMepTable augments the dot1agCfmMepEntry (please see section 168 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally 169 defined for an individual MEP and its associated Flow. 171 TRILL-OAM-MIB 173 |--trillOamNotifications (trillOamMib 0} 175 |--trillOamFaultAlarm 177 |--trillOamMibObjects {trillOamMib 1} 179 |--trillOamMep {trillOamMibObjects 1} 181 |--trillOamMepTable {trillOamMep 1} - Local TRLL config 183 |--trillOamMepFlowCfgTable 185 |--trillOamPtrTable 187 |--trillOamMtvrTable 189 |--trillOamMepDbTable 191 5.3.1. The Notifications Subtree 193 Notifications (fault alarms) are sent to the management entity with the 194 OID of the MEP that has detected the fault. Notifications are generated 195 whenever MEP loses/restores contact with its peer Flow MEPs. 197 5.3.2. The Table Structures 199 The TRILL OAM MIB Per MEP Objects are defined in the trillOamMepTable. 200 The trillOamMepTable augments the dot1agCfmMepEntry (please see section 201 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally 202 defined for an individual MEP and its associated Flow. 204 5.3.2.1. trillOamMepTable Objects 205 This table is an extension of the dot1agCfmMepTable and rows are 206 automatically added or deleted from this table based upon row 207 creation and destruction of the dot1agCfmMepTable. 209 This table represents the local MEP TRILL OAM configuration table. 210 The primary purpose of this table is provide local parameters for the 211 TRILL OAM function found in RFC 7455 and instantiated at a MEP. 213 5.3.2.2. trillOamMepFlowCfgTable Objects 215 Each row in this table represents a Flow Configuration Entry for the 216 associated MEP. This table uses four indices. The first three indices 217 are the indices of the Maintenance Domain, MaNet, and MEP tables. The 218 fourth index is the specific Flow Configuration Entry on the selected 219 MEP. Some write-able objects in this table are only applicable in 220 certain cases (as described under each object below), and attempts to 221 write values for them in other cases will be ignored. 223 5.3.2.3. trillOamPtrTable Objects 225 Each row in this table represents a Path Trace reply Entry for the 226 Defined MEP and Transaction. This table uses four indices. The first 227 three indices identify the MEP and the fourth index specifies the 228 transaction identifier. This transaction identifier uniquely 229 identifies the response for a MEP which can have multiple flow. 231 5.3.2.4. trillOamMtvrTable Objects 233 This table includes managed objects for the Multi-Destination Reply. 234 Each row in the table represents a Multi-destination Reply Entry for 235 the defined MEP and Transaction. This table uses the following five 236 indices: 1) Maintenance Domain, 2) MANET, 3) MEP tables, 4) 237 Transaction identifier of selected MEP, and 5) receive order of 238 Multi-destination replies. 240 Some write-able objects in this table are only applicable in certain 241 cases (as described under each object below), and attempts to write a 242 value for them in other cases will be ignored. 244 5.3.2.5. trillOamMepDbTable Objects 246 This table is an augmentation of the dot1agCfmMepDbTable, and rows 247 are automatically added or deleted from this table based upon row 248 creation and destruction of the dot1agCfmMepDbTable. 250 6. Relationship to other MIB module 252 The IEEE8021-CFM-MIB, and LLDP-MIB contain objects that are relevant 253 to TRILL OAM MIB. Management objects contained in these modules are 254 not duplicated here, to reduce overlap to the extent possible. From 255 IEEE8021-CFM-MIB following objects are imported 257 o dot1agCfmMdIndex 259 o dot1agCfmMaIndex 261 o dot1agCfmMepIdentifier 263 o dot1agCfmMepEntry 265 o dot1agCfmMepDbEntry 267 o Dot1agCfmIngressActionFieldValue 269 o Dot1agCfmEgressActionFieldValue 271 o Dot1agCfmRemoteMepState 273 From LLDP-MIB following objects are imported 275 o LldpChassisId 277 o LldpChassisIdSubtype 279 o LldpPortId 281 6.1. Relationship to IEEE8021-TC-MIB 283 In TRILL, traffic labeling can be done using either a 12-bit VLAN 284 or a 24-bit fine grain label [RFC7172]. 286 The IEEE8021-TC-MIB definition of IEEE8021ServiceSelectorType 287 includes the two values: 289 - 1 representing a vlanId, and 291 - 2 representing a 24 bit isid 293 We have chosen to use value 2 for TRILL's fine grain label. As 294 such, TRILL-OAM-MIB will import IEEE8021ServiceSelectorType, 295 IEEE8021ServiceSelectorValueOrNone, and 296 IEEE8021ServiceSelectorValue from IEEE8021-TC-MIB. 298 6.2. Relationship to IEEE8021-CFM-MIB 300 trillOamMepTable augments dot1agCfmMepEntry. Implementation of 301 IEEE8021-CFM-MIB is required as we are augmenting the IEEE-CFM-MIB 302 Table. Objects/Tables that are not applicable to a TRILL 303 implementation have to be handled by the TRILL implementation back 304 end and appropriate default values as described in IEEE8021-CFM-MIB 305 have to be returned. 307 TRILL standard Implementation doesn't support Link Trace Message and 308 Link Trace Reply as RFC7455 substituted it with Path Trace Message 309 and Reply for unicast traffic and Multi-destination Tree verification 310 Message and Reply for multicast traffic, and statistics for these 311 messages should be default as per IEEE8021-CFM-MIB. 313 6.3. MIB modules required for IMPORTS 315 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 316 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IEEE-8021-CFM-MIB, LLDP- 317 MIB. 319 7. Definitions 321 TRILL-OAM-MIB DEFINITIONS ::= BEGIN 323 IMPORTS 325 MODULE-IDENTITY, 326 OBJECT-TYPE, 327 Counter32, 328 Unsigned32, 329 Integer32, 330 mib-2, 331 NOTIFICATION-TYPE 332 FROM SNMPv2-SMI 333 RowStatus, 334 TruthValue, 335 TimeStamp, 336 MacAddress 337 FROM SNMPv2-TC 338 OBJECT-GROUP, 339 NOTIFICATION-GROUP, 340 MODULE-COMPLIANCE 341 FROM SNMPv2-CONF 342 dot1agCfmMdIndex, 343 dot1agCfmMaIndex, 344 dot1agCfmMepIdentifier, 345 dot1agCfmMepEntry, 346 dot1agCfmMepDbEntry, 347 Dot1agCfmIngressActionFieldValue, 348 Dot1agCfmEgressActionFieldValue, 349 Dot1agCfmRemoteMepState 350 FROM IEEE8021-CFM-MIB 351 LldpChassisId, 352 LldpChassisIdSubtype, 353 LldpPortId, 354 LldpPortIdSubtype 355 FROM LLDP-MIB; 357 trillOamMib MODULE-IDENTITY 358 LAST-UPDATED "201508231200Z" 359 ORGANIZATION "IETF TRILL WG" 360 CONTACT-INFO 361 "E-mail: trill@ietf.org" 362 DESCRIPTION 363 "This MIB module contains the management objects for the 364 management of Trill Services Operations, Administration 365 and Maintenance. 366 Initial version. Published as RFC xxxx. 368 ------------------------------------------------------------- 369 Reference Overview 371 A number of base documents have been used to create the 372 Textual Conventions MIB. The following are the 373 abbreviations for the baseline documents: 375 [CFM] refers to 'Connectivity Fault Management', 376 IEEE 802.1Q-2014, December 2014 377 [Q.840.1] refers to 'ITU-T Requirements and analysis for 378 NMS-EMS management interface of Ethernet over Transport and 379 Metro Ethernet Network (EoT/MEN)', March 2007 380 [Y.1731] refers to ITU-T Y.1731 'OAM functions and mechanisms 381 for Ethernet based networks', February 2011 382 ------------------------------------------------------------- 384 Abbreviations Used 386 Term Definition 387 CCM Continuity Check Message 388 CFM Connectivity Fault Management 389 CoS Class of Service 390 IEEE Institute of Electrical and Electronics 391 Engineers 392 IETF Internet Engineering Task Force 393 ITU-T International Telecommunication Union - 394 Telecommunication Standardization Bureau 395 MAC Media Access Control 396 MA Maintenance Association (equivalent to a MEG) 397 MD Maintenance Domain (equivalent to a OAM 398 Domain in MEF 17) 399 MD Level Maintenance Domain Level (equivalent to a 400 MEG level) 401 ME Maintenance Entity 402 MEG Maintenance Entity Group (equivalent to a MA) 403 MEG Level Maintenance Entity Group Level (equivalent to 404 MD Level) 405 MEP Maintenance Association End Point or MEG End 406 Point 407 MIB Management Information Base 408 MIP Maintenance Domain Intermediate Point or 409 MEG Intermediate Point 410 MP Maintenance Point. One of either a MEP or a MIP 411 OAM Operations, Administration, and Maintenance 412 On-Demand OAM actions that are initiated via 413 manual intervention for a limited time to carry 414 out diagnostics. On-Demand OAM can result in 415 singular or periodic OAM actions during the 416 diagnostic time interval 417 PDU Protocol Data Unit 418 RFC Request for Comment 419 SNMP Simple Network Management Protocol 420 SNMP Agent An SNMP entity containing one or more command 421 responder and/or notification originator 422 applications(along with their associated SNMP 423 engine). Typically implemented in Network 424 Element. 425 SNMP Manager An SNMP entity containing one or more command 426 generator and/or notification receiver 427 applications (along with their associated SNMP 428 engine). Typically implemented in an 429 EMS or NMS. 430 TLV Type Length Value, a method of encoding Objects 431 UTC Coordinated Universal Time 432 UNI User-to-Network Interface 433 VLAN Virtual LAN 434 PTR Path Trace Reply 435 PTM Path Trace Message 436 MTVR Multi-destination Tree Verification Reply 437 MTVM Multi-destination Tree Verification Message" 439 REVISION "201508231200Z" 440 DESCRIPTION 441 "Initial version. Published as RFC xxxx." 442 ::= { mib-2 12000 } 444 -- RFC Ed.: assigned by IANA, see section 9 for details 445 -- 446 -- ***************************************************************** 447 -- Object definitions in the TRILL OAM MIB Module 448 -- ***************************************************************** 450 trillOamNotifications OBJECT IDENTIFIER 451 ::= { trillOamMib 0 } 453 trillOamMibObjects OBJECT IDENTIFIER 454 ::= { trillOamMib 1 } 456 trillOamMibConformance OBJECT IDENTIFIER 457 ::= { trillOamMib 2 } 459 -- ***************************************************************** 460 -- Groups in the TRILL OAM MIB Module 461 -- ***************************************************************** 463 trillOamMep OBJECT IDENTIFIER 464 ::= { trillOamMibObjects 1 } 466 -- ***************************************************************** 467 -- TRILL OAM MEP Configuration 468 -- ***************************************************************** 470 trillOamMepTable OBJECT-TYPE 471 SYNTAX SEQUENCE OF TrillOamMepEntry 472 MAX-ACCESS not-accessible 473 STATUS current 474 DESCRIPTION 475 "This table is an extension of the dot1agCfmMepTable and 476 rows are automatically added or deleted from this table 477 based upon row creation and destruction of the 478 dot1agCfmMepTable. 480 This table represents the local MEP TRILL OAM 481 configuration table. The primary purpose of this table 482 is provide local parameters for the TRILL OAM function 483 found in RFC 7455 and instantiated at a MEP." 484 REFERENCE "RFC 7455" 485 ::= { trillOamMep 1 } 487 trillOamMepEntry OBJECT-TYPE 488 SYNTAX TrillOamMepEntry 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "The conceptual row of trillOamMepTable." 493 AUGMENTS { dot1agCfmMepEntry } 494 ::= { trillOamMepTable 1 } 496 TrillOamMepEntry ::= SEQUENCE { 497 trillOamMepRName Unsigned32, 498 trillOamMepNextPtmTId Counter32, 499 trillOamMepNextMtvmTId Counter32, 500 trillOamMepPtrIn Counter32, 501 trillOamMepPtrInOutofOrder Counter32, 502 trillOamMepPtrOut Counter32, 503 trillOamMepMtvrIn Counter32, 504 trillOamMepMtvrInOutofOrder Counter32, 505 trillOamMepMtvrOut Counter32, 506 trillOamMepTxLbmDestRName Unsigned32, 507 trillOamMepTxLbmHC Unsigned32, 508 trillOamMepTxLbmReplyModeOob TruthValue, 509 trillOamMepTransmitLbmReplyIp OCTET STRING, 510 trillOamMepTxLbmFlowEntropy OCTET STRING, 511 trillOamMepTxPtmDestRName Unsigned32, 512 trillOamMepTxPtmHC Unsigned32, 513 trillOamMepTxPtmReplyModeOob TruthValue, 514 trillOamMepTransmitPtmReplyIp OCTET STRING, 515 trillOamMepTxPtmFlowEntropy OCTET STRING, 516 trillOamMepTxPtmStatus TruthValue, 517 trillOamMepTxPtmResultOK TruthValue, 518 trillOamMepTxPtmSeqNumber Unsigned32, 519 trillOamMepTxPtmMessages Integer32, 520 trillOamMepTxMtvmTree Unsigned32, 521 trillOamMepTxMtvmHC Unsigned32, 522 trillOamMepTxMtvmReplyModeOob TruthValue, 523 trillOamMepTransmitMtvmReplyIp OCTET STRING, 524 trillOamMepTxMtvmFlowEntropy OCTET STRING, 525 trillOamMepTxMtvmStatus TruthValue, 526 trillOamMepTxMtvmResultOK TruthValue, 527 trillOamMepTxMtvmMessages Integer32, 528 trillOamMepTxMtvmSeqNumber Unsigned32, 529 trillOamMepTxMtvmScopeList OCTET STRING, 530 trillOamMepDiscontinuityTime TimeStamp 531 } 533 trillOamMepRName OBJECT-TYPE 534 SYNTAX Unsigned32 (0..65471) 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "This object contains Rbridge NickName of TRILL Rbridge as 539 defined in RFC 6325 section 3.7." 540 REFERENCE "RFC 7455 and RFC 6325 section 3.7" 541 ::= { trillOamMepEntry 1 } 543 trillOamMepNextPtmTId OBJECT-TYPE 544 SYNTAX Counter32 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "Next sequence number/transaction identifier to be sent in a 549 Multi-destination message. This sequence number can be zero 550 because it wraps around. Implementation of this identifier 551 should be should provide a unique code value in order to 552 identify Transaction Id for a MEP with multiple flows." 553 REFERENCE "RFC 7455 10.1.1" 554 ::= { trillOamMepEntry 2 } 556 trillOamMepNextMtvmTId OBJECT-TYPE 557 SYNTAX Counter32 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "Next sequence number/transaction identifier to be sent in a 562 Multi-destination message. This sequence number can be zero 563 because it wraps around. Implementation should be unique to 564 identify Transaction Id for a MEP with multiple flows." 565 REFERENCE "RFC 7455 11.2.1" 566 ::= { trillOamMepEntry 3 } 568 trillOamMepPtrIn OBJECT-TYPE 569 SYNTAX Counter32 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "Total number of valid, in-order Path Trace Replies 574 received." 575 REFERENCE "RFC 7455 section 10" 576 ::= { trillOamMepEntry 4 } 578 trillOamMepPtrInOutofOrder OBJECT-TYPE 579 SYNTAX Counter32 580 MAX-ACCESS read-only 581 STATUS current 582 DESCRIPTION 583 "Total number of valid, out-of-order Path Trace Replies 584 received." 585 REFERENCE "RFC 7455 section 10" 586 ::= { trillOamMepEntry 5 } 588 trillOamMepPtrOut OBJECT-TYPE 589 SYNTAX Counter32 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "Total number of valid, Path Trace Replies 594 transmitted." 595 REFERENCE "RFC 7455 section 10" 596 ::= { trillOamMepEntry 6 } 598 trillOamMepMtvrIn OBJECT-TYPE 599 SYNTAX Counter32 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "Total number of valid, in-order Multi-destination 604 Replies received." 605 REFERENCE "RFC 7455 section 11" 606 ::= { trillOamMepEntry 7 } 608 trillOamMepMtvrInOutofOrder OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "Total number of valid, out-of-order Multi-destination 614 Replies received." 615 REFERENCE "RFC 7455 section 11" 616 ::= { trillOamMepEntry 8 } 618 trillOamMepMtvrOut OBJECT-TYPE 619 SYNTAX Counter32 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "Total number of valid, Multi-destination Replies 624 transmitted." 625 REFERENCE "RFC 7455 section 11" 626 ::= { trillOamMepEntry 9 } 628 trillOamMepTxLbmDestRName OBJECT-TYPE 629 SYNTAX Unsigned32 (0..65471) 630 MAX-ACCESS read-create 631 STATUS current 632 DESCRIPTION 633 "The Target Destination Rbridge NickName Field as 634 defined in RFC 6325 section 3.7 to be transmitted." 635 REFERENCE "RFC 7455 and RFC6325 section 3.7" 636 ::= { trillOamMepEntry 10 } 638 trillOamMepTxLbmHC OBJECT-TYPE 639 SYNTAX Unsigned32(1..63) 640 MAX-ACCESS read-create 641 STATUS current 642 DESCRIPTION 643 "The Hop Count to be transmitted. 644 " 645 REFERENCE "RFC 7455 section 9 and 3" 646 ::= { trillOamMepEntry 11 } 648 trillOamMepTxLbmReplyModeOob OBJECT-TYPE 649 SYNTAX TruthValue 650 MAX-ACCESS read-create 651 STATUS current 652 DESCRIPTION 653 "True indicates that Reply of Lbm is out of band and 654 out of band IP Address TLV is to be transmitted. 655 False indicates that In band reply is transmitted." 656 REFERENCE "RFC 7455 9.2.1" 657 ::= { trillOamMepEntry 12 } 659 trillOamMepTransmitLbmReplyIp OBJECT-TYPE 660 SYNTAX OCTET STRING (SIZE (4..16)) 661 MAX-ACCESS read-create 662 STATUS current 663 DESCRIPTION 664 "IP address for out of band IP Address TLV is to be 665 transmitted, Maximum length for IPv6 is 16 OCTET 666 and IPv4 is 4 OCTET." 667 REFERENCE "RFC 7455 section 3" 668 ::= { trillOamMepEntry 13 } 670 trillOamMepTxLbmFlowEntropy OBJECT-TYPE 671 SYNTAX OCTET STRING (SIZE (96)) 672 MAX-ACCESS read-create 673 STATUS current 674 DESCRIPTION 675 "96 Byte Flow Entropy as defined in RFC 7455 to be 676 transmitted." 677 REFERENCE "RFC 7455 section 3" 678 ::= { trillOamMepEntry 14 } 680 trillOamMepTxPtmDestRName OBJECT-TYPE 681 SYNTAX Unsigned32 (0..65471) 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "The Target Destination Rbridge NickName Field 686 as defined in RFC 6325 section 3.7 to be transmitted." 687 REFERENCE "RFC 7455 and RFC6325 section 3.7" 688 ::= { trillOamMepEntry 15 } 690 trillOamMepTxPtmHC OBJECT-TYPE 691 SYNTAX Unsigned32 (1..63) 692 MAX-ACCESS read-create 693 STATUS current 694 DESCRIPTION 695 "The Hop Count field to be transmitted." 696 REFERENCE "RFC 7455 section 3" 697 ::= { trillOamMepEntry 16 } 699 trillOamMepTxPtmReplyModeOob OBJECT-TYPE 700 SYNTAX TruthValue 701 MAX-ACCESS read-create 702 STATUS current 703 DESCRIPTION 704 "True Indicates that Reply of Ptm will be made out of 705 band and out of band IP Address TLV is to be 706 transmitted. False indicates that In band reply 707 is transmitted." 708 REFERENCE "RFC 7455 section 10" 709 DEFVAL { false } 710 ::= { trillOamMepEntry 17 } 712 trillOamMepTransmitPtmReplyIp OBJECT-TYPE 713 SYNTAX OCTET STRING (SIZE (4..16)) 714 MAX-ACCESS read-create 715 STATUS current 716 DESCRIPTION 717 "IP address for out of band IP Address TLV is to be 718 Transmitted. The maximum length for IPv6 719 address is 16 Octets. The maximum length 720 for an IPv4 address is 4 octets." 721 REFERENCE "RFC 7455 section 3 and 10" 722 ::= { trillOamMepEntry 18 } 724 trillOamMepTxPtmFlowEntropy OBJECT-TYPE 725 SYNTAX OCTET STRING (SIZE (96)) 726 MAX-ACCESS read-create 727 STATUS current 728 DESCRIPTION 729 "96 Byte Flow Entropy as defined in RFC 7455 to be 730 transmitted." 731 REFERENCE "RFC 7455 section 3" 732 ::= { trillOamMepEntry 19 } 734 trillOamMepTxPtmStatus OBJECT-TYPE 735 SYNTAX TruthValue 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "A Boolean flag set to true by the MEP Path Trace 740 Initiator State 741 Machine or an MIB manager to indicate that another 742 PTM is being transmitted. 743 This is Reset to false by the MEP Initiator 744 State Machine. 745 The PTM managed objects in the MEP table are used 746 in a manner similar to that described for LBM 747 transmission in dot1agCfmMepTable. As per RFC7455 748 section 10, Operation of the Path Trace Message is 749 identical to the Loopback Message except that it is 750 first transmitted with a TRILL Header Hop count 751 field value of 1 and then retransmitted with 752 incrementing Hop count until a response is received 753 from the destination RBridge, or the Hop Count 754 reaches a configured maximum value. 755 trillOamMepTxPtmStatus Status is reset to FALSE 756 by initiator when last PTM is transmitted." 757 REFERENCE "RFC 7455 section 10" 758 DEFVAL { false } 759 ::= { trillOamMepEntry 20 } 761 trillOamMepTxPtmResultOK OBJECT-TYPE 762 SYNTAX TruthValue 763 MAX-ACCESS read-create 764 STATUS current 765 DESCRIPTION 766 "Indicates the following results of the operation: 767 - true The Path Trace Message(s) will be (or has been) 768 sent. 769 - false The Path Trace Message(s) will not be sent." 770 REFERENCE "RFC 7455 section 10" 771 DEFVAL { true } 772 ::= { trillOamMepEntry 21 } 774 trillOamMepTxPtmSeqNumber OBJECT-TYPE 775 SYNTAX Unsigned32 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "The Path Trace Transaction Identifier of the first 780 PTM (to be) sent. The value returned is 781 undefined if trillOamMepTxPtmResultOK is false." 782 REFERENCE "RFC 7455 section 10" 783 ::= { trillOamMepEntry 22 } 785 trillOamMepTxPtmMessages OBJECT-TYPE 786 SYNTAX Integer32 (1..1024) 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "The number of Path Trace messages to be transmitted. 791 As per RFC section 10 first Path Trace Messages 792 is transmitted with Hop count 1 and An RBridge may 793 continue to retransmit the request at periodic 794 interval until response is received from destination 795 Rbridge, or the Hop Count reaches a configured 796 maximum value. The event of the Destination 797 response being received or the Hop count reaching 798 its maximum is treated as single Counter 799 increment of this object, and above process is 800 repeated starting 801 Hop count 1 till maximum PTM transmission 802 is reached. It's treated as Repeat Counter for 803 above described operation." 804 REFERENCE "RFC 7455 section 10" 805 ::= { trillOamMepEntry 23 } 807 trillOamMepTxMtvmTree OBJECT-TYPE 808 SYNTAX Unsigned32 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "The Multi-destination Tree is identifier for tree as 813 defined in RFC6325." 814 ::= { trillOamMepEntry 24 } 816 trillOamMepTxMtvmHC OBJECT-TYPE 817 SYNTAX Unsigned32(1..63) 818 MAX-ACCESS read-create 819 STATUS current 820 DESCRIPTION 821 "The Hop Count field to be transmitted. 822 " 823 REFERENCE "RFC 7455 section 3, RFC 6325 section 3" 824 ::= { trillOamMepEntry 25 } 826 trillOamMepTxMtvmReplyModeOob OBJECT-TYPE 827 SYNTAX TruthValue 828 MAX-ACCESS read-create 829 STATUS current 830 DESCRIPTION 831 "A True Indicates that Reply of Mtvm is out of band and 832 out of band IP Address TLV is to be transmitted. 833 A False indicates that In band reply is transmitted." 834 REFERENCE "RFC 7455 section 11" 835 ::= { trillOamMepEntry 26 } 837 trillOamMepTransmitMtvmReplyIp OBJECT-TYPE 838 SYNTAX OCTET STRING (SIZE (4..16)) 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "IP address for out of band IP Address TLV is to be 843 transmitted. The Maximum length for IPv6 is 16 OCTET 844 and IPv4 is 4 OCTET." 845 REFERENCE "RFC 7455 section 11" 846 ::= { trillOamMepEntry 27 } 848 trillOamMepTxMtvmFlowEntropy OBJECT-TYPE 849 SYNTAX OCTET STRING (SIZE (96)) 850 MAX-ACCESS read-create 851 STATUS current 852 DESCRIPTION 853 "96 Byte Flow Entropy as defined in RFC 7455 to be 854 transmitted." 855 REFERENCE "RFC 7455 section 3" 856 ::= { trillOamMepEntry 28 } 858 trillOamMepTxMtvmStatus OBJECT-TYPE 859 SYNTAX TruthValue 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "A Boolean flag set to true by the MEP Multi Destination 864 Initiator State Machine or an MIB manager to indicate 865 that another Mtvm is being transmitted. 866 Reset to false by the MEP Initiator State Machine. 867 The Mtvm managed objects in the MEP table are used 868 in a manner similar to that described for LBM 869 transmission in dot1agCfmMepTable. As per RFC7455 870 section 11, Operation of the MTvm Message is 871 identical to the Loopback Message except that it is 872 first transmitted with a TRILL Header Hop count 873 field value of 1 and it is retransmitted incrementing 874 Hop count until a response is received from the 875 destination RBridge, or the Hop Count reaches a 876 configured maximum value. trillOamMepTxMtvmStatus 877 Status is reset to FALSE by initiator when last Mtvm 878 is transmitted." 879 REFERENCE "RFC 7455 section 11" 880 DEFVAL { false } 881 ::= { trillOamMepEntry 29 } 883 trillOamMepTxMtvmResultOK OBJECT-TYPE 884 SYNTAX TruthValue 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "Indicates the result of the operation in 889 the following way: 890 - true The Multi-destination Message(s) will be 891 (or has been) sent. 892 - false The Multi-destination Message(s) will not be sent." 893 REFERENCE "RFC 7455 section 11" 894 DEFVAL { true } 895 ::= { trillOamMepEntry 30 } 897 trillOamMepTxMtvmMessages OBJECT-TYPE 898 SYNTAX Integer32 (1..1024) 899 MAX-ACCESS read-create 900 STATUS current 901 DESCRIPTION 902 "The number of Multi Destination messages to be transmitted. 903 The Rbridge transmit the Multi Destination message 904 incrementing the session Identification Number at periodic 905 interval until count expires." 906 REFERENCE "RFC 7455 section 11" 907 ::= { trillOamMepEntry 31 } 909 trillOamMepTxMtvmSeqNumber OBJECT-TYPE 910 SYNTAX Unsigned32 911 MAX-ACCESS read-create 912 STATUS current 913 DESCRIPTION 914 "The Multi-destination Transaction Identifier of the 915 first MTVM (to be) 916 sent. The value returned is undefined if 917 trillOamMepTxMtvmResultOK is false." 918 REFERENCE "RFC 7455 section 11" 919 ::= { trillOamMepEntry 32 } 921 trillOamMepTxMtvmScopeList OBJECT-TYPE 922 SYNTAX OCTET STRING 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "The Multi-destination Rbridge Scope list which 927 requires 2 octets per Rbridge." 928 REFERENCE "RFC 7455 section 11" 929 ::= { trillOamMepEntry 33 } 931 trillOamMepDiscontinuityTime OBJECT-TYPE 932 SYNTAX TimeStamp 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "Snapshot of the value of the sysUpTime object at the 937 beginning of the latest period of continuity of the 938 statistical counters associated with this MEP." 939 ::= { trillOamMepEntry 34 } 941 -- ***************************************************************** 942 -- TRILL OAM Tx Measurement Configuration Table 943 -- ***************************************************************** 945 trillOamMepFlowCfgTable OBJECT-TYPE 946 SYNTAX SEQUENCE OF TrillOamMepFlowCfgEntry 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "This table includes configuration objects and operations 951 for the Trill OAM RFC 7455. 953 Each row in the table represents a Flow configuration 954 Entry for the defined MEP. This table uses four indices. 955 The first three indices are the indices of the Maintenance 956 Domain, MaNet, and MEP tables. The fourth index is the 957 specific flow configuration Entry on the selected MEP. 959 Some writable objects in this table are only applicable in 960 certain cases (as described under each object), and 961 attempts to write values for them in other cases 962 will be ignored." 963 REFERENCE "RFC 7455" 964 ::= { trillOamMep 2 } 966 trillOamMepFlowCfgEntry OBJECT-TYPE 967 SYNTAX TrillOamMepFlowCfgEntry 968 MAX-ACCESS not-accessible 969 STATUS current 970 DESCRIPTION 971 "The conceptual row of trillOamMepFlowCfgTable." 972 INDEX { 973 dot1agCfmMdIndex, 974 dot1agCfmMaIndex, 975 dot1agCfmMepIdentifier, 976 trillOamMepFlowCfgIndex 977 } 978 ::= { trillOamMepFlowCfgTable 1 } 980 TrillOamMepFlowCfgEntry ::= SEQUENCE { 981 trillOamMepFlowCfgIndex Unsigned32, 982 trillOamMepFlowCfgFlowEntropy OCTET STRING, 983 trillOamMepFlowCfgDestRName Unsigned32, 984 trillOamMepFlowCfgFlowHC Unsigned32, 985 trillOamMepFlowCfgRowStatus RowStatus 986 } 988 trillOamMepFlowCfgIndex OBJECT-TYPE 989 SYNTAX Unsigned32 (1..65535) 990 MAX-ACCESS not-accessible 991 STATUS current 992 DESCRIPTION 993 "An index to the Trill OAM MEP Flow Configuration table which 994 indicates the specific Flow for the MEP. 996 The index is never reused for other flow sessions on the 997 same 998 MEP while this session is active. The index value keeps 999 increasing until it wraps to 0. This value can also be 1000 used in Flow-identifier TLV RFC 7455." 1001 REFERENCE "RFC 7455" 1002 ::= { trillOamMepFlowCfgEntry 1 } 1004 trillOamMepFlowCfgFlowEntropy OBJECT-TYPE 1005 SYNTAX OCTET STRING (SIZE (96)) 1006 MAX-ACCESS read-create 1007 STATUS current 1008 DESCRIPTION 1009 "This is 96 byte of Flow Entropy as described in 1010 TRILL OAM RFC 7455." 1011 REFERENCE "RFC 7455 section 3" 1012 ::= { trillOamMepFlowCfgEntry 2 } 1014 trillOamMepFlowCfgDestRName OBJECT-TYPE 1015 SYNTAX Unsigned32 (0..65471) 1016 MAX-ACCESS read-create 1017 STATUS current 1018 DESCRIPTION 1019 "The Target Destination Rbridge NickName Field as 1020 defined in RFC 6325 section 3.7 to be transmitted." 1021 REFERENCE "RFC 7455 section 3 and RFC 6325 section 3.7" 1022 ::= { trillOamMepFlowCfgEntry 3 } 1024 trillOamMepFlowCfgFlowHC OBJECT-TYPE 1025 SYNTAX Unsigned32 (1..63) 1026 MAX-ACCESS read-create 1027 STATUS current 1028 DESCRIPTION 1029 "The Time to Live field to be transmitted. 1030 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 the Trill OAM RFC 7455. 1058 Each row in the table represents a Path Trace Reply Entry for 1059 the defined MEP and Transaction. 1060 This table uses four indices. 1061 The first three indices are the indices of the 1062 Maintenance Domain, 1063 MaNet, and MEP tables. The fourth index is the specific 1064 Transaction Identifier on the selected MEP. 1066 Some writable objects in this table are only applicable in 1067 certain cases (as described under each object), 1068 and attempts to 1069 write values for them in other cases will be ignored." 1070 REFERENCE "RFC 7455" 1071 ::= { trillOamMep 3 } 1073 trillOamPtrEntry OBJECT-TYPE 1074 SYNTAX TrillOamPtrEntry 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "The conceptual row of trillOamPtrTable." 1079 INDEX { 1080 dot1agCfmMdIndex, 1081 dot1agCfmMaIndex, 1082 dot1agCfmMepIdentifier, 1083 trillOamMepPtrTransactionId 1084 } 1085 ::= { trillOamPtrTable 1 } 1087 TrillOamPtrEntry ::= SEQUENCE { 1088 trillOamMepPtrTransactionId Unsigned32, 1089 trillOamMepPtrHC Unsigned32, 1090 trillOamMepPtrFlag Unsigned32, 1091 trillOamMepPtrErrorCode Unsigned32, 1092 trillOamMepPtrTerminalMep TruthValue, 1093 trillOamMepPtrLastEgressId Unsigned32, 1094 trillOamMepPtrIngress Dot1agCfmIngressActionFieldValue, 1095 trillOamMepPtrIngressMac MacAddress, 1096 trillOamMepPtrIngressPortIdSubtype LldpPortIdSubtype, 1097 trillOamMepPtrIngressPortId LldpPortId, 1098 trillOamMepPtrEgress Dot1agCfmEgressActionFieldValue, 1099 trillOamMepPtrEgressMac MacAddress, 1100 trillOamMepPtrEgressPortIdSubtype LldpPortIdSubtype, 1101 trillOamMepPtrEgressPortId LldpPortId, 1102 trillOamMepPtrChassisIdSubtype LldpChassisIdSubtype, 1103 trillOamMepPtrChassisId LldpChassisId, 1104 trillOamMepPtrOrganizationSpecificTlv OCTET STRING, 1105 trillOamMepPtrNextHopNicknames OCTET STRING 1106 } 1108 trillOamMepPtrTransactionId OBJECT-TYPE 1109 SYNTAX Unsigned32 (0..4294967295) 1110 MAX-ACCESS not-accessible 1111 STATUS current 1112 DESCRIPTION 1113 "Transaction identifier/sequence number returned by a 1114 previous transmit path trace message command, 1115 indicating which PTM's response is going to be returned." 1116 REFERENCE "RFC 7455 section 10" 1117 ::= { trillOamPtrEntry 1 } 1119 trillOamMepPtrHC OBJECT-TYPE 1120 SYNTAX Unsigned32 (1..63) 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "Hop Count field value for a returned PTR." 1125 REFERENCE "RFC 7455" 1126 ::= { trillOamPtrEntry 2 } 1128 trillOamMepPtrFlag OBJECT-TYPE 1129 SYNTAX Unsigned32 (0..15) 1130 MAX-ACCESS read-only 1131 STATUS current 1132 DESCRIPTION 1133 "FCOI (TRILL OAM Message TLV) field value for a 1134 returned PTR." 1135 REFERENCE "RFC 7455, 8.4.3" 1136 ::= { trillOamPtrEntry 3 } 1138 trillOamMepPtrErrorCode OBJECT-TYPE 1139 SYNTAX Unsigned32 (0..65535) 1140 MAX-ACCESS read-only 1141 STATUS current 1142 DESCRIPTION 1143 "Return Code and Return Sub code value for a returned PTR." 1144 REFERENCE "RFC 7455, 8.4.3" 1145 ::= { trillOamPtrEntry 4 } 1147 trillOamMepPtrTerminalMep OBJECT-TYPE 1148 SYNTAX TruthValue 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "A boolean value stating whether the forwarded PTM reached a 1153 MEP enclosing its MA, as returned in the Terminal MEP flag of 1154 the Flags field." 1155 REFERENCE "RFC 7455" 1156 ::= { trillOamPtrEntry 5 } 1158 trillOamMepPtrLastEgressId OBJECT-TYPE 1159 SYNTAX Unsigned32 (0..65535) 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "An Integer field holding the Last Egress Identifier returned 1164 in the PTR Upstream Rbridge nickname TLV of the PTR. 1165 The Last Egress Identifier identifies the Upstream Nickname." 1166 REFERENCE "RFC 7455 8.4.1" 1167 ::= { trillOamPtrEntry 6 } 1169 trillOamMepPtrIngress OBJECT-TYPE 1170 SYNTAX Dot1agCfmIngressActionFieldValue 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "The value returned in the Ingress Action Field of the PTR. 1175 The value ingNoTlv(0) indicates that no Reply Ingress TLV was 1176 returned in the PTM." 1177 REFERENCE "RFC 7455 8.4.1" 1178 ::= { trillOamPtrEntry 7 } 1180 trillOamMepPtrIngressMac OBJECT-TYPE 1181 SYNTAX MacAddress 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "MAC address returned in the ingress MAC address field." 1186 REFERENCE "RFC 7455 8.4.1" 1187 ::= { trillOamPtrEntry 8 } 1189 trillOamMepPtrIngressPortIdSubtype OBJECT-TYPE 1190 SYNTAX LldpPortIdSubtype 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "Ingress Port ID. The format of this object is determined by 1195 the value of the trillOamMepPtrIngressPortIdSubtype object." 1196 REFERENCE "RFC 7455 8.4.1" 1197 ::= { trillOamPtrEntry 9 } 1199 trillOamMepPtrIngressPortId OBJECT-TYPE 1200 SYNTAX LldpPortId 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 trillOamMepPtrIngressPortId object." 1206 REFERENCE "RFC 7455 8.4.1" 1207 ::= { trillOamPtrEntry 10 } 1209 trillOamMepPtrEgress OBJECT-TYPE 1210 SYNTAX Dot1agCfmEgressActionFieldValue 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The value returned in the Egress Action Field of the PTR. 1215 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1216 returned in the PTM." 1217 REFERENCE "RFC 7455 8.4.1" 1218 ::= { trillOamPtrEntry 11 } 1220 trillOamMepPtrEgressMac OBJECT-TYPE 1221 SYNTAX MacAddress 1222 MAX-ACCESS read-only 1223 STATUS current 1224 DESCRIPTION 1225 "MAC address returned in the egress MAC address field." 1226 REFERENCE "RFC 7455 8.4.1" 1227 ::= { trillOamPtrEntry 12 } 1229 trillOamMepPtrEgressPortIdSubtype OBJECT-TYPE 1230 SYNTAX LldpPortIdSubtype 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "Egress Port ID. The format of this object is determined by 1235 the value of the trillOamMepPtrEgressPortIdSubtype object." 1236 REFERENCE "RFC 7455 8.4.1" 1237 ::= { trillOamPtrEntry 13 } 1239 trillOamMepPtrEgressPortId OBJECT-TYPE 1240 SYNTAX LldpPortId 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 trillOamMepPtrEgressPortId object." 1246 REFERENCE "RFC 7455 8.4.1" 1247 ::= { trillOamPtrEntry 14 } 1249 trillOamMepPtrChassisIdSubtype OBJECT-TYPE 1250 SYNTAX LldpChassisIdSubtype 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "This object specifies the format of the Chassis ID returned 1255 in the Sender ID TLV of the PTR, if any. This value is 1256 meaningless if the trillOamMepPtrChassisId 1257 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 RFC 7455. 1306 Each row in the table represents a Multi-destination Reply 1307 Entry for the defined MEP and Transaction. 1308 This table uses five indices. 1309 The first three indices are the indices of the 1310 Maintenance Domain, 1311 MaNet, and MEP tables. The fourth index is the specific 1312 Transaction Identifier on the selected MEP. 1313 The fifth index is the receive order of Multi-destination 1314 replies. 1316 Some writable objects in this table are only applicable in 1317 certain cases (as described under each object), 1318 and attempts to 1319 write values for them in other cases will be ignored." 1320 REFERENCE "RFC 7455" 1321 ::= { trillOamMep 4 } 1323 trillOamMtvrEntry OBJECT-TYPE 1324 SYNTAX TrillOamMtvrEntry 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "The conceptual row of trillOamMtvrTable." 1329 INDEX { 1330 dot1agCfmMdIndex, 1331 dot1agCfmMaIndex, 1332 dot1agCfmMepIdentifier, 1333 trillOamMepPtrTransactionId, 1334 trillOamMepMtvrReceiveOrder 1335 } 1336 ::= { trillOamMtvrTable 1 } 1338 TrillOamMtvrEntry ::= SEQUENCE { 1339 trillOamMepMtvrTransactionId Unsigned32, 1340 trillOamMepMtvrReceiveOrder Unsigned32, 1341 trillOamMepMtvrFlag Unsigned32, 1342 trillOamMepMtvrErrorCode Unsigned32, 1343 trillOamMepMtvrLastEgressId Unsigned32, 1344 trillOamMepMtvrIngress Dot1agCfmIngressActionFieldValue, 1345 trillOamMepMtvrIngressMac MacAddress, 1346 trillOamMepMtvrIngressPortIdSubtype LldpPortIdSubtype, 1347 trillOamMepMtvrIngressPortId LldpPortId, 1348 trillOamMepMtvrEgress Dot1agCfmEgressActionFieldValue, 1349 trillOamMepMtvrEgressMac MacAddress, 1350 trillOamMepMtvrEgressPortIdSubtype LldpPortIdSubtype, 1351 trillOamMepMtvrEgressPortId LldpPortId, 1352 trillOamMepMtvrChassisIdSubtype LldpChassisIdSubtype, 1353 trillOamMepMtvrChassisId LldpChassisId, 1354 trillOamMepMtvrOrganizationSpecificTlv OCTET STRING, 1355 trillOamMepMtvrNextHopNicknames OCTET STRING, 1356 trillOamMepMtvrReceiverAvailability TruthValue, 1357 trillOamMepMtvrReceiverCount TruthValue 1358 } 1360 trillOamMepMtvrTransactionId OBJECT-TYPE 1361 SYNTAX Unsigned32 (0..4294967295) 1362 MAX-ACCESS not-accessible 1363 STATUS current 1364 DESCRIPTION 1365 "Transaction identifier/sequence number returned by a 1366 previous 1367 transmit Multi-destination message command, indicating 1368 which MTVM's response is going to be returned." 1369 REFERENCE "RFC 7455 section 11" 1370 ::= { trillOamMtvrEntry 1 } 1372 trillOamMepMtvrReceiveOrder OBJECT-TYPE 1373 SYNTAX Unsigned32 (1..4294967295) 1374 MAX-ACCESS not-accessible 1375 STATUS current 1376 DESCRIPTION 1377 "An index to distinguish among multiple MTVR with same 1378 MTVR Transaction Identifier field value. 1379 trillOamMepMtvrReceiveOrder are assigned sequentially 1380 from 1, 1381 in the order that the Multi-destination Tree Initiator 1382 received the MTVRs." 1383 REFERENCE "RFC 7455 section 11" 1384 ::= { trillOamMtvrEntry 2 } 1386 trillOamMepMtvrFlag OBJECT-TYPE 1387 SYNTAX Unsigned32 (0..15) 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "FCOI (TRILL OAM Message TLV) field value for a 1392 returned MTVR." 1393 REFERENCE "RFC 7455, 8.4.2" 1394 ::= { trillOamMtvrEntry 3 } 1396 trillOamMepMtvrErrorCode OBJECT-TYPE 1397 SYNTAX Unsigned32 (0..65535) 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "Return Code and Return Sub code value for a returned MTVR." 1402 REFERENCE "RFC 7455, 8.4.2" 1403 ::= { trillOamMtvrEntry 4 } 1405 trillOamMepMtvrLastEgressId OBJECT-TYPE 1406 SYNTAX Unsigned32 (0..65535) 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "An Integer field holding the Last Egress Identifier 1411 returned in the MTVR Upstream Rbridge Nickname TLV 1412 of the MTVR. 1413 The Last Egress Identifier identifies the 1414 Upstream Nickname." 1415 REFERENCE "RFC 7455 8.4.1" 1416 ::= { trillOamMtvrEntry 5 } 1418 trillOamMepMtvrIngress OBJECT-TYPE 1419 SYNTAX Dot1agCfmIngressActionFieldValue 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION 1423 "The value returned in the Ingress Action Field of 1424 the MTVR. 1425 The value ingNoTlv(0) indicates that no 1426 Reply Ingress TLV was returned in the MTVM." 1427 REFERENCE "RFC 7455 11.2.3" 1428 ::= { trillOamMtvrEntry 6 } 1430 trillOamMepMtvrIngressMac OBJECT-TYPE 1431 SYNTAX MacAddress 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "MAC address returned in the ingress MAC address field." 1436 REFERENCE "RFC 7455 8.4.1" 1437 ::= { trillOamMtvrEntry 7 } 1439 trillOamMepMtvrIngressPortIdSubtype OBJECT-TYPE 1440 SYNTAX LldpPortIdSubtype 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "Ingress Port ID. The format of this object is 1445 determined by 1447 the value of the trillOamMepMtvrIngressPortIdSubtype 1448 object." 1449 REFERENCE "RFC 7455 8.4.1" 1450 ::= { trillOamMtvrEntry 8 } 1452 trillOamMepMtvrIngressPortId OBJECT-TYPE 1453 SYNTAX LldpPortId 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "Ingress Port ID. The format of this object is determined by 1458 the value of the trillOamMepMtvrIngressPortId object." 1459 REFERENCE "RFC 7455 8.4.1" 1460 ::= { trillOamMtvrEntry 9 } 1462 trillOamMepMtvrEgress OBJECT-TYPE 1463 SYNTAX Dot1agCfmEgressActionFieldValue 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "The value returned in the Egress Action Field of the MTVR. 1468 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1469 returned in the MTVR." 1470 REFERENCE "RFC 7455 8.4.1" 1471 ::= { trillOamMtvrEntry 10 } 1473 trillOamMepMtvrEgressMac OBJECT-TYPE 1474 SYNTAX MacAddress 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "MAC address returned in the egress MAC address field." 1479 REFERENCE "RFC 7455 8.4.1" 1480 ::= { trillOamMtvrEntry 11 } 1482 trillOamMepMtvrEgressPortIdSubtype OBJECT-TYPE 1483 SYNTAX LldpPortIdSubtype 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 trillOamMepMtvrEgressPortIdSubtype object." 1489 REFERENCE "RFC 7455 8.4.1" 1490 ::= { trillOamMtvrEntry 12 } 1492 trillOamMepMtvrEgressPortId OBJECT-TYPE 1493 SYNTAX LldpPortId 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 trillOamMepMtvrEgressPortId object." 1499 REFERENCE "RFC 7455 8.4.1" 1500 ::= { trillOamMtvrEntry 13 } 1502 trillOamMepMtvrChassisIdSubtype OBJECT-TYPE 1503 SYNTAX LldpChassisIdSubtype 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This object specifies the format of the Chassis ID returned 1508 in the Sender ID TLV of the MTVR, if any. This value is 1509 meaningless if the trillOamMepMtvrChassisId has a 1510 length of 0." 1511 REFERENCE "RFC 7455 8.4.1" 1512 ::= { trillOamMtvrEntry 14 } 1514 trillOamMepMtvrChassisId OBJECT-TYPE 1515 SYNTAX LldpChassisId 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "The Chassis ID returned in the Sender ID TLV of the MTVR, if 1520 any. The format of this object is determined by the 1521 value of the trillOamMepMtvrChassisIdSubtype object." 1522 REFERENCE "RFC 7455 8.4.1" 1523 ::= { trillOamMtvrEntry 15 } 1525 trillOamMepMtvrOrganizationSpecificTlv OBJECT-TYPE 1526 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "All Organization specific TLVs returned in the MTVR, if 1531 any. Includes all octets including and following the TLV 1532 Length field of each TLV, concatenated together." 1533 REFERENCE "RFC 7455 8.4.1" 1534 ::= { trillOamMtvrEntry 16 } 1536 trillOamMepMtvrNextHopNicknames OBJECT-TYPE 1537 SYNTAX OCTET STRING (SIZE (0 | 4..1500)) 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "Next hop Rbridge List TLV returned in the PTR, if 1542 any. Includes all octets including and following the TLV 1543 Length field of each TLV, concatenated together." 1544 REFERENCE "RFC 7455 8.4.3" 1545 ::= { trillOamMtvrEntry 17 } 1547 trillOamMepMtvrReceiverAvailability OBJECT-TYPE 1548 SYNTAX TruthValue 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "True value indicates that MTVR response contained 1553 Multicast receiver availability TLV." 1554 REFERENCE "RFC 7455 8.4.10" 1555 ::= { trillOamMtvrEntry 18 } 1557 trillOamMepMtvrReceiverCount OBJECT-TYPE 1558 SYNTAX TruthValue 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "Indicates the number of Multicast receivers available on 1563 responding RBridge on the VLAN specified by the 1564 diagnostic VLAN." 1565 REFERENCE "RFC 7455 8.4.10" 1566 ::= { trillOamMtvrEntry 19 } 1568 -- ***************************************************************** 1569 -- TRILL OAM MEP Database Table 1570 -- ***************************************************************** 1572 trillOamMepDbTable OBJECT-TYPE 1573 SYNTAX SEQUENCE OF TrillOamMepDbEntry 1574 MAX-ACCESS not-accessible 1575 STATUS current 1576 DESCRIPTION 1577 "This table is an extension of the dot1agCfmMepDbTable 1578 and rows 1579 are automatically added to or deleted from this table based 1580 upon row creation and destruction of the 1581 dot1agCfmMepDbTable." 1582 REFERENCE 1583 "RFC 7455" 1584 ::= { trillOamMep 5 } 1586 trillOamMepDbEntry OBJECT-TYPE 1587 SYNTAX TrillOamMepDbEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "The conceptual row of trillOamMepDbTable." 1592 AUGMENTS { 1593 dot1agCfmMepDbEntry 1594 } 1595 ::= { trillOamMepDbTable 1 } 1597 TrillOamMepDbEntry ::= SEQUENCE { 1598 trillOamMepDbFlowIndex Unsigned32, 1599 trillOamMepDbFlowEntropy OCTET STRING, 1600 trillOamMepDbFlowState Dot1agCfmRemoteMepState, 1601 trillOamMepDbFlowFailedOkTime TimeStamp, 1602 trillOamMepDbRbridgeName Unsigned32, 1603 trillOamMepDbLastGoodSeqNum Counter32 1604 } 1606 trillOamMepDbFlowIndex OBJECT-TYPE 1607 SYNTAX Unsigned32 (1..65535) 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "This object identifies the Flow. If Flow Identifier TLV 1612 is received 1613 than index received can also be used." 1614 REFERENCE "RFC 7455" 1615 ::= {trillOamMepDbEntry 1 } 1617 trillOamMepDbFlowEntropy OBJECT-TYPE 1618 SYNTAX OCTET STRING (SIZE (96)) 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "96 byte Flow Entropy." 1623 REFERENCE "RFC 7455 section 3." 1624 ::= {trillOamMepDbEntry 2 } 1626 trillOamMepDbFlowState OBJECT-TYPE 1627 SYNTAX Dot1agCfmRemoteMepState 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "The operational state of the remote MEP (flow based) 1632 IFF State machines. State Machine is running now per 1633 flow." 1634 REFERENCE "RFC 7455" 1635 ::= {trillOamMepDbEntry 3 } 1637 trillOamMepDbFlowFailedOkTime OBJECT-TYPE 1638 SYNTAX TimeStamp 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "The Time (sysUpTime) at which the Remote MEP Flow state 1643 machine last entered either the RMEP_FAILED or RMEP_OK 1644 state." 1645 REFERENCE "RFC 7455" 1646 ::= {trillOamMepDbEntry 4 } 1648 trillOamMepDbRbridgeName OBJECT-TYPE 1649 SYNTAX Unsigned32(0..65471) 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "Remote MEP Rbridge Nickname." 1654 REFERENCE "RFC 7455 RFC 6325 section 3" 1655 ::= {trillOamMepDbEntry 5 } 1657 trillOamMepDbLastGoodSeqNum OBJECT-TYPE 1658 SYNTAX Counter32 1659 MAX-ACCESS read-only 1660 STATUS current 1661 DESCRIPTION 1662 "Last Sequence Number received." 1663 REFERENCE "RFC 7455 13.1" 1664 ::= {trillOamMepDbEntry 6} 1666 -- ****************************************************************** 1667 -- TRILL OAM MIB NOTIFICATIONS (TRAPS) 1668 -- This notification is sent to management entity whenever a 1669 -- MEP loses/restores 1670 -- contact with its peer Flow Meps 1671 -- ****************************************************************** 1672 trillOamFaultAlarm NOTIFICATION-TYPE 1673 OBJECTS { trillOamMepDbFlowState } 1674 STATUS current 1675 DESCRIPTION 1676 "A MEP Flow has a persistent defect condition. 1677 A notification (fault alarm) is sent to the management 1678 entity with the OID of the Flow that has detected the fault. 1680 The management entity receiving the notification can identify 1681 the system from the network source address of the 1682 notification, and can identify the Flow reporting the defect 1683 by the indices in the OID of the 1684 trillOamMepFlowIndex, and trillOamFlowDefect 1685 variable in the notification: 1687 dot1agCfmMdIndex - Also the index of the MEP's 1688 Maintenance Domain table entry 1689 (dot1agCfmMdTable). 1690 dot1agCfmMaIndex - Also an index (with the MD table index) 1691 of the MEP's Maintenance Association 1692 network table entry 1693 (dot1agCfmMaNetTable), and (with the MD 1694 table index and component ID) of the 1695 MEP's MA component table entry 1696 (dot1agCfmMaCompTable). 1697 dot1agCfmMepIdentifier - MEP Identifier and final index 1698 into the MEP table (dot1agCfmMepTable). 1699 trillOamMepFlowCfgIndex - Index identifies 1700 indicates the specific Flow for 1701 the MEP" 1702 REFERENCE "RFC 7455" 1703 ::= { trillOamNotifications 1 } 1705 -- ****************************************************************** 1706 -- TRILL OAM MIB Module - Conformance Information 1707 -- ****************************************************************** 1709 trillOamMibCompliances OBJECT IDENTIFIER 1710 ::= { trillOamMibConformance 1 } 1712 trillOamMibGroups OBJECT IDENTIFIER 1713 ::= { trillOamMibConformance 2 } 1715 -- ****************************************************************** 1716 -- TRILL OAM MIB Units of conformance 1717 -- ****************************************************************** 1719 trillOamMepMandatoryGroup OBJECT-GROUP 1720 OBJECTS { 1721 trillOamMepRName, 1722 trillOamMepNextPtmTId, 1723 trillOamMepNextMtvmTId, 1724 trillOamMepPtrIn, 1725 trillOamMepPtrInOutofOrder, 1726 trillOamMepPtrOut, 1727 trillOamMepMtvrIn, 1728 trillOamMepMtvrInOutofOrder, 1729 trillOamMepMtvrOut, 1730 trillOamMepTxLbmDestRName, 1731 trillOamMepTxLbmHC, 1732 trillOamMepTxLbmReplyModeOob, 1733 trillOamMepTransmitLbmReplyIp, 1734 trillOamMepTxLbmFlowEntropy, 1735 trillOamMepTxPtmDestRName, 1736 trillOamMepTxPtmHC, 1737 trillOamMepTxPtmReplyModeOob, 1738 trillOamMepTransmitPtmReplyIp, 1739 trillOamMepTxPtmFlowEntropy, 1740 trillOamMepTxPtmStatus, 1741 trillOamMepTxPtmResultOK, 1742 trillOamMepTxPtmMessages, 1743 trillOamMepTxPtmSeqNumber, 1744 trillOamMepTxMtvmTree, 1745 trillOamMepTxMtvmHC, 1746 trillOamMepTxMtvmReplyModeOob, 1747 trillOamMepTransmitMtvmReplyIp, 1748 trillOamMepTxMtvmFlowEntropy, 1749 trillOamMepTxMtvmStatus, 1750 trillOamMepTxMtvmResultOK, 1751 trillOamMepTxMtvmMessages, 1752 trillOamMepTxMtvmSeqNumber, 1753 trillOamMepTxMtvmScopeList, 1754 trillOamMepDiscontinuityTime 1755 } 1756 STATUS current 1757 DESCRIPTION 1758 "Mandatory objects for the TRILL OAM MEP group." 1759 ::= { trillOamMibGroups 1 } 1761 trillOamMepFlowCfgTableGroup OBJECT-GROUP 1762 OBJECTS { 1763 trillOamMepFlowCfgFlowEntropy, 1764 trillOamMepFlowCfgDestRName, 1765 trillOamMepFlowCfgFlowHC, 1766 trillOamMepFlowCfgRowStatus 1767 } 1768 STATUS current 1769 DESCRIPTION 1770 "Trill OAM MEP Flow Configuration objects group." 1771 ::= { trillOamMibGroups 2 } 1773 trillOamPtrTableGroup OBJECT-GROUP 1774 OBJECTS { 1775 trillOamMepPtrHC, 1776 trillOamMepPtrFlag, 1777 trillOamMepPtrErrorCode, 1778 trillOamMepPtrTerminalMep, 1779 trillOamMepPtrLastEgressId, 1780 trillOamMepPtrIngress, 1781 trillOamMepPtrIngressMac, 1782 trillOamMepPtrIngressPortIdSubtype, 1783 trillOamMepPtrIngressPortId, 1784 trillOamMepPtrEgress, 1785 trillOamMepPtrEgressMac, 1786 trillOamMepPtrEgressPortIdSubtype, 1787 trillOamMepPtrEgressPortId, 1788 trillOamMepPtrChassisIdSubtype, 1789 trillOamMepPtrChassisId, 1790 trillOamMepPtrOrganizationSpecificTlv, 1791 trillOamMepPtrNextHopNicknames 1792 } 1793 STATUS current 1794 DESCRIPTION 1795 "Trill OAM MEP PTR objects group." 1796 ::= { trillOamMibGroups 3 } 1798 trillOamMtvrTableGroup OBJECT-GROUP 1799 OBJECTS { 1800 trillOamMepMtvrFlag, 1801 trillOamMepMtvrErrorCode, 1802 trillOamMepMtvrLastEgressId, 1803 trillOamMepMtvrIngress, 1804 trillOamMepMtvrIngressMac, 1805 trillOamMepMtvrIngressPortIdSubtype, 1806 trillOamMepMtvrIngressPortId, 1807 trillOamMepMtvrEgress, 1808 trillOamMepMtvrEgressMac, 1809 trillOamMepMtvrEgressPortIdSubtype, 1810 trillOamMepMtvrEgressPortId, 1811 trillOamMepMtvrChassisIdSubtype, 1812 trillOamMepMtvrChassisId, 1813 trillOamMepMtvrOrganizationSpecificTlv, 1814 trillOamMepMtvrNextHopNicknames, 1815 trillOamMepMtvrReceiverAvailability, 1816 trillOamMepMtvrReceiverCount 1817 } 1818 STATUS current 1819 DESCRIPTION 1820 "Trill OAM MEP MTVR objects group." 1821 ::= { trillOamMibGroups 4 } 1823 trillOamMepDbGroup OBJECT-GROUP 1824 OBJECTS { 1825 trillOamMepDbFlowIndex, 1826 trillOamMepDbFlowEntropy, 1827 trillOamMepDbFlowState, 1828 trillOamMepDbFlowFailedOkTime, 1829 trillOamMepDbRbridgeName, 1830 trillOamMepDbLastGoodSeqNum 1831 } 1833 STATUS current 1834 DESCRIPTION 1835 "Trill OAM MEP DB objects group." 1836 ::= { trillOamMibGroups 5 } 1838 trillOamNotificationGroup NOTIFICATION-GROUP 1839 NOTIFICATIONS { trillOamFaultAlarm } 1840 STATUS current 1841 DESCRIPTION 1842 "A collection of objects describing notifications(traps)." 1843 ::= { trillOamMibGroups 6 } 1845 -- ****************************************************************** 1846 -- TRILL OAM MIB Module Compliance statements 1847 -- ****************************************************************** 1849 trillOamMibCompliance MODULE-COMPLIANCE 1850 STATUS current 1851 DESCRIPTION 1852 "The compliance statement for the TRILL OAM MIB." 1853 MODULE -- this module 1854 MANDATORY-GROUPS { 1855 trillOamMepMandatoryGroup, 1856 trillOamMepFlowCfgTableGroup, 1857 trillOamPtrTableGroup, 1858 trillOamMtvrTableGroup, 1859 trillOamMepDbGroup, 1860 trillOamNotificationGroup 1861 } 1862 ::= { trillOamMibCompliances 1 } 1864 -- Compliance requirement for read-only implementation. 1866 trillOamMibReadOnlyCompliance MODULE-COMPLIANCE 1867 STATUS current 1868 DESCRIPTION 1869 "Compliance requirement for implementation that only 1870 provide read-only support for TRILL-OAM-MIB. 1871 Such devices can be monitored but cannot be configured 1872 using this MIB module." 1873 MODULE -- this module 1874 MANDATORY-GROUPS { 1875 trillOamMepMandatoryGroup, 1876 trillOamMepFlowCfgTableGroup, 1877 trillOamPtrTableGroup, 1878 trillOamMtvrTableGroup, 1879 trillOamMepDbGroup, 1880 trillOamNotificationGroup 1881 } 1882 -- trillOamMepTable 1884 OBJECT trillOamMepTxLbmDestRName 1885 MIN-ACCESS read-only 1886 DESCRIPTION 1887 "Write access is not required." 1889 OBJECT trillOamMepTxLbmHC 1890 MIN-ACCESS read-only 1891 DESCRIPTION 1892 "Write access is not required." 1894 OBJECT trillOamMepTxLbmReplyModeOob 1895 MIN-ACCESS read-only 1896 DESCRIPTION 1897 "Write access is not required." 1899 OBJECT trillOamMepTransmitLbmReplyIp 1900 MIN-ACCESS read-only 1901 DESCRIPTION 1902 "Write access is not required." 1904 OBJECT trillOamMepTxLbmFlowEntropy 1905 MIN-ACCESS read-only 1906 DESCRIPTION 1907 "Write access is not required." 1909 OBJECT trillOamMepTxPtmDestRName 1910 MIN-ACCESS read-only 1911 DESCRIPTION 1912 "Write access is not required." 1914 OBJECT trillOamMepTxPtmHC 1915 MIN-ACCESS read-only 1916 DESCRIPTION 1917 "Write access is not required." 1919 OBJECT trillOamMepTxPtmReplyModeOob 1920 MIN-ACCESS read-only 1921 DESCRIPTION 1922 "Write access is not required." 1924 OBJECT trillOamMepTransmitPtmReplyIp 1925 MIN-ACCESS read-only 1926 DESCRIPTION 1927 "Write access is not required." 1929 OBJECT trillOamMepTxPtmFlowEntropy 1930 MIN-ACCESS read-only 1931 DESCRIPTION 1932 "Write access is not required." 1934 OBJECT trillOamMepTxPtmStatus 1935 MIN-ACCESS read-only 1936 DESCRIPTION 1937 "Write access is not required." 1939 OBJECT trillOamMepTxPtmResultOK 1940 MIN-ACCESS read-only 1941 DESCRIPTION 1942 "Write access is not required." 1944 OBJECT trillOamMepTxPtmMessages 1945 MIN-ACCESS read-only 1946 DESCRIPTION 1947 "Write access is not required." 1949 OBJECT trillOamMepTxPtmSeqNumber 1950 MIN-ACCESS read-only 1951 DESCRIPTION 1952 "Write access is not required." 1954 OBJECT trillOamMepTxMtvmTree 1955 MIN-ACCESS read-only 1956 DESCRIPTION 1957 "Write access is not required." 1959 OBJECT trillOamMepTxMtvmHC 1960 MIN-ACCESS read-only 1961 DESCRIPTION 1962 "Write access is not required." 1964 OBJECT trillOamMepTxMtvmReplyModeOob 1965 MIN-ACCESS read-only 1966 DESCRIPTION 1967 "Write access is not required." 1969 OBJECT trillOamMepTransmitMtvmReplyIp 1970 MIN-ACCESS read-only 1971 DESCRIPTION 1972 "Write access is not required." 1974 OBJECT trillOamMepTxMtvmFlowEntropy 1975 MIN-ACCESS read-only 1976 DESCRIPTION 1977 "Write access is not required." 1979 OBJECT trillOamMepTxMtvmStatus 1980 MIN-ACCESS read-only 1981 DESCRIPTION 1982 "Write access is not required." 1984 OBJECT trillOamMepTxMtvmResultOK 1985 MIN-ACCESS read-only 1986 DESCRIPTION 1987 "Write access is not required." 1989 OBJECT trillOamMepTxMtvmMessages 1990 MIN-ACCESS read-only 1991 DESCRIPTION 1992 "Write access is not required." 1994 OBJECT trillOamMepTxMtvmSeqNumber 1995 MIN-ACCESS read-only 1996 DESCRIPTION 1997 "Write access is not required." 1999 OBJECT trillOamMepTxMtvmScopeList 2000 MIN-ACCESS read-only 2001 DESCRIPTION 2002 "Write access is not required." 2004 -- trillOamMepFlowCfgTable 2006 OBJECT trillOamMepFlowCfgFlowEntropy 2007 MIN-ACCESS read-only 2008 DESCRIPTION 2009 "Write access is not required." 2011 OBJECT trillOamMepFlowCfgDestRName 2012 MIN-ACCESS read-only 2013 DESCRIPTION 2014 "Write access is not required." 2016 OBJECT trillOamMepFlowCfgFlowHC 2017 MIN-ACCESS read-only 2018 DESCRIPTION 2019 "Write access is not required." 2021 OBJECT trillOamMepFlowCfgRowStatus 2022 MIN-ACCESS read-only 2023 DESCRIPTION 2024 "Write access is not required." 2026 ::= { trillOamMibCompliances 2 } 2028 END 2030 8. Security Considerations 2032 This MIB relates to a system that will provide network connectivity 2033 and packet forwarding services. As such, improper manipulation of the 2034 objects represented by this MIB may result in denial of service to a 2035 large number of end-users. 2037 There are number of management objects defined in this MIB module 2038 with a MAX-ACCESS clause of read-create. Such objects may be 2039 considered sensitive or vulnerable in some network environments. The 2040 support for SET operations in a non-secure environment without proper 2041 protection can have negative effect on sensitivity/vulnerability: 2043 The following table and objects in the TRILL-OAM-MIB can be 2044 manipulated to interfere with the operation of RBridges by causing 2045 cpu spike: 2047 o trillOamMepTransmitLbmReplyIp allows reply of Loopback message to 2048 be transmitted to Ip address in the TLV and thus allowing replies to 2049 be sent to any system or single single system to cause Denial of 2050 Service. 2052 o trillOamMepTransmitPtmReplyIp allows reply of Path Trace message to 2053 be transmitted to Ip address in the TLV and thus allowing replies to 2054 be sent to any system or single single system to cause Denial of 2055 Service. 2057 o trillOamMepTxPtmMessages allows generation of Ptm Messages and can 2058 be used to generate lots of cpu driven traffic. 2060 o trillOamMepTransmitMtvmReplyIp allows reply of Mtv message to be 2061 transmitted to Ip address in the TLV and thus allowing replies to be 2062 sent to any system or single single system to cause Denial of 2063 Service. 2065 o trillOamMepTxMtvmMessages allows generation of Mtv Messages and can 2066 be used to generate lots of cpu driven traffic. 2068 The following objects in the TRILL-OAM-MIB are read-create and can be 2069 manipulated to interfere with the OAM operations of RBridges only. If 2070 number of OAM frames are generated in network is high that can cause 2071 cpu spike on Destination Rbridges if Control plane policing 2072 implementation is not properly configured on destination Rbridges. 2074 o trillOamMepTxLbmHC: is used to set the Maximum Hop count for the 2075 LBM message. As OAM frame doesn't leak out of the Trill network it 2076 has no side effect. 2078 o trillOamMepTxLbmReplyModeOob is used to indicate the reply is in- 2079 band or out-of-band. This object vulnerability is covered as part of 2080 trillOamMepTransmitLbmReplyIp. 2082 o trillOamMepTxLbmFlowEntropy is used to indicate customer flow and 2083 find the exact path in the network, creation of valid flows is 2084 intended purpose, if invalid flows are created on vulnerable system 2085 they will be dropped in forwarding. 2087 o trillOamMepTxLbmDestRName is read-create but it's not vulnerable as 2088 invalid name route won't be present and will be rejected by the OAM 2089 application as normal processing. 2091 o trillOamMepTxPtmHC: is used to set the Maximum Hop count for the 2092 PTM message. As OAM frame doesn't leak out of the Trill network it 2093 has no side effect. 2095 o trillOamMepTxPtmReplyModeOob is used to indicate the reply is in- 2096 band or out-of-band. This object vulnerability is covered as part of 2097 trillOamMepTransmitPtmReplyIp. 2099 o trillOamMepTxPtmFlowEntropy is used to indicate customer flow and 2100 find the exact path in the network, creation of valid flows is 2101 intended purpose, if invalid flows are created on vulnerable system 2102 they will be dropped in forwarding. 2104 o trillOamMepTxPtmDestRName is read-create but it's not vulnerable as 2105 invalid name route won't be present and will be rejected by the OAM 2106 application as normal processing. 2108 o trillOamMepTxPtmStatus is required for normal Ptm operation. 2110 o trillOamMepTxPtmResultOK is required for normal Ptm operation. 2112 o trillOamMepTxPtmSeqNumber is required for normal Ptm operation. 2114 o trillOamMepTxPtmMessages is required for normal Ptm operation. 2116 o trillOamMepTxMtvmTree is required for normal Mtm operation. 2118 o trillOamMepTxMtvmHC is used to set the Maximum Hop count for the 2119 Mtm message. As OAM frame doesn't leak out of the Trill network it 2120 has no side effect 2122 o trillOamMepTxMtvmReplyModeOob is used to indicate the reply is in- 2123 band or out-of-band. This object vulnerability is covered as part of 2124 trillOamMepTransmitMtmReplyIp 2126 o trillOamMepTxMtvmFlowEntropy is used to indicate customer flow and 2127 find the exact path in the network, creation of valid flows is 2128 intended purpose, if invalid flows are created on vulnerable system 2129 they will be dropped in forwarding. 2131 o trillOamMepTxMtvmStatus is required for normal Mtvm operation. 2133 o trillOamMepTxMtvmResultOK, trillOamMepTxMtvmMessages, 2134 trillOamMepTxMtvmSeqNumber, and trillOamMepTxMtvmScopeList is 2135 required for normal Mtvm operation. 2137 trillOamMepTransmitLbmReplyIp, trillOamMepTransmitPtmReplyIp, and 2138 trillOamMepTransmitMtvmReplyIp allow set of IP address where reports 2139 are to be sent and thus it can be used for Denial of Service for that 2140 IP. 2142 Some of the readable objects in this MIB module (i.e., objects with a 2143 MAX-ACCESS other than not-accessible) may be considered sensitive or 2144 vulnerable in some network environments. It is thus important to 2145 control GET and/or NOTIFY access to these objects and possibly to 2146 encrypt the values of these objects when sending them over the 2147 network via SNMP. For example, Path trace message expose unicast 2148 topology of network and Multi-destination Tree verification message 2149 expose multicast tree topology of network and this information should 2150 not be available to all users of the network. 2152 SNMP version prior to SNMPv3 did not include adequate security. Even 2153 if the network itself is secure(for example by using IPsec), there is 2154 no control as to who on the secure network is allowed to access and 2155 GET/SET (read/change/create/delete) the objects in this MIB module. 2157 Implementation should provide the security features described by 2158 SNMPv3 framework (see [RFC3410]), and implementations claiming 2159 compliance to the SNMPv3 standard MUST include full support for 2160 authentication and privacy via the User-based Security Model 2161 (USM)[RFC3414] with the AES cipher algorithm [RFC3826]. 2162 Implementations MAY also provide support for the Transport Security 2163 Model (TSM) [RFC5591] in combination with a secure transport such as 2164 SSH [RFC5592] or TLS/DTLS [RFC6353]. 2166 Further, deployment of SNMP version prior to SNMPv3 is NOT 2167 RECOMMENDED. Instead, deployment of SNMPv3 with cryptographic 2168 security enabled is RECOMMENDED. It is then a customer/operator 2169 responsibility to ensure that the SNMP entity giving access to an 2170 instance of this MIB module is properly configured to give only those 2171 principals (users) that have legitimate rights to indeed GET or SET 2172 (change/create/delete) them access to the objects. 2174 9. IANA Considerations 2176 The MIB module in this document uses the following IANA-assigned 2177 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2179 Descriptor OBJECT IDENTIFIER value 2180 ---------------------------------------- 2181 trillOamMIB { mib-2 xxx } 2183 Editor's Note (to be removed prior to publication): the IANA is 2184 requested to assign a value for "xxx" under the 'mib-2' subtree and 2185 to record the assignment in the SMI Numbers registry. When the 2186 assignment has been made, the RFC Editor is asked to replace "XXX" 2187 (here and in the MIB module) with the assigned value and to remove 2188 this note. 2190 10. Contributors 2192 We wish to thank members of the IETF TRILL WG, and mib-doctor for 2193 their comments and suggestions. Detailed comments were provided by 2194 Sam Aldrin, Donald Eastlake, Tom Taylor, and Harrie Hazewinkel. 2196 11. References 2197 11.1. Normative References 2199 [RFC2119] Bradner, S., "Key words for use in RFCs to 2200 Indicate Requirement Levels", BCP 14, RFC 2119, March 2201 1997. 2203 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2204 Schoenwaelder, Ed., "Structure of Management Information 2205 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2207 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2208 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2209 58, RFC 2579, April 1999. 2211 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2212 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2213 STD 58, RFC 2580, April 1999. 2215 [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, 2216 S., and A. Ghanwani, "Routing Bridges (RBridges): Base 2217 Protocol Specification", RFC 6325, July 2011. 2219 [RFC7172] Eastlake 3rd, D., Zhang, M., Agarwal, P., 2220 Perlman, R., and D. Dutt, "Transparent Interconnection of 2221 Lots of Links (TRILL): Fine-Grained Labeling", RFC 7172, 2222 May 2014. 2224 [RFC7455] Senevirathne, T., et.al., "Transparent 2225 Interconnection of Lots of Links (TRILL): Fault 2226 Management", March 2015. 2228 [LLDP-MIB] IEEE, 2229 http://www.ieee802.org/1/files/public/MIBs/LLDP-MIB- 2230 200505060000Z.txt 2232 [802.1Q] IEEE, "IEEE Standard for Local and metropolitan 2233 area networks - Media Access Control (MAC) Bridges and 2234 Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 2235 31 August 2011. 2237 11.2. Informative References 2239 [802.1Q] IEEE, "IEEE Standard for Local and metropolitan 2240 area networks - Media Access Control (MAC) Bridges and 2241 Virtual Bridge Local Area Networks", IEEE Std 802.1Q-2011, 2242 31 August 2011. 2244 [RFC3410] Case, J., Mundy, R., Partain, D., and B.Stewart, 2245 "Introduction and Applicability Statements for Internet- 2246 Standard Management Framework", RFC 3410, December 2002. 2248 [RFC6905] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., 2249 and R. Watve, "Requirements for Operations, 2250 Administration, and Maintenance (OAM) in Transparent 2251 Interconnection of Lots of Links (TRILL)", RFC 6905, March 2252 2013. 2254 [RFC7174] Salam, S., Senevirathne, T., Aldrin, S., and D. 2255 Eastlake 3rd, "Transparent Interconnection of Lots of 2256 Links (TRILL) Operations, Administration, and Maintenance 2257 (OAM) Framework", RFC 7174, May 2014. 2259 Authors' Addresses 2261 Deepak Kumar 2262 Cisco 2263 510 McCarthy Blvd, 2264 Milpitas, CA 95035, USA 2265 Phone : +1 408-853-9760 2266 Email: dekumar@cisco.com 2268 Samer Salam 2269 Cisco 2270 595 Burrard St. Suite 2123 2271 Vancouver, BC V7X 1J1, Canada 2272 Email: ssalam@cisco.com 2274 Tissa Senevirathne 2275 Consultant 2276 Email: tsenevir@gmail.com