Juniper-LOG-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Juniper-LOG-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2002-09-16

Category: Device Management, Technology: Logging/Syslog, Vendor: Juniper

Description: Provides managed objects for system log (syslog) configuration, filtering, and message statistics on Juniper Networks E-series routers.

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 Juniper-LOG-MIB?

Juniper-LOG-MIB is a Juniper enterprise MIB that manages the logging facility on Juniper E-series routers, controlling where log messages are sent (syslog server, console, non-volatile file) and at what severity, along with per-category log filtering. It exposes destination-specific severity thresholds, a syslog server table with per-server severity and facility settings, and log category definitions. Its monitoring value is squarely software/operational status: verifying that critical severity events are actually being forwarded to the intended syslog collector, console, or persistent log file, which is foundational to catching hardware and software faults elsewhere on the device. It is a self-contained enterprise MIB, conceptually parallel to but independent of IETF SYSLOG-MSG-MIB. It is deployed on Juniper E-series routers wherever centralized log collection or on-box event logging is configured. Network engineers evaluating or troubleshooting this functionality can download the Juniper-LOG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-LOG-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

  • Juniper E-series router

Monitoring Examples

An administrator checks juniLogDestSyslogSeverity and juniLogDestSyslogAddress to confirm logs at or above the configured severity are being forwarded to the correct syslog server, and reviews juniLogSyslogTable/juniLogSyslogEntry (juniLogSyslogIpAddress, juniLogSyslogSeverity, juniLogSyslogFacility) when multiple syslog destinations are configured. If console-visible errors aren't appearing on a remote collector, comparing juniLogDestConsoleSeverity against juniLogDestSyslogSeverity often reveals a severity filter mismatch. juniLogCatTable/juniLogCatEntry lets an operator confirm whether a specific event category (e.g., routing or security) is enabled for logging at all.

What Can Be Monitored

  • syslog destination severity thresholds
  • configured syslog server addresses
  • console/NV-file log severity
  • per-category logging enablement
  • syslog facility settings
Imported Objects

From Juniper-MIBs

juniMibsMODULE-IDENTITY

From Juniper-TC

JuniLogSeverity

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using juniLogCatDiscards OID:

Select a Juniper E-series router (logging facility/syslog destinations) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type juniLogCatDiscards into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of messages generated by this log category that were discarded because of resource limitations. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Manages logging facility for Juniper Networks devices with syslog, console, and local file logging destinations.

Start monitoring Juniper E-series router (logging facility/syslog destinations) 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.

Download Juniper-LOG-MIB