All MIBs › RTBRICK-SYSLOG-MIB
Organization: RtBrick
Last Updated: 2019--0-1-
Category: Technology: SDN/OpenFlow
Description: Manages syslog message forwarding configuration and event notification for RtBrick routing software.
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 RTBRICK-SYSLOG-MIB?
RTBRICK-SYSLOG-MIB is a vendor-specific MIB for RtBrick, a disaggregated network operating system vendor, covering the system-logging/event-notification area of its routing software. It defines objects and a notification for individual syslog messages generated by the device, including message sequence number, originating facility, severity level, and the message text itself. Its monitoring value is squarely in software/event status: it lets an NMS receive real-time SNMP traps mirroring syslog output so operators can detect software faults, configuration errors, or operational events (link flaps, process restarts, authentication failures) as they are logged, without needing separate syslog collection infrastructure. It complements the standard SYSLOG-MSG-MIB pattern and relies on the device's underlying RtBrick FullStack/BRICK OS syslog subsystem to source events. It is typically deployed on RtBrick-based disaggregated routers and switches in service-provider or data-center networks where centralized SNMP-based event monitoring is preferred alongside or instead of traditional syslog servers. Engineers can download the RTBRICK-SYSLOG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in RTBRICK-SYSLOG-MIB. 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
- RtBrick-based disaggregated router/switch
Monitoring Examples
An admin would configure trap reception for the syslogMessage notification, then inspect its bound varbinds - syslogMsgNumber, syslogMsgFacility, syslogMsgSeverity, and syslogMsgText - to see, for instance, a message with high severity and facility 'kernel' indicating a line-card or interface failure. Tracking syslogMsgNumber across received traps also lets the NMS detect gaps, revealing dropped or unreceived log messages. This gives visibility into software-level events and faults on the router without requiring a separate syslog server integration.
What Can Be Monitored
- syslog message severity
- syslog message facility
- syslog message text/content
- syslog message sequence number
- real-time event notifications
Imported Objects
From RTBRICK-MIB
| rtbrickModules | OBJECT-IDENTITY |
| rtbrickSyslogNotifications | OBJECT-IDENTITY |
| rtbrickTraps | OBJECT-IDENTITY |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION |
OIDs
RFC description
RTBrick system logging MIB for monitoring syslog messages with severity levels and facility information.
Start monitoring RtBrick-based disaggregated router/switch (syslog message SNMP trap notifications) 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.