CISCO-SYSLOG-MIB.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file CISCO-SYSLOG-MIB and use it to monitor vendor specific OID's.
CISCO-SYSLOG-MIB file content
Object view of CISCO-SYSLOG-MIB:
| Scalar Object |
| clogNotificationsSent |
.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.
|
| clogNotificationsEnabled |
.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.
|
| clogMaxSeverity |
.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(4) is more severe than
debug(8).
|
| clogMsgIgnores |
.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.
|
| clogMsgDrops |
.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.
|
| clogHistTableMaxLength |
.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.
|
| clogHistMsgsFlushed |
.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.
|
| clogHistoryEntry |
.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.
|
| Tabular Object |
| clogHistIndex |
.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.
|
| clogHistFacility |
.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'.
|
| clogHistSeverity |
.1.3.6.1.4.1.9.9.41.1.2.3.1.3 |
|
The severity of the message.
|
| clogHistMsgName |
.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.
|
| clogHistMsgText |
.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.
|
| clogHistTimestamp |
.1.3.6.1.4.1.9.9.41.1.2.3.1.6 |
|
The value of sysUpTime when this message was generated.
|
| Table |
| clogHistoryTable |
.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.
|
| Trap |
| clogMessageGenerated |
.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.
|
| Object Identifier |
| ciscoSyslogMIB |
.1.3.6.1.4.1.9.9.41 |
|
The MIB module to describe and store the system messages
generated by the IOS.
|
| ciscoSyslogMIBObjects |
.1.3.6.1.4.1.9.9.41.1 |
| clogBasic |
.1.3.6.1.4.1.9.9.41.1.1 |
| clogHistory |
.1.3.6.1.4.1.9.9.41.1.2 |
| ciscoSyslogMIBNotificationPrefix |
.1.3.6.1.4.1.9.9.41.2 |
| ciscoSyslogMIBNotifications |
.1.3.6.1.4.1.9.9.41.2.0 |
| ciscoSyslogMIBConformance |
.1.3.6.1.4.1.9.9.41.3 |
| ciscoSyslogMIBCompliances |
.1.3.6.1.4.1.9.9.41.3.1 |
| ciscoSyslogMIBGroups |
.1.3.6.1.4.1.9.9.41.3.2 |
| Group |
| ciscoSyslogMIBGroup |
.1.3.6.1.4.1.9.9.41.3.2.1 |
|
A collection of objects providing the syslog MIB capability.
|
