All MIBs › OPCD-SUPPORT-MIB-V2
Organization: Opencode Systems
Last Updated: 2007-03-06
Category: VoIP/Telephony
Description: Supplies diagnostic and general system support objects for SNMP management of the OpenCode VoIP/IVR platform.
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 OPCD-SUPPORT-MIB-V2?
OPCD-SUPPORT-MIB-V2 is a private enterprise MIB from OpenCode Communications supporting general system diagnostics and alarm reporting for its VoIP/IVR call-processing platform. Its objects are organized around a support/trap framework (ocsupport, ocsupport-traps) with associated definitions and vars subtrees that supply the variable bindings carried in notifications. Its primary monitoring value is software/service fault visibility: objects such as mcr-Host, mcr-Severity, and mcr-Text are designed to identify which host raised a condition, how severe it is, and a descriptive message, letting an operator distinguish routine informational events from critical platform failures. It is a vendor-specific module built on standard SNMPv2 notification conventions (NOTIFICATION-TYPE) rather than depending on other functional MIBs. It is deployed on OpenCode VoIP/IVR media and call-processing servers where operations staff monitor for alarm conditions signaling degraded call handling or service faults. Locating the specific OPCD-SUPPORT-MIB-V2 OID for mcr-Severity is typically the starting point when configuring trap-based alerting thresholds for this platform.
IPNetwork Monitor allows you to monitor SNMP objects defined in OPCD-SUPPORT-MIB-V2. 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
- OpenCode VoIP/IVR platform servers
- media/call-processing servers
Monitoring Examples
The ocsupport-traps notifications are expected to carry mcr-Host, mcr-Severity, and mcr-Text varbindings, so an operator receiving such a trap can immediately see which host raised it, its severity level, and a human-readable description of the fault. A trap reporting high severity from a specific mcr-Host would prompt investigation into that host's call-processing service, while the definitions/vars subtrees hold the supporting object definitions that populate those varbinds.
What Can Be Monitored
- alarm/trap severity
- alarm source host
- alarm descriptive text
- platform fault/service events
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| enterprises |
From SNMPv2-TC
| DisplayString |
OIDs
RFC description
Provides general system support and diagnostic objects for OpenCode VoIP/IVR platform SNMP management.
Start monitoring OpenCode VoIP/IVR platform servers (system diagnostics/alarm trap framework) 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.