RFC 2127 (rfc2127) - Page 3 of 49
ISDN Management Information Base using SMIv2
Alternative Format: Original Text Document
RFC 2127 ISDN MIB March 1997
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.
3. Overview
3.1. Structure of the MIB
For managing ISDN interfaces, the following information is necessary:
o Information for managing physical interfaces. In case of ISDN
primary rate, this are usually T1 or E1 lines, being managed in
the DS1/E1 MIB [12]. For Basic Rate lines, physical interfaces
are managed by this MIB.
o Information for managing B channels.
o Information for managing signaling channels.
o Optionally, information for managing Terminal Endpoints (TE).
A Terminal Endpoint is a link layer connection to a switch.
o Optionally, information for managing a list of directory numbers.
In order to manage connections over ISDN lines, the management of
peer information and call history information is required as well.
This information is defined in the Dial Control MIB [15].
The purpose for splitting the required information in two MIBs is to
be able to use parts of this information for non-ISDN interfaces as
well. In particular, the Dial Control MIB might also be used for
other types of interfaces, e.g. modems or X.25 virtual connections.
Within this document, information has been structured into five
groups, which are described in the following chapters.
3.1.1. General Description
This MIB controls all aspects of ISDN interfaces. It consists of
five groups.
o The isdnMibBasicRateGroup is used to provide information
regarding physical Basic Rate interfaces.
o The isdnMibBearerGroup is used to control B (bearer) channels.
Roeck Standards Track