RFC 2127 (rfc2127) - Page 2 of 49

ISDN Management Information Base using SMIv2

RFC 2127                        ISDN MIB                      March 1997


   3.2.4.1 ifEntry for a Basic Rate hardware interface ............    8
   3.2.4.2 ifEntry for a B channel ................................    9
   3.2.4.3 ifEntry for LAPD (D channel Data Link Layer) ...........   10
   3.2.4.4 ifEntry for a signaling channel ........................   12
   3.3 Relationship to other MIBs .................................   14
   3.3.1 Relationship to the DS1/E1 MIB ...........................   14
   3.3.2 Relationship to the DS0 and DS0Bundle MIBs ...............   14
   3.3.3 Relationship to the Dial Control MIB .....................   14
   3.4 ISDN interface specific information and implementation hints
        ...........................................................   14
   3.4.1 ISDN leased lines ........................................   14
   3.4.2 Hyperchannels ............................................   15
   3.4.3 D channel backup and NFAS trunks .........................   16
   3.4.4 X.25 based packet-mode service in B and D channels .......   16
   3.4.5 SPID handling ............................................   17
   3.4.6 Closed User Groups .......................................   17
   3.4.7 Provision of point-to-point line topology ................   18
   3.4.8 Speech and audio bearer capability information elements ..   18
   3.4.9 Attaching incoming calls to router ports .................   19
   3.4.10 Usage of isdnMibDirectoryGroup and isdnDirectoryTable ...   20
   4 Definitions ..................................................   21
   5 Acknowledgments ..............................................   47
   6 References ...................................................   47
   7 Security Considerations ......................................   49
   8 Author's Address .............................................   49

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.

2.  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)



Roeck                      Standards Track