draft-ietf-isdnmib-snmp-isdn-mib-03.txt   draft-ietf-isdnmib-snmp-isdn-mib-04.txt 
ISDN Management Information Base ISDN Management Information Base
draft-ietf-isdnmib-snmp-isdn-mib-03.txt draft-ietf-isdnmib-snmp-isdn-mib-04.txt
Mon Feb 5 22:36:47 MET 1996 Mon Feb 12 20:12:40 MET 1996
Guenter Roeck (editor) Guenter Roeck (editor)
Conware GmbH Conware GmbH
roeck@conware.de roeck@conware.de
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
skipping to change at page 2, line 5 skipping to change at page 1, line 29
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as a "work in progress". or to cite them other than as a "work in progress".
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
1. Introduction Abstract
This draft defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it defines a minimal set of managed objects community. In particular, it defines a minimal set of managed objects
for SNMP-based management of ISDN terminal interfaces. ISDN interfaces for SNMP-based management of ISDN terminal interfaces. ISDN interfaces
are supported on a variety of equipment (for data and voice) including are supported on a variety of equipment (for data and voice) including
terminal adapters, bridges, hosts, and routers. terminal adapters, bridges, hosts, and routers.
This document specifies a MIB module in a manner that is both compliant This document specifies a MIB module in a manner that is both compliant
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
definitions. definitions.
This document is a product of the ISDN MIB working group within the This document is a product of the ISDN MIB working group within the
Internet Engineering Task Force. Comments are solicited and should be Internet Engineering Task Force. Comments are solicited and should be
addressed to the working group's mailing list at isdn-mib@cisco.com addressed to the working group's mailing list at isdn-mib@cisco.com
and/or the author. and/or the author.
2. The Community-based SNMPv2 Network Management Framework 1. The SNMPv2 Network Management Framework
The Community-based SNMPv2 Network Management Framework consists of four The SNMPv2 Network Management Framework presently consists of three
major components. They are: major components. They are:
o RFC 1902 [1] which defines the SMI, the mechanisms used for o the SMI, described in RFC 1902 [1] - the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects
objects for the Internet suite of protocols. for the Internet suite of protocols.
o RFC 1901 [3] which defines the administrative and other
architectural aspects of the framework.
o RFC 1905 [4] which defines the protocol used for network access to o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for
managed objects. accessing managed objects.
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
2.1. Object Definitions 2. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the 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, SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
an administratively assigned name. The object type together with an an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string, the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type. termed the descriptor, to refer to the object type.
3. Overview 3. Overview
3.1. Structure of MIB 3.1. Structure of MIB
For managing ISDN interfaces, the following information is necessary: For managing ISDN interfaces, the following information is necessary:
o Information for managing physical interfaces. In case of ISDN o Information for managing physical interfaces. In case of ISDN
primary rate, this will usually be T1 or E1 lines, being managed in primary rate, this will usually be T1 or E1 lines, being managed in
the DS1/E1 MIB. For Basic Rate lines, physical interfaces will be the DS1/E1 MIB [12]. For Basic Rate lines, physical interfaces
managed by this MIB. will be managed by this MIB.
o Information for managing bearer channels, usually referred to as B o Information for managing bearer channels, usually referred to as B
channels. channels.
o Information for managing signaling channels. o Information for managing signaling channels.
o Optionally, information for managing Terminal Endpoints (TE). A o Optionally, information for managing Terminal Endpoints (TE). A
Terminal Endpoint is a link layer connection to a switch. Terminal Endpoint is a link layer connection to a switch.
o Optionally, information for managing a list of directory numbers. o Optionally, information for managing a list of directory numbers.
skipping to change at page 7, line 28 skipping to change at page 6, line 28
+-----------------------------------------------------+ +-----------------------------------------------------+
Mapping of Terminal Endpoints (D channel Layer 3) to Layer 2 interfaces Mapping of Terminal Endpoints (D channel Layer 3) to Layer 2 interfaces
IfEntries are maintained for each D channel Network Layer entity IfEntries are maintained for each D channel Network Layer entity
(Terminal Endpoint), for LAPD and for each B channel. (Terminal Endpoint), for LAPD and for each B channel.
The ifType for a Terminal Endpoint can be isdn(63) for ISDN signaling The ifType for a Terminal Endpoint can be isdn(63) for ISDN signaling
channels or x25ple(40) for X.25 based packet mode services. The ifType channels or x25ple(40) for X.25 based packet mode services. The ifType
for D channel Data Link Layer (LAPD) interfaces is lapd(77). The ifType for D channel Data Link Layer (LAPD) interfaces is lapd(77). The ifType
for B channels is ds0(). The ifType for physical interfaces is the for B channels is ds0(81). The ifType for physical interfaces is the
matching IANA ifType, usually ds1(18) for Primary Rate interfaces or matching IANA ifType, usually ds1(18) for Primary Rate interfaces or
ISDNs(75)/ISDNu(76) for Basic Rate interfaces. ISDNs(75)/ISDNu(76) for Basic Rate interfaces.
The ifStackTable is used to map B channels and LAPD interfaces to The ifStackTable is used to map B channels and LAPD interfaces to
physical interfaces and to map D channel Network Layer interfaces physical interfaces and to map D channel Network Layer interfaces
(Terminal Endpoints) to LAPD. (Terminal Endpoints) to LAPD.
Mapping of B channels to upper interface layers will usually be done Mapping of B channels to upper interface layers will usually be done
using the Dial Control MIB. For example, mapping on top of B channels using the Dial Control MIB. For example, mapping on top of B channels
might look as follows: might look as follows:
skipping to change at page 9, line 19 skipping to change at page 8, line 19
The ifGeneralGroup of RFC 1573 is supported for Basic Rate hardware The ifGeneralGroup of RFC 1573 is supported for Basic Rate hardware
interfaces. interfaces.
ifTable Comments ifTable Comments
============== =========================================== ============== ===========================================
ifIndex Each ISDN Basic Rate hardware interface is ifIndex Each ISDN Basic Rate hardware interface is
represented by an ifEntry. represented by an ifEntry.
ifDescr Textual port description. ifDescr Textual port description.
ifType An IANA value to be assigned. ifType The IANA value of ISDNs (75) or ISDNu(76),
whichever is appropriate.
ifSpeed The overall bandwidth of this interface. ifSpeed The overall bandwidth of this interface.
ifPhysAddress Return zero. ifPhysAddress Return zero.
ifAdminStatus The desired administrative status of the ifAdminStatus The desired administrative status of the
ISDN interface. ISDN interface.
ifOperStatus The current operational status of this ifOperStatus The current operational status of this
interface. If the operational status is dormant(5), interface. If the operational status is dormant(5),
skipping to change at page 10, line 16 skipping to change at page 9, line 16
The ifEntry for a B channel supports the ifGeneralGroup and the The ifEntry for a B channel supports the ifGeneralGroup and the
ifPacketGroup of RFC 1573. ifPacketGroup of RFC 1573.
ifTable Comments ifTable Comments
============== =========================================== ============== ===========================================
ifIndex Each ISDN B channel is represented by an ifEntry. ifIndex Each ISDN B channel is represented by an ifEntry.
ifDescr Textual port description. ifDescr Textual port description.
ifType The IANA value of ds0(). ifType The IANA value of ds0(81).
ifSpeed The bandwidth of this B channel. ifSpeed The bandwidth of this B channel.
Usually, this will be the value Usually, this will be the value
of 56000 or 64000. of 56000 or 64000.
ifPhysAddress The ISDN address assigned to this port. ifPhysAddress The ISDN address assigned to this port.
This is a copy of isdnBearerCallingAddress. This is a copy of isdnBearerCallingAddress.
ifAdminStatus The desired administrative status of the ifAdminStatus The desired administrative status of the
ISDN port. ISDN port.
skipping to change at page 12, line 38 skipping to change at page 11, line 38
Refer to RFC 1573. Refer to RFC 1573.
ifHighSpeed Return zero. ifHighSpeed Return zero.
ifName Refer to RFC 1573. ifName Refer to RFC 1573.
ifMtu The size of the largest frame which can be ifMtu The size of the largest frame which can be
sent/received on this interface, sent/received on this interface,
specified in octets. Usually, this will be the specified in octets. Usually, this will be the
default value of 260 as specified in Q.921 default value of 260 as specified in Q.921
(see [6], chapter 5.9.3). [6], chapter 5.9.3.
ifInOctets The total number of octets received on this ifInOctets The total number of octets received on this
interface. interface.
ifInUcastPkts The number of frames received on this interface ifInUcastPkts The number of frames received on this interface
whose address is not TEI=127. whose address is not TEI=127.
ifInNUcastPkts Deprecated. Return the number of frames ifInNUcastPkts Deprecated. Return the number of frames
received on this interface which is received on this interface which is
targeted TEI=127. targeted TEI=127.
skipping to change at page 14, line 38 skipping to change at page 13, line 38
Refer to RFC 1573. Refer to RFC 1573.
ifHighSpeed Return zero. ifHighSpeed Return zero.
ifName Refer to RFC 1573. ifName Refer to RFC 1573.
ifMtu The size of the largest frame which can be ifMtu The size of the largest frame which can be
sent/received on this signaling channel, sent/received on this signaling channel,
specified in octets. Usually, this will be the specified in octets. Usually, this will be the
default value of 260 as specified in Q.921 default value of 260 as specified in Q.921
(see [6], chapter 5.9.3). [6], chapter 5.9.3.
ifInOctets The total number of octets received on this ifInOctets The total number of octets received on this
signaling channel. signaling channel.
ifInUcastPkts The number of frames received which are targeted ifInUcastPkts The number of frames received which are targeted
to this channel's TEI. to this channel's TEI.
ifInNUcastPkts Deprecated. Return the number of frames ifInNUcastPkts Deprecated. Return the number of frames
received on this signaling channel which are received on this signaling channel which are
targeted TEI=127. targeted TEI=127.
skipping to change at page 15, line 45 skipping to change at page 14, line 45
3.3. ISDN interface specific information 3.3. ISDN interface specific information
3.3.1. ISDN leased lines 3.3.1. ISDN leased lines
ISDN leased lines can be specified on a per-B-channel basis. To do so, ISDN leased lines can be specified on a per-B-channel basis. To do so,
the value of isdnBearerChannelType has to be set to leased(2). There the value of isdnBearerChannelType has to be set to leased(2). There
will be no signaling protocol support for leased line B channels, since will be no signaling protocol support for leased line B channels, since
there is no signaling protocol action for this kind of interfaces. there is no signaling protocol action for this kind of interfaces.
If on a given D channel there is no signaling protocol available, any If there is no signaling support available for an ISDN interface, this
isdnSignalingTable and isdnEndpointTable entries layered on top of LAPD must be specified in the according interface specific table. For Basic
must be removed. Depending on the leased line type and the service Rate interfaces, isdnBasicTblSignalMode of isdnBasicRateTable must be
provider, the D channel can then eventually be used for data transfer. set to inactive(2). For Primary Rate interfaces, dsx1SignalMode of
Only B and D channel interfaces will exist in this case. dsx1ConfigTable in DS1/E1 MIB [12] must be set to none(1). There will
be no isdnLapdTable or isdnSignalingTable entries for such interfaces.
For a Primary Rate interface being set up entirely as a leased line, Depending on the leased line type and the service provider, the D
channel can then eventually be used for data transfer. To support this,
the D channel interface type will be ds0(81) instead of lapd(77) and its
usage will be identical to B channel usage if there is no signaling
channel available.
For a Primary Rate interface which is entirely used as a leased line,
there will be no ISDN specific information available or required. Such there will be no ISDN specific information available or required. Such
leased lines can entirely be handled by the DS1/E1 MIB. leased lines can entirely be handled by the DS1/E1 MIB.
3.3.2. Hyperchannels 3.3.2. Hyperchannels
The switch protocol in use will define if hyperchannels are supported, The switch protocol in use will define if hyperchannels are supported,
and the actual support will be implementation dependent. Hyperchannel and the actual support will be implementation dependent. Hyperchannel
connections itself will be requested by the interface user, e.g. by the connections itself will be requested by the interface user, e.g. by the
neighbor connection handling procedures. neighbor connection handling procedures.
In the ISDN MIB, the isdnBearerStatsMultirate object of In the ISDN MIB, the isdnBearerStatsMultirate object of
isdnBearerStatsTable can be used to check if hyperchannels are being isdnBearerStatsTable can be used to check if hyperchannels are being
used for an active call. used for an active call.
If hyperchannels are being used, there will be another interface layer
required to map multiple B channels to a single hyperchannel. This is
accomplished by the DS0Bundle MIB [13].
3.3.3. D channel backup and NFAS trunks 3.3.3. D channel backup and NFAS trunks
D channel backup is defined in Q.931 [8], Annex F. It describes Non- D channel backup is defined in Q.931 [8], Annex F. It describes Non-
Associated signaling and its use and functionality is basically Associated signaling and its use and functionality is basically
identical to NFAS trunks. identical to NFAS trunks.
Non Facility Accociated Signaling (NFAS) basically means that a D Non Facility Accociated Signaling (NFAS) basically means that a D
channel on a PRI interface is used to manage calls on other PRI trunks. channel on a PRI interface is used to manage calls on other PRI trunks.
This is required in North America for H11 channels, since all 24 time This is required in North America for H11 channels, since all 24 time
slots are being used for bearer channels. slots are being used for bearer channels.
skipping to change at page 18, line 4 skipping to change at page 17, line 17
The EID has two bytes: USID (User Service IDentifier) and TID (Terminal The EID has two bytes: USID (User Service IDentifier) and TID (Terminal
IDentifier). These are later used by some of the software versions IDentifier). These are later used by some of the software versions
running on the switch side (e.g. compliant with NI-1, 5ESS custom) to running on the switch side (e.g. compliant with NI-1, 5ESS custom) to
broadcast SETUP messages with these included, so the correct endpoint broadcast SETUP messages with these included, so the correct endpoint
would accept the call. Other switch software versions identify the would accept the call. Other switch software versions identify the
endpoint with the Called Party Number. endpoint with the Called Party Number.
In the ISDN MIB, the SPID can be entered using the isdnEndpointSpid In the ISDN MIB, the SPID can be entered using the isdnEndpointSpid
object of isdnEndpointTable. The isdnSigTblCallingAddress, already object of isdnEndpointTable. The isdnSigTblCallingAddress, already
being used to specify the calling number, cannot be used for this being used to specify the calling number, cannot be used for this
purpose, since both may differ and be required in parallel. purpose, since both may differ and be required in parallel.
3.3.6. Closed User Groups 3.3.6. Closed User Groups
Closed User Groups (CUG), as defined in Q.931 [8], chapter 4.6.1, are Closed User Groups (CUG), as defined in I.255.1 [14], are supported for
supported for circuit mode calls by ETSI and 1TR6. In these networks, circuit mode calls by ETSI (ETS 300 138) and 1TR6. In these networks,
an ISDN address can have one or more Closed User Groups assigned. If an ISDN address can have one or more Closed User Groups assigned. If
there is more than one Closed User Groups assigned to a given address, there is more than one Closed User Group assigned to a given address,
one of those will be the preferred Closed User Group. For such one of those will be the preferred Closed User Group. For such
addresses, only calls from assigned Closed User Groups will be accepted addresses, only calls from assigned Closed User Groups will be accepted
by the network. by the network.
Thus, Closed User Groups are a parameter for neighbor entries and will Thus, Closed User Groups are a parameter for neighbor entries and will
be defined in the Dial Control MIB. A neighbor entry attached to a be defined in the Dial Control MIB. A neighbor entry attached to a
Closed User Group will have to point to an ISDN interface which is Closed User Group will have to point to an ISDN interface which is
attached to the Closed User Group in question. attached to the Closed User Group in question.
3.3.7. Provision of point-to-point line topology 3.3.7. Provision of point-to-point line topology
skipping to change at page 18, line 36 skipping to change at page 18, line 6
"point-to-point". "point-to-point".
In ISDN standards, the term point-to-point will usually be used for data In ISDN standards, the term point-to-point will usually be used for data
link connections, i.e. layer 2 connections, where each layer 2 link connections, i.e. layer 2 connections, where each layer 2
connection from the TE to the network is a single point-to-point connection from the TE to the network is a single point-to-point
connection. Multiple connections of this kind may exist on one physical connection. Multiple connections of this kind may exist on one physical
(layer 1) connection, however, and in case of Basic Rate interfaces (layer 1) connection, however, and in case of Basic Rate interfaces
there may be several TE's connected to one physical line to the network. there may be several TE's connected to one physical line to the network.
The second meaning of "point-to-point" refers to the line topology, i.e. The second meaning of "point-to-point" refers to the line topology, i.e.
to layer 1 connections. For Primary Rate interfaces, the layer 1 to layer 1 connections. For Primary Rate interfaces, the line topology
connection will always be of the point-to-point type. For Basic Rate will always be point-to-point. For Basic Rate interfaces, layer 1
interfaces, layer 1 point-to-point connections do exist in several point-to-point connections do exist in several countries, usually being
countries, usually being used for connecting PBX systems to the network. used for connecting PBX systems to the network.
The second meaning (layer 1 connections) is what will be referred to as The second meaning (layer 1 connections) is what will be referred to as
"point-to-point" connection throughout this document. "point-to-point" connection throughout this document.
The isdnSignalingTable object isdnSigTblLineTopology can be used to For Basic Rate interfaces, the isdnBasicRateTable object
select the line topology. In case of Primary Rate interfaces, this isdnBasicTblLineTopology can be used to select the line topology.
object must always have a value of pointToPoint(1).
3.3.8. Speech and audio bearer capability information elements 3.3.8. Speech and audio bearer capability information elements
The objects speech(2), audio31(6) and audio7(7), as being used in The objects speech(2), audio31(6) and audio7(7), as being used in
isdnBearerStatsInfoType, refer to the Speech, 3.1 kHz Audio and old 7 isdnBearerStatsInfoType, refer to the Speech, 3.1 kHz Audio and old 7
kHz Audio (now Multi-use) bearer capabilities for ISDN, as defined in kHz Audio (now Multi-use) bearer capabilities for ISDN, as defined in
Q.931 [8], chapter 4.5.5, octet 3 of bearer capability information Q.931 [8], chapter 4.5.5, octet 3 of bearer capability information
element. element.
These capabilities are signaling artifices that allow networks to do These capabilities are signaling artifices that allow networks to do
skipping to change at page 20, line 33 skipping to change at page 20, line 33
FROM SNMPv2-CONF FROM SNMPv2-CONF
ifIndex, ifIndex,
InterfaceIndex InterfaceIndex
FROM IF-MIB FROM IF-MIB
IANAifType IANAifType
FROM IANAifType-MIB FROM IANAifType-MIB
transmission transmission
FROM RFC1213-MIB; FROM RFC1213-MIB;
isdnMib MODULE-IDENTITY isdnMib MODULE-IDENTITY
LAST-UPDATED "MIB_DATE" LAST-UPDATED "9602122040Z"
ORGANIZATION "IETF ISDN MIB Working Group" ORGANIZATION "IETF ISDN MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Guenter Roeck " Guenter Roeck
Postal: Conware GmbH Postal: Conware GmbH
Killisfeldstrasse 64 Killisfeldstrasse 64
76227 Karlsruhe 76227 Karlsruhe
Germany Germany
Tel: +49 721 9495 0 Tel: +49 721 9495 0
E-mail: roeck@conware.de" E-mail: roeck@conware.de"
DESCRIPTION DESCRIPTION
skipping to change at page 21, line 15 skipping to change at page 21, line 15
-- by a media specific ifEntry. -- by a media specific ifEntry.
-- --
-- For basic rate lines, the media specifics for the physical interface -- For basic rate lines, the media specifics for the physical interface
-- will be defined in the physical interface group of the ISDN MIB. -- will be defined in the physical interface group of the ISDN MIB.
-- The ifType for physical basic rate interfaces will be ISDNs(75) -- The ifType for physical basic rate interfaces will be ISDNs(75)
-- or ISDNu(76), whichever is appropriate. -- or ISDNu(76), whichever is appropriate.
-- --
-- For primary rate, the media specifics will be defined in the Trunk -- For primary rate, the media specifics will be defined in the Trunk
-- MIB. The ifType will have a value of ds1(18). -- MIB. The ifType will have a value of ds1(18).
-- Each signaling channel will be represented by an entry
-- in the isdnSignalingTable. -- in the isdnSignalingTable.
-- The signaling channel will have an ifType value of isdn(63),
-- refer to RFC 1213.
-- Each B channel will also be represented as an entry -- Each B channel will also be represented as an entry
-- in the ifTable. The B channels will have an ifType value -- in the ifTable. The B channels will have an ifType value
-- of ds0(81).
-- This model will be used while defining objects and tables -- This model will be used while defining objects and tables
-- for management. -- for management.
-- The ISDN MIB will allow sub-layers. For example, the data transfer -- The ISDN MIB will allow sub-layers. For example, the data transfer
-- over a B channel may take place with PPP encapsulation. While the -- over a B channel may take place with PPP encapsulation. While the
-- ISDN MIB will describe the D and B channels, a media specific MIB -- ISDN MIB will describe the D and B channels, a media specific MIB
-- for PPP can be used on a layered basis. This will be as per -- for PPP can be used on a layered basis. This will be as per
-- RFC 1573. -- RFC 1573.
-- Textual conventions -- Textual conventions
skipping to change at page 23, line 28 skipping to change at page 23, line 28
SYNTAX IsdnBasicRateTableEntry SYNTAX IsdnBasicRateTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the ISDN Basic Rate Table." "An entry in the ISDN Basic Rate Table."
INDEX { ifIndex } INDEX { ifIndex }
::= { isdnBasicRateTable 1 } ::= { isdnBasicRateTable 1 }
IsdnBasicRateTableEntry ::= SEQUENCE { IsdnBasicRateTableEntry ::= SEQUENCE {
isdnBasicTblIfType INTEGER, isdnBasicTblIfType INTEGER,
isdnBasicTblIfMode INTEGER isdnBasicTblLineTopology INTEGER,
isdnBasicTblIfMode INTEGER,
isdnBasicTblSignalMode INTEGER
} }
isdnBasicTblIfType OBJECT-TYPE isdnBasicTblIfType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
isdnS(1), isdnS(1),
isdnU(2) isdnU(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The physical interface type. For 'S/T' interfaces, "The physical interface type. For 'S/T' interfaces,
also called 'Four-wire Basic Access Interface', also called 'Four-wire Basic Access Interface',
the value of this object will be isdnS(1). the value of this object will be isdnS(1).
For 'U' interfaces, also called 'Two-wire Basic For 'U' interfaces, also called 'Two-wire Basic
Access Interface', the value of this object will be Access Interface', the value of this object will be
isdnU(2)." isdnU(2)."
::= { isdnBasicRateTableEntry 1 } ::= { isdnBasicRateTableEntry 1 }
isdnBasicTblLineTopology OBJECT-TYPE
SYNTAX INTEGER {
pointToPoint(1),
pointToMultipoint(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The line topology to be used for this interface.
Note that setting isdnBasicTblIfType to isdnS(1)
does not necessarily mean a line topology of
point-to-multipoint."
::= { isdnBasicRateTableEntry 2 }
isdnBasicTblIfMode OBJECT-TYPE isdnBasicTblIfMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
te(1), te(1),
nt(2) nt(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The physical interface mode. For TE mode, the value "The physical interface mode. For TE mode, the value
of this object will be te(1). For NT mode, the value of this object will be te(1). For NT mode, the value
of this object will be nt(2)." of this object will be nt(2)."
::= { isdnBasicRateTableEntry 2 } ::= { isdnBasicRateTableEntry 3 }
isdnBasicTblSignalMode OBJECT-TYPE
SYNTAX INTEGER {
active(1),
inactive(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The signaling channel operational mode for this interface.
If set to active(1), there is a signaling channel on this
interface. If set to inactive(2), a signaling channel is
not available."
::= { isdnBasicRateTableEntry 4 }
-- The B channel (bearer channel) group -- The B channel (bearer channel) group
-- Note that disconnects can explicitely be handled using the -- Note that disconnects can explicitely be handled using the
-- ifStack table. If a connection is to be disconnected, -- ifStack table. If a connection is to be disconnected,
-- the according ifStack entry has to be removed. -- the according ifStack entry has to be removed.
-- More specific, the ifStackTable entry which binds the high-layer -- More specific, the ifStackTable entry which binds the high-layer
-- ifTable entry (and related dialCtlNbrCfgTable entry) to the -- ifTable entry (and related dialCtlNbrCfgTable entry) to the
-- B channel ifTable entry (and related isdnBearerTable entry) -- B channel ifTable entry (and related isdnBearerTable entry)
-- during an active call has to be removed. -- during an active call has to be removed.
isdnBearerGroup OBJECT IDENTIFIER ::= { isdnMibObjects 2 } isdnBearerGroup OBJECT IDENTIFIER ::= { isdnMibObjects 2 }
isdnBearerTable OBJECT-TYPE isdnBearerTable OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnBearerEntry SYNTAX SEQUENCE OF IsdnBearerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 29, line 47 skipping to change at page 30, line 31
SYNTAX IsdnSignalingTableEntry SYNTAX IsdnSignalingTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the ISDN Signaling Table." "An entry in the ISDN Signaling Table."
INDEX { ifIndex } INDEX { ifIndex }
::= { isdnSignalingTable 1 } ::= { isdnSignalingTable 1 }
IsdnSignalingTableEntry ::= SEQUENCE { IsdnSignalingTableEntry ::= SEQUENCE {
isdnSigTblSignalingProtocol IsdnSignalingProtocol, isdnSigTblSignalingProtocol IsdnSignalingProtocol,
isdnSigTblLineTopology INTEGER,
isdnSigTblCallingAddress DisplayString, isdnSigTblCallingAddress DisplayString,
isdnSigTblSubAddress DisplayString, isdnSigTblSubAddress DisplayString,
isdnSigTblBchannelCount Integer32, isdnSigTblBchannelCount Integer32,
isdnSigTblStatus RowStatus isdnSigTblStatus RowStatus
} }
isdnSigTblSignalingProtocol OBJECT-TYPE isdnSigTblSignalingProtocol OBJECT-TYPE
SYNTAX IsdnSignalingProtocol SYNTAX IsdnSignalingProtocol
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The particular protocol type supported by the "The particular protocol type supported by the
switch providing access to the ISDN network switch providing access to the ISDN network
to which this signaling interface is connected." to which this signaling interface is connected."
::= { isdnSignalingTableEntry 1 } ::= { isdnSignalingTableEntry 1 }
isdnSigTblLineTopology OBJECT-TYPE
SYNTAX INTEGER {
pointToPoint(1),
pointToMultipoint(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The line topology to be used for this interface.
On Primary Rate interfaces, this object must have
a value of pointToPoint(1) and should be read-only."
::= { isdnSignalingTableEntry 2 }
isdnSigTblCallingAddress OBJECT-TYPE isdnSigTblCallingAddress OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ISDN Address to be assigned to this signaling "The ISDN Address to be assigned to this signaling
interface. More specific, this is the 'Calling Address interface. More specific, this is the 'Calling Address
information element' as being passed to the switch information element' as being passed to the switch
in outgoing call setup messages. in outgoing call setup messages.
skipping to change at page 31, line 7 skipping to change at page 31, line 22
or any other number necessary to identify a signaling or any other number necessary to identify a signaling
interface. If there is no such number defined or required, interface. If there is no such number defined or required,
this is a zero length string. It is represented in this is a zero length string. It is represented in
DisplayString form. DisplayString form.
Incoming calls can also be identified by this number. Incoming calls can also be identified by this number.
If the Directory Number, i.e. the Called Number in If the Directory Number, i.e. the Called Number in
incoming calls, is different to this number, the incoming calls, is different to this number, the
isdnDirectoryTable has to be used to specify all isdnDirectoryTable has to be used to specify all
possible Directory Numbers." possible Directory Numbers."
::= { isdnSignalingTableEntry 3 } ::= { isdnSignalingTableEntry 2 }
isdnSigTblSubAddress OBJECT-TYPE isdnSigTblSubAddress OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Supplementary information to the ISDN address assigned "Supplementary information to the ISDN address assigned
to this interface. Usually, this will be the subaddress to this interface. Usually, this will be the subaddress
as defined in Q.931. as defined in Q.931.
If there is no such number defined or required, this is If there is no such number defined or required, this is
a zero length string. a zero length string.
The subaddress will be used for incoming calls as well as The subaddress will be used for incoming calls as well as
for outgoing calls. for outgoing calls.
It is represented in DisplayString form." It is represented in DisplayString form."
::= { isdnSignalingTableEntry 4 } ::= { isdnSignalingTableEntry 3 }
isdnSigTblBchannelCount OBJECT-TYPE isdnSigTblBchannelCount OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of B channels (bearer channels) "The total number of B channels (bearer channels)
managed by this signaling interface." managed by this signaling interface."
::= { isdnSignalingTableEntry 5 } ::= { isdnSignalingTableEntry 4 }
isdnSigTblStatus OBJECT-TYPE isdnSigTblStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create and delete rows in the "This object is used to create and delete rows in the
isdnSignalingTable." isdnSignalingTable."
::= { isdnSignalingTableEntry 6 } ::= { isdnSignalingTableEntry 5 }
-- Signaling channel statistics table -- Signaling channel statistics table
-- There is one entry for each signaling connection -- There is one entry for each signaling connection
-- in this table. -- in this table.
-- Note that the ifEntry also has some statistics information. -- Note that the ifEntry also has some statistics information.
isdnSignalingStatsTable OBJECT-TYPE isdnSignalingStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnSignalingStatsEntry SYNTAX SEQUENCE OF IsdnSignalingStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 39, line 46 skipping to change at page 40, line 14
GROUP isdnMibDirectoryGroup GROUP isdnMibDirectoryGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional for all systems "Implementation of this group is optional for all systems
that attach to ISDN interfaces." that attach to ISDN interfaces."
OBJECT isdnBasicTblIfType OBJECT isdnBasicTblIfType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"It is conformant to implement this object as read-only." "It is conformant to implement this object as read-only."
OBJECT isdnSigTblLineTopology OBJECT isdnBasicTblLineTopology
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"It is conformant to implement this object as read-only. "It is conformant to implement this object as read-only."
For Primary Rate ISDN interfaces, this object must be
implemented as read-only and has to return the value of OBJECT isdnBasicTblIfMode
pointToPoint(1)." MIN-ACCESS read-only
DESCRIPTION
"It is conformant to implement this object as read-only."
OBJECT isdnBasicTblSignalMode
MIN-ACCESS read-only
DESCRIPTION
"It is conformant to implement this object as read-only."
::= { isdnMibCompliances 1 } ::= { isdnMibCompliances 1 }
-- units of conformance -- units of conformance
isdnMibBasicRateGroup OBJECT-GROUP isdnMibBasicRateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
isdnBasicTblIfType, isdnBasicTblIfType,
isdnBasicTblIfMode isdnBasicTblLineTopology,
isdnBasicTblIfMode,
isdnBasicTblSignalMode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for ISDN Basic Rate "A collection of objects required for ISDN Basic Rate
physical interface configuration and statistics." physical interface configuration and statistics."
::= { isdnMibGroups 1 } ::= { isdnMibGroups 1 }
isdnMibBearerGroup OBJECT-GROUP isdnMibBearerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
isdnBearerChannelType, isdnBearerChannelType,
skipping to change at page 40, line 47 skipping to change at page 41, line 24
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for ISDN Bearer channel "A collection of objects required for ISDN Bearer channel
control and statistics." control and statistics."
::= { isdnMibGroups 2 } ::= { isdnMibGroups 2 }
isdnMibSignalingGroup OBJECT-GROUP isdnMibSignalingGroup OBJECT-GROUP
OBJECTS { OBJECTS {
isdnSigTblSignalingProtocol, isdnSigTblSignalingProtocol,
isdnSigTblLineTopology,
isdnSigTblCallingAddress, isdnSigTblCallingAddress,
isdnSigTblSubAddress, isdnSigTblSubAddress,
isdnSigTblBchannelCount, isdnSigTblBchannelCount,
isdnSigTblStatus, isdnSigTblStatus,
isdnSigStatsInCalls, isdnSigStatsInCalls,
isdnSigStatsInConnected, isdnSigStatsInConnected,
isdnSigStatsOutCalls, isdnSigStatsOutCalls,
isdnSigStatsOutConnected, isdnSigStatsOutConnected,
isdnSigStatsChargedUnits, isdnSigStatsChargedUnits,
isdnLapdPrimaryChannel, isdnLapdPrimaryChannel,
skipping to change at page 42, line 42 skipping to change at page 43, line 42
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version 2 S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996. January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II", STD 17, for Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, Hughes LAN Systems, Performance Systems International, RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991. March 1991.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple
S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP
January 1996. Research, Performance Systems International, MIT Lab for Computer
Science, May 1990.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and
S. Waldbusser, "Protocol Operations for Version 2 of the Simple S. Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] ITU-T Recommendation "Digital subscriber Signaling System No. 1 [5] ITU-T Recommendation "Digital subscriber Signaling System No. 1
(DSS 1) - ISDN User-Network Interface Data Link Layer - General (DSS 1) - ISDN User-Network Interface Data Link Layer - General
Aspects Rec. Q.920 Aspects Rec. Q.920.
[6] ITU-T Recommendation "Digital subscriber Signaling System No. 1 [6] ITU-T Recommendation "Digital subscriber Signaling System No. 1
(DSS 1) - ISDN User-Network Interface - Data Link Layer (DSS 1) - ISDN User-Network Interface - Data Link Layer
Specification Rec. Q.921 Specification Rec. Q.921.
[7] ITU-T Recommendation "Digital subscriber Signaling System No. 1 [7] ITU-T Recommendation "Digital subscriber Signaling System No. 1
(DSS 1) - ISDN Data Link Layer Specification for Frame Mode Bearer (DSS 1) - ISDN Data Link Layer Specification for Frame Mode Bearer
Services (LAPF) Rec. Q.922 Services (LAPF) Rec. Q.922.
[8] ITU-T Recommendation "Digital subscriber Signaling System No. 1 [8] ITU-T Recommendation "Digital subscriber Signaling System No. 1
(DSS 1) - ISDN user-network interface layer 3 specification for (DSS 1) - ISDN user-network interface layer 3 specification for
basic call control", Rec. Q.931(I.451), March 1993.
[9] ITU-T Recommendation "Generic procedures for the control of ISDN [9] ITU-T Recommendation "Generic procedures for the control of ISDN
supplementary services ISDN user-network interface layer 3 supplementary services ISDN user-network interface layer 3
specification", Rec. Q.932(I.452) specification", Rec. Q.932(I.452).
[10] ITU-T Recommendation "Digital subscriber Signaling System No. 1 [10] ITU-T Recommendation "Digital subscriber Signaling System No. 1
(DSS 1) - Signaling specification for frame-mode basic call (DSS 1) - Signaling specification for frame-mode basic call
control", Rec. Q.933 control", Rec. Q.933.
[11] McCloghrie, K. and F. Kastenholz, "Evolution of the Interfaces [11] McCloghrie, K. and F. Kastenholz, "Evolution of the Interfaces
Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software,
January 1994 January 1994.
[12] D. Fowler, "Definitions of Managed Objects for the DS1/E1/DS2/E2
Interface Types", RFCxxxx, Newbridge Networks, February 1996.
[13] D. Fowler, "Definitions of Managed Objects for the DS0 and
DS0Bundle Interface Types", RFCxxxx, Newbridge Networks, February
1996.
[14] ITU-T Recommendation "Integrated Services Digital Network (ISDN)
General Structure and Service Capabilities - Closed User Group",
Rec. I.255.1.
7. Security Considerations 7. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
8. Author's Address 8. Author's Address
Guenter Roeck Guenter Roeck
Conware GmbH Conware GmbH
Killisfeldstrasse 64 Killisfeldstrasse 64
76137 Karlsruhe, Germany 76137 Karlsruhe, Germany
Phone: +49 721 9495 0 Phone: +49 721 9495 0
Email: roeck@conware.de Email: roeck@conware.de
Table of Contents Table of Contents
1 Introduction .................................................... 2 1 The SNMPv2 Network Management Framework ......................... 2
2 The Community-based SNMPv2 Network Management Framework ......... 3 2 Object Definitions .............................................. 2
2.1 Object Definitions ............................................ 3 3 Overview ........................................................ 3
3 Overview ........................................................ 4 3.1 Structure of MIB .............................................. 3
3.1 Structure of MIB .............................................. 4 3.1.1 General Description ......................................... 3
3.1.1 General Description ......................................... 4 3.2 Relationship to RFC 1573 ...................................... 4
3.2 Relationship to RFC 1573 ...................................... 5 3.2.1 Layering Model .............................................. 4
3.2.1 Layering Model .............................................. 5 3.2.2 ifTestTable ................................................. 7
3.2.2 ifTestTable ................................................. 8 3.2.3 ifRcvAddressTable ........................................... 7
3.2.3 ifRcvAddressTable ........................................... 8 3.2.4 ifEntry ..................................................... 8
3.2.4 ifEntry ..................................................... 9 3.2.4.1 ifEntry for a Basic Rate hardware interface ............... 8
3.2.4.1 ifEntry for a Basic Rate hardware interface ............... 9 3.2.4.2 ifEntry for a B channel (bearer channel) .................. 9
3.2.4.2 ifEntry for a B channel (bearer channel) .................. 10 3.2.4.3 ifEntry for LAPD (D channel Data Link Layer) .............. 10
3.2.4.3 ifEntry for LAPD (D channel Data Link Layer) .............. 11 3.2.4.4 ifEntry for a signaling channel ........................... 12
3.2.4.4 ifEntry for a signaling channel ........................... 13 3.3 ISDN interface specific information ........................... 14
3.3 ISDN interface specific information ........................... 15 3.3.1 ISDN leased lines ........................................... 14
3.3.1 ISDN leased lines ........................................... 15 3.3.2 Hyperchannels ............................................... 15
3.3.2 Hyperchannels ............................................... 16 3.3.3 D channel backup and NFAS trunks ............................ 15
3.3.3 D channel backup and NFAS trunks ............................ 16 3.3.4 X.25 based packet-mode service in D channel ................. 16
3.3.4 X.25 based packet-mode service in D channel ................. 17 3.3.5 SPID handling ............................................... 16
3.3.5 SPID handling ............................................... 17 3.3.6 Closed User Groups .......................................... 17
3.3.6 Closed User Groups .......................................... 18 3.3.7 Provision of point-to-point line topology ................... 17
3.3.7 Provision of point-to-point line topology ................... 18 3.3.8 Speech and audio bearer capability information elements ..... 18
3.3.8 Speech and audio bearer capability information elements ..... 19
4 Definitions ..................................................... 20 4 Definitions ..................................................... 20
5 Acknowledgments ................................................. 42 5 Acknowledgments ................................................. 43
6 References ...................................................... 42 6 References ...................................................... 43
7 Security Considerations ......................................... 43 7 Security Considerations ......................................... 45
8 Author's Address ................................................ 43 8 Author's Address ................................................ 45
 End of changes. 53 change blocks. 
100 lines changed or deleted 148 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/