Network Working Group Martin Dubuc Internet Draft edgeflow, Inc. Expires: July 2001 Link Management Protocol Management Information Base Using SMIv2 draft-dubuc-lmp-mib-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Table of Contents 1. Abstract ..................................................... 2 2. Introduction ................................................. 2 3. Terminology .................................................. 2 4. The SNMP Management Framework ................................ 3 4.1. Object Definitions ........................................... 4 5. Feature Checklist ............................................ 4 6. Outline ...................................................... 5 6.1. Summary of LMP MIB ........................................... 5 7. Brief Description of MIB Objects ............................. 6 7.1. lmpInterfaceTable ............................................ 6 7.2. lmpLinkVerificationTable ..................................... 6 7.3. lmpControlChannelTable ....................................... 6 7.4. lmpLinkBundleTable ........................................... 6 7.5. lmpDataBearingLinkTable ...................................... 6 8. Example of LMP Control Channel Interface Setup ............... 7 Dubuc Expires July 2001 [Page 1] Internet Draft MPLS LMP MIB January 26, 2001 9. Application of the Interface Group to LMP .................... 9 9.1. Support of the LMP Layer by ifTable .......................... 9 10. The Use of RowPointer ........................................ 11 11. Link Management Protocol MIB Definitions ..................... 11 12. Security Considerations ...................................... 35 13. Acknowledgments .............................................. 36 14. References ................................................... 36 15. Author's Addresses ........................................... 39 16. Full Copyright Statement ..................................... 39 1. Abstract This memo defines an experimental portion of the Management Informa- tion Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP) [LMP]. 2. Introduction This memo defines an experimental portion of the Management Informa- tion Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP) [LMP]. Comments should be made directly to the MPLS mailing list at mpls@uu.net. This memo does not, in its draft form, specify a standard for the Internet community. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119, reference [BCP14]. 3. Terminology This document uses terminology from the document describing the Link Management Protocol [LMP]. LMP messages are conceptually exchanged over the control channel interface. The control channel interface is a logical entity built around a collection of control channels. One of these channels is the active control channel and carries the actual control plane traffic. The other channels are used as standby Dubuc Expires July 2001 [Page 2] Internet Draft MPLS LMP MIB January 26, 2001 control channels. The active control channel can also be used to exchange MPLS control plane information or routing information. LMP is designed to aggregate one or more similar entities between a node pair into a link bundle [BUNDLE]. Those entities as sometimes referred to as component links (e.g. fiber) or ports (e.g. lambda). In this MIB, those entities are called data-bearing links. Within a link bundle, a number of data-bearing links are considered as primary and the rest as secondary. If any of the primary data-bearing links fails, data traffic switches over to one of the secondary data- bearing links. Each link bundle is associated with one and only one control channel interface. This control channel interface is used to manage the data-bearing links within the link bundle. However, a control channel interface can service several link bundles. 4. The SNMP Management Framework The SNMP Management Framework presently consists of five major com- ponents: - An overall architecture, described in RFC 2271 [SNMPArch]. - Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The second version, called SMIv2, is described in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. - Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [SNMPv1]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. - Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in RFC 1157 [SNMPv1]. A second set of protocol operations and associated PDU formats is described in RFC 1905 Dubuc Expires July 2001 [Page 3] Internet Draft MPLS LMP MIB January 26, 2001 [SNMPv2PO]. - A set of fundamental applications described in RFC 2273 [SNMPv3App] and the view-based access control mechanism described in RFC 2575 [SNMPv3VACM]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possi- ble (use of Counter64). Some machine-readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine-readable informa- tion is not considered to change the semantics of the MIB. 4.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to also refer to the object type. 5. Feature Checklist The Link Management protocol MIB (LMP-MIB) is designed to satisfy the following requirements and constraints: - The MIB supports the enabling and disabling of LMP capability on LMP capable interfaces of a photonic switch, optical cross-connect or router. - Support is provided for configuration of the keep alive and link verification parameters. - The MIB allows the mapping between the link bundle and the control channel interface to be established either through manual Dubuc Expires July 2001 [Page 4] Internet Draft MPLS LMP MIB January 26, 2001 configuration or via the link verification procedure. - The MIB is used to express the mapping between local and remote link bundle identifiers, as well as local and remote entity interface identifiers. 6. Outline Configuring LMP through an optical device involves the following steps: - Enabling LMP on LMP capable interfaces through configuration of control channel interfaces. - Optionally specifying link verification parameters. - Configuring the data bearing links and associating them to the appropriate link bundle. - Associating the link bundles to the appropriate control channel interface. 6.1. Summary of LMP MIB The MIB objects for performing these actions consist of the following tables: - The interface configuration table (lmpInterfaceTable), which is used for enabling the LMP protocol on LMP-capable interfaces. A LMP interface is also referred to as a control channel interface. - The link verification table (lmpLinkVerificationTable), which is used for configuring the LMP link verification parameters associated with a control channel interface. - The control channel table (lmpControlChannelTable), which is used to define the control channels associated with a control channel interface. - The link bundle table (lmpLinkBundleTable), which is used for specifying link bundles and associate link bundles to a control channel interface. Dubuc Expires July 2001 [Page 5] Internet Draft MPLS LMP MIB January 26, 2001 - The data-bearing link table (lmpDataBearingLinkTable), which is used to specify the data bearing links that are associated with the link bundles. These tables are described in the subsequent sections. 7. Brief Description of MIB Objects Sections 7.1-7.3 describe objects pertaining to LMP-capable inter- faces of a photonic switch, optical cross-connect or router. Section 7.4 and 7.5 describes objects for specifying link bundles and data- bearing links. The MIB objects were derived from the LMP document [LMP]. 7.1. lmpInterfaceTable This table represents the interfaces that are LMP capable. A pho- tonic, optical cross-connect, or router creates an entry in this table for every LMP capable interface on that device. 7.2. lmpLinkVerificationTable This table represents the link verification parameters associated with the LMP control channel interfaces. 7.3. lmpControlChannelTable This table specifies the control channels that are associated with each control channel interface. 7.4. lmpLinkBundleTable This table represents the link bundles and their association with a LMP control channel interface. Dubuc Expires July 2001 [Page 6] Internet Draft MPLS LMP MIB January 26, 2001 7.5. lmpDataBearingLinkTable The data-bearing link table enumerates the data-bearing link that are associated with each link bundle. 8. Example of LMP Control Channel Interface Setup In this section we provide a brief example of using the MIB objects described in section 11 to set up a LMP control channel interface. While this example is not meant to illustrate every nuance of the MIB, it is intended as an aid to understanding some of the key concepts. It is meant to be read after going through the MIB itself. Suppose that one would like to manually create a control channel interface with two control channels (one active and one backup) that controls 3 data-bearing links (two primary and one secondary). Assume that the data-bearing links are port entity interfaces (lambdas). We also assume that the link verification procedure is not enabled. The following example illustrates which rows and corresponding objects might be created to accomplish this. First, the control channel interface must be set up. In lmpInterfaceTable: { lmpInterfaceId = 1 lmpInterfaceActiveControlChannelPtr = 0.0 lmpInterfaceConfigRetransmitInterval = 10 lmpInterfaceHelloInterval = 5 lmpInterfaceHelloDeadInterval = 15 lmpInterfaceLinkSumRetransmitInterval = 10 lmpInterfaceRowStatus = createAndGo(4) } We must next create the two control channels. In lmpControlChannelTable: { lmpInterfaceId = 1 lmpControlChannelIndex = 10 lmpControlChannelRowStatus = createAndGo(4) } { lmpInterfaceId = 1 Dubuc Expires July 2001 [Page 7] Internet Draft MPLS LMP MIB January 26, 2001 lmpControlChannelIndex = 11 lmpControlChannelRowStatus = createAndGo(4) } Next, a link bundle entry is created. In lmpLinkBundleTable: { lmpLinkBundleId = 20 lmpRemoteLinkBundleId = 33 lmpControlChannelIfPtr = lmpInterfaceId.1 lmpLinkBundleProtectionType = shared(2) lmpLinkBundleEncodingType = sonet(6) lmpLinkBundleBitRate = 100000 lmpLinkBundleWavelength = 0 lmpLinkBundleRowStatus = createAndGo(4) } Finally, the three data-bearing links are created. In lmpDataBearingLinkTable: { lmpLinkBundleId = 20 lmpDataBearingLinkEntityIfId = 40 lmpDataBearingLinkRemoteEntityIfId = 47 lmpLinkBundleProtectionType = primary(1) lmpLinkBundleRowStatus = createAndGo(4) } { lmpLinkBundleId = 20 lmpDataBearingLinkEntityIfId = 43 lmpDataBearingLinkRemoteEntityIfId = 42 lmpLinkBundleProtectionType = primary(1) lmpLinkBundleRowStatus = createAndGo(4) } { lmpLinkBundleId = 20 lmpDataBearingLinkEntityIfId = 44 lmpDataBearingLinkRemoteEntityIfId = 48 lmpLinkBundleProtectionType = secondary(2) lmpLinkBundleRowStatus = createAndGo(4) } Note that the lmpInterfaceActiveControlChannelPtr object will automatically be populated with the value lmpControlChannelIndex.10 or lmpControlChannelIndex.11 if either one of those two control Dubuc Expires July 2001 [Page 8] Internet Draft MPLS LMP MIB January 26, 2001 channel is up. Also, the lmpDataBearingLinkActivityStatus of entity interface id 40 and 43 will be set to active(1) and that of entity interface id 44 will be set to standby(2) given that the operational status of both entity interface id 40 and 43 is up. 9. Application of the Interface Group to LMP The Interfaces Group of MIB II defines generic managed objects for managing interfaces. This memo contains the media-specific extensions to the Interfaces Group for managing LMP interfaces. This memo assumes the interpretation of the Interfaces Group to be in accordance with [IFMIB] which states that the interfaces table (ifTable) contains information on the managed resource's interfaces and that each sub-layer below the internetwork layer of a network interface is considered an interface. Thus, the LMP interface is represented as an entry in the ifTable. The inter- relation of entries in the ifTable is defined by Interfaces Stack Group defined in [IFMIB]. When using LMP interfaces, the interface stack table might appear as follows: +----------------------------------------+ | LMP-interface ifType = lmp(199) + +----------------------------------------+ | Underlying Layer... + +----------------------------------------+ In the above diagram, "Underlying Layer..." refers to the ifIndex of any interface type, which has been defined for LMP interworking. Examples include ATM, Frame Relay, Ethernet, etc. 9.1. Support of the LMP Layer by ifTable Some specific interpretations of ifTable for the LMP layer follow. Object Use for the LMP layer ifIndex Each LMP interface is represented by an ifEntry. ifDescr Description of the LMP interface. Dubuc Expires July 2001 [Page 9] Internet Draft MPLS LMP MIB January 26, 2001 ifType The value that is allocated for LMP is 199. ifSpeed The total bandwidth in bits per second for use by the LMP layer. ifPhysAddress Unused. ifAdminStatus This variable indicates the administrator's intent as to whether LMP should be enabled, disabled, or running in some diagnostic testing mode on this interface. Also see [IFMIB]. ifOperStatus This value reflects the actual or operational status of LMP on this interface. ifLastChange See [IFMIB]. ifInOctets The number of received octets over the interface, i.e., the number of received, octets received as labeled packets. ifOutOctets The number of transmitted octets over the interface, i.e., the number of octets transmitted as labeled packets. ifInErrors The number of labeled packets dropped due to uncorrectable errors. ifInUnknownProtos The number of received packets discarded during packet header validation, including packets with unrecognized label values. ifOutErrors See [IFMIB]. ifName Textual name (unique on this system) of the interface or an octet string of zero length. ifLinkUpDownTrapEnable Default is disabled (2). ifConnectorPresent Set to false (2). ifHighSpeed See [IFMIB]. ifHCInOctets The 64-bit version of ifInOctets; supported if required by the compliance statements in [IFMIB]. Dubuc Expires July 2001 [Page 10] Internet Draft MPLS LMP MIB January 26, 2001 ifHCOutOctets The 64-bit version of ifOutOctets; supported if required by the compliance statements in [IFMIB]. ifAlias The non-volatile 'alias' name for the interface as specified by a network manager. ifCounterDiscontinuityTime See [IFMIB]. 10. The Use of RowPointer RowPointer is a textual convention used to identify a conceptual row in an SNMP Table by pointing to one of its objects. In this MIB, it is used in the lmpInterfaceTable to identify the active control chan- nel of a control channel interface and in the lmpLinkBundleTable to associate a link bundle with its control channel interface. In the control channel interface and link bundle tables, the lmpInterfaceAc- tiveChannelPtr and lmpControlChannelIfPtr SHOULD point to the first column of the appropriate conceptual row. 11. LMP MIB Definitions LMP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, experimental, Integer32, Unsigned32 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, RowPointer, TimeStamp FROM SNMPv2-TC InterfaceIndex, InterfaceIndexOrZero FROM IF-MIB; lmpMIB MODULE-IDENTITY LAST-UPDATED "200101261200Z" -- 26 January 2001 12:00:00 EST ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Martin Dubuc Dubuc Expires July 2001 [Page 11] Internet Draft MPLS LMP MIB January 26, 2001 Postal: edgeflow, Inc. 329 March Rd. Kanata, ON, CANADA K2K 2E1 Tel: +1-613-2709279 x253 Email: martin.dubuc@edgeflow.com" DESCRIPTION "This MIB contains managed object definitions for the Link Management Protocol (LMP) as defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., Rekhter, Y., Berger, L., Rajagopalan, B., Basak, D., Sandick, H., Zinin, A., and Banarjee, A., Link Management Protocol, Internet Draft , November 2000." -- Revision history. REVISION "200101261200Z" -- 26 January 2001 12:00:00 EST DESCRIPTION "Initial draft version." ::= { experimental 97 } -- Textual Conventions -- A control channel identifier (CCId) LmpCcId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This value represents a control channel identifier. It is a node-wide unique 32-bit integer that is assigned to each direction of the control channel interface." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." SYNTAX Unsigned32 LmpLinkBundleId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This value represents a link bundle identifier." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, Dubuc Expires July 2001 [Page 12] Internet Draft MPLS LMP MIB January 26, 2001 A. Banerjee, November 2000." SYNTAX Unsigned32 LmpInterval ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The interval delay in milliseconds." SYNTAX INTEGER (1..65535) -- Top level components of this MIB -- Tables, Scalars lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } -- Traps lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 2 } lmpNo- tifyPrefix OBJECT IDENTIFIER ::= { lmpNotifications 0 } -- Conformance lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 3 } -- LMP Control Channel Interface Table lmpInterfaceTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies LMP control channel interface capability and associated information." ::= { lmpObjects 1 } lmpInterfaceEntry OBJECT-TYPE SYNTAX LmpInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a LMP-enabled device for every control channel interface." INDEX { lmpInterfaceId } ::= { lmpInterfaceTable 1 } LmpInterfaceEntry ::= SEQUENCE { lmpInterfaceId LmpCcId, lmpInterfaceCapabilities BITS, lmpInterfaceActiveControlChannelPtr RowPointer, lmpInterfaceConfigRetransmitInterval LmpInterval, lmpInterfaceHelloInterval LmpInterval, lmpInterfaceHelloDeadInterval LmpInterval, lmpInterfaceLinkSumRetransmitInterval LmpInterval, lmpInterfaceRowStatus RowStatus, Dubuc Expires July 2001 [Page 13] Internet Draft MPLS LMP MIB January 26, 2001 lmpInterfaceStorageType StorageType, lmpInterfaceAdminStatus INTEGER, lmpInterfaceOperStatus INTEGER } lmpInterfaceId OBJECT-TYPE SYNTAX LmpCcId MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the LmpInterfaceTable." ::= { lmpInterfaceEntry 1 } lmpInterfaceCapabilities OBJECT-TYPE SYNTAX BITS { linkVerification(0), faultIsolation(1) } MAX-ACCESS read-only STATUS current DESCRIPTION "The capability bit mask indicates which extended LMP procedures are supported. If neither of those bits are set, it indicates that only the base LMP procedures are supported." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpInterfaceEntry 2 } lmpInterfaceActiveControlChannelPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "This variable represents a pointer to the active control channel for this control channel interface. This value may point at an entry in the LmpControlChannelTable to indicate which LmpControlChannelEntry is currently active on the control channel interface. A value of zero-dot-zero indicates that there is no active channel." ::= { lmpInterfaceEntry 3 } lmpInterfaceConfigRetransmitInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION Dubuc Expires July 2001 [Page 14] Internet Draft MPLS LMP MIB January 26, 2001 "This object specifies the interval that is used for the retransmission of Config messages during the parameter negotiation phase." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpInterfaceEntry 4 } lmpInterfaceHelloInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the HelloInterval parameter used in the Hello protocol keep-alive phase. It indicates how frequently LMP Hello messages will be sent." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpInterfaceEntry 5 } lmpInterfaceHelloDeadInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the HelloDeadInterval parameter used in the Hello protocol keep-alive phase. It indicates how long a device should wait before declaring the control channel dead. The HelloDeadInterval parameter must be greater than the HelloInterval parameter and should be at least three times the value of HelloInterval." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpInterfaceEntry 6 } lmpInterfaceLinkSumRetransmitInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION Dubuc Expires July 2001 [Page 15] Internet Draft MPLS LMP MIB January 26, 2001 "This object specifies the interval that is used for the retransmission of LinkSummary messages during the property correlation phase." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpInterfaceEntry 7 } lmpInterfaceRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpInterfaceEntry 8 } lmpInterfaceStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this entry." ::= { lmpInterfaceEntry 9 } lmpInterfaceAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The desired operational status of this control channel interface." ::= { lmpInterfaceEntry 10 } lmpInterfaceOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this control channel interface." ::= { lmpInterfaceEntry 11 } -- End of lmpInterfaceTable Dubuc Expires July 2001 [Page 16] Internet Draft MPLS LMP MIB January 26, 2001 -- LMP Control Channel Interface Link Verification Table lmpLinkVerificationTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpLinkVerificationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies control channel interface information associated with the LMP verification procedure." ::= { lmpObjects 2 } lmpLinkVerificationEntry OBJECT-TYPE SYNTAX LmpLinkVerificationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a LMP-enabled device for every control channel interface." AUGMENTS { lmpInterfaceEntry } ::= { lmpLinkVerificationTable 1 } LmpLinkVerificationEntry ::= SEQUENCE { lmpVerifyInterval LmpInterval, lmpVerifyDeadInterval LmpInterval, lmpVerifyTransportMechanism BITS, lmpVerifyAllLinks INTEGER } lmpVerifyInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the VerifyInterval parameter used in the LMP link verification process. It indicates the interval at which the Test messages are sent." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpLinkVerificationEntry 1 } lmpVerifyDeadInterval OBJECT-TYPE SYNTAX LmpInterval MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the VerifyDeadInterval parameter used Dubuc Expires July 2001 [Page 17] Internet Draft MPLS LMP MIB January 26, 2001 in the verification of the physical connectivity of data-bearing links. It specifies the observation period used to detect a Test message at the remote node." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpLinkVerificationEntry 2 } lmpVerifyTransportMechanism OBJECT-TYPE SYNTAX BITS { -- SONET/SDH encoding type: j0OverheadBytes(0), dccSectionOverheadBytes(1), dccLineOverheadBytes(2), pos(3) -- GigE encoding type: TBD -- 10GigE encoding type: TBD } MAX-ACCESS read-only STATUS current DESCRIPTION "This defines the transport mechanism for the Test messages. The scope of this bit mask is restricted to each link encoding type. The local node will set the bits corresponding to the various mechanisms it can support for transmitting LMP Test messages. The receiver chooses the appropriate mechanism in the BeginVerifyAck message." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpLinkVerificationEntry 3 } lmpVerifyAllLinks OBJECT-TYPE SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates whether the verification process checks all entities or only the new entities that have been added to this bundle." ::= { lmpLinkVerificationEntry 4 } -- End of lmpLinkVerificationTable Dubuc Expires July 2001 [Page 18] Internet Draft MPLS LMP MIB January 26, 2001 -- LMP Control Channel Table lmpControlChannelTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpControlChannelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides the control channel information." ::= { lmpObjects 3 } lmpControlChannelEntry OBJECT-TYPE SYNTAX LmpControlChannelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created for every control channel of the control channel interface." INDEX { lmpInterfaceId, lmpControlChannelIndex } ::= { lmpControlChannelTable 1 } LmpControlChannelEntry ::= SEQUENCE { lmpControlChannelIndex InterfaceIndexOrZero, lmpControlChannelRowStatus RowStatus, lmpControlChannelStorageType StorageType, lmpControlChannelOperStatus INTEGER } lmpControlChannelIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique interface index for an entry in the lmpControlChannelTable. This value represents the interface index for the control channel. It points to an interface entry of the LMP-layer in the ifTable." REFERENCE "RFC 2233 - The Interfaces Group MIB using SMIv2, McCloghrie, K., and F. Kastenholtz, Nov. 1997" ::= { lmpControlChannelEntry 2 } lmpControlChannelRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpControlChannelEntry 3 } Dubuc Expires July 2001 [Page 19] Internet Draft MPLS LMP MIB January 26, 2001 lmpControlChannelStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this entry." ::= { lmpControlChannelEntry 4 } lmpControlChannelOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), switchingOver(3), takingOver(4), goingDown(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The operational status of this control channel interface." ::= { lmpControlChannelEntry 5 } -- End of lmpControlChannelTable -- LMP Link Bundle Table lmpLinkBundleTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpLinkBundleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a collection of link bundles." ::= { lmpObjects 4 } lmpLinkBundleEntry OBJECT-TYPE SYNTAX LmpLinkBundleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents one link bundle. Entries in this table are indexed by the link bundle identifier." INDEX { lmpLinkBundleId } ::= { lmpLinkBundleTable 1 } LmpLinkBundleEntry ::= SEQUENCE { Dubuc Expires July 2001 [Page 20] Internet Draft MPLS LMP MIB January 26, 2001 lmpLinkBundleId INTEGER, lmpLinkBundleIdType INTEGER, lmpRemoteLinkBundleId INTEGER, lmpRemoteLinkBundleIdType INTEGER, lmpControlChannelIfPtr RowPointer, lmpLinkBundleProtectionType INTEGER, lmpLinkBundleEncodingType INTEGER, lmpLinkBundleBitRate Unsigned32, lmpLinkBundleWavelength Unsigned32, lmpLinkBundleRowStatus RowStatus, lmpLinkBundleStorageType StorageType, lmpLinkBundleOperStatus INTEGER } lmpLinkBundleId OBJECT-TYPE SYNTAX LmpLinkBundleId MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the lmpLinkBundleTable." ::= { lmpLinkBundleEntry 1 } lmpLinkBundleIdType OBJECT-TYPE SYNTAX INTEGER { numbered(0), unnumbered(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "The link bundle identifier type (numbered or unnumbered)." ::= { lmpLinkBundleEntry 2 } lmpRemoteLinkBundleId OBJECT-TYPE SYNTAX LmpLinkBundleId MAX-ACCESS read-write STATUS current DESCRIPTION "This identifies the link bundle identifier on the remote side of the link bundle. This is either configured manually or is communicated by the remote node during the link verification procedure. It is expected that for unnumbered bundles, this value will be set to 0." ::= { lmpLinkBundleEntry 3 } lmpRemoteLinkBundleIdType OBJECT-TYPE SYNTAX INTEGER { numbered(0), Dubuc Expires July 2001 [Page 21] Internet Draft MPLS LMP MIB January 26, 2001 unnumbered(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "The remote link bundle identifier type (numbered or unnumbered)." ::= { lmpLinkBundleEntry 4 } lmpControlChannelIfPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-write STATUS current DESCRIPTION "This variable represents a pointer to the control channel interface that is associated with the link bundle. This association may be established during the link verification procedure. If the link verification procedure is not used, this association must be done by configuration." ::= { lmpLinkBundleEntry 5 } lmpLinkBundleProtectionType OBJECT-TYPE SYNTAX INTEGER { unprotected(0), shared(1), dedicated1For1(2), dedicated1Plus1(3), enhanced(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "The link bundle protection type." ::= { lmpLinkBundleEntry 6 } lmpLinkBundleEncodingType OBJECT-TYPE SYNTAX INTEGER { packet(1), ethernet(2), ansiPdh(3), etsiPdh(4), sdh(5), sonet(6), digitalWrapper(7), lambda(8), fiber(9) } MAX-ACCESS read-write Dubuc Expires July 2001 [Page 22] Internet Draft MPLS LMP MIB January 26, 2001 STATUS current DESCRIPTION "The encoding type of the data-bearing links contained in the link bundle." REFERENCE "draft-ietf-mpls-generalized-signaling-00.txt - Generalized MPLS Signaling Functional Description, P. Ashwood-Smith, A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, V. Sharma, G. Swallow, Z. Tang, October 2000." ::= { lmpLinkBundleEntry 7 } lmpLinkBundleBitRate OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "This is the bit rate at which the Test messages will be transmitted and is expressed in bytes per second." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpLinkBundleEntry 8 } lmpLinkBundleWavelength OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "This value corresponds to the wavelength at which the Test messages will be transmitted over and is measured in nanometers (nm). If each data-bearing link corresponds to a separate wavelength, than this value should be set to 0." REFERENCE "draft-ietf-mpls-lmp-01.txt - Link Management Protocol (LMP), J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, L. Berger, B. Rajagopalan, D. Basak, H. Sandick, A. Zinin, A. Banerjee, November 2000." ::= { lmpLinkBundleEntry 9 } lmpLinkBundleRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION Dubuc Expires July 2001 [Page 23] Internet Draft MPLS LMP MIB January 26, 2001 "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpLinkBundleEntry 10 } lmpLinkBundleStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object." ::= { lmpLinkBundleEntry 11 } lmpLinkBundleOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this link bundle." ::= { lmpLinkBundleEntry 12 } -- End of lmpLinkBundleTable -- LMP Data Bearing Link Table lmpDataBearingLinkTable OBJECT-TYPE SYNTAX SEQUENCE OF LmpDataBearingLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies the data-bearing links managed by the LMP." ::= { lmpObjects 5 } lmpDataBearingLinkEntry OBJECT-TYPE SYNTAX LmpDataBearingLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table contains information about the data-bearing links." INDEX { lmpLinkBundleId, lmpDataBearingLinkEntityIfId } ::= { lmpDataBearingLinkTable 1 } LmpDataBearingLinkEntry ::= SEQUENCE { lmpDataBearingLinkEntityIfId InterfaceIndexOrZero, lmpDataBearingLinkRemoteEntityIfId InterfaceIndexOrZero, Dubuc Expires July 2001 [Page 24] Internet Draft MPLS LMP MIB January 26, 2001 lmpDataBearingLinkProtectionType INTEGER, lmpDataBearingLinkActivityStatus INTEGER, lmpDataBearingLinkRowStatus RowStatus, lmpDataBearingLinkStorageType StorageType, lmpDataBearingLinkAdminStatus INTEGER, lmpDataBearingLinkOperStatus INTEGER } lmpDataBearingLinkEntityIfId OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This is a unique index for an entry in the lmpDataBearingLinkTable. This value represents the interface index for the data-bearing link. It points to an interface in the ifTable." ::= { lmpDataBearingLinkEntry 1 } lmpDataBearingLinkRemoteEntityIfId OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "Entity interface identifier of the remote end point. This information is either configured manually or is communicated by the remote node during the link verification procedure." ::= { lmpDataBearingLinkEntry 2 } lmpDataBearingLinkProtectionType OBJECT-TYPE SYNTAX INTEGER { primary(1), secondary(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute specifies whether this data-bearing link is a primary or secondary entity." ::= { lmpDataBearingLinkEntry 3 } lmpDataBearingLinkActivityStatus OBJECT-TYPE SYNTAX INTEGER { active(1), standby(2) } MAX-ACCESS read-only STATUS current Dubuc Expires July 2001 [Page 25] Internet Draft MPLS LMP MIB January 26, 2001 DESCRIPTION "This attribute specifies whether this data-bearing link is currently active or in standby mode." ::= { lmpDataBearingLinkEntry 4 } lmpDataBearingLinkRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { lmpDataBearingLinkEntry 7 } lmpDataBearingLinkStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object." ::= { lmpDataBearingLinkEntry 8 } lmpDataBearingLinkAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The desired operational status of this data-bearing link." ::= { lmpDataBearingLinkEntry 9 } lmpDataBearingLinkOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), testing(3), degraded(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The actual operational status of this data-bearing link. A data-bearing link is in the degraded state if the control channel and associated backup control channel(s) are down but the data-bearing link is still operational." ::= { lmpDataBearingLinkEntry 10 } -- End of lmpDataBearingLinkTable -- Notification Configuration lmpLinkPropertyMismatchTrapEnable OBJECT-TYPE Dubuc Expires July 2001 [Page 26] Internet Draft MPLS LMP MIB January 26, 2001 SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpLinkBundlePropertyMismatch and lmpDataBearingLinkPropertyMismatch traps, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 6 } lmpControlChannelTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpControlChannelSwitchover trap, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 7 } lmpControlChannelInterfaceTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpControlChannelInterfaceNoStandby trap, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 8 } lmpDataBearingLinkTrapEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of lmpDataBearingLinkDegraded trap, otherwise these traps are not emitted." DEFVAL { false } ::= { lmpObjects 9 } -- Link Property Mismatch Traps lmpLinkBundlePropertyMismatch NOTIFICATION-TYPE OBJECTS { lmpLinkBundleId, Dubuc Expires July 2001 [Page 27] Internet Draft MPLS LMP MIB January 26, 2001 lmpRemoteLinkBundleId, lmpRemoteLinkBundleId } STATUS current DESCRIPTION "This notification is generated when a link bundle property mismatch is detected on the node. The first remote link bundle id is the remote link bundle id configured on the node. The second remote link bundle id is the remote link bundle id received in the LinkSummary message." ::= { lmpNotifyPrefix 1 } lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE OBJECTS { lmpLinkBundleId, lmpDataBearingLinkEntityIfId, lmpDataBearingLinkRemoteEntityIfId, lmpDataBearingLinkRemoteEntityIfId } STATUS current DESCRIPTION "This notification is generated when a data-bearing link property mismatch is detected on the node. The first remote entity interface id is the remote entity interface id configured on the node. The second remote entify interface id is the remote entity interface id received in the LinkSummary message." ::= { lmpNotifyPrefix 2 } -- Control Channel Trap lmpControlChannelSwitchover NOTIFICATION-TYPE OBJECTS { lmpInterfaceId, lmpControlChannelIndex } STATUS current DESCRIPTION "This notification is generated when the active control channel changes. lmpControlChannelIndex refers to the control channel that has become the new active control channel." ::= { lmpNotifyPrefix 3 } -- Control Channel Interface Trap lmpControlChannelInterfaceNoStandby NOTIFICATION-TYPE OBJECTS { lmpInterfaceId } STATUS current DESCRIPTION "This notification is generated when there are no more operational control channel on standby. If the current active control channel fails, then the control channel interface will transition into the down state." ::= { lmpNotifyPrefix 4 } Dubuc Expires July 2001 [Page 28] Internet Draft MPLS LMP MIB January 26, 2001 -- Data-bearing Link Trap lmpDataBearingLinkDegraded NOTIFICATION-TYPE OBJECTS { lmpLinkBundleId, lmpDataBearingLinkEntityIfId } STATUS current DESCRIPTION "This notification is generated when a lmpDataBearingLinkOperStatus object managed by one of the configured control channel entry enters the degraded state." ::= { lmpNotifyPrefix 5 } -- End of notifications -- Module compliance lmpGroups OBJECT IDENTIFIER ::= { lmpConformance 1 } lmpCompliances OBJECT IDENTIFIER ::= { lmpConformance 2 } lmpModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support the MPLS LMP MIB." MODULE -- this module -- The mandatory groups have to be implemented -- by all LMP-enabled devices. However, they may all be supported -- as read-only objects in the case where manual -- configuration is unsupported. MANDATORY-GROUPS { lmpInterfaceGroup, lmpLinkPropertyCorrelationGroup, lmpControlChannelGroup, lmpLinkBundleGroup, lmpDataBearingLinkGroup } -- lmpInterfaceTable OBJECT lmpInterfaceConfigRetransmitInterval DESCRIPTION "Write access is not required." OBJECT lmpInterfaceHelloInterval Dubuc Expires July 2001 [Page 29] Internet Draft MPLS LMP MIB January 26, 2001 DESCRIPTION "Write access is not required." OBJECT lmpInterfaceHelloDeadInterval DESCRIPTION "Write access is not required." OBJECT lmpInterfaceLinkSumRetransmitInterval DESCRIPTION "Write access is not required." OBJECT lmpInterfaceStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." OBJECT lmpInterfaceRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." -- lmpLinkVerificationTable OBJECT lmpVerifyInterval DESCRIPTION "Write access is not required." OBJECT lmpVerifyDeadInterval DESCRIPTION "Write access is not required." OBJECT lmpVerifyAllLinks MIN-ACCESS read-only DESCRIPTION "Write access is not required." -- lmpControlChannelTable OBJECT lmpControlChannelStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." Dubuc Expires July 2001 [Page 30] Internet Draft MPLS LMP MIB January 26, 2001 OBJECT lmpControlChannelRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpControlChannelOperStatus SYNTAX INTEGER { up(1), down(2) } MIN-ACCESS read-only DESCRIPTION "A value of switchingOver(3), takingOver(4) and goingDown(5) need not be supported." -- lmpLinkBundleTable OBJECT lmpLinkBundleIdType MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpRemoteLinkBundleId MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpRemoteLinkBundleIdType MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpControlChannelIfPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpLinkBundleProtectionType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpLinkBundleEncodingType MIN-ACCESS read-only Dubuc Expires July 2001 [Page 31] Internet Draft MPLS LMP MIB January 26, 2001 DESCRIPTION "Write access is not required." OBJECT lmpLinkBundleBitRate MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpLinkBundleWavelength MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpLinkBundleRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." OBJECT lmpLinkBundleStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." -- lmpDataBearingLinkTable OBJECT lmpDataBearingLinkRemoteEntityIfId MIN-ACCESS read-only DESCRIPTION "Write access is not required if the link verification procedure is enabled." OBJECT lmpDataBearingLinkProtectionType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT lmpDataBearingLinkRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported." Dubuc Expires July 2001 [Page 32] Internet Draft MPLS LMP MIB January 26, 2001 OBJECT lmpDataBearingLinkStorageType SYNTAX INTEGER { other(1) } MIN-ACCESS read-only DESCRIPTION "Only other(1) needs to be supported." OBJECT lmpDataBearingLinkOperStatus SYNTAX INTEGER { up(1), down(2), degraded(4) } MIN-ACCESS read-only DESCRIPTION "A value of testing(3) need not be supported." ::= { lmpCompliances 1 } -- Units of conformance lmpInterfaceGroup OBJECT-GROUP OBJECTS { lmpInterfaceCapabilities, lmpInterfaceActiveControlChannelPtr, lmpInterfaceConfigRetransmitInterval, lmpInterfaceHelloInterval, lmpInterfaceHelloDeadInterval, lmpInterfaceLinkSumRetransmitInterval, lmpInterfaceRowStatus, lmpInterfaceStorageType, lmpInterfaceAdminStatus, lmpInterfaceOperStatus, lmpControlChannelInterfaceTrapEnable } STATUS current DESCRIPTION "Collection of objects needed for LMP interface configuration." ::= { lmpGroups 1 } lmpLinkPropertyCorrelationGroup OBJECT-GROUP OBJECTS { lmpLinkPropertyMismatchTrapEnable } STATUS current DESCRIPTION "Collection of objects needed to implement the link property correlation procedure." ::= { lmpGroups 2 } lmpLinkVerificationGroup OBJECT-GROUP OBJECTS { lmpVerifyInterval, lmpVerifyDeadInterval, lmpVerifyTransportMechanism, Dubuc Expires July 2001 [Page 33] Internet Draft MPLS LMP MIB January 26, 2001 lmpVerifyAllLinks } STATUS current DESCRIPTION "Collection of objects needed to implement the link verification procedure." ::= { lmpGroups 3 } lmpControlChannelGroup OBJECT-GROUP OBJECTS { lmpControlChannelRowStatus, lmpControlChannelStorageType, lmpControlChannelOperStatus, lmpControlChannelTrapEnable } STATUS current DESCRIPTION "Collection of objects needed for configuration of the control channels associated with a control channel interface." ::= { lmpGroups 4 } lmpLinkBundleGroup OBJECT-GROUP OBJECTS { lmpLinkBundleIdType, lmpRemoteLinkBundleId, lmpRemoteLinkBundleIdType, lmpControlChannelIfPtr, lmpLinkBundleProtectionType, lmpLinkBundleEncodingType, lmpLinkBundleBitRate, lmpLinkBundleWavelength, lmpLinkBundleRowStatus, lmpLinkBundleStorageType, lmpLinkBundleOperStatus } STATUS current DESCRIPTION "Collection of objects needed for link bundle configuration." ::= { lmpGroups 5 } lmpDataBearingLinkGroup OBJECT-GROUP OBJECTS { lmpDataBearingLinkRemoteEntityIfId, lmpDataBearingLinkProtectionType, lmpDataBearingLinkActivityStatus, lmpDataBearingLinkRowStatus, lmpDataBearingLinkStorageType, lmpDataBearingLinkAdminStatus, Dubuc Expires July 2001 [Page 34] Internet Draft MPLS LMP MIB January 26, 2001 lmpDataBearingLinkOperStatus, lmpDataBearingLinkTrapEnable } STATUS current DESCRIPTION "Collection of objects needed for data-bearing link configuration." ::= { lmpGroups 6 } lmpNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { lmpLinkBundlePropertyMismatch, lmpDataBearingLinkPropertyMismatch, lmpControlChannelSwitchover, lmpControlChannelInterfaceNoStandby, lmpDataBearingLinkDegraded } STATUS current DESCRIPTION "Set of notifications implemented in this module. None is mandatory." ::= { lmpGroups 7 } -- End of LMP-MIB END 12. Security Considerations It is clear that this MIB is potentially useful for monitoring of LMP enabled devices. This MIB can also be used for configuration of cer- tain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. At this writing, no security holes have been identified beyond those that SNMP Security [SNMPArch] is itself intended to address. These relate to primarily controlled access to sensitive information and the ability to configure a device - or which might result from opera- tor error, which is beyond the scope of any security architecture. There are a number of management objects defined in this MIB which have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environ- ment without proper protection can have a negative effect on network operations. The use of SNMP Version 3 is recommended over prior ver- sions, for configuration control, as its security model is improved. SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if Dubuc Expires July 2001 [Page 35] Internet Draft MPLS LMP MIB January 26, 2001 the network itself is secure (for example by using IPSec [IPSEC]), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model [SNMPv3USM] and the View-based Access Control [SNMPv3VACM] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB is properly configured to give access to the objects only to those principals (users) that have leg- itimate rights to indeed GET or SET (change/create/delete) them. There are a number of managed objects in this MIB that may contain information that may be sensitive from a business perspective, in that they represent a customer's interface to the G-MPLS network. Allowing uncontrolled access to these objects could result in mali- cious and unwanted disruptions of network traffic or incorrect confi- gurations for these customers. There are no objects that are particu- larly sensitive in their own right, such as passwords or monetary amounts. 13. Acknowledgments The general structure of this draft, including sections on applica- bility of Interface Group and relationship with ifTable, has been modeled around draft-ietf-mpls-lsr-mib-06.txt. The author wishes to thank Dmitry Ryumkin. 14. References [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., Rekhter, Y., Berger, L., Rajagopalan, B., Basak, D., Sandick, H., Zinin, A., and Banarjee, A., "Link Management Protocol", Internet Draft , November 2000. [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., Bernstein, G., Drake, J., Fan, Y., Kompella, K., Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., Saha, D., Sharma, V., Swallow, G., and Tang, Z., "Generalized MPLS Signaling Function Description", Internet Draft , Dubuc Expires July 2001 [Page 36] Internet Draft MPLS LMP MIB January 26, 2001 October 2000. [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., "Link Bundling in MPLS Traffic Engineering", Internet Draft , November 2000. [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1700, October 1994. See also: http://www.isi.edu/in-notes/iana/assignments/smi- numbers [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS,(http://www.isi.edu/in- notes/iana/assignements/address-family-numbers), for MIB see: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, January 1998. [SMIv1] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP- based Internets", RFC 1155, May 1990. [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, March 1991. [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Dubuc Expires July 2001 [Page 37] Internet Draft MPLS LMP MIB January 26, 2001 Applications", RFC 2573, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., January 1996. [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996. [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, May 1990. [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998. [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Dubuc Expires July 2001 [Page 38] Internet Draft MPLS LMP MIB January 26, 2001 Management Protocol (SNMPv3)", RFC 2574, April 1999. [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2273, January 1998. [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [IPSEC] Kent, S., and Atkinson, R., "Security Architecture for the Internet Protocol", RFC 2401, November 1998. [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces Group MIB using SMIv2", RFC 2233, Nov. 1997 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 15. Authors' Addresses Martin Dubuc edgeflow, Inc. 329 March Rd. Kanata, ON, CANADA K2K 2E1 Phone: +1-613-270-9279 x253 Email: martin.dubuc@edgeflow.com 16. Full Copyright Statement Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any Dubuc Expires July 2001 [Page 39] Internet Draft MPLS LMP MIB January 26, 2001 kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this docu- ment itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of develop- ing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF Dubuc Expires July 2001 [Page 40]