Definitions of Managed Objects for Scheduling Management Operations
RFC 2591
Document | Type |
RFC - Proposed Standard
(May 1999; No errata)
Obsoleted by RFC 3231
|
|
---|---|---|---|
Authors | David Levi , Jürgen Schönwälder | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 2591 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group D. Levi Request for Comments: 2591 Nortel Networks Category: Standards Track J. Schoenwaelder TU Braunschweig May 1999 Definitions of Managed Objects for Scheduling Management Operations 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 (1999). All Rights Reserved. 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 a set of managed objects that are used to schedule management operations periodically or at specified dates and times. Table of Contents 1. Introduction ....................................................2 2. The SNMP Management Framework....................................2 3. Overview ........................................................3 3.1 Periodic Schedules .............................................3 3.2 Calendar Schedules .............................................4 3.3 One-shot Schedules .............................................4 3.4 Time Transitions ...............................................4 3.5 Actions ........................................................5 4. Definitions .....................................................5 5. Usage Examples .................................................18 5.1 Starting a script to ping devices every 20 minutes ............18 5.2 Starting a script at the next Friday the 13th .................18 5.3 Turning an interface off during weekends ......................19 6. Security Considerations ........................................21 7. Intellectual Property ..........................................22 8. Acknowledgments ................................................22 Levi & Schoenwaelder Standards Track [Page 1] RFC 2591 Scheduling MIB May 1999 9. References .....................................................22 10. Editors' Addresses ............................................24 11. Full Copyright Statement ......................................25 1. Introduction 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 a set of managed objects that are used to schedule management operations periodically or at specified dates and times. 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 [19]. 2. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2271 [1]. 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 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13]. o A set of fundamental applications described in RFC 2273 [14] and the view-based access control mechanism described in RFC 2275 [15]. Levi & Schoenwaelder Standards Track [Page 2] RFC 2591 Scheduling MIB May 1999Show full document text