JUNIPER-SRX5000-SPU-MONITORING-MIB

All MIBs › JUNIPER-SRX5000-SPU-MONITORING-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2012--0-7-

Category: IP and Core Protocols, VPN and Security, Vendor: Juniper

Description: Monitors Security Processing Unit (SPU) performance on Juniper SRX5000 series firewalls, including CPU usage, current/max session counts, and IPv4/IPv6 flow session statistics.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring JUNIPER-SRX5000-SPU-MONITORING-MIB with a free 30-day trial of IPNetwork Monitor.

What Is JUNIPER-SRX5000-SPU-MONITORING-MIB?

JUNIPER-SRX5000-SPU-MONITORING-MIB is a Juniper Networks proprietary MIB monitoring SPU (Services Processing Unit) load on SRX5000-series firewall platforms. Its per-SPU table, keyed by FPC/SPU index, reports CPU and memory usage, current/maximum flow-session count (with IPv4/IPv6 breakdown), and current/maximum central-point (CP) session count (with IPv4/IPv6 breakdown), while a cluster-objects table reports per-node current/maximum total session count. As a performance MIB it lets an administrator watch SPU CPU/memory load and flow-session-table utilization to catch an SRX5000 firewall approaching capacity before it starts dropping new sessions. It is deployed on Juniper Networks SRX5000-series firewall platforms. Engineers can download the JUNIPER-SRX5000-SPU-MONITORING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-SRX5000-SPU-MONITORING-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 SRX5000-series firewall platforms

Monitoring Examples

An administrator monitors jnxJsSPUMonitoringCurrentFlowSession against jnxJsSPUMonitoringMaxFlowSession per SPU to catch an SRX5000 firewall approaching its session-table limit before new connections start failing.

What Can Be Monitored

per-SPU CPU/memory usage and flow/CP session utilization

Imported Objects

From HCNUM-TC

CounterBasedGauge64

From JUNIPER-JS-SMI

jnxJsSPUMonitoringRoot

OBJECT-IDENTITY

From SNMPv2-SMI

Gauge32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxJsSPUMonitoringMIB	1.3.6.1.4.1.2636.3.39.1.12.1			This is Juniper Networks' implementation of enterprise specific MIB for SRX5000 SPU monitoring.
jnxJsSPUMonitoringObjectsTable	1.3.6.1.4.1.2636.3.39.1.12.1.1		not-accessible	This table exposes SPUs utilization statistics.
jnxJsSPUMonitoringObjectsEntry	1.3.6.1.4.1.2636.3.39.1.12.1.1.1		not-accessible	Each entry collects CPU/Memory utilization for a SPU.
U32 jnxJsSPUMonitoringIndex	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.1	Unsigned32	not-accessible	SPU's overall index in platform.
U32 jnxJsSPUMonitoringFPCIndex	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.2	Unsigned32	read-only	Which FPC SPU is on.
U32 jnxJsSPUMonitoringSPUIndex	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.3	Unsigned32	read-only	SPU'Index inside the FPC.
U32 jnxJsSPUMonitoringCPUUsage	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.4	Unsigned32	read-only	Current SPU(CPU) Utilization in percentage.
U32 jnxJsSPUMonitoringMemoryUsage	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.5	Unsigned32	read-only	Current memory usage of SPU(CPU) in percentage.
U32 jnxJsSPUMonitoringCurrentFlowSession	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6	Unsigned32	read-only	Current flow session number of SPU.
U32 jnxJsSPUMonitoringMaxFlowSession	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7	Unsigned32	read-only	Max flow session number of SPU.
U32 jnxJsSPUMonitoringCurrentCPSession	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.8	Unsigned32	read-only	Current CP session number of SPU.
U32 jnxJsSPUMonitoringMaxCPSession	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.9	Unsigned32	read-only	Max CP session number of SPU.
U32 jnxJsSPUMonitoringNodeIndex	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.10	Unsigned32	read-only	This 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.
STR jnxJsSPUMonitoringNodeDescr	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.11	DisplayString	read-only	This 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.
U32 jnxJsSPUMonitoringFlowSessIPv4	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.12	Unsigned32	read-only	Current IPv4 flow session number of SPU.
U32 jnxJsSPUMonitoringFlowSessIPv6	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.13	Unsigned32	read-only	Current IPv6 flow session number of SPU.
U32 jnxJsSPUMonitoringCPSessIPv4	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.14	Unsigned32	read-only	Current IPv4 CP session number of SPU.
U32 jnxJsSPUMonitoringCPSessIPv6	1.3.6.1.4.1.2636.3.39.1.12.1.1.1.15	Unsigned32	read-only	Current IPv6 CP session number of SPU.
U32 jnxJsSPUMonitoringCurrentTotalSession	1.3.6.1.4.1.2636.3.39.1.12.1.2	Unsigned32	read-only	System level total session in use.
U32 jnxJsSPUMonitoringMaxTotalSession	1.3.6.1.4.1.2636.3.39.1.12.1.3	Unsigned32	read-only	System level max session possible.
jnxSPUClusterObjectsTable	1.3.6.1.4.1.2636.3.39.1.12.1.4		not-accessible	This table exposes SPU monitoring objects in HA cluster.
jnxSPUClusterObjectsEntry	1.3.6.1.4.1.2636.3.39.1.12.1.4.1		not-accessible	Each entry collects SPU monitoring contents in HA cluster.
U32 jnxJsClusterMonitoringNodeIndex	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.1	Unsigned32	not-accessible	This 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.
STR jnxJsClusterMonitoringNodeDescr	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.2	DisplayString	read-only	This 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.
U32 jnxJsNodeCurrentTotalSession	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.3	Unsigned32	read-only	Node total session in use.
U32 jnxJsNodeMaxTotalSession	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.4	Unsigned32	read-only	Node max session possible.
NUM jnxJsNodeSessionCreationPerSecond	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.5	CounterBasedGauge64	read-only	Node average session created in last 96 seconds.
NUM jnxJsNodeSessCreationPerSecIPv4	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.6	CounterBasedGauge64	read-only	Node average IPv4 session created in last 96 seconds.
NUM jnxJsNodeSessCreationPerSecIPv6	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.7	CounterBasedGauge64	read-only	Node average IPv6 session created in last 96 seconds.
U32 jnxJsNodeCurrentTotalSessIPv4	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.8	Unsigned32	read-only	Node total IPv4 session in use.
U32 jnxJsNodeCurrentTotalSessIPv6	1.3.6.1.4.1.2636.3.39.1.12.1.4.1.9	Unsigned32	read-only	Node total IPv6 session in use.
U32 jnxJsSPUMonitoringTotalSessIPv4	1.3.6.1.4.1.2636.3.39.1.12.1.5	Unsigned32	read-only	System level total IPv4 session in use.
U32 jnxJsSPUMonitoringTotalSessIPv6	1.3.6.1.4.1.2636.3.39.1.12.1.6	Unsigned32	read-only	System level total IPv6 session in use.

RFC description

Monitors SPU (Secure Processing Unit) performance on Juniper SRX5000 firewalls including CPU and memory utilization.

Start monitoring Juniper Networks SRX5000-series firewall platform (SPU load monitoring) 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-SRX5000-SPU-MONITORING-MIB

What Is JUNIPER-SRX5000-SPU-MONITORING-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description