Browse Prior Art Database

Network Services Monitoring MIB (RFC2248)

IP.com Disclosure Number: IPCOM000002807D
Original Publication Date: 1998-Jan-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 19 page(s) / 22K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Freed: AUTHOR [+1]

Related Documents

10.17487/RFC2248: DOI

Abstract

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. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group N. Freed Request for Comments: 2248 Innosoft Obsoletes: 1565 S. Kille Category: Standards Track ISODE Consortium January 1998

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 (1998). All Rights Reserved.

1. 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 2248 Network Services MIB January 1998

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 the Host Resources MIB at present; development of an additional application MIB is currently underway in the IETF.

2. Table of Contents

1 Introduction ............................................... 1 2 Table of Contents .......................................... 2 3 The SNMPv2 Network Management Framework .................... 2 3.1 Object Definitions ....................................... 3 4 Rationale for having a Network Services Monitoring MIB ..... 3 4.1 General Relationship to Other MIBs ....................... 4 4.2 Restriction of Scope ..................................... 4 4.3 Configuration Information ................................ 4 5 Application Objects ........................................ 5 6 Definitions ..................................

Processing...
Loading...