Juniper-ROUTER-MIB

MIB Reference — IPNetwork Monitor

All MIBsJuniper-ROUTER-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2004-05-06

Category: Technology: Routing, Vendor: Juniper

Description:

Juniper Networks MIB for managing virtual router instances, routing contexts, and associated interfaces on Juniper E-series platforms.

Imported Objects

From Juniper-IP-POLICY-MIB

JuniIpPolicyExtendedCommunity
JuniIpPolicyName

From Juniper-MIBs

juniMibsMODULE-IDENTITY

From Juniper-TC

JuniName

From SNMP-FRAMEWORK-MIB

SnmpEngineID

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TruthValue

What Is Juniper-ROUTER-MIB?

Juniper-ROUTER-MIB is a Juniper Networks vendor-specific module for the E-series (ERX/E120/E320) platform, managing the creation, deletion, and administrative state of logical/virtual routers (VRs and VRFs) that run within a physical chassis. It exposes summary counts of configured virtual router instances alongside a per-router table giving each virtual router's name, context, VRF association, and row (creation/administrative) status. Its monitoring role is chiefly configuration/operational-status tracking for virtualization on the box: the summary counts let an operator confirm the expected number of virtual routers exist, while juniRouterRowStatus on each entry confirms a given virtual router is active rather than stuck mid-creation or being torn down. It underlies protocol- and interface-level MIBs scoped per virtual router context, since routing protocols and interfaces on an E-series box are managed relative to the router context they belong to. It is deployed specifically on Juniper E-series edge/broadband routers used by service providers for large-scale subscriber and VRF-based routing separation. Operators managing many virtual routers often browse the Juniper-ROUTER-MIB OID subtree directly to enumerate all provisioned VR/VRF entries at once rather than polling them individually.

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

What Can Be Monitored

  • number of virtual routers configured
  • number of VRFs configured
  • virtual router administrative/row status
  • virtual router name and routing context
  • total configured router instance count

Supported Devices

  • Juniper E-series router (ERX/E120/E320)

Monitoring Examples

An operator would poll juniRouterTable/juniRouterEntry, checking juniRouterRowStatus for each juniRouterName to confirm a provisioned virtual router is fully active, and cross-check juniRouterSummaryTotalConfigured against the expected count to catch a VR that failed to instantiate. juniRouterVrf and juniRouterContextName together let an operator map a virtual router to its VRF and see which routing context downstream interface/protocol MIBs should be queried against. A sudden drop in juniRouterSummaryParentVRsConfigured could indicate an unexpected virtual router deletion affecting subscriber routing separation.

OIDs
OID symbolicOID numericTypeAccessDescription
juniRouterMIB1.3.6.1.4.1.4874.2.2.32The Router MIB is used to manage the creation and deletion as well as the administrative states of the protocols and functions that run within a designated router.
juniRouterObjects1.3.6.1.4.1.4874.2.2.32.1
JUN juniRouterNextRouterIndex1.3.6.1.4.1.4874.2.2.32.1.1JuniNextRouterIndexread-onlyCoordinates routerIndex and juniRouterVrfIndex value allocation for entries in the juniRouterTable and juniRouterVrfTable, respectively. A GET of this object returns the next available routerIndex value to be used to create an entry in the associated router table; or zero, if no valid routerIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that routerIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.
juniRouterTable1.3.6.1.4.1.4874.2.2.32.1.2not-accessibleThis table contains entries for routers present in the system.
juniRouterEntry1.3.6.1.4.1.4874.2.2.32.1.2.1not-accessibleEach entry in this table represents a single router. Creating and/or deleting entries in this table causes corresponding entries to be created or deleted in the juniRouterProtocolTable. Note that VRFs also appear as entries in this table and can be differentiated by the juniRouterVrf object. The juniRouterVrfTable shows the parent / child relationship between routers and VRFs present in the system.
U32 juniRouterIndex1.3.6.1.4.1.4874.2.2.32.1.2.1.1Unsigned32not-accessibleThe routerIndex of this router. When creating entries in this table, suitable values for this object are determined by reading juniRouterNextRouterIndex.
JUN juniRouterName1.3.6.1.4.1.4874.2.2.32.1.2.1.2JuniNameread-createThe administratively assigned name given to this router. The name must be unique within the context of this table and cannot be changed after the router instance is created.
ROW juniRouterRowStatus1.3.6.1.4.1.4874.2.2.32.1.2.1.3RowStatusread-createControls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniRouterRowStatus juniRouterName In addition, when creating an entry the following conditions must hold: A value for juniRouterIndex must have been determined previously by reading juniRouterNextRouterIndex. A corresponding entries in juniRouterProtocolTable are created/destroyed as a result of creating/destroying an entry in this table.
T/F juniRouterVrf1.3.6.1.4.1.4874.2.2.32.1.2.1.4TruthValueread-onlyIdentifies whether this router is a VRF or not. A value of true(1) indicates that this is a VRF; a value of false(2) indicates that it is not.
OCT juniRouterContextName1.3.6.1.4.1.4874.2.2.32.1.2.1.5OCTET STRINGread-onlyAn internally derived/assigned name given to this router with a specific format: routerN where N is a decimal number (with no leading zeroes) in the range 1..16777215 corresponding to the value of the least significant 24 bits of the juniRouterIndex (the router UID). The name is unique within the context of this table.
SNM juniRouterContextEngineID1.3.6.1.4.1.4874.2.2.32.1.2.1.6SnmpEngineIDread-onlyThe virtual router SNMP engine's administratively-unique identifier. This is used as the contextEngineId to reach the virtual router's SNMP context via the system-wide SNMP engine using SNMPv3.
C32 juniRouterSummaryVRFCount1.3.6.1.4.1.4874.2.2.32.1.2.1.7Counter32read-onlyThe number of VRFs contained in the VR.
juniRouterProtocolTable1.3.6.1.4.1.4874.2.2.32.1.3not-accessibleThis table contains entries for each protocol supported by the router entry created in the juniRouterTable.
juniRouterProtocolEntry1.3.6.1.4.1.4874.2.2.32.1.3.1not-accessibleEach entry provides administrative control on a router protocol for the router designated by the first indice to this table. The second indice identifies the router protocol. Entries in this table are created as a side-effect of row creation in the juniRouterTable or juniRouterVrfTable.
U32 juniRouterProtocolRouterIndex1.3.6.1.4.1.4874.2.2.32.1.3.1.1Unsigned32not-accessibleThe routerIndex of this router. This object is the same as the juniRouterIndex object defined in the juniRouterTable.
JUN juniRouterProtocolProtocolIndex1.3.6.1.4.1.4874.2.2.32.1.3.1.2JuniRouterProtocolIndexnot-accessibleIdentities the router protocol.
ROW juniRouterProtocolRowStatus1.3.6.1.4.1.4874.2.2.32.1.3.1.3RowStatusread-writeAdministrative control and status of a protocol on a router. The following values can be read from this object: active(1) - Indicates that the protocol on the designated router is created, configured, and running. notReady(3) - Indicates that the protocol requires additional configuration in a protocol specific MIB module. Examples include the BGP and OSPF protocols, which require additional configuration of protocol specific parameters such as: Autonomous System (AS) for BGP, and Process Id for OSPF. destroy(6) - The destroy(3) operation can fail if there are executing applications dependent on the protocol. If an attempt is made to destroy(6) an active(1) protocol that other applications are dependent on, the rowStatus will read destroy(6). Normally, when a row is destroyed, the agent will cleaup and remove the entry. The following values can be written to this object: active(1) - Activate protocol on the designated router. createAndGo(4) - Create protocol on designated router. The router indicated by juniRouterProtocolRouterIndex must already exist in the juniRouterTable. The value of the juniRouterProtocolProtocolIndex must be from the set of protocol values defined by the JuniRouterProtocolIndex type. destroy(6) - Destroy protocol on designated router. If the operation is successful, the agent will remove the entry. If the operation failed, the row will remain in the table with a rowStatus value of destroy(6). Conditions on destroy(6): 1) The default router can not be deleted. 2) The local router can not be deleted. A local router is defined as the router that sourced the SNMP request. Upon creation of a router in the juniRouterTable, some protocol entries will appear in this table by default, which indicates that these protocols are created by the action of creating a router. It is important to note, that this behavior may change over time by protocol type.
juniRouterVrfTable1.3.6.1.4.1.4874.2.2.32.1.4not-accessibleThis table contains entries for each VRF on each router entry created in the juniRouterTable.
juniRouterVrfEntry1.3.6.1.4.1.4874.2.2.32.1.4.1not-accessibleEach entry provides administrative control on a router VRF for the router designated by the first indice of this table. The second indice identifies the router VRF. The parent router must exist in the juniRouterTable before performing VRF row creation in this table
U32 juniRouterVrfRouterIndex1.3.6.1.4.1.4874.2.2.32.1.4.1.1Unsigned32not-accessibleThe router index of this router, also referred to as the parent of the VRF. This object is the same as the juniRouterIndex object defined in the juniRouterTable.
U32 juniRouterVrfRouterVrfIndex1.3.6.1.4.1.4874.2.2.32.1.4.1.2Unsigned32not-accessibleThe VRF router index for this entry, also referred as the child of the parent router, which is identified by the first indice to this table.
JUN juniRouterVrfIpv4UnicastImportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.3JuniIpPolicyNameread-createThe VRF router import route map for IPv4 unicast routes.
JUN juniRouterVrfIpv4UnicastExportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.4JuniIpPolicyNameread-createThe VRF router export route map for IPv4 unicast routes.
JUN juniRouterVrfRouteDistinguisher1.3.6.1.4.1.4874.2.2.32.1.4.1.5JuniIpPolicyExtendedCommunityread-createThe VRF router route distinguisher.
ROW juniRouterVrfRowStatus1.3.6.1.4.1.4874.2.2.32.1.4.1.7RowStatusread-createControls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy *** LIMITED CONFIGURATION LEVEL *** RowStatus createAndGo/destroy operations have the following special-purpose semantics: createAndGo Create an entry having the specified configuration and append it to the target list, i.e. create an juniRouterVrfEntry table entry with the associated characteristics. destroy Destroy the specified element. Entries in this table can be modified once the row has been created. To create an entry in this table, the following entry objects MUST be explicitly configured: A value for juniRouterVrfRouterIndex must have been determined previously by reading juniRouterNextRouterIndex. A parent router must exist in the juniRouterTable.
JUN juniRouterVrfRouterName1.3.6.1.4.1.4874.2.2.32.1.4.1.8JuniNameread-createThe administratively assigned name given to this VRF router. The name must be unique within the context of this table and cannot be changed after the router instance is created.
STR juniRouterVrfRouterDescription1.3.6.1.4.1.4874.2.2.32.1.4.1.9DisplayStringread-createThe administratively assigned description given to this VRF router.
JUN juniRouterVrfIpv4UnicastGlobalExportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.10JuniIpPolicyNameread-createThe VRF router global export route map for IPv4 unicast routes.
T/F juniRouterVrfIpv4UnicastExportRouteMapFilter1.3.6.1.4.1.4874.2.2.32.1.4.1.11TruthValueread-createIs the VRF export map for IPv4 unicast routes allowed to filter routes?
JUN juniRouterVrfIpv6UnicastImportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.12JuniIpPolicyNameread-createThe VRF router import route map for IPv6 unicast routes.
JUN juniRouterVrfIpv6UnicastExportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.13JuniIpPolicyNameread-createThe VRF router export route map for IPv6 unicast routes.
JUN juniRouterVrfIpv6UnicastGlobalExportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.14JuniIpPolicyNameread-createThe VRF router global export route map for IPv6 unicast routes.
T/F juniRouterVrfIpv6UnicastExportRouteMapFilter1.3.6.1.4.1.4874.2.2.32.1.4.1.15TruthValueread-createIs the VRF export map for IPv6 unicast routes allowed to filter routes?
JUN juniRouterVrfIpv4UnicastGlobalImportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.16JuniIpPolicyNameread-createThe VRF router global import route map for IPv4 unicast routes.
U32 juniRouterVrfIpv4UnicastGlobalImportMaxRoutes1.3.6.1.4.1.4874.2.2.32.1.4.1.17Unsigned32read-createThe maximum number of IPv4 unicast routes which can be globaly imported.
JUN juniRouterVrfIpv6UnicastGlobalImportRouteMap1.3.6.1.4.1.4874.2.2.32.1.4.1.18JuniIpPolicyNameread-createThe VRF router global import route map for IPv6 unicast routes.
U32 juniRouterVrfIpv6UnicastGlobalImportMaxRoutes1.3.6.1.4.1.4874.2.2.32.1.4.1.19Unsigned32read-createThe maximum number of IPv6 unicast routes which can be globaly imported.
juniRouterVrfRouteTargetTable1.3.6.1.4.1.4874.2.2.32.1.5not-accessibleThis table contains entries for each route target for the router/VRF entry created in the juniRouterTable and juniRouterVrfTable.
juniRouterVrfRouteTargetEntry1.3.6.1.4.1.4874.2.2.32.1.5.1not-accessibleEach entry provides administrative control on VRF route targets for the router/VRF pair designated by the first and second indice of this table. The third indice identifies the route target. The parent router must exist in the juniRouterTable and the VRF router must exist in the juniRouterVrfTable before performing creation of the route target in this table.
U32 juniRouterVrfRouteTargetRouterIndex1.3.6.1.4.1.4874.2.2.32.1.5.1.1Unsigned32not-accessibleThe routerIndex of this router, also referred to as the parent of the VRF. This object is the same as the juniRouterIndex object defined in the juniRouterTable.
U32 juniRouterVrfRouteTargetRouterVrfIndex1.3.6.1.4.1.4874.2.2.32.1.5.1.2Unsigned32not-accessibleThe VRF router index for this entry, also referred as the child of the parent router, which is identified by the first indice to this table.
INT juniRouterVrfRouteTargetAddrFormat1.3.6.1.4.1.4874.2.2.32.1.5.1.3INTEGERnot-accessibleThe address format of the route target.
JUN juniRouterVrfRouteTargetRouteTarget1.3.6.1.4.1.4874.2.2.32.1.5.1.4JuniIpPolicyExtendedCommunitynot-accessibleThe VRF router route target.
INT juniRouterVrfRouteTargetType1.3.6.1.4.1.4874.2.2.32.1.5.1.5INTEGERread-createThe VRF router route target type.
ROW juniRouterVrfRouteTargetRowStatus1.3.6.1.4.1.4874.2.2.32.1.5.1.6RowStatusread-createControls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy *** LIMITED CONFIGURATION LEVEL *** RowStatus createAndGo/destroy operations have the following special-purpose semantics: createAndGo Create an entry having the specified configuration and append it to the target list, i.e., create an juniRouterVrfRouteTargetEntry table entry with the associated characteristics. destroy Destroy the specified element. To create an entry in this table, the following entry objects MUST be explicitly configured: A parent router must exist in the juniRouterTable. A VRF router must exist in the juniRouterVrfTable.
juniRouterSummaryCounts1.3.6.1.4.1.4874.2.2.32.1.6
juniRouterSummaryScalars1.3.6.1.4.1.4874.2.2.32.1.6.1
C32 juniRouterSummaryNonParentVRsConfigured1.3.6.1.4.1.4874.2.2.32.1.6.1.1Counter32read-onlyTotal number of VRs without VRFs configured.
C32 juniRouterSummaryParentVRsConfigured1.3.6.1.4.1.4874.2.2.32.1.6.1.2Counter32read-onlyTotal number of VRs with VRFs configured.
C32 juniRouterSummaryVRFsConfigured1.3.6.1.4.1.4874.2.2.32.1.6.1.3Counter32read-onlyTotal number of VRFs configured.
C32 juniRouterSummaryTotalConfigured1.3.6.1.4.1.4874.2.2.32.1.6.1.4Counter32read-onlyTotal number of Virtual Routers and VRFs configured.
juniRouterConformance1.3.6.1.4.1.4874.2.2.32.4
juniRouterCompliances1.3.6.1.4.1.4874.2.2.32.4.1
juniRouterCompliance1.3.6.1.4.1.4874.2.2.32.4.1.1An obsolete compliance statement for entities which implement the Juniper Router MIB. This statement became obsolete when support was added for VRFs within routers.
juniRouterCompliance21.3.6.1.4.1.4874.2.2.32.4.1.2An obsolete compliance statement for entities which implement the Juniper Router MIB. This statement became obsolete when support was added for the router context name.
juniRouterCompliance31.3.6.1.4.1.4874.2.2.32.4.1.3Obsolete compliance statement for entities which implement the Juniper Router MIB. This statement became obsolete when support was added for the router context engine ID.
juniRouterCompliance41.3.6.1.4.1.4874.2.2.32.4.1.4Obsolete compliance statement for entities which implement the Juniper Router MIB. This statement became obsolete when the global export map and the export map filter option were added to the VRF group.
juniRouterCompliance51.3.6.1.4.1.4874.2.2.32.4.1.5Obsolete compliance statement for entities which implement the Juniper Router MIB.
juniRouterCompliance61.3.6.1.4.1.4874.2.2.32.4.1.7Obsolete compliance statement for entities which implement the Juniper Router MIB.
juniRouterCompliance71.3.6.1.4.1.4874.2.2.32.4.1.8The compliance statement for entities which implement the Juniper Router MIB.
juniRouterGroups1.3.6.1.4.1.4874.2.2.32.4.2
juniRouterGroup1.3.6.1.4.1.4874.2.2.32.4.2.1An obsolete collection of objects providing management of routers and routing protocols in a Juniper product. This group became obsolete when support was added for VRFs within routers.
juniRouterGroup21.3.6.1.4.1.4874.2.2.32.4.2.2An obsolete collection of objects providing management of routers and routing protocols in a Juniper product. This group became obsolete when support was added for the router context name.
juniRouterVrfGroup1.3.6.1.4.1.4874.2.2.32.4.2.3Obsolete collection of objects providing management of VRFs within routers in a Juniper product. This group became obsolete when the VRF router description object was added.
juniRouterGroup31.3.6.1.4.1.4874.2.2.32.4.2.4Obsolete collection of objects providing management of routers and routing protocols in a Juniper product. This group became obsolete when the contect engine ID object was added.
juniRouterVrfGroup21.3.6.1.4.1.4874.2.2.32.4.2.5Obsolete collection of objects providing management of VRFs within routers in a Juniper product. This group became obsolete when the global export map and the export map filter option were added.
juniRouterGroup41.3.6.1.4.1.4874.2.2.32.4.2.6Obsolete collection of objects providing management of routers and routing protocols in a Juniper product. This group became obsolete when the summaryVRfCount object was added.
juniRouterVrfGroup31.3.6.1.4.1.4874.2.2.32.4.2.7Obsolete collection of objects providing management of VRFs within routers in a Juniper product. This group became obsolete when the global import map was added and when support for separate ipv4 and ipv6 route maps was added.
juniRouterGroup51.3.6.1.4.1.4874.2.2.32.4.2.8A collection of objects providing management of routers and routing protocols in a Juniper product.
juniRouterSummaryScalarsGroup1.3.6.1.4.1.4874.2.2.32.4.2.9A collection of objects providing summary counts for number of virtual routers and virtual router forwarding instances (VRFs) in a Juniper product.
juniRouterVrfGroup41.3.6.1.4.1.4874.2.2.32.4.2.10A collection of objects providing management of VRFs within routers in a Juniper product.

RFC description

Manages router creation, deletion, and administrative states of protocols and functions running within Juniper Networks JUNOSe virtual routers.

Start monitoring Juniper E-series router, ERX/E120/E320 (virtual router/VRF management) 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-ROUTER-MIB