All MIBs › XEROX-JOB-MONITORING-MIB › xcmJobPagesCompleted
xcmJobPagesCompleted
Module: XEROX-JOB-MONITORING-MIB
OID (symbolic): XEROX-JOB-MONITORING-MIB::xcmJobPagesCompleted
OID (numeric): 1.3.6.1.4.1.253.8.59.10.1.1.11
Node type: OBJECT-TYPE
Type: Counter32
Access: read-only
Description: For the MIB: this object is generalized so that it applies to scanning as well as printing.
ISO DPA: Pages-completed This attribute indicates the number of pages of the job that the printer(s) have completed printing.
NOTE - The number of source pages, impressions and sheets of media may differ. The following examples illustrate how they may differ when attributes, rather than the document contents, control the printing. If number-up is 0 or 1, there is one source page per impression, and if number-up is 2, there are two source pages per impression. If sides is 1, there is one impression per sheet of media, but if sides is 2, there are two impressions per sheet of media. By inference, if number-up is 4 and sides is 2, there are 4 source pages per impression and 8 source pages per sheet of media.
The server shall not reset its value during the processing of multiple copies of documents or the job. Since this attribute is intended to measure the progress of a job, the value shall include repeated pages due to multiple copies. When the job completes, this attribute should contain the value of the total number of source pages that the printer processed for the print-job.
The accuracy of this value is implementation-dependent. It is expected that the value reported is never greater than the actual value. This attribute may not be supported for all printers and all page description languages.
The value of this attribute shall be 0 if printing has not started for this job.
What is xcmJobPagesCompleted?
This read-only Counter32 tracks the cumulative number of source pages the device has finished processing for this job, generalized here to cover scanning as well as printing; it doesn't reset across multiple copies and stays at 0 until processing actually starts. An admin polls this to track a large job's real-time progress, expecting the number of pages, impressions, and media sheets to differ when number-up or duplex settings are in play.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.253.8.59.10.1.1.11 snmpwalk -v2c -c public <target> XEROX-JOB-MONITORING-MIB::xcmJobPagesCompleted
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.253.8.59.10.1.1.11.1 snmpget -v2c -c public <target> XEROX-JOB-MONITORING-MIB::xcmJobPagesCompleted.1
Start monitoring Xerox network printers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XEROX-JOB-MONITORING-MIB::xcmJobPagesCompleted OID value, configure state conditions and alerts, and monitor any Xerox network printers from a single console.
OID Breakdown
Upper-level ancestors (12 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.253 | xerox | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8 | xeroxCommonMIB | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59 | xcmJobMonMIB | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.10 | xcmJobGenExt | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.10.1 | xcmJobGenExtTable | XEROX-COMMON-MIB |
| 1.3.6.1.4.1.253.8.59.10.1.1 | xcmJobGenExtEntry | XEROX-COMMON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.253.8.59.10.1.1.11 | xcmJobPagesCompleted | XEROX-JOB-MONITORING-MIB |