Description

SNMP OID to monitor current and maximum sessions on SRX 5000 Series

Solution

The OIDs to monitor the current and maximum sessions:
 

  • Name: jnxJsSPUMonitoringCurrentFlowSession
  • OID: 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6
  • Description: Current flow session number of SPU.

 

  • Name: jnxJsSPUMonitoringMaxFlowSession
  • OID: 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7
  • Description: Max flow session number of SPU.

 

  • Name: jnxJsSPUMonitoringCurrentCPSession
  • OID: 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.8
  • Description: Current CP session number of SPU.

 

  • Name:  jnxJsSPUMonitoringMaxCPSession
  • OID: 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.9
  • Description: Max CP session number of SPU.

 

Lab Test Results: 
Please note the lab tests were done on SRX 5800 with one SPC II card and the total number may vary with the number and/or type of SPC card being used.

 

labroot@jtac-5800> set cli timestamp                     
Mar 11 06:06:03
Mar 11 06:06:03
CLI timestamp set to: %b %d %T

 

labroot@jtac-5800> show security monitoring                
Mar 11 06:06:09
         Flow session  Flow session   CP session   CP session
FPC PIC CPU Mem    current    maximum    current    maximum
0  0  0 16          0       0            0       0
0  1  0 11          0    6291456         0    7549747
0  2  0 11          0    6291456         0    7549747
0  3  0 11          0    6291456         0    7549747
Total Sessions:      0    18874368        0    22649241

labroot@jtac-5800> show snmp mib walk 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6  
Mar 11 06:06:12
jnxJsSPUMonitoringCurrentFlowSession.0 = 0
jnxJsSPUMonitoringCurrentFlowSession.1 = 0
jnxJsSPUMonitoringCurrentFlowSession.2 = 0
jnxJsSPUMonitoringCurrentFlowSession.3 = 0

labroot@jtac-5800> show snmp mib walk 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7  
Mar 11 06:06:15
jnxJsSPUMonitoringMaxFlowSession.0 = 0
jnxJsSPUMonitoringMaxFlowSession.1 = 6291456
jnxJsSPUMonitoringMaxFlowSession.2 = 6291456
jnxJsSPUMonitoringMaxFlowSession.3 = 6291456

labroot@jtac-5800> show snmp mib walk 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.8  
Mar 11 06:06:17
jnxJsSPUMonitoringCurrentCPSession.0 = 0
jnxJsSPUMonitoringCurrentCPSession.1 = 0
jnxJsSPUMonitoringCurrentCPSession.2 = 0
jnxJsSPUMonitoringCurrentCPSession.3 = 0
labroot@jtac-5800> show snmp mib walk 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.9  
Mar 11 06:06:20
jnxJsSPUMonitoringMaxCPSession.0 = 0
jnxJsSPUMonitoringMaxCPSession.1 = 7549747
jnxJsSPUMonitoringMaxCPSession.2 = 7549747
jnxJsSPUMonitoringMaxCPSession.3 = 7549747

 

SNMP Walk also works as intended
 

jtac@linux-box% snmpwalk -v 2c -Ob -c public 10.85.147.39 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.6.0 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.6.1 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.6.2 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.6.3 = Gauge32: 0


jtac@linux-box% snmpwalk -v 2c -Ob -c public 10.85.147.39 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.7.0 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.7.1 = Gauge32: 6291456
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.7.2 = Gauge32: 6291456
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.7.3 = Gauge32: 6291456


jtac@linux-box% snmpwalk -v 2c -Ob -c public 10.85.147.39 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.8
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.8.0 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.8.1 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.8.2 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.8.3 = Gauge32: 0


jtac@linux-box% snmpwalk -v 2c -Ob -c public 10.85.147.39 1.3.6.1.4.1.2636.3.39.1.12.1.1.1.9
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.9.0 = Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.9.1 = Gauge32: 7549747
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.9.2 = Gauge32: 7549747
SNMPv2-SMI::enterprises.2636.3.39.1.12.1.1.1.9.3 = Gauge32: 7549747

 

SNMP MIB Explorer: https://apps.juniper.net/mib-explorer/navigate

Modification History

2024-03-12 : Article Created