Tech-invite3GPPspaceIETFspace
959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 7784

Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIB

Pages: 50
Proposed Standard
Part 1 of 3 – Pages 1 to 8
None   None   Next

Top   ToC   RFC7784 - Page 1
Internet Engineering Task Force (IETF)                          D. Kumar
Request for Comments: 7784                                      S. Salam
Category: Standards Track                                          Cisco
ISSN: 2070-1721                                          T. Senevirathne
                                                           February 2016

          Transparent Interconnection of Lots of Links (TRILL)
         Operations, Administration, and Maintenance (OAM) MIB


Abstract

This document specifies the MIB for the OAM (Operations, Administration, and Maintenance) objects for IETF TRILL (Transparent Interconnection of Lots of Links). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7784. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Top   ToC   RFC7784 - Page 2

Table of Contents

1. Introduction ....................................................2 2. The Internet-Standard Management Framework ......................3 3. Conventions .....................................................3 4. Overview ........................................................4 5. Structure of the MIB Module .....................................4 5.1. Textual Conventions ........................................4 5.2. The TRILL OAM MIB Subtree ..................................4 5.3.1. The Notifications Subtree ...........................5 5.3.2. The Table Structures ................................5 5.3.2.1. trillOamMepTable Objects ...................5 5.3.2.2. trillOamMepFlowCfgTable Objects ............6 5.3.2.3. trillOamPtrTable Objects ...................6 5.3.2.4. trillOamMtvrTable Objects ..................6 5.3.2.5. trillOamMepDbTable Objects .................6 6. Relationship to Other MIB Modules ...............................6 6.1. Relationship to the IEEE8021-TC-MIB ........................7 6.2. Relationship to the IEEE8021-CFM-MIB .......................7 6.3. MIB Modules Required for IMPORTS ...........................8 7. Definitions .....................................................8 8. Security Considerations ........................................44 9. IANA Considerations ............................................47 10. References ....................................................47 10.1. Normative References .....................................47 10.2. Informative References ...................................49 Acknowledgments ...................................................50 Authors' Addresses ................................................50

1. Introduction

Overall, TRILL OAM meets the requirements given in [RFC6905]. The general framework for TRILL OAM is specified in [RFC7174]. The details of the Fault Management (FM) solution, conforming to that framework, are presented in [RFC7455]. The solution leverages the message format defined in Ethernet Connectivity Fault Management (CFM) [802.1Q] as the basis for the TRILL OAM message channel. This document uses the CFM MIB modules defined in [802.1Q] as the basis for TRILL OAM MIB and augments the existing tables to add new TRILL managed objects required by TRILL. This document further specifies a new table with associated managed objects for TRILL OAM- specific capabilities.
Top   ToC   RFC7784 - Page 3

2. The Internet-Standard Management Framework

For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].

3. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Abbreviations used in the document include the following: CCM - Continuity Check Message [802.1Q] EMS - Element Management System [Q.840.1] MEP - Maintenance End Point [RFC7174] [802.1Q] MIP - Maintenance Intermediate Point [RFC7174] [802.1Q] MP - Maintenance Point [RFC7174] MTVM - Multi-destination Tree Verification Message [RFC7455] MTVR - Multi-destination Tree Verification Reply [RFC7455] NMS - Network Management System [Q.840.1] PTM - Path Trace Message [RFC7455] PTR - Path Trace Reply [RFC7455]
Top   ToC   RFC7784 - Page 4

4. Overview

The TRILL OAM MIB module provides an overall framework for managing TRILL OAM. It leverages the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB modules defined in [802.1Q], and it augments the Maintenance End Point (MEP) and MEP Db entries. It also adds a new table for messages specific to TRILL OAM.

5. Structure of the MIB Module

Objects in this MIB module are arranged into subtrees. Each subtree is organized as a set of related objects. The various subtrees are shown below, supplemented with the required elements of the IEEE8021-CFM-MIB module.

5.1. Textual Conventions

Textual conventions are defined to represent object types relevant to the TRILL OAM MIB.

5.2. The TRILL OAM MIB Subtree

The TRILL OAM MIB tree described below consists of trilloamNotifications (Traps) and trillOamMibObjects. The trilloamNotifications are sent to the management entity whenever a MEP loses/restores contact with its peer flow MEPs. The TRILL OAM MIB per MEP Objects are defined in the trillOamMepTable. The trillOamMepTable augments the dot1agCfmMepEntry (please see Section 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally defined for an individual MEP and its associated flow.
Top   ToC   RFC7784 - Page 5
TRILL-OAM-MIB

|--trillOamNotifications          (trillOamMib 0}

   |--trillOamFaultAlarm

|--trillOamMibObjects             {trillOamMib 1}

   |--trillOamMep                 {trillOamMibObjects 1}

      |--trillOamMepTable         {trillOamMep 1}  - Local TRLL config

      |--trillOamMepFlowCfgTable

      |--trillOamPtrTable

      |--trillOamMtvrTable

      |--trillOamMepDbTable

5.3.1. The Notifications Subtree

Notifications (fault alarms) are sent to the management entity with the OID of the MEP that has detected the fault. Notifications are generated whenever MEP loses/restores contact with its peer flow MEPs.

5.3.2. The Table Structures

The TRILL OAM MIB per MEP Objects are defined in the trillOamMepTable. The trillOamMepTable augments the dot1agCfmMepEntry (please see Section 6.1) defined in IEEE8021-CFM-MIB. It includes objects that are locally defined for an individual MEP and its associated flow.
5.3.2.1. trillOamMepTable Objects
This table is an extension of the dot1agCfmMepTable. Rows are automatically added or deleted from this table based upon row creation and destruction of the dot1agCfmMepTable. This table represents the local MEP TRILL OAM configuration table. The primary purpose of this table is provide local parameters for the TRILL OAM function found in [RFC7455] and instantiated at a MEP.
Top   ToC   RFC7784 - Page 6
5.3.2.2. trillOamMepFlowCfgTable Objects
Each row in this table represents a Flow Configuration Entry for the associated MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MANET, and MEP tables. The fourth index is the specific Flow Configuration Entry on the selected MEP. Some writable objects in this table are only applicable in certain cases (as described under each object below), and attempts to write values for them in other cases will be ignored.
5.3.2.3. trillOamPtrTable Objects
Each row in this table represents a Path Trace Reply Entry for the Defined MEP and Transaction. This table uses four indices. The first three indices identify the MEP and the fourth index specifies the Transaction Identifier. This Transaction Identifier uniquely identifies the response for a MEP, which can have multiple flows.
5.3.2.4. trillOamMtvrTable Objects
This table includes managed objects for the Multi-destination Reply. Each row in the table represents a Multi-destination Reply Entry for the defined MEP and Transaction. This table uses the following five indices: 1) Maintenance Domain, 2) MANET, 3) MEP tables, 4) Transaction Identifier of selected MEP, and 5) receive order of Multi-destination replies. Some writable objects in this table are only applicable in certain cases (as described under each object below), and attempts to write a value for them in other cases will be ignored.
5.3.2.5. trillOamMepDbTable Objects
This table is an augmentation of the dot1agCfmMepDbTable, and rows are automatically added or deleted from this table based upon row creation and destruction of the dot1agCfmMepDbTable.

6. Relationship to Other MIB Modules

The IEEE8021-CFM-MIB [IEEE8021-CFM-MIB] and [LLDP-MIB] contain objects that are relevant to the TRILL OAM MIB. Management objects contained in these modules are not duplicated here, to reduce overlap to the extent possible. From the IEEE8021-CFM-MIB, the following objects are imported: o dot1agCfmMdIndex o dot1agCfmMaIndex
Top   ToC   RFC7784 - Page 7
      o dot1agCfmMepIdentifier

      o dot1agCfmMepEntry

      o dot1agCfmMepDbEntry

      o Dot1agCfmIngressActionFieldValue

      o Dot1agCfmEgressActionFieldValue

      o Dot1agCfmRemoteMepState

   From the [LLDP-MIB], the following objects are imported:

      o LldpChassisId

      o LldpChassisIdSubtype

      o LldpPortId

6.1. Relationship to the IEEE8021-TC-MIB

In TRILL, traffic labeling can be done using either a 12-bit VLAN or a 24-bit Fine-Grained Label (FGL) [RFC7172]. The IEEE8021-TC-MIB definition of IEEE8021ServiceSelectorType includes the following two values: - 1 representing a vlanId, and - 2 representing a 24-bit isid We have chosen to use value 2 for TRILL's FGL. As such, TRILL OAM MIB will import IEEE8021ServiceSelectorType, IEEE8021ServiceSelectorValueOrNone, and IEEE8021ServiceSelectorValue from IEEE8021-TC-MIB.

6.2. Relationship to the IEEE8021-CFM-MIB

trillOamMepTable augments dot1agCfmMepEntry. Implementation of IEEE8021-CFM-MIB is required as we are augmenting the IEEE-CFM-MIB Table. Objects/Tables that are not applicable to a TRILL implementation have to be handled by the TRILL implementation backend, and appropriate default values, as described in IEEE8021-CFM-MIB, have to be returned.
Top   ToC   RFC7784 - Page 8
   The TRILL OAM implementation doesn't support the Link Trace Message
   or Link Trace Reply, since, as described in RFC 7455, the Path Trace
   Message and Reply for unicast traffic and Multi-destination Tree
   verification Message and Reply for multicast traffic have been
   substituted for them.  Statistics for these messages should default
   as per IEEE8021-CFM-MIB.

6.3. MIB Modules Required for IMPORTS

The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IEEE-8021-CFM-MIB, and LLDP-MIB.


(page 8 continued on part 2)

Next Section