Dial Control Management Information Base using SMIv2
RFC 2128

Document Type RFC - Proposed Standard (March 1997; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2128 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                 G. Roeck, Editor
Request for Comments: 2128                               cisco Systems
Category: Standards Track                                   March 1997

          Dial Control Management Information Base using SMIv2

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.

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 managed objects used for managing demand
   access circuits, including ISDN.

   This document specifies a MIB module in a manner that is compliant to
   the SNMPv2 SMI.  The set of objects is consistent with the SNMP
   framework and existing SNMP standards.

   This document is a product of the ISDN MIB working group within the
   Internet Engineering Task Force.  Comments are solicited and should
   be addressed to the working group's mailing list at isdn-
   mib@cisco.com and/or the author.

Table of Contents

   1 The SNMPv2 Network Management Framework ......................    2
   1.1 Object Definitions .........................................    2
   2 Overview .....................................................    2
   2.1 Structure of MIB ...........................................    2
   2.2 Relationship to the Interfaces MIB .........................    3
   2.2.1 Layering Model and Virtual Circuits ......................    3
   2.2.2 ifTestTable ..............................................    4
   2.2.3 ifRcvAddressTable ........................................    4
   2.2.3.1 ifEntry for a single peer ..............................    5
   2.3 Multilink and backup line support ..........................    5
   2.4 Support for generic peers ..................................    5
   3 Definitions ..................................................    6
   3.1 Dial Control MIB ...........................................    6
   4 Acknowledgments ..............................................   32
   5 References ...................................................   33

Roeck                   Standards Track                         [Page 1]
RFC 2128                    Dial Control MIB                  March 1997

   6 Security Considerations ......................................   33
   7 Author's Address .............................................   34

1.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework presently consists of three
   major components.  They are:

   o    the SMI, described in RFC 1902 [1] - the mechanisms used for
        describing and naming objects for the purpose of management.

   o    the MIB-II, STD 17, RFC 1213 [2] - the core set of managed
        objects for the Internet suite of protocols.

   o    the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [4], -
        the protocol for accessing managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

1.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
   specific instantiation of the object.  For human convenience, we
   often use a textual string, termed the descriptor, to refer to the
   object type.

2.  Overview

2.1.  Structure of MIB

   Managing demand access circuits requires the following groups of
   information:

   o    General configuration information.

   o    Information to describe peer configuration and peer statistics.
        In this respect, peer configuration means information on how to
        connect to peers on outgoing calls, how to identify peers on
        incoming calls, and other call related configuration
        information.

   o    Information to store active call information.

Roeck                   Standards Track                         [Page 2]
RFC 2128                    Dial Control MIB                  March 1997

   o    Information to retain call history.

   The MIB, therefore, is structured into four groups.

   o    The dialCtlConfiguration group is used to specify general
        configuration information.

   o    The dialCtlPeer group is used to describe peer configuration
        and peer statistics.

   o    The callActive group is used to store active call information.
Show full document text