All MIBs › CADANT-TRAP-LOG-MIB
Organization: Arris International, Inc.
Last Updated: 2006-04-20
Category: Alarm and Event Management, DOCSIS and Cable, Vendor: ARRIS
Description: Manages SNMP trap logging, trap destination configuration, and trap history on ARRIS/Cadant CMTS platforms.
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 CADANT-TRAP-LOG-MIB?
CADANT-TRAP-LOG-MIB is an ARRIS/Cadant enterprise MIB that controls and reports on proprietary SNMP trap generation and event logging on Cadant/ARRIS CMTS equipment. It exposes global settings for enabling proprietary logging, local log and history buffer sizes, syslog facility selection, per-modem trap inhibiting, and tables for controlling and overriding the reporting/severity state of individual events. Its role is squarely fault/event monitoring for the device's software, letting an operator see which event classes are enabled for trap generation or logging, adjust logging capacity, and confirm syslog integration is configured as expected. It complements, and can duplicate control of, the standard event/notification-log MIBs typical of SNMP agents. It is deployed on ARRIS/Cadant CMTS headend equipment as the central point for tuning trap and logging behavior across the chassis. Engineers can download the CADANT-TRAP-LOG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CADANT-TRAP-LOG-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
- Arris/Cadant C4 CMTS cable modem termination system
Monitoring Examples
An operator would check cadLocalLogSize and cadLogHistorySize to confirm the CMTS retains enough event history for post-incident diagnosis, and cadSyslogFacility to verify events are being forwarded to the correct syslog facility. Reviewing cadEvControlTable/cadEvControlEntry for cadEvReporting per event, together with any active entries in cadEvOverrideTable (cadEvOvrdEvId, cadEvOvrdState), shows whether specific event types have been suppressed or overridden, which could explain missing alerts. Checking cadCmTrapInhibit helps confirm whether per-modem trap suppression is masking legitimate cable-modem fault notifications.
What Can Be Monitored
- local log/history buffer size
- syslog facility configuration
- per-event trap reporting state
- event override/suppression state
- per-modem trap inhibit status
Imported Objects
From CADANT-PRODUCTS-MIB
| cadNotification | OBJECT-IDENTITY |
From CADANT-TC
| InetAddressIPv4or6 |
| docsDevEvControlEntry | OBJECT-TYPE |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| RowStatus | |
| TruthValue |
OIDs
RFC description
Event notification, trap logging, and syslog configuration for Cadant/Arris cable modem access devices.
Start monitoring Arris/Cadant C4 CMTS 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.