Unisphere-Data-LOG-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Unisphere-Data-LOG-MIB

Organization: Unisphere Networks, Inc.

Last Updated: 2001-03-16

Category: Juniper Unisphere ERX Routing

Description: Manages Unisphere ERX system event logging configuration, log levels, and syslog server targeting.

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 Unisphere-Data-LOG-MIB?

Unisphere-Data-LOG-MIB is an enterprise MIB from Unisphere Networks (maker of the ERX edge routers, later folded into Juniper's E-series line) that manages the device's internal event-logging subsystem. It exposes configuration objects for logging destinations -- console, non-volatile file, and remote syslog servers -- including per-destination severity filtering, syslog server IP address and facility, and a table of configured log categories. Administrators use it to monitor and control which software subsystems log events and at what severity, governing visibility into the router's operational and fault history; a misconfigured severity or missing syslog target here would explain why expected fault/error messages aren't reaching a monitoring system. It operates as a vendor logging framework typically used alongside standard SNMP notifications and RFC 3164 syslog conventions for centralized log collection. It is typically deployed on Unisphere/Juniper ERX edge routers in service-provider access networks. Engineers can download the Unisphere-Data-LOG-MIB file directly to load it into their MIB browser.

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

  • Unisphere/Juniper ERX edge router

Monitoring Examples

An operator would check usdLogDestSyslogSeverity and usdLogDestSyslogAddress to confirm which severity level is forwarded to which remote syslog collector, and walk usdLogSyslogTable/usdLogSyslogEntry to see configured syslog server entries with usdLogSyslogIpAddress, usdLogSyslogFacility, and usdLogSyslogRowStatus. If usdLogDestConsoleSeverity is far more verbose than usdLogDestNvFileSeverity, console output and the persisted log file will diverge, explaining discrepancies during troubleshooting. Reviewing usdLogCatTable/usdLogCatEntry reveals which logging categories are enabled, helping confirm whether a specific subsystem's events are captured at all.

What Can Be Monitored

  • syslog destination severity filters
  • syslog server IP address and facility
  • console logging severity
  • NV file logging severity
  • configured log categories
Imported Objects

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

From Unisphere-Data-MIBs

usDataMibsMODULE-IDENTITY

From Unisphere-Data-TC

UsdLogSeverity

How to Use in IPNetwork Monitor

Example using usdLogCatDiscards OID:

Select an Unisphere/Juniper ERX edge router (log destination/severity-filter config status) 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 usdLogCatDiscards 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 system logging configuration and message delivery to SYSLOG, console, and local file destinations with severity and verbosity filtering.

Start monitoring Unisphere/Juniper ERX edge router (log destination/severity-filter config 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.

Download Unisphere-Data-LOG-MIB