All MIBs › Juniper-Registry
Organization: Juniper Networks, Inc.
Last Updated: 2004-12-23
Category: Protocol: SNMP, SNMP Framework, Vendor: Juniper
Description:
Juniper Networks MIB defining the top-level OID registry and namespace structure for Juniper E-series MIB modules.
Imported Objects
From Juniper-UNI-SMI
| juniperUniAdmin | OBJECT-IDENTITY |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY |
What Is Juniper-Registry?
Juniper-Registry is a Juniper Networks MIB defining the top-level OID registry and namespace structure for Juniper's E-series edge router product MIBs, originally from the acquired Unisphere/ERX platform. As a registration MIB it defines branch identifiers, e.g. for the ERX and ES2 platform families, and shared textual conventions such as entity physical type, rather than exposing tables of runtime data itself. It has no direct hardware/software status monitoring role; the actual monitorable objects, such as interface statistics or environmental sensors, are exposed by the various Juniper E-series MIBs that register their OIDs under this tree. Every Juniper E-series-specific MIB module depends on this registry MIB for its OID namespace assignment. A Juniper-Registry download is typically bundled with the full Juniper E-series MIB set and is present as the structural foundation MIB in ERX/ES2 edge router deployments.
IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-Registry. 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 E-series edge routers (ERX/ES2 platform family)
Monitoring Examples
juniRegistry, juniErxRegistry, and juniES2Registry are OID branch identifiers with no instantiable data, so no concrete polling scenario applies to this module directly; juniEntPhysicalType is a textual convention, likely aligned with ENTITY-MIB physical types, used by other Juniper MIBs to classify physical components such as line cards or power supplies.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| juniAdmin | 1.3.6.1.4.1.4874.4.2 | Administratively assigned object identifiers for Juniper Networks E-series edge router products. | ||
| juniRegistry | 1.3.6.1.4.1.4874.4.2.1 | |||
| juniEntPhysicalType | 1.3.6.1.4.1.4874.4.2.1.1 | |||
| juniPcmciaFlashCard | 1.3.6.1.4.1.4874.4.2.1.1.1 | The vendor type ID for a standard PCMCIA flash card. | ||
| juni85MegT2FlashCard | 1.3.6.1.4.1.4874.4.2.1.1.1.1 | The vendor type ID for an 85 Megabyte Type II ATA PCMCIA flash card (Product Code: PCM-85). | ||
| juni220MegT2FlashCard | 1.3.6.1.4.1.4874.4.2.1.1.1.2 | The vendor type ID for a 220 Megabyte Type II ATA PCMCIA flash card (Product Code: FLASH-220M). | ||
| juni512MegT2FlashCard | 1.3.6.1.4.1.4874.4.2.1.1.1.3 | The vendor type ID for a 512 Megabyte Type II ATA PCMCIA flash card (Product Code: RX-FLASH512-FRU). | ||
| juni1GigT2FlashCard | 1.3.6.1.4.1.4874.4.2.1.1.1.4 | The vendor type ID for a 1 Gigabyte Type II ATA PCMCIA flash card (Product Code: ERX-FLASH1GB-FRU). | ||
| juniTraceRouteImplementationTypes | 1.3.6.1.4.1.4874.4.2.1.2 | The registration node (point) for Juniper Traceroute implementation types. | ||
| juniTraceRouteUsingIcmpProbe | 1.3.6.1.4.1.4874.4.2.1.2.1 | Indicates that an implementation is using ICMP probes to perform the trace-route operation. | ||
| juniErxRegistry | 1.3.6.1.4.1.4874.4.2.2 | |||
| juniES2Registry | 1.3.6.1.4.1.4874.4.2.3 |
RFC description
Juniper Networks enterprise OID registry defining the root structure and namespace.
Start monitoring Juniper Networks E-series edge router, ERX/ES2 platform family (OID registry) 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.