UC4Vers2-MIB :: blkJPRunNr

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsUC4Vers2-MIBblkJPRunNr

blkJPRunNr

Module: UC4Vers2-MIB

OID (symbolic): UC4Vers2-MIB::blkJPRunNr

OID (numeric): 1.3.6.1.4.1.2562.1.1.8.1.1.3

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The run number of the job plan where blocking occurred.

What is blkJPRunNr?

Identifies the specific run number of the job plan in which this blocking condition occurred. An admin uses this to pull up the exact job-plan execution instance responsible for the block, rather than just the job plan's static definition.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2562.1.1.8.1.1.3
snmpwalk -v2c -c public <target> UC4Vers2-MIB::blkJPRunNr

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2562.1.1.8.1.1.3.1
snmpget -v2c -c public <target> UC4Vers2-MIB::blkJPRunNr.1

Start monitoring UC4 (Automic/Broadcom) workload-automation platforms (agent uptime/connection-count status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UC4Vers2-MIB::blkJPRunNr OID value, configure state conditions and alerts, and monitor any UC4 (Automic/Broadcom) workload-automation platforms (agent uptime/connection-count status) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.2562sbbUC4Vers2-MIB
1.3.6.1.4.1.2562.1uc4UC4Vers2-MIB
1.3.6.1.4.1.2562.1.1vers1UC4Vers2-MIB
1.3.6.1.4.1.2562.1.1.8blockingPointsUC4Vers2-MIB
1.3.6.1.4.1.2562.1.1.8.1blockingPointsTableUC4Vers2-MIB
1.3.6.1.4.1.2562.1.1.8.1.1blockingPointEntryUC4Vers2-MIB
1.3.6.1.4.1.2562.1.1.8.1.1.3blkJPRunNrUC4Vers2-MIB