Link Management Protocol (LMP) Management Information Base (MIB)
RFC 4327
Document | Type |
RFC - Proposed Standard
(January 2006; Errata)
Obsoleted by RFC 4631
|
|
---|---|---|---|
Authors | Thomas Nadeau , Evan McGinnis , Martin Dubuc , Jonathan Lang | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4327 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Bert Wijnen | ||
Send notices to | <m.dubuc@rogers.com>, <kireeti@juniper.net>,<adrian@olddog.co.uk>,<zinin@psg.com> |
Network Working Group M. Dubuc Request for Comments: 4327 T. Nadeau Category: Standards Track Cisco Systems J. Lang Sonos, Inc. E. McGinnis Hammerhead Systems January 2006 Link Management Protocol (LMP) Management Information Base (MIB) Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo defines a portion of the Management Information 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). Table of Contents 1. The Internet-Standard Management Framework ......................2 2. Introduction ....................................................2 3. Terminology .....................................................3 4. Feature Checklist ...............................................3 5. Outline .........................................................4 6. Brief Description of MIB Objects ................................4 6.1. lmpNbrTable ................................................4 6.2. lmpControlChannelTable .....................................4 6.3. lmpControlChannelPerfTable .................................4 6.4. lmpTeLinkTable .............................................5 6.5. lmpLinkVerificationTable ...................................5 6.6. lmpTeLinkPerfTable .........................................5 6.7. lmpDataLinkTable ...........................................5 6.8. lmpDataLinkPerfTable .......................................5 7. Example of LMP Control Channel Setup ............................5 Dubuc, et al. Standards Track [Page 1] RFC 4327 LMP-MIB Module January 2006 8. Application of the Interfaces Group to LMP ......................8 8.1. Support of the LMP Layer by ifTable ........................9 9. LMP MIB Module Definitions .....................................11 10. Security Considerations .......................................77 11. Contributors ..................................................78 12. Acknowledgements ..............................................78 13. IANA Considerations ...........................................78 13.1. IANA Considerations for lmp ifType .......................78 13.2. IANA Considerations for LMP-MIB ..........................78 14. References ....................................................79 14.1. Normative References .....................................79 14.2. Informative References ...................................80 1. 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]. 2. Introduction Current work is under way in the IETF to specify a suite of protocols to be used as a common control plane and a separate common measurement plane. Generalized MPLS (GMPLS) [RFC3471] and the Link Management Protocol [RFC4204] are key components of this standardization activity. The primary purpose of LMP is to manage traffic engineering (TE) links. Primary goals of LMP are the maintenance of the control channel connectivity, correlation of link properties, verification of data-bearing links, and detection and isolation of link faults. We describe in this document a MIB module that can be used to manage LMP implementations. This MIB module covers both configuration and performance monitoring aspects of LMP. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",Show full document text