JUNIPER-CHASSIS-CLUSTER-MIB

All MIBs › JUNIPER-CHASSIS-CLUSTER-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2013-09-20

Category: Technology: High Availability, Vendor: Juniper

Description: Provides management objects for chassis clustering (high availability) on Juniper Networks SRX firewalls, including redundancy group and node status.

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-CLUSTER-MIB?

JUNIPER-CHASSIS-CLUSTER-MIB is a Juniper Networks enterprise MIB for monitoring chassis clustering, the high-availability mechanism used primarily on SRX firewalls to pair two chassis into an active/standby (or active/active) redundant unit. It exposes cluster and redundancy-group status, node roles (primary/secondary), and failover-related state so an operator can confirm the cluster is healthy and correctly synchronized. This is fundamentally a hardware/software availability MIB: it directly reports whether a chassis has failed over, whether a node is degraded, and whether data/control planes remain synchronized, making it critical for detecting silent HA failures before they cause an outage. It is a Juniper-specific extension with no dependency on general IETF MIBs, since chassis clustering is a proprietary SRX feature, though it is often monitored alongside JUNIPER-FRU-MIB and interface MIBs for full HA visibility. Typical deployment is paired SRX firewalls in enterprise or data-center edge deployments requiring high availability. Engineers can download the JUNIPER-CHASSIS-CLUSTER-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-CHASSIS-CLUSTER-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 SRX firewall (chassis cluster pair)

Monitoring Examples

An administrator would poll redundancy-group status to confirm which chassis currently holds the primary role and verify both nodes report a healthy, synchronized state, catching a scenario where an unplanned failover has occurred or a redundancy group has become split-brain. No sample objects were extracted for this module, so specific table names cannot be cited, but the module description confirms its scope is chassis-cluster failover and redundancy-group objects. This MIB is essential for HA-pair fault detection rather than general traffic monitoring.

What Can Be Monitored

redundancy group status
primary/secondary node role
failover events
cluster synchronization state

Imported Objects

From JUNIPER-JS-SMI

jnxJsChassisCluster

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxJsChassisClusterMIB	1.3.6.1.4.1.2636.3.39.1.14.1			Chassis Clustering is concerned with ensuring minimal disruption to data and control planes in case of a failover. If one of the chassis in a cluster fails, the other chassis in the cluster takes over the function of the failed chassis with minimal service interruption. This module defines the objects pertaining to Chassis Cluster.
jnxJsChassisClusterNotifications	1.3.6.1.4.1.2636.3.39.1.14.1.0
NTF jnxJsChassisClusterSwitchover	1.3.6.1.4.1.2636.3.39.1.14.1.0.1			Notification to signal switchover/failover.
NTF jnxJsChClusterIntfTrap	1.3.6.1.4.1.2636.3.39.1.14.1.0.2			Notification to signal node health status change (healthy/unhealthy).
NTF jnxJsChClusterSpuMismatchTrap	1.3.6.1.4.1.2636.3.39.1.14.1.0.3			Notification to signal cluster having different SPU number.
NTF jnxJsChClusterWeightTrap	1.3.6.1.4.1.2636.3.39.1.14.1.0.4			Notification to signal node health status change (healthy/unhealthy).
jnxJsChassisClusterTrapObjects	1.3.6.1.4.1.2636.3.39.1.14.1.1
STR jnxJsChClusterSwitchoverInfoRedundancyGroup	1.3.6.1.4.1.2636.3.39.1.14.1.1.1	DisplayString	accessible-for-notify	This object contains identification of redundancy group that switched over.
STR jnxJsChClusterSwitchoverInfoClusterId	1.3.6.1.4.1.2636.3.39.1.14.1.1.2	DisplayString	accessible-for-notify	This object contains cluster identification information where the switchover occured.
STR jnxJsChClusterSwitchoverInfoNodeId	1.3.6.1.4.1.2636.3.39.1.14.1.1.3	DisplayString	accessible-for-notify	This object contains node identification information where the switchover occured.
STR jnxJsChClusterSwitchoverInfoPreviousState	1.3.6.1.4.1.2636.3.39.1.14.1.1.4	DisplayString	accessible-for-notify	This object contains the redundancy state of the cluster before the occurance of switchover.
STR jnxJsChClusterSwitchoverInfoCurrentState	1.3.6.1.4.1.2636.3.39.1.14.1.1.5	DisplayString	accessible-for-notify	This object contains the redundancy state of the cluster after the occurance of switchover.
STR jnxJsChClusterSwitchoverInfoReason	1.3.6.1.4.1.2636.3.39.1.14.1.1.6	DisplayString	accessible-for-notify	This object contains the cause for switchover.
STR jnxJsChClusterIntfName	1.3.6.1.4.1.2636.3.39.1.14.1.1.7	DisplayString	accessible-for-notify	This object contains the name of the link that changed its state.
STR jnxJsChClusterIntfState	1.3.6.1.4.1.2636.3.39.1.14.1.1.8	DisplayString	accessible-for-notify	This object contains the state of the link; whether it is UP or DOWN.
STR jnxJsChClusterIntfSeverity	1.3.6.1.4.1.2636.3.39.1.14.1.1.9	DisplayString	accessible-for-notify	This object reflects the severity; whether it is minor or major.
STR jnxJsChClusterIntfStateReason	1.3.6.1.4.1.2636.3.39.1.14.1.1.10	DisplayString	accessible-for-notify	This object contains the reason why the link state changed.
STR jnxJsChClusterNodeZeroId	1.3.6.1.4.1.2636.3.39.1.14.1.1.11	DisplayString	accessible-for-notify	This object contains remote node identification information where the event occured.
STR jnxJsChClusterNodeOneId	1.3.6.1.4.1.2636.3.39.1.14.1.1.12	DisplayString	accessible-for-notify	This object contains remote node identification information where the event occured.
STR jnxJsChClusterNodeZeroSpuCount	1.3.6.1.4.1.2636.3.39.1.14.1.1.13	DisplayString	accessible-for-notify	This object contains local node total SPU number.
STR jnxJsChClusterNodeOneSpuCount	1.3.6.1.4.1.2636.3.39.1.14.1.1.14	DisplayString	accessible-for-notify	This object contains remote node total SPU number.
STR jnxJsChClusterClusterID	1.3.6.1.4.1.2636.3.39.1.14.1.1.15	DisplayString	accessible-for-notify	This object contains identification of cluster, in which the event occured.
STR jnxJsChClusterRedundancyGroupID	1.3.6.1.4.1.2636.3.39.1.14.1.1.16	DisplayString	accessible-for-notify	This object contains identification of RedundancyGroup, in which the event occured.
STR jnxJsChClusterNodeID	1.3.6.1.4.1.2636.3.39.1.14.1.1.17	DisplayString	accessible-for-notify	This object contains identification of node, in which the event occured.
STR jnxJsChClusterWeightHealthStatus	1.3.6.1.4.1.2636.3.39.1.14.1.1.18	DisplayString	accessible-for-notify	This object contains health status, whether is healthy or unhealthy.
STR jnxJsChClusterWeightValue	1.3.6.1.4.1.2636.3.39.1.14.1.1.19	DisplayString	accessible-for-notify	This object contains weight value.

RFC description

Manages chassis clustering for Juniper devices ensuring minimal disruption during failover with cluster status and traps.

Start monitoring Juniper SRX firewall (chassis cluster HA pair) 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-CLUSTER-MIB

What Is JUNIPER-CHASSIS-CLUSTER-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description