JUNIPER-CHASSIS-CLUSTER-MIB :: jnxJsChClusterNodeZeroSpuCount

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-CHASSIS-CLUSTER-MIB › jnxJsChClusterNodeZeroSpuCount

jnxJsChClusterNodeZeroSpuCount

Module: JUNIPER-CHASSIS-CLUSTER-MIB

OID (symbolic): JUNIPER-CHASSIS-CLUSTER-MIB::jnxJsChClusterNodeZeroSpuCount

OID (numeric): 1.3.6.1.4.1.2636.3.39.1.14.1.1.13

Node type: OBJECT-TYPE

Type: DisplayString

Access: accessible-for-notify

Description: This object contains local node total SPU number.

What is jnxJsChClusterNodeZeroSpuCount?

This notification varbind reports the total number of Services Processing Units, or SPUs, on the local node, node 0. SPU count mismatches between cluster nodes can cause session-processing imbalance or cluster formation issues, so admins compare this against jnxJsChClusterNodeOneSpuCount when troubleshooting cluster health alerts. A value of 4 here, with node 1 also reporting 4, confirms both chassis have matching hardware capacity for cluster operation.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
1.3.6.1.4.1.2636.3.39jnxJsMibRootJUNIPER-SMI
1.3.6.1.4.1.2636.3.39.1jnxJsSecurityJUNIPER-JS-SMI
1.3.6.1.4.1.2636.3.39.1.14jnxJsChassisClusterJUNIPER-JS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.39.1.14.1jnxJsChassisClusterMIBJUNIPER-CHASSIS-CLUSTER-MIB
1.3.6.1.4.1.2636.3.39.1.14.1.1jnxJsChassisClusterTrapObjectsJUNIPER-CHASSIS-CLUSTER-MIB
1.3.6.1.4.1.2636.3.39.1.14.1.1.13jnxJsChClusterNodeZeroSpuCountJUNIPER-CHASSIS-CLUSTER-MIB