Definitions of Managed Objects for Scheduling Management Operations
RFC 3231

Document Type RFC - Proposed Standard (January 2002; No errata)
Obsoletes RFC 2591
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3231 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            D. Levi
Request for Comments: 3231                               Nortel Networks
Obsoletes: 2591                                         J. Schoenwaelder
Category: Standards Track                                TU Braunschweig
                                                            January 2002

                   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 (2002).  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.

   This document obsoletes RFC 2591.

Table of Contents

   1 Introduction .................................................    2
   2 The SNMP Management Framework ................................    2
   3 Overview .....................................................    3
   3.1 Periodic Schedules .........................................    4
   3.2 Calendar Schedules .........................................    4
   3.3 One-shot Schedules .........................................    5
   3.4 Time Transitions ...........................................    5
   3.5 Actions ....................................................    5
   4 Definitions ..................................................    6
   5 Usage Examples ...............................................   20
   5.1 Starting a script to ping devices every 20 minutes .........   20
   5.2 Starting a script at the next Friday the 13th ..............   21
   5.3 Turning an interface off during weekends ...................   22

Levi & Schoenwaelder        Standards Track                     [Page 1]
RFC 3231                      Schedule MIB                  January 2002

   6 Security Considerations ......................................   23
   7 Intellectual Property ........................................   25
   8 Changes from RFC 2591 ........................................   25
   9 Acknowledgments ..............................................   26
   10 References ..................................................   26
   11 Editors' Addresses ..........................................   28
   12 Full Copyright Statement ....................................   29

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 [RFC2119].

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [RFC2571].

   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 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
      [RFC1215].  The second version, called SMIv2, is described in STD
      58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
      2580 [RFC2580].

   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 [RFC1157].  A second version of the
      SNMP message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
      and RFC 1906 [RFC1906].  The third version of the message protocol
      is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572
      [RFC2572] and RFC 2574 [RFC2574].

Levi & Schoenwaelder        Standards Track                     [Page 2]
Show full document text