CISCO-ISDN-MIB

All MIBs › CISCO-ISDN-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2001-02-09

Category: Cisco Devices, Network Interfaces, Telephony and VoIP

Description: Monitors the status of ISDN interfaces on Cisco routers, providing call information and B-channel utilization data.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-ISDN-MIB with a free 30-day trial of IPNetwork Monitor.

What Is CISCO-ISDN-MIB?

CISCO-ISDN-MIB monitors ISDN interfaces and dial-on-demand routing (DDR) call state on Cisco routers equipped with ISDN BRI/PRI interfaces. It exposes a demand-neighbor table tracking each configured dial-on-demand number, including the physical and logical interface used, the dialed address, permission/dial-out settings, call duration, and the reason/code for the last call clearance. This is directly a call/session-status MIB: it reports call duration against configured maximums and the clear reason/code for the most recent call, letting an operator diagnose whether calls are failing, being clipped by idle-timeout, or exceeding cost-control duration limits, functioning much like process/job status monitoring but for dial calls. It relies on the underlying ISDN B-channel and physical interface indices from IF-MIB. It is deployed on Cisco routers using ISDN BRI/PRI for backup WAN links or dial-on-demand routing to remote sites. Engineers can download the CISCO-ISDN-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ISDN-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco routers with ISDN BRI/PRI interfaces

Monitoring Examples

demandNbrTable/demandNbrEntry tracks each demandNbrId with its demandNbrPhysIf/demandNbrLogIf, the demandNbrAddress dialed, and the outcome of the most recent call via demandNbrClearReason and demandNbrClearCode. An operator would poll demandNbrLastDuration against demandNbrMaxDuration to catch calls running long and risking toll cost overrun, and a repeated abnormal demandNbrClearCode across many entries would indicate a failing ISDN line or provisioning problem rather than normal call teardown.

What Can Be Monitored

ISDN call duration
last call clear reason/code
dial-on-demand neighbor configuration
dialed address per demand entry

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From IF-MIB

ifIndex

OBJECT-TYPE

From ISDN-MIB

isdnLapdOperStatus	OBJECT-TYPE
isdnSignalingIfIndex	OBJECT-TYPE
isdnSignalingIndex	OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus
TimeStamp

How to Use in IPNetwork Monitor

Example using demandNbrFailCalls OID:

Select a Cisco routers with ISDN BRI/PRI interface as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type demandNbrFailCalls into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of call attempts that have failed. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoIsdnMib	1.3.6.1.4.1.9.9.26			The MIB module to describe the status of the ISDN Interfaces on the routers.
ciscoIsdnMibObjects	1.3.6.1.4.1.9.9.26.1
isdnNeighbor	1.3.6.1.4.1.9.9.26.1.1
demandNbrTable	1.3.6.1.4.1.9.9.26.1.1.1		not-accessible	The list of neighbors from which the router will accept calls or to which it will place them.
demandNbrEntry	1.3.6.1.4.1.9.9.26.1.1.1.1		not-accessible	A single Neighbor. This entry is effectively permanent, and contains information describing the neighbor, his permissions, his last call attempt, and his cumulative effects.
I32 demandNbrPhysIf	1.3.6.1.4.1.9.9.26.1.1.1.1.1	Integer32	not-accessible	ifIndex value of the physical interface the neighbor will be called on. On an ISDN interface, this is the ifIndex value of the D channel.
I32 demandNbrId	1.3.6.1.4.1.9.9.26.1.1.1.1.2	Integer32	not-accessible	arbitrary sequence number associated with the neighbor.
I32 demandNbrLogIf	1.3.6.1.4.1.9.9.26.1.1.1.1.3	Integer32	read-create	ifIndex value of virtual interface associated with the neighbor. This interface maintains a queue of messages holding for the neighbor awaiting call completion, and all statistics.
STR demandNbrName	1.3.6.1.4.1.9.9.26.1.1.1.1.4	DisplayString	read-create	ASCII name of the neighbor.
STR demandNbrAddress	1.3.6.1.4.1.9.9.26.1.1.1.1.5	DisplayString	read-create	Call Address at which the neighbor should be called. Think of this as the set of characters following 'ATDT ' or the 'phone number' included in a D channel call request.
INT demandNbrPermission	1.3.6.1.4.1.9.9.26.1.1.1.1.6	INTEGER	read-create	applicable permissions.
I32 demandNbrMaxDuration	1.3.6.1.4.1.9.9.26.1.1.1.1.7	Integer32	read-create	Maximum call duration in seconds.
I32 demandNbrLastDuration	1.3.6.1.4.1.9.9.26.1.1.1.1.8	Integer32	read-only	Duration of last call in seconds.
STR demandNbrClearReason	1.3.6.1.4.1.9.9.26.1.1.1.1.9	DisplayString	read-only	ASCII reason that the last call terminated.
OCT demandNbrClearCode	1.3.6.1.4.1.9.9.26.1.1.1.1.10	OCTET STRING	read-only	encoded reason for the last call tear down.
C32 demandNbrSuccessCalls	1.3.6.1.4.1.9.9.26.1.1.1.1.11	Counter32	read-only	number of completed calls to neighbor since system reset.
C32 demandNbrFailCallsEx	1.3.6.1.4.1.9.9.26.1.1.1.1.12	Counter32	read-only	Number of call attempts that have failed.
C32 demandNbrAcceptCalls	1.3.6.1.4.1.9.9.26.1.1.1.1.13	Counter32	read-only	Number of calls accepted from the neighbor.
C32 demandNbrRefuseCalls	1.3.6.1.4.1.9.9.26.1.1.1.1.14	Counter32	read-only	Number of calls from neighbor that we have refused.
TIM demandNbrLastAttemptTime	1.3.6.1.4.1.9.9.26.1.1.1.1.15	TimeStamp	read-only	sysUpTime of last call attempt.
ROW demandNbrStatus	1.3.6.1.4.1.9.9.26.1.1.1.1.16	RowStatus	read-create	Somebody might want to manage the device using SNMP some day...
INT demandNbrCallOrigin	1.3.6.1.4.1.9.9.26.1.1.1.1.17	INTEGER	read-only	Indication of outgoing or incoming call.
ciscoIsdnMibTrapPrefix	1.3.6.1.4.1.9.9.26.2
ciscoIsdnMibTraps	1.3.6.1.4.1.9.9.26.2.0
NTF demandNbrCallInformation	1.3.6.1.4.1.9.9.26.2.0.1			This trap/inform is sent to the manager whenever a successful call clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then this is after all retry attempts have failed. However, only one such trap is sent in between successful call attempts; subsequent call attempts result in no trap.
NTF demandNbrCallDetails	1.3.6.1.4.1.9.9.26.2.0.2			This trap/inform is sent to the manager whenever a call connects, or clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then this is after all retry attempts have failed. However, only one such trap is sent in between successful call attempts; subsequent call attempts result in no trap. Whenever a call connects, demandNbrLastDuration, demandNbrClearReason, and demandNbrClearCode objects are not included in the trap.
NTF demandNbrLayer2Change	1.3.6.1.4.1.9.9.26.2.0.3			This trap/inform is sent to the manager whenever the D-channel of an interface changes state.
NTF demandNbrCNANotification	1.3.6.1.4.1.9.9.26.2.0.4			This trap/inform is sent to the manager whenever the an incoming call request is rejected with cause 'requested circuit/channel not available' (CNA), code number 44. isdnSignalingIfIndex is the ifIndex value of the interface associated with this signaling channel. ifIndex is the interface index of the requested bearer channel
ciscoIsdnMibConformance	1.3.6.1.4.1.9.9.26.3
ciscoIsdnMibCompliances	1.3.6.1.4.1.9.9.26.3.1
ciscoIsdnMibCompliance	1.3.6.1.4.1.9.9.26.3.1.1			The compliance statement for entities which implement the Cisco ISDN MIB
ciscoIsdnMibComplianceRev1	1.3.6.1.4.1.9.9.26.3.1.2			The compliance statement for entities which implement the Cisco ISDN MIB
ciscoIsdnMibGroups	1.3.6.1.4.1.9.9.26.3.2
ciscoIsdnMibGroup	1.3.6.1.4.1.9.9.26.3.2.1			A collection of objects providing the ISDN MIB capability.
ciscoIsdnMibGroupRev1	1.3.6.1.4.1.9.9.26.3.2.2			A collection of objects providing the call origin capability.

RFC description

Cisco vendor MIB managing ISDN interfaces, call statistics, and voice gateway operations.

Start monitoring Cisco routers with ISDN BRI/PRI interfaces with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-ISDN-MIB