All MIBs › TELDAT-TRAP-CNSL-MIB
Organization: Teldat, S.A.
Last Updated: 2014-01-20
Category: Teldat Router Management, Teldat Trap Notifications
Description: Defines Teldat router CNSL (console) event trap notifications.
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 TELDAT-TRAP-CNSL-MIB?
TELDAT-TRAP-CNSL-MIB is a Teldat, S.A. vendor-specific MIB that defines the SNMP notification objects generated by the CNSL (console/command-line) event subsystem on Teldat routers, tracking administrative command execution across the router's common, configuration, and running-configuration command processes. It models four CNSL events (cnslEventObjects1 through 4) — a common command executed from any process (cnsl1-executed-command), a command executed from the config process (cnsl2-executed-command), a command executed from the running-config process (cnsl3-executed-command), and a command execution error of a given type (cnsl4-error-type) — each paired with the acting cnsl*-user-name. Being trap-only, its monitoring value comes entirely from correlating the resulting notifications (cnslNotification1 through 4) against expected administrative activity, useful for auditing who changed configuration and when, or for catching command-execution errors that might indicate a scripting or automation fault. It depends on the base TELDAT-MIB for its telEventTraps registration point and is deployed on Teldat routers wherever command-level audit logging via SNMP trap is desired, and administrators can download the TELDAT-TRAP-CNSL-MIB file to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-CNSL-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
- Teldat routers
Monitoring Examples
An operator's trap receiver logs every cnslNotification2 (config-process command) with its cnsl2-user-name and cnsl2-executed-command; a cnslNotification4 error event immediately following, tied to the same user, would indicate that user's configuration command failed and needs review.
What Can Be Monitored
- common command execution events (any process)
- config-process command execution events
- running-config command execution events
- command execution error events
- acting user name per command event
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString |
From TELDAT-MIB
| telEventTraps | OBJECT-IDENTITY |
OIDs
RFC description
Manages SNMP notifications and traps generated by CNSL event subsystems on Teldat network devices.
Start monitoring Teldat routers (console/CLI command-execution audit event traps) 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.