idnits 2.17.1 draft-ietf-trill-oam-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 72 instances of too long lines in the document, the longest one being 11 characters in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 372 has weird spacing: '... Action field...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (July 26, 2014) is 3533 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: 'TRILLOAMFRM' is mentioned on line 86, but not defined == Missing Reference: 'FM' is mentioned on line 86, but not defined == Missing Reference: 'RFCfg1' is mentioned on line 137, but not defined == Missing Reference: 'RFC6325' is mentioned on line 330, but not defined == Missing Reference: 'CFM' is mentioned on line 629, but not defined ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 2 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). 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 Jan 2015 July 26, 2014 8 TRILL OAM MIB 9 draft-ietf-trill-oam-mib-01.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 November 08, 2013. 34 Copyright Notice 36 Copyright (c) 2014 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 50 This document specifies the Management Information Base (MIB) for the 51 IETF TRILL (Transparent Interconnection of Lots of Links) OAM 52 objects. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. The Internet-Standard Management Framework . . . . . . . . . . 3 58 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 5. Structure of the MIB module . . . . . . . . . . . . . . . . . . 4 61 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . . 4 62 5.2. TRILL-OAM-MIB relationship to IEEE8021-TC-MIB . . . . . . 4 63 5.3. TRILL OAM MIB Tree . . . . . . . . . . . . . . . . . . . . 5 64 5.3.1. Notifications . . . . . . . . . . . . . . . . . . . . 5 65 5.3.2. TRILL OAM MIB Per MEP Objects . . . . . . . . . . . . . 5 66 5.3.2.1. trillOamMepTable Objects . . . . . . . . . . . . . 5 67 5.3.2.2. trillOamMepFlowCfgTable Objects . . . . . . . . . . 8 68 5.3.2.3. trillOamPtrTable Objects . . . . . . . . . . . . . 9 69 5.3.2.4. trillOamMtrTable Objects . . . . . . . . . . . . . 10 70 5.3.2.4. trillOamMepDbTable Objects . . . . . . . . . . . . 12 71 6. Relationship to other MIB module . . . . . . . . . . . . . . . 13 72 6.1. Relationship to IEEE8021-CFM-MIB . . . . . . . . . . . . . 13 73 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 13 74 7. Definition of the TRILL OAM MIB module . . . . . . . . . . . . 13 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 47 76 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 48 77 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 78 10.1. Normative References . . . . . . . . . . . . . . . . . . 48 79 10.2. Informative References . . . . . . . . . . . . . . . . . 49 80 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 49 82 1. Introduction 84 Overall, TRILL OAM is intended to meet the requirements given in 85 [RFC6905]. The general framework for TRILL OAM is specified in 86 [TRILLOAMFRM]. The details of the Fault Management [FM] solution, 87 conforming to that framework, are presented in [TRILLOAMFM]. The 88 solution leverages the message format defined in Ethernet 89 Connectivity Fault Management (CFM) [802.1Q] as the basis for the 90 TRILL OAM message channel. 92 This document uses the CFM MIB modules defined in [802.1Q] as the 93 basis for TRILL OAM MIB, and augments the existing tables to add new 94 TRILL managed objects required by TRILL. This document further 95 specifies a new table with associated managed objects for TRILL OAM 96 specific capabilities. 98 2. The Internet-Standard Management Framework 99 For a detailed overview of the Internet-Standard Management 100 Framework, please refer to [RFC3410]. Managed objects are accessed 101 via a virtual information store, termed the Management Information 102 Base or MIB. MIB objects are generally accessed through the Simple 103 Network Management Protocol (SNMP). Objects in the MIB are defined 104 using the Structure of Management Information (SMI) specification. 105 This memo specifies a MIB module that is compliant to SMIv2 106 [RFC2578], [RFC2579] and [RFC2580]. 108 3. Overview 110 The TRILL-OAM-MIB module is intended to provide an overall framework 111 for managing TRILL OAM. It leverages the IEEE8021-CFM-MIB and 112 IEEE8021-CFM-V2-MIB modules defined in [802.1Q], and augments the Mep 113 and Mep Db entries. It also adds a new table for TRILL OAM specific 114 messages. 116 4. Conventions 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in RFC-2119 [RFC2119]. 122 5. Structure of the MIB module 124 Objects in this MIB module are arranged into subtrees. Each subtree 125 is organized as a set of related objects. The various subtrees are 126 shown below, supplemented with the required elements of the IEEE8021- 127 CFM-MIB module. 129 5.1. Textual Conventions 131 Textual conventions are defined to represent object types relevant to 132 the TRILL OAM MIB. 134 5.2. TRILL-OAM-MIB relationship to IEEE8021-TC-MIB 136 In TRILL, traffic labeling can be done using either a 12-bit VLAN or 137 a 24-bit fine grain label [RFCfg1]. 139 IEEE8021-TC-MIB defines IEEE8021ServiceSelectorType with two values: 141 - 1 representing a vlanId, and 143 - 2 representing a 24 bit isid. 145 We propose to use value 2 for TRILL's fine grain label. As such, 146 TRILL-OAM-MIB will import IEEE8021ServiceSelectorType, 147 IEEE8021ServiceSelectorValueOrNone, and IEEE8021ServiceSelectorValue 148 from IEEE8021-TC-MIB. 150 5.3. TRILL OAM MIB Tree 152 TRILL-OAM-MIB 154 |--trillOamNotifications 156 |--trillOamFaultAlarm 158 |--trillOamMibObjects 160 |--trillOamMep 162 |--trillOamMepTable 164 |--trillOamMepFlowCfgTable 166 |--trillOamPtrTable 168 |--trillOamMtrTable 170 |--trillOamMepDbTable 172 5.3.1. Notifications 174 Notification (fault alarm) is sent to the management entity with the 175 OID of the MEP that has detected the fault. 177 5.3.2. TRILL OAM MIB Per MEP Objects 179 The TRILL OAM MIB Per MEP Objects are defined in the 180 trillOamMepTable. The trillOamMepTable augments the dot1agCfmMepEntry 181 (please see section 6.1) defined in IEEE8021-CFM-MIB. It includes 182 objects that are locally defined for an individual MEP and its 183 associated Flow. 185 5.3.2.1. trillOamMepTable Objects 187 o trillOamMepRName - This object contains the Rbridge Nickname 188 as defined in [RFC6325] section 3.7. 190 o trillOamMepPtmTId - indicates the next sequence 191 number/transaction identifier to be sent in a Path Trace 192 message. The sequence number may be zero because it wraps 193 around. 195 o trillOamMepNexttMtmTId - indicates the next sequence 196 number/transaction identifier to be sent in a Multi-destination 197 message. The sequence number may be zero because it wraps 198 around. 200 o trillOamMepMepPtrIn - indicates the total number of valid, 201 in-order, Path Trace Replies received. 203 o trillOamMepPtrInOutofOrder - indicates the total number of 204 valid, out-of-order, Path Trace Replies received. 206 o trillOamMepPtrOut - indicates the total number of valid Path 207 Trace Replies transmitted. 209 o trillOamMepMtrIn - indicates the total number of valid, in- 210 order, Multi-destination Replies received. 212 o trillOamMepMtrInOutofOrder - indicates the total number of 213 valid, out-of-order, Multi-destination Replies received. 215 o trillOamMepMtrOut - indicates the total number of valid 216 Multi-destination Replies transmitted. 218 o trillOamMepTxLbmDestRName - indicates the target destination 219 Rbridge NickName as defined in [RFC6325] section 3.7. 221 o trillOamMepTxLbmHC - indicates the hop count field to be 222 transmitted. 224 o trillOamMepTxLbmReplyModeOob - True indicates that the Reply 225 Mode of the Loopback message is requested to be out-of-band, 226 and that the "Out of band IP address" TLV is to be transmitted. 227 False indicates that in-band reply is transmitted. 229 o trillOamMepTransmitLbmReplyIp - indicates the IP address to 230 be transmitted in the "Out of band IP Address TLV" in the 231 Loopback message. 233 o trillOamMepTxLbmFlowEntropy - indicates the 128 bytes Flow 234 entropy to be transmitted, as defined in [TRILLOAMFM]. 236 o trillOamMepTxPtmDestRName - indicates the target Destination 237 Rbridge Nickname to be transmitted, as defined in [RFC6325] 238 section 3.7. 240 o trillOamMepTxPtmHC - indicates the hop count field to be 241 transmitted. 243 o trillOamMepTxPtmReplyModeOob - True indicates that the Reply 244 Mode of the Path Trace message is requested to be out-of-band, 245 and that the "Out of band IP address TLV" is to be transmitted. 246 False indicates that in-band reply is transmitted. 248 o trillOamMepTransmitPtmReplyIP - indicates the IP address to 249 be transmitted in the "Out of band IP Address TLV" in the Path 250 Trace message. 252 o trillOamMepTranmitPtmFlowEntropy - indicates the 128 bytes 253 Flow entropy to be transmitted, as defined in [TRILLOAMFM]. 255 o trillOamMepTxPtmStatus - A Boolean flag set to True by the 256 MEP Path Trace Initiator State Machine or a MIB manager to 257 indicate that another Path trace message is being transmitted. 258 Reset to false by the MEP Initiator State Machine. 260 o trillOamMepTxPtmResultOK - Indicates the result of the 261 operation, True : The Path Trace Message(s) will be (or has 262 been) sent, False: The Path Trace Message(s) will not be sent. 264 o trillOamMepTxPtmMessages - The number of Path Trace messages 265 to be transmitted. 267 o trillOamMepTxPtmSeqNumber - Indicates the Path Trace 268 Transaction Identifier of the first PTM (to be) sent. The value 269 returned is undefined if trillOamMepTxPtmResultOK is false. 271 o trillOamMepTxMtmTree - Indicates the Multi-destination Tree 272 identifier as defined in RFC6325. 274 o trillOamMepTxMtmHC - Indicates the hop count field to be 275 transmitted. 277 o trillOamMepTxMtmReplyModeOob - True indicates that the Reply 278 of the Multi-destination message is requested to be out-of- 279 band, and that the "Out of band IP address TLV" is to be 280 transmitted. False indicates that in-band reply is transmitted. 282 o trillOamMepTransmitMtmReplyIp - the IP address to be 283 transmitted in the "Out of band IP address TLV" in the Multi- 284 destination message. 286 o trillOamMepTxMtmFlowEntropy - 128 Byte Flow Entropy to be 287 transmitted, as defined in [TRILL-FM]. 289 o trillOamMepTxMtmStatus - A Boolean flag set to True by the 290 MEP Multi-Destination Initiator State Machine or a MIB manager 291 to indicate that another Multicast trace message is being 292 transmitted. Reset to False by the MEP Initiator State Machine. 294 o trillOamMepTxMtmResultOK - Indicates the result of the 295 operation: -True The Multi-destination Message(s) will be (or 296 has been) sent. -False The Multi-destination Message(s) will 297 not be sent. 299 o trillOamMepTxMtmMessages -The number of Multi-Destination 300 Messages to be transmitted. 302 o trillOamMepTxMtmSeqNumber - The Sequence Number of the first 303 Multi-destination message (to be) sent. The value returned is 304 undefined if trillOamMepTxMtmResultOK is false. 306 o trillOamMepTxMtmScopeList - The Multi-destination Rbridge 307 Scope list, 2 octets per Rbridge. 309 5.3.2.2. trillOamMepFlowCfgTable Objects 311 Each row in this table represents a Flow Configuration Entry for the 312 associated MEP. The table uses four indices. The first three indices 313 are the indices of the Maintenance Domain, MaNet, and MEP tables. The 314 fourth index is the specific Flow Configuration Entry on the selected 315 MEP. Some write-able objects in this table are only applicable in 316 certain cases (as described under each object below), and attempts to 317 write values for them in other cases will be ignored. 319 o trillOamMepFlowCfgIndex - an index to the TRILL OAM Mep flow 320 configuration table which indicates the specific Flow for the 321 MEP. The index is never reused for other flow sessions on the 322 same MEP while this session is active. The index value keeps 323 increasing until it wraps to 0. This value can also be used in 324 Flow-identifier TLV. 326 o trillOamMepFlowCfgFlowEntropy - This is 96 bytes of flow 327 entropy as described in [TRILL-FM]. 329 o trillOamMepFlowCfgDestRname - The target Rbridge nickname 330 field to be transmitted as defined in [RFC6325] section 3.7. 332 o trillOamMepFlowCfgFlowHC - indicates the time to live field 333 to be transmitted. 335 o trillOamMepFlowCfgRowStatus - indicates the status of row. 336 The write-able columns in a row cannot be changed if the row is 337 active. All columns MUST have a valid value before a row can be 338 activated. 340 5.3.2.3. trillOamPtrTable Objects 342 Each row in the table represents a Path Trace Reply Entry for the 343 defined MEP and Transaction. This table uses four indices. The first 344 three indices identify the MEP and the fourth index specifies the 345 Transaction Identifier, and this transaction identifier uniquely 346 identifies the response for a MEP which can have multiple flow. 348 o trillOamMepPtrTransactionId - indicates Transaction 349 identifier/sequence number returned by a previous transmit path 350 trace message command, indicating which PTM's response is going 351 to be returned. 353 o trillOamPtrHC - indicates hop count field value for a 354 returned PTR. 356 o trillOamMepPtrFlag - indicates FCOI field value for a 357 returned PTR. 359 o trillOamMepPtrErrorcode - indicates the Return code and 360 Return sub-code value for a returned PTR. 362 o trillOamMepPtrTerminalMep - indicates a Boolean value stating 363 whether the forwarded PTM reached a MEP enclosing its MA, as 364 returned in the Terminal MEP flag field. 366 o trillOamMepPtrNextEgressIdentifer -An integer field holding 367 the last Egress Identifier returned in the PTR Upstream Rbridge 368 nickname TLV of the PTR. The Last Egress identifies the 369 Upstream Nickname. 371 o trillOamMepPtrIngress - The value returned in the Ingress 372 Action field of the PTM. The value ingNoTlv(0) indicates that 373 no Reply Ingress TLV was returned in the PTM. 375 o trillOamMepPtrIngressMac - indicates the MAC address returned 376 in the ingress MAC address filed. 378 o trillOamMepIngressPortIdSubtype - indicates ingress Port ID. 379 The format of this object is determined by the value of the 380 trillOamMepPtrIngressPortIdSubtype object. 382 o trillOamMepIngressPortId - indicates the ingress port ID. The 383 format of this object is determined by the value of the 384 trillOamMepPtrIngressPortId object. 386 o trillOamMepPtrEgressPortIdSubtype - indicates the value 387 returned in the Egress Action field of the PTM. The value 388 ingNoTlv(0) indicates that no Reply Egress TLV was returned in 389 the PTM. 391 o trillOamMepPtrEgressPortId - indicates the egress port ID. 392 The format of this object is determined by the value of 393 trillOamMepPtrEgressPortId object. 395 o trillOamMepPtrChassisIdSubtype - This object specifies the 396 format for the Chassis ID returned in the Sender ID TLV of the 397 PTR, if any. This value is ignored if the 398 trillOamMepPtrChassiId has a length of 0. 400 o trillOamMepPtrChassisId - indicates the chassis ID returned 401 in the Sender ID TLV of the PTR, if any. The format of this 402 object is determined by the value of the 403 trillOamMepPtrChassisIdSubtype object. 405 o trillOamMepPtrOrganizationSpecificTlv - indicates all 406 Organization specific TLVs returned in the PTR, if any. 407 Includes all octets including and following the TLV length 408 field of each TLV, concatenated together. 410 o trillOaMepPtrNextHopNicknames - indicates Next hop Rbridge 411 List TLV returned in the PTR, if any. Includes all octets 412 including and following the TLV length concatenated together. 414 5.3.2.4. trillOamMtrTable Objects 416 This table includes Multi-destination Reply managed objects. Each row 417 in the table represents a Multi-destination Reply Entry for the 418 defined MEP and Transaction. This table uses five indices: The first 419 three indices are the indices of the Maintenance Domain, MaNet, and 420 MEP tables. The fourth index is the specific Transaction Identifier 421 on the selected MEP. The fifth index is the receive order of Multi- 422 destination replies. Some write-able objects in this table are only 423 applicable in certain cases (as described under each object below), 424 and attempts to write a value for them in other cases will be 425 ignored. 427 o trillOamMepMtrTransactionId - indicates Transaction 428 identifier/sequence number returned by a previous transmit 429 Multi-destination message command, indicating which MTM's 430 response is going to be returned. 432 o trillOamMepMtrReceiveOrder - indicates an index to 433 distinguish among multiple MTR with same same MTR Transaction 434 Identifier field value. trillOamMepMtrReceiveOrder are assigned 435 sequentially from 1, in the order that the Multi-destination 436 Tree Initiator received the MTRs. 438 o trillOamMepMtrFlag - indicates FCOI field value for a 439 returned MTR. 441 o trillOamMepMtrErrorCode - indicates return code and return 442 sub code value for a returned MTR. 444 o trillOamMepMtrLastEgressIdentifier - indicates an integer 445 field holding the Last Egress Identifier returned in the MTR 446 Upstream Rbridge Nickname TLV of the MTR. The Last Egress 447 Identifier identifies the Upstream Nickname. 449 o trillOamMepMtrIngress - indicates the value returned in the 450 Ingress Action Field of the MTR. The value ingNoTlv(0) 451 indicates that no Reply Ingress TLV was returned in the MTM. 453 o trillOamMepMtrIngressMac - indicates the MAC address returned 454 in the ingress MAC address field. 456 o trillOamMepMtrIngressPortIdSubtype - indicates the ingress 457 Port ID. The format of this object is determined by the value 458 of the trillOamMepMtrIngressPortIdSubtype object. 460 o trillOamMepMtrIngressPortId - indicates the ingress Port Id. 461 The format of this object is determined by the value of the 462 trillOamMepMtrIngressPortId object. 464 o trillOamMepMtrEgress - indicates the value returned in the 465 Egress Action field of the MTR. The value ingNoTLv(0) indicates 466 that no Reply Egress TLV was returned in the MTR. 468 o trillOamMepMtrEgressMac - indicates the MAC address returned 469 in the egress MAC address field. 471 o trillOamMepMtrEgressPortIdSubtype - indicates the egress Port 472 ID. The format of this object is determined by the value of the 473 trillOamMepMtrEgressPortIdSubtype object. 475 o trillOamMepMtrEgressPortId - indicates the egress port ID. 476 The format of this object is determined by the value of the 477 trillOamMepMtrEgressPortId object. 479 o trillOamMepMtrChassisIdSubtype - indicates the format of the 480 chassis ID returned in the Sender ID TLV of the MTR, if any. 482 The value is ignored if the trillOamMepMtrChassisId has length 483 of 0. 485 o trillOamMepMtrChassisId - indicates the chassis ID returned 486 in the Sender ID TLV of the MTR, if any. The format of this 487 object is determined by the value of the 488 trillOamMepMtrChassisIdSubtype object. 490 o trillOamMepMtrOrganizationSpecificTlv - indicates all 491 Organization specific TLVs returned in the MTR, if any. 492 Includes all octets including and following the TLV length 493 filed of each TLV, contacted together. 495 o trillOamMepMtrNextHopNicknames - indicates next hop Rbridge 496 List TLV returned in the PTR, if any. Includes all octets 497 including and following the TLV length filed of each TLV, 498 concatenated together. 500 o trillOamMepMtrNextHopTotalReceivers - indicates value 501 indicating that MTR response contains Multicast receiver 502 availability TLV. 504 o trillOamMepMtrReceiverCount - indicates the number of 505 Multicast receivers available on responding Rbridge on the VLAN 506 specified by the diagnostic VLAN. 508 5.3.2.4. trillOamMepDbTable Objects 510 This table is an augmentation of the dot1agCfmMepDbTable, and rows 511 are automatically added or deleted from this table based upon row 512 creation and destruction of the dot1agCfmMepDbTable. 514 o trillOamMepDbFlowIndex - This object identifies the Flow. If 515 the Flow Identifier TLV is received than index received can 516 also be used. 518 o trillOamMepCfgFlowEntropy - indicates 96 bytes of Flow 519 entropy. 521 o trillOamMepDbFlowState - indicates the operational state of 522 the remote MEP (flow based) IFF state machines. 524 o trillOamMepDbRmepFailedOkTime - indicates the time 525 (sysUpTime) at which the Remote Mep Flow State machine last 526 entered either the RMEP_FAILED or RMEP_OK state. 528 o trillOamMepDbRbridgeName - indicates Remote MEP Rbridge 529 Nickname. 531 6. Relationship to other MIB module 533 The IEEE8021-CFM-MIB, IEEE801-CFM-V2-MIB and LLDP-MIB contain 534 objects relevant to TRILL OAM MIB. Management objects contained 535 in these modules are not duplicated here, to reduce overlap to 536 the extent possible. 538 6.1. Relationship to IEEE8021-CFM-MIB 540 TRILL OAM MIB Imports the following management objects from 541 IEEE8021-CFM-MIB: 543 o dot1agCfmMdIndex 545 o dot1agCfmMaIndex 547 o dot1agCfmMepIdentifier 549 o dot1agCfmMepEntry 551 o dot1agCfmMepDbEntry 553 o Dot1agCfmIngressActionFieldValue 555 o Dot1agCfmEgessActionFieldValue 557 o Dot1agCfmRemoteMepState 559 trillOamMepTable Augments dot1agCfmMepEntry. Implementation of IEEE- 560 CFM-MIB is required as we are Augmenting the IEEE-CFM-MIB Table. 561 Objects/Tables that are not applicable to a TRILL implementation have 562 to be handled by the TRILL implementation back end and appropriate 563 values as described in IEEE-CFM-MIB have to be returned. 565 6.2. MIB modules required for IMPORTS 567 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 568 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IEEE-8021-CFM-MIB, LLDP- 569 MIB. 571 7. Definition of the TRILL OAM MIB module 573 TRILL-OAM-MIB DEFINITIONS ::= BEGIN 575 IMPORTS 577 MODULE-IDENTITY, 578 OBJECT-TYPE, 579 NOTIFICATION-TYPE, 580 Counter32, 581 Unsigned32, 582 Integer32 583 FROM SNMPv2-SMI 584 RowStatus, 585 TruthValue, 586 TimeStamp, 587 MacAddress 588 FROM SNMPv2-TC 589 OBJECT-GROUP, 590 NOTIFICATION-GROUP, 591 MODULE-COMPLIANCE 592 FROM SNMPv2-CONF 593 dot1agCfmMdIndex, 594 dot1agCfmMaIndex, 595 dot1agCfmMepIdentifier, 596 dot1agCfmMepEntry, 597 dot1agCfmMepDbEntry, 598 Dot1agCfmIngressActionFieldValue, 599 Dot1agCfmEgressActionFieldValue, 600 Dot1agCfmRemoteMepState 601 FROM IEEE8021-CFM-MIB 602 LldpChassisId, 603 LldpChassisIdSubtype, 604 LldpPortId 605 FROM LLDP-MIB; 607 trillOamMib MODULE-IDENTITY 608 LAST-UPDATED "201407261200Z" 609 ORGANIZATION "TBD" 610 CONTACT-INFO 611 "E-mail: dekumar@cisco.com 612 Postal: 510 McCarthy Blvd 613 Milpitas, CA 95035 614 U.S.A. 615 Phone: +1 408 853 9760" 616 DESCRIPTION 617 "This MIB module contains the management objects for the 618 management of Trill Services Operations, Administration 619 and Maintenance. 620 Initial version. Published as RFC xxxx. 622 ----------------------------------------------------------------- 623 Reference Overview 625 A number of base documents have been used to create the 626 Textual Conventions MIB. The following are the 627 abbreviations for the baseline documents: 629 [CFM] refers to 'Connectivity Fault Management', IEEE 802.1ag-2007, 630 December 2007 631 [Q.840.1] refers to 'ITU-T Requirements and analysis for NMS-EMS 632 management interface of Ethernet over Transport and 633 Metro Ethernet Network (EoT/MEN)', March 2007 634 [Y.1731] refers to ITU-T Y.1731 'OAM functions and mechanisms for 635 Ethernet based networks', February 2011 636 ----------------------------------------------------------------- 638 Abbreviations Used 640 Term Definition 641 CCM Continuity Check Message 642 CFM Connectivity Fault Management 643 CoS Class of Service 644 IEEE Institute of Electrical and Electronics Engineers 645 IETF Internet Engineering Task Force 646 ITU-T International Telecommunication Union - Telecommunication 647 Standardization Bureau 648 MAC Media Access Control 649 MA Maintenance Association (equivalent to a MEG) 650 MD Maintenance Domain (equivalent to a OAM Domain in MEF 17) 651 MD Level Maintenance Domain Level (equivalent to a MEG level) 652 ME Maintenance Entity 653 MEG Maintenance Entity Group (equivalent to a MA) 654 MEG Level Maintenance Entity Group Level (equivalent to MD Level) 655 MEP Maintenance Association End Point or MEG End Point 656 MIB Management Information Base 657 MIP Maintenance Domain Intermediate Point or MEG Intermediate 658 Point 659 MP Maintenance Point. One of either a MEP or a MIP 660 OAM Operations, Administration, and Maintenance On-Demand 661 OAM actions that are initiated via manual intervention 662 for a limited time to carry out diagnostics. On-Demand 663 OAM can result in singular or periodic OAM actions during 664 the diagnostic time interval 665 PDU Protocol Data Unit 666 RFC Request for Comment 667 SNMP Simple Network Management Protocol 668 SNMP Agent An SNMP entity containing one or more command responder 669 and/or notification originator applications (along with 670 their associated SNMP engine). Typically implemented in 671 an NE. 672 SNMP Manager An SNMP entity containing one or more command generator 673 and/or notification receiver applications (along with 674 their associated SNMP engine). Typically implemented in 675 an EMS or NMS. 676 TLV Type Length Value, a method of encoding Objects 677 UTC Coordinated Universal Time 678 UNI User-to-Network Interface 679 VLAN Virtual LAN" 680 REVISION "201407261200Z" 681 DESCRIPTION 682 "Initial version. Published as RFC xxxx." 683 ::= { mib-2 xxx } 685 -- RFC Ed.: assigned by IANA, see section 9 for details 686 -- 687 -- ******************************************************************* 688 -- Object definitions in the TRILL OAM MIB Module 689 -- ******************************************************************* 691 trillOamNotifications OBJECT IDENTIFIER 692 ::= { trillOamMib 0 } 694 trillOamMibObjects OBJECT IDENTIFIER 695 ::= { trillOamMib 1 } 697 trillOamMibConformance OBJECT IDENTIFIER 698 ::= { trillOamMib 2 } 700 -- ******************************************************************* 701 -- Groups in the TRILL OAM MIB Module 702 -- ******************************************************************* 704 trillOamMep OBJECT IDENTIFIER 705 ::= { trillOamMibObjects 1 } 707 -- ******************************************************************* 708 -- TRILL OAM MEP Configuration 709 -- ******************************************************************* 711 trillOamMepTable OBJECT-TYPE 712 SYNTAX SEQUENCE OF TrillOamMepEntry 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "This table is an extension of the dot1agCfmMepTable and rows 717 are automatically added or deleted from this table based upon 718 row creation and destruction of the dot1agCfmMepTable. 720 This table represents the local MEP TRILL OAM configuration 721 table. The primary purpose of this table is provide local 722 parameters for the TRILL OAM function found in [TRILL-FM] and 723 instantiated at a MEP." 724 REFERENCE "[TRILL-FM]" 725 ::= { trillOamMep 1 } 727 trillOamMepEntry OBJECT-TYPE 728 SYNTAX TrillOamMepEntry 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "The conceptual row of trillOamMepTable." 733 AUGMENTS { dot1agCfmMepEntry } 734 ::= { trillOamMepTable 1 } 736 TrillOamMepEntry ::= SEQUENCE { 737 trillOamMepRName Unsigned32, 738 trillOamMepNextPtmTId Unsigned32, 739 trillOamMepNextMtmTId Unsigned32, 740 trillOamMepPtrIn Counter32, 741 trillOamMepPtrInOutofOrder Counter32, 742 trillOamMepPtrOut Counter32, 743 trillOamMepMtrIn Counter32, 744 trillOamMepMtrInOutofOrder Counter32, 745 trillOamMepMtrOut Counter32, 746 trillOamMepTxLbmDestRName Unsigned32, 747 trillOamMepTxLbmHC Unsigned32, 748 trillOamMepTxLbmReplyModeOob TruthValue, 749 trillOamMepTransmitLbmReplyIp OCTET STRING, 750 trillOamMepTxLbmFlowEntropy OCTET STRING, 751 trillOamMepTxPtmDestRName Unsigned32, 752 trillOamMepTxPtmHC Unsigned32, 753 trillOamMepTxPtmReplyModeOob TruthValue, 754 trillOamMepTransmitPtmReplyIp OCTET STRING, 755 trillOamMepTxPtmFlowEntropy OCTET STRING, 756 trillOamMepTxPtmStatus TruthValue, 757 trillOamMepTxPtmResultOK TruthValue, 758 trillOamMepTxPtmMessages Integer32, 759 trillOamMepTxPtmSeqNumber Unsigned32, 760 trillOamMepTxMtmTree Unsigned32, 761 trillOamMepTxMtmHC Unsigned32, 762 trillOamMepTxMtmReplyModeOob TruthValue, 763 trillOamMepTransmitMtmReplyIp OCTET STRING, 764 trillOamMepTxMtmFlowEntropy OCTET STRING, 765 trillOamMepTxMtmStatus TruthValue, 766 trillOamMepTxMtmResultOK TruthValue, 767 trillOamMepTxMtmMessages Integer32, 768 trillOamMepTxMtmSeqNumber Unsigned32, 769 trillOamMepTxMtmScopeList OCTET STRING 770 } 772 trillOamMepRName OBJECT-TYPE 773 SYNTAX Unsigned32 (0..65471) 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "This object contains Rbridge NickName of TRILL Rbridge as 778 defined in RFC 6325 section 3.7." 779 REFERENCE "TRILL-FM and RFC 6325 section 3.7" 780 ::= { trillOamMepEntry 1 } 782 trillOamMepNextPtmTId OBJECT-TYPE 783 SYNTAX Unsigned32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "Next sequence number/transaction identifier to be sent in a 788 Path Trace message. This sequence number can be zero because it 789 wraps around. Implementation should be unique to identify 790 Transaction Id for a MEP with multiple flows." 791 REFERENCE "TRILL-FM 10.1.1" 792 ::= { trillOamMepEntry 2 } 794 trillOamMepNextMtmTId OBJECT-TYPE 795 SYNTAX Unsigned32 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "Next sequence number/transaction identifier to be sent in a 800 Multi-destination message. This sequence number can be zero 801 because it wraps around. Implementation should be unique to 802 identify Transaction Id for a MEP with multiple flows." 803 REFERENCE "TRILL-FM 11.2.1" 804 ::= { trillOamMepEntry 3 } 806 trillOamMepPtrIn OBJECT-TYPE 807 SYNTAX Counter32 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION 811 "Total number of valid, in-order Path Trace Replies received." 812 REFERENCE "TRILL-FM section 10" 813 ::= { trillOamMepEntry 4 } 815 trillOamMepPtrInOutofOrder OBJECT-TYPE 816 SYNTAX Counter32 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "Total number of valid, out-of-order Path Trace Replies received." 821 REFERENCE "TRILL-FM section 10" 822 ::= { trillOamMepEntry 5 } 824 trillOamMepPtrOut OBJECT-TYPE 825 SYNTAX Counter32 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "Total number of valid, Path Trace Replies transmitted." 830 REFERENCE "TRILL-FM section 10" 831 ::= { trillOamMepEntry 6 } 833 trillOamMepMtrIn OBJECT-TYPE 834 SYNTAX Counter32 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "Total number of valid, in-order Multi-destination Replies 839 received." 840 REFERENCE "TRILL-FM section 11" 841 ::= { trillOamMepEntry 7 } 843 trillOamMepMtrInOutofOrder OBJECT-TYPE 844 SYNTAX Counter32 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "Total number of valid, out-of-order Multi-destination Replies 849 received." 850 REFERENCE "TRILL-FM section 11" 851 ::= { trillOamMepEntry 8 } 853 trillOamMepMtrOut OBJECT-TYPE 854 SYNTAX Counter32 855 MAX-ACCESS read-only 856 STATUS current 857 DESCRIPTION 858 "Total number of valid, Multi-destination Replies 859 transmitted." 860 REFERENCE "TRILL-FM section 11" 861 ::= { trillOamMepEntry 9 } 863 trillOamMepTxLbmDestRName OBJECT-TYPE 864 SYNTAX Unsigned32 (0..65471) 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "The Target Destination Rbridge NickName Field as 869 defined in RFC 6325 section 3.7 to be transmitted." 870 REFERENCE "TRILL-FM and RFC6325 section 3.7" 871 ::= { trillOamMepEntry 10 } 873 trillOamMepTxLbmHC OBJECT-TYPE 874 SYNTAX Unsigned32(1..63) 875 MAX-ACCESS read-create 876 STATUS current 877 DESCRIPTION 878 "The Hop Count to be transmitted. 879 " 880 REFERENCE "TRILL-FM section 9 and 3" 881 ::= { trillOamMepEntry 11 } 883 trillOamMepTxLbmReplyModeOob OBJECT-TYPE 884 SYNTAX TruthValue 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "True Indicates that Reply of Lbm is out of band and 889 out of band IP Address TLV is to be transmitted. 890 False indicates that In band reply is transmitted." 891 REFERENCE "TRILL-FM 9.2.1" 892 ::= { trillOamMepEntry 12 } 894 trillOamMepTransmitLbmReplyIp OBJECT-TYPE 895 SYNTAX OCTET STRING 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "IP address for out of band IP Address TLV is to be transmitted." 900 REFERENCE "TRILL-FM section 3" 901 ::= { trillOamMepEntry 13 } 903 trillOamMepTxLbmFlowEntropy OBJECT-TYPE 904 SYNTAX OCTET STRING 905 MAX-ACCESS read-create 906 STATUS current 907 DESCRIPTION 908 "128 Byte Flow Entropy as defined in TRILL-FM to be transmitted." 909 REFERENCE "TRILL-FM section 3" 910 ::= { trillOamMepEntry 14 } 912 trillOamMepTxPtmDestRName OBJECT-TYPE 913 SYNTAX Unsigned32 (0..65471) 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "The Target Destination Rbridge NickName Field 918 as defined in RFC 6325 section 3.7 to be transmitted." 919 REFERENCE "TRILL-FM and RFC6325 section 3.7" 920 ::= { trillOamMepEntry 15 } 922 trillOamMepTxPtmHC OBJECT-TYPE 923 SYNTAX Unsigned32 (1..63) 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "The Hop Count field to be transmitted. 928 " 929 REFERENCE "TRILL-FM section 3" 930 ::= { trillOamMepEntry 16 } 932 trillOamMepTxPtmReplyModeOob OBJECT-TYPE 933 SYNTAX TruthValue 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "True Indicates that Reply of Ptm is out of band and 938 out of band IP Address TLV is to be transmitted. 939 False indicates that In band reply is transmitted." 940 REFERENCE "TRILL-FM section 10" 941 DEFVAL { false } 942 ::= { trillOamMepEntry 17 } 944 trillOamMepTransmitPtmReplyIp OBJECT-TYPE 945 SYNTAX OCTET STRING 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "IP address for out of band IP Address TLV is to be transmitted." 950 REFERENCE "TRILL-FM section 3 and 10" 951 ::= { trillOamMepEntry 18 } 953 trillOamMepTxPtmFlowEntropy OBJECT-TYPE 954 SYNTAX OCTET STRING 955 MAX-ACCESS read-create 956 STATUS current 957 DESCRIPTION 958 "128 Byte Flow Entropy as defined in TRILL-FM to be transmitted." 959 REFERENCE "TRILL-FM section 3" 960 ::= { trillOamMepEntry 19 } 962 trillOamMepTxPtmStatus OBJECT-TYPE 963 SYNTAX TruthValue 964 MAX-ACCESS read-create 965 STATUS current 966 DESCRIPTION 967 "A Boolean flag set to true by the MEP Path Trace Initiator State 968 Machine or an MIB manager to indicate that another Ptm is being 969 transmitted. 970 Reset to false by the MEP Initiator State Machine." 971 REFERENCE "TRILL-FM section 10" 972 DEFVAL { false } 973 ::= { trillOamMepEntry 20 } 975 trillOamMepTxPtmResultOK OBJECT-TYPE 976 SYNTAX TruthValue 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "Indicates the result of the operation: 981 - true The Path Trace Message(s) will be (or has been) sent. 982 - false The Path Trace Message(s) will not be sent." 983 REFERENCE "TRILL-FM section 10" 984 DEFVAL { true } 985 ::= { trillOamMepEntry 21 } 987 trillOamMepTxPtmMessages OBJECT-TYPE 988 SYNTAX Integer32 (1..1024) 989 MAX-ACCESS read-create 990 STATUS current 991 DESCRIPTION 992 "The number of Path Trace messages to be transmitted." 993 REFERENCE "TRILL-FM section 10" 994 ::= { trillOamMepEntry 22 } 996 trillOamMepTxPtmSeqNumber OBJECT-TYPE 997 SYNTAX Unsigned32 998 MAX-ACCESS read-create 999 STATUS current 1000 DESCRIPTION 1001 "The Path Trace Transaction Identifier of the first PTM (to be) 1002 sent. The value returned is undefined if 1003 trillOamMepTxPtmResultOK is false." 1004 REFERENCE "TRILL-FM section 10" 1005 ::= { trillOamMepEntry 23 } 1007 trillOamMepTxMtmTree OBJECT-TYPE 1008 SYNTAX Unsigned32 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "The Multi-destination Tree is identifier for tree as defined in 1013 RFC6325." 1014 ::= { trillOamMepEntry 24 } 1016 trillOamMepTxMtmHC OBJECT-TYPE 1017 SYNTAX Unsigned32(1..63) 1018 MAX-ACCESS read-create 1019 STATUS current 1020 DESCRIPTION 1021 "The Hop Count field to be transmitted. 1022 " 1023 REFERENCE "TRILL-FM section 3, RFC 6325 section 3" 1024 ::= { trillOamMepEntry 25 } 1026 trillOamMepTxMtmReplyModeOob OBJECT-TYPE 1027 SYNTAX TruthValue 1028 MAX-ACCESS read-create 1029 STATUS current 1030 DESCRIPTION 1031 "True Indicates that Reply of Mtm is out of band and 1032 out of band IP Address TLV is to be transmitted. 1033 False indicates that In band reply is transmitted." 1034 REFERENCE "TRILL-FM section 11" 1035 ::= { trillOamMepEntry 26 } 1037 trillOamMepTransmitMtmReplyIp OBJECT-TYPE 1038 SYNTAX OCTET STRING 1039 MAX-ACCESS read-create 1040 STATUS current 1041 DESCRIPTION 1042 "IP address for out of band IP Address TLV is to be transmitted." 1043 REFERENCE "TRILL-FM section 11" 1044 ::= { trillOamMepEntry 27 } 1046 trillOamMepTxMtmFlowEntropy OBJECT-TYPE 1047 SYNTAX OCTET STRING 1048 MAX-ACCESS read-create 1049 STATUS current 1050 DESCRIPTION 1051 "128 Byte Flow Entropy as defined in TRILL-FM to be transmitted." 1052 REFERENCE "TRILL-FM section 3" 1053 ::= { trillOamMepEntry 28 } 1055 trillOamMepTxMtmStatus OBJECT-TYPE 1056 SYNTAX TruthValue 1057 MAX-ACCESS read-create 1058 STATUS current 1059 DESCRIPTION 1060 "A Boolean flag set to true by the MEP Multi Destination Initiator State 1061 Machine or an MIB manager to indicate that another Mtm is being 1062 transmitted. 1063 Reset to false by the MEP Initiator State Machine." 1064 REFERENCE "TRILL-FM section 11" 1065 DEFVAL { false } 1066 ::= { trillOamMepEntry 29 } 1068 trillOamMepTxMtmResultOK OBJECT-TYPE 1069 SYNTAX TruthValue 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "Indicates the result of the operation: 1074 - true The Multi-destination Message(s) will be (or has been) sent. 1075 - false The Multi-destination Message(s) will not be sent." 1076 REFERENCE "TRILL-FM section 11" 1077 DEFVAL { true } 1078 ::= { trillOamMepEntry 30 } 1080 trillOamMepTxMtmMessages OBJECT-TYPE 1081 SYNTAX Integer32 (1..1024) 1082 MAX-ACCESS read-create 1083 STATUS current 1084 DESCRIPTION 1085 "The number of Multi Destination messages to be transmitted." 1086 REFERENCE "TRILL-FM section 11" 1087 ::= { trillOamMepEntry 31 } 1089 trillOamMepTxMtmSeqNumber OBJECT-TYPE 1090 SYNTAX Unsigned32 1091 MAX-ACCESS read-create 1092 STATUS current 1093 DESCRIPTION 1094 "The Multi-destination Transaction Identifier of the first MTM (to be) 1095 sent. The value returned is undefined if 1096 trillOamMepTxMtmResultOK is false." 1097 REFERENCE "TRILL-FM section 11" 1098 ::= { trillOamMepEntry 32 } 1100 trillOamMepTxMtmScopeList OBJECT-TYPE 1101 SYNTAX OCTET STRING 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "The Multi-destination Rbridge Scope list, 2 OCTET per Rbridge." 1106 REFERENCE "TRILL-FM section 11" 1107 ::= { trillOamMepEntry 33 } 1109 -- ******************************************************************* 1110 -- TRILL OAM Tx Measurement Configuration Table 1111 -- ******************************************************************* 1113 trillOamMepFlowCfgTable OBJECT-TYPE 1114 SYNTAX SEQUENCE OF TrillOamMepFlowCfgEntry 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "This table includes configuration objects and operations for 1119 the Trill OAM [TRILL-FM]. 1121 Each row in the table represents a Flow configuration Entry for 1122 the defined MEP. This table uses four indices. The first 1123 three indices are the indices of the Maintenance Domain, 1124 MaNet, and MEP tables. The fourth index is the specific Flow 1125 configuration Entry on the selected MEP. 1127 Some writable objects in this table are only applicable in 1128 certain cases (as described under each object), and attempts to 1129 write values for them in other cases will be ignored." 1130 REFERENCE "[TRILL-FM]" 1131 ::= { trillOamMep 2 } 1133 trillOamMepFlowCfgEntry OBJECT-TYPE 1134 SYNTAX TrillOamMepFlowCfgEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "The conceptual row of trillOamMepFlowCfgTable." 1139 INDEX { 1140 dot1agCfmMdIndex, 1141 dot1agCfmMaIndex, 1142 dot1agCfmMepIdentifier, 1143 trillOamMepFlowCfgIndex 1144 } 1145 ::= { trillOamMepFlowCfgTable 1 } 1147 TrillOamMepFlowCfgEntry ::= SEQUENCE { 1148 trillOamMepFlowCfgIndex Unsigned32, 1149 trillOamMepFlowCfgFlowEntropy OCTET STRING, 1150 trillOamMepFlowCfgDestRName Unsigned32, 1151 trillOamMepFlowCfgFlowHC Unsigned32, 1152 trillOamMepFlowCfgRowStatus RowStatus 1153 } 1155 trillOamMepFlowCfgIndex OBJECT-TYPE 1156 SYNTAX Unsigned32 (1..65535) 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "An index to the Trill OAM Mep Flow Configuration table which 1161 indicates the specific Flow for the MEP. 1163 The index is never reused for other flow sessions on the same 1164 MEP while this session is active. The index value keeps 1165 increasing until it wraps to 0. 1166 This value can also be used in Flow-identifier TLV [TRILL-FM]" 1167 REFERENCE "TRILL-FM" 1168 ::= { trillOamMepFlowCfgEntry 1 } 1170 trillOamMepFlowCfgFlowEntropy OBJECT-TYPE 1171 SYNTAX OCTET STRING 1172 MAX-ACCESS read-create 1173 STATUS current 1174 DESCRIPTION 1175 "This is 128 byte of Flow Entropy as described in 1176 TRILL OAM [TRILL-FM]." 1177 REFERENCE "TRILL-FM section 3" 1178 ::= { trillOamMepFlowCfgEntry 2 } 1180 trillOamMepFlowCfgDestRName OBJECT-TYPE 1181 SYNTAX Unsigned32 (0..65471) 1182 MAX-ACCESS read-create 1183 STATUS current 1184 DESCRIPTION 1185 "The Target Destination Rbridge NickName Field as 1186 defined in RFC 6325 section 3.7 to be transmitted." 1187 REFERENCE "TRILL-FM section 3 and RFC 6325 section 3.7" 1188 ::= { trillOamMepFlowCfgEntry 3 } 1190 trillOamMepFlowCfgFlowHC OBJECT-TYPE 1191 SYNTAX Unsigned32 1192 MAX-ACCESS read-create 1193 STATUS current 1194 DESCRIPTION 1195 "The Time to Live field to be transmitted. 1196 to be transmitted." 1197 REFERENCE "TRILL-FM section 3 and RFC 6325 section 3.7" 1198 ::= { trillOamMepFlowCfgEntry 4 } 1200 trillOamMepFlowCfgRowStatus OBJECT-TYPE 1201 SYNTAX RowStatus 1202 MAX-ACCESS read-create 1203 STATUS current 1204 DESCRIPTION 1205 "The status of the row. 1207 The writable columns in a row cannot be changed if the row 1208 is active. All columns MUST have a valid value before a row 1209 can be activated." 1210 ::= { trillOamMepFlowCfgEntry 5 } 1212 -- ******************************************************************** 1213 -- TRILL OAM Path Trace Reply Table 1214 -- ******************************************************************** 1216 trillOamPtrTable OBJECT-TYPE 1217 SYNTAX SEQUENCE OF TrillOamPtrEntry 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 "This table includes Path Trace Reply objects and operations for 1222 the Trill OAM [TRILL-FM]. 1224 Each row in the table represents a Path Trace Reply Entry for 1225 the defined MEP and Transaction. This table uses four indices. 1226 The first three indices are the indices of the Maintenance Domain, 1227 MaNet, and MEP tables. The fourth index is the specific 1228 Transaction Identifier on the selected MEP. 1230 Some writable objects in this table are only applicable in 1231 certain cases (as described under each object), and attempts to 1232 write values for them in other cases will be ignored." 1233 REFERENCE "TRILL-FM" 1234 ::= { trillOamMep 3 } 1236 trillOamPtrEntry OBJECT-TYPE 1237 SYNTAX TrillOamPtrEntry 1238 MAX-ACCESS not-accessible 1239 STATUS current 1240 DESCRIPTION 1241 "The conceptual row of trillOamPtrTable." 1242 INDEX { 1243 dot1agCfmMdIndex, 1244 dot1agCfmMaIndex, 1245 dot1agCfmMepIdentifier, 1246 trillOamMepPtrTransactionId 1248 } 1249 ::= { trillOamPtrTable 1 } 1251 TrillOamPtrEntry ::= SEQUENCE { 1252 trillOamMepPtrTransactionId Unsigned32, 1253 trillOamMepPtrHC Unsigned32, 1254 trillOamMepPtrFlag Unsigned32, 1255 trillOamMepPtrErrorCode Unsigned32, 1256 trillOamMepPtrTerminalMep TruthValue, 1257 trillOamMepPtrLastEgressId Unsigned32, 1258 trillOamMepPtrIngress Dot1agCfmIngressActionFieldValue, 1259 trillOamMepPtrIngressMac MacAddress, 1260 trillOamMepPtrIngressPortIdSubtype LldpPortId, 1261 trillOamMepPtrIngressPortId LldpPortId, 1262 trillOamMepPtrEgress Dot1agCfmEgressActionFieldValue, 1263 trillOamMepPtrEgressMac MacAddress, 1264 trillOamMepPtrEgressPortIdSubtype LldpPortId, 1265 trillOamMepPtrEgressPortId LldpPortId, 1266 trillOamMepPtrChassisIdSubtype LldpChassisIdSubtype, 1267 trillOamMepPtrChassisId LldpChassisId, 1268 trillOamMepPtrOrganizationSpecificTlv OCTET STRING, 1269 trillOamMepPtrNextHopNicknames OCTET STRING 1270 } 1272 trillOamMepPtrTransactionId OBJECT-TYPE 1273 SYNTAX Unsigned32 (0..4294967295) 1274 MAX-ACCESS not-accessible 1275 STATUS current 1276 DESCRIPTION 1277 "Transaction identifier/sequence number returned by a previous 1278 transmit path trace message command, indicating which PTM's 1279 response is going to be returned." 1280 REFERENCE "TRILL-FM section 10" 1281 ::= { trillOamPtrEntry 1 } 1283 trillOamMepPtrHC OBJECT-TYPE 1284 SYNTAX Unsigned32 (1..63) 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "Hop Count field value for a returned PTR." 1289 REFERENCE "TRILL-FM" 1290 ::= { trillOamPtrEntry 2 } 1292 trillOamMepPtrFlag OBJECT-TYPE 1293 SYNTAX Unsigned32 (0..15) 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "FCOI (TRILL OAM Message TLV) field value for a 1298 returned PTR." 1299 REFERENCE "TRILL-FM, 9.4.2.1" 1300 ::= { trillOamPtrEntry 3 } 1302 trillOamMepPtrErrorCode OBJECT-TYPE 1303 SYNTAX Unsigned32 (0..65535) 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "Return Code and Return Sub code value for a returned PTR." 1308 REFERENCE "TRILL-FM, 9.4.2.1" 1309 ::= { trillOamPtrEntry 4 } 1311 trillOamMepPtrTerminalMep OBJECT-TYPE 1312 SYNTAX TruthValue 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "A boolean value stating whether the forwarded PTM reached a 1317 MEP enclosing its MA, as returned in the Terminal MEP flag of 1318 the Flags field." 1319 REFERENCE "TRILL-FM" 1320 ::= { trillOamPtrEntry 5 } 1322 trillOamMepPtrLastEgressId OBJECT-TYPE 1323 SYNTAX Unsigned32 (0..65535) 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "An Integer field holding the Last Egress Identifier returned 1328 in the PTR Upstream Rbridge nickname TLV of the PTR. 1329 The Last Egress Identifier identifies the Upstream Nickname" 1330 REFERENCE "TRILL-FM 8.4.1" 1331 ::= { trillOamPtrEntry 6 } 1333 trillOamMepPtrIngress OBJECT-TYPE 1334 SYNTAX Dot1agCfmIngressActionFieldValue 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The value returned in the Ingress Action Field of the PTM. 1339 The value ingNoTlv(0) indicates that no Reply Ingress TLV was 1340 returned in the PTM." 1341 REFERENCE "TRILL-FM 8.4.1" 1342 ::= { trillOamPtrEntry 7 } 1344 trillOamMepPtrIngressMac OBJECT-TYPE 1345 SYNTAX MacAddress 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "MAC address returned in the ingress MAC address field." 1350 REFERENCE "TRILL-FM 8.4.1" 1351 ::= { trillOamPtrEntry 8 } 1353 trillOamMepPtrIngressPortIdSubtype OBJECT-TYPE 1354 SYNTAX LldpPortId 1355 MAX-ACCESS read-only 1356 STATUS current 1357 DESCRIPTION 1358 "Ingress Port ID. The format of this object is determined by 1359 the value of the trillOamMepPtrIngressPortIdSubtype object." 1360 REFERENCE "TRILL-FM 8.4.1" 1361 ::= { trillOamPtrEntry 9 } 1363 trillOamMepPtrIngressPortId OBJECT-TYPE 1364 SYNTAX LldpPortId 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "Ingress Port ID. The format of this object is determined by 1369 the value of the trillOamMepPtrIngressPortId object." 1370 REFERENCE "TRILL-FM 8.4.1" 1371 ::= { trillOamPtrEntry 10 } 1373 trillOamMepPtrEgress OBJECT-TYPE 1374 SYNTAX Dot1agCfmEgressActionFieldValue 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "The value returned in the Egress Action Field of the PTM. 1379 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1380 returned in the PTM." 1381 REFERENCE "TRILL-FM 8.4.1" 1382 ::= { trillOamPtrEntry 11 } 1384 trillOamMepPtrEgressMac OBJECT-TYPE 1385 SYNTAX MacAddress 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "MAC address returned in the egress MAC address field." 1390 REFERENCE "TRILL-FM 8.4.1" 1391 ::= { trillOamPtrEntry 12 } 1393 trillOamMepPtrEgressPortIdSubtype OBJECT-TYPE 1394 SYNTAX LldpPortId 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "Egress Port ID. The format of this object is determined by 1399 the value of the trillOamMepPtrEgressPortIdSubtype object." 1400 REFERENCE "TRILL-FM 8.4.1" 1401 ::= { trillOamPtrEntry 13 } 1403 trillOamMepPtrEgressPortId OBJECT-TYPE 1404 SYNTAX LldpPortId 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "Egress Port ID. The format of this object is determined by 1409 the value of the trillOamMepPtrEgressPortId object." 1410 REFERENCE "TRILL-FM 8.4.1" 1411 ::= { trillOamPtrEntry 14 } 1413 trillOamMepPtrChassisIdSubtype OBJECT-TYPE 1414 SYNTAX LldpChassisIdSubtype 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "This object specifies the format of the Chassis ID returned 1419 in the Sender ID TLV of the PTR, if any. This value is 1420 meaningless if the trillOamMepPtrChassisId has a length of 0." 1421 REFERENCE "TRILL-FM 8.4.1" 1422 ::= { trillOamPtrEntry 15 } 1424 trillOamMepPtrChassisId OBJECT-TYPE 1425 SYNTAX LldpChassisId 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "The Chassis ID returned in the Sender ID TLV of the PTR, if 1430 any. The format of this object is determined by the 1431 value of the trillOamMepPtrChassisIdSubtype object." 1432 REFERENCE "TRILL-FM 8.4.1" 1433 ::= { trillOamPtrEntry 16 } 1435 trillOamMepPtrOrganizationSpecificTlv OBJECT-TYPE 1436 SYNTAX OCTET STRING (SIZE (0..0 | 4..1500)) 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "All Organization specific TLVs returned in the PTR, if 1441 any. Includes all octets including and following the TLV 1442 Length field of each TLV, concatenated together." 1443 REFERENCE "TRILL-FM 8.4.1" 1444 ::= { trillOamPtrEntry 17 } 1446 trillOamMepPtrNextHopNicknames OBJECT-TYPE 1447 SYNTAX OCTET STRING (SIZE (0..0 | 4..1500)) 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "Next hop Rbridge List TLV returned in the PTR, if 1452 any. Includes all octets including and following the TLV 1453 Length field of each TLV, concatenated together." 1454 REFERENCE "TRILL-FM 8.4.1" 1455 ::= { trillOamPtrEntry 18 } 1457 -- ******************************************************************** 1458 -- TRILL OAM Multi Destination Reply Table 1459 -- ******************************************************************** 1461 trillOamMtrTable OBJECT-TYPE 1462 SYNTAX SEQUENCE OF TrillOamMtrEntry 1463 MAX-ACCESS not-accessible 1464 STATUS current 1465 DESCRIPTION 1466 "This table includes Multi-destination Reply objects and 1467 operations for the Trill OAM [TRILL-FM]. 1469 Each row in the table represents a Multi-destination Reply 1470 Entry for the defined MEP and Transaction. 1471 This table uses five indices. 1472 The first three indices are the indices of the Maintenance Domain, 1473 MaNet, and MEP tables. The fourth index is the specific 1474 Transaction Identifier on the selected MEP. 1475 The fifth index is the receive order of Multi-destination 1476 replies. 1478 Some writable objects in this table are only applicable in 1479 certain cases (as described under each object), and attempts to 1480 write values for them in other cases will be ignored." 1481 REFERENCE "TRILL-FM" 1482 ::= { trillOamMep 4 } 1484 trillOamMtrEntry OBJECT-TYPE 1485 SYNTAX TrillOamMtrEntry 1486 MAX-ACCESS not-accessible 1487 STATUS current 1488 DESCRIPTION 1489 "The conceptual row of trillOamMtrTable." 1490 INDEX { 1491 dot1agCfmMdIndex, 1492 dot1agCfmMaIndex, 1493 dot1agCfmMepIdentifier, 1494 trillOamMepPtrTransactionId, 1495 trillOamMepMtrReceiveOrder 1496 } 1497 ::= { trillOamMtrTable 1 } 1499 TrillOamMtrEntry ::= SEQUENCE { 1500 trillOamMepMtrTransactionId Unsigned32, 1501 trillOamMepMtrReceiveOrder Unsigned32, 1502 trillOamMepMtrFlag Unsigned32, 1503 trillOamMepMtrErrorCode Unsigned32, 1504 trillOamMepMtrLastEgressId Unsigned32, 1505 trillOamMepMtrIngress Dot1agCfmIngressActionFieldValue, 1506 trillOamMepMtrIngressMac MacAddress, 1507 trillOamMepMtrIngressPortIdSubtype LldpPortId, 1508 trillOamMepMtrIngressPortId LldpPortId, 1509 trillOamMepMtrEgress Dot1agCfmEgressActionFieldValue, 1510 trillOamMepMtrEgressMac MacAddress, 1511 trillOamMepMtrEgressPortIdSubtype LldpPortId, 1512 trillOamMepMtrEgressPortId LldpPortId, 1513 trillOamMepMtrChassisIdSubtype LldpChassisIdSubtype, 1514 trillOamMepMtrChassisId LldpChassisId, 1515 trillOamMepMtrOrganizationSpecificTlv OCTET STRING, 1516 trillOamMepMtrNextHopNicknames OCTET STRING, 1517 trillOamMepMtrReceiverAvailability TruthValue, 1518 trillOamMepMtrReceiverCount TruthValue 1519 } 1521 trillOamMepMtrTransactionId OBJECT-TYPE 1522 SYNTAX Unsigned32 (0..4294967295) 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 "Transaction identifier/sequence number returned by a previous 1527 transmit Multi-destination message command, indicating 1528 which MTM's response is going to be returned." 1529 REFERENCE "TRILL-FM section 11" 1530 ::= { trillOamMtrEntry 1 } 1532 trillOamMepMtrReceiveOrder OBJECT-TYPE 1533 SYNTAX Unsigned32 (1..4294967295) 1534 MAX-ACCESS not-accessible 1535 STATUS current 1536 DESCRIPTION 1537 "An index to distinguish among multiple MTR with same 1538 MTR Transaction Identifier field value. 1539 trillOamMepMtrReceiveOrder are assigned sequentially from 1, 1540 in the order that the Multi-destination Tree Initiator 1541 received the MTRs." 1542 REFERENCE "TRILL-FM section 11" 1543 ::= { trillOamMtrEntry 2 } 1545 trillOamMepMtrFlag OBJECT-TYPE 1546 SYNTAX Unsigned32 (0..15) 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "FCOI (TRILL OAM Message TLV) field value for a 1551 returned MTR." 1552 REFERENCE "TRILL-FM, 8.4.2" 1553 ::= { trillOamMtrEntry 3 } 1555 trillOamMepMtrErrorCode OBJECT-TYPE 1556 SYNTAX Unsigned32 (0..65535) 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "Return Code and Return Sub code value for a returned MTR." 1561 REFERENCE "TRILL-FM, 8.4.2" 1562 ::= { trillOamMtrEntry 4 } 1564 trillOamMepMtrLastEgressId OBJECT-TYPE 1565 SYNTAX Unsigned32 (0..65535) 1566 MAX-ACCESS read-only 1567 STATUS current 1568 DESCRIPTION 1569 "An Integer field holding the Last Egress Identifier returned 1570 in the MTR Upstream Rbridge Nickname TLV of the MTR. 1571 The Last Egress Identifier identifies the Upstream Nickname." 1572 REFERENCE "TRILL-FM 8.4.1" 1573 ::= { trillOamMtrEntry 5 } 1575 trillOamMepMtrIngress OBJECT-TYPE 1576 SYNTAX Dot1agCfmIngressActionFieldValue 1577 MAX-ACCESS read-only 1578 STATUS current 1579 DESCRIPTION 1580 "The value returned in the Ingress Action Field of the MTR. 1581 The value ingNoTlv(0) indicates that no Reply Ingress TLV was 1582 returned in the MTM." 1583 REFERENCE "TRILL-FM 11.2.3" 1584 ::= { trillOamMtrEntry 6 } 1586 trillOamMepMtrIngressMac OBJECT-TYPE 1587 SYNTAX MacAddress 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "MAC address returned in the ingress MAC address field." 1592 REFERENCE "TRILL-FM 8.4.1" 1593 ::= { trillOamMtrEntry 7 } 1595 trillOamMepMtrIngressPortIdSubtype OBJECT-TYPE 1596 SYNTAX LldpPortId 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "Ingress Port ID. The format of this object is determined by 1601 the value of the trillOamMepMtrIngressPortIdSubtype object." 1602 REFERENCE "TRILL-FM 8.4.1" 1603 ::= { trillOamMtrEntry 8 } 1605 trillOamMepMtrIngressPortId OBJECT-TYPE 1606 SYNTAX LldpPortId 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "Ingress Port ID. The format of this object is determined by 1611 the value of the trillOamMepMtrIngressPortId object." 1612 REFERENCE "TRILL-FM 8.4.1" 1613 ::= { trillOamMtrEntry 9 } 1615 trillOamMepMtrEgress OBJECT-TYPE 1616 SYNTAX Dot1agCfmEgressActionFieldValue 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "The value returned in the Egress Action Field of the MTR. 1621 The value ingNoTlv(0) indicates that no Reply Egress TLV was 1622 returned in the MTR." 1623 REFERENCE "TRILL-FM 8.4.1" 1624 ::= { trillOamMtrEntry 10 } 1626 trillOamMepMtrEgressMac OBJECT-TYPE 1627 SYNTAX MacAddress 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "MAC address returned in the egress MAC address field." 1633 REFERENCE "TRILL-FM 8.4.1" 1634 ::= { trillOamMtrEntry 11 } 1636 trillOamMepMtrEgressPortIdSubtype OBJECT-TYPE 1637 SYNTAX LldpPortId 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "Egress Port ID. The format of this object is determined by 1642 the value of the trillOamMepMtrEgressPortIdSubtype object." 1643 REFERENCE "TRILL-FM 8.4.1" 1644 ::= { trillOamMtrEntry 12 } 1646 trillOamMepMtrEgressPortId OBJECT-TYPE 1647 SYNTAX LldpPortId 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "Egress Port ID. The format of this object is determined by 1652 the value of the trillOamMepMtrEgressPortId object." 1653 REFERENCE "TRILL-FM 8.4.1" 1654 ::= { trillOamMtrEntry 13 } 1656 trillOamMepMtrChassisIdSubtype OBJECT-TYPE 1657 SYNTAX LldpChassisIdSubtype 1658 MAX-ACCESS read-only 1659 STATUS current 1660 DESCRIPTION 1661 "This object specifies the format of the Chassis ID returned 1662 in the Sender ID TLV of the MTR, if any. This value is 1663 meaningless if the trillOamMepMtrChassisId has a length of 0." 1664 REFERENCE "TRILL-FM 8.4.1" 1665 ::= { trillOamMtrEntry 14 } 1667 trillOamMepMtrChassisId OBJECT-TYPE 1668 SYNTAX LldpChassisId 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "The Chassis ID returned in the Sender ID TLV of the MTR, if 1673 any. The format of this object is determined by the 1674 value of the trillOamMepMtrChassisIdSubtype object." 1675 REFERENCE "TRILL-FM 8.4.1" 1676 ::= { trillOamMtrEntry 15 } 1678 trillOamMepMtrOrganizationSpecificTlv OBJECT-TYPE 1679 SYNTAX OCTET STRING (SIZE (0..0 | 4..1500)) 1680 MAX-ACCESS read-only 1681 STATUS current 1682 DESCRIPTION 1683 "All Organization specific TLVs returned in the MTR, if 1684 any. Includes all octets including and following the TLV 1685 Length field of each TLV, concatenated together." 1686 REFERENCE "TRILL-FM 8.4.1" 1687 ::= { trillOamMtrEntry 16 } 1689 trillOamMepMtrNextHopNicknames OBJECT-TYPE 1690 SYNTAX OCTET STRING (SIZE (0..0 | 4..1500)) 1691 MAX-ACCESS read-only 1692 STATUS current 1693 DESCRIPTION 1694 "Next hop Rbridge List TLV returned in the PTR, if 1695 any. Includes all octets including and following the TLV 1696 Length field of each TLV, concatenated together." 1697 REFERENCE "TRILL-FM 8.4.3" 1698 ::= { trillOamMtrEntry 17 } 1700 trillOamMepMtrReceiverAvailability OBJECT-TYPE 1701 SYNTAX TruthValue 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "True value indicates that MTR response contained 1706 Multicast receiver availability TLV" 1707 REFERENCE "TRILL-FM 8.4.10" 1708 ::= { trillOamMtrEntry 18 } 1710 trillOamMepMtrReceiverCount OBJECT-TYPE 1711 SYNTAX TruthValue 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION 1715 "Indicates the number of Multicast receivers available on 1716 responding RBridge on the VLAN specified by the 1717 diagnostic VLAN." 1718 REFERENCE "TRILL-FM 8.4.10" 1719 ::= { trillOamMtrEntry 19 } 1721 -- ******************************************************************* 1722 -- TRILL OAM MEP Database Table 1723 -- ******************************************************************* 1725 trillOamMepDbTable OBJECT-TYPE 1726 SYNTAX SEQUENCE OF TrillOamMepDbEntry 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "This table is an extension of the dot1agCfmMepDbTable and rows 1731 are automatically added or deleted from this table based upon 1732 row creation and destruction of the dot1agCfmMepDbTable. 1733 " 1734 REFERENCE 1735 "[TRILL-FM]" 1736 ::= { trillOamMep 5 } 1738 trillOamMepDbEntry OBJECT-TYPE 1739 SYNTAX TrillOamMepDbEntry 1740 MAX-ACCESS not-accessible 1741 STATUS current 1742 DESCRIPTION 1743 "The conceptual row of trillOamMepDbTable." 1744 AUGMENTS { 1745 dot1agCfmMepDbEntry 1746 } 1747 ::= { trillOamMepDbTable 1 } 1749 TrillOamMepDbEntry ::= SEQUENCE { 1750 trillOamMepDbFlowIndex Unsigned32, 1751 trillOamMepDbFlowEntropy OCTET STRING, 1752 trillOamMepDbFlowState Dot1agCfmRemoteMepState, 1753 trillOamMepDbFlowFailedOkTime TimeStamp, 1754 trillOamMepDbRbridgeName Unsigned32, 1755 trillOamMepDbLastGoodSeqNum Counter32 1756 } 1758 trillOamMepDbFlowIndex OBJECT-TYPE 1759 SYNTAX Unsigned32 (1..65535) 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "This object identifies the Flow. If Flow Identifier TLV is received 1764 than index received can also be used. 1765 " 1766 REFERENCE "TRILL-FM" 1767 ::= {trillOamMepDbEntry 1 } 1769 trillOamMepDbFlowEntropy OBJECT-TYPE 1770 SYNTAX OCTET STRING 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "128 byte Flow Entropy. 1775 " 1776 REFERENCE "TRILL-FM section 3." 1777 ::= {trillOamMepDbEntry 2 } 1779 trillOamMepDbFlowState OBJECT-TYPE 1780 SYNTAX Dot1agCfmRemoteMepState 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "The operational state of the remote MEP (flow based) 1785 IFF State machines. State Machine is running now per 1786 flow." 1787 REFERENCE "TRILL-FM" 1788 ::= {trillOamMepDbEntry 3 } 1790 trillOamMepDbFlowFailedOkTime OBJECT-TYPE 1791 SYNTAX TimeStamp 1792 MAX-ACCESS read-only 1793 STATUS current 1794 DESCRIPTION 1795 "The Time (sysUpTime) at which the Remote Mep Flow state 1796 machine last entered either the RMEP_FAILED or RMEP_OK 1797 state. 1798 " 1799 REFERENCE "TRILL-FM" 1800 ::= {trillOamMepDbEntry 4 } 1802 trillOamMepDbRbridgeName OBJECT-TYPE 1803 SYNTAX Unsigned32(0..65471) 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "Remote MEP Rbridge Nickname" 1808 REFERENCE "TRILL-FM RFC 6325 section 3" 1809 ::= {trillOamMepDbEntry 5 } 1811 trillOamMepDbLastGoodSeqNum OBJECT-TYPE 1812 SYNTAX Counter32 1813 MAX-ACCESS read-only 1814 STATUS current 1815 DESCRIPTION 1816 "Last Sequence Number received." 1817 REFERENCE "TRILL-FM 13.1" 1818 ::= {trillOamMepDbEntry 6} 1820 -- ***************************************************************************** 1821 -- TRILL OAM MIB NOTIFICATIONS (TRAPS) 1822 -- This notification is sent to management entity whenever a MEP loses/restores 1823 -- contact with its peer Flow Meps 1824 -- ***************************************************************************** 1825 trillOamFaultAlarm NOTIFICATION-TYPE 1826 OBJECTS { trillOamMepDbFlowState } 1827 STATUS current 1828 DESCRIPTION 1829 "A MEP Flow has a persistent defect condition. 1830 A notification (fault alarm) is sent to the management 1831 entity with the OID of the Flow that has detected the fault. 1833 The management entity receiving the notification can identify 1834 the system from the network source address of the 1835 notification, and can identify the Flow reporting the defect 1836 by the indices in the OID of the 1837 trillOamMepFlowIndex, and trillOamFlowDefect 1838 variable in the notification: 1840 dot1agCfmMdIndex - Also the index of the MEP's 1841 Maintenance Domain table entry 1842 (dot1agCfmMdTable). 1843 dot1agCfmMaIndex - Also an index (with the MD table index) 1844 of the MEP's Maintenance Association 1845 network table entry 1846 (dot1agCfmMaNetTable), and (with the MD 1847 table index and component ID) of the 1848 MEP's MA component table entry 1849 (dot1agCfmMaCompTable). 1850 dot1agCfmMepIdentifier - MEP Identifier and final index 1851 into the MEP table (dot1agCfmMepTable). 1852 trillOamMepFlowCfgIndex - Index identifies 1853 indicates the specific Flow for the MEP" 1854 REFERENCE "TRILL-FM" 1855 ::= { trillOamNotifications 1 } 1857 -- ***************************************************************************** 1858 -- TRILL OAM MIB Module - Conformance Information 1859 -- ***************************************************************************** 1861 trillOamMibCompliances OBJECT IDENTIFIER 1862 ::= { trillOamMibConformance 1 } 1864 trillOamMibGroups OBJECT IDENTIFIER 1865 ::= { trillOamMibConformance 2 } 1867 -- ****************************************************************** 1868 -- TRILL OAM MIB Units of conformance 1869 -- ****************************************************************** 1871 trillOamMepMandatoryGroup OBJECT-GROUP 1872 OBJECTS { 1873 trillOamMepRName, 1874 trillOamMepNextPtmTId, 1875 trillOamMepNextMtmTId, 1876 trillOamMepPtrIn, 1877 trillOamMepPtrInOutofOrder, 1878 trillOamMepPtrOut, 1879 trillOamMepMtrIn, 1880 trillOamMepMtrInOutofOrder, 1881 trillOamMepMtrOut, 1882 trillOamMepTxLbmDestRName, 1883 trillOamMepTxLbmHC, 1884 trillOamMepTxLbmReplyModeOob, 1885 trillOamMepTransmitLbmReplyIp, 1886 trillOamMepTxLbmFlowEntropy, 1887 trillOamMepTxPtmDestRName, 1888 trillOamMepTxPtmHC, 1889 trillOamMepTxPtmReplyModeOob, 1890 trillOamMepTransmitPtmReplyIp, 1891 trillOamMepTxPtmFlowEntropy, 1892 trillOamMepTxPtmStatus, 1893 trillOamMepTxPtmResultOK, 1894 trillOamMepTxPtmMessages, 1895 trillOamMepTxPtmSeqNumber, 1896 trillOamMepTxMtmTree, 1897 trillOamMepTxMtmHC, 1898 trillOamMepTxMtmReplyModeOob, 1899 trillOamMepTransmitMtmReplyIp, 1900 trillOamMepTxMtmFlowEntropy, 1901 trillOamMepTxMtmStatus, 1902 trillOamMepTxMtmResultOK, 1903 trillOamMepTxMtmMessages, 1904 trillOamMepTxMtmSeqNumber, 1905 trillOamMepTxMtmScopeList 1906 } 1907 STATUS current 1908 DESCRIPTION 1909 "Mandatory objects for the TRILL OAM MEP group." 1910 ::= { trillOamMibGroups 1 } 1912 trillOamMepFlowCfgTableGroup OBJECT-GROUP 1913 OBJECTS { 1914 trillOamMepFlowCfgFlowEntropy, 1915 trillOamMepFlowCfgDestRName, 1916 trillOamMepFlowCfgFlowHC, 1917 trillOamMepFlowCfgRowStatus 1918 } 1919 STATUS current 1920 DESCRIPTION 1921 "Trill OAM MEP Flow Configuration objects group." 1922 ::= { trillOamMibGroups 2 } 1924 trillOamPtrTableGroup OBJECT-GROUP 1925 OBJECTS { 1926 trillOamMepPtrHC, 1927 trillOamMepPtrFlag, 1928 trillOamMepPtrErrorCode, 1929 trillOamMepPtrTerminalMep, 1930 trillOamMepPtrLastEgressId, 1931 trillOamMepPtrIngress, 1932 trillOamMepPtrIngressMac, 1933 trillOamMepPtrIngressPortIdSubtype, 1934 trillOamMepPtrIngressPortId, 1935 trillOamMepPtrEgress, 1936 trillOamMepPtrEgressMac, 1937 trillOamMepPtrEgressPortIdSubtype, 1938 trillOamMepPtrEgressPortId, 1939 trillOamMepPtrChassisIdSubtype, 1940 trillOamMepPtrChassisId, 1941 trillOamMepPtrOrganizationSpecificTlv, 1942 trillOamMepPtrNextHopNicknames 1943 } 1944 STATUS current 1945 DESCRIPTION 1946 "Trill OAM MEP PTR objects group." 1947 ::= { trillOamMibGroups 3 } 1949 trillOamMtrTableGroup OBJECT-GROUP 1950 OBJECTS { 1951 trillOamMepMtrFlag, 1952 trillOamMepMtrErrorCode, 1953 trillOamMepMtrLastEgressId, 1954 trillOamMepMtrIngress, 1955 trillOamMepMtrIngressMac, 1956 trillOamMepMtrIngressPortIdSubtype, 1957 trillOamMepMtrIngressPortId, 1958 trillOamMepMtrEgress, 1959 trillOamMepMtrEgressMac, 1960 trillOamMepMtrEgressPortIdSubtype, 1961 trillOamMepMtrEgressPortId, 1962 trillOamMepMtrChassisIdSubtype, 1963 trillOamMepMtrChassisId, 1964 trillOamMepMtrOrganizationSpecificTlv, 1965 trillOamMepMtrNextHopNicknames, 1966 trillOamMepMtrReceiverAvailability, 1967 trillOamMepMtrReceiverCount 1969 } 1970 STATUS current 1971 DESCRIPTION 1972 "Trill OAM MEP MTR objects group." 1973 ::= { trillOamMibGroups 4 } 1975 trillOamMepDbGroup OBJECT-GROUP 1976 OBJECTS { 1977 trillOamMepDbFlowIndex, 1978 trillOamMepDbFlowEntropy, 1979 trillOamMepDbFlowState, 1980 trillOamMepDbFlowFailedOkTime, 1981 trillOamMepDbRbridgeName, 1982 trillOamMepDbLastGoodSeqNum 1983 } 1985 STATUS current 1986 DESCRIPTION 1987 "Trill OAM MEP DB objects group." 1988 ::= { trillOamMibGroups 5 } 1990 trillOamNotificationGroup NOTIFICATION-GROUP 1991 NOTIFICATIONS { 1992 trillOamFaultAlarm 1993 } 1994 STATUS current 1995 DESCRIPTION 1996 "Objects for Notification Group" 1997 ::= { trillOamMibGroups 6 } 1999 -- ****************************************************************** 2000 -- TRILL OAM MIB Module Compliance statements 2001 -- ****************************************************************** 2003 trillOamMibCompliance MODULE-COMPLIANCE 2004 STATUS current 2005 DESCRIPTION 2006 "The compliance statement for the TRILL OAM MIB." 2007 MODULE -- this module 2008 MANDATORY-GROUPS { 2009 trillOamMepMandatoryGroup, 2010 trillOamMepFlowCfgTableGroup, 2011 trillOamPtrTableGroup, 2012 trillOamMtrTableGroup, 2013 trillOamMepDbGroup, 2014 trillOamNotificationGroup 2015 } 2016 ::= { trillOamMibCompliances 1 } 2018 -- Compliance requirement for read-only implementation. 2020 trillOamMibReadOnlyCompliance MODULE-COMPLIANCE 2021 STATUS current 2022 DESCRIPTION 2023 "Compliance requirement for implementation that only 2024 provide read-only support for TRILL-OAM-MIB. 2025 Such devices can be monitored but cannot be configured 2026 using this MIB module 2027 " 2028 MODULE -- this module 2029 MANDATORY-GROUPS { 2030 trillOamMepMandatoryGroup, 2031 trillOamMepFlowCfgTableGroup, 2032 trillOamPtrTableGroup, 2033 trillOamMtrTableGroup, 2034 trillOamMepDbGroup, 2035 trillOamNotificationGroup 2036 } 2037 -- trillOamMepTable 2039 OBJECT trillOamMepTxLbmDestRName 2040 MIN-ACCESS read-only 2041 DESCRIPTION 2042 "Write access is not required." 2044 OBJECT trillOamMepTxLbmHC 2045 MIN-ACCESS read-only 2046 DESCRIPTION 2047 "Write access is not required." 2049 OBJECT trillOamMepTxLbmReplyModeOob 2050 MIN-ACCESS read-only 2051 DESCRIPTION 2052 "Write access is not required." 2054 OBJECT trillOamMepTransmitLbmReplyIp 2055 MIN-ACCESS read-only 2056 DESCRIPTION 2057 "Write access is not required." 2059 OBJECT trillOamMepTxLbmFlowEntropy 2060 MIN-ACCESS read-only 2061 DESCRIPTION 2062 "Write access is not required." 2064 OBJECT trillOamMepTxPtmDestRName 2065 MIN-ACCESS read-only 2066 DESCRIPTION 2067 "Write access is not required." 2069 OBJECT trillOamMepTxPtmHC 2070 MIN-ACCESS read-only 2071 DESCRIPTION 2072 "Write access is not required." 2074 OBJECT trillOamMepTxPtmReplyModeOob 2075 MIN-ACCESS read-only 2076 DESCRIPTION 2077 "Write access is not required." 2079 OBJECT trillOamMepTransmitPtmReplyIp 2080 MIN-ACCESS read-only 2081 DESCRIPTION 2082 "Write access is not required." 2084 OBJECT trillOamMepTxPtmFlowEntropy 2085 MIN-ACCESS read-only 2086 DESCRIPTION 2087 "Write access is not required." 2089 OBJECT trillOamMepTxPtmStatus 2090 MIN-ACCESS read-only 2091 DESCRIPTION 2092 "Write access is not required." 2094 OBJECT trillOamMepTxPtmResultOK 2095 MIN-ACCESS read-only 2096 DESCRIPTION 2097 "Write access is not required." 2099 OBJECT trillOamMepTxPtmMessages 2100 MIN-ACCESS read-only 2101 DESCRIPTION 2102 "Write access is not required." 2104 OBJECT trillOamMepTxPtmSeqNumber 2105 MIN-ACCESS read-only 2106 DESCRIPTION 2107 "Write access is not required." 2109 OBJECT trillOamMepTxMtmTree 2110 MIN-ACCESS read-only 2111 DESCRIPTION 2112 "Write access is not required." 2114 OBJECT trillOamMepTxMtmHC 2115 MIN-ACCESS read-only 2116 DESCRIPTION 2117 "Write access is not required." 2119 OBJECT trillOamMepTxMtmReplyModeOob 2120 MIN-ACCESS read-only 2121 DESCRIPTION 2122 "Write access is not required." 2124 OBJECT trillOamMepTransmitMtmReplyIp 2125 MIN-ACCESS read-only 2126 DESCRIPTION 2127 "Write access is not required." 2129 OBJECT trillOamMepTxMtmFlowEntropy 2130 MIN-ACCESS read-only 2131 DESCRIPTION 2132 "Write access is not required." 2134 OBJECT trillOamMepTxMtmStatus 2135 MIN-ACCESS read-only 2136 DESCRIPTION 2137 "Write access is not required." 2139 OBJECT trillOamMepTxMtmResultOK 2140 MIN-ACCESS read-only 2141 DESCRIPTION 2142 "Write access is not required." 2144 OBJECT trillOamMepTxMtmMessages 2145 MIN-ACCESS read-only 2146 DESCRIPTION 2147 "Write access is not required." 2149 OBJECT trillOamMepTxMtmSeqNumber 2150 MIN-ACCESS read-only 2151 DESCRIPTION 2152 "Write access is not required." 2154 OBJECT trillOamMepTxMtmScopeList 2155 MIN-ACCESS read-only 2156 DESCRIPTION 2157 "Write access is not required." 2159 -- trillOamMepFlowCfgTable 2160 OBJECT trillOamMepFlowCfgFlowEntropy 2161 MIN-ACCESS read-only 2162 DESCRIPTION 2163 "Write access is not required." 2165 OBJECT trillOamMepFlowCfgDestRName 2166 MIN-ACCESS read-only 2167 DESCRIPTION 2168 "Write access is not required." 2170 OBJECT trillOamMepFlowCfgFlowHC 2171 MIN-ACCESS read-only 2172 DESCRIPTION 2173 "Write access is not required." 2175 OBJECT trillOamMepFlowCfgRowStatus 2176 MIN-ACCESS read-only 2177 DESCRIPTION 2178 "Write access is not required." 2180 ::= { trillOamMibCompliances 2 } 2182 END 2184 8. Security Considerations 2186 This MIB relates to a system that will provide network connectivity 2187 and packet forwarding services. As such, improper manipulation of the 2188 objects represented by this MIB may result in denial of service to a 2189 large number of end-users. 2191 There are number of management objects defined in this MIB module 2192 with a MAX-ACCESS clause of read-create. Such objects may be 2193 considered sensitive or vulnerable in some network environments. The 2194 support for SET operations in a non-secure environment without proper 2195 protection can have negative effect on sensitivity/vulnerability are 2196 described below. 2198 Some of the readable objects in this MIB module (objects with a MAC- 2199 ACCESS other than not-accessible) may be considered sensitive or 2200 vulnerable in some network environments. It is thus important to 2201 control GET and/or NOTIFY access to these objects and possibly to 2202 encrypt the values of these objects when sending them over the 2203 network via SNMP. 2205 SNMP version prior to SNMPv3 did not include adequate security. Even 2206 if the network itself is secure, there is no control as to who on the 2207 secure network is allowed to access and GET/SET 2208 (read/change/create/delete) the objects in this MIB module. 2210 It is RECOMMENDED that implementers consider the security features as 2211 provided by the SNMPv3 framework (see [RFC3410], section 8), 2212 including full support for the SNMPv3 cryptographic mechanism (for 2213 authentication and privacy). 2215 Further, deployment of SNMP version prior to SNMPv3 is NOT 2216 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2217 enable cryptographic security. It is then a customer/operator 2218 responsibility to ensure that the SNMP entity giving access to an 2219 instance of this MIB module is properly configured to give access to 2220 the objects only to those principals (users) that have legitimate 2221 rights to indeed GET or SET (change/create/delete) them. 2223 9. IANA Considerations 2225 The MIB module in this document uses the following IANA-assigned 2226 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 2228 Descriptor OBJECT IDENTIFIER value 2229 ---------------------------------------- 2230 trillOamMIB { mib-2 xxx } 2232 Editor's Note (to be removed prior to publication): the IANA is 2233 requested to assign a value for "xxx" under the 'mib-2' subtree and 2234 to record the assignment in the SMI Numbers registry. When the 2235 assignment has been made, the RFC Editor is asked to replace "XXX" 2236 (here and in the MIB module) with the assigned value and to remove 2237 this note. 2239 10. References 2240 10.1. Normative References 2242 [RFC2119] Bradner, S., "Key words for use in RFCs to 2243 Indicate Requirement Levels", BCP 14, RFC 2119, March 2244 1997. 2246 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2247 Schoenwaelder, Ed., "Structure of Management Information 2248 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2250 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2251 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2252 58, RFC 2579, April 1999. 2254 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2255 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2256 STD 58, RFC 2580, April 1999. 2258 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 2259 Stewart, "Introduction and Applicability Statements for 2260 Internet-Standard Management Framework", RFC 3410, 2261 December 2002. 2263 10.2. Informative References 2265 [RFC6905] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., 2266 and R. Watve, "Requirements for Operations, 2267 Administration, and Maintenance (OAM) in Transparent 2268 Interconnection of Lots of Links (TRILL)", RFC 6905, March 2269 2013. 2271 [TRILLOAMFM] Salam, S., et.al., "TRILL OAM Framework", 2272 draft-ietf-trill-oam-framework, Work in Progress,November, 2273 2012. 2275 [TRILL-FM] Senevirathne, T., et.al., "TRILL Fault 2276 Management", draft-tissa-trill-oam-fm, Work in Progress, 2277 Feburary, 2013. 2279 11. Acknowledgments 2281 We wish to thank members of the IETF TRILL WG for their comments and 2282 suggestions. Detailed comments were provided by Sam Aldrin, and 2283 Donald Eastlake. 2285 Copyright (c) 2014 IETF Trust and the persons identified as authors 2286 of the code. All rights reserved. Redistribution and use in source 2287 and binary forms, with or without modification, is permitted pursuant 2288 to, and subject to the license terms contained in, the Simplified BSD 2289 License set forth in Section 4.c of the IETF Trust's Legal Provisions 2290 Relating to IETF Documents (http://trustee.ietf.org/license-info). 2292 Copyright (c) 2014 IETF Trust and the persons identified as authors 2293 of the code. All rights reserved. Redistribution and use in source 2294 and binary forms, with or without modification, are permitted 2295 provided that the following conditions are met: 2297 o Redistributions of source code must retain the above copyright 2298 notice, this list of conditions and the following disclaimer. 2300 o Redistributions in binary form must reproduce the above 2301 copyright notice, this list of conditions and the following 2302 disclaimer in the documentation and/or other materials provided 2303 with the distribution. 2305 o Neither the name of Internet Society, IETF or IETF Trust, nor 2306 the names of specific contributors, may be used to endorse or 2307 promote products derived from this software without specific prior 2308 written permission. 2310 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2311 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2312 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2313 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2314 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2315 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2316 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2317 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2318 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2319 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2320 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2322 Authors' Addresses 2324 Deepak Kumar 2325 Cisco 2326 510 McCarthy Blvd, 2327 Milpitas, CA 95035, USA 2328 Phone : +1 408-853-9760 2329 Email: dekumar@cisco.com 2331 Samer Salam 2332 Cisco 2333 595 Burrard St. Suite 2123 2334 Vancouver, BC V7X 1J1, Canada 2335 Email: ssalam@cisco.com 2337 Tissa Senevirathne 2338 Cisco 2339 375 East Tasman Drive 2340 San Jose, CA 95134, USA 2341 Email: tsenevir@cisco.com