All MIBs › SYSLOG
Category: Fault Management, IP Services and Protocols
Description: Defines SNMP management objects for the syslog protocol message delivery per RFC 5676.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is SYSLOG?
SYSLOG is a vendor-neutral, standards-based MIB implementing RFC 5676, which defines how syslog protocol messages are represented as SNMP notifications so that syslog events can be correlated with SNMP-based management. It exposes objects describing syslog message attributes such as facility, severity, timestamp, originating hostname, and application name, carried within the notification payload. Its role in monitoring is centered on software/event status rather than hardware counters: it lets a management station receive and interpret syslog-originated fault or status events, such as a process crash or a configuration change logged via syslog, through the same SNMP trap-receiving infrastructure used for other alerts. It is defined directly by IETF RFC 5676 and is meant to be layered on top of standard SNMP notification-delivery mechanisms. It is deployed on any SNMP-managed device that also generates syslog messages, wherever an operator wants unified event correlation between the two protocols. Engineers can download the SYSLOG file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in SYSLOG. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer; applicable to any SNMP-managed device that also emits syslog messages
Monitoring Examples
An admin configures a device to forward selected syslog messages as SNMP notifications and then monitors the resulting trap's severity and facility fields to filter for critical events, such as an "emergency" or "critical" severity syslog message indicating a hardware or software fault. The message's hostname and application-name fields let the receiving management station attribute the event to the correct originating process or subsystem without needing a separate syslog collector. Because this module's role is definitional/mapping rather than exposing a live table of counters, most "monitoring" here consists of trap content rather than polled objects.
What Can Be Monitored
- syslog message severity level
- syslog message facility
- originating hostname/application name of syslog event
- syslog message timestamp and text
Imported Objects
From ExaltComm
| SyslogEnableT | |
| SyslogFilterSelectT |
From ExaltComProducts
| radioConfig | OBJECT-IDENTITY |
From SNMPv2-SMI
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString |
OIDs
RFC description
Configures syslog remote logging to send system events to a remote syslog server.
Start monitoring vendor-neutral, standards-based MIB (RFC 5676), any SNMP-managed device emitting syslog messages (syslog-to-SNMP notification correlation) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.