JUNIPER-FABRIC-CHASSIS

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-FABRIC-CHASSIS

Organization: Juniper Networks, Inc.

Last Updated: 2012-09-13

Category: Hardware and Environment, Vendor: Juniper

Description: Defines managed objects for fabric chassis monitoring in Juniper Networks QFabric and multi-chassis systems.

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-FABRIC-CHASSIS?

JUNIPER-FABRIC-CHASSIS is a Juniper Networks enterprise MIB representing the hardware components of Juniper's QFabric and other multi-chassis fabric systems, which interconnect many physical nodes into a single logical switching fabric. It exposes an anatomy of scalar and tabular hardware inventory data describing the fabric's constituent components (e.g., director nodes, interconnect devices, node devices) and their identification/status. As a hardware-status MIB it is used to confirm that all fabric components are present, correctly enumerated, and operationally healthy, which is essential in a distributed fabric where a single failed interconnect or node device can silently degrade capacity. It is a Juniper-specific enterprise MIB and typically works alongside JUNIPER-FRU-MIB and generic chassis MIBs to give complete hardware visibility across the fabric. Typical deployment is large data-center QFabric or multi-chassis fabric deployments requiring unified visibility across dozens of physical devices. Engineers can download the JUNIPER-FABRIC-CHASSIS file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-FABRIC-CHASSIS. 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 QFabric system
  • Juniper multi-chassis fabric switch

Monitoring Examples

An administrator would walk the jnxFabricAnatomyTables to enumerate all physical components across the fabric and check the jnxFabricAnatomyScalars for fabric-wide summary counts, catching a scenario where a fabric node or interconnect device has disappeared from the inventory, indicating a hardware failure or a communication loss within the fabric. Because sample objects here are limited to top-level scalar/table groupings, specific column-level detail (like per-component status codes) cannot be confirmed from what's provided. This MIB is primarily useful as a fabric-wide hardware inventory and presence check rather than a performance-counter source.

What Can Be Monitored

  • fabric component inventory
  • fabric-wide summary scalars
  • node/interconnect device presence
  • fabric hardware anatomy
Imported Objects

From JUNIPER-MIB

JnxChassisId

From JUNIPER-SMI

jnxDcfMibRootOBJECT-IDENTITY
jnxFabricChassisOKTrapsOBJECT-IDENTITY
jnxFabricChassisTrapsOBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DateAndTime
DisplayString
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using jnxFabricRedundancySwitchoverCount OID:

Select a Juniper QFabric system / multi-chassis fabric switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxFabricRedundancySwitchoverCount into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of switchover as perceived by this subject since routing engine is up and running. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Manages Juniper Quantum Fabric hardware components including chassis, nodes, and fabric container family information.

Start monitoring Juniper QFabric system / multi-chassis fabric switch 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-FABRIC-CHASSIS