All MIBs › BW-CallDetailServerFault
Organization: Broadsoft, Inc
Last Updated: 2002-01-22
Category: Alarm and Event Management, Telephony and VoIP, Vendor: BroadSoft
Description: Defines fault trap notifications for BroadSoft BroadWorks call detail record server failures.
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 BW-CallDetailServerFault?
BW-CallDetailServerFault is a BroadSoft-specific MIB that defines SNMP trap notifications for the Call Detail Server component of the BroadWorks softswitch/VoIP platform, rather than exposing pollable counters or tables of its own. Its notifications — bwPMCallDetailServerLaunched, bwPMCallDetailServerShutDown, bwPMCallDetailServerRestarted, and bwPMCallDetailServerDeath — report the Call Detail Server process lifecycle, while bwNetworkServerRequestError, bwCAPSCallCenterLinkDown, and bwOCIReportingLinkDown report failures in related network-server requests, CAPS call-center links, and OCI reporting links; each notification carries common BroadWorks fault fields (identifier, timeStamp, alarmName, systemName, severity, component, subcomponent, problemText, recommendedActionsText) imported from BroadworksFault. Because it is purely a fault/trap definitions module, its monitoring value comes entirely from receiving and correlating these traps in an NMS — a bwPMCallDetailServerDeath or bwPMCallDetailServerShutDown trap without a corresponding planned-maintenance window would flag a call-detail-record outage that could cause billing/CDR data loss. It depends on the shared BroadworksFault module for its common notification varbinds and is deployed on BroadSoft BroadWorks application-server clusters running the Call Detail Server component; NMS teams that need BW-CallDetailServerFault SNMP monitoring configure their trap receivers against these specific OIDs to catch CDR pipeline failures early.
IPNetwork Monitor allows you to monitor SNMP objects defined in BW-CallDetailServerFault. 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
- BroadSoft BroadWorks application server (Call Detail Server component)
Monitoring Examples
An NMS receives a bwPMCallDetailServerDeath trap with its problemText and severity varbinds populated; combined with the absence of a preceding bwPMCallDetailServerShutDown trap, this indicates an unplanned crash of the Call Detail Server that operators should treat as a billing-data-at-risk event.
What Can Be Monitored
- Call Detail Server process launch/shutdown/restart/death events
- network server request errors
- CAPS call-center link down events
- OCI reporting link down events
- fault severity and component/subcomponent identification
Imported Objects
From BroadworksFault
| alarmName | OBJECT-TYPE |
| alarmState | OBJECT-TYPE |
| common | OBJECT-IDENTITY |
| component | OBJECT-TYPE |
| faultFields | OBJECT-IDENTITY |
| identifier | OBJECT-TYPE |
| problemText | OBJECT-TYPE |
| recommendedActionsText | OBJECT-TYPE |
| severity | OBJECT-TYPE |
| subcomponent | OBJECT-TYPE |
| systemName | OBJECT-TYPE |
| timeStamp | OBJECT-TYPE |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE |
OIDs
RFC description
Reports fault and alarm notifications for BroadWorks call detail server system events.
Start monitoring BroadSoft BroadWorks VoIP/UC application servers 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.