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