JUNIPER-CHASSIS-DEFINES-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-CHASSIS-DEFINES-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2014-04-01

Description: JUNIPER-CHASSIS-DEFINES-MIB module

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is JUNIPER-CHASSIS-DEFINES-MIB?

JUNIPER-CHASSIS-DEFINES-MIB is a Juniper Networks enterprise MIB that contains no monitorable OBJECT-TYPE leaves of its own; instead it defines the large tree of OBJECT IDENTIFIER constants -- product line, product name, chassis, slot, module, and submodule/PIC identifiers -- that JUNIPER-CHASSIS-MIB and related modules use to identify exactly which platform, slot type, or interface card a given hardware-inventory entry represents. It spans Juniper's M-series and T-series routers (M5/M10/M20/M40/M40e/M160, T320/T640) down to individual slot types (FPC, SIB/SFM, Routing/Host Engine, power supply, cooling fan/impeller) and dozens of named Physical Interface Card (PIC) constants covering SONET/SDH, ATM, Gigabit Ethernet, channelized T3/E3/T1/E1, and tunnel/crypto interfaces, plus later revisions extending coverage to EX/QFX/MX-series switches and Quantum Fabric components. Because every constant here is purely an identification OID rather than a live value, this module is consumed indirectly: an agent implementing JUNIPER-CHASSIS-MIB returns one of these OIDs as the value of a chassis-component-type object, and a management station cross-references it against this MIB to render a human-readable platform/component name. It depends on the JUNIPER-SMI enterprise tree for its parent OID and is deployed alongside JUNIPER-CHASSIS-MIB on all Juniper routing and switching platforms, and administrators can download the JUNIPER-CHASSIS-DEFINES-MIB file to decode chassis-component identity values returned by a Juniper device.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-CHASSIS-DEFINES-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.

Supported Devices

  • Juniper Networks M-series and T-series routers (and later EX/QFX/MX platforms per revision)

Monitoring Examples

An operator reads a chassis-component-type object from JUNIPER-CHASSIS-MIB on an M160 router and cross-references the returned OID against jnxT320FPC/jnxT640FPC-style constants in this MIB to determine the exact FPC or PIC model installed in a slot; an OID that fails to resolve against any constant here would indicate a newer hardware type not yet covered by the installed MIB revision.

What Can Be Monitored

  • chassis/slot/module type identification OIDs
  • PIC (Physical Interface Card) type identification
  • product line/name/model classification
  • backplane/midplane and power-supply component identification

This MIB depends on

Related MIBs

Imported Objects

From JUNIPER-SMI

jnxMibsOBJECT-IDENTITY
jnxProductsOBJECT-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
OIDs

RFC description

A Juniper Networks enterprise-specific MIB module that defines OIDs and constants used by the Chassis MIB for identifying platform and hardware components on Juniper routers and switches.

Start monitoring Juniper Networks M/T-series router (and later EX/QFX/MX platforms), chassis component OID definitions 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-CHASSIS-DEFINES-MIB