JUNIPER-LSYSSP-FLOWSESS-MIB

All MIBs › JUNIPER-LSYSSP-FLOWSESS-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2010-05-19

Category: Vendor: Juniper

Description: Provides managed objects for flow session resource limits and usage per logical system security profile on Juniper Networks SRX devices.

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-LSYSSP-FLOWSESS-MIB?

JUNIPER-LSYSSP-FLOWSESS-MIB is part of the Juniper Logical System (LSYS) Security Profile MIB family, covering flow-session resource limits and usage for security profiles on SRX devices—LSYS lets a single physical SRX be partitioned into multiple logical systems each with resource quotas. It exposes resource-quota configuration and current-usage counters specifically for concurrent flow sessions per logical system. It is used to monitor a software resource-capacity metric—how many flow sessions a logical system is currently using versus its configured quota—helping detect a tenant approaching or hitting its session limit, similar to monitoring connection-table exhaustion. It is one of several sibling LSYSSP MIBs (scheduler, NAT-src-no-pat, secure-wire) that together model different resource types within the Juniper LSYS security-profile framework. It is typically deployed in multi-tenant Juniper SRX deployments where logical systems (virtual firewall instances) are provisioned with per-tenant resource limits, and administrators can download the JUNIPER-LSYSSP-FLOWSESS-MIB file to load it into their SNMP management tools.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-LSYSSP-FLOWSESS-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 SRX security devices (logical systems/multi-tenant deployments)

Monitoring Examples

No specific object names were provided for this MIB, but consistent with its description an admin would expect to poll a per-logical-system table for configured flow-session quota versus current flow-session count, in order to detect a tenant nearing its session limit—which could cause new connections for that logical system to be dropped once the quota is reached.

What Can Be Monitored

flow session quota limit
current flow session usage
per-logical-system resource utilization

Imported Objects

From JUNIPER-LSYS-SECURITYPROFILE-MIB

jnxLsysSpFlowsess

OBJECT-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxLsysSpFlowsessMIB	1.3.6.1.4.1.2636.3.39.1.17.6.1			This module defines the flow-session-specific MIB for Juniper Enterprise Logical-System (LSYS) security profiles. Juniper documentation is recommended as the reference. The LSYS security profile provides various static and dynamic resource management by observing resource quota limits. Security flow-session resource is the focus in this MIB.
jnxLsysSpFlowsessObjects	1.3.6.1.4.1.2636.3.39.1.17.6.1.1
jnxLsysSpFlowsessTable	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1		not-accessible	LSYSPROFILE flow-session objects for flow-session resource consumption per LSYS.
jnxLsysSpFlowsessEntry	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1.1		not-accessible	An entry in flow-session resource table.
STR jnxLsysSpFlowsessLsysName	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1.1.1	DisplayString	not-accessible	The name of the logical system for which flow-session resource information is retrieved.
STR jnxLsysSpFlowsessProfileName	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1.1.2	DisplayString	read-only	The security profile name string for the LSYS.
U32 jnxLsysSpFlowsessUsage	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1.1.3	Unsigned32	read-only	The current resource usage count for the LSYS.
U32 jnxLsysSpFlowsessReserved	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1.1.4	Unsigned32	read-only	The reserved resource count for the LSYS.
U32 jnxLsysSpFlowsessMaximum	1.3.6.1.4.1.2636.3.39.1.17.6.1.1.1.1.5	Unsigned32	read-only	The maximum allowed resource usage count for the LSYS.
jnxLsysSpFlowsessSummary	1.3.6.1.4.1.2636.3.39.1.17.6.1.2
U32 jnxLsysSpFlowsessUsedAmount	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.1	Unsigned32	read-only	The flow-session resource consumption over all LSYS.
U32 jnxLsysSpFlowsessMaxQuota	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.2	Unsigned32	read-only	The flow-session resource maximum quota for the whole device for all LSYS.
U32 jnxLsysSpFlowsessAvailableAmount	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.3	Unsigned32	read-only	The flow-session resource available in the whole device.
U32 jnxLsysSpFlowsessHeaviestUsage	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.4	Unsigned32	read-only	The most amount of flow-session resource consumed of a LSYS.
STR jnxLsysSpFlowsessHeaviestUser	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.5	DisplayString	read-only	The LSYS name that consume the most flow-session resource.
U32 jnxLsysSpFlowsessLightestUsage	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.6	Unsigned32	read-only	The least amount of flow-session resource consumed of a LSYS.
STR jnxLsysSpFlowsessLightestUser	1.3.6.1.4.1.2636.3.39.1.17.6.1.2.7	DisplayString	read-only	The LSYS name that consume the least flow-session resource.

RFC description

Manages flow-session resource consumption in Juniper logical-system security profiles.

Start monitoring Juniper SRX security device (logical-system flow-session quota) 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-LSYSSP-FLOWSESS-MIB

What Is JUNIPER-LSYSSP-FLOWSESS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description