jnxJsSPUMonitoringCurrentTotalSession
1.3.6.1.4.1.2636.3.39.1.12.1.2
Unsigned32
System level total session in use.
JUNIPER-SRX5000-SPU-MONITORING-MIB
2020-06-10
This is Juniper Networks' implementation of enterprise specific MIB for SRX5000 SPU monitoring.
Download JUNIPER-SRX5000-SPU-MONITORING-MIB.txt Open JUNIPER-SRX5000-SPU-MONITORING-MIB.txt in a new tab
SCALARS (9) · TABLES (3) · TRAPS (4)
Scalars (9)
Tables (3)
| Name | OID |
|---|---|
| jnxJsSPUMonitoringObjectsTable | 1.3.6.1.4.1.2636.3.39.1.12.1.1 |
| jnxSPUClusterObjectsTable | 1.3.6.1.4.1.2636.3.39.1.12.1.4 |
| jnxJsSPUMonitoringSPUThreadsTable | 1.3.6.1.4.1.2636.3.39.1.12.1.7 |
Traps (4)
END OF TOC
Scalar details
jnxJsSPUMonitoringMaxTotalSession
1.3.6.1.4.1.2636.3.39.1.12.1.3
Unsigned32
System level max session possible.
jnxJsSPUMonitoringTotalSessIPv4
1.3.6.1.4.1.2636.3.39.1.12.1.5
Unsigned32
System level total IPv4 session in use.
jnxJsSPUMonitoringTotalSessIPv6
1.3.6.1.4.1.2636.3.39.1.12.1.6
Unsigned32
System level total IPv6 session in use.
jnxJsResManCPUThreadIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.1
Unsigned32 (0..100)
The CPU Thread index
jnxJsResManCPUUtil
1.3.6.1.4.1.2636.3.39.1.12.1.8.2
Unsigned32 (0..100)
The CPU utilization in percentage.
jnxJsResManResourceUtil
1.3.6.1.4.1.2636.3.39.1.12.1.8.3
Unsigned32 (0..100)
The Resource utilization in percentage.
jnxJsResManFPCIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.4
Unsigned32
Which FPC SPU is on.
jnxJsResManSPUIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.5
Unsigned32
SPU'Index inside the FPC.
Table details
jnxJsSPUMonitoringObjectsTable
1.3.6.1.4.1.2636.3.39.1.12.1.1
Index: jnxJsSPUMonitoringIndex
This table exposes SPUs utilization statistics.
jnxJsSPUMonitoringIndex
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.1
Unsigned32
SPU's overall index in platform.
jnxJsSPUMonitoringFPCIndex
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.2
Unsigned32
Which FPC SPU is on.
jnxJsSPUMonitoringSPUIndex
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.3
Unsigned32
SPU'Index inside the FPC.
jnxJsSPUMonitoringCPUUsage
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.4
Unsigned32 · percent
Current SPU(CPU) Utilization in percentage.
jnxJsSPUMonitoringMemoryUsage
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.5
Unsigned32 · percent
Current memory usage of SPU(CPU) in percentage.
jnxJsSPUMonitoringCurrentFlowSession
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6
Unsigned32
Current flow session number of SPU.
jnxJsSPUMonitoringMaxFlowSession
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7
Unsigned32
Max flow session number of SPU.
jnxJsSPUMonitoringCurrentCPSession
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.8
Unsigned32
Current CP session number of SPU.
jnxJsSPUMonitoringMaxCPSession
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.9
Unsigned32
Max CP session number of SPU.
jnxJsSPUMonitoringNodeIndex
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.10
Unsigned32
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.
jnxJsSPUMonitoringNodeDescr
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.11
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a
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.
jnxJsSPUMonitoringFlowSessIPv4
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.12
Unsigned32
Current IPv4 flow session number of SPU.
jnxJsSPUMonitoringFlowSessIPv6
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.13
Unsigned32
Current IPv6 flow session number of SPU.
jnxJsSPUMonitoringCPSessIPv4
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.14
Unsigned32
Current IPv4 CP session number of SPU.
jnxJsSPUMonitoringCPSessIPv6
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.15
Unsigned32
Current IPv6 CP session number of SPU.
jnxJsSPUMonitoringSPUThreadsNumber
1.3.6.1.4.1.2636.3.39.1.12.1.1.1.16
Unsigned32
Number of threads for an SPU.
jnxSPUClusterObjectsTable
1.3.6.1.4.1.2636.3.39.1.12.1.4
Index: jnxJsClusterMonitoringNodeIndex
This table exposes SPU monitoring objects in HA cluster.
jnxJsClusterMonitoringNodeIndex
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.1
Unsigned32
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.
jnxJsClusterMonitoringNodeDescr
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.2
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a
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.
jnxJsNodeCurrentTotalSession
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.3
Unsigned32
Node total session in use.
jnxJsNodeMaxTotalSession
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.4
Unsigned32
Node max session possible.
jnxJsNodeSessionCreationPerSecond
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.5
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Node average session created in last 96 seconds.
jnxJsNodeSessCreationPerSecIPv4
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.6
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Node average IPv4 session created in last 96 seconds.
jnxJsNodeSessCreationPerSecIPv6
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.7
CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64
Node average IPv6 session created in last 96 seconds.
jnxJsNodeCurrentTotalSessIPv4
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.8
Unsigned32
Node total IPv4 session in use.
jnxJsNodeCurrentTotalSessIPv6
1.3.6.1.4.1.2636.3.39.1.12.1.4.1.9
Unsigned32
Node total IPv6 session in use.
jnxJsSPUMonitoringSPUThreadsTable
1.3.6.1.4.1.2636.3.39.1.12.1.7
Index: jnxJsSPUMonitoringIndex · jnxJsSPUMonitoringSPUThreadIndex
This table exposes threads utilization statistics for an SPU.
jnxJsSPUMonitoringSPUThreadIndex
1.3.6.1.4.1.2636.3.39.1.12.1.7.1.1
Unsigned32
Thread index on an SPU.
jnxJsSPUMonitoringSPUThreadLastMinUsage
1.3.6.1.4.1.2636.3.39.1.12.1.7.1.2
Unsigned32
Thread utilization of last minute.
jnxJsSPUMonitoringSPUThreadLastHourUsage
1.3.6.1.4.1.2636.3.39.1.12.1.7.1.3
Unsigned32
Thread utilization of last hour.
jnxJsSPUMonitoringSPUThreadLastDayUsage
1.3.6.1.4.1.2636.3.39.1.12.1.7.1.4
Unsigned32
Thread utilization of last day.
Trap details
jnxJsResManCPUThresholdStatus
1.3.6.1.4.1.2636.3.39.1.12.1.9.1
The 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.
jnxJsResManCPUThreadIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.1
Unsigned32 (0..100)
The CPU Thread index
jnxJsResManCPUUtil
1.3.6.1.4.1.2636.3.39.1.12.1.8.2
Unsigned32 (0..100)
The CPU utilization in percentage.
jnxJsResManSessionThresholdStatus
1.3.6.1.4.1.2636.3.39.1.12.1.9.2
The 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.
jnxJsResManFPCIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.4
Unsigned32
Which FPC SPU is on.
jnxJsResManSPUIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.5
Unsigned32
SPU'Index inside the FPC.
jnxJsResManResourceUtil
1.3.6.1.4.1.2636.3.39.1.12.1.8.3
Unsigned32 (0..100)
The Resource utilization in percentage.
jnxJsResManServicesMemoryStatus
1.3.6.1.4.1.2636.3.39.1.12.1.9.3
The 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.
jnxJsResManFPCIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.4
Unsigned32
Which FPC SPU is on.
jnxJsResManSPUIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.5
Unsigned32
SPU'Index inside the FPC.
jnxJsResManResourceUtil
1.3.6.1.4.1.2636.3.39.1.12.1.8.3
Unsigned32 (0..100)
The Resource utilization in percentage.
jnxJsResManPacketMemoryStatus
1.3.6.1.4.1.2636.3.39.1.12.1.9.4
The 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.
jnxJsResManFPCIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.4
Unsigned32
Which FPC SPU is on.
jnxJsResManSPUIndex
1.3.6.1.4.1.2636.3.39.1.12.1.8.5
Unsigned32
SPU'Index inside the FPC.
jnxJsResManResourceUtil
1.3.6.1.4.1.2636.3.39.1.12.1.8.3
Unsigned32 (0..100)
The Resource utilization in percentage.