Job-Monitoring-MIB :: jmJobKOctetsProcessed

MIB Reference — IPNetwork Monitor · Updated September 12, 2026

All MIBsJob-Monitoring-MIBjmJobKOctetsProcessed

jmJobKOctetsProcessed

Module: Job-Monitoring-MIB

OID (symbolic): Job-Monitoring-MIB::jmJobKOctetsProcessed

OID (numeric): 1.3.6.1.4.1.2699.1.1.1.3.1.1.6

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The total number of octets processed by the server or device

measured in units of K (1024) octets so far. The agent SHALL round the actual number of octets processed up to the next higher K. Thus 0 octets is represented as '0', 1-1024 octets is represented as '1', 1025-2048 octets is '2', etc. For printing devices, this value is the number interpreted by the page description language interpreter rather than what has been marked on media.

For implementations where multiple copies are produced by the interpreter with only a single pass over the data, the final value SHALL be equal to the value of the jmJobKOctetsPerCopyRequested object. For implementations where multiple copies are produced by the interpreter by processing the data for each copy, the final value SHALL be a multiple of the value of the jmJobKOctetsPerCopyRequested object.

NOTE - See the impressionsCompletedCurrentCopy and pagesCompletedCurrentCopy attributes for attributes that are reset on each document copy.

NOTE - The jmJobKOctetsProcessed object can be used with the jmJobKOctetsPerCopyRequested object to provide an indication of the relative progress of the job, provided that the multiplicative factor is taken into account for some implementations of multiple copies.

What is jmJobKOctetsProcessed?

This read-only value reports, in units of 1024 octets rounded up, how much data the device has processed for this job so far, which may be a multiple of jmJobKOctetsPerCopyRequested if multiple copies each require a separate processing pass. An admin compares it against jmJobKOctetsPerCopyRequested to gauge the job's progress. For example, seeing this value approach a multiple of the requested per-copy size confirms the job is nearing completion of all requested copies.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2699.1.1.1.3.1.1.6
snmpwalk -v2c -c public <target> Job-Monitoring-MIB::jmJobKOctetsProcessed

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2699.1.1.1.3.1.1.6.1
snmpget -v2c -c public <target> Job-Monitoring-MIB::jmJobKOctetsProcessed.1

Start monitoring Vendor-neutral IETF standard, RFC 2564 (network printers/print servers/MFDs) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Job-Monitoring-MIB::jmJobKOctetsProcessed OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard, RFC 2564 (network printers/print servers/MFDs) 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.2699.1.1jobmonMIBJob-Monitoring-MIB
1.3.6.1.4.1.2699.1.1.1jobmonMIBObjectsJob-Monitoring-MIB
1.3.6.1.4.1.2699.1.1.1.3jmJobJob-Monitoring-MIB
1.3.6.1.4.1.2699.1.1.1.3.1jmJobTableJob-Monitoring-MIB
1.3.6.1.4.1.2699.1.1.1.3.1.1jmJobEntryJob-Monitoring-MIB
1.3.6.1.4.1.2699.1.1.1.3.1.1.6jmJobKOctetsProcessedJob-Monitoring-MIB