JUNIPER-SYSLOG-MIB

All MIBs › JUNIPER-SYSLOG-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2006-03-20

Category: Technology: Logging/Syslog, Vendor: Juniper

Description: Juniper Networks MIB for monitoring system log (syslog) message generation and buffer statistics on Juniper routing platforms.

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-SYSLOG-MIB?

JUNIPER-SYSLOG-MIB is a Juniper Networks enterprise MIB implementing monitoring of system log (syslog) message generation and buffering statistics for JUNOS. It exposes statistics about syslog messages generated by the operating system, such as message counts and buffer utilization for the internal syslog facility. Its monitoring value is software status: tracking syslog message volume and buffer state can reveal abnormal logging activity (a spike suggesting a fault condition elsewhere in the system) or syslog buffer overflow that could cause log messages to be dropped. It is a self-contained Juniper enterprise MIB for JUNOS syslog internals without a stated dependency on external standards MIBs. It is deployed on Juniper routing and switching platforms where operators want SNMP-based visibility into syslog health as a complement to direct syslog message collection. Engineers can download the JUNIPER-SYSLOG-MIB file directly to load it into their MIB browser.

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

Juniper Networks routers
Juniper Networks switches

Monitoring Examples

No sample object names were provided for this module, so specific table or counter names cannot be confirmed from source; the module description only indicates it covers syslog statistics generated by JUNOS. In practice an administrator would expect to poll syslog message-count and buffer-utilization counters to detect an abnormal surge in log messages or a syslog buffer nearing capacity on a Juniper device, but naming exact objects here would be speculative given the lack of grounding data.

Imported Objects

From JUNIPER-SMI

jnxMibs	OBJECT-IDENTITY
jnxSyslogNotifications	OBJECT-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxSyslog	1.3.6.1.4.1.2636.3.35			This is Juniper Networks implementation of enterprise specific MIB for syslogs generated by JUNOS.
jnxSyslogNotifyVars	1.3.6.1.4.1.2636.3.35.1			Notification object definitions.
jnxSyslogTable	1.3.6.1.4.1.2636.3.35.1.1		not-accessible	A table of syslog messages generated by the device.
jnxSyslogEntry	1.3.6.1.4.1.2636.3.35.1.1.1		not-accessible	An entry of syslog table.
U32 jnxSyslogId	1.3.6.1.4.1.2636.3.35.1.1.1.1	Unsigned32	not-accessible	Syslog message identifier. This is also used as primary index in jnxSyslogAttrValTable
STR jnxSyslogEventName	1.3.6.1.4.1.2636.3.35.1.1.1.2	DisplayString	accessible-for-notify	An octet string containing syslog event name.
DAT jnxSyslogTimestamp	1.3.6.1.4.1.2636.3.35.1.1.1.3	DateAndTime	accessible-for-notify	Date and Time of syslog message generation.
JNX jnxSyslogSeverity	1.3.6.1.4.1.2636.3.35.1.1.1.4	JnxSyslogSeverity	accessible-for-notify	Identifies the severity of this syslog message.
JNX jnxSyslogFacility	1.3.6.1.4.1.2636.3.35.1.1.1.5	JnxSyslogFacility	accessible-for-notify	Identified the facility of this syslog message.
U32 jnxSyslogProcessId	1.3.6.1.4.1.2636.3.35.1.1.1.6	Unsigned32	accessible-for-notify	Process-Id of the process that generated this syslog message.
STR jnxSyslogProcessName	1.3.6.1.4.1.2636.3.35.1.1.1.7	DisplayString	accessible-for-notify	Name of the process that generated this syslog message.
STR jnxSyslogHostName	1.3.6.1.4.1.2636.3.35.1.1.1.8	DisplayString	accessible-for-notify	Hostname of host on which this syslog message is generated.
OCT jnxSyslogMessage	1.3.6.1.4.1.2636.3.35.1.1.1.9	OCTET STRING	accessible-for-notify	The syslog message string.
jnxSyslogAvTable	1.3.6.1.4.1.2636.3.35.1.2		not-accessible	A table of attribute value pairs of the syslog messages generated by the device.
jnxSyslogAvEntry	1.3.6.1.4.1.2636.3.35.1.2.1		not-accessible	An entry of attribute value pair.
U32 jnxSyslogAvIndex	1.3.6.1.4.1.2636.3.35.1.2.1.1	Unsigned32	not-accessible	Identifies the sequence number of attribute-value pair in the syslog message.
STR jnxSyslogAvAttribute	1.3.6.1.4.1.2636.3.35.1.2.1.2	DisplayString	accessible-for-notify	Attribute of the syslog message identified by jnxSyslogId.
STR jnxSyslogAvValue	1.3.6.1.4.1.2636.3.35.1.2.1.3	DisplayString	accessible-for-notify	Value of the attribute identified by jnxSyslogAvAttribute.
jnxSyslogNotificationPrefix	1.3.6.1.4.1.2636.4.12.0			All Syslog notifications are registered under this branch.
NTF jnxSyslogTrap	1.3.6.1.4.1.2636.4.12.0.1			Notification of a generated syslog message. Apart from the jnxSyslogTrap objects, this notification can include one or more attribute-value pairs. The attribute-value pairs shall be identified by objects jnxSyslogAvAttribute and jnxSyslogAvValue.

RFC description

Juniper Networks syslog message generation tracking for JUNOS devices. Manages syslog severity levels, facility codes, and message content.

Start monitoring Juniper Networks router/switch running JUNOS (syslog statistics) 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-SYSLOG-MIB

What Is JUNIPER-SYSLOG-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description