Network Services Monitoring MIB
RFC 2788

 
Document Type RFC - Proposed Standard (March 2000; No errata)
Obsoletes RFC 2248
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 2788 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           N. Freed
Request for Comments: 2788                                      Innosoft
Category: Standards Track                                       S. Kille
Obsoletes: 2248                                     MessagingDirect Ltd.
                                                              March 2000

                    Network Services Monitoring 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 (2000).  All Rights Reserved.

Introduction

   A networked application is a realization of some well-defined service
   on one or more host computers that is accessible via some network,
   uses some network for its internal operations, or both.

   There are a wide range of networked applications for which it is
   appropriate to provide SNMP monitoring of their network usage.  This
   includes applications using both TCP/IP and OSI networking.  This
   document defines a MIB which contains the elements common to the
   monitoring of any network service application.  This information
   includes a table of all monitorable network service applications, a
   count of the associations (connections) to each application, and
   basic information about the parameters and status of each
   application-related association.

   This MIB may be used on its own for any application, and for most
   simple applications this will suffice.  This MIB is also designed to
   serve as a building block which can be used in conjunction with
   application-specific monitoring and management.  Two examples of this
   are MIBs defining additional variables for monitoring a Message
   Transfer Agent (MTA) service or a Directory Service Agent (DSA)
   service. It is expected that further MIBs of this nature will be
   specified.

Freed & Kille               Standards Track                     [Page 1]
RFC 2788            Network Services Monitoring MIB           March 2000

   This MIB does not attempt to provide facilities for management of the
   host or hosts the network service application runs on, nor does it
   provide facilities for monitoring applications that provide something
   other than a network service.  Host resource and general application
   monitoring is handled by either the Host Resources MIB [1] or the
   application MIB [2].

Table of Contents

   1  The SNMP Network Management Framework .......................  2
   2  Rationale for having a Network Services Monitoring MIB ......  3
      1 General Relationship to Other MIBs ........................  4
      2 Restriction of Scope ......................................  4
      3 Configuration Information .................................  5
   3  Application Objects .........................................  5
   4  Definitions .................................................  5
   5  Changes made since RFC 2248 ................................. 18
   6  Acknowledgements ............................................ 18
   7  References .................................................. 19
   8  Security Considerations ..................................... 20
   9  Author and Chair Addresses .................................. 21
   10 Full Copyright Statement .................................... 22

1.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

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

   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 [4], STD 16, RFC 1212 [5] and RFC 1215 [6]. The
       second version, called SMIv2, is described in STD 58, RFC 2578
       [7], STD 58, RFC 2579 [8] and STD 58, RFC 2580 [9].

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

Freed & Kille               Standards Track                     [Page 2]
Show full document text