JUNIPER-TRACEROUTE-MIB

File: JUNIPER-TRACEROUTE-MIB.mib (5796 bytes)

Imported modules

SNMPv2-SMI SNMP-FRAMEWORK-MIB SNMPv2-TC
JUNIPER-SMI

Imported symbols

MODULE-IDENTITY OBJECT-TYPE SnmpAdminString
DisplayString jnxMibs

Defined Types

JnxTraceRouteCtlEntry  
SEQUENCE    
  jnxTRCtlOwnerIndex SnmpAdminString
  jnxTRCtlTestName SnmpAdminString
  jnxTRCtlIfName DisplayString
  jnxTRCtlRoutingInstanceName DisplayString

Defined Values

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.
MODULE-IDENTITY    

jnxTraceRouteObjects 1.3.6.1.4.1.2636.3.8.1
OBJECT IDENTIFIER    

jnxTraceRouteCtlTable 1.3.6.1.4.1.2636.3.8.1.2
Defines the jnxTraceRoute Control Table for providing enterprise specific options to the corresponding traceRouteCtlTable entry.
OBJECT-TYPE    
  SEQUENCE OF  
    JnxTraceRouteCtlEntry

jnxTraceRouteCtlEntry 1.3.6.1.4.1.2636.3.8.1.2.1
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.
OBJECT-TYPE    
  JnxTraceRouteCtlEntry  

jnxTRCtlOwnerIndex 1.3.6.1.4.1.2636.3.8.1.2.1.1
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.
OBJECT-TYPE    
  SnmpAdminString Size(0..32)  

jnxTRCtlTestName 1.3.6.1.4.1.2636.3.8.1.2.1.2
The name of the traceRoute test. This is locally unique, within the scope of an traceRouteCtlOwnerIndex.
OBJECT-TYPE    
  SnmpAdminString Size(0..32)  

jnxTRCtlIfName 1.3.6.1.4.1.2636.3.8.1.2.1.3
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
OBJECT-TYPE    
  DisplayString Size(0..24)  

jnxTRCtlRoutingInstanceName 1.3.6.1.4.1.2636.3.8.1.2.1.4
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.
OBJECT-TYPE    
  DisplayString Size(0..31)