JUNIPER-TRACEROUTE-MIB

All MIBs › JUNIPER-TRACEROUTE-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2003-07-18

Category: Vendor: Juniper

Description: Juniper Networks MIB for executing and monitoring traceroute path-discovery operations and results on Juniper 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-TRACEROUTE-MIB?

JUNIPER-TRACEROUTE-MIB is a Juniper Networks enterprise MIB implementing the vendor-specific portions of the standard traceRouteMIB (from DISMAN-TRACEROUTE-MIB in mib-2), letting an SNMP manager remotely trigger and retrieve traceroute path-discovery results on Juniper devices. It belongs to the network diagnostics/path-monitoring technology area and exposes control objects for defining traceroute tests — target, owning entity, interface name, and routing instance — with corresponding results tied back to the standard traceroute MIB structures. Its monitoring value is diagnostic rather than continuous telemetry: it is used to actively test and verify network reachability and path/hop behavior from a Juniper device, which helps operators confirm routing paths, detect route changes, or isolate where along a path connectivity is failing, including across specific routing instances (VRFs). It is explicitly designed as an enterprise extension of the IETF traceRouteMIB, with directly related entries in that standard MIB. Typical deployment context is Juniper routers and switches in service-provider or enterprise networks, where JUNIPER-TRACEROUTE-MIB SNMP monitoring supports on-demand or scheduled network path diagnostics, including multi-VRF environments.

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

Monitoring Examples

An administrator creates an entry in jnxTraceRouteCtlTable/jnxTraceRouteCtlEntry, setting jnxTRCtlOwnerIndex, jnxTRCtlTestName, jnxTRCtlIfName, and jnxTRCtlRoutingInstanceName to run a traceroute from a specific interface within a specific VRF. Reviewing the resulting hop-by-hop path (via jnxTraceRouteObjects and the related standard traceRouteMIB result tables) reveals where latency spikes or unreachable hops occur, helping isolate a routing or connectivity fault within that routing instance.

What Can Be Monitored

traceroute test configuration per interface
traceroute test per routing instance (VRF)
hop-by-hop path results
test ownership/name tracking

Imported Objects

From JUNIPER-SMI

jnxMibs

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxTraceRouteMIB	1.3.6.1.4.1.2636.3.8			This is Juniper Networks' implementation of enterprise specific portions of traceRouteMib. Any data stored in this MIB has directly related entries in mib-2, traceRouteMIB.
jnxTraceRouteObjects	1.3.6.1.4.1.2636.3.8.1
jnxTraceRouteCtlTable	1.3.6.1.4.1.2636.3.8.1.2		not-accessible	Defines the jnxTraceRoute Control Table for providing enterprise specific options to the corresponding traceRouteCtlTable entry.
jnxTraceRouteCtlEntry	1.3.6.1.4.1.2636.3.8.1.2.1		not-accessible	Defines an entry in the jnxTraceRouteCtlTable. The first index element, jnxTraceRouteCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows an management application to identify its entries. The second index, jnxTraceRouteCtlTestName (also an SnmpAdminString), enables the same management application to have multiple outstanding requests. Entries are created in the traceRouteCtlTable and mirrored here.
STR jnxTRCtlOwnerIndex	1.3.6.1.4.1.2636.3.8.1.2.1.1	SnmpAdminString	not-accessible	To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible.
STR jnxTRCtlTestName	1.3.6.1.4.1.2636.3.8.1.2.1.2	SnmpAdminString	not-accessible	The name of the traceRoute test. This is locally unique, within the scope of an traceRouteCtlOwnerIndex.
STR jnxTRCtlIfName	1.3.6.1.4.1.2636.3.8.1.2.1.3	DisplayString	read-create	Setting this object to an interface name prior to starting a remote traceRoute operation directs the traceRoute probes to be transmitted over the specified interface. To specify the interface index instead, see traceRouteCtlIfIndex. The interface name must be specified under interfaces statement of the JUNOS configuration. A zero length string value for this object means that this option is not enabled. The following values may be set simultaneously, however, only one value is used. The precedence order is a follows: traceRouteCtlIfIndex (see traceRouteCtlTable in traceRouteMIB) jnxTRCtlIfName jnxTRCtlRoutingInstanceName
STR jnxTRCtlRoutingInstanceName	1.3.6.1.4.1.2636.3.8.1.2.1.4	DisplayString	read-create	Use this option to specify the name of the routing instance used when directing outgoing traceRoute packets. The instance name specified must be configured under routing-instances of the JUNOS configuration.

RFC description

Juniper enterprise traceroute control and results management with extended options.

Start monitoring Juniper Networks router/switch (enterprise traceroute diagnostics) 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-TRACEROUTE-MIB

What Is JUNIPER-TRACEROUTE-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description