Browse Prior Art Database

Definitions of Managed Objects for Scheduling Management Operations (RFC3231)

IP.com Disclosure Number: IPCOM000006540D
Original Publication Date: 2002-Jan-01
Included in the Prior Art Database: 2002-Jan-14
Document File: 30 page(s) / 61K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Levi: AUTHOR [+2]

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

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 Manag...