All MIBs › SIP-DS2-MIB
Organization: Lucent Technologies
Last Updated: 240701
Category: ATM and Frame Relay, SIP and VoIP Protocol
Description: Manages Lucent SIP-over-DS2 interface configuration and SMDS high-speed subscriber access.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.
What Is SIP-DS2-MIB?
SIP-DS2-MIB is a vendor-specific MIB from Lucent Technologies registered under the softSwitch/sipDeviceServer branch of the Lucent enterprise tree; despite its name, the source module does not define DS2 interface or SMDS subscriber-access objects — it is a small, generically templated MIB (its own MODULE-IDENTITY DESCRIPTION is literally left as placeholder text) exposing basic SIP device-server identity and call-activity counters. It defines dsInfo and dsProtocolInfo (device/stack version identification), logLevel (error/warning/info verbosity control), succeededCalls, activeCalls, and failedCalls scalar counters, plus reloadConfig and resetLog action objects. This narrow set of counters is useful for basic health checks of a SIP softswitch device server — confirming it is reachable, running an expected stack version, and processing calls without an abnormal failure rate. It has no table structures or dependent MIBs beyond standard SNMPv2-SMI/SNMPv2-TC imports, and is deployed alongside Lucent softswitch/device-server platforms; administrators can download the SIP-DS2-MIB file to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in SIP-DS2-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
- Lucent Technologies SIP device server / softswitch platform
Monitoring Examples
An operator polls succeededCalls, activeCalls, and failedCalls at intervals to compute a call failure rate for the device server; a sharp rise in failedCalls relative to succeededCalls, especially alongside an unexpected logLevel change, would flag a SIP signaling or stack-level problem worth investigating via dsProtocolInfo.
What Can Be Monitored
- device/stack version identification
- log verbosity level
- succeeded/active/failed call counters
- config reload trigger
- log reset trigger
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| Counter | |
| enterprises |
From RFC1213-MIB
| DisplayString |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| ObjectName | |
| snmpModules |
From SNMPv2-TC
| RowStatus | |
| TestAndIncr | |
| TimeStamp | |
| TruthValue |
OIDs
RFC description
The MIB module for SIP Device Server entities in Lucent soft-switch systems.
Start monitoring Lucent Technologies SIP device server / softswitch platform (call-activity counters/version identification) 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.