Definitions of Managed Objects for Service Level Agreements Performance Monitoring
RFC 2758
Document | Type |
RFC - Experimental
(February 2000; No errata)
Was draft-white-slapm-mib (individual)
|
|
---|---|---|---|
Author | Kenneth White | ||
Last updated | 2013-03-02 | ||
Stream | Legacy | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | Legacy state | (None) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | RFC 2758 (Experimental) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group K. White Request for Comments: 2758 IBM Corp. Category: Experimental February 2000 Definitions of Managed Objects for Service Level Agreements Performance Monitoring Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract This memo defines a Management Information Base (MIB) for performance monitoring of Service Level Agreements (SLAs) defined via policy definitions. The MIB defined herein focuses on defining a set of objects for monitoring SLAs and not on replication of the content of the policy definitions being monitored. The goal of the MIB defined within this document is to defined statistics related to a policy rule definition for reporting on the effect that a policy rule has on a system and to defined a method of monitoring this data. Table of Contents 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 The SNMP Network Management Framework . . . . . . . . . . 2 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . 3 3.1 Scalar objects . . . . . . . . . . . . . . . . . . . . . . 4 3.2 slapmPolicyNameTable . . . . . . . . . . . . . . . . . . . 5 3.3 slapmPolicyRuleStatsTable . . . . . . . . . . . . . . . . 6 3.4 slapmPRMonTable . . . . . . . . . . . . . . . . . . . . . 6 3.5 slapmSubcomponentTable . . . . . . . . . . . . . . . . . . 8 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 8 5.0 Security Considerations . . . . . . . . . . . . . . . . . 67 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . 67 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 68 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . 68 9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . 70 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . 71 White Experimental [Page 1] RFC 2758 SLAPM-MIB February 2000 1.0 Introduction 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 [13]. This document's purpose is to define a MIB module for performance management of Service Level Agreements (SLAs). It is assumed that an SLA is defined via policy schema definitions. The policy definitions being modeled with respect to performance management is primarily related to network Quality of Service (QOS). There are a number of methods that exist for defining and administering policy. Definition of these methods is considered out side of the scope of this document. The MIB module defined within this memo has been modeled using the various versions of the schema definitions being developed within the Policy Framework Working Group in the IETF. The content of the MIB defined within this memo has evolved along with the Policy Framework Working Group schema definitions. 2.0 The SNMP Network Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [7]. o 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 STD 16, RFC 1155 [14], STD 16, RFC 1212 [15] and RFC 1215 [16]. The second version, called SMIv2, is described in STD 58, RFC 2578 [3], STD 58, RFC 2579 [4] and STD 58, RFC 2580 [5]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [1]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [17] and RFC 1906 [18]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [18], RFC 2572 [8] and RFC 2574 [10]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [1]. A second set of protocol White Experimental [Page 2] RFC 2758 SLAPM-MIB February 2000Show full document text