Home/Catalog/CISCO-SYSLOG-MIB

CISCO-SYSLOG-MIB

AI MIB Summary

The CISCO-SYSLOG-MIB enables the monitoring and retrieval of system event messages and log entries generated by Cisco IOS and compatible operating systems via SNMP. This module facilitates the collection of critical operational data, including system state changes, error conditions, and administrative actions, for centralized logging and troubleshooting.

The MIB module to describe and store the system messages generated by the IOS and any other OS which supports syslogs.
Main OID:
ciscoSyslogMIB.1.3.6.1.4.1.9.9.41
34
Objects
Active
Status
6
Dependencies

Imported Objects

Objects

34 total
Object Name
ciscoSyslogMIB
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.41
ciscoSyslogMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.1
clogBasic
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.1.1
clogNotificationsSentro
Counter32 UNITS "notifications"
.1.3.6.1.4.1.9.9.41.1.1.1
clogNotificationsEnabledrw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.41.1.1.2
clogMaxSeverityrw
SyslogSeverity
.1.3.6.1.4.1.9.9.41.1.1.3
clogMsgIgnoresro
Counter32 UNITS "messages"
.1.3.6.1.4.1.9.9.41.1.1.4
clogMsgDropsro
Counter32 UNITS "messages"
.1.3.6.1.4.1.9.9.41.1.1.5
clogOriginIDTyperw
Enumeration
.1.3.6.1.4.1.9.9.41.1.1.6
clogOriginIDrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.41.1.1.7
clogHistory
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.1.2
clogHistTableMaxLengthrw
Integer32
.1.3.6.1.4.1.9.9.41.1.2.1
clogHistMsgsFlushedro
Counter32 UNITS "messages"
.1.3.6.1.4.1.9.9.41.1.2.2
clogHistoryTable
SEQUENCE OF ClogHistoryEntry
.1.3.6.1.4.1.9.9.41.1.2.3
clogHistoryEntry
ClogHistoryEntry
.1.3.6.1.4.1.9.9.41.1.2.3.1
clogHistIndex
Integer32
.1.3.6.1.4.1.9.9.41.1.2.3.1.1
clogHistFacilityro
DisplayString
.1.3.6.1.4.1.9.9.41.1.2.3.1.2
clogHistSeverityro
SyslogSeverity
.1.3.6.1.4.1.9.9.41.1.2.3.1.3
clogHistMsgNamero
DisplayString
.1.3.6.1.4.1.9.9.41.1.2.3.1.4
clogHistMsgTextro
DisplayString
.1.3.6.1.4.1.9.9.41.1.2.3.1.5
clogHistTimestampro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.9.9.41.1.2.3.1.6
clogServer
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.1.3
clogMaxServersro
Unsigned32
.1.3.6.1.4.1.9.9.41.1.3.1
clogServerConfigTable
SEQUENCE OF ClogServerConfigEntry
.1.3.6.1.4.1.9.9.41.1.3.2
clogServerConfigEntry
ClogServerConfigEntry
.1.3.6.1.4.1.9.9.41.1.3.2.1
clogServerAddrType
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.41.1.3.2.1.1
clogServerAddr
InetAddress
.1.3.6.1.4.1.9.9.41.1.3.2.1.2
clogServerStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.41.1.3.2.1.3
ciscoSyslogMIBNotificationPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.2
ciscoSyslogMIBNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.2.0
clogMessageGenerated
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.41.2.0.1
ciscoSyslogMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.3
ciscoSyslogMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.3.1
ciscoSyslogMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.41.3.2

CISCO-SYSLOG-MIB Technical Reference Overview

The CISCO-SYSLOG-MIB SNMP MIB module published by Cisco defines 34 managed OID objects, including 19 scalar/column metrics, 2 SNMP tables, and 1 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.41. Key tabular structures include clogHistoryTable, clogServerConfigTable. Monitored SNMP traps/notifications include clogMessageGenerated.

Key OID Definitions in CISCO-SYSLOG-MIB

ciscoSyslogMIBMODULE-IDENTITYnot-accessible
.1.3.6.1.4.1.9.9.41

The MIB module to describe and store the system messages generated by the IOS and any other OS which supports syslogs.

clogHistoryTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.41.1.2.3

A table of syslog messages generated by this device. All 'interesting' syslog messages (i.e. severity <= clogMaxSeverity) are entered into this table.

clogServerConfigTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.41.1.3.2

This table contains entries that allow application to configure syslog servers for the system. The maximum number of entries that can be created for this table is limited by the object clogMaxServers.

clogMessageGeneratedNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.41.2.0.1

When a syslog message is generated by the device a clogMessageGenerated notification is sent. The sending of these notifications can be enabled/disabled via the clogNotificationsEnabled object.

clogNotificationsSentCounter32read-only
.1.3.6.1.4.1.9.9.41.1.1.1

The number of clogMessageGenerated notifications that have been sent. This number may include notifications that were prevented from being transmitted due to reasons such as resource limitations and/or non-connectivity. If one is receiving notifications, one can periodically poll this object to determine if any notifications were missed. If so, a poll of the clogHistoryTable might be appropriate.

clogNotificationsEnabledTruthValueread-write
.1.3.6.1.4.1.9.9.41.1.1.2

Indicates whether clogMessageGenerated notifications will or will not be sent when a syslog message is generated by the device. Disabling notifications does not prevent syslog messages from being added to the clogHistoryTable.

clogMaxSeveritySyslogSeverityread-write
.1.3.6.1.4.1.9.9.41.1.1.3

Indicates which syslog severity levels will be processed. Any syslog message with a severity value greater than this value will be ignored by the agent. note: severity numeric values increase as their severity decreases, e.g. 'error' is more severe than 'debug'.

clogMsgIgnoresCounter32read-only
.1.3.6.1.4.1.9.9.41.1.1.4

The number of syslog messages which were ignored. A message will be ignored if it has a severity value greater than clogMaxSeverity.

clogMsgDropsCounter32read-only
.1.3.6.1.4.1.9.9.41.1.1.5

The number of syslog messages which could not be processed due to lack of system resources. Most likely this will occur at the same time that syslog messages are generated to indicate this lack of resources. Increases in this object's value may serve as an indication that system resource levels should be examined via other mib objects. A message that is dropped will not appear in the history table and no notification will be sent for this message.

clogOriginIDTypeINTEGERread-write
.1.3.6.1.4.1.9.9.41.1.1.6

This object identifies the type of value that will be contained in clogOriginID object. The possible value(s) are: 'none' : do not send origin identifier in syslog messages. 'other' : type that is not identified by other values specified in this object. 'hostName' : Send hostname of the system in syslog messages. 'ipv4Address': Send IP address of the sending interface. 'contextName': Send context name of the security device. 'userDefined': Send user configured string in syslog message. The value 'other' and 'none' can not be set but can only be read.

clogOriginIDSnmpAdminStringread-write
.1.3.6.1.4.1.9.9.41.1.1.7

This object is used for configuring the origin identifier for the syslog messages. The origin identifier is useful for identifying the source of system logging messages in cases syslog messages from multiple devices are sent to a single syslog host. The origin identifier is added to the beginning of all system logging (syslog) messages sent to remote hosts. The type of the identifier is specified by clogOriginIDType object. This object can be written by the SNMP manager only when clogOriginIDType is set to 'userDefined'. For following value(s) of clogOriginIDType, this object can not be set; the value of this object is derived by the system in these cases: 'contextName' 'ipv4Address' 'hostName' 'other' 'none' This object contains the context name of the device, when clogOriginIDType is set to 'contextName'. This object contains IPv4 address (in dotted decimal notation) of the sending interface when clogOriginIDType is set to 'ipv4Address'. This object contains hostname of the system when clogOriginIDType is set to 'hostName'. This object will contain zero length octet string when clogOriginIDType is either 'none' or 'other'.

clogHistTableMaxLengthInteger32read-write
.1.3.6.1.4.1.9.9.41.1.2.1

The upper limit on the number of entries that the clogHistoryTable may contain. A value of 0 will prevent any history from being retained. When this table is full, the oldest entry will be deleted and a new one will be created.

clogHistMsgsFlushedCounter32read-only
.1.3.6.1.4.1.9.9.41.1.2.2

The number of entries that have been removed from the clogHistoryTable in order to make room for new entries. This object can be utilized to determine whether your polling frequency on the history table is fast enough and/or the size of your history table is large enough such that you are not missing messages.

clogMaxServersUnsigned32read-only
.1.3.6.1.4.1.9.9.41.1.3.1

The maximum number of syslog servers that can be configured for the system in clogServerConfigTable. A value of zero for this object indicates there is no specified limit for the system and is only dictated by system resources.

clogHistoryEntryClogHistoryEntrynot-accessible
.1.3.6.1.4.1.9.9.41.1.2.3.1

A syslog message that was previously generated by this device. Each entry is indexed by a message index.

clogHistIndexInteger32not-accessible
.1.3.6.1.4.1.9.9.41.1.2.3.1.1

A monotonically increasing integer for the sole purpose of indexing messages. When it reaches the maximum value the agent flushes the table and wraps the value back to 1.

clogHistFacilityDisplayStringread-only
.1.3.6.1.4.1.9.9.41.1.2.3.1.2

Name of the facility that generated this message. For example: 'SYS'.

clogHistSeveritySyslogSeverityread-only
.1.3.6.1.4.1.9.9.41.1.2.3.1.3

The severity of the message.

clogHistMsgNameDisplayStringread-only
.1.3.6.1.4.1.9.9.41.1.2.3.1.4

A textual identification for the message type. A facility name in conjunction with a message name uniquely identifies a message type.

clogHistMsgTextDisplayStringread-only
.1.3.6.1.4.1.9.9.41.1.2.3.1.5

The text of the message. If the text of the message exceeds 255 bytes, the message will be truncated to 254 bytes and a '*' character will be appended - indicating that the message has been truncated.

clogHistTimestampTimeStampread-only
.1.3.6.1.4.1.9.9.41.1.2.3.1.6

The value of sysUpTime when this message was generated.

clogServerConfigEntryClogServerConfigEntrynot-accessible
.1.3.6.1.4.1.9.9.41.1.3.2.1

An entry containing information about syslog servers configured for the system.

clogServerAddrTypeInetAddressTypenot-accessible
.1.3.6.1.4.1.9.9.41.1.3.2.1.1

The type of Internet address of this syslog server.

clogServerAddrInetAddressnot-accessible
.1.3.6.1.4.1.9.9.41.1.3.2.1.2

The Internet address of this syslog server. The type of this address is determined by the value of the clogServerAddrType object.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.

920 objects→