2002-02-12
This MIB module extends the Cisco Syslog MIB and provides network management support to handle and process Syslog messages as device events.
Download CISCO-SYSLOG-EVENT-EXT-MIB.txt Open CISCO-SYSLOG-EVENT-EXT-MIB.txt in a new tab
| Name | OID |
|---|---|
| cslogEventDispositionTable | 1.3.6.1.4.1.9.9.270.1.1.5 |
END OF TOC
1.3.6.1.4.1.9.9.270.1.1.1
INTEGER1 = noDisplay2 = sparseDetail3 = normalDetail4 = verboseDetail5 = exhaustiveDetail · Integer32
This object defines the detail level at which Syslog messages are displayed on the console or HTML user interface. Detail level classifications are: noDisplay(1) - No display at all. sparseDetail(2) - Minimum detail. normalDetail(3) - General detail. verboseDetail(4) - Verbose detail. exhaustiveDetail(5) - Full detail.
1.3.6.1.4.1.9.9.270.1.1.2
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0. 'emergency' : system is unusable 'alert' : action must be taken immediately 'critical' : critical conditions 'error' : error conditions 'warning' : warning conditions 'notice' : normal but significant condition 'informational': informational messages 'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
This object indicates which syslog severity level messages can be displayed on the console. A high severity value implies a low severity. If the display bit on the object cslogEventDisposition is set for this severity, all messages have severity values less than or equal to clogMaxSeverity and this object will be displayed on the console.
1.3.6.1.4.1.9.9.270.1.1.3
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0. 'emergency' : system is unusable 'alert' : action must be taken immediately 'critical' : critical conditions 'error' : error conditions 'warning' : warning conditions 'notice' : normal but significant condition 'informational': informational messages 'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
This object indicates which syslog severity level messages can be displayed on the event log GUI. A high severity value implies a low severity. If the display bit on the object cslogEventDisposition is set for this severity, all messages have severity values less than or equal to clogMaxSeverity and this object will be displayed on the event log GUI web pages.
1.3.6.1.4.1.9.9.270.1.1.4
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0. 'emergency' : system is unusable 'alert' : action must be taken immediately 'critical' : critical conditions 'error' : error conditions 'warning' : warning conditions 'notice' : normal but significant condition 'informational': informational messages 'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
This object indicates which syslog severity level messages can be displayed on the HTML event log console. A high severity value implies a low severity. If the display bit on the object cslogEventDisposition is set for this severity, all messages have severity values less than or equal to clogMaxSeverity and this object will be displayed on the GUI browser console page.
1.3.6.1.4.1.9.9.270.1.1.5
Index: cslogEventDispositionSeverity
This table contains parameters to configure Syslog message disposition mechanisms and keep message counts.
1.3.6.1.4.1.9.9.270.1.1.5.1.1
SyslogSeverity1 = emergency2 = alert3 = critical4 = error5 = warning6 = notice7 = info8 = debugThe severity of a syslog message. The enumeration values are equal to the values that syslog uses + 1. For example, with syslog, emergency=0. 'emergency' : system is unusable 'alert' : action must be taken immediately 'critical' : critical conditions 'error' : error conditions 'warning' : warning conditions 'notice' : normal but significant condition 'informational': informational messages 'debug' : debug-level messages.Reference: RFC 3164, Section 4.1 - syslog Message Parts · Integer32
This object defines the Syslog serverity.
1.3.6.1.4.1.9.9.270.1.1.5.1.2
CslogEventDispositionThis definition specifies the manner in which a Syslog message should be handled by the system as a device event. Events are first recorded by the Syslog subsystem, and then they can be counted, displayed on the console, or forward to external device. The four disposition mechanisms are: none(0) - Record only, no further handling. count(1) - All Syslog messages received after this bit is set will be counted according to their corresponding event types. display(2) - All Syslog messages received after this bit is set will be displayed on the device console, HTML console or WEB pages (pending on severity level configuration of each display types). notify(3) - All Syslog messages received after this bit is set will cause notification to be sent. · BITS
This object defines the disposition method for Syslog messages of a specific severity.
1.3.6.1.4.1.9.9.270.1.1.5.1.3
Counter32
This is the number of Syslog messages of a specific severity.