JUNIPER-SRX5000-SPU-MONITORING-MIB
Updated Jun 10, 2020AI MIB Summary
The JUNIPER-SRX5000-SPU-MONITORING-MIB enables SNMP-based monitoring of Service Processing Unit (SPU) health, resource utilization, and operational status on Juniper SRX5000 series services gateways. It provides granular visibility into SPU-specific metrics such as CPU load, memory usage, packet processing rates, and interface statistics to facilitate capacity planning and fault isolation within high-performance firewall clusters.
This is Juniper Networks' implementation of enterprise specific MIB for SRX5000 SPU monitoring.
Main OID:
jnxJsSPUMonitoringMIB.1.3.6.1.4.1.2636.3.39.1.12.1
51
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
51 total| Object Name |
|---|
jnxJsSPUMonitoringMIBThis is Juniper Networks' implementation of enterprise
specific MIB for SRX5000 SPU monitoring. MODULE-IDENTITY .1.3.6.1.4.1.2636.3.39.1.12.1 |
jnxJsSPUMonitoringObjectsTableThis table exposes SPUs utilization statistics. SEQUENCE OF JnxJsSPUMonitoringObjectsEntry .1.3.6.1.4.1.2636.3.39.1.12.1.1 |
jnxJsSPUMonitoringObjectsEntryEach entry collects CPU/Memory utilization for a SPU. JnxJsSPUMonitoringObjectsEntry .1.3.6.1.4.1.2636.3.39.1.12.1.1.1 |
jnxJsSPUMonitoringIndexSPU's overall index in platform. Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.1 |
jnxJsSPUMonitoringFPCIndexWhich FPC SPU is on.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.2 |
jnxJsSPUMonitoringSPUIndexSPU'Index inside the FPC.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.3 |
jnxJsSPUMonitoringCPUUsageCurrent SPU(CPU) Utilization in percentage.ro Unsigned32 UNITS "percent" .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.4 |
jnxJsSPUMonitoringMemoryUsageCurrent memory usage of SPU(CPU) in percentage.ro Unsigned32 UNITS "percent" .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.5 |
jnxJsSPUMonitoringCurrentFlowSessionCurrent flow session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6 |
jnxJsSPUMonitoringMaxFlowSessionMax flow session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7 |
jnxJsSPUMonitoringCurrentCPSessionCurrent CP session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.8 |
jnxJsSPUMonitoringMaxCPSessionMax CP session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.9 |
jnxJsSPUMonitoringNodeIndexThis attribute is used to identify a chassis. A chassis can
be configured in a single or cluster mode. When it is in a
cluster mode, the chassis can be denote as a cluster node.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.10 |
jnxJsSPUMonitoringNodeDescrThis attribute is used to describe the chassis/cluster
node information. Chassis can be configured as a single, or
cluster node. When it is cluster mode, the chassis can be
denoted as a cluster node.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.11 |
jnxJsSPUMonitoringFlowSessIPv4Current IPv4 flow session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.12 |
jnxJsSPUMonitoringFlowSessIPv6Current IPv6 flow session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.13 |
jnxJsSPUMonitoringCPSessIPv4Current IPv4 CP session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.14 |
jnxJsSPUMonitoringCPSessIPv6Current IPv6 CP session number of SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.15 |
jnxJsSPUMonitoringSPUThreadsNumberNumber of threads for an SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.1.1.16 |
jnxJsSPUMonitoringCurrentTotalSessionSystem level total session in use.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.2 |
jnxJsSPUMonitoringMaxTotalSessionSystem level max session possible.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.3 |
jnxSPUClusterObjectsTableThis table exposes SPU monitoring objects in HA cluster. SEQUENCE OF JnxSPUClusterObjectsEntry .1.3.6.1.4.1.2636.3.39.1.12.1.4 |
jnxSPUClusterObjectsEntryEach entry collects SPU monitoring contents in HA cluster. JnxSPUClusterObjectsEntry .1.3.6.1.4.1.2636.3.39.1.12.1.4.1 |
jnxJsClusterMonitoringNodeIndexThis attribute is used to identify a chassis. A chassis can
be configured in a single or cluster mode. When it is in a
cluster mode, the chassis can be denote as a cluster node. Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.1 |
jnxJsClusterMonitoringNodeDescrThis attribute is used to describe the chassis/cluster
node information. Chassis can be configured as a single, or
cluster node. When it is cluster mode, the chassis can be
denoted as a cluster node.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.2 |
jnxJsNodeCurrentTotalSessionNode total session in use.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.3 |
jnxJsNodeMaxTotalSessionNode max session possible.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.4 |
jnxJsNodeSessionCreationPerSecondNode average session created in last 96 seconds.ro CounterBasedGauge64 (HCNUM-TC) .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.5 |
jnxJsNodeSessCreationPerSecIPv4Node average IPv4 session created in last 96 seconds.ro CounterBasedGauge64 (HCNUM-TC) .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.6 |
jnxJsNodeSessCreationPerSecIPv6Node average IPv6 session created in last 96 seconds.ro CounterBasedGauge64 (HCNUM-TC) .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.7 |
jnxJsNodeCurrentTotalSessIPv4Node total IPv4 session in use.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.8 |
jnxJsNodeCurrentTotalSessIPv6Node total IPv6 session in use.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.4.1.9 |
jnxJsSPUMonitoringTotalSessIPv4System level total IPv4 session in use.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.5 |
jnxJsSPUMonitoringTotalSessIPv6System level total IPv6 session in use.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.6 |
jnxJsSPUMonitoringSPUThreadsTableThis table exposes threads utilization statistics for an SPU. SEQUENCE OF JnxJsSPUMonitoringSPUThreadsEntry .1.3.6.1.4.1.2636.3.39.1.12.1.7 |
jnxJsSPUMonitoringSPUThreadsEntryEntry collects CPU utilization statistics for a thread. JnxJsSPUMonitoringSPUThreadsEntry .1.3.6.1.4.1.2636.3.39.1.12.1.7.1 |
jnxJsSPUMonitoringSPUThreadIndexThread index on an SPU.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.7.1.1 |
jnxJsSPUMonitoringSPUThreadLastMinUsageThread utilization of last minute.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.7.1.2 |
jnxJsSPUMonitoringSPUThreadLastHourUsageThread utilization of last hour.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.7.1.3 |
jnxJsSPUMonitoringSPUThreadLastDayUsageThread utilization of last day.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.7.1.4 |
jnxJsResManTrapVars OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.12.1.8 |
jnxJsResManCPUThreadIndexThe CPU Thread indexro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.8.1 |
jnxJsResManCPUUtilThe CPU utilization in percentage.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.8.2 |
jnxJsResManResourceUtilThe Resource utilization in percentage.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.8.3 |
jnxJsResManFPCIndexWhich FPC SPU is on.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.8.4 |
jnxJsResManSPUIndexSPU'Index inside the FPC.ro Unsigned32 .1.3.6.1.4.1.2636.3.39.1.12.1.8.5 |
jnxJsResManNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.12.1.9 |
jnxJsResManCPUThresholdStatusThe Resource Manager CPU untilization threshold status
trap signifies that the CPU load on system has bypassed a
certain percentage, or clear of that percentage.
jnxJsResManCPUThreadIndex: Thread index on an SPU, if thread
affinity, else 0
jnxJsResManCPUUtil is the weighted percentage of utilization
of the CPU. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.3.39.1.12.1.9.1 |
jnxJsResManSessionThresholdStatusThe Resource Manager Session untilization threshold status
trap signifies that the Session load on system has bypassed a
certain percentage
jnxJsResManFPCIndex: FPC Index
jnxJsResManSPUIndex: SPU Index
jnxJsResManResourceUtil is the weighted percentage of utilization
of the Sessions. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.3.39.1.12.1.9.2 |
jnxJsResManServicesMemoryStatusThe Resource Manager Services Data Objcache untilization threshold status
trap signifies that the Services Memory load on system has bypassed a
certain percentage
jnxJsResManFPCIndex: FPC Index
jnxJsResManSPUIndex: SPU Index
jnxJsResManResourceUtil is the weighted percentage of utilization
of the Services Memory. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.3.39.1.12.1.9.3 |
jnxJsResManPacketMemoryStatusThe Resource Manager Packet Memory untilization threshold status
trap signifies that the Packet Memory load on system has bypassed a
certain percentage
jnxJsResManFPCIndex: FPC Index
jnxJsResManSPUIndex: SPU Index
jnxJsResManResourceUtil is the weighted percentage of utilization
of the Packet Memory. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.3.39.1.12.1.9.4 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →JUNIPER-CHASSIS-DEFINES-MIB
The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
5187 objects→
JUNIPER-MOBILE-GATEWAY-GTP-MIB
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
1616 objects→
GGSN-MIB
SNMP MIB module
789 objects→
JUNIPER-IFOPTICS-MIB
SNMP MIB module
754 objects→
JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
683 objects→
JUNIPER-IPSEC-FLOW-MON-MIB
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.
453 objects→