CADANT-TRAP-LOG-MIB: View SNMP OID List / Download MIB

This MIB defines objects which are used to control and report on Cadant proprietary event notificaton (trap) and logging operation.

If this value is set to true, then all Cadant proprietary log entries are enabled. Otherwise, the syslog logs will consist only of standard logs entries.

The maximum size of the local log, in number of entries. The local log is only what is put into the docsDevEventTable.

The maximum size of the log history, in number of entries. This log contains both Cadant prioprietary and DOCSIS notifications.

The syslog logging facility. Enumeration: 'local5': 5, 'local4': 4, 'local7': 7, 'local6': 6, 'local1': 1, 'local0': 0, 'local3': 3, 'local2': 2.

Controls the generation of SNMP traps regarding to CM status change. A cleared bit indicates that a trap must be generated if a CM resets while in the corresponding state. If resetRanging(0) is clear, a CM reset while in the ranging state will generate a cmResetNotification trap. If resetProvisioning(1) is clear, a CM reset while in the rangingComplete or ipComplete states will generate a cmResetNotification trap. If resetRegistered(2) is clear, a CM reset while in the registrationComplete state will generate a cmResetNotification trap. If resetClear(3) is clear, a on-line CM from previous flap will generate a cmResetClearNotification trap. If registered(4) is clear, a registered CM will generate a cmRegistrationNotification trap. Bits: 'resetRanging': 0, 'resetClear': 3, 'registered': 4, 'resetRegistered': 2, 'resetProvisioning': 1.

This table allows control of the reporting of event classes. For each event priority, a combination of logging and reporting mechanisms may be chosen.

Allows configuration of the reporting mechanisms for a particular event priority.

Currently, only the console destination is persistent in SNMP. Transient sessions, such as telnet, are not configurable via the MIB. Those are configurable only via CLI. Bits: 'console': 0.

This table allows the event priority to be overridden. Each entry indicates an override condition for the given event.

Allows configuration of the event priority overrides.

Uniquely identifies the type of event that is reported by this entry.

Indicates the current override state of the event. admit allows the event to be generated and inhibit prevents the event from being generated regardless of the priority is enabled for the event. Setting the priority allows the event to generated with the desired priority. Enumeration: 'priority': 3, 'admit': 1, 'inhibit': 2.

This variable indicates the status of the entry. Valid values for a set include createAndGo(4) and destroy(6).

This field is only valid when the override state is set to priority and indicates the priority level that should be used when this notification is generated. Enumeration: 'information': 7, 'notice': 6, 'emergency': 1, 'invalid': 0, 'alert': 2, 'critical': 3, 'error': 4, 'debug': 8, 'warning': 5.

This table stores syslog server information when there is more than one syslog server configured.

Syslog server information.

IP address of the syslog server.

Facility associated with the syslog server. Enumeration: 'local5': 5, 'local4': 4, 'local7': 7, 'local6': 6, 'local1': 1, 'local0': 0, 'local3': 3, 'local2': 2.

This variable displays the status of the entry.

This table is used to configure the logging level for each of the CLI authorization levels.

Syslog server information.

A CLI authorization level.

The logging level that all commands assigned to this authorization level will be output at when executed. Enumeration: 'information': 7, 'notice': 6, 'emergency': 1, 'alert': 2, 'critical': 3, 'error': 4, 'debug': 8, 'warning': 5.

Compliance statement for entities implementing the CADANT-TRAP-LOG-MIB

Global trap and logging objects

Trap and log event control objects

Syslog control objects

CLI authorization to log level mapping control objects