All MIBs › Juniper-TC
Organization: Juniper Networks, Inc.
Last Updated: 2005-12-21
Category: Protocol: SNMP, SNMP Framework, Textual Conventions and Registries, Vendor: Juniper
Description:
Juniper Networks textual conventions MIB defining common data types and enumeration values used across Juniper E-series MIB modules.
Imported Objects
From Juniper-MIBs
| juniMibs | MODULE-IDENTITY |
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| TimeTicks |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is Juniper-TC?
This MIB defines the common textual conventions (custom data types and enumerations) used across the family of Juniper Networks E-series MIB modules. It is a foundational, vendor-specific support module rather than one exposing device status data itself, providing standardized types for things like row status conventions, interface references, and enumerated state values used consistently throughout Juniper's E-series MIB suite. Its role in monitoring is indirect: it ensures that hardware and software status fields defined across dozens of other Juniper MIBs (interface state, alarm severity, module status, etc.) are interpreted consistently by NMS tooling. Nearly every other Juniper-E-series-specific MIB module depends on this one for shared type definitions, making it a core dependency rather than a standalone monitoring target. The Juniper-TC MIB is loaded automatically whenever a MIB compiler processes any Juniper E-series module that references its shared type definitions. It is present on any Juniper E-series router deployment as a supporting import for the broader MIB stack.
IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-TC. 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
- shared textual convention definitions used by other Juniper MIBs (not directly pollable)
Supported Devices
- Juniper Networks E-series edge routers
Monitoring Examples
When an NMS decodes an enumerated status value from, say, juniSmdsIfRowStatus or another Juniper E-series table, it relies on textual convention definitions imported from Juniper-TC to correctly interpret the integer codes as human-readable states. Because Juniper-TC itself has no operational objects, it is never polled directly but is essential for correct MIB compilation and value interpretation across the Juniper MIB tree. A missing or mismatched Juniper-TC import would cause MIB compilers to fail loading dependent Juniper E-series modules.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| juniTextualConventions | 1.3.6.1.4.1.4874.2.2.1 | Textual conventions defined and used by the Juniper Networks enterprise. |
RFC description
Textual conventions and data type definitions used throughout Juniper Networks enterprise MIBs.
Start monitoring Juniper Networks E-series edge router (shared textual conventions) 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.