JUNIPER-TRACEROUTE-MIB
Updated Jul 18, 2003The JUNIPER-TRACEROUTE-MIB module enables monitoring of Juniper Networks routing devices by exposing traceRouteMIB metrics, specifically tracking active traceroute sessions, hop-by-hop path latency, and packet loss statistics to validate network path integrity.
Imported Objects
Objects
8 total| Object Name |
|---|
jnxTraceRouteMIBThis is Juniper Networks' implementation of enterprise specific
portions of traceRouteMib. Any data stored in this MIB has
directly related entries in mib-2, traceRouteMIB. MODULE-IDENTITY .1.3.6.1.4.1.2636.3.8 |
jnxTraceRouteObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.8.1 |
jnxTraceRouteCtlTableDefines the jnxTraceRoute Control Table for providing enterprise
specific options to the corresponding traceRouteCtlTable entry. SEQUENCE OF JnxTraceRouteCtlEntry .1.3.6.1.4.1.2636.3.8.1.2 |
jnxTraceRouteCtlEntryDefines 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. JnxTraceRouteCtlEntry .1.3.6.1.4.1.2636.3.8.1.2.1 |
jnxTRCtlOwnerIndexTo 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. SnmpAdminString .1.3.6.1.4.1.2636.3.8.1.2.1.1 |
jnxTRCtlTestNameThe name of the traceRoute test. This is locally unique, within
the scope of an traceRouteCtlOwnerIndex. SnmpAdminString .1.3.6.1.4.1.2636.3.8.1.2.1.2 |
jnxTRCtlIfNameSetting 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
jnxTRCtlRoutingInstanceNamerw DisplayString .1.3.6.1.4.1.2636.3.8.1.2.1.3 |
jnxTRCtlRoutingInstanceNameUse 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.rw DisplayString .1.3.6.1.4.1.2636.3.8.1.2.1.4 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
SNMP MIB module
SNMP MIB module
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.