draft-ietf-isdnmib-snmp-isdn-mib-06.txt   draft-ietf-isdnmib-snmp-isdn-mib-07.txt 
ISDN Management Information Base ISDN Management Information Base
draft-ietf-isdnmib-snmp-isdn-mib-06.txt draft-ietf-isdnmib-snmp-isdn-mib-07.txt
Sat Apr 27 10:59:33 MET DST 1996 Fri Aug 23 09:15:06 PDT 1996
Guenter Roeck (editor) Guenter Roeck (editor)
Conware GmbH cisco Systems
roeck@conware.de groeck@cisco.com
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
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Abstract Abstract
This memo 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 compliant to
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 the SNMPv2 SMI. The set of objects is consistent with the SNMP
definitions. framework and existing SNMP standards.
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.
The current version of this document reflects changes made during the
last call period and the IESG review.
Table of Contents
1 The SNMPv2 Network Management Framework ......................... 3
2 Object Definitions .............................................. 3
3 Overview ........................................................ 4
3.1 Structure of the MIB .......................................... 4
3.1.1 General Description ......................................... 4
3.2 Relationship to the Interfaces MIB ............................ 5
3.2.1 Layering Model .............................................. 5
3.2.2 ifTestTable ................................................. 8
3.2.3 ifRcvAddressTable ........................................... 8
3.2.4 ifEntry ..................................................... 8
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 ............................ 15
3.4.4 X.25 based packet-mode service in B and D channels .......... 16
3.4.5 SPID handling ............................................... 16
3.4.6 Closed User Groups .......................................... 17
3.4.7 Provision of point-to-point line topology ................... 17
3.4.8 Speech and audio bearer capability information elements ..... 18
3.4.9 Attaching incoming calls to router ports .................... 18
3.4.10 Usage of isdnMibDirectoryGroup and isdnDirectoryTable ...... 19
4 Definitions ..................................................... 20
5 Acknowledgments ................................................. 44
6 References ...................................................... 44
7 Security Considerations ......................................... 45
8 Author's Address ................................................ 46
1. The SNMPv2 Network Management Framework 1. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework presently consists of three The SNMPv2 Network Management Framework presently consists of three
major components. They are: major components. They are:
o the SMI, described in RFC 1902 [1] - 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 the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects
for the Internet suite of protocols. for the Internet suite of protocols.
skipping to change at page 3, line 12 skipping to change at page 4, line 12
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 the MIB 3.1. Structure of the 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 are usually T1 or E1 lines, being managed in the
the DS1/E1 MIB [12]. For Basic Rate lines, physical interfaces DS1/E1 MIB [12]. For Basic Rate lines, physical interfaces are
will be managed by this MIB. managed by this MIB.
o Information for managing B channels. o Information for managing B 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.
Within this document, this information has been structured into five
groups, which will be described in the following chapters.
In order to manage connections over ISDN lines, the management of In order to manage connections over ISDN lines, the management of
neighbors and call history information is required as well. This neighbors and call history information is required as well. This
information will be defined in the Dial Control MIB. information is defined in the Dial Control MIB [15].
The purpose for splitting the required information in two MIBs is to be 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. 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 In particular, the Dial Control MIB might also be used for other types
of interfaces. 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 3.1.1. General Description
This MIB controls all aspects of ISDN interfaces. It consists of five This MIB controls all aspects of ISDN interfaces. It consists of five
groups. groups.
o The isdnMibBasicRateGroup is used to provide information regarding o The isdnMibBasicRateGroup is used to provide information regarding
physical Basic Rate interfaces. physical Basic Rate interfaces.
o The isdnMibBearerGroup is used to control B (bearer) channels. It o The isdnMibBearerGroup is used to control B (bearer) channels. It
skipping to change at page 4, line 9 skipping to change at page 5, line 9
o The isdnMibSignalingGroup is used to control D (delta) channels. o The isdnMibSignalingGroup is used to control D (delta) channels.
There are three tables in this group. The isdnSignalingTable and There are three tables in this group. The isdnSignalingTable and
isdnSignalingStatsTable support ISDN Network Layer configuration isdnSignalingStatsTable support ISDN Network Layer configuration
and statistics. The isdnLapdTable supports ISDN Data Link Layer and statistics. The isdnLapdTable supports ISDN Data Link Layer
(LAPD) configuration and statistics. (LAPD) configuration and statistics.
o The optional isdnMibEndpointGroup can be used to specify Terminal o The optional isdnMibEndpointGroup can be used to specify Terminal
Endpoints. It is required only if there are non-ISDN endpoints Endpoints. It is required only if there are non-ISDN endpoints
defined for a given D channel, or if additional information like defined for a given D channel, or if additional information like
Terminal Endpoint Identifier (TEI) values or Service Profile Terminal Endpoint Identifier (TEI) values or Service Profile
IDentifiers (SPID) is required. IDentifiers (SPID) is required to identify a given ISDN user.
o The optional isdnMibDirectoryGroup can be used to specify a list of o The optional isdnMibDirectoryGroup can be used to specify a list of
directory numbers for each signaling channel. It is required only directory numbers for each signaling channel. It is required only
if the directory numbers to be accepted differ from the if the directory numbers to be accepted differ from the
isdnSignalingCallingAddress as specified in the isdnSignalingTable. isdnSignalingCallingAddress as specified in the isdnSignalingTable.
3.2. Relationship to RFC 1573 3.2. Relationship to the Interfaces MIB
RFC 1573 [11], the Interface MIB Evolution, requires that any MIB module
which is an adjunct of the Interface MIB, clarify specific areas within
the Interface MIB. These areas were intentionally left vague in RFC
1573 to avoid over constraining the MIB module, thereby precluding
management of certain media-types.
Section 3.3 of RFC 1573 enumerates several areas which a media-specific This section clarifies the relationship of this MIB to the Interfaces
MIB module must clarify. Each of these areas is addressed in a MIB [11]. Several areas of correlation are addressed in the following
following subsection. The implementor is referred to RFC 1573 in order subsections. The implementor is referred to the Interfaces MIB document
to understand the general intent of these areas. in order to understand the general intent of these areas.
3.2.1. Layering Model 3.2.1. Layering Model
An ISDN interface usually consists of a D channel and a number of B An ISDN interface usually consists of a D channel and a number of B
channels, all of which will be layered on top of a physical interface. channels, all of which are layered on top of a physical interface.
Furthermore, there are multiple interface layers for each D channel. Furthermore, there are multiple interface layers for each D channel.
There are Data Link Layer (LAPD) as well as Network Layer entities. There are Data Link Layer (LAPD) as well as Network Layer entities.
This is accomplished in this MIB by creating a logical interface This is accomplished in this MIB by creating a logical interface
(ifEntry) for each of the D channel entities and a logical interface (ifEntry) for each of the D channel entities and a logical interface
(ifEntry) for each of the B channels. These are then correlated to each (ifEntry) for each of the B channels. These are then correlated to each
other and to the physical interface using the ifStack table of RFC 1573. other and to the physical interface using the ifStack table of the
Interfaces MIB [11].
The basic model, therefore, looks something like this: The basic model, therefore, looks something like this:
| | | |
+--+ +--+ +--+ +--+
| D ch. | | D ch. |
|Layer 3| |Layer 3|
+--+ +--+ +--+ +--+
| | | | | | <== interface to upper | | | | | | <== interface to upper
+--+ +--+ +--+ +--+ +--+ +--+ layers, to be provided +--+ +--+ +--+ +--+ +--+ +--+ layers, to be provided
skipping to change at page 6, line 19 skipping to change at page 7, line 19
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.
In the example given above, the assignment of index values could for In the example given above, the assignment of index values could for
example be as follows: example be as follows:
ifIndex ifType Description ifIndex ifType ISDN MIB tables Description
1 isdns(75) Basic Rate physical interface indexed by ifIndex
2 lapd(77) LAPD interface
3 x25ple(40) X.25 Packet Layer 1 isdns(75) isdnBasicRateTable Basic Rate physical interface
4 isdn(63) ISDN signaling channel #1 2 lapd(77) isdnLapdTable LAPD interface
5 isdn(63) ISDN signaling channel #2 3 x25ple(40) isdnEndpointTable X.25 Packet Layer
6 ds0(81) B channel #1 4 isdn(63) isdnSignalingTable ISDN signaling channel #1
7 ds0(81) B channel #2 isdnEndpointTable
5 isdn(63) isdnSignalingTable ISDN signaling channel #2
isdnEndpointTable
6 ds0(81) isdnBearerTable B channel #1
7 ds0(81) isdnBearerTable B channel #2
8 ppp(23) neighbor entry #1 (see below) 8 ppp(23) neighbor entry #1 (see below)
9 ppp(23) neighbor entry #2 (see below) 9 ppp(23) neighbor entry #2 (see below)
The corresponding ifStack table entries would then be: The corresponding ifStack table entries would then be:
ifStackTable Entries ifStackTable Entries
HigherLayer LowerLayer HigherLayer LowerLayer
0 3 0 3
0 4 0 4
skipping to change at page 6, line 50 skipping to change at page 7, line 54
1 0 1 0
2 1 2 1
3 2 3 2
4 2 4 2
5 2 5 2
6 1 6 1
7 1 7 1
8 6 8 6
9 7 9 7
Mapping of B channels to upper interface layers will usually be done Mapping of B channels to upper interface layers is usually done using
using the Dial Control MIB. For example, mapping on top of B channels the Dial Control MIB. For example, mapping on top of B channels might
might look as follows: look as follows:
+-------------------------------------------------------+ +-------------------------------------------------------+
| Network Layer Protocol | | Network Layer Protocol |
+------+ +-------+ +-------+ +-------+ +-------+ +------+ +------+ +-------+ +-------+ +-------+ +-------+ +------+
| | | | | | | | | | <== appears active | | | | | | | | | | <== appears active
+-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
| PPP | | PPP | | F/R | | PPP | | F/R | | PPP | | PPP | | F/R | | PPP | | F/R |
| for | | for | | for | | for | | for | ifEntry with | for | | for | | for | | for | | for | ifEntry with
|Nbr 1| |Nbr 2| |switch |Nbr 3| |switch shadow |Nbr 1| |Nbr 2| |switch |Nbr 3| |switch shadow
| | | | | A | | | | B | NeighborEntry | | | | | A | | | | B | NeighborEntry
skipping to change at page 7, line 46 skipping to change at page 8, line 46
The ifTestTable is not supported by this MIB. The ifTestTable is not supported by this MIB.
3.2.3. ifRcvAddressTable 3.2.3. ifRcvAddressTable
The ifRcvAddressTable is not supported by this MIB. The ifRcvAddressTable is not supported by this MIB.
3.2.4. ifEntry 3.2.4. ifEntry
3.2.4.1. ifEntry for a Basic Rate hardware interface 3.2.4.1. ifEntry for a Basic Rate hardware interface
The ifGeneralGroup of RFC 1573 is supported for Basic Rate hardware The ifGeneralGroup 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 The IANA value of isdns(75) or isdnu(76), ifType The IANA value of isdns(75) or isdnu(76),
whichever is appropriate. whichever is appropriate.
ifSpeed The overall bandwidth of this interface. ifSpeed The overall bandwidth of this interface.
ifPhysAddress Return zero. ifPhysAddress Return an empty string.
ifAdminStatus The desired administrative status of the ifAdminStatus The administrative status of the ISDN interface.
ISDN interface.
ifOperStatus The current operational status of this ifOperStatus The current operational status of this interface.
interface. If the operational status is dormant(5), The operational status is dormant(5) if
the interface is in standby mode, i.e. connected the interface is in standby mode, i.e. connected
to the network, but without call activity. to the network, but without call activity.
If the operational status is down(2), the hardware The operational status is down(2) if the hardware
has detected that there is no level 1 connection has detected that there is no layer 1 connection
to the switch. to the switch.
For other values, refer to the Interfaces MIB.
ifLastChange Refer to RFC 1573. ifLastChange Refer to the Interfaces MIB.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Refer to RFC 1573. Refer to the Interfaces MIB.
ifConnectorPresent ifConnectorPresent
Refer to RFC 1573. Refer to the Interfaces MIB.
ifHighSpeed Return zero. ifHighSpeed Return zero.
ifName Refer to RFC 1573. ifName Refer to the Interfaces MIB.
3.2.4.2. ifEntry for a B channel 3.2.4.2. ifEntry for a B channel
The ifEntry for a B channel supports the ifGeneralGroup and the The ifEntry for a B channel supports the ifGeneralGroup of the
ifPacketGroup of RFC 1573. Interfaces MIB.
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(81). 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 is the value of 56000 or 64000.
of 56000 or 64000.
ifPhysAddress The ISDN address assigned to this port. ifPhysAddress Return an empty string.
This is a copy of isdnBearerCallingAddress.
ifAdminStatus The desired administrative status of the ifAdminStatus The administrative status of this interface.
ISDN port.
ifOperStatus The current operational status of the ISDN ifOperStatus The current operational status of this interface.
port. Note that dormant(5) is explicitly being
used as defined in RFC 1573.
ifLastChange Refer to RFC 1573. Note that dormant(5) is explicitly being used
as defined in the Interfaces MIB.
For other values, refer to the Interfaces MIB.
ifLastChange Refer to the Interfaces MIB.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Refer to RFC 1573. Refer to the Interfaces MIB.
ifConnectorPresent ifConnectorPresent
Refer to RFC 1573. Refer to the Interfaces MIB.
ifHighSpeed Return zero. ifHighSpeed Return zero.
ifName Refer to RFC 1573. ifName Refer to the Interfaces MIB.
ifMtu The size of the largest frame which can be
sent/received on this B Channel,
specified in octets.
ifInOctets The total number of octets received on this
B channel.
ifInUcastPkts The number of frames received on this B channel.
ifInNUcastPkts Deprecated. Return zero.
ifInDiscards The total number of received frames discards.
The possible reasons are: buffer shortage.
ifInErrors The number of inbound frames that contained
errors preventing them from being deliverable
to a higher-layer protocol.
ifInUnknownProtos The number of inbound frames with unknown
upper layers.
ifOutOctets The total number of octets transmitted on this
B channel.
ifOutUcastPkts The number of frames transmitted on this
B channel.
ifOutNUcastPkts Deprecated. Return zero.
ifOutDiscards The total number of outbound frames which
were discarded. Possible reasons are:
buffer shortage.
ifOutErrors The number of frames which could not be
transmitted due to errors.
ifOutQlen Deprecated. Return zero.
ifSpecific Deprecated. Return {0 0}.
3.2.4.3. ifEntry for LAPD (D channel Data Link Layer) 3.2.4.3. ifEntry for LAPD (D channel Data Link Layer)
The ifEntry for LAPD (D channel Data Link Layer) supports the The ifEntry for LAPD (D channel Data Link Layer) supports the
ifGeneralGroup and the ifPacketGroup of RFC 1573. ifGeneralGroup and the ifPacketGroup of the Interfaces MIB.
ifTable Comments ifTable Comments
============== =========================================== ============== ===========================================
ifIndex Each ISDN D channel Data Link layer is represented ifIndex Each ISDN D channel Data Link layer is represented
by an ifEntry. by an ifEntry.
ifDescr Textual port description. ifDescr Textual port description.
ifType The IANA value of lapd(77). ifType The IANA value of lapd(77).
ifSpeed The bandwidth of this interface. Usually, this will ifSpeed The bandwidth of this interface. Usually, this is
be the value of 16000 for basic rate interfaces or the value of 16000 for basic rate interfaces or
64000 for primary rate interfaces. 64000 for primary rate interfaces.
ifPhysAddress Returns an empty string. ifPhysAddress Return an empty string.
ifAdminStatus The desired administrative status of this ifAdminStatus The administrative status of this interface.
interface.
ifOperStatus The current operational status of the ISDN ifOperStatus The current operational status of the ISDN
UNI (User Network Interface) interface. If the LAPD interface. The operational status is
operational status is dormant(5), the D channel dormant(5) if the interface is in standby mode
is in standby mode (see Q.931 [8], Annex F, (see Q.931 [8], Annex F, D channel backup
D channel backup procedures). procedures).
For other values, refer to the Interfaces MIB.
ifLastChange Refer to RFC 1573. ifLastChange Refer to the Interfaces MIB.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Refer to RFC 1573. Refer to the Interfaces MIB.
ifConnectorPresent ifConnectorPresent
Refer to RFC 1573. Refer to the Interfaces MIB.
ifHighSpeed Return zero. ifHighSpeed Return zero.
ifName Refer to RFC 1573. ifName Refer to the Interfaces MIB.
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 is the
default value of 260 as specified in Q.921 default value of 260 as specified in Q.921
[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 with TEI=127.
targeted TEI=127.
ifInMulticastPkts Return zero.
ifInBroadcastPkts Return the number of frames received
on this interface with TEI=127.
ifInDiscards The total number of received frames which have been ifInDiscards The total number of received frames which have been
discarded. discarded.
The possible reasons are: buffer shortage. The possible reasons are: buffer shortage.
ifInErrors The number of inbound frames that contained ifInErrors The number of inbound frames that contained
errors preventing them from being deliverable errors preventing them from being deliverable
to LAPD. to LAPD.
ifInUnknownProtos The number of frames with known TEI, but unknown ifInUnknownProtos The number of frames with known TEI, but unknown
SAPI (Service Access Point Identifier, SAPI (Service Access Point Identifier,
see Q.921 [6], chapter 3.3.3). see Q.921 [6], chapter 3.3.3).
ifOutOctets The total number of octets transmitted on this ifOutOctets The total number of octets transmitted on this
interface. interface.
ifOutUcastPkts The number of frames transmitted on this ifOutUcastPkts The number of frames transmitted on this
interface whose address is not TEI=127. interface whose address is not TEI=127.
ifOutNUcastPkts Deprecated. Return the number of frames ifOutNUcastPkts Deprecated. Return the number of frames
transmitted on this interface which transmitted on this interface with TEI=127.
have TEI=127.
ifOutMulticastPkts
Return zero.
ifOutBroadcastPkts
Return the number of frames transmitted
on this interface with TEI=127.
ifOutDiscards The total number of outbound frames which ifOutDiscards The total number of outbound frames which
were discarded. Possible reasons are: were discarded. Possible reasons are:
buffer shortage. buffer shortage.
ifOutErrors The number of frames which could not be ifOutErrors The number of frames which could not be
transmitted due to errors. transmitted due to errors.
ifOutQlen Deprecated. Return zero. ifOutQlen Deprecated. Return zero.
ifSpecific Deprecated. Return {0 0}. ifSpecific Deprecated. Return {0 0}.
3.2.4.4. ifEntry for a signaling channel 3.2.4.4. ifEntry for a signaling channel
The ifEntry for a signaling channel supports the ifGeneralGroup and the The ifEntry for a signaling channel supports the ifGeneralGroup and the
ifPacketGroup of RFC 1573. ifPacketGroup of the Interfaces MIB.
ifTable Comments ifTable Comments
============== =========================================== ============== ===========================================
ifIndex Each ISDN signaling channel is represented by ifIndex Each ISDN signaling channel is represented by
an ifEntry. an ifEntry.
ifDescr Textual port description. ifDescr Textual port description.
ifType The IANA value of isdn(63). ifType The IANA value of isdn(63).
ifSpeed The bandwidth of this signaling channel. Usually, ifSpeed The bandwidth of this signaling channel. Usually,
this will the same value as for LAPD, this is the same value as for LAPD, i.e. 16000
i.e. 16000 for basic rate interfaces or 64000 for basic rate interfaces or 64000 for primary rate
for primary rate interfaces. interfaces.
ifPhysAddress The ISDN address assigned to this signaling channel. ifPhysAddress The ISDN address assigned to this signaling channel.
This is a copy of isdnSignalingCallingAddress. This is a copy of isdnSignalingCallingAddress.
ifAdminStatus The desired administrative status of the ifAdminStatus The administrative status of the signaling channel.
signaling channel.
ifOperStatus The current operational status of this signaling ifOperStatus The current operational status of this signaling
channel. If the operational status is dormant(5), channel. The operational status is dormant(5) if
the signaling channel is currently not activated. the signaling channel is currently not activated.
For other values, refer to the Interfaces MIB.
ifLastChange Refer to RFC 1573. ifLastChange Refer to the Interfaces MIB.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Refer to RFC 1573. Refer to the Interfaces MIB.
ifConnectorPresent ifConnectorPresent
Refer to RFC 1573. Refer to the Interfaces MIB.
ifHighSpeed Return zero. ifHighSpeed Return zero.
ifName Refer to RFC 1573. ifName Refer to the Interfaces MIB.
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 is the
default value of 260 as specified in Q.921 default value of 260 as specified in Q.921
[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.
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 with TEI=127.
targeted TEI=127.
ifInMulticastPkts Return zero.
ifInBroadcastPkts Return the number of frames received
on this signaling channel with TEI=127.
ifInDiscards The total number of received frames which have been ifInDiscards The total number of received frames which have been
discarded. discarded.
The possible reasons are: buffer shortage. The possible reasons are: buffer shortage.
ifInErrors The number of inbound frames that contained ifInErrors The number of inbound frames that contained
errors preventing them from being deliverable errors preventing them from being deliverable
to the signaling channel. to the signaling channel.
ifInUnknownProtos Return zero. ifInUnknownProtos Return zero.
ifOutOctets The total number of octets transmitted on this ifOutOctets The total number of octets transmitted on this
signaling channel. signaling channel.
ifOutUcastPkts The number of frames transmitted on this ifOutUcastPkts The number of frames transmitted on this
signaling channel whose address is not TEI=127. signaling channel whose address is not TEI=127.
ifOutNUcastPkts Deprecated. Return the number of frames ifOutNUcastPkts Deprecated. Return the number of frames
transmitted on this signaling channel which transmitted on this signaling channel with TEI=127.
have TEI=127.
ifOutMulticastPkts
Return zero.
ifOutBroadcastPkts
Return the number of frames transmitted
on this signaling channel with TEI=127.
ifOutDiscards The total number of outbound frames which ifOutDiscards The total number of outbound frames which
were discarded. Possible reasons are: were discarded. Possible reasons are:
buffer shortage. buffer shortage.
ifOutErrors The number of frames which could not be ifOutErrors The number of frames which could not be
transmitted due to errors. transmitted due to errors.
ifOutQlen Deprecated. Return zero. ifOutQlen Deprecated. Return zero.
ifSpecific Deprecated. Return {0 0}. ifSpecific Deprecated. Return {0 0}.
3.3. Relationship to other MIBs 3.3. Relationship to other MIBs
3.3.1. Relationship to the DS1/E1 MIB 3.3.1. Relationship to the DS1/E1 MIB
Implementation of the DS1/E1 MIB is not required for supporting this Implementation of the DS1/E1 MIB [12] is not required for supporting
MIB. It is however recommended to implement the DS1/E1 MIB on entities this MIB. It is however recommended to implement the DS1/E1 MIB on
supporting Primary Rate interfaces. entities supporting Primary Rate interfaces.
3.3.2. Relationship to the DS0 and DS0Bundle MIBs 3.3.2. Relationship to the DS0 and DS0Bundle MIBs
Implementation of the DS0 MIB is optional. Implementation of the DS0 MIB [13] is optional.
Implementation of the DS0Bundle MIB is required only if hyperchannels Implementation of the DS0Bundle MIB [13] is required only if
are to be supported. hyperchannels are to be supported.
3.3.3. Relationship to the Dial Control MIB 3.3.3. Relationship to the Dial Control MIB
Implementation of the Dial Control MIB is required. Implementation of the Dial Control MIB [15] is required.
3.4. ISDN interface specific information 3.4. ISDN interface specific information and implementation hints
3.4.1. ISDN leased lines 3.4.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 is
will be no signaling protocol support for leased line B channels, since no signaling protocol support for leased line B channels, since there is
there is no signaling protocol action for these kinds of interfaces. no signaling protocol action for these kinds of interfaces.
If there is no signaling support available for an ISDN interface, this If there is no signaling support available for an ISDN interface, this
must be specified in the appropriate interface specific table. For must be specified in the appropriate interface specific table. For
Basic Rate interfaces, isdnBasicRateSignalMode of isdnBasicRateTable Basic Rate interfaces, isdnBasicRateSignalMode of isdnBasicRateTable
must be set to inactive(2). For Primary Rate interfaces, dsx1SignalMode must be set to inactive(2). For Primary Rate interfaces, dsx1SignalMode
of dsx1ConfigTable in DS1/E1 MIB [12] must be set to none(1). There of dsx1ConfigTable in DS1/E1 MIB [12] must be set to none(1). There are
will be no isdnLapdTable or isdnSignalingTable entries for such no isdnLapdTable or isdnSignalingTable entries for such interfaces.
interfaces.
Depending on the leased line type and the service provider, the D Depending on the leased line type and the service provider, the D
channel can then eventually be used for data transfer. To support this, channel can be used for data transfer. If this is the case the D
the D channel interface type will be ds0(81) instead of lapd(77) and its channel interface type is ds0(81) instead of lapd(77) and its usage is
usage will be identical to B channel usage if there is no signaling identical to B channel usage if there is no signaling channel available.
channel available.
For a Primary Rate interface which is entirely used as a leased line, 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 is 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.4.2. Hyperchannels 3.4.2. Hyperchannels
The switch protocol in use will define if hyperchannels are supported, The active switch protocol defines if hyperchannels are supported, and
and the actual support will be implementation dependent. Hyperchannel the actual support is implementation dependent. Hyperchannel
connections itself will be requested by the interface user, e.g. by the connections will be requested by the interface user at call setup time,
neighbor connection handling procedures. e.g. by the neighbor connection handling procedures.
In the ISDN MIB, the isdnBearerMultirate object of isdnBearerTable can In the ISDN MIB, the isdnBearerMultirate object of isdnBearerTable can
be used to check if hyperchannels are being used for an active call. be used to check if hyperchannels are being used for an active call.
If hyperchannels are being used, there will be another interface layer If hyperchannels are being used, another interface layer is required to
required to map multiple B channels to a single hyperchannel. This is map multiple B channels to a single hyperchannel. This is accomplished
accomplished by the DS0Bundle MIB [13]. by using the DS0Bundle MIB [13].
Each hyperchannel call is treated as one call in the
isdnSignalingStatsTable, independent of the number of B channels
involved.
For a hyperchannel call, all objects in the isdnBearerTable entries
related to this call (i.e., all isdnBearerTable entries associated to B
channels used by the hyperchannel) have identical values. The related
objects in the isdnBearerTable are:
isdnBearerPeerAddress
isdnBearerPeerSubAddress
isdnBearerCallOrigin
isdnBearerInfoType
isdnBearerMultirate
isdnBearerCallSetupTime
isdnBearerCallConnectTime
isdnBearerChargedUnits
3.4.3. D channel backup and NFAS trunks 3.4.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 Non Facility Associated Signaling (NFAS) trunks. identical to Non Facility Associated Signaling (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 B channels. slots are being used for B channels.
According to Q.931, Annex F, the D channel backup feature can be According to Q.931, Annex F, the D channel backup feature can be
provided on a subscription basis and is network dependent. The D provided on a subscription basis and is network dependent. The D
channel backup procedure is described in detail in Q.931. channel backup procedure is described in detail in Q.931.
skipping to change at page 15, line 16 skipping to change at page 16, line 5
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 B channels. slots are being used for B channels.
According to Q.931, Annex F, the D channel backup feature can be According to Q.931, Annex F, the D channel backup feature can be
provided on a subscription basis and is network dependent. The D provided on a subscription basis and is network dependent. The D
channel backup procedure is described in detail in Q.931. channel backup procedure is described in detail in Q.931.
For D channel backup, the controlling isdnSignalingTable entry will be For D channel backup, the controlling isdnSignalingTable entry is
layered on top of all attached LAPD interfaces. This layering will be layered on top of all attached LAPD interfaces. This layering is done
done using the ifStack table. There will be only one active LAPD using the ifStack table. There is only one active LAPD interface,
interface, however. Inactive LAPD interfaces will have an ifOperStatus however. Inactive LAPD interfaces have an ifOperStatus of dormant(5).
of dormant(5).
NFAS trunks will also be handled using the ifStack table. In this case, NFAS trunks are also handled using the ifStack table. In this case, a
a signaling channel will be layered on top of a LAPD interface as well signaling channel is layered on top of a LAPD interface as well as on
as on top of all physical interfaces which are controlled by the top of all physical interfaces which are controlled by the signaling
signaling channel, but do not supply a D channel. channel, but do not supply a D channel.
3.4.4. X.25 based packet-mode service in B and D channels 3.4.4. X.25 based packet-mode service in B and D channels
X.25 based packet mode service over B channels can be handled using the X.25 based packet mode service over B channels can be handled using the
Dial Control MIB by creating an appropriate neighbor entry. The Dial Control MIB by creating an appropriate neighbor entry. The
neighbor entry ifType can then be x25(5), thus providing access to X.25 neighbor entry ifType can then be x25(5), thus providing access to X.25
service. service.
X.25 based packet mode service over D channels can be handled by X.25 based packet mode service over D channels can be handled by
creating an ifEndpointTable entry with an isdnEndpointIfType of creating an ifEndpointTable entry with an isdnEndpointIfType of
skipping to change at page 16, line 16 skipping to change at page 17, line 4
There is one data link for each SPID. As part of terminal registration, There is one data link for each SPID. As part of terminal registration,
an EID (Endpoint IDentifier) is defined by the switch. On incoming an EID (Endpoint IDentifier) is defined by the switch. On incoming
calls, the switch may provide the EID, a called party number, or both, calls, the switch may provide the EID, a called party number, or both,
depending on the ISDN code implemented in the switch. depending on the ISDN code implemented in the switch.
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 isdnSignalingCallingAddress, already object of isdnEndpointTable. The isdnSignalingCallingAddress, already
being used to specify the calling number, cannot be used for this being used to specify the calling number, cannot be used to record the
purpose, since both may differ and be required in parallel. SPID since the values of the SPID and the Calling Address may differ and
both may be required to be present.
3.4.6. Closed User Groups 3.4.6. Closed User Groups
Closed User Groups (CUG), as defined in I.255.1 [14], are supported for Closed User Groups (CUG), as defined in I.255.1 [14], are supported for
circuit mode calls by ETSI (ETS 300 138) 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 Group 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 is the preferred Closed User Group. For such addresses,
addresses, only calls from assigned Closed User Groups will be accepted only calls from assigned Closed User Groups are 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 are
be defined in the Dial Control MIB. A neighbor entry attached to a defined in the Dial Control MIB. A neighbor entry attached to a Closed
Closed User Group will have to point to an ISDN interface which is User Group has to point to an ISDN interface which is attached to the
attached to the Closed User Group in question. Closed User Group in question.
3.4.7. Provision of point-to-point line topology 3.4.7. Provision of point-to-point line topology
In the ISDN standards, there are two different meanings for the term In the ISDN standards, there are two different meanings for the term
"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 are usually 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 line topology to layer 1 connections. For Primary Rate interfaces, the line topology
will always be point-to-point. For Basic Rate interfaces, layer 1 is always point-to-point. For Basic Rate interfaces, layer 1 point-to-
point-to-point connections do exist in several countries, usually being point connections do exist in several countries, usually being used for
used for connecting PBX systems to the network. 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.
For Basic Rate interfaces, the isdnBasicRateTable object For Basic Rate interfaces, the isdnBasicRateTable object
isdnBasicRateLineTopology can be used to select the line topology. isdnBasicRateLineTopology can be used to select the line topology.
3.4.8. Speech and audio bearer capability information elements 3.4.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
skipping to change at page 18, line 5 skipping to change at page 18, line 45
In some cases, the Speech or 3.1 kHz Bearer Capability provides a 56 In some cases, the Speech or 3.1 kHz Bearer Capability provides a 56
kbit/s data path through the network. Therefore, some people are kbit/s data path through the network. Therefore, some people are
setting up calls with the Speech or 3.1 kHz BC and transmitting 56 setting up calls with the Speech or 3.1 kHz BC and transmitting 56
kbit/s data over the connection. This is usually to take advantage of kbit/s data over the connection. This is usually to take advantage of
favorable tariffs for Speech as opposed to Data. favorable tariffs for Speech as opposed to Data.
On the incoming side, the equipment is usually configured to ignore the On the incoming side, the equipment is usually configured to ignore the
Bearer Capability and either answer all Speech calls as 56 kbit/s data Bearer Capability and either answer all Speech calls as 56 kbit/s data
or to use one Directory Number for real speech and another for data. or to use one Directory Number for real speech and another for data.
3.4.9. Attaching incoming calls to router ports
In ISDN, there are several ways to identify an incoming call and to
attach a router port to this call.
o The call can be identified and attached to a router port using the
ISDN Calling Address, that is, the peer ISDN address. Since the
peer address is defined in a Dial Control MIB configuration entry
for this peer, this would be the most natural way to attach an
incoming call to a router port.
In this configuration, only a single isdnSignalingTable entry is
required for each physical ISDN interface. Unfortunately, the ISDN
Calling Address is not available in all countries and/or switch
protocols. Therefore, other means for attaching incoming calls to
router ports must be provided.
o The call can also be identified and attached to a router port using
the ISDN Called Address. In this case, a distinct ISDN address or
subaddress must be specified for each of the router ports.
This can be accomplished in the ISDN MIB by creating a
isdnSignalingTable entry for each of the router ports, and by
connecting Dial Control MIB neighbor entries to the thereby created
interface using the dialCtlNbrCfgLowerIf object of
dialCtlNbrCfgTable.
If this type of router port identification is used in an
implementation, it is up to the implementor to decide if there
should be distinct TEI values assigned for each of the
isdnSignalingTable entries. For this reason, the isdnEndpointTable
permits specifying the same TEI value in multiple entries. It is
recommended to use dynamic TEI assignment whenever possible.
The implementor should be aware that this type of configuration
requires a lot of configuration work for the customer, since an
entry in isdnSignalingTable must be created for each of the router
ports.
o Incoming calls can also be identified and attached to router ports
using a higher layer functionality, such as PPP authentication.
Defining this functionality is outside the scope of this document.
3.4.10. Usage of isdnMibDirectoryGroup and isdnDirectoryTable
In some switch protocol or PBX implementations, the Called Number
Information Element on incoming calls can differ from the Calling Number
on outgoing calls. Sometimes, the Called Number can be different for
incoming Local Calls, Long Distance Calls and International Calls. For
Hunt Groups, the Called Number can be any of the numbers in the Hunt
Group.
The isdnDirectoryTable can be used to specify all these numbers.
Entries in the isdnDirectoryTable are always connected to specific
isdnSignalingTable entries. No ifEntry is created for
isdnDirectoryTable entries. Therefore, the isdnDirectoryTable can not
be used to attach incoming calls to router ports. For router port
identification, isdnSignalingTable entries should be created instead.
4. Definitions 4. Definitions
ISDN-MIB DEFINITIONS ::= BEGIN ISDN-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Gauge32, Gauge32,
skipping to change at page 18, line 36 skipping to change at page 20, line 36
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 "9604271033Z" -- Apr 27, 1996 LAST-UPDATED "9608230910Z" -- Aug 23, 1996
ORGANIZATION "IETF ISDN MIB Working Group" ORGANIZATION "IETF ISDN MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Guenter Roeck " Guenter Roeck
Postal: Conware GmbH Postal: cisco Systems
Killisfeldstrasse 64 170 West Tasman Drive
76227 Karlsruhe San Jose, CA 95134
Germany U.S.A.
Tel: +49 721 9495 0 Phone: +1 408 527 3143
E-mail: roeck@conware.de" E-mail: groeck@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module to describe the "The MIB module to describe the
management of ISDN interfaces." management of ISDN interfaces."
::= { transmission 20 } ::= { transmission 20 }
-- The ISDN hardware interface (BRI or PRI) is represented
-- 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
-- is defined in the physical interface group of the ISDN MIB.
-- The ifType for physical basic rate interfaces is isdns(75)
-- or isdnu(76), whichever is appropriate. -- or isdnu(76), whichever is appropriate.
-- --
-- For primary rate, the media specifics are defined in the Trunk
-- MIB and the ifType has a value of ds1(18).
-- Each signaling channel is represented by an entry
-- in the isdnSignalingTable. -- in the isdnSignalingTable.
-- The signaling channel has an ifType value of isdn(63).
-- Each B channel is also represented as an entry
-- in the ifTable. The B channels have an ifType value
-- of ds0(81). -- of ds0(81).
-- This model is used while defining objects and tables
-- for management. -- for management.
-- The ISDN MIB allows 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 describes the D and B channels, a media specific MIB
-- for PPP can be used on a layered basis. This is as per
-- the interfaces MIB.
-- Textual conventions -- Textual conventions
IsdnSignalingProtocol ::= TEXTUAL-CONVENTION IsdnSignalingProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
isdnSignalingProtocol object in the isdnSignalingProtocol object in the
definition of ISDN-MIB's isdnSignalingTable. definition of ISDN-MIB's isdnSignalingTable.
skipping to change at page 21, line 23 skipping to change at page 23, line 23
isdnBasicRateIfType OBJECT-TYPE isdnBasicRateIfType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
isdns(75), isdns(75),
isdnu(76) isdnu(76)
} }
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(75). the value of this object is isdns(75).
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 is
isdnu(76)." isdnu(76)."
::= { isdnBasicRateEntry 1 } ::= { isdnBasicRateEntry 1 }
isdnBasicRateLineTopology OBJECT-TYPE isdnBasicRateLineTopology OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pointToPoint(1), pointToPoint(1),
pointToMultipoint(2) pointToMultipoint(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 21, line 52 skipping to change at page 23, line 52
isdnBasicRateIfMode OBJECT-TYPE isdnBasicRateIfMode 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 is te(1). For NT mode, the value
of this object will be nt(2)." of this object is nt(2)."
::= { isdnBasicRateEntry 3 } ::= { isdnBasicRateEntry 3 }
isdnBasicRateSignalMode OBJECT-TYPE isdnBasicRateSignalMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
active(1), active(1),
inactive(2) inactive(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The signaling channel operational mode for this interface. "The signaling channel operational mode for this interface.
If set to active(1), there is a signaling channel on this If active(1) there is a signaling channel on this
interface. If set to inactive(2), a signaling channel is interface. If inactive(2) a signaling channel is
not available." not available."
::= { isdnBasicRateEntry 4 } ::= { isdnBasicRateEntry 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 specifically, 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
STATUS current STATUS current
skipping to change at page 23, line 22 skipping to change at page 25, line 22
isdnBearerChannelType OBJECT-TYPE isdnBearerChannelType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dialup(1), dialup(1),
leased(2) leased(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The B channel type. If the B channel is connected "The B channel type. If the B channel is connected
to a dialup line, this object will be have a value of to a dialup line, this object has a value of
dialup(1). In this case, it will be controlled by dialup(1). In this case, it is controlled by
an associated signaling channel. If the B channel an associated signaling channel. If the B channel
is connected to a leased line, this object will have is connected to a leased line, this object has
a value of leased(2). For leased line B channels, there a value of leased(2). For leased line B channels, there
is no signaling channel control available." is no signaling channel control available."
::= { isdnBearerEntry 1 } ::= { isdnBearerEntry 1 }
isdnBearerOperStatus OBJECT-TYPE isdnBearerOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
idle(1), idle(1),
connecting(2), connecting(2),
connected(3), connected(3),
active(4) active(4)
skipping to change at page 24, line 21 skipping to change at page 26, line 21
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ISDN address the current or last call is or was "The ISDN address the current or last call is or was
connected to. connected to.
In some cases, the format of this information can not In some cases, the format of this information can not
be predicted, since it largely depends on the type be predicted, since it largely depends on the type
of switch or PBX the device is connected to. Therefore, of switch or PBX the device is connected to. Therefore,
the detailed format of this information will not be the detailed format of this information is not
specified and is implementation dependent. specified and is implementation dependent.
If possible, the agent should supply this information If possible, the agent should supply this information
using the E.164 format. In this case, the number must using the E.164 format. In this case, the number must
start with '+'. Otherwise, IA5 number digits must be used. start with '+'. Otherwise, IA5 number digits must be used.
If the peer ISDN address is not available, If the peer ISDN address is not available,
this object it will have a length of zero." this object has a length of zero."
REFERENCE REFERENCE
"ITU-T E.164, Q.931 chapter 4.5.10" "ITU-T E.164, Q.931 chapter 4.5.10"
::= { isdnBearerEntry 4 } ::= { isdnBearerEntry 4 }
isdnBearerPeerSubAddress OBJECT-TYPE isdnBearerPeerSubAddress OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ISDN subaddress the current or last call is or was "The ISDN subaddress the current or last call is or was
connected to. connected to.
The subaddress is an user supplied string of up to 20 The subaddress is an user supplied string of up to 20
IA5 characters and is transmitted transparently through IA5 characters and is transmitted transparently through
the network. the network.
If the peer subaddress is not available, this object If the peer subaddress is not available, this object
will have a length of zero." has a length of zero."
REFERENCE REFERENCE
"ITU-T I.330, Q.931 chapter 4.5.11" "ITU-T I.330, Q.931 chapter 4.5.11"
::= { isdnBearerEntry 5 } ::= { isdnBearerEntry 5 }
isdnBearerCallOrigin OBJECT-TYPE isdnBearerCallOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
originate(2), originate(2),
answer(3), answer(3),
callback(4) callback(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The call origin for the current or last call. If since "The call origin for the current or last call. If since
system startup there was no call on this interface, system startup there was no call on this interface,
this object will have a value of unknown(1)." this object has a value of unknown(1)."
::= { isdnBearerEntry 6 } ::= { isdnBearerEntry 6 }
isdnBearerInfoType OBJECT-TYPE isdnBearerInfoType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
speech(2), speech(2),
unrestrictedDigital(3), -- as defined in Q.931 unrestrictedDigital(3), -- as defined in Q.931
unrestrictedDigital56(4), -- with 56k rate adaption unrestrictedDigital56(4), -- with 56k rate adaption
restrictedDigital(5), restrictedDigital(5),
audio31(6), -- 3.1 kHz audio audio31(6), -- 3.1 kHz audio
skipping to change at page 25, line 41 skipping to change at page 27, line 41
or last call. or last call.
speech(2) refers to a non-data connection, whereas speech(2) refers to a non-data connection, whereas
audio31(6) and audio7(7) refer to data mode connections. audio31(6) and audio7(7) refer to data mode connections.
Note that Q.931, chapter 4.5.5, originally defined Note that Q.931, chapter 4.5.5, originally defined
audio7(7) as '7 kHz audio' and now defines it as audio7(7) as '7 kHz audio' and now defines it as
'Unrestricted digital information with tones/ 'Unrestricted digital information with tones/
announcements'. announcements'.
If since system startup there was no call on this If since system startup there has been no call on this
interface, this object will have a value of unknown(1)." interface, this object has a value of unknown(1)."
REFERENCE REFERENCE
"Q.931 [8], chapter 4.5.5, octet 3 of bearer capability "Q.931 [8], chapter 4.5.5, octet 3 of bearer capability
information element, combined with the User Rate information element, combined with the User Rate
(as defined in octets 5 and 5a to 5d), if rate adaption (as defined in octets 5 and 5a to 5d), if rate adaption
is being used." is being used."
::= { isdnBearerEntry 7 } ::= { isdnBearerEntry 7 }
isdnBearerMultirate OBJECT-TYPE isdnBearerMultirate OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This flag describes if the current or last call used "This flag indicates if the current or last call used
multirate. The actual information transfer rate, multirate. The actual information transfer rate,
in detail specified in octet 4.1 (rate multiplier), in detail specified in octet 4.1 (rate multiplier),
will be the sum of all B channel ifSpeed values for is the sum of all B channel ifSpeed values for
the hyperchannel. the hyperchannel.
If since system startup there was no call on this If since system startup there was no call on this
interface, this object will have a value of false(2)." interface, this object has a value of false(2)."
REFERENCE REFERENCE
"Q.931 [8], chapter 4.5.5." "Q.931 [8], chapter 4.5.5."
::= { isdnBearerEntry 8 } ::= { isdnBearerEntry 8 }
isdnBearerCallSetupTime OBJECT-TYPE isdnBearerCallSetupTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when the ISDN setup message for "The value of sysUpTime when the ISDN setup message for
the current or last call was sent or received. If since the current or last call was sent or received. If since
system startup there was no call on this interface, this system startup there has been no call on this interface,
object will have a value of zero." this object has a value of zero."
::= { isdnBearerEntry 9 } ::= { isdnBearerEntry 9 }
isdnBearerCallConnectTime OBJECT-TYPE isdnBearerCallConnectTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when the ISDN connect message for "The value of sysUpTime when the ISDN connect message for
the current or last call was sent or received. If since the current or last call was sent or received. If since
system startup there was no call on this interface, this system startup there has been no call on this interface,
object will have a value of zero." this object has a value of zero."
::= { isdnBearerEntry 10 } ::= { isdnBearerEntry 10 }
isdnBearerChargedUnits OBJECT-TYPE isdnBearerChargedUnits OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of charged units for the current or last "The number of charged units for the current or last
connection. For incoming calls or if charging information connection. For incoming calls or if charging information
is not supplied by the switch, the value of this object is not supplied by the switch, the value of this object
will be zero." is zero."
::= { isdnBearerEntry 11 } ::= { isdnBearerEntry 11 }
-- ISDN signaling group -- ISDN signaling group
isdnSignalingGroup OBJECT IDENTIFIER ::= { isdnMibObjects 3 } isdnSignalingGroup OBJECT IDENTIFIER ::= { isdnMibObjects 3 }
-- signaling channel configuration table -- signaling channel configuration table
-- There is one entry in this table for each Terminal Endpoint -- There is one entry in this table for each Terminal Endpoint
-- (link layer connection to the switch). -- (link layer connection to the switch).
-- Usually, there is one endpoint per D channel. In some
-- cases, however, there can be multiple endpoints. -- cases, however, there can be multiple endpoints.
-- Thus, entries in this table can be created and deleted. -- Thus, entries in this table can be created and deleted.
-- This also means the creation of an associated ifEntry.
-- --
-- D channel backup and NFAS trunks are handled using the
-- ifStack table. -- ifStack table.
-- In case of D channel backup, there are multiple
-- Data Link Layer (LAPD) interfaces. Only one interface is
-- active; all others are dormant(5).
-- In case of NFAS trunks, one lower interface is the
-- LAPD interface, while the other lower interfaces are physical
-- interfaces. -- interfaces.
-- If directory number and calling address differ from each other -- If directory number and calling address differ from each other
-- or multiple directory numbers are being used, -- or multiple directory numbers are being used,
-- the isdnDirectoryTable has to be used to enter such -- the isdnDirectoryTable has to be used to enter such
-- directory numbers. -- directory numbers.
isdnSignalingGetIndex OBJECT-TYPE isdnSignalingGetIndex OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 28, line 50 skipping to change at page 30, line 50
switch providing access to the ISDN network switch providing access to the ISDN network
to which this signaling channel is connected." to which this signaling channel is connected."
::= { isdnSignalingEntry 3 } ::= { isdnSignalingEntry 3 }
isdnSignalingCallingAddress OBJECT-TYPE isdnSignalingCallingAddress 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
channel. More specific, this is the 'Calling Address channel. More specifically, 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.
It can be an EAZ (1TR6), a calling number (DSS1, ETSI) It can be an EAZ (1TR6), a calling number (DSS1, ETSI)
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.
The format of this information largely depends on the type The format of this information largely depends on the type
of switch or PBX the device is connected to. Therefore, of switch or PBX the device is connected to. Therefore,
the detailed format of this information will not be the detailed format of this information is not
specified and is implementation dependent. specified and is implementation dependent.
If possible, the agent should implement this information If possible, the agent should implement this information
using the E.164 number format. In this case, the number using the E.164 number format. In this case, the number
must start with '+'. Otherwise, IA5 number digits must must start with '+'. Otherwise, IA5 number digits must
be used." be used."
REFERENCE REFERENCE
"ITU-T E.164, Q.931 chapter 4.5.10" "ITU-T E.164, Q.931 chapter 4.5.10"
DEFVAL { "" } DEFVAL { "" }
::= { isdnSignalingEntry 4 } ::= { isdnSignalingEntry 4 }
isdnSignalingSubAddress OBJECT-TYPE isdnSignalingSubAddress 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 signaling channel. Usually, this will be the to this signaling channel. Usually, this is the
subaddress as defined in Q.931. subaddress 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 is used for incoming calls as well as
for outgoing calls. for outgoing calls.
The subaddress is an user supplied string of up to 20 The subaddress is an user supplied string of up to 20
IA5 characters and is transmitted transparently through IA5 characters and is transmitted transparently through
the network." the network."
REFERENCE REFERENCE
"ITU-T I.330, Q.931 chapter 4.5.11" "ITU-T I.330, Q.931 chapter 4.5.11"
DEFVAL { "" } DEFVAL { "" }
::= { isdnSignalingEntry 5 } ::= { isdnSignalingEntry 5 }
isdnSignalingBchannelCount OBJECT-TYPE isdnSignalingBchannelCount 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 channel. The default value managed by this signaling channel. The default value
of this object depends on the physical interface type of this object depends on the physical interface type
and will either be 2 for Basic Rate interfaces or and is either 2 for Basic Rate interfaces or
24 (30) for Primary Rate interfaces." 24 (30) for Primary Rate interfaces."
::= { isdnSignalingEntry 6 } ::= { isdnSignalingEntry 6 }
isdnSignalingInfoTrapEnable OBJECT-TYPE isdnSignalingInfoTrapEnable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 30, line 43 skipping to change at page 32, line 43
-- 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
DESCRIPTION DESCRIPTION
"ISDN signaling table containing statistics "ISDN signaling table containing statistics
information for all ISDN signaling channels information for all ISDN signaling channels
on this managed device. on this managed device.
Only statistical information which is not being counted Only statistical information which is not already being
in the ifTable is being defined in this table." counted in the ifTable is being defined in this table."
::= { isdnSignalingGroup 3 } ::= { isdnSignalingGroup 3 }
isdnSignalingStatsEntry OBJECT-TYPE isdnSignalingStatsEntry OBJECT-TYPE
SYNTAX IsdnSignalingStatsEntry SYNTAX IsdnSignalingStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the ISDN Signaling statistics Table." "An entry in the ISDN Signaling statistics Table."
AUGMENTS { isdnSignalingEntry } AUGMENTS { isdnSignalingEntry }
::= { isdnSignalingStatsTable 1 } ::= { isdnSignalingStatsTable 1 }
skipping to change at page 31, line 56 skipping to change at page 33, line 56
isdnSigStatsChargedUnits OBJECT-TYPE isdnSigStatsChargedUnits OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of charging units on this interface since "The number of charging units on this interface since
system startup. system startup.
Only the charging units applying to the local interface, Only the charging units applying to the local interface,
i.e. for originated calls or for calls with 'Reverse i.e. for originated calls or for calls with 'Reverse
charging' being active, will be counted here." charging' being active, are counted here."
::= { isdnSignalingStatsEntry 5 } ::= { isdnSignalingStatsEntry 5 }
-- --
-- The LAPD table -- The LAPD table
isdnLapdTable OBJECT-TYPE isdnLapdTable OBJECT-TYPE
SYNTAX SEQUENCE OF IsdnLapdEntry SYNTAX SEQUENCE OF IsdnLapdEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table containing configuration and statistics "Table containing configuration and statistics
information for all LAPD (D channel Data Link) information for all LAPD (D channel Data Link)
interfaces on this managed device. interfaces on this managed device.
Only statistical information which is not being counted Only statistical information which is not already being
in the ifTable is being defined in this table." counted in the ifTable is being defined in this table."
::= { isdnSignalingGroup 4 } ::= { isdnSignalingGroup 4 }
isdnLapdEntry OBJECT-TYPE isdnLapdEntry OBJECT-TYPE
SYNTAX IsdnLapdEntry SYNTAX IsdnLapdEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the LAPD Table." "An entry in the LAPD Table."
INDEX { ifIndex } INDEX { ifIndex }
::= { isdnLapdTable 1 } ::= { isdnLapdTable 1 }
skipping to change at page 32, line 46 skipping to change at page 34, line 46
isdnLapdPrimaryChannel OBJECT-TYPE isdnLapdPrimaryChannel OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If set to true(1), this D channel is the designated "If set to true(1), this D channel is the designated
primary D channel if D channel backup is active. primary D channel if D channel backup is active.
There must be exactly one primary D channel There must be exactly one primary D channel
configured. If D channel backup is not used, this configured. If D channel backup is not used, this
object will have a value of true(1)." object has a value of true(1)."
REFERENCE REFERENCE
"Q.931 [8], Annex F, D channel backup procedures." "Q.931 [8], Annex F, D channel backup procedures."
::= { isdnLapdEntry 1 } ::= { isdnLapdEntry 1 }
isdnLapdOperStatus OBJECT-TYPE isdnLapdOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
inactive(1), inactive(1),
l1Active(2), l1Active(2),
l2Active(3) l2Active(3)
} }
skipping to change at page 35, line 14 skipping to change at page 37, line 14
Terminal Endpoint." Terminal Endpoint."
::= { isdnEndpointEntry 2 } ::= { isdnEndpointEntry 2 }
isdnEndpointIfType OBJECT-TYPE isdnEndpointIfType OBJECT-TYPE
SYNTAX IANAifType SYNTAX IANAifType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface type for this Terminal Endpoint. "The interface type for this Terminal Endpoint.
Interface types of x25ple(40) and isdn(63) are allowed. Interface types of x25ple(40) and isdn(63) are allowed.
The interface type will be identical to the value of The interface type is identical to the value of
ifType in the associated ifEntry." ifType in the associated ifEntry."
::= { isdnEndpointEntry 3 } ::= { isdnEndpointEntry 3 }
isdnEndpointTeiType OBJECT-TYPE isdnEndpointTeiType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dynamic(1), dynamic(1),
static(2) static(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of TEI (Terminal Endpoint Identifier) to be "The type of TEI (Terminal Endpoint Identifier)
used for this Terminal Endpoint. In case of dynamic(1), used for this Terminal Endpoint. In case of dynamic(1),
the TEI value will be selected by the switch. In the TEI value is selected by the switch. In
case of static(2), a valid TEI value will have to be case of static(2), a valid TEI value has to be
entered in the isdnTeTeiValue object. entered in the isdnEndpointTeiValue object.
The default value for this object will depend on the The default value for this object depends on the
interface type as well as the Terminal Endpoint type. interface type as well as the Terminal Endpoint type.
On Primary Rate interfaces, the default value will be On Primary Rate interfaces the default value is
static(2). On Basic Rate interfaces, the default value static(2). On Basic Rate interfaces the default value
will be dynamic(1) for isdn(63) Terminal Endpoints and is dynamic(1) for isdn(63) Terminal Endpoints and
static(2) for x25ple(40) Terminal Endpoints." static(2) for x25ple(40) Terminal Endpoints."
::= { isdnEndpointEntry 4 } ::= { isdnEndpointEntry 4 }
isdnEndpointTeiValue OBJECT-TYPE isdnEndpointTeiValue OBJECT-TYPE
SYNTAX INTEGER ( 0..255 ) SYNTAX INTEGER ( 0..255 )
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TEI (Terminal Endpoint Identifier) value "The TEI (Terminal Endpoint Identifier) value
for this Terminal Endpoint. If isdnEndpointTeiType for this Terminal Endpoint. If isdnEndpointTeiType
is set to static(2), valid numbers are 0..63, is set to static(2), valid numbers are 0..63,
while otherwise the value will be set internally. while otherwise the value is set internally.
The default value will be 0 for static TEI values The default value of this object is 0 for static
and selected internally for dynamic TEI values." TEI assignment.
The default value for dynamic TEI assignment is also
0 as long as no TEI has been assigned. After TEI
assignment, the assigned TEI value is returned."
::= { isdnEndpointEntry 5 } ::= { isdnEndpointEntry 5 }
isdnEndpointSpid OBJECT-TYPE isdnEndpointSpid OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Service profile IDentifier (SPID) information "The Service profile IDentifier (SPID) information
for this Terminal Endpoint. for this Terminal Endpoint.
The SPID is composed of 9-20 numeric characters. The SPID is composed of 9-20 numeric characters.
This information has to be defined in addition to This information has to be defined in addition to
the local number for some switch protocol types, the local number for some switch protocol types,
e.g. Bellcore NI-1 and NI-2. e.g. Bellcore NI-1 and NI-2.
If this object is not required, it will be a If this object is not required, it is a
zero length string." zero length string."
REFERENCE REFERENCE
"Bellcore SR-NWT-001953, Generic Guidelines for ISDN "Bellcore SR-NWT-001953, Generic Guidelines for ISDN
Terminal Equipment on Basic Access Interfaces, Terminal Equipment on Basic Access Interfaces,
Chapter 8.5.1." Chapter 8.5.1."
DEFVAL { "" } DEFVAL { "" }
::= { isdnEndpointEntry 6 } ::= { isdnEndpointEntry 6 }
isdnEndpointStatus OBJECT-TYPE isdnEndpointStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
skipping to change at page 37, line 26 skipping to change at page 39, line 28
DESCRIPTION DESCRIPTION
"The index value which uniquely identifies an entry "The index value which uniquely identifies an entry
in the isdnDirectoryTable." in the isdnDirectoryTable."
::= { isdnDirectoryEntry 1 } ::= { isdnDirectoryEntry 1 }
isdnDirectoryNumber OBJECT-TYPE isdnDirectoryNumber OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Directory Number. Directory Numbers will be used "A Directory Number. Directory Numbers are used
to identify incoming calls on the signaling to identify incoming calls on the signaling
channel given in isdnDirectorySigIndex. channel given in isdnDirectorySigIndex.
The format of this information largely depends on the type The format of this information largely depends on the type
of switch or PBX the device is connected to. Therefore, of switch or PBX the device is connected to. Therefore,
the detailed format of this information will not be the detailed format of this information is not
specified and is implementation dependent. specified and is implementation dependent.
If possible, the agent should implement this information If possible, the agent should implement this information
using the E.164 number format. In this case, the number using the E.164 number format. In this case, the number
must start with '+'. Otherwise, IA5 number digits must must start with '+'. Otherwise, IA5 number digits must
be used." be used."
REFERENCE REFERENCE
"ITU-T E.164, Q.931 chapter 4.5.10" "ITU-T E.164, Q.931 chapter 4.5.10"
::= { isdnDirectoryEntry 2 } ::= { isdnDirectoryEntry 2 }
isdnDirectorySigIndex OBJECT-TYPE isdnDirectorySigIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index pointing to an ISDN signaling channel. "An index pointing to an ISDN signaling channel.
Incoming calls will be accepted on this Incoming calls are accepted on this
signaling channel if the isdnDirectoryNumber is signaling channel if the isdnDirectoryNumber is
presented as Called Number in the SETUP message." presented as Called Number in the SETUP message."
::= { isdnDirectoryEntry 3 } ::= { isdnDirectoryEntry 3 }
isdnDirectoryStatus OBJECT-TYPE isdnDirectoryStatus 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
skipping to change at page 38, line 34 skipping to change at page 40, line 38
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap/inform is sent to the manager under the "This trap/inform is sent to the manager under the
following condidions: following condidions:
- on incoming calls for each call which is rejected for - on incoming calls for each call which is rejected for
policy reasons (e.g. unknown neighbor or access policy reasons (e.g. unknown neighbor or access
violation) violation)
- on outgoing calls whenever a call attempt is determined - on outgoing calls whenever a call attempt is determined
to have ultimately failed. In the event that call retry to have ultimately failed. In the event that call retry
is active, then this is after all retry attempts have is active, then this will be after all retry attempts
failed. have failed.
- whenever a call connects. In this case, the object - whenever a call connects. In this case, the object
isdnBearerCallConnectTime should be included in the isdnBearerCallConnectTime should be included in the
trap. trap.
Only one such trap is sent in between successful or Only one such trap is sent in between successful or
unsuccessful call attempts from or to a single neighbor; unsuccessful call attempts from or to a single neighbor;
subsequent call attempts result in no trap. subsequent call attempts result in no trap.
If the Dial Control MIB objects dialCtlNbrCfgId and If the Dial Control MIB objects dialCtlNbrCfgId and
dialCtlNbrCfgIndex are known by the entity generating dialCtlNbrCfgIndex are known by the entity generating
skipping to change at page 42, line 12 skipping to change at page 44, line 12
END END
5. Acknowledgments 5. Acknowledgments
This document was produced by the ISDN MIB Working Group. Special This document was produced by the ISDN MIB Working Group. Special
thanks is due to the following persons: thanks is due to the following persons:
Ed Alcoff Ed Alcoff
Fred Baker Fred Baker
Scott Bradner
Bibek A. Das Bibek A. Das
Maria Greene Maria Greene
Ken Grigg Ken Grigg
Stefan Hochuli Stefan Hochuli
Jeffrey T. Johnson Jeffrey T. Johnson
Glenn Kime Glenn Kime
Oliver Korfmacher Oliver Korfmacher
Kedar Madineni Kedar Madineni
Bill Miskovetz Bill Miskovetz
Mike O'Dowd Mike O'Dowd
skipping to change at page 43, line 40 skipping to change at page 45, line 40
Interface Types", RFCxxxx, Newbridge Networks, February 1996. Interface Types", RFCxxxx, Newbridge Networks, February 1996.
[13] D. Fowler, "Definitions of Managed Objects for the DS0 and [13] D. Fowler, "Definitions of Managed Objects for the DS0 and
DS0Bundle Interface Types", RFCxxxx, Newbridge Networks, February DS0Bundle Interface Types", RFCxxxx, Newbridge Networks, February
1996. 1996.
[14] ITU-T Recommendation "Integrated Services Digital Network (ISDN) [14] ITU-T Recommendation "Integrated Services Digital Network (ISDN)
General Structure and Service Capabilities - Closed User Group", General Structure and Service Capabilities - Closed User Group",
Rec. I.255.1. Rec. I.255.1.
[15] G. Roeck, "Dial Control Management Information Base", RFCxxxx,
cisco Systems, June 1996.
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 cisco Systems
Killisfeldstrasse 64 170 West Tasman Drive
76227 Karlsruhe, Germany San Jose, CA 95134
U.S.A.
Phone: +49 721 9495 0
Email: roeck@conware.de
Table of Contents
1 The SNMPv2 Network Management Framework ......................... 2 Phone: +1 408 527 3143
2 Object Definitions .............................................. 2 Email: groeck@cisco.com
3 Overview ........................................................ 3
3.1 Structure of the MIB .......................................... 3
3.1.1 General Description ......................................... 3
3.2 Relationship to RFC 1573 ...................................... 4
3.2.1 Layering Model .............................................. 4
3.2.2 ifTestTable ................................................. 7
3.2.3 ifRcvAddressTable ........................................... 7
3.2.4 ifEntry ..................................................... 7
3.2.4.1 ifEntry for a Basic Rate hardware interface ............... 7
3.2.4.2 ifEntry for a B channel ................................... 8
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 .................................... 13
3.3.1 Relationship to the DS1/E1 MIB .............................. 13
3.3.2 Relationship to the DS0 and DS0Bundle MIBs .................. 13
3.3.3 Relationship to the Dial Control MIB ........................ 14
3.4 ISDN interface specific information ........................... 14
3.4.1 ISDN leased lines ........................................... 14
3.4.2 Hyperchannels ............................................... 14
3.4.3 D channel backup and NFAS trunks ............................ 14
3.4.4 X.25 based packet-mode service in B and D channels .......... 15
3.4.5 SPID handling ............................................... 15
3.4.6 Closed User Groups .......................................... 16
3.4.7 Provision of point-to-point line topology ................... 16
3.4.8 Speech and audio bearer capability information elements ..... 17
4 Definitions ..................................................... 18
5 Acknowledgments ................................................. 42
6 References ...................................................... 42
7 Security Considerations ......................................... 43
8 Author's Address ................................................ 43
 End of changes. 137 change blocks. 
260 lines changed or deleted 379 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/