7-150
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 7 Cisco Management Information Base
CISCO-SYSLOG-MIB
::= { ciscoSyslogMIBNotifications 1 }
Conformance Information
ciscoSyslogMIBConformance OBJECT IDENTIFIER ::= { ciscoSyslogMIB 3 }
ciscoSyslogMIBCompliances OBJECT IDENTIFIER ::= { ciscoSyslogMIBConformance 1 }
ciscoSyslogMIBGroups OBJECT IDENTIFIER ::= { ciscoSyslogMIBConformance 2 }
Compliance Statements
ciscoSyslogMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
The compliance statement for entities which implement the Cisco syslog MIB.
MANDATORY-GROUPS { ciscoSyslogMIBGroup }
::= { ciscoSyslogMIBCompliances 1 }
Units of Conformance
ciscoSyslogMIBGroup OBJECT-GROUP
OBJECTS { clogNotificationsSent, clogNotificationsEnabled, clogMaxSeverity, clogMsgIgnores,
clogMsgDrops, clogHistTableMaxLength, clogHistMsgsFlushed, clogHistFacility,
clogHistSeverity, clogHistMsgName, clogHistMsgText, clogHistTimestamp }
STATUS current
DESCRIPTION
A collection of objects providing the syslog MIB capability.
::= { ciscoSyslogMIBGroups 1 }
Troubleshooting
Syslog has standard buffer size while generating a SNMP trap message; the data is trimmed to the
specified field size (255). This avoids any errors caused by data that is too large for the field. For
example, if you have specified the message text field to be 255 bytes, but a message arrives that is 300
bytes, the data will be truncated to 255 bytes before being logged.
Trap Configuration
To configure the traps, set clogsNotificationEnabled (1.3.6.1.4.1.9.9.41.1.1.2) to TRUE(1) by using
SNMP set operation in any SNMP management application. Set the severity using clogMaxSeverity
(1.3.6.1.4.1.9.9.41.1.1.3) by using any SNMP management application. This object indicates the syslog
severity level that needs to be processed. Any syslog message with a severity value greater than this value
will be ignored by the agent. Severity numeric values increase as their severity decreases.
To Next Page
Loading...
Need help?
General